Commissioning and configuration
EPI4xxx, ERI4xxx
54
Version: 1.6
5.5
ADS access to device parameters
The exchange of the acyclic data takes place via a specified index and subindex range that is device-specific
and can be read about in the corresponding vendor documentation.
Parameter data exchange
An intelligent IO-Link sensor/actuator (in the previous figure marked "Sensor (IO-Link Device)") can support
parameterization by SPDU (Service Protocol Data Units). The PLC must explicitly query or, when marked as
such, send these acyclic service data.
SPDU access
TwinCAT supports access via ADS and via the EP6224-xxxxxx CoE directory.
The respective parameter is addressed via the so-called SPDU index. The following ranges are available:
Name
Index range
System
0x00 … 0x0F
Identification
0x10 … 0x1F
Diagnostic
0x20 … 0x2F
Communication
0x30 … 0x3F
Preferred Index
0x40 … 0xFE
Extended Index
0x0100 … 0x3FFF
the range 0x4000 … 0xFFFF is reserved
The use of the implementation of these ranges is the responsibility of the sensor/actuator vendor. In the
interest of clarity, only a few possible indices with names are listed here. Please refer to the corresponding
chapter "Object description and parameterization".
Index
Name
0010
Vendor Name
0011
Vendor Text
0012
Product Name
0013
Product ID
0015
Serial Number
0016
Hardware Revision
0017
Firmware Revision
...
...
ADS
Communication relating to IO-Link demand data is initiated via an ADS command. An ADS address always
consists of a NetID and PortNo. TwinCAT forwards an ADS command to the EP6224 Box module via AoE
(ADS over EtherCAT). From where the command is relayed to the IO-Link master section and therefore to
the data channel.
AoE-NetID
The EP6224 is assigned a dedicated AoE-NetID for communication with the IO-Link master section. This is
assigned by the configuration tool (see the figure below).