Mapping in the Bus Coupler

The KL6051 is mapped into the bus coupler depending on the set parameters. The terminal always occupies memory space in the process image of the inputs and outputs.

Default for: CANopen, CANCAL, DeviceNET, ControlNet, RS232 and RS485

Conditions	I/O offset	High byte	Low byte
Full evaluation: no Motorola format: no Word alignment: any	3
	2
	1	D3	D2
	0	D1	D0

Default for: PROFIBUS and Interbus

Conditions	I/O offset	High byte	Low byte
Full evaluation: no Motorola format: yes Word alignment: any	3
	2
	1	D2	D3
	0	D0	D1

Conditions	I/O offset	High byte	Low byte
Full evaluation: yes Motorola format: no Word alignment: no	3
	2	D4	D3
	1	D2	D1
	0	D0	CT/ST

Conditions	I/O offset	High byte	Low byte
Full evaluation: yes Motorola format: yes Word alignment: no	3
	2	D3	D4
	1	D2	D0
	0	D1	CT/ST

Default for: Lightbus and Bus Terminal Controller (BCxxxx)

Conditions	I/O offset	High byte	Low byte
Full evaluation: yes Motorola format: no Word alignment: yes	3	D4	D3
	2	-	D2
	1	D1	D0
	0	-	CT/ST

Conditions	I/O offset	High byte	Low byte
Full evaluation: yes Motorola format: yes Word alignment: yes	3	D3	D4
	2	-	D2
	1	D0	D1
	0	-	CT/ST

Key

Complete evaluation	The terminal is mapped with control and status byte.
Motorola format	Motorola or Intel format can be set.
Word alignment	The terminal is positioned on a word limit in the Bus Coupler.
CT	Control byte (appears in the process image of the outputs).
ST	Status byte (appears in the process image of the inputs).
Ser.-CT	Control byte for the handshake (appears in the process image of the outputs).
Ser. ST	Status byte for the handshake (appears in the process image of the inputs).
D0-D4	Data byte 0 - 4
“-“	This byte is not used or occupied by the terminal.