User Manual

6 Communication
significant byte.
• The RMC will respond to this request with the following packet:
Offset
Data
(hex)
Description
0
E0
Acknowledge. Indicates that the packet is an
acknowledgement.
1
rr
Response Code. Indicates whether the write was
successful or not. See the Response Codes section
below.
Reading Data from the RMC:
Reading from one or more registers in the RMC requires the following 4-packet sequence:
• The client sends the RMC a read request:
Offset
Data
(hex)
Description
0-1
60 00
Sub-Header. These 2 bytes should always have
these values in a read request.
2-3
03 00
Packet Length. This value holds the number of 16-
bit words in this packet, not including this field and
the sub-header. For read requests, this field will
always be 03 00.
4-5
mm nn
Read Count. This value holds the number of 32-bit
RMC registers to read. This value cannot be greater
than 382.
6-7
ff ff
Register File. This value holds the file portion of the
address of the first register to read from. For
example, for the IEC address %MD12.2, this field
would be 0C 00.
8-9
ee ee
Register Element. This value holds the element
portion of the address of the first register to read
from. For example, for the IEC address %MD12.2,
this field would be 02 00.
• The RMC acknowledges the request with the following short packet:
Offset
Data
(hex)
Description
0
E0
Acknowledge. Indicates that the packet is an
acknowledgement.
1
rr
Response Code. Indicates whether the read was
successful or not. See the Response Codes section
below.
• If the response above is success (00), then the RMC will then send a second packet,
holding the data requested:
Offset
Data
(hex)
Description
0-1
60 00
Sub-Header. These 2 bytes will always have these
values in a read response.
deltamotion.com 441