Terminal configuration

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

BK2000 Lightbus Coupler

In the BK2000 Lightbus Coupler, the control/status byte is always 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 - example for KL3351

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 bytes are not evaluated, the terminals occupy 4 bytes of input data (2 bytes per channel)

Terminal configuration 2:
Mapping in the Profibus Coupler - example for KL3351

BK4000 Interbus Coupler

In delivery state, the BK4000 Interbus Coupler maps the terminals with 4 bytes of input data (2 bytes per channel).

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 KL3351

Other Bus Couplers and further information

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 chapter on Mapping in the Bus Coupler contains an overview of possible mapping configurations, depending on the configurable parameters.

Terminal configuration 4:

Parameterization with KS2000

The KS2000 configuration software can be used for parameterizations via the serial interface of the Bus Coupler, independent of the fieldbus system.