Release Notes

Compact GuardLogix L43S Controller
Version 20.018 (released 11/2015)

Catalog Number 1768-L43S (series B)

These release notes describe version information for 1768-L43S, version 20.018 (released 11/2015).

Corrected Anomalies in This Release

This release corrects the following anomalies.

Sequential Function Chart Executes Incorrectly (00167203)

Corrected Anomaly with Firmware Revision 20.018

Known Anomaly First Identified as of Firmware Revision 11

Catalog Numbers:


A Sequential Function Chart (SFC) can execute incorrectly after the sequence occurs:

1. You stop the execution of an SFC inside a nested simultaneous branch when all nested simultaneous branches are on their last steps.

2. You reset the chart.


Download firmware, associated files, and access product release notes from the Product Compatibility and Download Center at http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.



Online Configuration Changes Fail for Dynamix 1444 Series Module (00166830)

Corrected Anomaly with Firmware Revision 20.018

Known Anomaly First Identified as of Firmware Revision 20.011

Catalog Numbers:


Attempts to change the configuration for a Dynamix™ 1444 Series dynamic measurement module while a Studio 5000 Logix Designer application project is online results in a Module Reconfiguration Error.
To work around the anomaly, complete these steps.
1. Change the module configuration and apply the changes.
2. Inhibit the module.
3. Uninhibit the module.
For more information, see Rockwell Automation Knowledgebase article #701388 – 1444-Dynamix module error when clicking apply after changes made when online with the controller.

The Knowledgebase is accessible from the Rockwell Automation Technical Support site. A login in required. Download firmware, associated files, and access product release notes from the Product Compatibility and Download Center at http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.


K6500 Drive Bus Regulator Action Attribute Rejection (00160680)

Corrected Anomaly with Firmware Revision V20.018

Known Anomaly First Identified as of Firmware Revision V20.011

Catalog Numbers:


Power cycle of a Kinetix 6500 drive system can lead to the rejection of the bus regulator action attribute. To facilitate this error, the drive system must be subjected to a very brief power cycle while Logix control power remains. The drive system will reject this attribute unless the bus voltage is depleted.


Download firmware, associated files, and access product release notes from the Product Compatibility and Download Center at http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.


Major Non-recoverable Fault Occurs During Online Editing (00140975)

Corrected Anomaly with Firmware Revision 20.018

Known Anomaly First Identified as of Firmware Revision V11

Catalog Numbers:


The controller can experience a major non-recoverable fault (MNRF) when you make online edits in Sequential Function Chart (SFC) programming routines. If the anomaly occurs, the controller experiences a fault and deletes the project from its memory.
If the anomaly occurs, clear the controller fault and re-download the project to the controller.

Download firmware, associated files, and access product release notes from the Product Compatibility and Download Center at http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.



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.




Known Anomalies in This Release

This release has the following known anomalies.

Applications with PowerFlex drives in the I/O configuration can experience a major non-recoverable fault (MNRF) (00200734, 00200735, 00200600, 00200599)

Corrected Anomaly as of Firmware Revision 31.011 and 30.014 for these catalog numbers:

Corrected Anomaly as of Firmware Revision 31.011 and 30.013 for these catalog numbers:

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

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

If a controller already has an application loaded into it that contains PowerFlex drives in the I/O configuration, a MNRF (Major Non-Recoverable Fault) can occur when any of the following occurs:

For more information and workarounds, see Knowledgebase document 1067997.



Known Anomalies from Previous Releases

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


MRP Instruction (Lgx00135082, Lgx00134472)

Corrected: Logix Firmware/Studio 5000 Software 21.011

Corrected: Logix Firmware 20.014 for only
·1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
·1756-L71, 1756-L72, 1756-L73, 1756-L73XT, 1756-L74, 1756-L75
·1769-L18ERM-BB1B,1769-L27ERM-QBFC1B,1769-L30ERM,1769-L33ERM, 1769-L36ERM
·1768-L43, 1768-L45

Anomaly

Logix Firmware/RSLogix 5000 Software 20.013

Catalog Numbers

·1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
·1756-L61S, 1756-L62S, 1756-L63S
·1756-L71, 1756-L72, 1756-L73, 1756-L73XT, 1756-L74, 1756-L75
·1756-L71S, 1756-L72S, 1756-L73S, 1756-L73SXT
·1769-L18ERM-BB1B,1769-L27ERM-QBFC1B,1769-L30ERM,1769-L33ERM, 1769-L36ERM
· 1768-L43, 1768-L43S, 1768-L45, 1768-L45S

If single-axis or multi-axis move instructions are initiated while a Motion Redefine Position (MRP) instruction is in process, the controller experiences Motion Error 85. This anomaly occurs when the MRP instruction is configured to use an Absolute or Relative operation.


With the anomaly correction, motion that is initiated while an MRP instruction, configured for Absolute operation, is in process causes the controller to experience Motion Error 85.


PI Function Block Appears to Stop Executing

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 is possible. This possibility is dependant on 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 Process Control and Drives Instructions User Manual, publication 1756-RM006.



Alarm Systems Timeout Changes Require New Download (00069461)

Known Anomaly First Identified as of:

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:


Cycle Power to Clear a Major Fault

Known Anomaly First Identified as of:

If a 1769 I/O fault occurs, you must cycle power to the CompactLogix™ controller after clearing the major fault. I/O communication is not restored until after the power cycle. Never use the fault handling routine to clear local I/O faults. Clear local I/O faults manually on a per case basis, and then the controller must be power cycled.

Time Synchronization Causes Controller to Become Local Master

Known Anomaly First Identified as of:

Enabling the time synchronization feature of a CompactLogix™ controller results in the controller becoming the local master. It does not result in the controller synchronizing with other wallclock times in the system.


Use of a Safety Tag Results in a Timeout (000104877)

Known Anomaly

Cat. No.
Identified As Of
1768-L43S, 1768-L45S
Firmware Revision 18.011/RSLogix 5000 Software Version 18

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

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

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

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

 

Absolute Immediate or Passive Home Generates Error (00135080, 00134716)

Corrected: Logix Firmware 20.014 for only
·1768-L43, 1768-L45

Known Anomaly First Identified as of:

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


  

Fault/Program States Not Supported by Using the Module Configuration
Dialog Box

Known Anomaly First Identified as of:

This anomaly applies to CompactLogix™ systems as follows:

In this description, the term I/O module refers to 1769 Compact output modules or output points on 1769 Compact combination modules.

RSLogix™ 5000 software does not support Fault/Program state action for I/O modules in CompactLogix systems. The controller cannot trigger the configured Fault/Program state action. You can configure the Fault/Program state action in RSLogix 5000 software, but the configuration does not take effect.

If either of the following conditions exists, outputs turn off, regardless of the Fault/Program state action configuration:

Additionally, RSLogix 5000 software generates configuration tags for any I/O modules in the project. Some of the tags define configuration (C) data type members that include attributes for Fault/Program states, also known as alternate output states.

Because CompactLogix systems do not support Fault/Program state action for I/O modules, do not configure the attribute tags listed in the following table.

Attribute Tags to Avoid

Digital Output Modules
Analog Output Modules
  • ProgToFaultEn
  • ProgMode
  • ProgValue
  • FaultMode
  • FaultValue
  • CHxProgToFaultEn
  • CHxProgMode
  • CHxFaultMode
Where CHx = the channel number

Multiple Absolute MAM Instructions with S-curve and Merge Enabled Can Overshoot Target Position (00078822)

Known Anomaly First Identified as of:

Overshoot can occur with MAM instruction with Merge Enabled if there is not enough distance until the end of the move for the programmed dynamic jerk parameters, that is decel jerk and axis decel, in the merged move.

Overshoot can be avoided by increasing the decel jerk or not using the merge.


Motion Axis Move Instruction May Overshoot Programmed Position (00078822)

Known Anomaly First Identified as of:

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

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


Motion Group Shutdown Reset Instruction Execution Results in Shutdown State Error (00095484)

Known Anomaly First Identified as of:

If a Motion Group Shutdown Reset (MGSR) instruction is executed while a Motion Group Shutdown (MGSD) is still executing, motion error #7, that is, Shutdown State Error, results.

The purpose of an MGSR instruction is to bring an axis group out of the shutdown state. However, when the scenario that is described in the previous paragraph exists, the MGSR instruction is not executed because the shutdown procedure, which is initiated by the MGSD instruction, has precedence. Thus, the MGSR instruction generates motion error #7 because the shutdown procedure has not completed. The shutdown procedure must complete before any attempt to reset the shutdown.


VelocityFeedback Attribute May Contain Incorrect Value (00107793)

Known Anomaly First Identified as of:

IMPORTANT: This anomaly only occurs in SERCOS applications that use Kinetix® SERCOS drives and linear motors.w

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

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

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

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

Workaround - To avoid this anomaly, do not enable the VelocityFeedback attribute until the RSLogix 5000 program is online.


Configure the Compact GuardLogix Controller as the CST Master (00104194)

Known Anomaly

Cat. No.
Identified As Of
1768-L43S, 1768-L45S
Firmware Revision 18.011/RSLogix 5000 Software Version 18

We recommend that you configure the Compact GuardLogix controller so that it becomes the CST master. To do so, select Enable Time Synchronization on the Date/Time tab of the Controller Properties dialog box. If you do not configure the Compact GuardLogix controller to become the CST master and your project uses safety tags that are produced, I/O faults can occur when the project is downloaded.

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

 

Using Automatic Device Configuration (00129165)

Known Anomaly First Identified as of:

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™, to change drive parameters. Doing so can cause a sequence of events to occur that results in the connection between the controller and the drive to be dropped. Also, the controller cannot re-establish the connection.

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


ALMA and ALMD Tag Members Mismatch (00119996)

Known Anomaly First Identified as of:

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 must be handled as zero.


Axis Prevents Execution of Motor Feedback or Marker Test (00128827)

Known Anomaly First Identified as of:

In Axis-Servo-Drive data types (SERCOS), the axis is not allowing execution of motor feedback or marker test while the axis’ safe-off input is open. This action operated correctly in version 19.00.00, but does not operate correctly in RSLogix™ 5000 software, version 20.00.00 and 20.01.00.


Accept Edits Effect on Controller Log (00122622)

Known Anomaly First Identified as of:

When you accept edits in LD, ST, and FBD, the controller will log an ‘Online Edit’ entry in the controller log. Accepting edits in an SFC routine is done by performing a partial import, resulting in a ‘Transaction Commit’ entry in the controller log.

This function 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.


Maximum Simultaneous Active Reconfigure Messages (00125204)

Known Anomaly First Identified as of:

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

For example, if you send five reconfiguration messages simultaneously, three reconfigure messages truly complete (DN bit goes high), and the I/O modules are reconfigured. The other two reconfigure messages indicate complete (DN bit goes high), but the I/O modules is not reconfigured. In this case, the last two are supposed to have errored (ER bit), but do not.


Corrected: Logix Firmware/Studio 5000 Software 21.011

Log On to FactoryTalk Dialog Box Displays When Launching RSLogix 5000 (00124955)

Known Anomaly First Identified as of:

When launching RSLogix™ 5000 software, the Log On to FactoryTalk® dialog box can display. This dialog box can 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 canceled, the RSLogix 5000 software is not launched. When the dialog box is displayed, entering the credentials for a user that has Administrator privileges on the personal computer allows 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.

(In some cases, to continue, you need to provide credentials for a user with Administrator privileges.)

  1. 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.
  2. Click Add and provide the domain\logon name for the desired user.

(You can click Check Names to verify that the name was found.)

  1. 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.
  2. Click Add and type the name of the user group, Authenticated Users.

The Log On to FactoryTalk dialog box can also be displayed when you are using Remote Desktop to connect to the personal computer running RSLogix 5000 software.

This dialog box appears because FactoryTalk Security does not recognize the computer name. To enable access through Remote Desktop for a specific computer, you must 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 with your domain credentials.
  2. Navigate to Network\System\Security Policy. In the Computer Policy Settings section, set Identify terminal server clients with 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 is displayed each time RSLogix 5000 software is launched. When this is launched, proper user credentials must be entered to continue. (By default, ‘Use single sign-on’ is set to enable.)


SFC Action Body Executes Erroneously (00124697)

Known Anomaly First Identified as of:

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 accumulator of the timer (ACC) rolls 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 executes. If ACC >=PRE, it is not executed. When the rollover occurs, the ACC,PRE, and the action body incorrectly exectutes.


Arithmetic State Flags (00122480)

Known Anomaly First Identified as of:

Arithmetic State flags anomalies.

  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 Unavailable

Known Anomaly First Identified as of:

The Logix CPU security tool does not work with version 20 controllers.


RSLogix 5000 Clock Update Does Not Support Some Operating Systems

Known Anomaly First Identified as of:

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



Autotune Ignores Motion Polarity Setting (00135082,00133874)
Corrected: Logix Firmware 20.014 for only
·1768-L43, 1768-L45

Known Anomaly First Identified as of:

An autotune does not verify that the Motion Polarity is set properly. The Motion Polarity setting is used by the controller when it generates motion commands to the drive, but when the autotune is done by the drive it does not use the setting. This difference could cause unexpected motion.


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.



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.





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



  

Application Notes

This release has the following application notes.

Firmware Upgrade Guidelines for Safety Controllers

This application note applies to all firmware revisions of:

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

For Example:
  1. From the Product Compatibility and Download Center:
    1. Review all firmware release notes, starting with the original firmware revision through the new firmware revision, to identify any changes that impact the safety-related implementation of the application.
    2. Review hardware and firmware compatibility to identify any restrictions between the original system components and the new system components.
  2. Perform a hazard and risk assessment for any changes identified during the impact analysis and determine what additional testing is necessary.
  3. Perform the online and offline edit process described in the safety reference manual for your controller. You can restrict the ‘Test the Application’ block to the testing identified by the hazard and risk assessment.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 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.