Publication 1756-UM523F-EN-P - December 2006
ControlLogix Redundancy System Overview 21
Quick Start Checklists
These checklists provide a summary of the criteria for a successful
ControlLogix redundancy system. See the remaining chapters for more
information on each parameter.
System Layout
Parameter Criteria Page
ControlNet Networks • ControlNet networks are the primary networks for the system.
• OK to bridge to devices on other networks, such as DeviceNet, Universal Remote I/O,
and DH+ networks.
• Networks follow the guidelines in Logix5000 Controllers Design Considerations,
publication 1756-RM094.
28, 31
I/O Placement • All I/O modules in remote chassis or DIN rails (no I/O in the local chassis)
• All I/O in only these locations:
• Same ControlNet network as the redundant controllers (no bridging)
• DeviceNet network (via a 1756-DNB module in a remote chassis)
• Universal remote I/O network (via a 1756-DHRIO module in a remote chassis)
28, 31
ControlNet Network Update
Times
• NUTs ≤ 90 ms
• NUTs ≤ specified relationship to each other
35
Number of ControlNet Nodes At least 2 nodes on each network in addition to the CNBs in the redundant chassis. For
example, each ControlNet network has at least 4 nodes.
35
ControlNet Node Assignments • Nonredundant nodes use the lowest node numbers.
• CNB modules in the redundant chassis set close to the scheduled network maximum
(SMAX).
• 2 consecutive node addresses for each set of partner CNB modules (one in each
chassis).
• Switches of each partner CNB module set to the same node address.
18, 35
Network Access Ports No devices connected to the network access ports of CNB modules in the redundant
chassis.
28
EtherNet/IP Networks EtherNet/IP networks are only for HMIs, workstations, and messaging (no control of I/O).
No EtherNet/IP network for:
• control of I/O.
• peer interlocking (produced and consumed tags).
28, 38
To Next Page
Loading...
Need help?
General
