Release Notes

CompactLogix 5370 L3 Controller, 2Mb Memory, w/Supercap Backup, up to 16 1769 I/O expansion modules, 32 EtherNet/IP and 120 TCP
Version 35.011 (released 11/2022)

Catalog Number 1769-L33ER/1769-L33ERK (series A)

These release notes describe version information for 1769-L33ER/1769-L33ERK, version 35.011 (released 11/2022).

Requirements

This release has the following requirements.

Compatible Software for Controller Firmware Revision 35.011

System Requirements as of Revision 35.011 for these catalog numbers:

This table identifies the minimum software versions that are compatible with firmware revision 35.011:

Software
Version
 
Studio 5000 Logix Designer®
35.00.00
 
RSLinx® Classic
4.30.00
 
FactoryTalk® Linx
6.31.00
 
ControlFLASH™
15.06.00
 
ControlFLASH Plus™
5.00.00
 




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.

 

Accept Edits (Lgx00122528, Lgx00122622)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

 

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

Arithmetic State Flags (Lgx00122480)

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:

 

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

Logix CPU Security Tool

Known Anomaly First Identified as of Firmware Revision 20.011

RSLogix 5000™ Version 20.00

Studio 5000 Logix Designer™ First Identified as of Version 21.00

 

Catalog numbers:

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.

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
  
 

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.
 

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

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:

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


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.

I/O Activity Affects Periodic Sampling for Data Logs (Lgx00129461)

Known Anomaly First Identified as of Firmware Revision 24.011

Catalog Numbers:

 

I/O activity can affect the repeatability of the periodic sampling for data logs.  The result of this anomaly occurring is missed periods of data samples. That is, the time between two data samples is twice as long as expected. 

The following are I/O activities:

Alarm Log Content Lost at Powerup (Lgx00138163)

Known Anomaly First Identified as of Firmware Revision 24.011

Catalog Numbers:

 

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

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

Known Anomaly First Identified as of Firmware Revision 24.011 for:

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

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


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

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.

  

Attribute Values Incorrect with Set System Value Instruction (00169713)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:

                                                    

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



Wall Clock Value Different From Previous Value (00169756)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:


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

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



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

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:


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



Unconnected Timeout Time Incorrect (00171872)

Known Anomaly First Identified as of Firmware Revision 27.011

Catalog Numbers:


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



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

Known Anomaly First Identified as of Firmware Revision 28.011

Catalog Numbers:


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

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

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

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



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

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix™ 5370
29.011
—
Compact GuardLogix® 5370
29.011
—
ControlLogix® 5570
29.011
—
GuardLogix 5570
29.011
—
ControlLogix 5570 redundant
30.051
—


Controller applications with a continuous task with CONCAT or DTOS instructions where indirect addressing exists may result in a controller major nonrecoverable fault/assert when additional task(s) exist. See Knowledgebase Technote 5570/5370 Controller Anomaly with Continuous Task, Indirect Addressing and CONCAT or DTOS.


  

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

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


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

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



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

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


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


  

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 Writing to the Message Backing Tag Timeout (TO) Bit Repetitively (3830685)

Controllers
First Known in Firmware Revision
Corrected in Firmware Revision
CompactLogix® 5370
34.011
—
Compact GuardLogix® 5370
34.011
—


The more message instructions that are enabled and have their timeout bits written to faster than one second, the more likely controller asserts are to occur.

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.