Denial-of-Service Vulnerability That Affects Logix 5000™ Controllers (1042476,1042479)

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.

CVE-2022-3157: Denial-of-Service Vulnerability That Affects Logix 5000™ Controllers (1256258, 1289747)

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

Dual Feedback Position Error Jumps (00232347, 00232504)

When the following configuration or conditions are met:

• Dual feedback.
• Feedback 2 is a linear device.
• Linear load type. Direct coupled linear or linear actuator.

Anytime the axis moves past one meter, the position command jumps by 1000 or 39.37 depending on the configured motion units.

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.

Some Faults Are Not Logged in The Controller Log (1061142, 1594647)

The Controller Log feature does not properly log User Task Watchdog faults (Type 6 Code 1) in the Controller Log. For more information about the Controller Log feature, see the Logix 5000® Controllers Information and Status Programming Manual, publication 1756-PM015.

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”

Controller Can Assert During The I/O Module Configuration Process (1024030, 00219969)

Certain I/O modules send more configuration data than fits in a standard forward open (508 bytes) when the connection is being established.  Therefore, the configuration process can take longer to complete. Examples include E300™ Electronic Overload Relays, 1444 Dynamics, 1718 I/O, 1719 I/O, and many third-party I/O devices.

When the configuration data is being sent to the device, if you change the configuration through the Add-on Profile for the device and then apply the changes the controller can assert.

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.

Grandmaster Clock Description Not Correctly Being Displayed (939979)

Located in controller properties → Date Time → Advanced → Grandmaster Clock description could be shown as a blank description or could be showing old information. This does not impact time synchronization.

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.

Mechanical Brake Delay (Lgx00113541, Lgx00107169)

Anomaly

Logix Firmware/RSLogix 5000™ Software 19.011

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L72, 1756-L73, 1756-L74, 1756-L75

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1756-L71, 1756-L72S, 1756-L73S, 1756-L73XT, 1756-L73SXT

Catalog Numbers 1769-L18ERM-BB1B, 1769-L27ERM-QBFC1B, 1769-L30ERM, 1769-L33ERM, 1769-L36ERM

This anomaly occurs only in Integrated Motion on the EtherNet/IP network applications.

When you create a new CIP axis, the default value for Mechanical Brake Delay = 0. If you are using a motor with a brake on this axis and do not change the Mechanical Brake Delay value, the motor will not work properly when you attempt to execute motion.

To work around this anomaly, make sure that you set the Mechanical Brake Delay to the appropriate value before executing motion.

MSF Instruction (Lgx00113540, Lgx00108486)

Known Anomaly First Identified As Of

Catalog Numbers

- 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L72, 1756-L73, 1756-L74, 1756-L75 - Firmware Revision 19.011

- 1756-L71, 1756-L72S, 1756-L73S, 1756-L73XT, 1756-L73SXT - Firmware Revision 20.011

- 1769-L18ERM-BB1B, 1769-L27ERM-QBFC1B, 1769-L30ERM, 1769-L33ERM, 1769-L36ERM - Firmware Revision 20.011

This anomaly occurs only in Integrated Motion on the EtherNet/IP network applications.

Every time there is a Motion Servo Off (MSF) instruction/Motion Servo On (MSO) instruction cycle, the Position Trim value is added to the axis position. This change in axis position causes the axis to move unexpectedly by a distance equal to the Position Trim value.

Absolute Feedback Offset (Lgx00076298)

Known Anomaly First Identified as of:

Catalog Numbers:

• 1756 ControlLogix® L6, Firmware Revision 18.011
• 1756 ControlLogix L7, Firmware Revision 19.011
• 1756 GuardLogix® L6, Firmware Revision 18.011
• 1756 GuardLogix L7, Firmware Revision 20.011

If you issue an Absolute Feedback Offset, it results in a feedback fault. If you issue an Absolute Feedback Offset via an SSV instruction on the 1756-M02AS module, the result is a feedback fault. The feedback fault occurs regardless of whether feedback is on or off.

Alarm Log Content Lost at Powerup (Lgx00138163)

Known Anomaly First Identified as of Firmware Revision 24.011

Catalog Numbers:

• 1756 ControlLogix L7
• 1756 GuardLogix L7
• 5370 CompactLogix L1
• 5370 CompactLogix L2
• 5370 CompactLogix L3

Alarm Log content can be lost if there is a Secure Digital (SD) card in the controller that contains a project that is configured to load the project on powerup.

Controller Appears to Be Stuck in the Transition to Run Mode (Lgx00154875)

Known Anomaly First Identified as of Firmware Revision 24.011 for:

• ControlLogix 5570
• GuardLogix 5570
• CompactLogix 5370

Corrected Anomaly as of Firmware Revision 1.013 for 1732E-OB8M8SR

Known Anomaly First Identified as of Firmware Revision 1.012 for 1732E-OB8M8SR 

If your project uses a 1732E-OB8M8SR module, upgrade the module firmware to firmware revision 1.013 or later.

PI Function Block (Lgx00070832)

Known Anomaly First Identified as of:

• 1756 ControlLogix® L6 Firmware Revision 16
• 1756 ControlLogix L7 Firmware Revision 19
• 1756 GuardLogix L6 Firmware Revision 16
• 1756 GuardLogix® L7 Firmware Revision 19
• 5370 CompactLogix™ L1 Firmware Revision 20
• 5370 CompactLogix L2 Firmware Revision 20
• 5370 CompactLogix L3 Firmware Revision 20
• 1789 SoftLogix™ Firmware Revision 20

Real Time Axis Attribute of VelocityFeedback (Lgx00107793)

Known Anomaly First Identified As Of:

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65 Version 18.011

Catalog Numbers 1756-L72, 1756-L73, 1756-L74, 1756-L75 Version 19.011

Catalog Numbers 1756-L71, 1756-L72S, 1756-L73S, 1756-L73XT, 1756-L73SXT Version 20.011

This anomaly occurs only in SERCOS applications that use Kinetix SERCOS drives and linear motors.

Under certain conditions, it is possible that the Real Time Axis attribute VelocityFeedback contains an incorrect value. The inaccuracy is the result of incorrect scaling of that attribute.

Your program will have an incorrect value for the VelocityFeedback attribute if you follow these steps.

1. While offline, you write your RSLogix 5000 program and, as part of that program, the VelocityFeedback attribute is selected.
2. You save the program and download it to the controller.
3. You go online.

The VelocityFeedback attribute value is incorrect because that attribute was enabled before the program was saved, downloaded, and put online.

To work around this anomaly, do not enable the VelocityFeedback attribute until the RSLogix 5000 program is online.

Axis Schedule Changes After Project Import and Download (00169297)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• 1756 ControlLogix^® L7
• 1756 GuardLogix^® L7
• 5370 CompactLogix™ L1 (1769-L18ERM-BB1B only)
• 5370 CompactLogix L2 (1769-L27ERM-QBFC1B only)
• 5370 CompactLogix L3 (1769-L30ERM, 1769-L33ERM, 1769-L36ERM only)

An axis schedule can change when you import a Studio 5000 Logix Designer^® application, versions 24 and 26, project into Logix Designer application, version 27.

MAM Instruction With Merge Enabled (Lgx00078822)

Known Anomaly First Identified as of

Catalog numbers:

• 1756 ControlLogix® L6 Firmware Revision 17.004
• 1756 ControlLogix L7 Firmware Revision 19.011
• 1756 GuardLogix L6 Firmware Revision 17.008
• 1756 GuardLogix® L7 Firmware Revision 20.011
• 5370 CompactLogix™ L1 (1769-L18ERM-BB1B only) Firmware Revision 20.011
• 5370 CompactLogix L2 (1769-L27ERM-QBFC1B only) Firmware Revision 20.011
• 5370 CompactLogix L3 (1769-L30ERM, 1769-L33ERM, 1756-L36ERM only) Firmware Revision 20.011

Under some rare occurrences, if a Motion Axis Move (MAM) instruction with Merge Enabled is activated during the deceleration segment of an active MAM instruction then the new MAM instruction may overshoot its programmed endpoint. The occurrence of the overshoot depends on the following factors:

•The original MAM instruction's remaining travel distance at the time of the merge and the new MAM instruction's remaining travel distance

•The relationship of the decel jerk of the new MAM instruction to the decel jerk of the original MAM instruction

•If the original MAM instruction is decelerating

Typically, the overshoot does not occur. If either of the following conditions exist, you will avoid the overshoot:

•The new MAM instruction is programmed with Merge Disabled. If there is no other motion active at the time of the merge, then the Merge Disable results in the same operation as the Merge Enable.

•The new MAM instruction has a slightly higher jerk (in units/seconds³) than the original MAM instruction. You should note, though, lower value of jerk in % of time results in higher value of jerk (in units/seconds³).

Safety Tag With Multicast Consuming Controllers (Lgx00104877)

Known Anomaly First Identified As Of:

Catalog Numbers

- 1756 GuardLogix® L6 Firmware Revision 18.011

- 1756 ControlLogix® L7 Firmware Revision 20.011

The use of a safety tag with several multicast consuming controllers at varying firmware revisions can result in a connection timeout.

If your application is configured with GuardLogix controllers consuming safety tags produced by a GuardLogix controller at revision 18.x, and the consuming controllers of one safety tag are at varying firmware revisions you may experience a connection timeout with error code 0x203. In the event of a connection timeout, all of the consuming controllers appear to connect to the tag and run for some time, but then the connection timeout occurs.

If you use a single consumer of a safety tag, that consumer will connect and remain connected.

To workaround this anomaly, set the revision of the producing controller to the same revision as the lowest revision of the consumers connecting to the safety tag. For example, if you have consuming GuardLogix controllers at revisions 17.x and 18.x, set the producing controller to revision 17.x to match the lowest revision of the consumers.

Accept Edits (Lgx00122528, Lgx00122622)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

• 1756 ControlLogix® L6
• 1756 ControlLogix L7
• 1756 GuardLogix L6
• 1756 GuardLogix® L7
• 5370 CompactLogix™ L1
• 5370 CompactLogix L2
• 5370 CompactLogix L3

When you accept edits in LD, ST, and FBD, the controller will log an 'Online Edit' entry in the controller log. Accepting edits in a SFC routine is done by performing a partial import, resulting in a 'Transaction Commit' entry in the controller log. This is confusing because you can select to mask both entries separately. Selecting only Online edits would cause the Audit Value to change only when FBD, ST, and LD edits are made. SFC online edits would change the Audit Value only if the 'Partial Import Online Transaction Completed' bit was set.

Arithmetic State Flags (Lgx00122480)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

• 1756 ControlLogix® L6
• 1756 ControlLogix L7
• 1756 GuardLogix® L6
• 1756 GuardLogix L7
• 5370 CompactLogix™ L1
• 5370 CompactLogix L2
• 5370 CompactLogix L3

1. When dealing with Floating point numbers, the controller does not truncate denormalized values or -0.0… 0.0.
2. For an integer divide, when the denominator is 0, the S:N and S:Z are not set.
3. For the MOD instruction, the S:V is not set if an overflow occurred during the calculation.

Logix CPU Security Tool

Known Anomaly First Identified as of Firmware Revision 20.011

RSLogix 5000™ Version 20.00

Studio 5000 Logix Designer™ First Identified as of Version 21.00

Catalog numbers:

• 1756 ControlLogix® L6
• 1756 ControlLogix L7
• 1756 GuardLogix L6
• 1756 GuardLogix® L7
• 5370 CompactLogix™ L1
• 5370 CompactLogix L2
• 5370 CompactLogix L3
• 1789 SoftLogix™

Anomaly

Logix Firmware/RSLogix 5000 Software 20.013, 21.011

Catalog Numbers:

● 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65

● 1756-L61S, 1756-L62S, 1756-L63S

● 1756-L71, 1756-L72, 1756-L73, 1756-L73XT, 1756-L74, 1756-L75

● 1756-L71S, 1756-L72S, 1756-L73S, 1756-L73SXT

Attribute Values Incorrect with Set System Value Instruction (00169713)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

When you use a Set System Variable (SSV) instruction to set the values for attributes available with the WallClockTime class, the values can be set incorrectly.

Wall Clock Value Different From Previous Value (00169756)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

After you set the wall clock for a controller, the actual time can be offset from the value that you set by approximately 2 seconds.

This anomaly occurs after Precision Time Protocol (PTP) is disabled in a controller that was previously synchronized with the grandmaster clock.

Cannot Save Firmware to Secure Digital Card (00170011)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers GuardLogix^® 5570

The Load/Store button on the Nonvolatile Memory tab of the Controller Properties dialog can be disabled when the controller is online. As a result, you cannot save firmware to the Secure Digital (SD) card.

Expiration Times On a Logix Repository Record Can Differ (00171229)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

When the Logix Repository deletes a record, the cached value of the earliest expiration time and the actual expiration time value of the record can be different.

Unconnected Timeout Time Incorrect (00171872)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

The unconnected timeout time can be longer for a Forward Open service than expected.

Motion Run Axis Tuning Instruction Gets Stuck (00172234)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

A Motion Run Axis Tuning (MRAT) instruction can get stuck and the .IP (In Process) stays set to 1. This anomaly can occur when the MRAT instruction is used to command a motion module to run a tuning motion profile for an axis, the instruction

Media Space Calculation Incorrect with 3rd-party Secure Digital Cards (00175295)

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

The media space calculation that is done to determine the available memory on a Secure Digital (SD) card can be incorrect with 3^rd-party SD cards that are 4 GB or greater.

This anomaly does not occur when you use SD cards available from Rockwell Automation. That is, the 1784-SD1 and 1784-SD2 cards.

We recommend that you use the SD cards available from Rockwell Automation with your controller.

While other SD cards can be used with the controller, Rockwell Automation has not tested the use of those cards with the controller. If you use an SD card other than those cards that are available from Rockwell Automation, you can experience data corruption or loss.

Motion Instruction Interference Can Prevent Axis From Being Enabled (00175334)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

• Compact GuardLogix^® 5370
• CompactLogix^™ 5370
• ControlLogix^® 5570
• GuardLogix 5570

Intermittent execution of a Motion Group Shutdown Reset (MGSR) instruction and Motion Servo On (MSO) instructions can result in an error on the MSO instruction and failure to enable an axis.

Major Non-recoverable Fault on Safety Controller (00178080)

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers GuardLogix^® 5570

An oscillator diagnostic fault can cause a major non-recoverable fault on the controller. The diagnostic fault occurs as a result of the time that is elapsed between two oscillators is greater than 10%.

GuardLogix is a trademark of Rockwell Automation, Inc.

Safety Controller Can Fault and Incorrectly Enter Program Mode After Power Is Cycled (00172782)

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers GuardLogix^® 5570

After a powerup, the controller can experience a major non-recoverable fault (MNRF) and incorrectly enter Program mode instead of Run mode, as expected.

This anomaly occurs in the following conditions:

• The controller and the safety partner use the same firmware revision.

The revision is previous to revision 28, for example, firmware revision 26.

• The Studio 5000 Logix Designer^® project is saved to the SD card in the controller. The Load/Store parameters are as follows:
  • Load Image: On Powerup
  • Load Mode: Run (remote only)
• The controller and safety partner are updated to firmware revision 28.011.
• The safety partner is replaced by a safety partner that uses a firmware revision other than revision 28.011.
• Power is cycled on the controller.

When the anomaly occurs, the controller experiences a fault of Type 14:Code 07 and the Safety Task is inoperable.

The anomaly resolution varies based on if the project uses a Safety Signature. For example, if a Safety Signature is used, there are two resolution options.

Safety Signature Is Applied to Project

Resolution # 1

1. Clear the fault.
2. Set the key to the desired mode, that is, Remote Run or Run mode.

Resolution # 2

1. Cycle power to the controller again.
2. Controller mode after the power cycle is determined by the mode before the power cycle and does not require user action:

• Controller was in Remote Run mode – Controller stays in Remote Run mode.
• Controller was in Remote Program mode – Controller transitions to Remote Run mode.
• Controller was in Run mode – Controller stays in Run mode.
• Controller was in Program mode – Controller stays in Program mode.

Safety Signature Is Not Applied to Project

Resolution

1. Cycle power to the controller.
2. Controller mode before the power cycle determines the power mode after it:

• Controller was in Remote Run mode – Controller stays in Remote Run mode.
• Controller was in Remote Program mode – Controller transitions to Remote Run mode.
• Controller was in Run mode – Controller stays in Run mode.
• Controller was in Program mode – Controller stays in Program mode.

Safety Fault if GuardLogix Controller Not CST Master (Lgx00104194)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers

• 1756 GuardLogix^® L7

With earlier revisions of GuardLogix controller firmware, we recommended that you set the GuardLogix controller as the Coordinated System Time (CST) master to avoid nonrecoverable safety faults.

If you are using the CIP Sync enhancement with RSLogix™ 5000 software and a GuardLogix controller, we recommend that you configure the GuardLogix controller so that it becomes the CST master. To do so, select Enable Time Synchronization on the Date/Time tab of the Controller Properties dialog box. If you do not configure the GuardLogix controller to become the CST master and your project uses safety tags that are produced, I/O faults can occur when the project is downloaded.

For more information about enabling the GuardLogix controller to become the CST master, see the GuardLogix Controllers User Manual, publication 1756-UM020.

Incorrect Execution Schedule for Scheduled Output Module (Lgx00157174)

Known Anomaly First Identified as of Firmware Revision 24.011

Catalog Numbers:

• 1756 ControlLogix L7
• 1756 GuardLogix L7
• 5370 CompactLogix L1 (1769-L18ERM-BB1B only)
• 5370 CompactLogix L2 (1769-L27ERM-QBFC1B only)
• 5370 CompactLogix L3 (1769-L30ERM, 1769-L33ERM, 1769-L36ERM only)

This anomaly occurs with only 1756-OB16IEFS and 1732-OB8M8SR Scheduled Output modules.

The Scheduled Output module may schedule outputs incorrectly if the Motion Arm Output Cam (MAOC) instruction is enabled before the module’ s connection is in the RUNNING state. The following sequence must occur to observe the anomalous behavior.

1. The MAOC issues a new schedule before the Scheduled Output module connection enters the RUNNING state.
2. A change in system time occurs between the time the new schedule is created and the connection entering the RUNNING state.

To work around this anomaly, update your logic to verify that the scheduled output module is in the RUNNING state before executing the MAOC instruction.

Produce/Consume Communication Can Cause I/O Status Indicators to Blink (Lgx00135976)

Known Anomaly First Identified As Of Version 21.011

Catalog Numbers

• 1756 GuardLogix^® L7

If an application requires produce/consume communication between GuardLogix controllers, the I/O status indicator can blink, giving the indication that an I/O fault is present even though the system is functioning properly.

This status indicator behavior occurs when the following conditions exist:

• A GuardLogix controller is configured to consume data from another GuardLogix controller of a later firmware revision.
• The consuming GuardLogix controller is a 1756-L6xS controller that uses firmware revision 19 or earlier.
• The producing GuardLogix controller is a 1756-L7xS controller.

IMPORTANT: In the conditions described previously, you must have two controller applications-one for the 1756-L6xS controller, that is, the consumer, and one for the 1756-L7xS controller, that is, the producer.

You cannot add a 1756-L7xS controller to a 1756-L6xS controller's RSLogix™ 5000 software project, if the project is version 19 or earlier.

To work around this anomaly, complete one of the following tasks:

• Upgrade the consuming controller to use RSLogix 5000 software, version 20, and firmware revision 20.xxx.
• In the consuming controller's application, add a 1756-L6xS controller to the I/O configuration tree as the producing controller and configure it exactly as you would configure the 1756-L7xS controller.

This workaround causes the I/O status indicator to blink. Despite the blinking status indicator, there is no I/O fault.

Work arounds to consider:

PhaseManager™ and SequenceManager™ Show Different States of Phase in Program Mode (00183769)

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:

• ControlLogix® 5570
• GuardLogix® 5570
• CompactLogix™ 5370
• Compact GuardLogix 5370

If the controller is switched to Program mode while a sequence and phase are running, the phase state changes to idle and displays idle, while the sequence continues to show running. On transition back to Run mode, the sequence displays inactive.

Controller Anomaly with Continuous Task, Indirect Addressing, and CONCAT or DTOS (1442602)

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.

SequenceManager Event Client 2.0 Can Experience Slow Performance When Using the Start Up Recovery Option (1769621)

After downloading a new project, the SequenceManager™ Event Client that started with the Start Up Recovery option should stop attempting to recover events immediately. However, the Event Client can continue to attempt recovery until the maximum number of events has been reached.

Workaround: Start the SequenceManager Event Client with the Start Up Recovery option disabled.

SequenceManager Event Client 2.0 Cannot Reliably Recover Events on Startup of The Service (1766682)

Starting the SequenceManager™ Event Client 2.0 service with the Start Up Recovery option enabled can result in missing data.

TSSM Instruction May Not Function as Documented (3343045, 3343050, 3343083, 3343105)

For additional information, see Knowledgebase Article Unexpected TSSM Instruction Behaviour.

The RunMode state will provide the mode of the Producing controller from within the Consuming tag’s data. The RunMode state does not provide unique values in the Producing tag’s data. To monitor the state of the Producing controller within the Producing controller’s logic, use a Get System Value (GSV), with the Object set to ControllerDevice and the Attribute set to Status.

This application note applies to all firmware revisions of:

• GuardLogix® 5580, GuardLogix 5570, and GuardLogix 5560 controllers
• Compact GuardLogix 5380 and Compact GuardLogix 5370 controllers
• Compact GuardLogix L4 controllers

• All major and minor firmware releases for GuardLogix controller systems are certified for use in safety applications. As part of the certification process, Rockwell Automation tests the safety-related firmware functions (for example the CIP Safety™ communication subsystems, embedded safety instruction execution, and safety-related diagnostic functions). The firmware release notes identify changes to safety-related functions.
• Perform an impact analysis of the planned firmware upgrade.
  • Review of the firmware release notes for changes in safety-related functionality.
  • Review of hardware and firmware compatibility in the Product Compatibility and Download site to identify potential compatibility conflicts.
  • Any modification, enhancement, or adaptation of your validated software must be planned and analyzed for any impact to the functional safety system as described in the ‘Edit Your Safety Application’ section in the safety reference manual for your controller.
• You must remove and regenerate the safety signature as part of the firmware upgrade process. Use the online and offline edit process described in the safety reference manual for your controller.

• GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference Manual, 1756-RM012
• GuardLogix 5570 and Compact GuardLogix 5370 Safety Reference Manual, 1756-RM099
• GuardLogix 5560 and Compact GuardLogix L4 Safety Reference Manual, 1756-RM093

1. From the Product Compatibility and Download Center:
   1. Review all firmware release notes, starting with the original firmware revision through the new firmware revision, to identify any changes that impact the safety-related implementation of the application.
   2. Review hardware and firmware compatibility to identify any restrictions between the original system components and the new system components.
2. Perform a hazard and risk assessment for any changes identified during the impact analysis and determine what additional testing is necessary.
3. Perform the online and offline edit process described in the safety reference manual for your controller. You can restrict the ‘Test the Application’ block to the testing identified by the hazard and risk assessment.