Release Notes

CompactLogix 5370 L3 Controller, 3Mb Memory w/Supercap Backup, 16 Axis CIP Motion, up to 30 1769 I/O expansion modules, 48 Ether
Version 21.011 (released 1/2013)

Catalog Number 1769-L36ERM/1769-L36ERMO (series A)

These release notes describe version information for 1769-L36ERM/1769-L36ERMO, version 21.011 (released 1/2013).

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.

Corrected: Logix Firmware Revision 20.014/21.011

CompactLogix 5370 Controller Major Non-Recoverable Fault (Lgx00129680, Lgx00131989)

Anomaly

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


A major non-recoverable fault (MNRF) can occur in the process of handling forward open requests that are associated with Class 3 messaging.

These Class 3 messaging types can result in this anomaly:

For more information, see Knowledgebase article 547830 - CompactLogix 5370 firmware v20 controller may experience Major Non-Recoverable Fault. 

 

Access Denied dialog box does not appear when users without FactoryTalk Security access attempt to modify Motion Configuration (Lgx00184951)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio Logix Designer v30.00

When a user without Motion: Modify Configuration security credentials attempts to modify the motion configuration, an Access Denied dialog box does not appear.

Denial of Service/Buffer Overflow Vulnerability

Known Anomaly in Logix5000 Programmable Controllers, Firmware Revisions 16-21


A vulnerability exists in the Logix5000™ Programmable Controller product line that, if successfully exploited, can cause a Denial of Service ("DoS") or potentially allow an attacker to alter the operating state of the controller through a buffer overflow.


Risk Mitigations

Customers using affected controllers are encouraged to upgrade to an available firmware version that addresses the associated risk.

For details on affected controllers, recommended firmware revisions, and other risk mitigations, see Knowledgebase ID 970074.

  

VxWorks vulnerabilities that affect Logix 5000™ controllers (00225602, 00225603, 00225605, 00225606, 00225607, 880628, 1000204)

CORRECTED Anomaly firmware revisions 28.015, 32.013, and 33.011 for these catalog numbers:

CORRECTED Anomaly in firmware revisions 32.013 and 33.011 for these catalog numbers:

CORRECTED Anomaly in Firmware Revision 31.013, 32.013, and 33.011 for these catalog numbers:

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

Known Anomaly First Identified in firmware revision 20.011 for these catalog numbers:

Known Anomaly First Identified in firmware revision 28.011 for these catalog numbers:

Known Anomaly First Identified in firmware revision 31.011 for these catalog numbers:

Known Anomaly First Identified in firmware revision 32.011 for these catalog numbers:

For a full list of the potentially affected Rockwell Automation products and a description of the vulnerabilities, see Knowledgebase Technote VxWorks Vulnerabilities affect Programmable Automation Controllers, EtherNet/IP™ Communication Modules, I/O Modules, Kinetix 6500 Servo Drive, High-Frequency RFID Interface Block.



TCP Packet Vulnerability (00231064, 00198804, 00201157)

CORRECTED Anomaly with

Known Anomaly First Identified in

For a full description of this vulnerability, see Rockwell Automation Knowledgebase article CompactLogix / Compact GuardLogix 5370 Denial of Service.

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.


  

Features

This release includes the following system features.

Project Documentation Stored in Controller

System Feature

Firmware Revision/ Software Version 21.011

 

Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


The Logix Designer application, version 21, provides the option to store all of your project documentation, including comments, tag descriptions, and other key descriptors of the project in the controller.
Other project descriptions can be stored online, such as routine descriptions and task descriptions.
Uploading a project now restores all of the original project documentation without having to find the original ACD file.
 

Pre-scan of Add-On Instruction Behavior

System Feature

Firmware Revision/ Software Version 21.011

 

Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


The Pre-scan behavior of Add-On Instructions has been enhanced. This enhancement can affect Pre-scan behavior of Add-On Instructions when indirect addressing is used.
This enhancement can improve the Add-On Instruction initialization behavior when indirect addressing is used.
For more information, see Rockwell Automation Knowledgebase document 481124.

You can access the Rockwell Automation Knowledgebase at: http://www.rockwellautomation.com/rockwellautomation/support/overview.page?

 

HMI Connectivity and Performance Improvements

System Feature

Firmware Revision/ Software Version 21.011

 

Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


HMI communication drivers can perform Rockwell Automation-approved symbolic data reads. Symbolic reads improve the read performance and eliminate errors being returned when the HMI attempts to collect data.

For more information, see the Logix5000™ Data Access Programming Manual, publication 1756-PM020.

 

Extended Tag Properties

System Feature

Firmware Revision/ Software Version 21.011

 

Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


You can use Extended Properties to define additional information about a tag or structure of tags.
The Logix Designer application, version 21 or later, provides the option to specify Engineering Units and Min/Max Values for numeric tags, Engineering Units and state information for Boolean tags.
Extended properties are also available for user defined data types, arrays, or other complex data structures.
 

Module Overlap Fault Behavior

System Feature

Logix Firmware/RSLogix 5000 Software 21.011

Catalog Numbers 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


The local 1769-CompactBus module overlap minor fault behavior has changed. In RSLogix 5000 software, version 20, when a module overlap minor fault was detected one minor fault was logged and no others would be logged again until the minor fault was cleared.

In the Logix Designer application, version 21, all instances of module overlap minor faults are logged, regardless if one has been previously logged. The faults continue to be logged until you clear the faults or the faults no longer exist.

After a connection is establishing to a 1769-CompactBus module, the software does not log any module overlap minor faults for the approximately 30 seconds.

Corrected Anomalies in This Release

This release corrects the following anomalies.

Corrected: Logix Firmware/Studio 5000 Software 21.011

Buffer Timeout for FactoryTalk Alarms and Events Subscribers (Lgx00069461)

Anomaly

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65 Revision18.011

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

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

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM

Catalog Numbers 1789-L10, 1789-L30, 1789-L60
 

Changes made to the Buffer Timeout value for FactoryTalk® Alarm subscribers do not take effect until the existing buffer has been deleted.

The FactoryTalk alarm buffer (stored in Logix controller memory) is designed to persist through power cycles. If you change the Buffer Timeout value (via the Communication Setup dialog in FactoryTalk View SE), the controller does not use the new timeout value until the existing buffer is deleted and then recreated. To force recreation of this buffer, you can either:

 

Corrected: Logix Firmware/Studio 5000 Software 21.011

Automatic Device Configuration (Lgx00129012, Lgx00129165)

Known Anomaly First Identified as of Firmware Revision 20.012

Catalog Numbers:


When using the Automatic Device Configuration (ADC) feature, the Logix controller ‘owns’ the configuration in the drive. Do not use the HIM or other external tools, such as DriveExplorer™ software, to change drive parameters. Doing so may cause a sequence of events to occur that results in the connection between the controller and the drive to be dropped, and causes the controller to not be able to re-establish the connection.

Consider using the Write Mask function (drive Parameter 888 - [Write Mask Cfg]) to prevent tools connected to ports other than the Embedded EtherNet/IP port from writing to the drive.
 

Corrected: Logix Firmware/Studio 5000 Software 21.011

MinDurationPRE and MinDurationACC Members (Lgx00119996, Lgx00119981)

Anomaly

Logix Firmware/RSLogix 5000™ Software 20.011

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L72S, 1756-L73, 1756-L73S, 1756-L73XT, 1756-L73SXT, 1756-L74, 1756-L75

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


The MinDurationPRE and MinDurationACC members of ALARM_ANALOG and ALARM_DIGITAL tags are defined as DINT (signed double integer) but they are treated as UDINT (unsigned double integer) by Logix firmware. This causes negative values of the tag members to be handled as large positive numbers when they should be handled as zero.
 

Corrected: Logix Firmware/Studio 5000 Software 21.011

Time-Limited Actions in Steps (Lgx00124697)

Anomaly

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L72S, 1756-L73, 1756-L73S, 1756-L73XT, 1756-L73SXT, 1756-L74, 1756-L75 Version 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33Er, 1769-L33ERM, 1769-L36ERM Version 20.011

Catalog Numbers 1789-L10, 1789-L30, 1789-L60


In SFCs, when using time-limited actions in steps, if the program stays on a given step for greater than 24 days (2**32 ms) the timer’ s accumulator (ACC) will roll over and the action body starts to execute again.

The time-limited action initializes its timer when it starts (step is first scanned). On subsequent scans, it compares the timers PRE and ACC value. If ACC<PRE, the action body will execute. If ACC >=PRE, it is not executed. When the roll over occurs, the ACC,PRE and the action body will again execute when it should not.
 

Corrected: Logix Firmware/Studio 5000 Software 21.011

Active Reconfigure MSG Instructions (Lgx00125204, Lgx00149693)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:


The controller supports only three active reconfigure messages at a time. If more than three are triggered at a time, they will complete (DN bit will go high), but not all the modules will be reconfigured.

For example, if you send five reconfiguration messages at the same time, three reconfigure messages will truly complete (DN bit will go high), and the I/O modules will be reconfigured. The other two reconfigure messages will indicate complete (DN bit will go high), but the I/O modules will not be reconfigured. In this case, the last two should have errored (ER bit), but do not.
 

Corrected: Logix Firmware/Studio 5000 Software 21.011

Launch RSLogix 5000 Software (Lgx00124955)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:


When launching RSLogix 5000™ software, the Log On to FactoryTalk dialog box may be displayed. This dialog box may be seen when you do not have Administrator privileges on the personal computer and the current user does not exist in the FactoryTalk directory. If this dialog box is cancelled, the RSLogix 5000 software will not be launched. When the dialog box is displayed, entering the credentials for a user that has Administrator privileges on the personal computer will then allow RSLogix 5000 software to be launched.

To avoid seeing this dialog box, you can add the current user or user group to the FactoryTalk directory. Follow these steps to add a user or user group to the FactoryTalk directory.
1. Launch the FactoryTalk Administration Console (available from the Start menu).
2. Select the Network directory when prompted.
(You may need to provide credentials for a user with Administrator privileges in order to continue.)
3. To allow access for a particular user, navigate to Network\System\Users and Groups\Users, right-click the Users folder and choose New>Windows Linked User.
4. Click Add and provide the domain\logon name for the desired user.
(You can click Check Names to verify that the name was found.)
5. To allow access for all authenticated users, navigate to Network\System\Users and Groups\User Groups, right-click the User Groups folder and choose New>Windows Linked User Group.
6. Click Add and type the name of the user group, Authenticated Users.
The Log On to FactoryTalk dialog box may also display when using Remote Desktop to connect to the personal computer running RSLogix 5000 software. This is due to FactoryTalk Security not recognizing the computer name. To enable access through Remote Desktop for a specific computer, you should add the name of the computer initiating the Remote Desktop connection to the Network\System\Computers and Groups\Computers folder in the FactoryTalk Administration Console.

To allow all computers to connect, follow these steps.
1. Open the FactoryTalk Administration Console and log in to the Network directory using your domain credentials.
2. Navigate to Network\System\Security Policy. In the Computer Policy Settings section, set Identify terminal server clients using the name of to Server Computer.

Important: If Use single sign-on is set to disable in FactoryTalk software, then the Log On to FactoryTalk dialog box will be displayed each time RSLogix 5000 software is launched and proper user credentials must be entered in order to continue. (By default, ‘ Use single sign-on’ is set to enable .
 

Corrected: Logix Firmware/Studio 5000® Software 21.011

RSLogix 5000 Clock Update Tool

Anomaly

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L72S, 1756-L73, 1756-L73S, 1756-L73XT, 1756-L73SXT, 1756-L74, 1756-L75 Version 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM Version 20.011

Catalog Numbers 1789-L10, 1789-L30, 1789-L60


The RSLogix 5000™ Clock Update tool does not support Windows 7 or Windows Server 2008.
 

RPI Rate  (Lgx00127668, Lgx00128715)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.012

Catalog Numbers 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


A combination of two application conditions may cause the System Task that manages the local CompactBus to stop functioning, resulting in a number of unexpected control system behaviors.

The first application condition includes any of the following:

The second application condition is that you change the RPI rate for one or more Compact I/O modules in the control system via a project download or online change.

When the anomaly occurs, the following events occur:
For example, if the I/O connections over an EtherNet/IP network are controlled via the Continuous Task, they no longer update.
You can correct this anomaly by cycling power to the controller.

 

 

MSG Instruction via CompactBus to 1769-SDN (Lgx00126025, Lgx135673)

Corrected Anomaly as of Firmware Revision 20.014. 21.011

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers  1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


If the controller sends MSG instructions across the CompactBus through a 1769-SDN scanner module to nodes on a DeviceNet network, and a targeted node does not exist on the network, the .DN bit may be set for that MSG instruction when the .ER bit should be set.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Power Cycle Fault (Lgx00126770, Lgx126637)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.012

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


Your controller might experience a major nonrecoverable fault if it uses an RSLogix 5000 project that requires most of the controller’ s available memory and power is cycled to the controller.

If the RSLogix 5000 project is so large that fewer than 25,000 bytes of controller memory remain free before power is cycled, the controller might experience this anomaly.

Complete these steps to best determine how much controller memory the project uses.
  
  1. If your controller is online, go offline.
  2. Download the RSLogix 5000 project to the controller.
  3. Cycle through all screens on each HMI device used in the application.

Often, the inclusion of HMI devices, such as PanelView Plus terminals, in the project causes it to use a large portion of the controller’ s memory.
  
  1. Go online with the controller.
  2. Access the Memory tab on the Controller Properties dialog box:

If this anomaly occurs, clear the fault and download the project.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Major Fault with POINT I/O (Lgx00129095, Lgx00129057)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.012

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


When the following conditions exist in your CompactLogix 5370 L3 control system, the controller may log a major recoverable fault, Type 2/Code 23:
  

To work around this anomaly, do not configure any remote POINT I/O modules over an EtherNet/IP network to Major Fault On Controller if Connection Fails While in Run Mode.
  

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Project with 1747-AENTR Adapter (Lgx00128819, Lgx00127668)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.012

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


When using a 1747-AENTR SLC 500 EtherNet/IP Adapter and more than five modules in a remote SLC chassis connected to your CompactLogix 5370 L3 controller, the second download of a project to your controller causes the controller to lose communication with the remote SLC chassis.

After losing communication with the remote SLC chassis, you also cannot communicate with the controller via the USB nor Ethernet port. You must disconnect the Ethernet cable from the 1747-AENTR adapter.

After the Ethernet cable is disconnected from the 1747-AENTR adapter, you can re-establish communication to the controller. However, the controller contains no program at that point.

You must re-download the program to the controller and then reconnect the Ethernet cable to the 1747-AENTR adapter to resume normal operations.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Fault or Connection Loss on CompactBus (Lgx00138101, Lgx00125644)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.012

Catalog Numbers 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


If a single module on the CompactBus experiences a fault or connection loss, all bits in the Fault word transition to 1.

The Fault word bits for only the faulted module should transition to 1 and the Fault word bits for the other modules on the CompactBus remain 0. However, the Fault word bits for all modules transition to 1.

Despite the Fault word bit transition to 1, the other modules on the CompactBus should be operating as expected. The controller incorrectly reports that the unaffected modules have experienced a fault.
You must cycle power to the controller for the bits to return to the correct status, that is, 0, when all modules are in the running state.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Write Files to SD Card (Lgx00124850, Lgx00124576)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


If the power to the controller is lost when the controller is writing a file to the SD card via a MSG instruction, the access can fail. The result of the failure is that the file or the file allocation table (FAT) can be corrupted on the SD card.

Consequently, all future attempts to read from or write to the SD card can also fail.
If your program is structured to attempt to access the SD card, it will repeatedly fail and experience a timeout condition on the operation. While these attempts are occurring, the controller does not service other message communication as expected, resulting in slower controller communication performance.

IMPORTANT: As long as the corrupted file exists on the SD card, you cannot use the SD card in other controllers. You must first clear all files from the SD card before it can be used again.

If you experience this anomaly, complete these steps to attempt to correct it.
  1. Change your controller to Program mode.
  2. Remove the SD card.
  3. Delete the corrupted file from the card or format the card.
  4. Re-install the SD card.
  5. Re-attempt to write the file to the SD card via a MSG instruction.

If you complete these steps and the issue persists, contact Rockwell Automation Technical Support.

TIP: The life expectancy of flash media is dependent on the number of write cycles that are performed. Flash media controllers use wear leveling but you should avoid frequent writes.
Avoiding frequent writes is particularly important when logging data. We recommend that you log data to a buffer in your controller’ s memory
and limit the number of times data is written to removable media.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Module RPI Overlap (Lgx00125325, Lgx00140412, Lgx00140413)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


Your controller can experience a Module RPI Overlap minor fault (Type 03/Code 94) when you perform any of the following actions:

Typically, a project download results in this anomaly if the project includes modules with large I/O sizes, such as a 1769-SDN scanner module, or high numbers of I/O modules.
  

When your controller experiences a Module RPI Overlap minor fault as a result of these actions, use the Controller Properties dialog box to clear
the fault.

Corrected: Logix Firmware Revisions 20.014, 21.011

Unconnected MSG Instructions via CompactBus (Lgx00124799, Lgx00122887, Lgx00124720, Lgx00135673)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


When a controller transmits unconnected MSG instructions over the CompactBus and through a 1769-SDN scanner module, the instruction execution time can be longer than expected. Slower execution times can cause some MSG instructions to timeout.
This anomaly occurs when the MSG instruction is targeted at or through any of the following modules:

Corrected: Logix Firmware Revisions 20.014, 21.011

Connections to Local Expansion Modules (Lgx00124799, Lgx00135673)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


You must inhibit all controller connections to local expansion modules, including the 1769-SDN scanner module, before uploading a scanlist from, or downloading a scanlist to, a 1769-SDN scanner module.

If you attempt to upload or download a scanlist without inhibiting connections to the local expansion modules, the scanlist upload or download can fail.

To work around this anomaly, use one of the following options:

For example, if you slow RPI rates for local expansion modules or change user task timing and priorities, the controller is more likely to upload or download a scanlist successfully.
  

You must inhibit all controller connections to local expansion modules, including the 1769-SDN scanner module, before updating firmware to a 1769-SDN scanner module.

If you attempt a firmware update to a 1769-SDN scanner module without inhibiting the connections, the firmware update can timeout, rendering the scanner module inoperable.

To work around this anomaly, use one of the following options.
Option One
  1. In a separate system, update the firmware revision on a replacement 1769-SDN scanner module to the desired revision.
  2. Remove power from the CompactLogix 5370 L2/L3 control system.
  3. Replace the existing 1769-SDN scanner module with the updated scanner module.
  4. Change the original RSLogix 5000 project so the 1769-SDN scanner module is configured with the new firmware revision.
  5. Power the control system.
  6. Download the original RSLogix 5000 project, updated with the new 1769-SDN scanner module firmware revision, to the CompactLogix 5370 L2/L3 controller.

Option Two
  1. Download a new, blank RSLogix 5000 project to the CompactLogix 5370 L2/L3 controller.
  2. Update the firmware revision of the 1769-SDN scanner module.
  3. Change the original RSLogix 5000 project so the 1769-SDN scanner module is configured with the new firmware revision.
  4. Download the original RSLogix 5000 project, updated with the new 1769-SDN scanner module firmware revision, to the CompactLogix 5370 L2/L3 controller.

Option Three
  1. Access the 1769-SDN scanner module via the DeviceNet network, for example, through a 1784-U2DN USB-to-DeviceNet cable or 1788-EN2DN Ethernet-to-DeviceNet linking device.
  2. Update the firmware revision of the 1769-SDN scanner module.
  3. Change the original RSLogix 5000 project so the 1769-SDN scanner module is configured with the new firmware revision.
  4. Download the original RSLogix 5000 project, updated with the new 1769-SDN scanner module firmware revision, to the CompactLogix 5370 L2/L3 controller.

IMPORTANT: When using any of the options described above, consider the Electronic Keying configuration for the 1769-SDN scanner module in your RSLogix 5000 project and any impact the configuration choice might have on your control system operation.

Corrected: Logix Firmware/RSLogix 5000 Software 20.018

Diagnostics for Active Ring Supervisor (Lgx00125647, Lgx00147559)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


The controller does not correctly display the active ring supervisor on the Ring Statistics webpage available from the Diagnostics folder.

The webpage displays the active ring supervisor IP address in reverse order. For example, an active ring supervisor using an IP address of 192.168.1.4 appears on the Ring Statistics webpage as 4.1.168.192.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Ethernet Port Settings (Lgx00149187, Lgx00125674)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


The controller’s Ethernet port settings, for example, the IP address or Subnet Mask, are always loaded from the SD card regardless of the Load Image parameter configuration on the Nonvolatile Memory Load/Store dialog box.

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Modify Ethernet Configuration via RSLinx Classic (Lgx00126023, Lgx00125612)

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


When modifying the controller’ s Ethernet configuration with RSLinx Classic software, you may experience a Module Configuration Invalid: Parameter error (16#0009).
This anomaly occurs if you try to apply two network configuration changes without closing the Controller Properties dialog box between the changes.
To work around this anomaly, close the Controller Properties dialog box after making every Ethernet configuration change in RSLinx Classic
software.
Corrected: Logix Firmware/Studio 5000 Software 20.013/21.011

PowerFlex 750 Series Drives (Lgx00134308, Lgx00135067, Lgx00130112)

Anomaly


Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT
 
Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM

 

When using PowerFlex 750 series drives with firmware that supports Drives Automatic Device Configuration (ADC) on powerup, the controller can become stuck in the transition to Run mode. When stuck in the transition to Run mode, the application is not executing and the outputs are not being
updated.

For more information, see Rockwell Automation Knowledgebase document 493802.

You can access the Rockwell Automation Knowledgebase at: http://www.rockwellautomation.com/rockwellautomation/support/overview.page?
 
Corrected: Logix Firmware/Studio 5000 Software 21.011

Audit Mask Value (Lgx00135562)

Anomaly


Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


In RSLogix 5000 software, version 20 and earlier, the Audit Mask Value is not saved as part of the user application. Consequently, when a restore from removable media, that is, an SD card, is performed, the value is restored to its default value.

In Logix Designer application, version 21 and later, the Audit Mask Value is saved with the user application.
 

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Heavily Loaded CompactBus (Lgx00133064)

Anomaly

Catalog Numbers 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


If the 1769 CompactBus is heavily loaded, one of the following can occur:
When the controller is in this state, no user programs are executing and no output data is being sent to modules.
 

Corrected: Logix Firmware/RSLogix 5000 Software 21.011

Project Downloads Fail (Lgx00135974)

Anomaly

Catalog Numbers 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


If the controller project includes modules with large I/O sizes, for example, ProSoft or 1769-SDN DeviceNet scanner modules, the initial project download executes as expected.
Subsequent project downloads to the controller fail and the Logix Designer application goes offline.
 

Fail Drive Connection on Peripheral Error (Lgx00138238)

Corrected Anomaly with Firmware Revision 21.011 and Firmware Revision 20.019

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

If you use a PowerFlex® drive that supports automatic drive configuration (ADC) and has a peripheral that is configured to Fail Drive Connection on Peripheral Error, the controller can experience a major non-recoverable fault (MNRF) when your application is downloaded to the controller.




Fault or Connection Loss on CompactBus (Lgx00138101, Lgx00125644)

Corrected Logix Firmware/Studio 5000® Software Revision 21.011 and Firmware Revision 20.019

Known Anomaly First Identified as of Firmware Revision 20.011

1769 CompactLogix™ 5370 Controllers Catalog Numbers:

If one module on the CompactBus experiences a fault or connection loss, all bits in the Fault word transition to 1.

The Fault word bits for only the faulted module transition to 1 and the Fault word bits for the other modules on the CompactBus remain 0. However, the Fault word bits for all modules transition to 1.

Despite the Fault word bit transition to 1, the other modules on the CompactBus are operating as expected. The controller incorrectly reports that the unaffected modules have experienced a fault.

You must cycle power to the controller for the bits to return to the correct status, that is, 0, when all modules are in the running state.


  

MAJ Instruction (Lgx00136317, Lgx00150458)

Corrected Anomaly with Studio 5000® Environment Software Revision 21.011, RSLogix 5000® Software Revision 20 and Controller Firmware Revision 20.019

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

An axis can move in the wrong direction in the following conditions:

– Profile Type = Trapezoidal

In this case, the direction on the faceplate is set to forward.

– Profile Type = S-curve

In this case, the sign of the current axis velocity of the axis being merged via the MAJ instruction and the sign of the velocity that is specified by the combination of the Direction parameter and Speed parameter on the faceplate are inconsistent.

You can complete the following tasks to work around this anomaly:

Always set the Speed parameter to +1.0.

If the current axis velocity is unknown, use a GSV instruction to obtain it.



CompactLogix Wall Clock Time (WCT) jumps ahead by 100 years (Lgx00152701, Lgx00179778)

Corrected Anomaly with Firmware Revision 20.019

Known Anomaly First Identified as of Firmware Revision 17

Catalog Numbers:

The WCT (WallClockTime) of the controller can jump 100 years on a power cycle. This jump can be seen as a one-time 100-year jump or a 100-year jump on every power cycle.

Product and Series
Continual 100-year jump on power cycle
One-time 100-year jump on power cycle
1769-L3x/L2x
Yes
No
1768-L4x/A and B
No
No
1768-L4x/C and D
Yes
No
1756-L63/A
No
No
ControlLogix 5560 Controllers series B
Yes
No
CompactLogix 5370
No
No
1756-L7x
No
Yes

The continual 100-year jump occurs 2 years after a program has been downloaded to a controller after the memory had been cleared / set to default.

The one-time 100-year jump occurs if the WCT is set to a value that has the year from 1990...1999.


Reconfigure Message Instruction Causes a Major Non-Recoverable Fault (Lgx00131221)

Corrected Anomaly with Firmware Revision 20.018

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

If a message instruction is configured to reconfigure an I/O module, it causes the Controller to Experience a major non-recoverable fault (MNRF).

See Knowledgebase document 576267.




Controller Faults When Alarm Instruction is Executed (Lgx00135333)

Corrected Anomaly with Firmware Revision 20.019

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

If an Analog Alarm (ALMA) or Digital Alarm (ALMD) instruction has a string-type associated tag and the string has a negative length, the controller can experience a major non-recoverable fault (MNRF) when the instruction is executed.





Known Anomalies in This Release

This release has the following known anomalies.

Disable Download Project Documentation and Extended Properties Features (Lgx00135928)

Known Anomaly First Identified As Of Firmware Revision 21.011

Studio 5000 Logix Designer First Identified As Of Version 21.00


Catalog Numbers:
- 1756 ControlLogix L7
- 1756 GuardLogix L7
- 5370 CompactLogix L1
- 5370 CompactLogix L2
- 5370 CompactLogix L3


IMPORTANT: The following restrictions apply to enabling or disabling the Download Project Documentation and Extended Properties feature and should be considered collectively. Any, or none, of these restrictions might apply to your application.

Restriction #1
Storing your project comments and tag descriptions in the controller can increase upload/download times. Be aware of the following:
• If you click the Cancel dialog box during the Finalize portion of the download process, the download process continues to successful completion and you may not be able to access the controller for long as 10 minutes.
• If the Finalizing portion of the download process takes longer than 10 minutes, the controller can generate a Major Non-recoverable fault (MNRF).

To work around this restriction, clear the Download Project Documentation and Extended Properties checkbox when downloading the project.

Restriction #2

IMPORTANT: This restriction exists only in environments that use multi-workstation development.
If you are using multi-workstation development, we strongly recommend that you configure the Logix Designer project to include all project documentation and extended properties when downloading a project to the controller.
This configuration setting is the default setting.
A Logix Designer project can lose content from the text boxes for routines written in either Function Block Diagram (FBD) or Sequential Function Chart (SFC) programming languages when both of the following conditions exist:
• Multiple workstations are online with the controller.
• The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared.
When project edits are made at one workstation, the content in the text boxes of edited routines are deleted from all of the other workstations in the environment.
To work around this restriction, configure the Logix Designer project so that the Download Project Documentation and Extended Properties checkbox is checked.

IMPORTANT: Consider the following:
• This anomaly does not apply if your Logix Designer project uses Ladder Logic (LL) or Structured Text (ST) programming languages.
• A restriction applies to when you check the Download Project Documentation and Extended Properties checkbox.

Restriction #3

IMPORTANT: This restriction exists only in environments that use multi-workstation development.
If you are using multi-workstation development, we strongly recommend that you configure the Logix Designer project to include all project documentation and extended properties when downloading a project to the controller.
A Logix Designer project can temporarily lose content in the Rung Comments sections when all of the following conditions exist:
• Multiple workstations are online with the controller.
• The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared.
• The Logix Designer project uses the Ladder Logic programming language.
When project edits are made at one workstation, the content in the Rung Comments sections for the project rungs is briefly hidden in all of the other workstations in the environment.

When rung edits are finalized on the workstation that is making edits, the content in the Rung Comments sections for the project rungs reappears in the in all of the other workstations in the environment.

To work around this anomaly, configure the Logix Designer project so that the Download Project Documentation and Extended Properties checkbox is checked.
 

ALMA and ALMD Instructions in Logix Designer

CORRECTED with Firmware Revision 24.011

Studio 5000 Logix Designer Version 24.00

Known Anomaly First Identified as of Firmware Revision 21.011


Catalog Numbers:


Even though controllers that use firmware revision 21.011 or later can use ALMA and ALMD instructions, FactoryTalk View Studio SE software, versions 6 and 7, cannot connect to a Logix Designer application that uses firmware revision 21.011 or later and uses ALMA or ALMD instructions.

IMPORTANT: This anomaly applies to the use of ALMA and ALMD instructions only. Tag-based alarming systems that use FactoryTalk Alarms and Events functionality work as expected.

IMPORTANT: This anomaly applies to the use of ALMA and ALMD instruction only. Tag-based alarming systems that use FactoryTalk Alarms and Events functionality work as expected with FactoryTalk View Studio SE software, version 6.

Local Expansion Modules Configured to Use IOT Instruction (Lgx00136059)

CORRECTED with Firmware Revision 24.011
Known Anomaly First Identified as of Firmware Revision 21.011

Catalog Numbers:


If any local expansion modules, that is, 1769 Compact I/O modules, are configured to use the Immediate Output (IOT) instruction, the controller can experience a Major Non-recoverable fault (MNRF) at powerup.

To recover from the fault, clear the fault and redownload the project.

To work around this anomaly, configure local expansion modules so that Major Fault On Controller if Connection Fails in Run Mode is enabled.

RPI for Local Expansion Modules (Lgx00136853)

Anomaly Identified As Of Revision 21.011

 
Catalog Numbers:
- 5370 CompactLogix L2
- 5370 CompactLogix L3

When configuring the RPI for local expansion modules, that is, 1769 Compact I/O modules, follow the guidelines described in the CompactLogix 5370 Controllers User Manual, publication 1769-UM021.

If you fail to follow the guidelines, the following can occur, indicating that the controller is not updating the local expansion module properly:

We recommend that you monitor your application code for the Module RPI Overlap minor fault being logged.

Reconfigure Message Instruction Active When Controller Is Power Cycled Causes a Major Non-Recoverable Fault (Lgx139492)


Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
21.011
29.011
Compact GuardLogix® 5370
21.011
29.011
ControlLogix® 5570
21.011
29.011
ControlLogix® 5570 Redundant
21.011
29.011
GuardLogix 5570
21.011
29.011


If a message instruction is configured to reconfigure an I/O module and the message is active when you cycle power to the controller, the controller can experience a major non-recoverable fault (MNRF).

See the Knowledgebase article Reconfigure Message if active when the controller powers down, will MNRF on the power up.

.






  

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.



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.

Known Anomalies from Previous Releases

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

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.

 

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:

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.

Data Integrity Anomalies with I/O modules that have large I/O Size (00188017)

Corrected Anomaly as of Firmware Revision 31.011

Known Anomaly First Identified in Firmware Revision 20.011

Catalog Numbers:

If you are using modules that have large IO sizes (for example, the 1769-SDN, 1769-SM1, 1769-SM2, ProSoft Modules), the controller will need to send the I/O data to these modules fragmented. This could result in the module using a mixture of old and new data.


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.


Domain Name and IP Address (Lgx00126785, Lgx00126981)

CORRECTED with Firmware Revision 24.011
Known Anomaly First Identified as of Firmware Revision 20.011


Catalog Numbers:

Your controller’ s domain name, an IP address setting, will not be retained if the name uses 48 characters and power is cycled to the controller. The maximum number of characters available in the domain name field is 48.

Therefore, if you use all of the available characters in the domain name field and power is cycled to the controller, the domain name is not retained.

This anomaly will not occur if the domain name field uses 47 or fewer characters.

Browse via RSLinx Classic over the USB Port (Lgx00128816, Lgx00128101)

Known Anomaly First Identified As Of Firmware Revision 20.012

Catalog Numbers

- 5370 CompactLogix L2

- 5370 CompactLogix L3

When you browse the controller via RSLinx Classic software using the USB driver and click the + to open the EtherNet/IP network, the IP address for the controller will not indicate the configured values.

Instead, the software shows an IP address of 0.0.0.0 as shown below.

graphic

Communication with 1769 I/O Modules

Anomaly

Logix Firmware/RSLogix 5000 Software 20.011

Catalog Numbers 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM


Tasks are the basic scheduling mechanism for executing a program and are created as part of the project and program creation process. In addition to other internal tasks, the CompactLogix controllers have an internal task to provide communication with the 1769 I/O modules. This task executes periodically at the Requested Packet Interval (RPI) selected in the properties of the CompactBus. If the task has not completed before it is time to execute again, a task overlap occurs. This task overlap causes the packaged controller to declare a minor fault of Type = 6 (Task Overlap), Code = 4 (VA task).

You can use various strategies to resolve minor faults due to task watchdog timeout and/or task overlap. For more information, see RSLogix 5000 Online Help ‘ Identifying and Managing Tasks’ . In the case of a minor fault caused by VA task overlap, increase the RPI until the overlap no longer occurs.

Operation with PanelView Plus Terminals (Lgx00127906)

CORRECTED with Firmware Revision 24.011
Known Anomaly First Identified as of Firmware Revision 20.011


Catalog Numbers:


When using the controller with PanelView Plus terminals, consider the following:

This firmware upgrade file for package 6.10 is available at: http://support.rockwellautomation.com/ControlFlash/FUWCom.asp.

The firmware upgrade file is available at http://support.rockwellautomation.com/ControlFlash/FUW.asp.

For more information, see KnowledgeBase article #473017 - CompactLogix 5370 Controllers Compatibility with PanelView Plus.

Connection via USB Cable (Lgx00122143)

Known Anomaly First Identified As Of Firmware Revision 20.011

Catalog Numbers:

- 5370 CompactLogix L1

- 5370 CompactLogix L2

- 5370 CompactLogix L3


If the controller is connected to a computer via a USB cable and the computer is restarted while the cable remains connected, you must disconnect and reconnect the cable between the controller and computer after the computer restart is complete.

Failure to disconnect and reconnect the cable results in a failure of the computer to recognize the controller when browsing in RSLinx Classic software.
  
 

Compact I/O Affects Controller Power-up Sequence (Lgx00127867, Lgx00127768)

Anomaly Identified As Of Revision 20.011

Catalog Numbers:

- 5370 CompactLogix L2

- 5370 CompactLogix L3


When you use some I/O modules in a 5370 CompactLogix L2 or 5370 CompactLogix L3 control system, they can cause the controller to fail its power-up sequence. When this occurs, the controller remains in a state with the OK status indicator solid red.
If you use any of the modules listed below in your 5370 CompactLogix L2 or 5370 CompactLogix L3 control system, make sure you use the series and firmware revisions, or later, listed.
  
Cat. No.
Series
Firmware Revision
1769-ARM
A
3.1
1769-ASCII
A
2.001
1769-BOOLEAN
A
1.2
1769-HSC
A
1.1
1769-IA16
A
3.1
1769-IA8I
A
3.1
1769-IF16C
A
1.2
1769-IF16V
A
1.2
1769-IF4
B
2.1
1769-IF4XOF2F
A
1.2
1769-IF4I
A
1.2
1769-IF4XOF2
A
1.1
1769-IF8
A
1.1
1769-IG16
A
3.1
1769-IM2
A
3.1
1769-IQ16
A
3.1
1769-IQ16F
A
3.1
1769-IQ32
A
3.1
1769-IQ6XOW4
B
3.1
1769-IR16
A
3.1
1769-IT6
A
2.2
1769-OA16
A
3.1
1769-OA8
B
3.1
1769-OB16
B
3.1
1769-OB16P
B
3.1
1769-OB32
A
3.1
1769-OB32T
A
3.1
1769-OB8
A
3.1
1769-OF2
B
2.1
1769-OF4
A
1.1
1769-OF4CI
A
2.1
1769-OF4VI
A
2.1
1769-OF8C
A
2.1
1769-OF8V
A
2.1
1769-OG16
A
3.1
1769-OV16
B
3.1
1769-OV32T
A
3.1
1769-OW16
A
3.1
1769-OW8
B
3.1
1769-OW8I
B
3.1
1769-SDN
B
2.2
  
 
Controller can Assert When Stopping an Axis That Is Executing an S-Curve Profile Jog (4913301, 4976159)
  
Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
38.011 and later
Compact GuardLogix® 5370
28.011
38.011 and later
ControlLogix® 5570
18.012
38.011 and later
GuardLogix 5570
20.011
38.011 and later
CompactLogix 5380
28.011
38.011 and later
Compact GuardLogix 5380 SIL 2
31.011
38.011 and later
Compact GuardLogix 5380 SIL 3
32.013
38.011 and later
CompactLogix 5380 Process
33.011
38.011 and later
CompactLogix 5480
32.011
38.011 and later
ControlLogix 5580
28.011
38.011 and later
GuardLogix 5580
31.011
38.011 and later
ControlLogix 5580 Process
33.011
38.011 and later

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

Work arounds to consider:

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

  

UID and UIE Instructions in a Continuous Task (00149169, 00144170)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
20.019, 24.011 and later
GuardLogix® 5570
20.011
24.011 and later
ControlLogix® 5570
20.011
20.019, 24.011 and later
ControlLogix 5560
20.011
20.019
1768 CompactLogix L4
20.011
20.019


If the UID (User Interrupt Disable) and UIE (User Interrupt Enable) instructions are used in a continuous task on powerup the controller could major non-recoverable fault (MNRF).






  

Message Instructions in Add-On Instruction PreScan and Main Logic Routines (Lgx00152820)

Known Anomaly since Firmware Revision 16

Catalog Numbers:

If a message instruction with the same backing tag is used in an Add-On Instruction in the Prescan and Main Logic routine, the controller on a transition to Run mode does one of the following:

Or



  

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.



  

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.

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.

Socket Application Code Can Cause the Controller to MNRF (00227905, 00228810)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
33.011
Compact GuardLogix® 5370
28.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 your application code tries to access a socket that has already been deleted, the controller can experience a major nonrecoverable fault.


  

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.

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.


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.

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.

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.



Controller can take more time than expected to re-establish connections (00212775, 00227804)

CORRECTED Anomaly with

Known Anomaly First Identified in

If repeated connection interruptions occur because of network cable disconnections, the controller can take more than 10 minutes to re-establish connections. If the controller is power cycled, connection re-establishment is almost immediate.

  

On powerup CompactLogix and Compact GuardLogix controller Ethernet port may not properly initialize (00223080, 00179897)

CORRECTED Anomaly with

Known Anomaly First Identified in

When the controller is powering up, if there is sufficient incoming communication to the embedded Ethernet port, the port may not initialize properly and communication to and from the controller can fail. While the controller is in this state, the IP address of the controller is reported as 0.0.0.0 and the NS (Network Status) indicator is off.

To allow the embedded Ethernet port to initialize correctly to allow controller communication, the controller must be power-cycled with incoming communication sufficiently decreased.

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.

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.

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.

  

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.



Message T0 (Timeout) Bit Does Not Function as Designed (1068449)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
34.011
Compact GuardLogix® 5370
28.011
34.011


When setting the message TO (TimeOut) bit in the message instruction backing tag the message instruction does not timeout immediately as expected.  It will time out as set by the unconnected timeout setting in the message instruction backing tag, which the default is 30 seconds.


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.


Module does not get IP Address Assigned from a DHCP Server (2188094, 2233611)

Modules
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
20.011
36.011
Compact GuardLogix® 5370
28.011
36.011
1756-EN2F
 5.028 (Signed)
2.005 (Unsigned)
12.001 and later
1756-EN2T
5.028 (Signed)
12.001 and later
1756-EN2TP
10.020
12.001 and later
1756-EN2TR
 5.028 (Signed)
1.003 (Unsigned)
12.001 and later
1756-EN3TR
 5.028 (Signed)
3.004 (Unsigned)
12.001 and later
1756-ENBT
1.061
—
1768-ENBT
1.003
—


This anomaly was due to a change in the Dynamic Host Configuration Protocol (DHCP) standard, RFC 6842. This anomaly results in the module not being able to obtain an IP address through DHCP with some Stratix® switches that follow the updated standard.

For more information, see Knowledgebase Technote Some Ethernet devices do not obtain DHCP lease from Stratix 5800 as DHCP Server.



  
Controller Can Assert When Motion Instruction Accel And/Or Decel Operands Are Out of Range (3341103, 3453881, 3453882, 3453883, 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
34.015, 35.014, 36.013, 37.011 and later
Compact GuardLogix 5380 SIL 2
31.011
34.015, 35.014, 36.013, 37.011 and later
Compact GuardLogix 5380 SIL 3
32.013
34.015, 35.014, 36.013, 37.011 and later
CompactLogix 5380 Process
33.011
34.015, 35.014, 36.013, 37.011 and later
CompactLogix 5480
32.011
34.015, 35.014, 36.013, 37.011 and later
ControlLogix 5580
28.011
34.015, 35.014, 36.013, 37.011 and later
GuardLogix 5580
31.011
34.015, 35.014, 36.013, 37.011 and later
ControlLogix 5580 Process
33.011
34.015, 35.014, 36.013, 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.


Functional Changes

This release has the following functional changes from the previous release.

V21 Additional Memory Requirements for CompactLogix 5370 Controllers

Functional Change

Available As Of:

Firmware Revision 21.011/RSLogix 5000 Software Version 21

 

Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM

If you are upgrading your system through multiple firmware revisions, add all components your application uses for each of the revisions you upgrade through.


If you upgrade from 20.x to 21.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Safety
Program
+ 8 bytes
 
X
 
Add-On Instruction
+ 12 bytes
 
X
 
SFC Routine
+ 8 bytes
 
X
 
Tag that uses AXIS_GENERIC data type
+ 32 bytes
 
X
 
Tag that uses OUTPUT_CAM data type
+ 512 bytes
 
X
 
Tag that uses AXIS_SERVO_DRIVE data type
- 8 bytes
 
X
 
Tag that uses CIP_DRIVE data type
+ 4 bytes
 
X
 
PRODUCE_TAG
+ 2 bytes
 
X
 
Tag that uses ALARM_DIGITAL data type
+ 64 bytes
 
X
 
Tag that uses ALARM_ANALOG data type
+ 436 bytes
 
X
 
Tag that uses MOTION_GROUP data type
- 8 bytes
 
X
 
For each controller
-76 bytes
 
X
 
            CompactLogix 5370 L1
+ 376 bytes
X
 
 
CompactLogix 5370 L1
+ 6600 bytes
 
X
 
CompactLogix 5370 L2 (1769-L24ER-QB1B)
+ 1392 bytes
X
 
 
            CompactLogix 5370 L2 (1769-L24ER-QB1B)
+ 13588 bytes
 
X
 
CompactLogix 5370 L2 (1769-L24ER-QBFC1B or 1769-L27ERM-QBFC1B)
+1392 bytes
X
 
 
CompactLogix 5370 L2 (1769-L24ER-QBFC1B or 1769-L27ERM-QBFC1B)
+ 13564 bytes
 
X
 
CompactLogix 5370 L3
+ 24 bytes
X
 
 
            CompactLogix 5370 L3
+ 14984 bytes
 
X
 
1756-L7xS
+ 48 bytes
X
 
 
1756-L7xS
+ 24720 bytes
 
X
 
            1756-L7x
+ 16 bytes
X
 
 
            1756-L7x
+ 24720 bytes
 
X
 
1789-L10, 1789-L30, 1789-L60
+ 76196 bytes
X
 
 


If you upgrade from 19.x to 20.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Safety
Task
+  1312 bytes
 
X
 
Program
+ 16 bytes
 
X
 
Equipment phase
+ 8 bytes
 
X
 
Routine
+ 24 bytes
 
X
 
Add-On Instruction
+ 32 bytes
 
X
 
Project with any tags that use ALARM_ANALOG or ALARM_DIGITAL data type
-76 bytes
 
X
 
            Tag that uses ALARM_ANALOG data type
+ 4 bytes
 
X
 
            Tag that uses ALARM_DIGITAL data type
+ 24 bytes
 
X
 
            Tag that uses MOTION_GROUP data type
+ 56 bytes
 
X
 
            Tag that uses COORDINATE_SYSTEM data type
+ 950 bytes
 
X
 
            Tag that uses AXIS_CIP_DRIVE data type
+ 676 bytes
 
X
 
            Tag that uses AXIS data type other than
            AXIS_CIP_DRIVE
+ 672 bytes
 
X
 
            Standard produced tag
+ 4 bytes + (4 bytes x number of consumers)
X
 
 
            Standard consumed tag
+ 12 bytes
X
 
 
            Safety produced tag
+ 4 bytes
 
 
X
            Safety consumed tag
+ 4 bytes
 
 
X
            I/O module
+ 8 bytes
 
X
 
Module input connection
+ 4 bytes
 
X
 
Module output connection
+ 4 bytes
 
X
 
For each controller (> 1 K bytes change):
 
 
 
 
            1756-L6x controller
+ 1264 bytes
 
X
 
            1756-L6x controller
+ 1268 bytes
X
 
 
            1756-L6xS controller
+ 1316 bytes
 
X
 
            1756-L6xS controller
+ 1312 bytes
X
 
 
            1756-L7x controller
+ 5588 bytes
 
X
 
            1756-L7x controller
+ 1296 bytes
X
 
 
            1768-L4x, 1768-L4xS controller
+ 1212 bytes
 
X
 
            1768-L4x controller
+ 1292 bytes
X
 
 
            1768-L4xS controller
+ 1340 bytes
X
 
 
            1768-L4xS controller
+ 1312 bytes
 
 
X
            1769-L23 controller
+ 2488 bytes
X
 
 
            1769-L31 controller
+ 2492 bytes
X
 
 
            1769-L32C, 1769-L35CR controller
+ 2812 bytes
X
 
 
            1769-L33E, 1769-L35E controller
+ 2496 bytes
X
 
 



If you upgrade from 18.x to 19.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
NA
<no change>
 
 



If you upgrade from 17.x to 18.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Program
+ 8 bytes
 
X
Equipment phase
+ 20 bytes
 
X
Add-On Instruction
+ 12 bytes
 
X
Each tag
In addition, if you use a tag of the types listed below, increase the memory as indicated for each instance:
+ 4 bytes
 
X
Produced tag
+ 36 bytes + (24 bytes * number of consumers)
X
 
Consumed tag
+ 24 bytes
X
 
Data access control
+ 4 bytes per symbol
 
X
Tag that uses ALARM_ANALOG data type
- 20 bytes
 
X
Tag that uses ALARM_DIGITAL data type
+ 28 bytes
 
X
Tag that uses MOTION_GROUP data type
+ 76
 
X
Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type
+ 786 bytes
 
X
Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE
+ 818 bytes
 
X
Tag that uses COORDINATE_SYSTEM data type with no transform dimensions
+ 40 bytes
 
X
Tag that uses COORDINATE_SYSTEM data type with transform dimensions
+ 100 bytes
 
X
Module input connection
+ 20 bytes
 
X
Module output connection
+ 24 bytes
 
X
Safety controller
- 8 bytes
 
X
Safety partner
- 8 bytes
 
X
For each controller (> 1k bytes change):
 
 
 
1756-L6x, 1756-L6xS, 1756-L63XT
+ 16728 bytes
 
X
1768-L4x, 1768-L4xS
+ 14448 bytes
 
X
1769-L2x
+ 35084 bytes
X
 
1769-L31
+ 14740 bytes
X
 
1769-L32C, 1756-L35CR
+ 35400 bytes
X
 
1769-L32E, 1756-L35E
+ 35036 bytes
X
 
1789-L10, 1789-L30, 1789-L60
+ 4992
X
 


If you upgrade from 16.x to 17.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Task
+ 4 bytes
 
X
Program
+ 4 bytes
 
X
Equipment phase
+ 8 bytes
 
X
LD routine
+ 12 bytes
 
X
FBD routine
- 8 bytes
 
X
SFC routine
+ 28 bytes
 
X
ST routine
+ 4 bytes
 
X
Add-On Instruction
- 12 bytes
 
X
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Produced tag
+ [4 bytes + (4 bytes * number of consumers)]
X
 
Consumed tag
+ 8 bytes
X
 
Tag that uses MESSAGE data type
+ 4 bytes
 
X
Tag that uses ALARM_ANALOG data type
- 64 bytes
 
X
Tag that uses ALARM_DIGITAL data type
- 28 bytes
 
X
Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type
 - 34 bytes
(2 bytes x number of output cam execution targets)
 
X
Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE
 - 52 bytes
(2 bytes x number of output cam execution targets)
 
X
Tag that uses COORDINATE_SYSTEM data type of 2 dimensions with 2 transform dimensions
+ 20 bytes
 
X
Tag that uses COORDINATE_SYSTEM data type of 3 dimensions with 3 transform dimensions
+ 108 bytes
 
X


If you upgrade from 15.x to 16.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Tag that uses ALARM_ANALOG data type (with no associated tag references)
+ 16 bytes
 
X
Tag that uses ALARM_DIGITAL data type (with no associated tag references)
+ 4 bytes
 
X
Tag that uses ALARM_ANALOG data type (if associated tags are configured for the ALARM_ANALOG tag)
 + 22 bytes
+ (9 x the number of configured, associated tags)
+ (3 x the sum of the bytes used by the data type of each of the configured associated tags)
For example, an analog alarm moved to V16.03 with two Associated Tags – one DINT (4 bytes) and one STRING (88 bytes) would need to add:
22 + 9(2) + 3(92) = 316 bytes
 
X
Tag that uses the COORDINATE_SYSTEM data type
+ 132 bytes
 
X


If you upgrade from 14.x to 15.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Input module
+ 4 bytes
X
 
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Produced tag
+ 12 bytes
X
 
Consumed tag
+ 4 bytes
X
 
Tag that uses COORDINATE_SYSTEM data type
+ 748 bytes
 
X
Tag the uses any AXIS data type
+ 800 bytes
 
X
Task
+ 20 bytes
 
X
Program or equipment phase
+ 24 bytes
 
X
Routine
+ 4 bytes
 
X
Serial port
+ 1120 bytes
 
X
Project
+ 4012 bytes
 
X





If you upgrade from 13.x to 14.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Tag that uses the COORDINATE SYSTEM data type
+ 60 bytes
 
X
Tag that uses any AXIS data type
+ 4 bytes
 
X


If you upgrade from 12.x to 13.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Program
+ 12 bytes
 
X
Task
+ 4 bytes
 
X
User-defined data type
+ 4 bytes
 
X
I/O module
+ 16 bytes
 X
(8 bytes)
 X
(8 bytes)
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Produced tag
+ 8 bytes
X
 
Consumed tag
+ 8 bytes
X
 






If you upgrade from 11.x to 12.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
I/O module with a comm format = Rack Optimization
+ 90 bytes
 
X
I/O module with a comm format = something other than Rack Optimization (such as a direct connection)
+ 144 bytes
 
X
CompactLogix 1769 I/O module
+ 170 bytes
 
X
Bridge module with a comm format = None
+ 160 bytes
 
X
Bridge module with a comm format = Rack Optimization
+ 220 bytes
 
X


If you upgrade from 10.x to 11.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
User-defined data type
  • Number of user-defined data types in the controller organizer > Data Types folder > User-Defined folder
  • Not the use of that data type in tags
+ 128 bytes
 
X
Indirect address (using a tag as the subscript for an array in an instruction, such as an Array_A[Tag_B]). This memory change applies only if the array:
  • uses a structure as its data type
  • does not use one of these data types: CONTROL, COUNTER, PID, or TIMER
has only one dimension (such as UDT_1[5])
- 60 bytes
 
X


If you upgrade from 9.x to 10.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Program
+ 12 bytes
 
X
Routine
+ 16 bytes
 
X


If you upgrade from 8.x to 9.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Tag that uses the MESSAGE data type
+ 376 bytes
 
X


If you upgrade from 7.x to 8.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Project
+ 1050 bytes
X
 
Tag
+ 0.55 bytes
 
X
Message that transfers more than 500 bytes of data and targets a controller in the same chassis
This memory is allocated only when the MSG instruction is enabled. To estimate, count the number of these messages that are enabled and/or cached at one time
+ 2000 bytes
X
 


If you upgrade from 6.x to 7.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
Base tag
+ 24 bytes
 
X
Alias tag
+ 16 bytes
 
X
Produced tag    DINT 4
+ 12 bytes
 
X
Produced tagREAL 4
+ 12 bytes
 
X
Consumed tag  DINT 4
+ 12 bytes
 
X
Consumed tagREAL 4
+ 12 bytes
 
X
Routine
+ 68 bytes
 
X


If you upgrade from 5.x to 6.x

Then add the following memory requirements to your project
Which comes from this type of memory
Component
Increase/Decrease Per Instance
I/O
Data and Logic
Routine
+ 116 bytes
 
X



 

 

MCS Instruction (Lgx00133646, Lgx00133127)

Functional Change First Identified as of:

In the Logix Designer application, version 21, stopping coordinated motion by using a Motion Coordinated Stop (MCS) All instruction could take longer than expected if the following conditions existed:
• The MCS All instruction is executed when the coordinate motion instruction is accelerating, decelerating, or blending with another instruction.
• The duration of the acceleration or deceleration is very short, for example, 10 coarse update periods or fewer.
• The configured maximum deceleration of any axis in the coordinate system is significantly lower, for example, 50% or less, than programmed maximum deceleration of the MCS instruction.

  

Application Notes

This release has the following application notes.

Logix Designer Not Able to Download Project

Application Note for:

Your Logix Designer application project will not download in the following conditions:
• The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared.
• The controller ’s programming code uses minimum or maximum extended properties in code elements tag name.@MIN or tag name@MAX.

To work around this restriction, check the Download Project Documentation and Extended Properties checkbox when configuring the project.

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

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