This release includes security enhancements as a part of our ongoing efforts to improve security. For information regarding Rockwell Automation's vulnerability disclosure process, please reference the Rockwell Automation Vulnerability Policy.
This release has the following requirements.
ControlLogix Redundancy Compatible Software for Revision 34.052_kit1
Catalog Numbers: ControlLogix® 5570 controllers*
Software
|
Required Software Version min
|
CompareTool
|
9.00.00
|
ControlFLASH Plus™
|
4.01.00
|
FactoryTalk® Services Platform
|
6.30.00 (CPR9-SR13)
|
FactoryTalk Activation Manager
|
4.06.13 (CPR9-SR13)
|
FactoryTalk Alarms and Events(1)
|
6.30.00 (CPR9-SR13)
|
FactoryTalk AssetCentre
|
12.00.00 (CPR9-SR13)
|
FactoryTalk Batch
|
15.00.00 (3)
|
FactoryTalk View Site Edition(2)
|
13.00 (CPR9-SR13)
|
Factory Talk Linx Redundancy Module
Configuration Tool
|
9.00.00
|
FactoryTalk Linx (4)
|
6.30 (CPR9-SR13)
|
RSLinx® Classic
|
4.30 (CPR9-SR13)
|
Studio 5000 Logix Designer®
|
34.00.00
|
RSNetWorx™ for ControlNet
|
28.01.00
|
RSNetWorx for EtherNet/IP
|
28.01.00
|
(1) You must download a FactoryTalk Alarm and Events patch. See Knowledgebase Article Master list of all available Patch TOCs.
(2) The installation of FactoryTalk View Site Edition also installs FactoryTalk Services Platform, which installs FactoryTalk Alarms and Events. Also, if you download and install the latest FactoryTalk Services Patch Rollup, this patch automatically installs the patch for FactoryTalk Alarms and Events.
(3) Use the most recent FactoryTalk Batch Patch Roll-up with this redundancy firmware revision. For the most recent patch roll-up, see Knowledgebase Article Master list of all available Patch TOCs.
(4) For the most recent FactoryTalk Linx patch roll-up, see Rockwell Automation Knowledgebase Answer ID Knowledgebase Article Master list of all available Patch TOCs.
Digitally Signed Ethernet Module Firmware for Revision 34.052_kit1
Catalog Numbers: 1756-EN2T/C, 1756-EN2TXT/C 1756-EN2T/D, 1756-EN2TK/D, 1756-EN2TXT/D, 1756-EN2TR/B, 1756-EN2TRXT/B, 1756-EN2TR/C, 1756-EN2TRK/C, 1756-EN2TRXT/C 1756- EN2TP/A, 1756-EN2TPK/A, 1756-EN2TPXT/A, 1756-EN2F/B, 1756-EN2FK/B, 1756-EN2F/C, 1756-EN2FK/C
Digitally signed firmware provides more security over the unsigned firmware. This firmware is different based on the EtherNet/IP™ communication modules you use.
Cat. No.
|
Supported
Firmware
Revisions
|
Digitally Signed
Firmware
|
Included with this
Redundancy Bundle
|
1756-EN2T/D
1756-EN2TK/D
1756-EN2TXT/D
|
11.004
|
Yes
|
Yes
|
1756-EN2T/C or earlier
1756-EN2TXT/C or earlier
|
5.009
|
No
|
Yes
|
5.029
|
Yes
|
No
| |
1756-EN2TP/A
1756-EN2TPK/A
1756-EN2TPXT/A
|
11.004
|
Yes
|
Yes
|
1756-EN2TR/C
1756-EN2TRK/C
1756-EN2TRXT/C
|
11.004
|
Yes
|
Yes
|
1756-EN2TR/B or earlier
1756-EN2TRXT/B or earlier
|
5.009
|
No
|
Yes
|
5.029
|
Yes
|
No
| |
1756-EN2F/C
1756-EN2FK/C
|
11.004
|
Yes
|
Yes
|
1756-EN2F/B or earlier
1756-EN2FK/B or earlier
|
5.009
|
No
|
Yes
|
5.029
|
Yes
|
No
|
ControlLogix Redundancy System Components Revision 34.052_kit1
Catalog Numbers: ControlLogix® 5570 controllers*, 1756-RM2, 1756-RM2K, 1756-RM2XT
This redundancy system revision includes the following:
Cat. No.
|
Module Description
|
Series
|
Firmware Revision
|
1756-EN2F
1756-EN2FK
|
ControlLogix EtherNet/IP™ fiber communication
module
|
C
|
11.004
|
B or earlier
|
5.009 or 5.029
| ||
1756-EN2T
|
ControlLogix EtherNet/IP communication module
|
D
|
11.004
|
C or earlier
|
5.009 or 5.029
| ||
1756-EN2TK
|
ControlLogix EtherNet/IP communication module
(conformal coated)
|
D
|
11.004
|
1756-EN2TXT
|
ControlLogix-XT™ EtherNet/IP communication module
|
D
|
11.004
|
C or earlier
|
5.009 or 5.029
| ||
| |||
1756-EN2TP
1756-EN2TPK
1756-EN2TPXT
|
ControlLogix EtherNet/IP communication module –
Parallel Redundancy Protocol (PRP)
|
A
|
11.004
|
1756-EN2TR
|
ControlLogix EtherNet/IP communication module
|
C
|
11.004
|
B or earlier
|
5.009 or 5.029
| ||
1756-EN2TRK
|
ControlLogix EtherNet/IP communication module
(conformal coated)
|
C
|
11.004
|
1756-EN2TRXT
|
ControlLogix-XT EtherNet/IP communication module
|
C
|
11.004
|
B
|
5.029
| ||
1756-CN2
|
ControlLogix ControlNet® bridge
|
C
|
25.006
|
B
|
20.022
| ||
1756-CN2R
|
ControlLogix redundant media ControlNet bridge
|
C
|
25.006
|
B
|
20.022
| ||
1756-CN2RK
|
ControlLogix redundant ControlNet bridge (conformal
coated)
|
C
|
25.006
|
1756-CN2RXT
|
ControlLogix-XT redundant media ControlNet bridge
|
C
|
25.006
|
B
|
20.022
| ||
1756-L71
1756-L72 1756-L73 1756-L73XT 1756-L74 1756-L75 |
ControlLogix 5570 controllers
|
All
|
34.052
|
1756-RM2
|
ControlLogix redundancy module
|
All
|
20.030
|
1756-RM2K
|
ControlLogix redundancy module (conformal coated)
|
All
|
20.030
|
1756-RM2XT
|
ControlLogix-XT redundancy module
|
All
|
20.030
|
1756-N2
|
Slot Filler Module
|
All
|
N/A
|
Additional Resources for Revision 34.052_kit1
Known Restrictions as of ControlLogix® Redundancy Revision 34.052_kit1
CIP Sync™ Technology Included in Redundant Systems:
These anomalies are from previous releases but are still known in this release.
Applications with PowerFlex drives in the I/O configuration can experience a major non-recoverable fault (MNRF) (00200734, 00200735, 00200600, 00200599)
Corrected Anomaly as of Firmware Revision 31.011 and 30.014 for these catalog numbers:
Corrected Anomaly as of Firmware Revision 31.011 and 30.013 for these catalog numbers:
Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:
Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:
If a controller already has an application loaded into it that contains PowerFlex drives in the I/O configuration, a MNRF (Major Non-Recoverable Fault) can occur when any of the following occurs:
For more information and workarounds, see Knowledgebase document 1067997.
Sequential Function Chart Execution Results in a MNRF (2126796)
Controllers
|
First Known in
Version
|
Corrected in Version
|
ControlLogix® 5570 Redundant
|
31.052
|
36.051 and later
|
Known Anomaly as of ControlLogix Redundancy Revision 20.054
Catalog Numbers
You cannot use a 1756-EWEB communication module in an enhanced redundancy system, revision 20.054.
If you are migrating from a ControlLogix standard redundancy system to an enhanced redundancy system, you must replace existing 1756-EWEB communication modules with any of the 1756-EN2Tx communication modules Keep in mind that when you replace a 1756-EWEB communication module with a 1756-EN2Tx communication module, your application loses functionality that is available with only the 1756-EWEB communication module. These are examples of functionality that is no longer available in an Enhanced Redundancy System:
You must account for this lost functionality in your RSLogix 5000 software project.
IMPORTANT: You cannot perform online migration from 1756-EWEB communication modules to 1756-EN2T or 1756-EN2TR communication modules.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
Keep in mind the following alarm considerations in redundancy systems:
(Lgx00093529)
Alarm parameters can be lost when a switchover occurs.
When a switchover occurs in a redundant system that uses alarms, certain alarm parameters can not be transferred to the new primary controller if the parameters have changed since the last crossload of data. Alarm parameters that can not transfer include the following:
Once the alarm data is buffered, the parameters are updated.
(Lgx00093826)
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.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
When a high number of consumed connections are routed through a ControlNet communication module in the primary chassis to a SoftLogix controller, the primary controller reports a connection failure, that is, error code 16#0203. This anomaly occurs despite the fact that there are no network disruptions or device power cycling.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
1756-L7 controllers display No Project message during qualification process.
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.
Known Anomaly as of ControlLogix Redundancy Revision 20.054
Catalog Numbers
There are differences between CIP Sync technology in nonredundant systems and enhanced redundancy systems, revision 20.054.
IMPORTANT: Before you use this enhancement in an enhanced redundancy system, see these publications for a full understanding of CIP Sync technology in any system:
Consider the following when you use CIP Sync technology in an enhanced redundancy system, revision 20.054:
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.
– 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.
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.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
Connections can drop temporarily if a 1756-EN2Tx communication module is not configured correctly.
If your application includes a connection from a remote controller to a primary controller over an EtherNet/IP network, you must use these configuration settings for the 1756-EN2Tx communication module in the primary chassis when it is added to the remote controller’ s RSLogix 5000 project:
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 controller’s RSLogix 5000 project, you can use any settings for the parameters above with no effect on the connection from remote controller to primary controller.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
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 user’ s name. After the switchover, the user name indicates ‘ unknown.’
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
Redundant chassis synchronization fails when the controller is near its connection limit.
Chassis synchronization can fail if the controller is near its connection limits. To reduce the likelihood of this anomaly, verify that you use controller connections within the limits of the controller and that at least eight controller connections are reserved for the redundant system.
Known Anomaly as of ControlLogix Redundancy Revision 20.054
Catalog Numbers
A redundant controller project cannot contain consumed Unicast connections. The project can contain produced Unicast tags consumed by remote consumers.
Known Anomaly as of ControlLogix Redundancy Revision 20.054
Catalog Numbers
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
When a program in the primary controller is inhibited or uninhibited, the secondary can disqualify and re-qualify.
When changing the Inhibit Program setting, plan for secondary chassis disqualification according to potential implications that are specific to your application. Or, unschedule the program rather than inhibiting it.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
Inhibiting equipment phase can cause disqualification.
If you inhibit an equipment phase, or a task that includes an equipment phase, in a primary controller, the secondary controller is disqualified. This disqualification results from program sequence mismatches between the primary and secondary controllers.
Known Anomaly as of ControlLogix Redundancy Revision 20.055
Catalog Numbers
(Lgx00114044, Lgx00113005, Lgx00111045, Lgx00111230)
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:
Object already exists
Already in request mode/state
After the switchover completes, restart the PIO with the redundant chassis pair disqualified or synchronized, and the PIO is complete.
(Lgx00108673)
When you import a routine to an empty program in a synchronized enhanced
redundancy system, disqualification can occur.
(Lgx00108575)
If tasks are not properly tuned and you execute a large PIO, the primary
controller can experience a watchdog fault during the import because the
Watchdog parameter is set too low. The fault causes a switchover.
When this anomaly occurs, however, once the secondary controller goes online, it shows incorrect data in its fault log. The incorrect data appears in the Task, Program, and Routine fields.
The fault log typically shows the following:
You must execute an upload on the secondary controller to obtain correct Task, Program, and Routine watchdog information in the event of a future watchdog fault.
Known Anomaly as of ControlLogix Redundancy Revision 20.054
Catalog Numbers
If a qualification fails due to a ControlNet scheduling issue ((29) Qualification Error - Failed Connection Duplication logged in the 1756-RM event logs), the system continuously attempts the qualification and fail. This continues to occur until the cause is addressed or the Auto-Qualification option is changed to Never. The visual symptom is a repetitive display sequence of QFNG/DISQ on the 1756-RM.
Failure to Download to Primary Redundancy Controller While Synchronized (00210711)
Known Anomaly first identified in Firmware Revision 31.052
If your application is configured to have over 300 I/O connections, a download to a synchronized redundant pair may fail.
When a project download is in process to the controller, the Studio 5000 Logix Designer® application can show Downloading (Not Responding), as shown.
Click Cancel, another dialog box is displayed.
Flashing Firmware From 20.030 To 20.010 Results in The Module Loading BOOT Firmware (00233910)
Devices
|
First Known in
Firmware Revision
|
Corrected in Firmware
Revision
|
1756-RM2/1756-RM2XT
|
20.010
|
—
|
5570 Redundancy
|
30.051_kit2
|
—
|
When a redundancy module is at firmware version 20.030 and an attempt is made to flash to 20.010, the module reverts to 20.022.0.
A workaround to recover from this is to flash the module in the following order: 20.030 -> 20.009 -> 20.010.
For more information, see Knowledgebase Technote Flashing 1756-RM2 from v20.030 to v20.010.
Controller Anomaly with Continuous Task, Indirect Addressing, and CONCAT or DTOS (1442602)
Controllers
|
First Known in
Firmware Revision
|
Corrected in Firmware
Revision
|
CompactLogix™ 5370
|
29.011
|
—
|
Compact GuardLogix® 5370
|
29.011
|
—
|
ControlLogix® 5570
|
29.011
|
—
|
GuardLogix 5570
|
29.011
|
—
|
ControlLogix 5570 redundant
|
30.051
|
—
|
Controller applications with a continuous task with CONCAT or DTOS instructions where indirect addressing exists may result in a controller major nonrecoverable fault/assert when additional task(s) exist. See Knowledgebase Technote 5570/5370 Controller Anomaly with Continuous Task, Indirect Addressing and CONCAT or DTOS.
Concurrent Updates of 1756-RM2 and Communication Modules Causes 1756-RM2 To MNRF/ASSERT (987259)
Devices
|
First Known in Firmware
Revision
|
Corrected in Firmware
Revision
|
1756-RM2/1756-RM2XT
|
20.030
|
—
|
ControlLogix® 5570
redundant controllers
|
34.051
|
—
|
ControlLogix 5580
controllers
|
33.011
|
—
|
ControlLogix 5580
Process controllers
|
33.011
|
—
|
If you update the 1756-RM2 module to revision 20.030 or later while concurrently updating 1756-ENx communication modules to revision 5.008 or 5.028, the 1756-RM2 firmware update fails. The 1756-RM2 displays "ERAS" and/or "E813 Comm Error".
To work around this issue, do not select the 1756-RM2 module along with 1756-ENx revision 5.0xx modules for concurrent updates.
If you do experience a 1756-RM2 firmware update failure:
See the Knowledgebase Technote Concurrent flashing of 1756-RM2 and Communication modules causes 1756-RM2 to fail.