Publication 1756-UM523F-EN-P - December 2006
38 Design the System
Planning an EtherNet/IP
Network
Follow these guidelines as you plan your EtherNet/IP network.
EtherNet/IP Network Guidelines
Guideline Details
Use EtherNet/IP only for HMIs, workstations, and
messaging.
In a redundant system, use an EtherNet/IP network only for HMI, workstation,
and message communication. Do not use an EtherNet/IP network for:
• control of I/O modules.
• peer interlocking (produced and consumed tags).
Important: RSLogix 5000 software lets you set up and download a project
that tries to use an EtherNet/IP network for I/O, produced tags, or consumed
tags. Those communications do not work however.
Are communication delays OK during a switchover?
If Yes, then continue with EtherNet/IP.
If No, then use ControlNet.
Communication stops over an EtherNet/IP network with your controllers and
HMIs during a switchover.
• You will not be able to communicate with them for up to a minute.
• The actual delay depends on your network topology.
If you need bumpless communication, use a ControlNet network.
If you need a redundant network, use ControlNet. 2 EtherNet/IP modules in same chassis does not give you redundant
EtherNet/IP communication. A switchover still happens if one of the modules
fails or a cable breaks.
See How an EtherNet/IP Module Handles a Cable Break on page 40.
Make sure that your ENBT modules are catalog revision
E01 or later.
To use a 1756-ENBT module in a redundant controller chassis, make sure the
catalog revision of the module is greater than or equal to E01 (E01, E02, …,
F01).
• To find the catalog revision, look at the label on the side of the module or
box.
• If you use an older ENBT module, your secondary chassis will not
synchronize.
ControlLog
1756-ENBT
CAT. NO./SERIES
E01
CAT. REV.
Ethernet/IP 10/100
Catalog Revision
To Next Page
Loading...
Need help?
General
