The rule
ControlLogix enhanced redundancy does not allow I/O modules in the redundant controller chassis. All I/O has to sit in remote chassis reached over EtherNet/IP or ControlNet. The source is Rockwell's ControlLogix Redundancy User Manual, publication 1756-UM015.
Most single-controller systems were built with local I/O in the same chassis as the processor. That is what makes "just add a second one" impossible.
What the system actually needs
Starting from a typical single chassis with local I/O, the change is:
- A second controller, so there is a pair.
- Two 1756-RM2 redundancy modules and the fibre between them.
- Two chassis and two power supplies for the controller pair.
- An EtherNet/IP adapter in the old chassis, because once its controller moves out, that chassis becomes a remote I/O chassis on the network.
- The program reworked so every I/O reference points at the remote chassis.
Only one line on that list is the second controller.
How to check a redundancy proposal
- Is there any I/O drawn in the redundant chassis? If yes, the design does not work.
- Does the old I/O chassis have a network adapter in it, not a processor?
- Is the program rework in the scope, with a test plan?
- Is the cutover planned around your shutdown, with a way back?
We draw this rather than describe it. A Rockwell-literate engineer on the client side will test exactly this point, and a drawing that shows I/O in the redundant chassis loses the room in one look. It is also why the line should never be value-engineered down to "just the second controller": the design stops working.
Questions engineers ask
Can I put I/O modules in a ControlLogix redundant chassis?
No. ControlLogix enhanced redundancy requires all I/O to be in remote chassis over EtherNet/IP or ControlNet, per Rockwell publication 1756-UM015.
What hardware does ControlLogix redundancy need?
A pair of controllers, two 1756-RM2 redundancy modules with fibre, two chassis and power supplies for the pair, and network adapters in the I/O chassis, which become remote. The program also has to be reworked to the remote I/O.