EtherNet/IP is an open application protocol, maintained and distributed by ODVA (http://www.odva.org). EtherNet/IP 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.
The RMC is a passive EtherNet/IP device. It does not establish its own I/O connections, nor does it initiate messaging transactions. Therefore, an active EtherNet/IP device or client is required to control the RMC or request data from the RMC.
The RMC ENET supports both EtherNet/IP messaging and I/O. The RMC100 ENET statements of conformance and EDS files are available for download from the Delta website at www.deltamotion.com.
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 Setting Up an EtherNet/IP I/O Connection 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 it initiate messaging transactions. Therefore, an active EtherNet/IP device or client is required to control the RMC or request data from the RMC.
RMC ENET Supported Numbers of TCP and CIP Resources
TCP Connections:
4 TCP connections (all inbound)
Examples:
RMCWin
Each I/O connection is set up using an EtherNet/IP TCP connection
Any other PLC communication
CIP Connected Messaging:
The RMC ENET limits CIP connections as follows:
Max of 8 total CIP connections
Max of 4 I/O CIP connections
Examples:
I/O Data connection with a ControlLogix
Input Data connection with a ControlLogix
ControlLogix message to RMC ENET (cache enabled)
Copyright (c) 1997-2015 by Delta Computer Systems, Inc.