Filter
Top Products
APPENDIX C: ETHERNET/IP – OBJECT MODEL
C.1.2 Message Router Object (0x02)
This object has no supported attributes.
C.1.3 Assembly Object (0x04 – 3 Instances)
Class Attributes
Attribute
ID
Name
Data
Type
Data Value Access Rule
1 Revision UINT 1 Get
2 Max Instance UINT 81 Get
Instance 0x64 Attributes (Input Instance)
Attribute
ID
Name
Data
Type
Default
Data
Value
Access
Rule
3 Status Information
Structure of:
Bitmap of Consume Instances with Data
Bitmap of Produce Instances with Data
DINT
DINT
0
0
Get
UDP I/O Sequence Number Handshaking
Valid sequence numbers are 1-65535. The producing device increments the data
sequence number by one on every new serial data packet. The device consuming
the data must echo the sequence number in the handshake location once the data is
processed to allow the producing Node to remove the data from the queue. This is
needed for I/O communications since UDP isn’t guaranteed to arrive in order.
If the Node ID number is passed as part of the I/O message, the message is stored
to the appropriate location in the Modbus RTU table. Since communications are
asynchronous, the Node ID number is also stored as part of the output data. It is the
responsibility of the PLC programmer to make sure the proper request lines up with
the proper response if the HS500E is used as a request/response device.
HS500E – OPERATOR’S MANUAL P/N: 17-1305 REV02 (12-05)
PAGE 66 OF 82