Supported devices for the Ethernet/IP Driver
Ethernet/IP is used to communicate with multiple generations and families of Rockwell Automation / Allen Bradley PLCs. The name can be confusing, and actually stands for [Common] Industrial Protocol over Ethernet. It is an application layer protocol, layered on top of standard TCP/IP networking.
There are two distinct families of PLCs with which this driver can be used, and they have significant operational differences. The newer devices such as ControlLogix, CompactLogix, and FlexLogix PLCs implement native CIP Protocol. This allows reads and writes using the actual tag-names from the PLC, complex tag structuring, and grouping of unrelated tags in a single message.
The older devices such as PLC5, SLC5, and MicroLogix implement PCCC/DF1 protocol, encapsulated in Ethernet/IP. These devices group their tags into very specific categories of File, Instance, and SubElement. Only requests for items within the same file can be grouped in a given request.
· Uses standard Ethernet networking hardware
· The WinCC OA system is always the master and initiates all connections and transactions (reads are polled)
· Through-routing to remote PLCs without an Ethernet connection is only supported for transparent interfaces such as the 1761-NET-ENI
· Supports WinCC OA Redundancy
Supported devices include the following:
PLC Series<o:p></o:p> | Model<o:p></o:p> | Protocol<o:p></o:p> | Interface<o:p></o:p> |
ControlLogix<o:p></o:p> | <o:p> </o:p> | Native EIP<o:p></o:p> | CPU Direct,<o:p></o:p> 1756-ENBT<o:p></o:p> 1756-ENET/B<o:p></o:p> |
CompactLogix<o:p></o:p> | 1769-L32E,<o:p></o:p> 1769-L35E<o:p></o:p> <o:p> </o:p> Other models<o:p></o:p> | Native EIP<o:p></o:p> | CPU Direct<o:p></o:p> <o:p> </o:p> <o:p> </o:p> 1768-ENBT,<o:p></o:p> 1761-NET-ENI<o:p></o:p> |
FlexLogix<o:p></o:p> | 1794-L34,<o:p></o:p> 1794-L33,<o:p></o:p> Other models<o:p></o:p> | Native EIP<o:p></o:p> | 1788,<o:p></o:p> 1761-NET-ENI<o:p></o:p> <o:p> </o:p> |
PLC5E<o:p></o:p> <o:p> </o:p> PLC5E,<o:p></o:p> PLC5C<o:p></o:p> | <o:p> </o:p> | PCCC<o:p></o:p> | CPU Direct<o:p></o:p> <o:p> </o:p> 1785-ENET,<o:p></o:p> 1761-NET-ENI<o:p></o:p> |
SLC500<o:p></o:p> | SLC 5/05<o:p></o:p> <o:p> </o:p> SLC 5/04,<o:p></o:p> SLC 5/03<o:p></o:p> | PCCC<o:p></o:p> | CPU Direct<o:p></o:p> <o:p> </o:p> 1761-NET-ENI<o:p></o:p> |
MicroLogix<o:p></o:p> | MicroLogix 1100,<o:p></o:p> MicroLogix 1400<o:p></o:p> <o:p> </o:p> MicroLogix 1100,<o:p></o:p> MicroLogix 1200,<o:p></o:p> MicroLogix 1500<o:p></o:p> | PCCC<o:p></o:p> | CPU Direct<o:p></o:p> <o:p> </o:p> <o:p> </o:p> 1761-NET-ENI<o:p></o:p> |
Some older devices may require firmware updates if they were not previously being used with Ethernet/IP.<o:p></o:p>
Other models supporting native EIP should also work if they have a built-in Ethernet port or an Ethernet interface card.<o:p></o:p>
Other models supporting PCCC should also work if they have a built-in Ethernet port supporting EIP encapsulation, or through a transparent Ethernet to serial bridge such as a 1761-NET-ENI.<o:p></o:p>
Note that the 1761-NET-ENI bridges to a PLC’s serial port, so compared to direct Ethernet, throughput will be reduced.<o:p></o:p>