PDO Assignment

The scope of the process data offered varies depending on the configured IO-Link ports.
“DeviceState Inputs Device” and “DeviceState Inputs” are selected by default. Device-specific PDOs (0x1A0n “Port (n-1) Process Data”) are only displayed after configuring on the respective port and restarting the EtherCAT system or reloading the configuration in Config mode; see Activating the configuration.

SM3, PDO Assignment 0x1C13
Index	Size (byte.bit)	Name	PDO content
0x1A81	2.0	DeviceState Inputs Device	Index 0xF101:0D - Device Diag Index 0xF101:10 - Device State
0x1A80	4.0	DeviceState Inputs	Index 0xF100:01 - State Ch1 Index 0xF100:02 - State Ch2 Index 0xF100:03 - State Ch3 Index 0xF100:04 - State Ch4
0x1A00	0.0 - 32.0	Port 1 Process Data	IO-Link device-specific / only active after configuration
0x1A01	0.0 - 32.0	Port 2 Process Data	IO-Link device-specific / only active after configuration
0x1A02	0.0 - 32.0	Port 3 Process Data	IO-Link device-specific / only active after configuration
0x1A03	0.0 - 32.0	Port 4 Process Data	IO-Link device-specific / only active after configuration

	Process data representation If data types are used that don’t conform to IEC61131-3, they are represented as octet strings.

The status of the IO-Link ports 1 to 4 is displayed via index 0xF100:0n.
The indexes 0xF101:xx provide general diagnosis data.

Index	Size (byte.bit)	Name	Meaning
0xF101:0D	0.1	Device Diag	Occurrence of events (on the device side) is reported via a status bit
0xF101:10	0.1	Device State	Interruption of communication with one of the slaves is reported via a status bit
0xF100:01	1.0	State Ch.1	See table “Meaning of status byte Ch. 1 - Ch. 4”
0xF100:02	1.0	State Ch.2
0xF100:03	1.0	State Ch.3
0xF100:04	1.0	State Ch.4

The status bytes are divided into two nibbles.

Meaning Status byte Ch. 1 - Ch. 4
Low nibble: 0x_0 = Port disabled 0x_1 = Port in std dig in 0x_2 = Port in std dig out 0x_3 = Port in communication OP 0x_4 = Port in communication COMSTOP / dig in Bit (only in std. IO Mode) 0x_5 = not defined 0x_6 = not defined 0x_7 = not defined 0x_8 = Process Data Invalid Bit Combinations are possible and are displayed as addition of the values (s. note)
Higher nibble: 0x1_ = Watchdog detected 0x2_ = internal Error 0x3_ = invalid Device ID 0x4_ = invalid Vendor ID 0x5_ = invalid IO-Link Version 0x6_ = invalid Frame Capability 0x7_ = invalid Cycle Time 0x8_ = invalid PD in length 0x9_ = invalid PD out length 0xA_ = no Device detected 0xB_ = error PreOP/Data storage Combinations are possible and are displayed as addition of the values (s. note)

Meaning Status byte Ch. 1 - Ch. 4

Low nibble:

0x_0 = Port disabled
0x_1 = Port in std dig in
0x_2 = Port in std dig out
0x_3 = Port in communication OP
0x_4 = Port in communication COMSTOP / dig in Bit (only in std. IO Mode)
0x_5 = not defined
0x_6 = not defined
0x_7 = not defined
0x_8 = Process Data Invalid Bit

Combinations are possible and are displayed as addition of the values (s. note)

Higher nibble:

0x1_ = Watchdog detected
0x2_ = internal Error
0x3_ = invalid Device ID
0x4_ = invalid Vendor ID
0x5_ = invalid IO-Link Version
0x6_ = invalid Frame Capability
0x7_ = invalid Cycle Time
0x8_ = invalid PD in length
0x9_ = invalid PD out length
0xA_ = no Device detected
0xB_ = error PreOP/Data storage

Combinations are possible and are displayed as addition of the values (s. note)

	Addition of the values in case of simultaneously occurring diagnostic messages If messages occur simultaneously, the value is displayed as a sum in the Status byte of the relevant channel. Often for example 0x03 “Port in communication OP” and 0x08 “Process Data Invalid Bit” occur simultaneously: 0x03 + 0x08 = 0x0B (11_dec) The value 0x0B (11_dec) is displayed in the Status byte.