Delta RMC151 - Manual (Page 430)

RMC70/150 and RMCTools User Manual
• Allen-Bradley CompactLogix with Ethernet Interface Module (1769-ENBT)
• Allen-Bradley FlexLogix with Ethernet Interface Module (1788-ENBT)
• Allen-Bradley SoftLogix 5
• Allen-Bradley RSLinx
• Automation Direct DL05, DL06, DL205, DL405 with the Hn-ECOM100
• GE Fanuc RX3i with the ETM001 Ethernet Module
• Mitsubishi Q-Series with the QJ71MT91 or QJ71E71-100
• Modicon Quantum with the 140 NOE 711 00, 711 01, 711 10 and other Ethernet
TCP/IP modules
• Modicon Momentum M1E Processor
• Omron CS/CJ PLCs
• Siemens S7-300 controllers with PROFINET support
• Siemens S7-400 controllers with PROFINET support
• SoftPLC Corporation's SoftPLC
Note: If your Ethernet device is not listed above, then Delta recommends contacting one of
our sales engineers to discuss the device. There may be subtle problems with using some
devices with the RMC. For example, a device that proclaims Modbus/TCP support may only be
a slave device, and since the RMC is also a slave, neither device will initiate transfers,
preventing the devices from being able to work together. By talking with a sales engineer,
Delta receives feedback on the devices that customers want to communicate with and may
lead to enhancements in Delta’s documentation and device support.
General Communication Details
Communicating with an RMC involves doing the following:
• Reading and Writing Registers
Read and write to registers in the RMC just as you would with a PLC. Use the Register
Map topics to find the addresses of the RMC registers.
The RMC contains only 32-bit registers. Most are floating-point registers, but some
are double integers (DINT) or double words (DWORD). If your device only supports
16-bit integers, it may still be possible to communicate with the RMC, although the
communications will be limited and it will require more setup in the RMC.
• Issuing Commands
Issuing commands consists of writing to the command registers. The device must be
able to write to several registers at once. Issuing Commands topic for more details.
6.8.4. Communicating Directly over TCP
Master Ethernet controllers can communicate with the RMC using several methods. This topic
describes only one of those methods—using raw TCP packets—which is appropriate when the
master controller cannot use any of the other methods. Please review the other available
options in the Ethernet Overview topic before proceeding with this method.
This topic assumes that your controller has an established network platform and that you are
familiar with how to send and receive TCP data on that platform. Some PLCs provide access to
TCP connections using function blocks, while embedded controllers may require using a socket
interface such as Berkeley sockets. Proper use of these interfaces is outside the scope of this
documentation.
Protocol Overview
410 Delta Computer Systems, Inc.