Communication Module Requirements
At least one communication module is required in the same slot of each redundant chassis. Follow these requirements for communication modules in a redundant chassis with
ControlLogix®
5590 redundant controllers:- The following catalog numbers are supported:1756-EN4TR, 1756-EN4TRK, 1756-EN4TRXT, 1756-EN2TP, 1756-EN2F/C,1756-EN2TR/C, 1756-EN2T/D
- For communication between a redundant controller andsafetyI/O in a remote chassis, you must use a 1756-EN4TR, 1756-EN4TRK, or 1756-EN4TRXT communication module that is configured for concurrent communication. See Concurrent Communication to I/O.
- Use any combination of up to seven communication modules in each redundant chassis.
- Do not use the USB ports of communication modules to access the redundant system network while the system is online. Use of the USB ports while online can result in a loss of communication of traffic through the USB port after a switchover.
- Use the same firmware levels in a partnered set. The series for communication modules is not required to match in a partnered set. However, if your application requires a feature specific to a module series level, you must use the same series level for each module. For example, only the 1756-EN2T/C communication module offers the double-data rate (DDR) feature. You must use 1756-EN2T/C modules or later in each chassis of the redundant chassis pair to use DDR.
Plan for Communication Module Connections
A
CIP™
connection is a point-to-point communication mechanism that is used to transfer data between a producer and a consumer. These mechanisms are examples of CIP™
connections:- Logix 5000®controller message transfer toLogix 5000®controller
- I/O or produced tag
- Program upload
- PanelView™polling of aLogix 5000®controller
EtherNet/IP™
communication modules use CIP™
connection to connect devices. Three CIP™
connections are reserved for redundancy. You can use the remaining connections in any manner that your application requires.To determine the total number of
CIP™
connections supported by your communication module, see the ControlLogix Communication Modules Specifications Technical Data, publication 1756-TD003.Provide Feedback