Delta RMC151 - Manual (Page 452)

RMC70/150 and RMCTools User Manual
The FINS protocol uses a three-stage addressing system: network address, node number, and
unit number. These three address elements have the following purposes:
• Network Address
This value identifies the network on which the target node resides. The PLC looks up
this number in its Local and Remote Network Tables to determine which local unit
number should be used to send out the request. For Ethernet systems, typically only
the Local Network Table is used to map a network address (for example, 1) to the unit
number on the ETN01 Ethernet Unit (for example, 0). See your Omron PLC and/or
CX-Programmer documentation for details on setting up the Local and Remote
Network Tables.
• Node Number
This value identifies the node on the network given by the network address. For
Ethernet networks, this number must be converted to an IP address. This conversion
is done by the ETN01 Ethernet Unit. Three methods are available. In the Automatic
Address Generation method, the IP address is derived by combining the ETN01's IP
Network Address (e.g. 192.168.0.0) with the Node Number (e.g. 5) to get an IP
Address (e.g. 192.168.0.5). In the IP Address Table method, each Node Number
maps to an IP Address via an entry in an IP Address Table. In the Combined method,
the IP Address Table is used first, but if the Node Number is not found in the table,
then the Automatic Address Generation method is used. See the Omron ETN01
Ethernet Unit manual for details on these methods.
• Unit Number
This value identifies the unit number on the rack of the remote node identified by the
Network Address and Node Number.
The RMC does not require manually setting these values in the RMC. Only the IP address
needs to be set in the RMC; see the RMC Ethernet Setup topic for details.
Addressing:
See the FINS Addressing topic for information on the FINS address of RMC registers.
Communicating Directly over UDP
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 UDP is
allowed, Delta recommended that FINS/UDP is implemented by the user manually. The
remainder of this topic describes how to manually implement FINS/UDP to communicate
with the RMC75E and RMC150E, ignoring the unused features and fields in the protocol.
Firmware versions 3.31.0 and newer support the Delta Motion Control Protocol (DMCP),
which is the preferred method of manual direct communication over UDP.
The RMC75E and RMC150E listen for FINS/UDP requests on UDP port 9600. The client
port number can be any number. This protocol is a request/response protocol, meaning
that for each request packet sent to the RMC, there will be one response packet sent by
the RMC. The only FINS/UDP commands used in this topic are CMD_MEM_AREA_READ
and CMD_MEM_AREA_WRITE.
Writing Data to the RMC
To send one or more registers to the RMC, send the following packet to the RMC:
Offset Data
(hex)
Description
0-8 80 00 02
00
00 00 00
00
00
Static Values. These 9 bytes should always have
these values in a write request.
9 kk Service ID. This value is simply echoed by the RMC
432 Delta Computer Systems, Inc.