RMCTools Online Help

EtherNet/IP (CIP)

EtherNet/IP (CIP)

EtherNet/IP is an open application protocol, maintained and distributed by ODVA (http://www.odva.org). EtherNet/IP is used by Ethernet modules for several PLC's including Allen Bradley, Schneider Electric, and Omron. EtherNet/IP is an Ethernet adaptation of the Control Information Protocol (CIP) in the same way that DeviceNet is a CAN adaptation of CIP and ControlNet is a CTDMA adaptation of CIP.

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 statements of conformance and EDS files are available for download from the Delta website at www.deltamotion.com.

The RMC75E, RMC150E, and RMC200 support EtherNet/IP Messaging and EtherNet/IP I/O.

EtherNet/IP I/O

EtherNet/IP I/O provides a mechanism of deterministically sending data in both directions between a PLC and remote device. This data is sent on an interval called the Requested Packet Interval (RPI). EtherNet/IP I/O is a very fast and easy-to-use method of communication. It reduces the amount of ladder logic required for communication, and communication occurs even when the PLC is in Program mode.

Supported RPI (Requested Packet Interval)

 

RMC75E

RMC150E

RMC200

Minimum RPI*

2 ms

2 ms

1 ms

*The RPI may not be less than the loop time to which the RMC is set.

 

The RMC supports only one controlling I/O connection at a time. Therefore, EtherNet/IP I/O cannot be used simultaneously with a PROFINET IO connection. Other protocols can be used simultaneously with EthetNet/IP.

To learn about setting up and using EtherNet/IP I/O, see the following topics:

EtherNet/IP Messaging

EtherNet/IP explicit messaging allows the originator (PLC or HMI) to request individual services from the target device (RMC). These requests are made explicitly rather than being scheduled cyclically like I/O. Explicit messaging is much more flexible than I/O in terms of what data or services are accessed in the target device, since I/O connections must pre-configure the I/O data to be exchanged.

In most cases, RMC users use EtherNet/IP Explicit messaging to read and write registers in the RMC. The RMC provides two methods for doing so. Also, some advanced EtherNet/IP users may want to access standard CIP services and attributes.

The three types of EtherNet/IP explicit messaging services users may want to use in the RMC are:

  • Read and/or write RMC registers using the Allen-Bradley PCCC/DF1 services.

  • Read and/or write RMC registers using the Data Table Object.

  • Access standard CIP services and attributes.

See Using EtherNet/IP Explicit Messaging for details on all three.

Supported Number of Connections

The maximum number of each type of connection supported by the RMCs is listed below:

Connection Type

RMC75E

RMC150E

RMC200

TCP

64

64

64

CIP

32

32

32

CIP I/O

4*

4*

4*

*Only one CIP connection can have output data sent from the PLC. The rest must be Input Only or Listen Only.

 

See Also

Ethernet Overview | Setting up an EtherNet/IP I/O Connection | Using an EtherNet/IP I/O Connection | Handling Broken EtherNet/IP I/O Connections | Troubleshooting EtherNet/IP I/O | Multiple EtherNet/IP I/O Connections | EtherNet/IP I/O Performance | Using EtherNet/IP Explicit Messaging | Using Allen-Bradley Controllers via Message Block | Using Allen-Bradley Controllers via EtherNet/IP I/O | Using Omron Controllers via EtherNet/IP I/O


Copyright (c) 2005-2016 by Delta Computer Systems, Inc.

\n\n\n\n\n\n