Справочник Пользователя для EMSA HS500E

A P P E N D I X C : E T H E R N E T / I P – O B J E C T M O D E L

C . 1 . 2 M e s s a g e R o u t e r O b j e c t ( 0 x 0 2 )

This object has no supported attributes.

C . 1 . 3 A s s e m b l y O b j e c t ( 0 x 0 4 – 3 I n s t a n c e s )

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

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.

H S 5 0 0 E – O P E R A T O R ’ S M A N U A L

P / N : 1 7 - 1 3 0 5 R E V 0 2 ( 1 2 - 0 5 )

P A G E 6 6 O F 8 2