Release Notes

ControlLogix Type: GuardLogix
Version 28.012 (released 5/2016)

Catalog Number 1756-L73S (series B)

These release notes describe version information for 1756-L73S, version 28.012 (released 5/2016).

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.

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

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.016, 34.011 and later
Compact GuardLogix® 5370
28.011
33.016, 34.011 and later
ControlLogix® 5570
20.011
33.016, 34.011 and later
ControlLogix 5570 redundant
20.054
33.053, 34.051 and later
GuardLogix 5570
20.011
33.016, 34.011 and later
CompactLogix 5380
28.011
32.016, 33.011 and later
Compact GuardLogix 5380 SIL 2
31.011
32.016, 33.011 and later
Compact GuardLogix 5380 SIL 3
32.013
32.016, 33.011 and later
CompactLogix 5480
32.011
32.016, 33.011 and later
ControlLogix 5580
28.011
32.016, 33.011 and later
GuardLogix 5580
31.011
32.016, 33.011 and later


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)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.013, 34.011 and later
Compact GuardLogix® 5370
28.011
33.013, 34.011 and later
ControlLogix® 5570
20.011
33.013, 34.011 and later
GuardLogix 5570
20.011
33.013, 34.011 and later
ControlLogix 5570 redundant
20.054
33.052, 34.051 and later


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.

  

CVE-2020-6998: Denial-of-Service Vulnerability That Affects Logix 5000™ Controllers (00228528)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011 and later
Compact GuardLogix® 5370
28.011
33.011 and later
ControlLogix® 5570
20.011
33.011 and later
GuardLogix 5570
20.011
33.011 and later
ControlLogix 5570 redundant
20.054
33.051 and later


For a full list of the potentially affected Rockwell Automation products and a description of the vulnerability, see Knowledgebase Product Notice CompactLogix 5370 and ControlLogix 5570 Controllers Vulnerable to Denial of Service Conditions due to Improper Input Validation.


  

Corrected Anomalies in This Release

This release corrects the following anomalies.

Larger Than Expected Increase in the Base Memory Size of an Empty Application Program (Lgx00177148)

Corrected Anomaly with Firmware Revision 28.012

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:

A blank controller project that uses this firmware revision had a larger memory size than expected when compared to previous firmware revisions. The base memory size of an empty application program grew more than expected in 28.011 firmware. This increase was 17.4 Kb. The increase was reduced to 0.5 Kb.

Download Fails With an Attribute Error When Using CIP Based Motion Drives

Lgx00179529 and Lgx00179817

Corrected Anomaly with Firmware Revision V28.012

Catalog Numbers:

Known with Firmware Revisions

Catalog Numbers:


For CIP based motion drives that support dual connections:

graphic

If a safety signature has been applied to the safety controller and a download is attempted the download will fail with the following errors:

graphic




  

Known Anomalies in This Release

This release has the following known anomalies.

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.



Known Anomalies from Previous Releases

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

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:

 

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.

PI Function Block (Lgx00070832)

Known Anomaly First Identified as of:

 

The PI Function block appears to stop executing as the output does not change and instruction faults are logged.

If the PI instruction is being used in Linear mode, this floating-point equation is used to calculate the ITerm.

graphic

Due to the use of the single-precision floating point values, it may be possible, depending on the values of WLD and KP, for the ITerm value to be small enough, less than 0.0000001, to be lost when adding to the ITermn-1.

For more information regarding the PI instruction, see the Logix5000™ Controllers Advanced Process Control and Drives Instructions User Manual, publication 1756-RM006.

 

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.

 

Motion Run Axis Tuning Instruction Gets Stuck (00172234)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:


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



ConfigUpdateInProcess Bit Does Not Change State When Issuing an SSV Instruction to Change the Value of the Conversion Constant (00230152, 00228464, 880625, 1594437)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011 and later
Compact GuardLogix® 5370
28.011
33.011 and later
ControlLogix® 5570
20.011
33.011 and later
GuardLogix 5570
20.011
33.011 and later
CompactLogix 5380
28.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 2
31.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 3
32.013
32.016, 33.011 and later
CompactLogix 5480
32.011
32.016, 33.011 and later
ControlLogix 5580
28.011
31.013, 32.016, 33.011 and later
GuardLogix 5580
31.011
31.013, 32.016, 33.011 and later


The Configuration Update Status Bits attribute provides a method for monitoring the progress of one or more specific module configuration attribute updates initiated by either a Set Attribute List service or an SSV in the user program. As soon as such an update is initiated, the controller sets the ConfigurationUpdateInProcess bit. The bit remains set until the Set Attribute List reply comes back from the servo module indicating that the update process was successful. Thus, the Configuration Update Status Bits attribute provides a method of waiting until the servo configuration data update to the connected motion module is complete before starting a dependent operation.

MAM Instruction With Merge Enabled (Lgx00078822)

Known Anomaly First Identified as of

Catalog numbers:


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/seconds3) than the original MAM instruction. You should note, though, lower value of jerk in % of time results in higher value of jerk (in units/seconds3).

 

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:

 

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:

 

  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:


Corrected: Logix Firmware 20.014 for only

● 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
● 1756-L71, 1756-L72, 1756-L73, 1756-L73XT, 1756-L74, 1756-L75


Absolute Immediate or Passive Home (Lgx00135080, Lgx00134716)

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



Prior to RSLogix 5000 software, version 19.00.00, you could perform either an absolute immediate (SERCOS only) or a passive home with the drive in a safe off state. In RSLogix 5000 software, version 20.00.00, that feature was inadvertently changed to be blocked and generates the error 16#0028 'You are trying to run a motion command when the drive is locally disabled'.
 

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

 

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


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.

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

  

Safety Fault if GuardLogix Controller Not CST Master (Lgx00104194)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers


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.

Alarm Log Content Lost at Powerup (Lgx00138163)

Known Anomaly First Identified as of Firmware Revision 24.011

Catalog Numbers:

 

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:

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.

Incorrect Execution Schedule for Scheduled Output Module (Lgx00157174)

Known Anomaly First Identified as of Firmware Revision 24.011

Catalog Numbers:


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


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:

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:

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

Axis Schedule Changes After Project Import and Download (00169297)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:


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.


Drive Instability With Frequent Wall Clock Time Update Requests (00174495, 00174563)

Corrected Anomaly in Firmware Revision 30.011

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:

Frequent requests to update the controller Wall Clock Time in applications that use Integrated Motion over an EtherNet/IP network can cause drive instability.

The following are examples of wall clock time update requests:


The following are examples of drive behavior when the anomaly occurs:




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

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
Compact GuardLogix® 5370
28.011
37.011 and later
Compact GuardLogix® 5380 SIL 2
31.011
37.011 and later
Compact GuardLogix 5380 SIL 3
32.013
37.011 and later
GuardLogix 5560
17.008
—
GuardLogix 5570
20.011
37.011 and later
GuardLogix 5580
31.011
37.011 and later

The TSSM Muting Lamp (ML) output is enabled when Sensor 2 input transitions instead of waiting the configured TSSM S1S2-LC Min time.

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


Controller Can Assert When Motion Instruction Accel And/Or Decel Operands Are Out of Range (3341103, 3453889)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
37.011 and later
Compact GuardLogix® 5370
28.011
37.011 and later
ControlLogix® 5570
20.011
37.011 and later
GuardLogix 5570
20.011
37.011 and later
CompactLogix 5380
29.011
37.011 and later
Compact GuardLogix 5380 SIL 2
31.011
37.011 and later
Compact GuardLogix 5380 SIL 3
32.013
37.011 and later
CompactLogix 5380 Process
33.011
37.011 and later
CompactLogix 5480
32.011
37.011 and later
ControlLogix 5580
28.011
37.011 and later
GuardLogix 5580
31.011
37.011 and later
ControlLogix 5580 Process
33.011
37.011 and later

When MAM, MAJ, MCD, MAG and MAS instruction Accel and/or Decel operands are near zero, a controller assert can occur.

For more information, see Knowledgebase Article Studio 5000 Motion Instruction Error Code 13 Accel and Decel out-of-range limits.


Attribute Value Incorrect with Get System Value Instruction (00169204)

Corrected Anomaly as of Firmware Revision 30.011

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

                                     

When used with a Get System Value (GSV) instruction, the PortPhysicalAddressInfo attribute value can be incorrect.

The PortPhysicalAddressInfo attribute is available when you use the TimeSynchronize Class.



Attribute Values Incorrect with Set System Value Instruction (00169713)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

                                                    

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:


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:


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:


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



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

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:


The media space calculation that is done to determine the available memory on a Secure Digital (SD) card can be incorrect with 3rd-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:


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.



Incorrect Firmware Saved to Secure Digital Card (00178137)

Corrected Anomaly with Firmware Revision 29.011

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:


When the Firmware Supervisor is used to save the firmware of two 1756-EN2T EtherNet/IP communication modules to a Secure Digital (SD) card, incorrect firmware can be saved on the SD card.



Wall Clock Time Incorrect After Controller Reset (00177851)

Corrected Anomaly with Firmware Revision 29.011

updated to reflect Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:


After the controller is reset, the wall clock time can be set to the incorrect time.



Events in Sequence Missed (00176328)

Corrected Anomaly as of Firmware Revision 29.011

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:


When a controller executes alarms, the controller can miss some events from a sequence of events.




Set System Variable Instruction Does Not Update Attribute While Online (00177665)

Corrected Anomaly with Firmware Revision 29.011

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:


Attempts to update the TimeZoneString attribute value can fail. The failure occurs if the update attempt is performed via a Set System Variable (SSV) instruction that uses the INT data type.

  

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 revision is previous to revision 28, for example, firmware revision 26.


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:

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:
  

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.



  

A Program’s First Scan May Not Occur if the Program is Uninhibited (00190610, 00190512)

Corrected Anomaly in Firmware Revision 31.011

Known Anomaly First Identified in Firmware Revision 19.013

Catalog Numbers:

If a program is inhibited, and then uninhibited, then a small timing window could occur where the S:FS first scan bit is reset before the program is truly first scanned.


AxisHomedStatus Bit Gets Set To Zero When Inhibiting the Axis (00199162, 00217021)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 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 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.013 for these catalog numbers:

If the AxisHomedStatus bit is already established on a CIP™ drive, issuing an SSV to inhibit the axis resets the AxisHomedStatus bit to zero.

Velocity Scaling Not Performed Before SLAT Setpoint Sent to Drive (00218527, 00200340)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

The controller does not perform velocity scaling before it sends the Speed Limited Adjustable Torque (SLAT) setpoint to a drive.

Firmware Supervisor Does Not Update Kinetix 5700 2198-D032-ERS4 Drive Firmware (00218796)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

If Firmware Supervisor tries to update the firmware on a Kinetix® 5700 2198-D032-ERS4 Drive, the Studio 5000 Logix Designer® Application can report a module fault: “(Code 16#fe11) Automated Firmware Update Failed: Firmware file invalid.”

Workaround: To update the firmware, use ControlFLASH™ or ControlFLASH Plus™ software.

Connected Cached Messages Do Not Time Out after Repeated Connection Requests (00206909, 217264)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

CORRECTED Anomaly with Firmware Revision 33.051 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.054 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

The connection for connected cached messages does not time out after the max number of retries for the connected request is attempted.


MAOC Drifting Errors (00211178, 00218822)

CORRECTED Anomaly with Firmware Revision 33.011

Known Anomaly First Identified as of Firmware Revision 20.011 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 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.013 for these catalog numbers:

Motion Arm Output Cam (MAOC) planner’s output can diverge from master axis position over time. For more information, see Knowledgebase article MAOC Drifting Errors.

Controller Does Not Transition to Run Mode after Online Edit of PowerFlex Drive Parameters (00219408)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

CORRECTED Anomaly with Firmware Revision 33.051 for these catalog numbers:

CORRECTED Anomaly with Firmware Revision 32.012 and 33.011 for these catalog numbers:

CORRECTED Anomaly with Firmware Revision 31.013, 32.012, and 33.011 for these catalog numbers:

CORRECTED Anomaly as of Firmware Revision 30.015, 31.013, 32.012, and 33.011 for these Catalog Numbers:

CompactLogix 5380 Controllers Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.054 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 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:



If you edit a PowerFlex® drive parameter online in Program mode, the controller does not transition to run mode when you change from Program mode to run mode. This can occur when you use the 20-750-ENETR PowerFlex 755 dual-port Ethernet communication module.


MCLM/MCCM Set to Merge All Can Cause Controller MNRF (00220553, 00219873)

CORRECTED Anomaly with Firmware Revision 30.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 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 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.013 for these catalog numbers:

The controller can experience a major non-recoverable fault (MNRF) due to the following:

  1. Motion Coordinated Linear Move (MCLM) / Motion Coordinated Circular Move (MCCM) is decelerating.
  2. Merge All is activated.
  3. Merging is happening in the last Coarse Update Period of the MCLM/MCCM being merged.

Using Compare Instruction with String Data Types (00223326, 00223030,0226535)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011
Compact GuardLogix® 5370
28.011
33.011
ControlLogix® 5570
20.011
33.011
ControlLogix 5570 redundant
20.054
33.051
GuardLogix 5570
20.011
33.011
CompactLogix 5380
28.011
33.011
Compact GuardLogix 5380 SIL 2
31.011
33.011
Compact GuardLogix 5380 SIL 3
32.013
33.011
CompactLogix 5480
32.011
33.011
ControlLogix 5580
28.011
33.011
GuardLogix 5580
31.011
33.011


If compare instructions (EQU, GEQ, GRT, LEQ, LES, NEQ) are used with string data types and the length of the string is negative, it can result in the controller experiencing these faults:


For more information, see Knowledgebase Technote Using compare instructions with string data types can cause task watchdog faults or controller asserts.
  

Nested SFC with Selection Branch Execution on First Transition May Be Incorrect (00227908, 00225009, 880618, 1594431)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011 and later
Compact GuardLogix® 5370
28.011
33.011 and later
ControlLogix® 5570
20.011
33.011 and later
ControlLogix 5570 redundant
20.054
33.051 and later
GuardLogix 5570
20.011
33.011 and later
CompactLogix 5380
28.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 2
31.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 3
32.013
32.016, 33.011 and later
CompactLogix 5480
32.011
32.016, 33.011 and later
ControlLogix 5580
28.011
31.013, 32.016, 33.011 and later
GuardLogix 5580
31.011
31.013, 32.016, 33.011 and later


Under the following conditions, a sequential function chart (SFC) selection branch will not execute correctly.

  1. The selection branch is in a nested SFC.
  2. SFCs are configured for the following:
  1. SFR instruction is used to reset the main SFC to the initial step.

Under these conditions, if an SFC is reset while evaluating parallel transitions, the chart may remember that one transition from before the reset was true. If another transition is true after the execution path reaches that select divergence again, the chart could still remember the transition from before the reset and choose the incorrect execution path.

After Power Cycling, The Controller SFC Routines Do Not Execute Properly (00229202, 00229027, 926153, 1594432)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011 and later
Compact GuardLogix® 5370
28.011
33.011 and later
ControlLogix® 5570
20.011
33.011 and later
ControlLogix 5570 redundant
20.054
33.051 and later
GuardLogix 5570
20.011
33.011 and later
CompactLogix 5380
28.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 2
31.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 3
32.013
32.016, 33.011 and later
CompactLogix 5480
32.011
32.016, 33.011 and later
ControlLogix 5580
28.011
31.013, 32.016, 33.011 and later
GuardLogix 5580
31.011
31.013, 32.016, 33.011 and later


Following a power cycle, if the application program includes an SFC with a simultaneous branch, the possibility exists for one or more steps on that simultaneous branch not to execute. This anomaly does not occur on every power cycle.

See Knowledgebase Technote Unexplained Sequential Function Chart (SFC) simultaneous branch execution.

Unexpected command sent to phase when connection is lost to Logix Designer (00224198)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

CORRECTED Anomaly with Firmware Revision 33.051 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.054 for these catalog numbers: 

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

The Equipment Phase has a property called ‘External Sequencer Loss of Communication Command’. This setting specifies the command to send to the phase when it is attached to by an external sequencer and the communication with the external sequencer is lost.

The options for this configuration are:
     - None (continue in its current state)
     - Hold
     - Stop
     - Abort

The anomaly occurs when Logix Designer has an override attach to the equipment phase and the connection is lost to Logix Designer. The anomaly is that the phase is sent the command specified in the ‘External Sequencer Loss of Communication Command’ property. What should happen is no command should be sent—only the override should be cleared. The configured command should only be sent when there is an External Sequencer (FTBatch) attached.

Execution of a MAS Instruction results in error 104 (00213035)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

Under the following specific sequence of events the execution of the MAS instruction could result in error 104. The sequence of events is as follows:

  1. Interruption of an S-Curve MAM instruction with an MAS instruction of type move.
  2. Interruption of the MAS instruction with an MSF instruction.
  3. Interrupting the MAM instruction again with the same MAS instruction.

  

Consumed axis actual position exceeds the produced axis unwind position (00225674, 00223851)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 21.011 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 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.013 for these catalog numbers:

The consume axis can reach positions beyond the unwind value. This is something that can occur depending on the CUP (Course Update Period) of the Motion Group and the produced axis speed.

The consumed axis is configured for linear, but it applies the unwind value that the consumer gets from the producing axis. Depending on the execution schedule, the unwind value could be applied after the controller tag for the axis position has been updated.

Refer to Knowledgebase article Consumed axis is reaching positions beyond the unwind value.

Homing an axis introduces a spike in the Actual Velocity attribute (00225946, 00223672)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified in these controllers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.013 for these catalog numbers:

While homing to the limit switch, you see a large spike on the axis’ ActualVelocity attribute. The drive position and velocity feedback do not reflect the spike noticed on the ActualVelocity attribute of the controller. They stay consistent with the expected behavior.

CIP Motion Axis Feedback 1 and 2 length incorrectly converted by the controller (00218528, 00218407)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 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 31.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 32.013 for these catalog numbers:

CIP Motion Axis attribute 1419 Feedback 1 Length and 1469 Feedback 2 Length are converted from float to integer by the controller before being sent to the drive. The conversion is unexpected and causes the value in the drive to become incorrect.

  

Axis Stuck In Synchronizing State When SSV And Inhibiting Axis On The Same Module (00229573, 00225308)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:


Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

When continually executing multiple SSV instructions to change drive attributes on axis A and inhibiting axis B on the same module, axis A and other axes on the same module become stuck in the synchronizing state and never go to pre-charge/stopped state. You must re-download the project to recover.



Online Editing of PowerFlex Drives (00227003, 1594434)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011 and later
Compact GuardLogix® 5370
28.011
33.011 and later
ControlLogix® 5570
20.011
33.011 and later
ControlLogix 5570 redundant
20.054
33.051 and later
GuardLogix 5570
20.011
33.011 and later
CompactLogix 5380
28.011
30.015, 31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 2
31.011
31.013, 32.016, 33.011 and later
Compact GuardLogix 5380 SIL 3
32.013
32.016, 33.011 and later
CompactLogix 5480
32.011
32.016, 33.011 and later
ControlLogix 5580
28.011
30.015, 31.013, 32.016, 33.011 and later
GuardLogix 5580
31.011
31.013, 32.016, 33.011 and later


See Knowledgebase Technote Product Notice 2019-01-001 Revision C - Online Editing of PowerFlex Low and Medium Voltage Drives (201901001).

IMPORTANT: You must use a CORRECTED controller firmware revision (listed above) in conjunction with Drives AOP 5.007 or greater; a CORRECTED controller firmware revision alone will not address the anomaly described in the product notice.

Some Safety faults are not logged in the Controller Log (00213448, 00222776, 00223323)

CORRECTED Anomaly with

Known Anomaly First Identified in

The Controller Log feature does not properly log some Safety faults in the Controller Log. This does not affect the controller’s ability to detect and react to Safety faults. The Controller Log feature detects and logs changes made to Logix 5000™ controllers without adding any auditing software. For more information about the Controller Log feature, refer to Logix 5000 Controllers Information and Status Programming Manual, publication 1756-PM015.

  

SRT (Sort) instruction with a large length can cause the controller to MNRF (00227157)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

CORRECTED Anomaly with Firmware Revision 33.051 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.054 for these catalog numbers: 

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

When the SRT (Sort) instruction is executed, it can result in a controller major non-recoverable fault (MNRF). This can occur when the SRT is performed in an array with a large length, typically over 120 elements.

  

Dual Feedback Position Error Jumps (00232347, 00232504)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011
Compact GuardLogix® 5370
28.011
34.011
ControlLogix® 5570
20.011
34.011
GuardLogix 5570
20.011
34.011
CompactLogix 5380
28.011
33.011
Compact GuardLogix 5380 SIL 2
31.011
33.011
Compact GuardLogix 5380 SIL 3
32.013
33.011
CompactLogix 5480
32.011
33.011
ControlLogix 5580
28.011
33.011
GuardLogix 5580
31.011
33.011


When the following configuration or conditions are met:

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


  

Firmware Supervisor fails with “(Code 16#fe11) Automated Firmware Update Failed: Firmware file invalid.” (00206938)

CORRECTED Anomaly with Firmware Revision 33.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:

Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:

If Firmware Supervisor tries to update the firmware on a 1734-AENTR module, for example, the Studio 5000 Logix Designer® Application can report a module fault: “(Code 16#fe11) Automated Firmware Update Failed: Firmware file invalid.”

Workaround: To update the firmware, use ControlFLASH™ or ControlFLASH Plus™ software.

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

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.016, 34.011 and later
Compact GuardLogix® 5370
28.011
33.016, 34.011 and later
ControlLogix® 5570
20.011
33.016, 34.011 and later
ControlLogix 5570 redundant
20.054
33.053, 34.051 and later
GuardLogix 5570
20.011
33.016, 34.011 and later


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)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011
Compact GuardLogix® 5370
28.011
34.011
ControlLogix® 5570
20.011
34.011
ControlLogix 5570 redundant
20.054
34.051
GuardLogix 5570
28.011
34.011
CompactLogix 5380
28.011
34.011
Compact GuardLogix 5380 SIL 2
31.011
34.011
Compact GuardLogix 5380 SIL 3
32.013
34.011
CompactLogix 5380 Process
33.011
34.011
CompactLogix 5480
32.011
34.011
ControlLogix 5580
28.011
34.011
GuardLogix 5580
31.011
34.011
ControlLogix 5580 Process
33.011
34.011


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)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011
Compact GuardLogix® 5370
28.011
34.011
ControlLogix® 5570
20.011
34.011
ControlLogix 5570 redundant
20.054
34.051
GuardLogix 5570
28.011
34.011
CompactLogix 5380
28.011
33.011
Compact GuardLogix 5380 SIL 2
31.011
33.011
Compact GuardLogix 5380 SIL 3
32.013
33.011
CompactLogix 5480
32.011
33.011
ControlLogix 5580
28.011
33.011
GuardLogix 5580
31.011
33.011


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)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011
Compact GuardLogix® 5370
28.011
34.011
ControlLogix® 5570
20.011
34.011
GuardLogix 5570
28.011
34.011
CompactLogix 5380
28.011
34.011
Compact GuardLogix 5380 SIL 2
31.011
34.011
Compact GuardLogix 5380 SIL 3
32.011
34.011
CompactLogix 5380 Process
33.011
34.011
CompactLogix 5480
32.011
34.011
ControlLogix 5580
28.011
34.011
GuardLogix 5580
31.011
34.011
ControlLogix 5580 Process
33.011
34.011


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)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011
Compact GuardLogix® 5370
28.011
34.011
ControlLogix® 5570
20.011
34.011
ControlLogix 5570 redundant
20.054
34.051
GuardLogix 5570
20.011
34.011


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.



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

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
28.011
36.011 and later
Compact GuardLogix® 5370
28.011
36.011 and later
ControlLogix® 5570
28.011
36.011 and later
GuardLogix 5570
28.011
36.011 and later


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)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
28.011
36.011 and later
Compact GuardLogix® 5370
28.011
36.011 and later
ControlLogix® 5570
28.011
36.011 and later
GuardLogix 5570
28.011
36.011 and later


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


  

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

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011 and later
Compact GuardLogix® 5370
28.011
34.011 and later
ControlLogix® 5570
19.011
34.011 and later
GuardLogix 5570
20.011
34.011 and later
CompactLogix 5380
28.011
34.011 and later
CompactLogix 5380 process
33.011
34.011 and later
Compact GuardLogix 5380 SIL 2
31.011
34.011 and later
Compact GuardLogix 5380 SIL 3
32.013
34.011 and later
CompactLogix 5480
32.011
34.011 and later
ControlLogix 5580
28.011
34.011 and later
ControlLogix 5580 process
33.011
34.011 and later
GuardLogix 5580
31.011
34.011 and later


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.


Application Notes

This release has the following application notes.

Firmware Upgrade Guidelines for Safety Controllers

This application note applies to all firmware revisions of:

The IEC 61508 functional safety standard requires impact analysis before upgrading or modifying components in a certified, functional safety system. This release note provides high-level guidance on how you can perform the impact analysis for safety controller hardware/firmware upgrades. Reference the standard to make sure you fulfill all of the requirements as they relate to your application.
When you upgrade controller firmware to a newer version, consider the following:
For more controller-specific information, see one of the following:
Important: The 5580/5380 controllers have a different compiler than earlier controllers. You must revalidate that applications on earlier controllers compile correctly on 5580/5380 controllers.
For product change management guidelines and definitions of how Rockwell Automation manages product versions, see System Security Design Guidelines Reference Manual, SECURE-RM001.

For Example:
  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.
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 © 2024 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.