Delta RMC151 - Manual (Page 455)

6 Communication
Prefix Area Code
D 82
E0_ A0
E1_ A1
In the FINS/UDP protocol, the Starting Address is encoded as a 16-bit value with the
most-significant byte first.
Example
Find the FINS/UDP encoding for the RMC address %MD56.0.
By using the conversion tool in the FINS Addressing topic, we find that %MD56.0 is
represented by FINS Address D28672. Notice that the Low Address listed there as
well (D01536) can be ignored when using FINS/UDP in this manner. It is necessary
only when using PLCs that prevent the user from entering high addresses.
We separate the FINS Address into its prefix (D) and starting address (28672). By
using the prefix chart above, converting the starting address to hexadecimal
(0x7000) and appending the 00 bit address byte, we get the following FINS/UDP
encoding of our address:
82 70 00 00
FINS Response Codes
The response packet holds a two-byte Response Code field, indicating to the client
whether the transaction was successful or not. The RMC uses the following response
codes:
Response
Code
Description
00 00 Success.
04 01 Undefined Command. The 2-byte Command
field did not match a command supported by
the controller.
10 01 Packet Too Long. There were more bytes in
the packet than expected for the command
type.
10 02 Packet Too Short. There were fewer bytes
in the packet than expected for the command
type.
10 03 Bad Data Length. The amount of data in a
write request did not match the Write Length
field in the packet header.
11 01 Invalid Address Area Code. The Area Code
(first byte in the FINS Address field) is not a
valid value.
11 02 Size Error. Either the 4th byte in the FINS
Address field is non-zero, or the Read Length
or Write Length field is greater than 512.
11 03 Bad Starting Address. The 2-byte starting
address is greater than 0x7FFF.
11 04 Bad Ending Address. The 2-byte starting
address plus the read or write length exceeds
0x8000. A single read or write cannot cross
over memory areas.
deltamotion.com 435