1756 rn694 - en P PDF
1756 rn694 - en P PDF
1756 rn694 - en P PDF
Topic Page
Product Release Notes 2
About This Enhanced Redundancy Firmware Bundle 2
Compatible Software Versions 6
About the Redundancy Module Configuration Tool 7
These enhancements have been made in previous firmware revisions. 7
Corrected Anomalies 10
Known Anomalies 14
Restrictions 17
Application Notes 20
Upgrade the RSLogix 5000 Software Version 29
Replace a Module in the Secondary Chassis that has the Same Catalog Number and Firmware Revision 31
Replace 1756-EN2T, 1756-EN2TR, or 1756-EN2F Modules 32
Replace 1756-CN2 Modules 38
Upgrade the RSLogix 5000 Software Version and Replace 1756-EN2T, 1756-EN2TR or 1756-CN2 43
Upgrade the Firmware by Using Redundancy System Update 45
Update IP Address Set Via Software to Address Set Via Rotary Switches 65
Replace 1756-RM/B (or earlier) Modules with 1756-RM2 Modules 69
Storing a Project to a Nonvolatile Memory Card While Your Process Is Running 70
Access Product Release Notes 73
Additional Resources 74
Product Release Notes Product release notes for the individual products that are part of this
ControlLogix Enhanced Redundancy bundle are available online within the
Product Compatibility and Download Center.
For example, you can access release note information specific to the 1756-EN2T
ControlLogix EtherNet/IP bridge.
About This Enhanced This enhanced redundancy firmware bundle, which is identified as revision
20.056_kit1, contains series firmware revisions for each of the modules that are
Redundancy Firmware Bundle listed in Table 1, Required Series and Firmware Revisions for Components Used
in an Enhanced Redundancy System, Revision 20.056_kit1
You can download the firmware bundle at the Product Compatibility and
Download Center:
http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page?.
Information that has been added or changed since the last revision of this
publication is indicated by a change bar as shown next to this paragraph. In
addition to information specific to the most recent firmware revision, the
information from previous minor revisions is retained in these release notes.
IMPORTANT When designing, installing, and operating the redundant chassis pair (RCP) for this
enhanced redundancy system revision, you can use only the modules that are specified
in Table 1, Required Series and Firmware Revisions for Components Used in an
Enhanced Redundancy System, Revision 20.056_kit1.
Also, keep in mind the series and firmware revision requirements listed apply only to
components used in the redundant chassis pair, not to components used with
the redundancy system outside the redundant chassis pair.
Table 1 - Required Series and Firmware Revisions for Components Used in an Enhanced Redundancy System, Revision 20.056_kit1
Cat. No. Module Description Series Firmware Revision
1756-CN2 ControlLogix ControlNet bridge module B 20.020
1756-CN2R ControlLogix redundant media ControlNet bridge module
1756-CN2RXT ControlLogix-XT redundant media ControlNet bridge module
1756-CN2(1) ControlLogix ControlNet bridge module C 25.005
(1)
1756-CN2R ControlLogix redundant media ControlNet bridge module
(1)
1756-CN2RXT ControlLogix-XT redundant media ControlNet bridge module
(1)
1756-CN2RK ControlLogix redundant ControlNet bridge (conformal coated) module
1756-EN2T ControlLogix EtherNet/IP communication module D 10.007(2)(3)
C (or earlier) 5.008 or 5.028(4)(5)
1756-EN2TR ControlLogix EtherNet/IP communication module C 10.007(3)(6)
B (or earlier) 5.008 or 5.028(5)(7)
1756-EN2F ControlLogix EtherNet/IP fiber communication module C 10.009(8)
B (or earlier) 5.008 or 5.028(4)(5)
1756-EN2TXT ControlLogix-XT EtherNet/IP communication module D 10.007(2)(3)
C (or earlier) 5.008 or 5.028(4)(5)
Table 1 - Required Series and Firmware Revisions for Components Used in an Enhanced Redundancy System, Revision 20.056_kit1 (Continued)
Cat. No. Module Description Series Firmware Revision
1756-EN2TRXT ControlLogix-XT EtherNet/IP redundant communication module C 10.007(3)(6)
B 5.028(5)(7)
1756-EN2TRK ControlLogix EtherNet/IP conformal coated communication bridge module C 10.007(3)(6)
1756-EN2TK ControlLogix EtherNet/IP conformal coated communication bridge module D 10.007(2)(3)
1756-L61 ControlLogix 5561 controller Any 20.056
1756-L62 ControlLogix 5562 controller
1756-L63 ControlLogix 5563 controller
1756-L63XT ControlLogix-XT controller
1756-L64 ControlLogix 5564 controller
1756-L65 ControlLogix 5565 controller
1756-L71 ControlLogix 5571 controller
1756-L72 ControlLogix 5572 controller
1756-L73 ControlLogix 5573 controller
1756-L73XT ControlLogix-XT controller
1756-L74 ControlLogix 5574 controller
1756-L75 ControlLogix 5575 controller
1756-RM2 ControlLogix redundancy module Any 20.005
1756-RM2XT ControlLogix-XT redundancy module
1756-RM ControlLogix redundancy module Any 3.003
1756-RMXT ControlLogix-XT redundancy module
(1) IMPORTANT: The 1756-CN2/C, 1756-CN2R/C, 1756-CN2RXT/C, 1756-CN2RK/C modules do not support firmware revisions previous to revision 25.004. Do not attempt to
update the firmware to earlier revisions.
(2) IMPORTANT: The 1756-EN2T/D modules do not support firmware revisions previous to revision 10.006. Do not attempt to update the firmware to earlier revisions.
(3) Firmware revision 10.006 or later is digitally signed. For more information on digitally signed firmware, see page 5.
(4) IMPORTANT: The 1756-EN2T/C (or earlier) modules do not support firmware revision 10.006 or later. Do not attempt to update the firmware to revision 10.006 or later.
(5) Firmware revision 5.028 is digitally signed firmware. Firmware revision 5.008 is unsigned firmware. For more information on digitally signed firmware, see page 5.
(6) IMPORTANT: The 1756-EN2TR/C modules do not support firmware revisions previous to revision 10.007. Do not attempt to update the firmware to previous revisions.
(7) IMPORTANT: The 1756-EN2TR/B (or earlier) modules do not support firmware revision 10.007. Do not attempt to update the firmware to revision 10.007.
(8) IMPORTANT: The 1756-EN2F/C modules do not support firmware revisions previous to revision 10.009. Do not attempt to update the firmware to a previous version.
IMPORTANT When you install the digitally signed firmware, that is, firmware revision 5.028, into a
1756-EN2T/C (or earlier), 1756-EN2TR/B (or earlier), or 1756-EN2F/B (or earlier)
module, the installation makes the module incompatible with some firmware
revisions.
For example, after you upgrade firmware, the module supports use of only digitally
signed firmware. Any unsigned firmware updates are rejected by the module.
You can download firmware revision 5.028 and the enhanced redundancy system,
revision 20.056_kit1 firmware bundle at the Product Compatibility and
Download Center:
http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page
TIP Select the base catalog number in ControlFLASH software when upgrading extended
temperature or conformal coated modules.
For example, select the 1756-EN2TR when upgrading a 1756-EN2TRXT module.
Extended temperature and conformal coated modules use the same Redundancy
module ControlFLASH kit.
Compatible Software Versions Use these versions of software with this redundancy firmware bundle.
Table 2 - Required Software Versions for Enhanced Redundancy System, Revision 20.056_kit1
Software Required Software Version, Min
CompareTool 3.20.02
ControlFLASH 12.01.00
FactoryTalk Services Platform 2.50.00 (CPR 9, SR5)
FactoryTalk Activation 3.50.00 (CPR 9, SR5)
FactoryTalk Alarms and Events 2.40.00 (CPR 9, SR4)
FactoryTalk AssetCentre 4.00.00
FactoryTalk Batch 11.00.00(2)
FactoryTalk View Site Edition 6.10.00 (CPR 9, SR4)
Redundancy Module Configuration Tool 8.02.01
RSLinx Enterprise 5.50.04 (CPR 9, SR5)
RSLinx Classic 2.59.01 (CPR 9, SR5)
RSLogix5000(1) 20.01.00 (CPR 9, SR5)
20.03.00 (CPR9, SR5)
RSNetWorx for ControlNet 11.00.00 (CPR 9, SR5)
RSNetWorx for EtherNet/IP
(1) If you choose to use RSLogix 5000 software, version 20.03.00, we strongly recommend that you read Upgrade the RSLogix 5000
Software Version on page 29 before proceeding.
(2) Use the most recent FactoryTalk Batch Patch Roll-up with this enhanced redundancy firmware revision. For the most recent patch
roll-up, see Rockwell Automation Knowledgebase Answer ID 59058, accessible at:
http://www.rockwellautomation.com/knowledgebase/.
For system requirements, go to http://www.rockwellautomation.com/rockwellsoftware/design/rslogix5000/sysreq.html.
About the Redundancy Module You can use 1756-RM2, 1756-RM2XT, 1756-RM, or 1756-RMXT redundancy
modules to commission a redundant system. These modules operate in a
Configuration Tool plug-and-play manner, that is, they can commission a system without any
additional programming. However, there is more functionality available if you
use the modules with the Redundancy Module Configuration Tool (RMCT).
This enhanced redundancy system revision requires the RMCT, version 8.02.01
that is packaged with this enhanced redundancy system revision bundle. The
About screen for the RMCT displays 8.2.1.0 but its the correct version.
You can use the RMCT with the redundancy modules to complete these tasks:
IMPORTANT This publication documents Corrected Anomalies and Known Anomalies associated
with the RMCT. We recommend that you read these anomaly descriptions before using
the RMCT, version 8.02.01.
Also, if you need to upgrade your RMCT separately from downloading this enhanced
redundancy system revision or by using RSLinx Classic software, version 2.59.00, see
Upgrade the Redundancy Module Configuration Tool on page 47.
Table 3 - Enhancements Provided with Enhanced Redundancy System, Revision 20.055_kit4 (or earlier)
System Enhanced Enhancement
Components Redundancy
System Revision
1756-CN2/C support 20.055_kit5 The 1756-CN2, 1756-CN2R, 1756-CN2RXT, and 1756-CN2RK modules are available with firmware revision 25.005 in this enhanced
redundancy bundle.
1756-EN2F/C support The 1756-EN2F/C modules are available with firmware revision 10.009 in the enhanced redundancy bundle.
Table 3 - Enhancements Provided with Enhanced Redundancy System, Revision 20.055_kit4 (or earlier) (Continued)
System Enhanced Enhancement
Components Redundancy
System Revision
1756-CN2/C support 20.055_kit4 The 1756-CN2, 1756-CN2R, 1756-CN2RXT, 1756-CN2RK modules are available with firmware revision 25.004 in this enhanced
redundancy bundle.
1756-RM2 firmware Upgraded Firmware Revision
The 1756-RM2 and 1756-RM2XT modules use firmware revision 20.005 in this enhanced redundancy bundle.
Redundancy Module The RMCT has been revised to version 8.02.01.
Configuration Tool
ControlLogix 20.055_kit3 New Module Series and Firmware Revision
EtherNet/IP The 1756-EN2TR/C module, firmware revision 10.007, is available.
communication IMPORTANT: The 1756-EN2TR/C modules do not support firmware revisions previous to revision 10.007. Do not attempt to flash the
module, firmware to previous revisions.
1756-EN2TR/C
Product Resiliency Improvement
This release includes enhancements that are intended to improve product resiliency to potentially disruptive activities. These
enhancements have been verified not to affect product safety, performance, expected life, configuration, or operation of the product.
Rockwell Automation advises customers to follow good Industrial Control System (ICS) security practices that include regular product
updates. To help ensure authenticity, obtain product updates and new releases directly from Rockwell Automation.
With the 1756-EN2TR/C module, firmware revision 10.007, message performance is improved over earlier revisions.
ControlLogix Upgraded Firmware Revision
EtherNet/IP The 1756-EN2T/D module uses firmware revision 10.007 in this enhanced redundancy bundle.
communication
module,
1756-EN2T/D
ControlLogix 20.055_kit2 The 1756-EN2T/D module, firmware revision 10.006, is available.
EtherNet/IP IMPORTANT: The 1756-EN2T/D modules do not support firmware revisions previous to revision 10.006. Do not attempt to update the
communication firmware to previous revisions.
module,
1756-EN2T/D With the 1756-EN2T/D module, firmware revision 10.006, message performance is improved over earlier revisions.
Product Resiliency Improvement
This release includes enhancements that are intended to improve product resiliency to potentially disruptive activities. These
enhancements have been verified not to affect product safety, performance, expected life, configuration, or operation of the product.
Rockwell Automation advises customers to follow good Industrial Control System (ICS) security practices that include regular product
updates. To help ensure authenticity, obtain product updates and new releases directly from Rockwell Automation.
RSLogix 5000 Option to use RSLogix 5000 software, version 20.03.00
Software
RSLogix 5000 software, version 20.03.00 includes enhancements that are intended to improve product resiliency to potentially
disruptive activities. These enhancements have been verified not to affect product safety, performance, expected life, configuration,
or operation of the product.
IMPORTANT: For information on upgrading your RSLogix 5000 software project to version 20.03.00, see Rockwell Automation
Knowledgebase Answer ID 565204 - RSLogix 5000 Software, Version 20.03, accessible at:
http://www.rockwellautomation.com/knowledgebase/. (log on is required.)
We strongly recommend that you read the Knowledgebase article, and the associated documents that are referenced within it, before
upgrading your RSLogix 5000 software version.
Table 3 - Enhancements Provided with Enhanced Redundancy System, Revision 20.055_kit4 (or earlier) (Continued)
System Enhanced Enhancement
Components Redundancy
System Revision
Redundancy Module 20.054_kit1 Reduction in scan time of up to 35% per sync point in comparison to the 1756-RM/B module, due to higher 1756-RM2 module speed
Configuration Tool of up to 1000 Mbps.
(RMCT),
1756-RM2 Redundant fiber ports for the 1756-RM2 module for crossloading; no single point of failure of a fiber cable.
The redundancy module firmware now reports back to the RMCT about the version of the RMCT it is compatible with. If there is an
incompatibility, the RMCT shows only the Module Info tab that indicates the version that the firmware is compatible with.
A synchronization process that takes a long time (up to 10 minutes, in the case of a PTP configuration error) to complete can be
aborted via the Disqualify button in the RMCT. Without this feature, you must abort qualification by taking a manual action, for
example, when you cycle power to the secondary chassis or when you remove the redundancy module under power (RIUP).
There are new causes added for partner compatibility of communication modules that appear in the RMCT Status tab under
Compatibility.
For example, the primary and secondary partners are not on the same network (the partners must be communicating on the same
network to synchronize), or one or both of the partners keepers are invalid. Update the keepers to valid and matching keeper values.
1756-L61 20.054 The 375 ms RPI limit has been increased. You can now configure I/O modules to use up to a 750 ms RPI; the same as in a simplex
1756-L62 system.
1756-L63 Beginning with revision 20.054, HMI blind time due to switchover has been reduced.
1756-L63XT See page HMI Blind Time on page 28.
1756-L64
1756-L65
1756-L71
1756-L72
1756-L73
1756-L73XT
1756-L74
1756-L75
1756-L71 Support added for the 1756-L71 controller for redundancy Logix and Redundancy Module Configuration Tool (RMCT).
1756-EN2F Support added for the 1756-EN2F in the Redundancy Module Configuration Tool (RMCT).
1756-EN2T Sockets are supported in the 1756-EN2T and 1756-EN2TR modules.
1756-EN2TR
Security To enhance system and device-level security in systems that use our products, Rockwell Automation prescribes validated,
defense-in-depth measures and design practices to enhance system and device-level security. For the latest information on security
solutions and enhancements, visit http://www.rockwellautomation.com/solutions/security.
Redundancy Module The redundancy module firmware now reports back to the RMCT about the version of the RMCT that it is compatible with. If an
Configuration Tool incompatibility exists, the RMCT shows the Module Info tab that indicates the version that the firmware is compatible with.
(RMCT),
1756-RM An ongoing synchronization process that takes a long time (up to 10 minutes, in the case of a PTP configuration error) to complete can
be aborted via the Disqualify button in the RMCT. Without this feature, you must abort qualification by taking a manual action, such as
when you cycle power to the secondary chassis, or when you remove the redundancy module under power (RIUP).
There are new causes added for partner compatibility of communication modules that appear in the RMCT Status tab under
Compatibility.
For example, the primary and secondary partners are not on the same network (the partners must be communicating on the same
network to synchronize), or one or both of the partners keepers are invalid. Update the keepers to valid and matching keeper values.
Corrected Anomalies The following sections describe anomalies that are corrected in enhanced
redundancy system revisions.
Table 5 - Corrected Anomalies in Enhanced Redundancy System, Revision 20.055_kit5 (or earlier)
Cat. No./System Enhanced Description
Component Redundancy
System Revision
1756-CN2/C 20.055_kit5 CORRECTED: When the second power supply of a redundant power supply pair powers up, ControlNet interface modules that reside in
1756-CN2R/C the same chassis experience an overvoltage condition. The 5V power rail on the interface module briefly exceeds the maximum
1756-CN2RXT/C voltage setting in the Voltage Monitoring System (VMS).
Lgx00158735
1756-CN2RK
CORRECTED: The Redundancy System Update feature takes several minutes to report that a secondary module with an earlier
firmware revision is paired with a primary module that has more recent firmware.
Lgx00155142
1756-L61 20.055_kit1 CORRECTED: When using PowerFlex 750 drives with firmware that supports Drives ADC (Automatic Drive Configuration) on
1756-L62 powerup, the controller can become stuck in the transition to Run mode. When stuck in the transition to Run mode, the application is
1756-L63 not executing and the outputs are not being updated. For more information, see Knowledgebase document 493802. Also refer to
Product Notice 2012-10-004.
1756-L63XT Lgx00140810, Lgx0130112
1756-L64
1756-L65
1756-L71
1756-L72
1756-L73
1756-L73XT
1756-L74
1756-L75
1756-L61 20.054 CORRECTED: During online editing, an anomaly can occur when testing edits to an SFC routine. Normally, test edits are applied to a
1756-L62 test SFC routine and verified before accepting them in the program's logic.
1756-L63 When this anomaly occurs, test edits are implemented in the online routine. Despite trying to cancel the online editing operation,
1756-L63XT when the cancelation option appears to cancel the program edits, the edits are, instead, accepted.
1756-L64 There are no workarounds for this anomaly.
1756-L65 Lgx00119071
1756-L71
1756-L72
1756-L73
1756-L73XT
1756-L74
1756-L75
Table 5 - Corrected Anomalies in Enhanced Redundancy System, Revision 20.055_kit5 (or earlier) (Continued)
Cat. No./System Enhanced Description
Component Redundancy
System Revision
1756-L61 20.054 CORRECTED: An anomaly can occur when you nest simultaneous branches in a sequential function chart (SFC) routine as shown
1756-L62 below.
1756-L63
1756-L63XT
1756-L64
1756-L65
1756-L71
1756-L72
1756-L73
1756-L73XT
1756-L74
1756-L75
Bottom-most Steps
During normal operations, the logic does not step out of a simultaneous branch until all of the incoming legs have reached their
bottom-most step. In the example shown, the logic does not step out of the Outer simultaneous branch until the left-most leg has
stepped out of the Inner simultaneous branch.
The first time through the SFC routine, the application works as expected. On subsequent scans, however, the chart steps out of the
Outer simultaneous branch even though the left leg has not reached the Inner simultaneous branch yet.
This behavior occurs because the information in the bottom step, that is, the step next to the word Outer, remains from the previous
scan. This stale information incorrectly causes the transition to move on as if the left leg is at the bottom step when it actually is not.
To work around this anomaly, confirm all of the incoming legs have reached their bottom steps in the transition. You can check the .x
bits to make sure the bottom-most step of each converging leg is active before allowing the chart to advance. This check can be added
to the transition logic already present.
For example, the steps in the following expression are the bottom steps (see graphic above) of the incoming legs. Each step has a
timer. The transition does not move on until all of the step timers have reached their preset value.
The expression can be modified to be sure those steps are truly active. This is the original expression:
// Unit is ready to Transition
Step1_ready.dn and Step2_ready.dn and Step3_ready.dn and Step4_ready.dn and Step5_ready.dn
This is the modified expression to workaround this anomaly.
// Unit is ready to Transition
Step1_ready.x and Step2_ready.x and Step3_ready.x and Step4_ready.x and Step5_ready.x and Step1_ready.dn and
Step2_ready.dn and Step3_ready.dn and Step4_ready.dn and Step5_ready.dn
IMPORTANT: The x bit is cleared when the chart transitions out of a step.
Adding this check to the condition forces the engine to wait until all of those steps are genuinely active before advancing out of the
simultaneous branch.
Lgx00118189, Lgx00116506
Table 5 - Corrected Anomalies in Enhanced Redundancy System, Revision 20.055_kit5 (or earlier) (Continued)
Cat. No./System Enhanced Description
Component Redundancy
System Revision
1756-L61 20.054 CORRECTED: Deleting a small rung, such as a rung with just an XIC and OTE, or a rung with a single instruction, such as NOP or RES,
1756-L62 could cause a controller to experience a Major nonrecoverable fault.
1756-L63 Lgx00124861
1756-L63XT
1756-L64 CORRECTED: When an alarm instruction is being modified online while it is executing, it can cause the redundancy system to
1756-L65 disqualify. The system recovers automatically at a later time.
1756-L71 Lgx00117401
1756-L72
1756-L73 CORRECTED: In some systems with a single periodic task, forced output drops upon redundancy switchover.
1756-L73XT Lgx00124234
1756-L74
1756-L75 CORRECTED: In some systems where the first scan bit (S:FS) is being analyzed, the first system scans the first scan bit again on the first
scan after a switchover.
Lgx00126870
1756-CN2, 1756-CN2R, CORRECTED: After a switchover is completed, the primary redundancy module incorrectly reports a Synchronized status in RSLogix
1756-CN2RXT, 5000 software, and primary ControlNet and Ethernet/IP communication modules report a No Partner status
1756-EN2T, After a successful switchover, these components in the enhanced redundancy system give these indications:
1756-EN2TR,
1756-EN2TXT, Primary communication module is PwNS
1756-RM, 1756-RMXT Secondary communication module is DSNP
Synchronization Status tab in the RMCT shows Synchronized
These indications on the communication module and Synchronization Status tab incorrectly indicate that a switchover is complete but
a redundancy state change is pending.
Typically, the components give these indications when the switchover is, in fact, complete and no state change is pending:
Primary communication module is PwDS
Secondary communication module is CMPT
Synchronization Status tab in the RMCT shows Disqualified
To force the completion of the pending state change and re-synchronize the redundant chassis pair, cycle power to the secondary
chassis.
Lgx00115764
RPI CORRECTED: In all prior releases for ControlLogix Redundancy, the RPI to an I/O module could not be set greater than 376 ms. This has
been enhanced to allow any RPI acceptable for the module being configured.
Lgx00105642
RSLinx software CORRECTED: The following RSLinx software corrections have been made:
Upgrading RSLinx software to version 2.59.00 or later, no longer stops the operation of the RMCT. If the RSLinx software version
that you are upgrading to includes an older version of the RMCT than what is already installed, then the already-installed RMCT
version is not affected. Alternatively, if the upgraded RSLinx version included a newer version of the RMCT, then the new RMCT
version installs automatically on top of the already-installed RMCT version.
The RMCT can be successfully installed without seeing any error messages after the uninstallation of RSLinx software, version
2.57.00 or later.
With RSLinx software, version 2.57.00 or later, RSLinx software can be downgraded to an older version without any errors. For
example, if you have the RMCT, version 7.02.07 installed while using RSLinx software, version 2.59.00, then you can uninstall
RSLinx version 2.59.00 and successfully install RSLinx software, version 2.57.00. The RMCT, version 7.02.07, is not overwritten with
the older version of the RMCT that is included in RSLinx software, version 2.57.00. To downgrade the RMCT version as well,
manually uninstall and reinstall the desired RMCT version by using ADD/Remove Programs in the Control Panel.
Lgx00086040
1756-RM, 1756-RMXT CORRECTED: Repeated connection and disconnection, or irregular insertion, of the 1756-RM or 1756-RMXT redundancy modules
fiber-optic cable results in various fault codes indicated on the module status display.
If the 1756-RM or 1756-RMXT redundancy modules fiber-optic cable is disconnected and connected repeatedly within short periods
of time, or the cable is inserted slowly at a slight angle to the connector, the redundancy module faults and indicates error codes such
as E0xx or EAxx.
To avoid experiencing these faults, wait 510 seconds between disconnecting and connecting the 1756-RM or 1756-RMXT
redundancy modules fiber-optic cable and verify that the insertion is quick and straight into the connector.
Lgx00084595, Lgx00113995, Lgx00113954, Lgx00116055
Known Anomalies This table lists the known anomalies applicable to the enhanced redundancy
system, revision 20.056_kit1 (or earlier).
Table 6 - Known Anomalies in Enhanced Redundancy System, Revision 20.056_kit1 (or earlier)
Cat. No. Description
1756-EN2T, 1756-EN2TR, 1756-EN2TXT You cannot have kits with firmware revisions 10.006 and 10.007 installed on the same computer. If you have firmware revision 10.006
installed and you attempt to install firmware revision10.007, 10.007 generates an error directing to an incorrect .nvs file. Reinstall the
desired firmware revision and ignore the error. We recommend using Firmware revision 10.007 because it has corrected anomalies from
firmware revision 10.006.
Lgx00155450
1756-CN2, 1756-CN2R, 1756-CN2RXT, Multiple switchovers can cause connection failure to SoftLogix controllers.
1756-EN2T, 1756-EN2TR, 1756-EN2TXT, When a high number of consumed connections are routed through a ControlNet communication module in the primary chassis to a
1756-EN2F, 1756-RM, 1756-RMXT, SoftLogix controller, the primary controller reports a connection failure, that is, error code 16#0203.
1756-L61, 1756-L62, 1756-L63, This anomaly occurs despite the fact that there are no network disruptions or device power cycling.
1756-L63XT, 1756-L64, 1756-L65, Lgx00115516
1756-L71, 1756-L72, 1756-L73,
1756-L73XT, 1756-L74, 1756-L75
1756-EN2T, 1756-EN2TR, 1756-EN2TXT, Connections can drop temporarily if a 1756-EN2Tx communication module is not configured correctly.
1756-EN2F, 1756-L61, 1756-L62. If your application includes a connection from a remote controller to a primary controller over an EtherNet/IP network, you must use
1756-L63, 1756-L63XT, 1756-L64, these configuration settings for the 1756-EN2Tx communication module in the primary chassis when it is added to the remote
1756-L65, 1756-L71, 1756-L72, 1756-L73, controllers RSLogix 5000 project:
1756-L73XT, 1756-L74, Rack Connection = None
1756-L75
Time Sync Connection = None
If the parameters are configured in any other combination, the connection between the remote controller and primary controller is
temporarily dropped during a switchover. The connection is re-established after the switchover is complete.
IMPORTANT When you add the 1756-EN2Tx communication module to the primary controllers RSLogix 5000 project, you
can use any settings for the parameters above with no effect on the connection from remote controller to
primary controller.
Table 6 - Known Anomalies in Enhanced Redundancy System, Revision 20.056_kit1 (or earlier) (Continued)
Cat. No. Description
1756-L61, 1756-L62, 1756-L63, Alarm parameters can be lost when a switchover occurs.
1756-L63XT, 1756-L64, 1756-L65, When a switchover occurs in a redundant system that uses alarms, certain alarm parameters can not be transferred to the new primary
1756-L71, 1756-L72, 1756-L73, controller if the parameters have changed since the last crossload of data. Alarm parameters that can not transfer include the following:
1756-L73XT, 1756-L74, 1756-L75
DeliveryER
DeliveryEN
NoSubscriber
NoConnection
CommError
AlarmBuffered
SubscNotified
Once the alarm data is buffered, the parameters are updated.
Lgx00093529
Alarms can fail to be acknowledged when the attempt to acknowledge them occurs during a switchover.
If you attempt to acknowledge an alarm while a switchover occurs, a failure to acknowledge the alarm is indicated. Attempting to
acknowledge the alarm a second time is successful.
Lgx00093826
A Partial Import Online to a primary controller over a ControlNet network can fail if a system switchover occurs while the PIO is still in
process.
When the anomaly occurs and the PIO fails, you can see any of these errors:
Table 6 - Known Anomalies in Enhanced Redundancy System, Revision 20.056_kit1 (or earlier) (Continued)
Cat. No. Description
1756-L71, 1756-L72, 1756-L73, 1756-L7x controllers display No Project message during qualification process.
1756-L73XT, 1756-L74, 1756-L75 While qualification is in process in a system that uses 1756-L7x controllers, controllers in the secondary chassis display No Project in
their Scrolling Status Display status indicator. When qualification is complete, the secondary controllers display the name of the project
loaded into the primary controller.
Lgx00115228
ControlNet network If connecting a redundant controller over ControlNet by using the Controller Log feature, and a switchover occurs, the controller log
entries no longer shows the users name. After the switchover, the user name indicates unknown.
Lgx00125445
Restrictions This table lists the restrictions applicable to the enhanced redundancy system,
revision 20.056_kit1 (or earlier)
Table 7 - Restrictions in Enhanced Redundancy System, Revision 20.056_kit1 (or earlier) (Continued)
System Component Description
1756-L61, 1756-L62, 1756-L63, A redundant controller project cannot contain consumed Unicast connections. The project can contain produced Unicast tags consumed by
1756-L63XT, 1756-L64, 1756-L65, remote consumers.
1756-L71, 1756-L72, 1756-L73,
1756-L73XT,
1756-L74, 1756-L75
1756-EN2T, 1756-EN2TR, 1756-EN2TXT
1756-EN2F
1756-EN2T, 1756-EN2TR, 1756-EN2TXT, There are differences between CIP Sync technology in nonredundant systems and enhanced redundancy systems, revision 20.054.
1756-EN2F,
1756-L61, 1756-L62, 1756-L63,
1756-L63XT, 1756-L64, 1756-L65, IMPORTANT Before you use this enhancement in an enhanced redundancy system, see these publications for a full
1756-L71, 1756-L72, 1756-L73, understanding of CIP Sync technology in any system:
1756-L73XT, 1756-L74,1756-L75
ControlLogix System User Manual, publication 1756-UM001
ControlLogix Controllers, Revision 18 Release Notes, publication 1756-RN018
Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003
Consider the following when you use CIP Sync technology in an enhanced redundancy system, revision 20.054:
If you enable CIP Sync Time Synchronization in the controllers in a redundant chassis pair, you must also enable Time Synchronization
in the EtherNet/IP communication modules in the redundant chassis pair so all devices have a single path to the Grandmaster.
If time synchronization is enabled in any controller in the primary chassis of a disqualified Redundant Chassis Pair, and no other
devices, that is, EtherNet/IP communication modules, in the primary chassis have time synchronization enabled, the redundant chassis
pair attempts to qualify. However, in these application conditions, the attempt to qualify fails.
While CIP Sync technology can handle multiple paths between master and slave clocks, it resolves mastership most effectively if you
configure the redundant paths so that Time Synchronization is enabled in only the minimum required number of EtherNet/IP
communication modules.
For example, if your redundant chassis pair has three 1756-EN2T communication modules and all are connected to the same network,
enable Time Synchronization in only one of the modules.
If the primary controller is the Grandmaster, the enhanced redundancy system automatically manages the CIP Sync clock attributes so
that the controller in the primary chassis is always set to be the Grandmaster instead of the secondary controller. This clock
management ensures a change to a new Grandmaster when the redundancy system switches over.
When a switchover occurs, these events take place:
The Grandmaster status transfers from the original primary controller to the new primary controller. This transfer can take longer to
complete than if Grandmaster status was transferred between devices in a nonredundant system.
The synchronization of the enhanced redundancy system can take longer to complete than when it occurs on a switchover in an
enhanced redundancy system, revision 20.054, that does not use CIP Sync technology.
If you attempt to use the Redundant System Update (RSU) feature to upgrade an enhanced redundancy system, revision 16.081 or
earlier, that uses Coordinated System Time (CST), the enhanced redundancy system, revision 20.054 does not permit a locked
switchover and the upgrade fails to complete.
To work around this restriction, first disable CST Mastership in the original redundancy system and then use RSU to upgrade to
enhanced redundancy system, revision 20.054.
Table 7 - Restrictions in Enhanced Redundancy System, Revision 20.056_kit1 (or earlier) (Continued)
System Component Description
1756-L61, 1756-L62, 1756-L63, You can place a maximum of two controllers in the same chassis in a redundant chassis pair. When two controllers are used in the same
1756-L63XT, 1756-L64, 1756-L65, chassis, they must be of the same product family. For example, you cannot place a 1756-L6x controller with a 1756-L7x controller in the
1756-L71, 1756-L72, 1756-L73, same chassis.
1756-L73XT, 1756-L74, 1756-L75
Do not use Match Project to Controller property with redundant controllers.
If you use the Match Project to Controller property available in the Advanced tab of the Controller Properties dialog box, you cannot go
online with, download to, or upload from the new primary controller after a switchover. This is because the serial number of the new
primary controller is not the same as the serial number of the old primary controller and the project cannot be matched to the
newly-switched-to controller.
Firmware Supervisor
You cannot use the Firmware Supervisor feature available in RSLogix 5000 software.
Event Tasks
You cannot use event tasks in a ControlLogix enhanced redundancy systems. When you enable redundancy, you must change event tasks
to nonevent tasks or delete them from your project.
SERCOS Motion or Integrated Motion on the EtherNet/IP Network
You cannot use Motion in ControlLogix enhanced redundancy systems. A remote controller can contain motion instructions even if it is on
the same network as a redundancy system.
Under some error conditions, the 1756-RM module continually attempts to requalify the system while the error prevents it from being
successful. This causes the redundancy module error log to fill with the same error condition. If the system is in this condition, the
redundancy module display cycles between QFNG and DISQ. To stop this from happening, change the redundancy module synchronization
trigger in the Redundancy Module Configuration Tool (RMCT) to Never, until the error condition is corrected.
1756-L61, 1756-L62, 1756-L63, Update controller firmware from boot firmware can cause major nonrecoverable fault.
1756-L63XT, 1756-L64 We recommend that you upgrade controller firmware in a nonredundant chassis. When you update these controllers from the boot
firmware revisions listed to higher firmware revisions, execute the update with the controller in a nonredundant chassis or primary
chassis.
If you attempt the firmware update with the controller in a redundant chassis, a major nonrecoverable fault (MNRF) can occur. If the fault
does occur, the controller remains in a faulted state until you attempt the firmware update again with the controller in a nonredundant
chassis.
The label on the side of the controller indicates the series controller and the boot firmware revision.
After you have updated the controller beyond the boot firmware revision, you can perform any additional controller updates in either
nonredundant or redundant chassis.
Table 7 - Restrictions in Enhanced Redundancy System, Revision 20.056_kit1 (or earlier) (Continued)
System Component Description
1756-CN2, 1756-CN2R, 1756-CN2RXT, System Event Entry contains a module failure event when an enhanced communication module is inserted.
1756-EN2T, 1756-EN2TR, 1756-EN2TXT The System Event History displays a `Module Failure entry when you insert a 1756-CN2x communication module or a 1756-EN2x
1756-EN2F communication module in the chassis while the redundant chassis pair is synchronized. This is not indicative of any module failure;
instead, it indicates that only an enhanced communication module was inserted in the chassis.
1756-RM Under rare conditions, inserting a redundancy module into a running system can cause the redundancy system to switchover or disqualify,
1756-RMXT and cause the other modules in that chassis to reset themselves.
Inserting the module at an angle causes the anomaly. Make sure the module is inserted straight into the chassis without any side-to-side
or top-to-bottom movement.
Application Notes Consider these application notes when configuring, programming, and using
your ControlLogix enhanced redundancy system revision 20.056_kit1.
TIP You may need to click on the `> symbol next to the `Custom Download Files to
expand the AOP list.
Note: The version listed in the tables is the version of the AOP, not the version of the
supported firmware.
You use the RSLogix 5000 Module Profiles Setup Wizard to install the AOP.
IMPORTANT AOPs are not available for the 1756-CN2/C, 1756-CN2R/C, 1756-CN2RXT/C, and
1756-CN2RK/C communication modules.
If your RSLogix 5000 software version does not allow you to configure a
device to exactly match the physical device, you must download and install
the devices AOP.
The existing 1756-EN2T/D module specification sheets do not list the modules
as being SIL2 certified. Policies currently in place by TV require that only the
1756-EN2T/C or the 1756-EN2TR modules be used for SIL2 applications as
part of the safety loop.
You can use a mix of 1756-RM module series or 1756-RMXT module series in
enhanced redundancy system, revision 20.054 (or later). You can also mix series
of RM redundancy modules within a partnered set. For example, you can use a
1756-RM module in the primary chassis and a 1756-RM/B module in the
secondary chassis.
TIP Your enhanced redundancy system experiences the best scan performance if it uses
1756-L7x controllers with 1756-RM2 modules in the RCP.
For more information, see the ControlLogix Enhanced Redundancy System User
Manual, publication 1756-UM535.
IMPORTANT The minimum firmware revisions listed above apply only to EtherNet/IP
communication modules in the remote chassis.
In a redundant chassis pair, you can use only the ControlLogix modules listed in Table 1.
The maximum_scan_time is the maximum scan time for the entire task when the
secondary controller is synchronized.
IMPORTANT This works only when there is no Continuous task configured in the Logix application.
1. Monitor the Max Scan Time for each task while the redundant chassis pair
is synchronized.
2. Set the Watchdog times for each task to 3 times the Max Scan Time.
3. Use the Logix5000 Task Monitor Tool to configure each Task Period. (1)
Adjust the Task periods of each so that the maximum scan time is less than
80% of the task period rate.
(1) See the PlantPAx Automation System Reference Manual, publication PROCES-RM001.
Adjust the Task periods so that the Logix CPU% utilization is never
above 75%.
While performing these tests, the HMI and any other external systems
must be connected to the Logix controller.
If your secondary chassis becomes disqualified, or you manually disqualify it, take
these actions before you try to synchronize the chassis:
Wait at least 15 seconds after the redundant chassis are disqualified before
you try to synchronize them.
Failure to install the new EDS files available in enhanced redundancy system,
revisions 20.054_kit1 (or later), firmware bundles prevents the use of RMCT,
version 8.02.01.
If you use the EDS files available with enhanced redundancy system, revision
16.081 in an enhanced redundancy system, firmware revision 20.054,
1756-RM2/B modules and 1756-RM2XT/B modules, appears as series A
modules in the Device Type column of an RSWho browse screen.
In this case, use the information in the Online Name column to identify your
redundancy modules series level. The information in the Online Name column is
accurate.
We recommend that you use the EDS file for redundancy modules that is
included with the enhanced redundancy system, revision 20.054_kit1 firmware
bundle. With the new EDS file, the RSWho software Device Type column shows
a generic 1756-RM device type, as shown in this graphic.
IMPORTANT The Batch Server detects the lost connection and repeatedly attempts to re-establish
the connection until successful. However, while the connection is lost, the Batch Server
puts the recipes, or entire batch, in the held state.
After the connection between the Batch Server and the redundant chassis pair is
re-established, you can clear the communication failure and restart the recipes. The
Batch Server keeps the recipes in the held state until the failure is cleared and recipes
restarted.
If any alarms are generated while the connection is lost, that data is
buffered. When the connection is re-established, you must acknowledge
the connection loss.
If your application requires that the connections described above are maintained
during a switchover, we recommend that the connection bridge between the
component and a redundant chassis pair with an EtherNet/IP network to
ControlNet network path.or exclusive ControlNet connection.
After a switchover, the time between the communication (updating active data)
interruption and the restoration (resumes updates) is often referred to as HMI
Blind Time.
Beginning with revision 20.054, HMI blind time due to switchover has been
reduced.
IMPORTANT RSLinx Enterprise software version 5.50.04 is required beginning with version 20.054.
Upgrade the RSLogix 5000 This section describes how to upgrade your RSLogix 5000 software and,
subsequently, the software project, when the following system conditions exist:
Software Version
IMPORTANT Before you upgrade your RSLogix 5000 software version, consider the following:
We strongly recommend that you read Rockwell Automation Knowledgebase
Answer ID 565204 - RSLogix 5000 Software, Version 20.03, accessible at:
http://www.rockwellautomation.com/knowledgebase/.
A login is required to access the article.
Upgrading the RSLogix 5000 software to version 20.03.00 is optional.
If desired, you can continue to use RSLogix 5000 software version 20.01.00.
You cannot install RSLogix 5000 software, revision 20.01.00 and revision
20.03.00, on the same computer simultaneously.
Your system is using RSLogix 5000 software and project, version 20.01.00.
You can take the project offline, that is, the system is not required to
continue to run during the software upgrade.
If your system must continue to run during the software upgrade, you must
use the Redundancy System Update option. This option is described on
page 45.
Complete the following steps to upgrade the RSLogix 5000 software version and
project in your enhanced redundancy system.
IMPORTANT There are multiple methods available to upgrade the RSLogix 5000 software version in
your enhanced redundancy system. The specific tasks required vary by system
configuration and requirements.
This section describes one of the methods available.
For more information on upgrading your RSLogix 5000 software version, see Rockwell
Automation Knowledgebase Answer ID 565204 referenced above.
Replace a Module in the These steps only apply when the primary chassis is at revision 20.056_kit1. These
steps are used when performing a direct communication module replacement, for
Secondary Chassis that has the example, when replacing a communication module in the secondary chassis with
Same Catalog Number and a module that has the same:
Firmware Revision Catalog number
Series
Firmware (after updating the firmware, if necessary)
When you replace communication modules, make sure that the node address (for
ControlNet modules), rotary switches, and Port Configuration (for Ethernet
modules) match the existing modules.
If you want to replace the Ethernet communication module with the same catalog
number and same firmware revision in the secondary chassis then see Replace a
Module in the Secondary Chassis that has the Same Catalog Number and
Firmware Revision on page 31.
IMPORTANT The following section describes the requirements and tasks used to replace 1756-EN2T
modules with 1756-EN2T/D modules.
The same requirements and tasks apply when you replace 1756-EN2TR modules with
1756-EN2TR/C modules and when you replace 1756-EN2F/B (or earlier) modules with
1756-EN2F/C modules with the only differences being between specific catalog
numbers and series levels.
For example, before replacing 1756-EN2T modules, make sure you have installed the
correct firmware on all 1756-EN2T/D modules.
The same task applies when you replace 1756-EN2TR modules. That is, before you
replace 1756-EN2TR modules, make sure you have installed the correct firmware on all
1756-EN2TR/C modules.
You can replace the 1756-EN2T modules with 1756-EN2T/D by using the
following methods:
Synchronization and Switchover for the 1756-EN2T Modules - Use this
method if the following conditions exist:
The module being replaced is a 1756-EN2T module in a system
revision 20.055_kit1, 20.055_kit2, 20.055_kit3, 20.055_kit4,
20.055_kit5, or 20.056_kit1 and Electronic Keying is not set to Exact
match.
For more information on this method, see page 33.
For more information on this method, see Upgrade the Firmware by Using
Redundancy System Update on page 45
1. Make sure the existing module and replacement module use the same IP,
Network Mask, and Gateway addresses.
2. If the Redundancy Module Configuration Tool (RMCT) is not at version
8.02.01, update to version 8.02.01.
3. If you are using a 1756-RM2, upgrade the firmware to 20.005.
5. For each module, verify that the Electronic Keying is set to Compatible
Module or Disable Keying.
6. In the RSLinx Classic software, start the RMCT for the 1756-RM module
in the primary chassis.
8. Click Apply.
19. Disconnect the Ethernet cables from the secondary Ethernet module.
20. Turn off power to the secondary chassis.
21. Remove the 1756-EN2T module from the secondary chassis.
22. Set the 1756-EN2T/D module switches to 888 and insert it in the
secondary chassis and turn on power to the secondary chassis.
a. After the reset is complete, turn power off to the secondary chassis,
remove the module from the secondary chassis.
b. Set the switches to the same settings as on the EN2T that was removed.
c. Reinsert the module into the secondary chassis, reattach the cable and
turn on power to the secondary chassis.
d. Bridging across the backplane (or via the Ethernet modules USB port),
configure the secondary Ethernet modules Port Configuration to
match the Ethernet modules Port Configuration from step 10 on
page 35.
e. If you have not already updated the firmware of the 1756-EN2T/D,
Update the module to firmware revision 10.007
23. Repeat the steps 19 25 for all ethernet modules in secondary chassis.
Replace 1756-CN2 Modules This section describes how to replace ControlLogix ControlNet communication
modules in a ControlLogix enhanced redundancy system. You can replace
ControlNet communication modules 1756-CN2/B, 1756-CN2R/B, and
1756-CN2RXT/B modules with 1756-CN2/C, 1756-CN2R/C,
1756-CN2RXT/C, or 1 756-CN2RK/C, modules.
IMPORTANT The following section describes the requirements and tasks used to replace 1756-CN2
modules with 1756-CN2/C modules.
The same requirements and tasks apply when you replace 1756-CN2R modules with
1756-CN2R/C modules with the only differences being between specific catalog
numbers and series levels.
For example, before replacing 1756-CN2/B modules, make sure you have installed the
correct firmware on all 1756-CN2/C modules.
If you need to replace the ControlNet module with the same catalog number and
same firmware revision in the secondary chassis, see Replace a Module in the
Secondary Chassis that has the Same Catalog Number and Firmware Revision on
page 31.
You can replace the 1756-CN2/B modules with 1756-CN2/C by using the
following methods:
Synchronization and Switchover for the 1756-CN2/B Modules - Use this
method if the following two conditions are met:
the module being replaced is a 1756-CN2/B module that is in a system
at revision 20.055_kit1, 20.055_kit2, 20.055_kit3, 20.055_kit4,
20.055_kit5, or 20.056_kit1.
if electronic keying is set to disable or compatible module
For more information on this method, see page 39.
IMPORTANT When you upgrade 1756-CN2/B modules to 1756-CN2/C modules, you must do so in
pairs. If not, the system cannot synchronize after a switchover.
Replace 1756-CN2/B with 1756-CN2/C, and 1756-CN2RXT/B with 1756-CN2RXT/C
modules.
1. Add the EDS files for the Revision 25 1756-CN2/C modules, if you have
not already done so.
2. Make sure the existing module and replacement module use the same
ControlNet node address.
3. If the Redundancy Module Configuration Tool (RMCT) is not at version
8.02.01, update to version 8.02.01.
4. If you are using a 1756-RM2, upgrade the firmware to 20.005.
5. Using RSLogix 5000 software, go online with the primary controller.
6. For each 1756-CN2/B module, verify that Electronic Keying is set to
Compatible Module or Disable Keying.
7. In the RSLinx Classic software, start the RMCT for the 1756-RM or
1756-RM2 module in the primary chassis.
15. If you have not already updated the firmware of the 1756-CN2/C
modules, use the ControlFLASH update tool to update the firmware of
each 1756-CN2/C module in secondary chassis.
16. Verify that the Synchronization Status tab indicates the modules are fully
compatible.
19. Turn off the power to secondary chassis and then remove the
1756-CN2/B modules from the secondary chassis.
20. Make sure to match the node address of replacing the ControlNet module
with existing module.
21. Insert each 1756-CN2/C module into the secondary chassis, reconnect
the module to the network, and turn on power to the chassis.
22. If you have not already updated the firmware of the 1756-CN2/C,
modules, use ControlFLASH to update the firmware of each
1756-CN2/C module in secondary chassis.
Upgrade the RSLogix 5000 This section describes how to upgrade your RSLogix 5000 software and,
subsequently, the software project, and also replace ControlLogix EtherNet/IP or
Software Version and Replace ControlNet communication modules in your enhanced redundancy system.
1756-EN2T, 1756-EN2TR or when the following system conditions exist:
1756-CN2
You are using enhanced redundancy system, revision 20.055_kit5 or
20.056_kit1.
Your system is using RSLogix 5000 software and project, version 20.01.00.
IMPORTANT Before you upgrade the RSLogix 5000 software version on your computer,
consider the following:
We strongly recommend that you read Rockwell Automation
Knowledgebase Answer ID 565204 - RSLogix 5000 Software, Version
20.03, accessible at:
http://www.rockwellautomation.com/knowledgebase/.
A login is required to access the article.
Upgrading the RSLogix 5000 software to version 20.03.00 is optional.
If desired, you can continue to use RSLogix 5000 software version
20.01.00.
You cannot install RSLogix 5000 software, revision 20.01.00 and
revision 20.03.00, on the same computer simultaneously.
Complete the following steps to upgrade the RSLogix 5000 software version and
project in your enhanced redundancy system.
IMPORTANT There are multiple methods available to upgrade the RSLogix 5000 software version in
your enhanced redundancy system. The specific tasks required vary by system
configuration and requirements.
This section describes one of the methods available.
For more information on upgrading your RSLogix 5000 software version, see Rockwell
Automation Knowledgebase Answer ID 565204 referenced above.
Upgrade the Firmware by Using You can upgrade an enhanced redundancy system revision to another while your
process continues to run. This is known as Redundancy System Update (RSU).
Redundancy System Update
IMPORTANT Remember the following before using this section:
RSU is available when upgrading only from an enhanced redundancy system
revision to another. You cannot use this process to upgrade from a standard
redundancy system to an enhanced redundancy system.
You can upgrade only from firmware revision 19.052 or later, to firmware
revision 20.055 or 20.056_kit1.
Therefore, if you are not upgrading from ControlLogix enhanced redundancy
system, revision 19.052 or later, ignore this section.
The term 1756-RM is synonymous with 1756-RM2 in the text and graphics
throughout this section.
You must use this process if the following conditions exist:
You are upgrading from an enhanced redundancy system, to revision
20.055_kit5 or 20.056_kit1.
Your RSLogix 5000 software project requires EtherNet/IP modules to use
Electronic Keying = Exact Match.
You must install the AOP described on page 20 for the 1756-EN2T/D,
1756-EN2TR/C, or 1756-EN2F/C modules to use Exact Match.
Complete the steps in this table to upgrade your redundancy system from one
enhanced redundancy system revision to another enhanced redundancy revision
while your process continues to run.
Task Page
Before You Begin 46
Upgrade the Workstation Software 47
Upgrade the Redundancy Module Configuration Tool 47
Verify Your RMCT Version 48
Add the EDS Files 49
Prepare the Redundant Chassis for the Firmware Upgrade 49
Update the Primary Chassis 1756-RM2, 1756-RM2XT, 1756-RM, or 1756-RMXT Redundancy 51
Module Firmware
Upgrade the Secondary 1756-RM2, 1756-RM2XT, 1756-RM, or 1756-RMXT Redundancy 52
Module Firmware and All Other Modules Firmware in the Secondary Chassis
Prepare the RSLogix 5000 Project for the Upgrade 57
Lock the System and Initiate a Switchover to Upgrade 59
Upgrade the New Secondary Chassis Firmware 61
Synchronize the Redundant Chassis 63
During the upgrade procedures, you cannot use RSLogix 5000 software to
change the mode of the controller. Instead, use the mode switch on the
front of the controller.
Remember the following when completing the tasks described in the rest
of this section:
Do not make any changes to the RSLogix 5000 project other than
those identified in these tasks.
Verify that no one is making changes to the project.
Do not use a FactoryTalk Batch Server to change equipment
phase-states when upgrading your enhanced redundancy system.
Download and install the redundancy firmware revision bundle from the
Rockwell Automation Support website at:
http://www.rockwellautomation.com/support/
1. From the Get Support Now menu, click the Downloads link.
2. Under Additional Resources, click Firmware Updates.
3. Click Control Hardware.
4. Click the 1756-Lxx Enhanced Redundancy Bundle file.
The Flash Firmware Updates window appears.
With RSLinx Classic software open, from the File menu, choose Exit and
Shutdown.
Install the software required for your redundant system configuration. See
Compatible Software Versions on page 6 for software versions required for use
with this enhanced redundancy system revision.
Use the installation instructions or release notes provided with each software
version for installation procedures and requirements.
The About dialog box opens and indicates the RMCT version.
TIP The RMCT launches at the version that is compatible with the 1756-RM or
1756-RMXT redundancy module firmware that is currently installed.
If you upgrade your RMCT version but do not upgrade your 1756-RM or 1756-RMXT
redundancy module firmware revision compatible with the new RMCT version, the
About dialog box can not reflect the new RMCT version.
If needed, obtain EDS files for modules in your system from the
Rockwell Automation website at:
http://www.rockwellautomation.com/resources/eds/.
1. Once you have downloaded the required EDS file, launch the EDS
Hardware Configuration Tool.
2. Choose Start > Programs > Rockwell Software > RSLinx Tools > EDS
Hardware Installation Tool.
The tool then prompts you to Add or Remove EDS files.
Complete these steps to prepare both the primary and secondary redundant
chassis for redundancy firmware upgrades.
1. Set the mode switch of the primary and secondary controllers to REM.
If the redundant controllers in both chassis of the redundant chassis pair
are not in Remote Program (REM) mode, the redundancy firmware
upgrade cannot be completed.
Status in RMCT
Wait at least 45 seconds before you begin updating the 1756-RM firmware.
During this time, the redundancy module conducts internal operations to
prepare for an upgrade.
Complete these steps to upgrade the firmware of the 1756-RM module in the
primary chassis.
Primary Chassis
Secondary Chassis
4. Click OK.
5. Select the firmware revision to upgrade to and click Next.
6. Click Finish.
The firmware begins to update. When the update is complete, the Update
status dialog box indicates completion.
Power on the secondary chassis. Wait at least 45 seconds before you begin
updating the secondary chassis firmware. During this time, the redundancy
module conducts internal operations to prepare for an upgrade.
1. Complete the following steps for each module in the secondary chassis,
including a new controller, if applicable.
2. If you are replacing or upgrading your module hardware, remove the
module from the secondary chassis and replace it with the new module.
IMPORTANT When replacing communications modules, make sure that the node address
(for ControlNet modules), rotary switches, and Port Configuration (for
Ethernet modules) match the existing modules.
If you are replacing a controller, use this table to determine if your planned
primary and secondary controllers can be used together in the redundant
chassis.
For more information, see the ControlLogix Enhanced Redundancy System User Manual, publication
1756-UM535.
IMPORTANT Controller compatibility is the same for the XT controllers as the standard controllers.
IMPORTANT Continue with step 12 on page 54, if you are upgrading from a system using
revision 19.052, 19.053, 19.053 Oct 2011, or 19.053_kit1, and you are either:
a. Updating 1756-EN2T/C (or earlier) modules with 1756-EN2T/C (or earlier)
modules and the modules being replaced have rotary switches set to 2254.
b. Replacing 1756-EN2T/C (or earlier) modules with EN2T/D modules, and the
modules being replaced have rotary switches set to 2...254.
Primary Chassis
Secondary Chassis
7. Click OK.
8. Select the firmware revision to upgrade to and click Next.
9. Click Finish.
The firmware begins to update. When the update is complete, the Update
status dialog box indicates completion.
Gateway Address
13. Disconnect the Ethernet cables from the secondary Ethernet module.
14. If a 1756-EN2T/D module is the replacement module, then set the
1756-EN2T/D module switches to 888 and insert it in the secondary
chassis.
15. After the reset is complete, remove the module from the secondary chassis.
16. If a 1756-EN2T/C module is being updated, remove the 1756-EN2T/C
from the secondary chassis.
17. Set the switches to 999 and reinsert the module into the secondary chassis.
18. Bridging across the backplane (or via the Ethernet modules USB port),
configure the secondary Ethernet modules Port Configuration to match
the primary Ethernet modules Port Configuration from step 12.
Secondary
Chassis
d. Click OK.
e. Select the firmware revision to upgrade to and click Next.
f. Click Finish.
The firmware begins to update. When the update is complete, the Update
status dialog box indicates completion.
20. After the update completes, connect the Ethernet cable to the secondary
Ethernet module, and wait for communication to resume on the network.
21. Check the Synchronization tab in the RMCT to verify that compatibility
is Full for all communication modules in the chassis.
22. Repeat steps 221 for the next module in the chassis.
Once you have either replaced or upgraded the firmware for each module in the
secondary chassis, prepare the RSLogix 5000 project for the upgrade.
Complete these steps to prepare the RSLogix 5000 program and controllers for
the upgrade.
1. Launch RSLogix 5000 software and go online with the primary controller.
2. Verify that the watchdog time is set to a value that corresponds with the
requirements of the enhanced redundancy system revision and your
application.
See Minimum Value for the Watchdog Time on page 24 for information
about calculating the minimum watchdog time.
8. Go offline.
Controller Properties
TIP If you are unable to specify the new revision, you need to change the Electronic
Keying parameter to Compatible Keying.
You are now ready to lock the system and initiate a locked switchover to update
the primary chassis. Continue with Lock the System and Initiate a Switchover to
Upgrade.
Once you have downloaded the RSLogix 5000 project you prepared, complete
these steps to lock your system and initiate a switchover.
This step results in your secondary chassis assuming control and becoming
the primary chassis. When the switchover is complete, the Locked
Switchover Attempts log indicates success.
In addition to the log, the text in chassis status row indicates the
switchover state.
Once your locked switchover is complete, upgrade the firmware revisions for
modules in the new secondary chassis.
IMPORTANT Following the locked switchover, secondary controllers no longer contain a user
application and their configuration settings are reset to the factory-default settings.
The new secondary controllers use the default settings and the components in the
secondary chassis are upgraded and the system is synchronized.
IMPORTANT Update the Gateway address of the primary chassis ethernet module to 192.168.1.1, if
you are upgrading from a system using revision 19.052, 19.053, 19.053 Oct 2011, or
19.053_kit1, and Electronic Keying is set to Exact Match, Compatible Module or
Disable Keying and you are either:
a. Updating 1756-EN2T/C (or earlier) modules with 1756-EN2T/C (or earlier) modules,
and the modules being replaced have rotary switches set to 2...254.
b. Replacing 1756-EN2T/C (or earlier) modules with EN2T/D modules, and the modules
being replaced have rotary switches set to 2...254.
Complete these steps to upgrade the firmware of all of the modules in the new
secondary chassis, except for the 1756-RM or 1756-RMXT redundancy module
that was already upgraded as described in Update the Primary Chassis
1756-RM2, 1756-RM2XT, 1756-RM, or 1756-RMXT Redundancy Module
Firmware on page 51.
1. If you are replacing and upgrading your module hardware, remove the
module from the secondary chassis and replace it with the new module.
TIP When replacing communications modules, make sure that the node address
(for Control net modules), rotary switches, and Port Configuration (for
Ethernet modules) match the existing modules.
2. If it is an Ethernet module:
a. Make a note of the rotary switch setting on the modules that you are
replacing.
b. Set rotary switches on the replacement module to 888 and insert the
module into the chassis.
c. After reset completed, remove the module.
d. Set the rotary switches to original values that you noted in step a.
e. Insert the module.
f. Go into the module properties and restore the values that you noted in
step 12 on page 54.
3. Launch ControlFLASH software and click Next.
Secondary Chassis
6. Click OK.
7. Select the firmware revision to upgrade to and click Next.
8. Click Finish.
The firmware begins to update. When the updated is complete, the
Update status dialog box indicates completion.
Once you have either replaced or upgraded the firmware for each of the modules
in the new secondary chassis, continue by synchronizing the redundant chassis.
IMPORTANT You only have to do steps 25 if you are upgrading from a system using revision
19.052, 19.053, 19.053 Oct 2011, or 19.053_kit1 and you are either:
a. Updating 1756-EN2T/C (or earlier) modules with 1756-EN2T/C (or earlier)
modules, and the modules being replaced have rotary switches set to 2...254.
b. Replacing 1756-EN2T/C (or earlier) modules with EN2T/D modules, and the
modules being replaced have rotary switches set to 2...254.
3. Initiate a switchover.
4. In the new secondary, set the rotary switches back to the original
configuration.
5. Repeat this for all Ethernet modules that need the rotary switches set back
to 2...254.
6. From the Auto-Synchronization pull-down menu, choose the frequency
that suits your application.
8. Set the redundancy module date and time according to your preference.
9. Click OK.
10. Close the RMCT.
Update IP Address Set Via This section describes how to change Ethernet IP address settings set by software
to IP addresses set by rotary switches when your system must continue to operate
Software to Address Set Via during the update.
Rotary Switches
One reason to change IP address settings to the rotary switch option is if you
system is experiencing a Duplicate IP address condition and IP address swapping
is disabled.
IMPORTANT Make sure the module is not physically connected to the network before
reinstalling it.
14. On the same tab, click Initiate Switchover to switch the primary and
secondary chassis in the system.
15. Remove the new secondary 1756-EN2T module from its chassis and
disconnect the Ethernet cables from the module.
16. Set the rotary switches on the removed secondary module to 888.
17. Reinstall the module into the secondary chassis.
IMPORTANT Make sure the module is not physically connected to the network before
reinstalling it.
22. Verify that the chassis are synchronized.Manually synchronize the chassis,
if needed.
Replace 1756-RM/B (or earlier) You can replace your current redundancy modules with 1756-RM2 modules
without initiating a switchover.
Modules with
1756-RM2 Modules TIP For the following steps, `redundancy modules refers to 1756-RM or 1756-RM/B
modules.
Storing a Project to a Use this procedure to store an updated project and firmware to the nonvolatile
memory card of the controller while your process is running.
Nonvolatile Memory Card While
Your Process Is Running IMPORTANT The ControlLogix controllers use these nonvolatile memory cards.
IMPORTANT We recommend that you store the same project on both controllers nonvolatile
memory cards. By doing so, you can be assured that if a controller, primary or
secondary, loses the project from its internal memory, you can load the most recent
project back onto that controller.
If you store the same project on both controllers nonvolatile memory cards, while the
process is running, you must save the project on the controllers while they are in the
secondary controller state. To do so, you save the project on the secondary controller,
conduct a switchover and save the project on the new secondary controller.
For more information, see the steps below.
Complete these steps to store the project to the nonvolatile memory card on a
secondary controller.
IMPORTANT Remain offline after you have stored the project to nonvolatile memory.
You must stay offline through the remainder of this procedure.
If you do not need to store the project to the nonvolatile memory card in
the primary controller, you are done.
10. If you want to store the project to the primary controllers nonvolatile
memory card, execute a switchover as described in these steps.
12. Return to step 1 on page 70 to store the project on the new secondary
controller.
Access Product Release Notes Product release notes for the products used with this enhanced redundancy
firmware bundle are available online within the Product Compatibility and
Download Center.
2. From the Compatibility Scenarios tab or the Get Downloads tab, search
for and choose your product.
Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Resource Description
ControlLogix Enhanced Redundancy System User Manual, Provides design, installation, and troubleshooting information specific to the enhanced redundancy system.
publication 1756-UM535
FactoryTalk Batch PhaseManager Users Guide, publication Provides instruction for PhaseManager, FactoryTalk Batch, and RSLogix 5000 software to develop a batch
BATCHX-UM010 automation system by using phase logic for Logix5000 controllers.
PhaseManager User Manual, publication LOGIX-UM001 Provides details about PhaseManager software and includes details about tags associated with the PHASE data
type.
ControlFLASH Firmware Upgrade Kit Quick Start, publication Contains information on how to upgrade module firmware.
1756-QS105
ControlLogix Controllers User Manual, publication 1756-UM001 Contains information on how to install, configure, program, and operate a ControlLogix system.
Product Certifications website, http://www.ab.com Provides declarations of conformity, certificates, and other certification details.
Rockwell Automation Technical Support Knowledgebase, available Provides details about how to assemble and mount the controller, how to upgrade firmware, and controller
at http://www.rockwellautomation.com/knowledgebase/ technical specifications.
Notes:
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more
information, contact your local distributor or Rockwell Automation representative, or visit
http://www.rockwellautomation.com/services/online-phone.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this
manual. You can contact Customer Support for initial help in getting your product up and running.
Rockwell Automation tests all of its products to help ensure that they are fully operational when shipped from the
manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to
complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.., Kar Plaza Merkezi E Blok Kat:6 34752 erenky, stanbul, Tel: +90 (216) 5698400