Annex, Mapping in the bus coupler – BECKHOFF KL6001 User Manual
Page 17

Annex
KL6001
17
Annex
As already described in the chapter terminal configuration, each bus termi-
nal is mapped in the bus coupler. In the standard case, this mapping is
done with the default setting in the bus coupler / bus terminal. This default
setting can be modified with the Beckhoff KS2000 configuration software or
using master configuration software (e.g. ComProfibus or TwinCAT System
Manager). The following tables provide information on how the KL6001
maps itself in the bus coupler depending on the set parameters.
Mapping in the bus coupler
Standard format
In the standard format, by default the KL6001 is mapped with 4 bytes (ad-
justable: 2 to 6 bytes via R35) of input and output data.
Remark: in the standard format, the CT/ST byte is used for register and
process data communication.
I/O Offset
High Byte
Low Byte
Complete evaluation
= X
3
MOTOROLA format
= X
2
D4(opt.)
D3(opt.)
Word alignment
= X
1
D2(opt.)
D1(opt.)
0
D0
CT/ST
Alternative format
In the alternative format, the KL6001 is mapped with 4/6 bytes of input data
and 4/6 bytes of output data. When delivered the KL6001 is set to the al-
ternative format.
Remark: in the alternative format, the CT/ST byte is used only for register
communication and the serial CT/ST byte is used only for the data hand-
shake.
I/O Offset
High Byte
Low Byte
Complete evaluation
= 0
3
MOTOROLA format
= 0
2
Word alignment
= 0
1
D2
D1
Default: CANCAL,
CANopen, RS232,
RS485, ControlNet,
DeviceNet
0
D0
Ser-CT/ST
I/O Offset
High Byte
Low Byte
Complete evaluation
= 0
3
MOTOROLA format
= 1
2
Word alignment
= 0
1
D1
D2
Default: Interbus,
Profibus
0
Ser-CT/ST
D0
I/O Offset
High Byte
Low Byte
Complete evaluation
= 1
3
MOTOROLA format
= 0
2
D2
D1
Word alignment
= 0
1
--
D0
0
Ser-CT/ST
CT/ST
I/O Offset
High Byte
Low Byte
Complete evaluation
= 1
3
MOTOROLA format
= 1
2
D1
D2
Word alignment
= 0
1
--
Ser-CT/ST
0
D0
CT/ST