Terminal configuration

The terminal can be configured and parameterized via the internal register structure. Each terminal channel is mapped in the Bus Coupler. Depending on the type of the Bus Coupler and the mapping configuration (e.g. Motorola/Intel format, word alignment etc.) the terminal data are mapped in different ways to the Bus Coupler memory. For parameterizing a terminal, the control and status byte also has to be mapped.

BK2000 Lightbus Coupler

In the BK2000 Lightbus coupler, the control and status byte is mapped in addition to the data bytes. This is always located in the low byte at the offset address of the terminal channel.

Terminal configuration 1:
Mapping in the Lightbus Coupler_KL3202

BK3000 Profibus Coupler

For the BK3000 PROFIBUS coupler, the master configuration should specify for which terminal channels the control and status byte is to be inserted. If the control and status byte are not evaluated, the terminals occupy 2 bytes per channel:

  • KL3202: 4 bytes of input data
  • KL3224: 8 bytes of input data
Terminal configuration 2:
Mapping in the Profibus coupler – example for KL3202

BK4000 Interbus Coupler

The BK4000 Interbus Coupler maps the terminals in the delivery state with 2 bytes per channel:

  • KL3202: 4 bytes of input data
  • KL3224: 8 bytes of input data

Parameterization via the fieldbus is not possible. If the control and status byte is to be used, the KS2000 configuration software is required.

Terminal configuration 3:
Mapping in the Interbus coupler – example for KL3202

Further information about the mapping configuration of Bus Couplers can be found in the Appendix of the respective Bus Coupler manual under Master configuration.

The Appendix contains an overview of possible mapping configurations depending on the parameters that can be set.

Note
Parameterization with KS2000

The parameterizations can be carried out independently of the fieldbus system with the KS2000 configuration software via the serial configuration interface in the Bus Coupler.