CVE-2022-3752: Denial-of-Service Vulnerability That Affects Logix 5000™ Controllers

For a full list of the potentially affected Rockwell Automation products and a description of the vulnerability, see Knowledgebase Product Notice Logix Controllers Vulnerable to Denial-of-Service Attack.

Improved Product Resiliency for Redundancy Firmware Bundle Version 33.015_kit2

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.

ControlLogix Redundancy Compatible Software for Revision 33.015_kit1

Catalog Numbers: ControlLogix® 5580 controllers*

(1) You must download a FactoryTalk Alarm and Events patch. See Knowledgebase Technote 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 Technote Master list of all available Patch TOCs.

IMPORTANT: The following steps apply only to the FactoryTalk Alarms and Events installation:

1. Install FactoryTalk View Site Edition.

This installation installs FactoryTalk Services Platform, which installs FactoryTalk Alarms and Events.

2. Download and install the latest FactoryTalk Services Patch Rollup.

This installation automatically installs the patch for FactoryTalk Alarms and Events.

(4) For the most recent FactoryTalk Linx patch roll-up, see Knowledgebase Technote Master list of all available Patch TOCs.

ControlLogix Redundancy System Components Revision 33.015_kit1

Catalog Numbers

• ControlLogix® 5580 controllers
• 1756-RM2, 1756-RM2K, 1756-RM2XT

This redundancy system revision includes the following:

(1) Firmware revision 11.003 is digitally signed firmware.

(2) Firmware revision 5.028 is digitally signed firmware. Firmware revision 5.008 is unsigned firmware.

EtherNet/IP is a trademark of ODVA, Inc.

Additional Resources for Revision 33.015_kit1

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

• The ControlLogix Redundancy Modules Installation Instructions, publication 1756-IN087.
• The ControlLogix 5580 Redundant Controller User Manual, publication 1756-UM015.
• High Availability System Reference Manual, publication HIGHAV-RM002-EN-P.
• Replacement Guidelines: Logix 5000™ Controllers, publication 1756-RM100.

Digitally Signed Ethernet Module Firmware for Revision 33.015_kit1

Catalog Numbers

• 1756-EN2T/C, 1756-EN2T/D, 1756-EN2TR/B, 1756-EN2TR/C, 1756- EN2TP/A, 1756-EN2F/B, 1756-EN2F/C

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

Firmware revision 5.028 is not included in the redundancy system, revision 33.015_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.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 update firmware, the module supports use of only digitally signed firmware. The module rejects any unsigned firmware updates.

You can download firmware revision 5.028 and the redundancy system firmware bundle, revision 33.015_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.

EtherNet/IP is a trademark of ODVA, Inc.

Controller Restrictions in Redundancy Systems with Revision 33.015_kit1

Known Restrictions as of ControlLogix® Redundancy Revision 33.015_kit1

This revision supports the following:

• ControlLogix 5580 controllers
• 1756-RM2, 1756-RM2K, and 1756-RM2XT modules

Catalog Numbers

1756-EN2T, 1756-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2TP:

• 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 1756-EN2x communication modules do not support bumpless I/O on switchover with Immediate Output (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:

• The 1756-EN4TR modules are not supported in the local rack for redundancy. The 1756-EN4TR modules are only supported in a remote rack as a standard adapter or in a redundant adapter architecture.

ControlLogix 5580 redundancy-enabled controllers, 1756-EN2T, 1756-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2TP:

• 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:

• There are differences between CIP Sync technology in non-redundant systems and redundancy systems.

• ControlLogix 5580 Redundant Controller User Manual, publication 1756-UM015
• Integrated Architecture® and CIP Sync Configuration Application Technique, publication IA-AT003

• Consider the following when you use CIP Sync technology in a redundancy system:

• 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.
• 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.
• 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 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.
• When a switchover occurs, these events take place:

1. 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.
2. 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 1756-RM2 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-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2TP:

• 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.

CIP, CIP Sync, and EtherNet/IP are trademarks of ODVA, Inc.

ControlLogix Redundancy Compatible Software for Revision 33.015_kit2

(1) You must download a FactoryTalk Alarm and Events patch. See Knowledgebase Technote 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 Technote Master list of all available Patch TOCs.

(4) For the most recent FactoryTalk Linx patch roll-up, see Knowledgebase Technote Master list of all available Patch TOCs.

Digitally Signed Ethernet Module Firmware for Revision 33.015_kit2

Catalog Numbers: 1756-EN2T/C, 1756-EN2T/D, 1756-EN2TR/B, 1756-EN2TR/C, 1756- EN2TP/A, 1756-EN2F/B, 1756-EN2F/C

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

Firmware revision 5.029 is not included in the redundancy system, revision 33.015_kit2 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 33.015_kit2, 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 33.015_kit2

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

This redundancy system revision includes the following:

(1) Firmware revision 11.004 is digitally signed firmware.

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

Additional Resources for Revision 33.015_kit2

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

Controller Restrictions in Redundancy Systems with Revision 33.015_kit2

Known Restrictions as of ControlLogix® Redundancy Revision 33.015_kit2

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

1756-EN2T, 1756-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2TP:

1756-EN4TR:

ControlLogix 5580 redundancy-enabled controllers, 1756-EN2T, 1756-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2TP:

CIP Sync Technology Included in Redundant Systems:

ControlLogix 5580 controllers

1756-EN2T, 1756-EN2TR, 1756-EN2TXT, 1756-EN2F, 1756-EN2TP:

ControlFLASH and ControlFLASH Plus Prevents Update to V33.011, V33.012, and V34.011 for ControlLogix 5580 XT Controllers

When you attempt to update a ControlLogix 5580 XT controller from a prior operational firmware (such as V32.016) to 33.011, 33.012, or 34.011 firmware, ControlFLASH™ and ControlFLASH Plus® prevents the update, and displays this error message:

“Invalid Revision: The update revision selected is not compatible with the selected target device. Press F1 for more information”

This does not occur when you attempt to update from boot firmware.

If 33.011, 33.012, or 34.011 is desired, flash to a version that has corrected this anomaly prior to the flash attempt.

Errors on I/O After Redundancy System Update (1286591, 1286593)

16#FF08-Invalid path to module error codes could occur on I/O modules that were inhibited or disconnected during a Redundancy System Update (RSU), and then uninhibited or reconnected after the update is complete. Error codes can be found on the Connection Tab in the I/O module properties. See Knowledgebase Technote 16#FF08 errors on I/O after a Redundancy System Update.

Online Edits of a Drive Peripheral for a Drive That Does Not Support ADC Can Cause a Controller MNRF (1502674, 1518216)

For a full list of the potentially affected Rockwell Automation products and a description of the vulnerabilities, see Knowledgebase Technote Product Notice 2022-05-002 - ControlLogix 5580 Redundancy Controller with V33 Firmware May Experience Anomalous Behavior when online Editing of Drive Peripherals Associated with Drives that do not support ADC.

MCTPO Conflict Causes Incorrect Instruction Outputs (1806725)

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.

Controller Can MNRF When Executing CPS Instruction with Specific Data Types (1800992, 2129625, 2129629)

When executing a Synchronous Copy File (CPS) instruction with a motion diagnostics connection as the source or destination tag, the controller can experience a major nonrecoverable fault (MNRF).

To work around this anomaly, do not use motion diagnostics connections (such as AB:Motion_Diagnostics:S:1) as arguments to the CPS instruction. If a copy is still necessary, use a non-synchronous copy via the COP instruction.

Periodic User Tasks Without Any Scheduled Programs Experience Overlaps on The New Primary Controller After Switchover (1723127, 1810033)

When configured for redundancy, if the application contains a periodic user task without any scheduled programs, then that user task will report task overlaps on the new Primary controller after a switchover.

The task overlaps result in a minor fault being reported.

Periodic User Tasks Can Experience Unexpected Overlaps on The New Primary Controller If Switchover Occurs Soon After Qualification Completes (1723127)

When configured for redundancy, if a switchover occurs before the period of the periodic user task expires, then the periodic user tasks that are running on the new Primary controller can report overlaps following the switchover.

The task overlaps result in a minor fault being reported.

Sent Bytes Per Second Displays a Larger Incorrect Value (1548181)

Under HMI/MSG Connected (EtherNet/IP Port) on the device Diagnostic webpages, Sent Bytes Per Second displays a much larger incorrect value, not the actual sent bytes per second.

Inverting Motion Polarity Does Not Invert the Value of Certain Signal Attributes (1329074, 1332544)

When the axis Motion Polarity bit is set to inverted, certain Signal attributes for a CIP™ axis will display a value opposite of the programmed direction of the axis.

The affected signal attributes are:

• #365 Fine Command Position

• #495 Torque Estimate

• #432 Position Reference

• #523 Motor Electrical Angle

• #565 Slip Compensation

• #600 Output Frequency

• #601 Output Current

• #602 Output Voltage

• #603 Output Power

• #1403 Velocity Feedback 1

• #1453 Velocity Feedback 2

For more information, see the Knowledgebase Technote Inverting Motion Polarity Does Not Invert the Value of Certain Signal Attributes.

Work arounds to consider:

Connected Uncached Messages Fail (00173896)

• GuardLogix® 5580 Controllers, Revision 29.011
• ControlLogix® 5580 Controllers, Revision 28.011
• ControlLogix 5580 Process Controllers, Revision 33.011
• CompactLogix™ 5380 Controllers, Revision 28.011
• CompactLogix 5380 Process Controllers, Revision 33.011
• Compact GuardLogix 5380 SIL 2 Controllers, Revision 31.011
• Compact GuardLogix 5380 SIL 3 Controllers, Revision 32.013
• CompactLogix 5480 Controllers, Revision 32.011

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:

• Cache connections. As many as 256 connections are available.
• Use the message instructions in a periodic task instead of a continuous task.
• Do not trigger messages as quickly as possible.

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

Known Anomaly First Identified in:

• ControlLogix® 5580 Controllers, Revision 28.011
• ControlLogix 5580 Process Controllers, Revision 33.011
• GuardLogix® 5580 Controllers, Revision 29.011
• CompactLogix™ 5380 Motion Controllers, Revision 28.011
• CompactLogix 5380 Process Controllers, Revision 33.011
• Compact GuardLogix 5380 SIL2 Controllers, Revision 31.011
• Compact GuardLogix 5380 SIL3 Controllers, Revision 32.013
• CompactLogix 5480 Controllers, Revision 32.011

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:

• ControlLogix® 5570, Firmware Revision 30.011 and 20.019
• GuardLogix® 5570, Firmware Revision 30.011
• CompactLogix™ 5370, Firmware Revision 30.011 and 20.019
• Compact GuardLogix 5370, Firmware Revision 30.011
• ControlLogix 5560, Firmware Revision 20.019

Known Anomaly First Identified in:

• ControlLogix® 5580, Firmware Revision 28.011
• ControlLogix 5580 Process, Firmware Revision 33.011
• GuardLogix® 5580, Firmware Revision 31.011

• CompactLogix™ 5380, Firmware Revision 28.011
• CompactLogix 5380 Process, Firmware Revision 33.011
• Compact GuardLogix 5380 SIL2, Firmware Revision 31.011
• Compact GuardLogix 5380 SIL3, Firmware Revision 32.013
• CompactLogix 5480, Firmware Revision 32.011

• ControlLogix 5570, Firmware Revision 19.011
• GuardLogix 5570, Firmware Revision 20.011

• CompactLogix 5370, Firmware Revision 20.011
• Compact GuardLogix 5370, Firmware Revision 28.011

• ControlLogix 5560, Firmware Revision 11.011

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.

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.

• GuardLogix® 5580 Controllers, Revision 31.011
• ControlLogix® 5580 Controllers, Revision 31.011
• ControlLogix 5580 Process Controllers, Revision 33.011
• CompactLogix™ 5380 Controllers, Revision 31.011
• CompactLogix 5380 Process Controllers, Revision 33.011
• Compact GuardLogix 5380 SIL 2 Controllers, Revision 31.011
• Compact GuardLogix 5380 SIL 3 Controllers, Revision 32.013
• CompactLogix 5480 Controllers, Revision 32.011

Known Anomaly First Identified in:

• ControlLogix® 5580 Controllers, Revision 32.011
• ControlLogix 5580 Process Controllers, Revision 33.011
• GuardLogix® 5580 Controllers, Revision 32.011
• CompactLogix™ 5380 Motion Controllers, Revision 32.011
• CompactLogix 5380 Process Controllers, Revision 33.011
• Compact GuardLogix 5380 SIL2 Controllers, Revision 32.011
• Compact GuardLogix 5380 SIL3 Controllers, Revision 32.013

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.

Known Anomaly First Identified as of Firmware Revision 32.012

Catalog Numbers:

• ControlLogix® 5580 Controllers
• ControlLogix 5580 Process Controllers
  
• CompactLogix™ 5380 Controllers
• CompactLogix 5380 Process Controllers
  
• GuardLogix® 5580 Controllers
• Compact GuardLogix 5380 Controllers
• CompactLogix 5480 Controllers

Known Anomaly First Identified as of Firmware Revision 33.011

A Controller Producing Tags, Consumed by Two Or More Controllers Can MNRF/Assert (987186)

If network disruptions are present that cause connections to drop, the producing controller can experience a major nonrecoverable fault (MNRF/Assert). The likelihood of the MNRF/Assert occurring on a producing controller increases as the:

• Number of consuming controllers increases.
• Number of consuming tags increases.
• Amount of network disruptions increases.

MAR and MAW Instructions Do Not Execute Properly After Controller Power Is Cycled (1120359, 1161982)

If a controller is powered down while a Motion Arm Registration (MAR) and/or a Motion Arm Watch (MAW) instruction is active, the state of the instruction will not be accurate on controller power up.

• A Motion Disarm Registration (MDR) is required to reset the MAR instruction.
• A Motion Disarm Watch (MDW) is required to reset to the MAW instruction.

For more information, see the Knowledgebase Technote MAR or MAW Instruction Not Executing Properly After a Power cycle.

AxisHomedStatus Bit Clears After Storing Project to Nonvolatile Memory (1169495, 1218911)

For a motion axis that was previously homed, the AxisHomedStatus bit will clear (value=0) after a project is stored to Nonvolatile Memory. See Knowledgebase Technote AxisHomeStatus bit cleared after storing project to the SD card.

Controller Input Data Associated with Remote 5069/5094 Standard Modules Can Be Inconsistent When Communication Errors Occur (1297430)

Remote 5069\5094 standard modules with unicast connection type can have inconsistent data when communication errors occur.

For more information, see Knowledgebase Technote Controller Input Data Associated with Remote 5069/5094 Standard Modules Can Be Inconsistent When Communication Errors Occur.

PCMD Returns Incorrect Error Code (1056295)

Equipment Phase Command (PCMD) returns the incorrect error code “0x6003, HIGH_PRIORITY_OWNED” when it should return “0x6004, NOT_ATTACHED”

CIP™ Axis Velocity Loop Causes Controller To MNRF/Assert (1008498, 1006943)

Setting the Axis Direct Command Velocity Tag to “Not a Number” (NaN) causes the controller to experience a major nonrecoverable fault/assert.

Task Switching of User Tasks When Executing Multiple RTOS Instructions Can Cause A MNRF/Assert (1105041)

If the application contains RTOS (Real to String) instructions in different user tasks and the following execution occurs:

• Task A is executing an RTOS.
• Task A is interrupted to execute Task B.
• Task B executes an RTOS.
• Task A completes the RTOS previously interrupted.

A major nonrecoverable fault (MNRF/Assert) can occur.

For information on how to work around this in user application code, see Knowledgebase Technote RTOS instruction execution causes controller to MNRF.

Concurrent Updates of 1756-RM2 and Communication Modules Causes 1756-RM2 To MNRF/ASSERT (987259)

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.

PortPhysicalAddressInfo GSV Does Not Populate After Controller Power Cycle (1451494, 1514584)

When a Get System Value (GSV) instruction configured for Class Name: TimeSynchronize and Attribute Name: PortPhysicalAddressInfo executes after a controller power cycle, the physical address (MAC ID) does not populate.

An OPC Client Requests an Excessively High Number of OPC Groups from RSLinx Classic’s OPC Interface (1239180, 1646089)

If an OPC Client requests a high number of OPC groups, this causes RSLinx® Classic to make a high number of optimized tag requests to a Logix controller and causes the Logix controller to experience a major nonrecoverable fault.

Controller Can MNRF During Online Edit (2123008, 2306717, 3741373)

Controller Can Become Unresponsive When You Inhibit or Uninhibit a Module (3080005)

1. Update the firmware on the controller.
2. Open the final copy of the project and download it to the controller.
3. Stay in Program Mode and store the project to the SD card.
4. When the storing process is complete, the controller can be put into Run Mode.

1. Upgrade the controller’s firmware.
2. Install the latest release of software associated with the major revision of firmware.
3. Open the project file and perform a compact and delete of cache.
   1. Go to File → Compact
   2. When the Compact Project File dialog appears, make sure the Delete cached build data checkbox is checked.

4. Download the project to the controller.

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:

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

• For high-frequency messaging, utilize connected cached messages

• Utilize message reads as opposed to message writes; they’re more efficient

• For ControlLogix 5580 controllers, route HMI/messages through communication modules in the chassis as opposed to going directly to the embedded port of the controller
  • Offloading some of the processing to the communications module results in greater messaging capacity than using the front port alone
  • This recommendation does not apply to I/O or produce/consume data, it is more efficient and there is more capacity for that data to route through the embedded port of the controller
• Upgrade to a 5590 controller
  • The HMI/messaging messaging capacity is doubled through the embedded ethernet port

For more information, see these publications:

• ControlLogix and GuardLogix Controller Specifications Technical Data, publication 1756-TD001

• CompactLogix 5380, Compact GuardLogix 5380, and CompactLogix 5480 Controllers Specifications Technical Data, publication 5069-TD002

• 1756 ControlLogix Communication Modules Specifications Technical Data, publication 1756-TD003

PXRQ Instruction Can Cause a Controller MNRF/Assert

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.