Mapping In The Bus Coupler; Fig. 16 Mapping In The Interbus Coupler - Example For Kl3202 - Beckhoff KL3224 Documentation

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.
Fig. 16: 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.
Parameterization with KS2000
The parameterizations can be carried out independently of the fieldbus system with the KS2000 configura-
tion software via the serial configuration interface in the Bus Coupler.
5.2

Mapping in the Bus Coupler

As already described in the Terminal Configuration section, each Bus Terminal is mapped in the Bus
Coupler. This mapping is usually done with the default setting in the Bus Coupler / Bus Terminal. The
KS2000 configuration software or a master configuration software (e.g. ComProfibus or TwinCAT System
Manager) can be used to change this default setting.
If the terminals are fully evaluated, they occupy memory space in the input and output process image.
The following tables provide information about how the terminals map themselves in the Bus Coupler,
depending on the parameters set.
Default mapping for: CANopen, CANCAL, DeviceNet, ControlNet, Modbus, RS232 and RS485 Coupler
Conditions
Complete evaluation: no
Motorola format: no
Word alignment: any
KL3224
NOTE
Word offset
0
1
2
3
Version: 2.0.0
Access from the user program
High byte Low byte
Ch0 D1 Ch0 D0
Ch1 D1 Ch1 D0
Ch2 D1 Ch2 D0
Ch3 D1 Ch3 D0
25