Delta RMC151 - Manual (Page 456)

RMC70/150 and RMCTools User Manual
Example 1: Writing a Single Register
In this example, the client will write the value 0x11223344 to variable 0 (%MD56.0). The
FINS Address of the current value of variable 0 (%MD56.0) is 82 70 00 00, as shown in
the example in the FINS Address section above. The client chooses a Service ID of 00
for this packet, either because he is not using this field, or because this is the first
transaction. Finally, we must re-arrange the byte order on the value we are writing from
0x11223344 to 33 44 11 22.
The Write Length is two (2) because each 32-bit RMC register requires two 16-bit FINS
registers.
This gives us the following packet that should be sent to UDP port 9600 on the RMC:
80 00 02 00 00 00 00 00
00 00 01 02 82 70 00 00
00 02 33 44 11 22
After the RMC has successfully received and processed this write request, it will respond
with the following packet:
C0 00 02 00 00 00 00 00
00 00 01 02 00 00
Notice that the last two bytes are the response code, with 00 00 meaning success.
Example 2: Reading a Single Register
In this example, the client will read a value from variable 0 (%MD56.0). The FINS Address
of the current value of variable 0 (%MD56.0) is 82 70 00 00, as shown in the example in
the FINS Address section above. The client chooses a Service ID of 1, perhaps because
this is the second transaction.
The Read Length is two (2) because each 32-bit RMC register requires two 16-bit FINS
registers.
This gives us the following packet that should be sent to UDP port 9600 on the RMC:
80 00 02 00 00 00 00 00
00 00 01 01 82 70 00 00
00 02
After the RMC has successfully received and processed this write request, it will respond
with the following packet if variable 0 held the value 0x11223344:
C0 00 02 00 00 00 00 00
00 00 01 02 00 00 33 44
11 22
Notice that bytes 12-13 hold the response code, and byte 14-17 hold the data that was
read.
6.8.10.4. Mitsubishi Procedure Exist Protocol
The Mitsubishi Procedure Exist Ethernet protocol is for Mitsubishi's Q-series QJ71E71-100
Ethernet module and the FX3U PLC. It requires RMC firmware 1.60 or newer.
The QJ71E71-100 and FX3U support several communication protocols. The one that matches
the needs of the RMC is the Fixed Buffer communication with the Procedure Exist control
method. It allows the Mitsubishi PLC to read and write binary data from an RMC over Ethernet.
The RMC requires that the data sent via the Procedure Exist method is formatted as described
in this topic. The Procedure Exist protocol is described in chapter 7 of the Q Corresponding
Ethernet Interface Module User's Manual (Basic). The manual part number is SH (NA)-
080009-I. Search for 080009 on www.meau.com on the Downloads>>Manuals section. It is
also described in the FX3U manual User explanations for FX3U-ENET Ethernet Block
(manual no. JY997D18101, searchable on www.meau.com).
436 Delta Computer Systems, Inc.