765-1205/100-000
Appendix
Product manual | Version: 2.0.0
117
8DIO FLD EC DC 24V 2.0A
Table 85: Structure of the AoE Header
Offset
in the
AoE
Frame
Name
Description
6 ... 11
Target NetId
AoE NetId of the target
If the module is the target, use the AoE NetId assigned by the Ether-
CAT master for IO-Link communication for ISDU.
12 ... 13
Target Port
Port number of the target
14 ... 19
Source NetId
AoE NetId of the source
If the module is the source, use the AoE NetId assigned by the Ether-
CAT master for IO-Link communication for ISDU.
20 ... 21
Source Port
Port number of the source
22 ... 23
Command ID
Command number for selecting the AoE service
The command numbers of the AoE services relevant to ISDU are:
For reading (AoE Read command): 0x0002
For writing (AoE Write command): 0x0003
24 ... 25
State Flags
Status flags (see below)
26 ... 29
Data Size
Size of the data area in bytes.
30 ... 33
Error code
Error code (only for response packet)
For the possible error codes, see
8
.
34 ... 37
Invoke ID
Free 32 bit field.
You can use the
Invoke ID
to establish a link between the request
packet and response packet. This is necessary, for example, if AoE is
to be accessed multiple times simultaneously.
Parameter State Flags (Offset 24 ... 25):
Table 86: Parameter status flags
Bit
Description
0x01
1: for response packet (Response)
0: for request packet (Request)
0x04
1: if the packet contains an AoE command
0: otherwise
The AoE data area starts at offset 38 of the AoE mailbox frame, directly following the AoE
header. The data area contains one or more AoE commands of length Data Size (offset
26 ... 29).
Note
Additional information
A description of AoE and the underlying ADS protocol can be found in ETG specification
1020. The “Mailbox” section of ETG specification 5001.6220 describes how IO-Link ser-
vices are mapped to EtherCAT services.
14.1.4 ISDU Read Service
Parameter data is read from an object of an IO-Link device using the AoE mailbox proto-
col and IO-Link ISDU services.
