Release Notes

5580E ControlLogix XT controller catalog 1756-L82EXT
Version 37.013 (released 2/2026)

Catalog Number 1756-L82EXT (series B)

These release notes describe version information for 1756-L82EXT, version 37.013 (released 2/2026).

Security

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.

Improved Product Resiliency for Redundancy Firmware Bundle Revision 37.013_kit1

Product improvements have been made to increase 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 recommends that you follow good Industrial Control System (ICS) security practices that include regular product updates. To maintain authenticity, obtain product updates and new releases directly from Rockwell Automation.


Requirements

This release has the following requirements.


ControlLogix® 5580 Redundancy System Update Migration Paths

General Rules:
• Going to a later minor revision and/or kit is acceptable.
• Going to the next major revision is acceptable.
• Going through more than one major revision requires you to perform the RSU process multiple times.

Redundancy System Update Migration Path Limitations
  
From Firmware Revision
Firmware Revision Updates Conditionally Not Allowed*
33.011_kit1
—
33.011_kit2
—
33.012_kit1
—
33.015_kit1
—
33.015_kit2
34.011_kit1
33.017_kit1
34.011_kit1, 34.011_kit2, 34.014_kit1
33.017_kit2
34.011_kit1, 34.011_kit2, 34.014_kit1, 34.014_kit2, 34.015_kit1
34.011_kit1
—
34.011_kit2
35.011_kit1
34.014_kit1
35.011_kit1, 35.011_kit2, 35.011_kit3
34.014_kit2
35.011_kit1, 35.011_kit2, 35.011_kit3, 35.013_kit1
34.015_kit1
35.011_kit1, 35.011_kit2, 35.011_kit3, 35.013_kit1
34.015_kit2
35.011_kit1, 35.011_kit2, 35.011_kit3, 35.013_kit1, 35.013_kit2, 35.014_kit1
35.011_kit1
—
35.011_kit2
—
35.011_kit3
—
35.013_kit1
—
35.013_kit2
36.011_kit1
35.014_kit1
36.011_kit1
35.014_kit2
36.011_kit1, 36.011_kit2
35.016_kit1
36.011_kit1, 36.011_kit2
35.017_kit1
36.011_kit1, 36.011_kit2, 36.011_kit3, 36.013_kit1
36.011_kit1
—
36.011_kit2
—
36.011_kit3
37.011_kit1
36.013_kit1
37.011_kit1
36.014_kit1
37.011_kit1, 37.011_kit2, 37.012_kit1
37.011_kit1
—
37.011_kit2
—
37.012_kit1
—
37.013_kit1
38.011_kit1
38.011_kit1
—

*Depending on the modules used in the local rack, you may not be able to update the system with RSU. See Knowledgebase Technote ControlLogix®: Redundancy Firmware Bundle Revision History to see which modules are at an older firmware in the newer redundancy bundle.



Digitally Signed Ethernet Module Firmware for Revision 37.013_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-EN2TP/A, 1756-EN2TPK/A, 1756-EN2TPXT/A, 1756-EN2F/B, 1756-EN2FK/B, 1756-EN2F/C, 1756-EN2FK/C, 1756-EN4TR/A, 1756-EN4TRK/A, 1756-EN4TRXT/A

Digitally signed firmware provides more security over the unsigned firmware. This firmware is different based on the EtherNet/IP™ communication modules that you use.

Cat. No.
Supported Firmware Revisions
Digitally Signed Firmware
Included with this Redundancy Bundle
1756-EN2T/D
1756-EN2TK/D
1756-EN2TXT/D
12.002
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
12.002
Yes
Yes
1756-EN2TR/C
1756-EN2TRK/C
12.002
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
12.002
Yes
Yes
1756-EN2F/B or earlier
1756-EN2FK/B or earlier
5.009
No
Yes
5.029
Yes
No
1756-EN4TR/A
1756-EN4TRK/A
1756-EN4TRXT/A
8.001
Yes
Yes


Firmware revision 5.029 is not included in the redundancy system, revision 37.013_kit1 firmware bundle. You must download and install this digitally signed firmware after the redundancy bundle is installed.

Important: When you install the digitally signed firmware, that is, firmware revision 5.029, 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 update firmware, the module supports use of only digitally signed firmware. The module rejects any unsigned firmware updates.

You can download firmware revision 5.029 and the redundancy system firmware bundle, revision 37.013_kit1, at the Product Compatibility and Download Center.

Tip: Select the base catalog number in ControlFLASH Plus™ 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 Plus kit.


ControlLogix Redundancy System Components Revision 37.013_kit1

Catalog Numbers: ControlLogix® 5580 controllers, 1756-RM2, 1756-RM2K, 1756-RM2XT, 1756-RM3, 1756-RM3XT

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
12.0021
B or earlier
5.009 or 5.0292
1756-EN2T
ControlLogix EtherNet/IP communication module
D
12.0021
C or earlier
5.009 or 5.0292
1756-EN2TK
ControlLogix EtherNet/IP communication module (conformal coated)
D
12.0021
1756-EN2TXT
ControlLogix-XT™ EtherNet/IP communication module
D
12.0021
C or earlier
5.009 or 5.0292
1756-EN2TP, 1756-EN2TPK, 1756-EN2TPXT
ControlLogix EtherNet/IP communication module – Parallel Redundancy Protocol (PRP)
A
12.0021
1756-EN2TR
ControlLogix EtherNet/IP communication module
C
12.0021
B or earlier
5.009 or 5.0292
1756-EN2TRK
ControlLogix EtherNet/IP communication module (conformal coated)
C
12.0021
1756-EN2TRXT
ControlLogix-XT EtherNet/IP communication module
C
12.0021
B
5.009 or 5.0292
1756-EN4TR, 1756-EN4TRK, 1756-EN4TRXT
ControlLogix EtherNet/IP communication module
A
8.001
1756-L81E, 1756-L81EK, 1756-L82E, 1756-L82EK, 1756-L83E, 1756-L83EK, 1756-L84E, 1756-L84EK, 1756-L85E, 1756-L85EK
ControlLogix 5580 standard controllers
B
37.013
1756-L81E-NSE, 1756-L82E-NSE, 1756-L83E-NSE, 1756-L84E-NSE, 1756-L85E-NSE,
1756-L81E-NSEXT, 1756-L82E-NSEXT, 1756-L83E-NSEXT, 1756-L84E-NSEXT, 1756-L85E-NSEXT
ControlLogix 5580 No Stored Energy (NSE) controllers
B
37.013
1756-L81EXT, 1756-L82EXT, 1756-L83EXT, 1756-L84EXT, 1756-L85EXT
ControlLogix-XT 5580 controllers
B
37.013
1756-L81EP, 1756-L83EP, 1756-L85EP, 1756-L81EPXT, 1756-L83EPXT, 1756-L85EPXT
ControlLogix 5580 process controllers
B
37.013
1756-RM2
ControlLogix redundancy module
All
20.031
1756-RM2K
ControlLogix redundancy module (conformal coated)
All
20.031
1756-RM2XT
ControlLogix-XT redundancy module
All
20.031
1756-RM3
ControlLogix redundancy module
A
22.011
1756-RM3XT
ControlLogix-XT redundancy module
A
22.011
1756-N2
Slot Filler Module
All
N/A

(1) Firmware revision 12.002 is digitally signed firmware.

(2) Firmware revision 5.029 is digitally signed firmware. Firmware revision 5.009 is unsigned firmware.

Additional Resources for Revision 37.013_kit1

For more information on how to install, configure and use your ControlLogix redundancy system, see:

ControlLogix Redundancy Modules Installation Instructions, publication 1756-IN087.
Redundancy Systems User Manual, publication 1756-UM015.
High Availability System Reference Manual, publication HIGHAV-RM002.
Replacement Guidelines: Logix 5000® Controllers, publication 1756-RM100.



ControlLogix Redundancy Compatible Software for Revision 37.013_kit1

Catalog Numbers: ControlLogix® 5580 controllers.

Software
Required Software Version, Min
Logix Designer Compare Tool
11.00.00
ControlFLASH Plus™
6.00.00
FactoryTalk® Services Platform
6.50.00 (CPR9-SR15)
FactoryTalk Activation Manager
5.01.01
FactoryTalk Alarms and Events(1)
6.50.00 (CPR9-SR15)
FactoryTalk View Site Edition(2)
15.00 (CPR9-SR15)
FactoryTalk Batch(3)
17.00.00
FactoryTalk AssetCentre
13.00.00 (CPR9-SR14)
FactoryTalk Linx Redundancy Module Configuration Tool
10.00.00
FactoryTalk Linx(4)
6.50 (CPR9-SR15)
Studio 5000 Logix Designer®
37.00.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 Article Master list of all available Patch TOCs.



Controller Restrictions in Redundancy Systems with Revision 37.013_kit1

Known Restrictions as of ControlLogix® Redundancy Revision 37.013_kit1

This revision supports the following: ControlLogix 5580 controllers, 1756-RM2, 1756-RM2K, 1756-RM2XT, 1756-RM3, and 1756-RM3XT modules.

1756-EN2T, 1756-EN2TK, 1756-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2FK, 1756-EN2TP, 1756-EN2TPK, 1756-EN2TPXT

The 1756-EN2x communication modules provide 259 CIP™ connections. However, three of the 259 CIP connections are always reserved for redundant control. These three redundant-system CIP connections always appear to be in use, even when no connections are open. Because three of the 259 CIP connections are reserved for redundancy, 256 CIP connections are available for nonredundancy use.

The Immediate Output (IOT) instruction does not function correctly when used in redundancy and should not be used. Additionally, the 1756-EN2x communication modules do not support bumpless I/O on switchover with IOT instructions. Because these modules do not support bumpless I/O on switchover with the IOT instruction, they cannot override the RPI in a remote chassis and immediately send new data over the EtherNet/IP™ network.

1756-EN4TR, 1756-EN4TRK, 1756-EN4TRXT

The 1756-EN4TR modules with firmware revision 4.001 or later support CIP Security™ for program upload/download/monitoring (not I/O) when the modules are paired with redundant ControlLogix 5580 controllers in the redundant chassis pair. The ControlLogix 5580 controllers must be at firmware revision 35.011 or later, and the 1756-EN4TR pair must be configured for non-IP address swapping.

The 1756-EN4TR modules are also supported in a remote rack as a standard adapter or in a redundant adapter architecture.

ControlLogix 5580 redundancy-enabled controllers, 1756-EN2T, 1756-EN2TK, 1756-EN2TR, 1756-EN2TRK, 1756-EN2TRXT, 1756-EN2TXT, 1756-EN2F, 1756-EN2FK, 1756-EN2TP, 1756-EN2TPK, 1756-EN2TPXT, 1756-EN4TR, 1756-EN4TRK, 1756-EN4TRXT

A redundant controller project cannot contain consumed Unicast connections. The project can contain produced Unicast tags that are consumed by remote consumers.

CIP Sync™ Technology Included in Redundant Systems:

1 - There are differences between CIP Sync technology in non-redundant systems and redundancy systems.
2 - IMPORTANT: Before you use this enhancement in a redundancy system, see these publications for a full understanding of CIP Sync technology in any system:
- Redundancy Systems User Manual, publication 1756-UM015
- Deploying Scalable Time Distribution within a Converged Plantwide Ethernet Architecture, publication ENET-TD016


Consider the following when you use CIP Sync technology in a redundancy system:
1 - 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 one path to the Grandmaster.

2 - If time synchronization is enabled in any controller in the primary chassis of a disqualified Redundant Chassis Pair, and no 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.

3 - While CIP Sync technology can handle multiple paths between timeTransmitter and timeReceiver 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.

4 - If the primary controller is the Grandmaster, the 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 makes sure that a change to a new Grandmaster when the redundancy system switches over.

5 - 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 non-redundant system.
- The synchronization of the redundancy system can take longer when you use CIP Sync technology.

ControlLogix 5580 controllers

You can have only one controller in each chassis in a redundant chassis pair.

The embedded Ethernet port is disabled when the controller is enabled for redundancy.

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 new primary controller.

The Firmware Supervisor feature is not supported in a redundant system.

You cannot use event tasks in a ControlLogix redundancy system. When you enable redundancy, you must change event tasks to nonevent tasks or delete them from your project.

You cannot use Motion in ControlLogix 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, often configuration related, the redundancy 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.

The MinDurationACC alarm tag member value does not update, and it stays at a 0 value. This change does not affect the MinDuration calculations.

1756-EN2T, 1756-EN2TK, 1756-EN2TR, 1756-EN2TRK, 1756-EN2TRXT, 1756-EN2TXT, 1756-EN2F, 1756-EN2FK, 1756-EN2TP, 1756-EN2TPK, 1756-EN2TPXT

The System Event History displays a `Module Failure’ entry when you insert a 1756-EN2x 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 a communication module was inserted in the chassis.


  

Corrected Anomalies in This Release

This release corrects the following anomalies.


Controller Cannot Establish New Class 3 Communication (5052808, 4964866, 4964936)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix® 5380
36.011
36.014, 37.013
Compact GuardLogix® 5380 SIL 2
36.011
36.014, 37.013
Compact GuardLogix 5380 SIL 3
36.011
36.014, 37.013
CompactLogix 5380 Process
36.011
36.014, 37.013
CompactLogix 5480
36.011
36.014, 37.013
ControlLogix® 5580
36.011
36.014, 37.013
GuardLogix 5580
36.011
36.014, 37.013
ControlLogix 5580 Process
36.011
36.014, 37.013

Class 3 communications can stop working resulting in:
• HMIs not communicating to the controller.
• Not being able to get online with the controller in Studio 5000 Logix Designer.
• MSG instructions to and from the controller not completing with a done (.DN) bit.

This anomaly occurs more often when:

• There are MSG instructions configured for Connected and Uncached,

and\or

• There are MSG instructions configured for Sockets and have many retries.

This anomaly can cause a controller assert in V38.011.


Controller can Assert when Accessing a Closed OPC UA Connection (4168880)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix® 5380
36.011
36.014, 37.013, 38.011 and later
Compact GuardLogix® 5380 SIL 2
36.011
36.014, 37.013, 38.011 and later
Compact GuardLogix 5380 SIL 3
36.011
36.014, 37.013, 38.011 and later
CompactLogix 5380 Process
36.011
36.014, 37.013, 38.011 and later
CompactLogix 5480
36.011
36.014, 37.013 and later
ControlLogix® 5580
36.011
36.014, 37.013, 38.011 and later
GuardLogix 5580
36.011
36.014, 37.013, 38.011 and later
ControlLogix 5580 Process
36.011
36.014, 37.013, 38.011 and later

Under certain timing conditions, a timeout could occur as a HELLO response was received. The controller would then attempt to read from a connection that was already closing, which could result in an assert.




Logix Controllers Display "TEST" or "C" After a Firmware Update from the SD Card (5023927, 5194416, 5194424)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix® 5380
28.011
36.014, 37.013, 38.011 and later
Compact GuardLogix® 5380 SIL 2
31.011
36.014, 37.013, 38.011 and later
Compact GuardLogix 5380 SIL 3
32.013
36.014, 37.013, 38.011 and later
CompactLogix 5380 Process
33.011
36.014, 37.013, 38.011 and later
CompactLogix 5480
32.011
36.014, 37.013 and later
ControlLogix® 5580
28.011
36.014, 37.013, 38.011 and later
GuardLogix 5580
31.011
36.014, 37.013, 38.011 and later
ControlLogix 5580 Process
33.011
36.014, 37.013, 38.011 and later

ControlLogix, GuardLogix, CompactLogix and Compact GuardLogix controllers can get stuck in test mode and display "TEST" or "C" after a SD card was used to update firmware.
There is no way to recover from this state.
For additional information and a workaround, see Knowledgebase Article Logix controllers display "TEST" or "C" after a firmware update from the SD card.





Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.

MCTPO Conflict Causes Incorrect Instruction Outputs (1806725)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5380
31.011
—
Compact GuardLogix® 5380 SIL 2
31.011
—
Compact GuardLogix 5380 SIL 3
32.013
—
CompactLogix 5380 Process
33.011
—
CompactLogix 5480
32.011
—
ControlLogix® 5580
31.011
—
GuardLogix 5580
31.011
—
ControlLogix 5580 Process
33.011
—


When you use a Motion Calculate Transform Position with Orientation (MCTPO) instruction in multiple tasks simultaneously, the MCTPO reports an incorrect transform position.

To work around this anomaly, place a User Interrupt Disable (UID) instruction before each MCTPO instruction in each task, then place a User Interrupt Enable (UIE) instruction after each MCTPO operation in each task. If all the MCTPO instructions are used in only one task, no change needs to be made.




Connected Uncached Messages Fail (00173896)

Known Anomaly First Identified in:

Connected UnCached messages that are sent to the controller can fail. This anomaly typically occurs if the Connected UnCached messages are sent when the controller is handling many messages and has temporarily run out of buffer resources.

To work around the anomaly, try the following:




MSF Instruction Clears the .DriveEnableStatus Bit after the .DN is Set (00175088)

Known Anomaly First Identified in:

The Motion Servo Off (MSF) instruction can report a .DN (Done) status before the drive clears the .DriveEnableStatus bit.


Value That Is Outside the Supported WallClockTime Range (00182341, 00182342, 00190288, Lgx00169520)

Corrected Anomaly in:

Known Anomaly First Identified in:

  
  
  
  


When reading or viewing the WCT (WallClockTime) of the controller, the year can show a value of 586XXX (where the XXX is any values). This means that the wallclock value is outside the valid range for EPoch time.

The range of the WCT has been tightened in the controller to 1/1/1970 00:00:00.000...12/31/2069 23:59:59.999. If the controller tries to handle a value outside the defined range, the controller does not apply the new value. It now logs a minor fault, Type 13 Code 21. The fault displays an unknown fault in the RSLogix 5000® software.

graphic

When the fault is logged, the WCT of the controller is set to 1/1/19XX 00:00:00.000, where XX is 81...86. The year corresponds to the Info[0] value for the minor fault.



  
Unable to establish connection to 32 client instances of the TCP/IP SocketObject (00180261)
Known Anomaly First Identified in:
You cannot connect to 32 instances of the TCP/IP socket object. The maximum number of connections is 31.

Velocity Disturbances on Consumed Axes While Running Constant Speed (00217531)

Known Anomaly First Identified in:

Minor fluctuations of the system time offset both on the producer controller and consumer controller side can cause minor velocity spikes, typically less than 1 % on the consumed axes in the remote controller.

This behavior is aesthetic and does not impact functionality.


SCARA 4D Coupled: Moving J6 Axis on Target Side Causes Motion on J6 and J3 Axes (00229999)


Known Anomaly First Identified as of Firmware Revision 32.012

Catalog Numbers:


In some SCARA 4D coupled robots, there is a mechanical coupling between Joint 3 and Joint 6 axes, due to a ball screw mechanism. The Z and Rz axes are decoupled in firmware, so that you will not notice Z movement due to rotation on Rz when you make a move on the source coordinate system.

If you try to make a move on J6 in the target coordinate system, you will notice movement in J3 due to rotation of J6. You must decouple the J3 and J6 axes in your application code to cancel movement on J3 when J6 is moved.


Removing Security Policy Can Result in Lost Access to The Controller (00233531)

Known Anomaly First Identified as of Firmware Revision 33.011

Catalog Numbers: ControlLogix® 5580 Controllers, ControlLogix 5580 Process Controllers

If you remove a security policy from the controller in FactoryTalk® Policy Manager, version 1.0.0 and then try to download a project with Studio 5000 Logix Designer® application, the download fails.

You also cannot change the controller's IP address with FactoryTalk Linx or RSLinx® software.

To resolve the anomaly, reset the controller to the factory default state.

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:

  1. Power cycle the 1756-RM2 to clear the fault (E813).
  2. After other concurrent updates are completed, relaunch ControlFLASH Plus® and update the 1756-RM2 module.

See the Knowledgebase Technote Concurrent flashing of 1756-RM2 and Communication modules causes 1756-RM2 to fail.

Disqualification of Redundant Chassis Pair Due to Concurrent Connection Timeout (1895856)

Communication Modules
First Known in Firmware Revision
Corrected in Firmware Revision
1756-EN4TR, 1756-EN4TRK,
1756-EN4TRXT
5.001
5.003

In a ControlLogix® 5580 Redundancy system, if 1756-EN4TR modules in the redundant chassis pair (RCP) are configured for Concurrent Communication, then the RCP can experience a disqualification due to a concurrent connection timeout.
  

Standard I/O Forces do not Display Correctly Through a Locked Switchover in Redundancy (5211412)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
ControlLogix® 5580
33.011
—
ControlLogix 5580 Process
33.011
—
GuardLogix 5580
37.011
—
ControlLogix 5590
38.011
—
ControlLogix 5590 Process
38.011
—

Standard I/O forces will not be correctly displayed on the new primary after a locked switchover during a redundancy system update if all the following conditions are met:

• A force is enabled with global forces enabled on the old primary controller.
• The user selects “No” when prompted by Logix Designer to enable forces when downloading to the new primary controller.

The I/O point will appear forced in Logix Designer, Global Forces will be enabled, and the LED indicates forces are present (solid amber) but the actual value of the I/O point will not reflect the force.

To recover: Disable and re-enable global forces on the new primary controller.


Controller can Assert When Stopping an Axis That Is Executing an S-Curve Profile Jog (4913301, 4976159)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
38.011 and later
Compact GuardLogix® 5370
28.011
38.011 and later
ControlLogix® 5570
18.012
38.011 and later
GuardLogix 5570
20.011
38.011 and later
CompactLogix 5380
28.011
38.011 and later
Compact GuardLogix 5380 SIL 2
31.011
38.011 and later
Compact GuardLogix 5380 SIL 3
32.013
38.011 and later
CompactLogix 5380 Process
33.011
38.011 and later
CompactLogix 5480
32.011
38.011 and later
ControlLogix 5580
28.011
38.011 and later
GuardLogix 5580
31.011
38.011 and later
ControlLogix 5580 Process
33.011
38.011 and later

A controller assert can occur when a Motion Axis Stop (MAS) instruction is executed on the same axis that is concurrently executing an S-Curve Motion Axis Jog (MAJ) instruction.

Work arounds to consider:

• Change the MAJ profile from S-Curve to Trapezoidal.
or
• Add a condition to prevent MAS on an axis where MAJ with S-Curve profile is in progress; this would involve the axis .IP bit.

  

Application Notes

This release has the following application notes.

PXRQ Instruction Can Cause a Controller MNRF/Assert

Controllers
First Known in Firmware Revision
CompactLogix™ 5380
31.011
Compact GuardLogix® 5380 SIL 2
31.011
Compact GuardLogix 5380 SIL 3
32.013
CompactLogix 5380 Process
33.011
CompactLogix 5480
32.011
ControlLogix® 5580
31.011
GuardLogix 5580
31.011
ControlLogix 5580 Process
33.011


Writing to the Equipment Phase External Request (PXRQ) instruction control\backing tag needs to be conditioned with a set .PC bit of the control\backing tag or the controller can MNRF/assert.

Note: Writing to the .PC item of the PXRQ control tag structure is expressly prohibited.
Only the phase engine in the controller firmware should change the value of the .PC item.

New Firmware Updates Can Impact the Performance of Message Rate Capacity HMI/MSG (Class 3) Data

Each new major revision of the controller/communication module firmware provides additional features and functionality, but this consumes additional processing power from the module even if the features are not utilized. This manifests as degrading HMI/messaging performance for the respective module.

Despite this degradation, the specifications defined for the respective modules have been maintained:

Module
Message Rate Across the Embedded Ethernet Port
ControlLogix® 5580
CompactLogix® 5380
2000 MSG/sec
GuardLogix® 5580 controllers in a SIL3 configuration
Compact GuardLogix 5380 SIL3 controllers
1000 MSG/sec
1756-EN4TR Ethernet modules
3700 MSGs/sec

To improve the messaging capacity, it is recommended to employ the following:

For more information, see these publications:

  
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.