X20 system modules • Other functions • X20DS438A
X20 system User's Manual 3.10
2255
4.26.5.9.4.3 IdentificationDeviceID
Name:
CfO_IdentificationDeviceId01 to CfO_IdentificationDeviceId04
If the device ID should be verified during startup, then the expected ID of the IO-Link device must be specified in
Information:
If the expected ID does not match the actual ID of the connected IO-Link device, communication will
not be started for this channel.
Data type
Value
UDINT
0 to 4,294,967,295
4.26.5.9.4.4 PDI_TypeInfo
Name: CfO_PDI_TypeInfo01 to CfO_PDI_TypeInfo04
To transfer process data from the IO-Link device to the CPU (application), the information is first read from the
module and saved temporarily. Typically, four bytes are reserved for each piece for registered information (see
4.26.5.9.8 "IO-Link process data").
This register can be used to configure how the incoming IO-Link process data stream (IO-Link frame) is divided up.
According to this configuration, the IO-Link process data is made available to the application via the corresponding
InputData registers. The input data registers are assigned to individual data points with the corresponding data
type in the I/O mapping.
Data type
Value
UDINT
See bit structure.
Bit structure:
Bit
Description
Value
Information
0000
Array[4] of Bytes
0001
USINT
0010
SINT
0011
UINT
0100
INT
0101
UDINT
0110
DINT
0111
REAL
0 to 3
IO-Link information 1
1000 - 1111 Reserved
4 - 7
IO-Link information 2
8 - 11
IO-Link information 3
12 - 15
IO-Link information 4
16 - 19
IO-Link information 5
20 - 23
IO-Link information 6
24 - 27
IO-Link information 7
28 - 31
IO-Link information 8
Possible values are identical with IO-Link information 1
Information:
With setting 0 (Array[4] of Bytes), the bytes are copied from the IO-Link data stream unchanged. In all
other modes, the byte order is changed (from big endian to little endian).