Delta RMC151 - Manual (Page 460)

RMC70/150 and RMCTools User Manual
(16
bits)
Count
(16
bits)
(32
bits)
(32
bits)
(32
bits)
Description:
16-bit Count This is the number of 16-bit words read from the
buffer.
32-bit Read
Count
This is the number of 32-bit registers that the RMC
returned.
Data Item 1-n This is the returned data.
Communicating Directly over TCP
For RMC firmware versions prior to 3.31.0, in applications where none of the RMC’s
protocols are supported by the master controller, but direct communication over TCP is
allowed, Delta recommended that the Mitsubishi Procedure Exist protocol be implemented
by the user manually. The remainder of this topic describes how to manually implement
the Mitsubishi Procedure Exist protocol for communication with RMCs. Firmware versions
3.31.0 and newer support the Delta Motion Control Protocol (DMCP), which is the
preferred method of manual direct communication over TCP.
The RMC75E and RMC150E listen for Procedure Exist connections on TCP port
hexadecimal 7171 (decimal 29041). The client TCP port number can be any valid port
number. This protocol is a request/response protocol, meaning that the RMC will not send
any data unless it receives a packet requesting that it do so.
All multiple-byte fields are encoded with the least-significant byte first. For example, a
Packet Length value of 3 would be encoded as 03 00, and a 32-bit data value of
0x11223344 would be encoded as 44 33 22 11.
Writing Data to the RMC:
Writing to one or more registers in the RMC requires the following 2-packet sequence:
• First, the client sends the following packet to the RMC:
Offset Data
(hex)
Description
0-1 60 00 Sub-Header. These 2 bytes should always have
these values in a write request.
2-3 mm nn Packet Length. This value holds the number of 16-
bit words in this packet, not including this field and
the sub-header. For writing N registers to the RMC,
this register will hold 3+2xN, since each RMC register
uses 32 bits, or two 16-bit words.
4-5 00 00 Must be Zero. These two bytes must be zero (0) to
indicate a write.
6-7 ff ff Register File. This value holds the file portion of the
address of the first register to write to. For example,
for the IED 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 write to.
For example, for the IEC address %MD12.2, this field
would be 02 00.
10-... ... Data. The values of each 32-bit register to write
should follow the above header, with each register
encoded in 4 bytes ordered from the least- to most-
440 Delta Computer Systems, Inc.