User manual

28 Publication ENET-UM001I-EN-P - January 2010
Chapter 1 EtherNet/IP Overview
Drive Configuration and Programming
The bridge can be an EtherNet/IP-to-DeviceNet bridging device or a
Logix5000 system with an EtherNet/IP communication module and a
DeviceNet communication module.
The bridge can be a:
• ControlLogix chassis with a 1756-ENBT, 1756-EN2F, 1756-EN2T,
1756-EN2TR, 1
756-EN2TXT, and 1756-DNB module.
The controller is not required.
• 1769-L23E-QB1B, 1756-L23E-QBFC1B, 1769-L32E, 1769-L35E
CompactLogix controller with 1769-SDN module
.
• 1768-L43 or 1768-L45 CompactLogix controller with 1768-ENBT
and
1769-SDN modules.
• 1788-EN2DN linking device.
Status data can also be transferred from a DeviceNet network through the
Logix5000 co
ntroller to a RSView32 operator interface. For a CompactLogix
or FlexLogix controller, map the data into the DeviceNet I/O image and then
use RSLinx OPC software from the workstation to the Logix5000 controller
over the EtherNet/IP network. This avoids using the limited bridging
resources of the CompactLogix or FlexLogix controller.
You cannot bridge EtherNet/IP I/O across networks. I/O modules must be
configure
d in either a local chassis or a remote chassis. You cannot go through
a gateway chassis to control I/O even though, in some circumstances,
RSLogix 5000 programming software accepts such a configuration in the I/O
Configuration folder.
Bridge
EtherNet/IP
PanelView Station
DeviceNet
Drive
Switch