Delta RMC101 - Manual (Page 344)

RMC100 and RMCWin User Manual
5-94
V10000-
V17777
Spline Download Area
Plot Registers:
Due to the limited addressing supported by the Automationdirect.com DirectLogic 205/405 PLCs,
plots cannot be read through the Ethernet.
5.2.6.3 EtherNet/IP Controllers
5.2.6.3.1 Using EtherNet/IP with the RMC ENET
EtherNet/IP is an exciting and innovative Ethernet protocol. This protocol is an open protocol
managed by the Open DeviceNet Vendor Association (ODVA), ControlNet International, and the
Industrial Ethernet Agency (IEA).
EtherNet/IP is innovative in that it combines the traditional messaging services with higher-
performance and more deterministic I/O services. Messaging can be used to send arbitrary data
between two devices using a request/response protocol. I/O is used to set up a specialized high-
speed connection between two or more devices using the producer consumer model.
For more information on EtherNet/IP refer to Rockwell Automation's EtherNet/IP Performance
and Application Guide
(Pub. No. ENET-AP001C-EN-P), or visit the EtherNet/IP web site at
http://www.ethernet-ip.org, where the specification and example source code can be downloaded
for free.
The RMC ENET supports both EtherNet/IP messaging and I/O.
Note: EtherNet/IP messaging requires RMC ENET firmware dated 20000420 or newer.
EtherNet/IP I/O requires RMC ENET firmware dated 20010724 or newer.
Using EtherNet/IP I/O with the RMC
The RMC can support I/O connections with up to four devices (PLCs, etc.). An I/O connection
sends specific data cyclically between the devices involved in the connection. This data is sent on
an interval called the Requested Packet Interval (RPI). The RMC supports an RPI from 5.0 ms up
to 3200.0 ms.
The Input data sent by the RMC includes one synchronization register followed by ten status
words for each axis in the module. The Output data sent to the RMC includes one
synchronization register followed by six command words for each axis in the module. Reading
and writing any registers other than the Status and Command registers requires use of
messaging. See Configuring an RMC EtherNet/IP I/O Connection for the ControlLogix and
Controlling the RMC over EtherNet/IP I/O for details.
Using EtherNet/IP Messaging with the RMC
EtherNet/IP supports messaging in addition to I/O connections. Messaging can be used to read
and write parameters, the Event Step table, splines, plots, status, and commands. In the
ControlLogix, MSG (message) blocks are used to read and write data in the RMC using
EtherNet/IP messaging. See Using Allen-Bradley Controllers with the RMC ENET for details.
EtherNet/IP Clients
The RMC is a passive EtherNet/IP device. It does not establish its own I/O connections, nor does