Release Notes

( 9324-RLDx ) Studio 5000 programming software. All you need for discrete, process, batch, motion, safety etc.
Version 37.00.00 (released 9/2024)

Catalog Number Studio 5000 Logix Designer 

These release notes describe version information for Studio 5000 Logix Designer, version 37.00.00 (released 9/2024).

Features

This release includes the following system features.

Support for Concurrent Communication Protocol Enhancements

Feature

IMPORTANT:

If you update any part of the system before all versions and revisions are available to be upgraded at the same time, you will get error code 16#0008 Service Request Error: Unsupported service.

For more information, see section Error Codes below.

An attempt to install a Logix SIS Redundancy or GuardLogix 5580 controller application will result in error code 16#008 Service Request Error: Unsupported service. If you see this error with either of these applications, you cannot clear it until the required FLEXHA 5000 EtherNet/IP adapter and FLEXHA 5000 I/O module firmware revisions are available.


If you are using Concurrent Communication, your system must meet the following requirements:

Components
Software Version
Firmware Revision
Software
Studio 5000 Logix Designer®
37.00.00 or later
—
FactoryTalk® Linx
6.31.00 or later
—
ControlFLASH Plus™
5.00.00 or later
—
ControlLogix 5580 Redundancy System
ControlLogix 5580 controllers
—
37.011 or later
1756-EN4TR ControlLogix EtherNet/IP™ communication modules
—
7.001 or later
FLEXHA 5000 I/O System (5015)
FLEXHA 5000 EtherNet/IP adapter
—
3.011 or later
FLEXHA 5000 I/O modules
—
3.011 or later
  
Components
Software Version
Firmware Revision
Software
Studio 5000 Logix Designer
37.00.00 or later
—
FactoryTalk Linx
6.31.00 or later
—
ControlFLASH Plus
5.00.00 or later
—
ControlLogix 5580 System
ControlLogix 5580 controllers
—
37.011 or later
1756-EN4TR ControlLogix EtherNet/IP communication modules
—
7.001 or later
FLEXHA 5000 I/O System (5015)
FLEXHA 5000 EtherNet/IP adapter
—
3.011 or later
FLEXHA 5000 I/O modules
—
3.011 or later

  
  
Components
Software Version
Firmware Revision
Software
Studio 5000 Logix Designer
37.00.00 or later
—
FactoryTalk Linx
6.31.00 or later
—
ControlFLASH Plus
5.00.00 or later
—
Logix SIS Redundancy
GuardLogix® 5580 controllers
—
37.011 or later
1756-EN4TR ControlLogix EtherNet/IP communication modules
—
7.001 or later
FLEX 5000 Safety I/O System (5094)
FLEX 5000 EtherNet/IP adapter
—
6.011 or later
FLEX 5000 Safety I/O modules
—
Any
FLEXHA 5000 I/O System (5015)
FLEXHA 5000 EtherNet/IP adapter
—
3.011 or later
FLEXHA 5000 I/O modules
—
3.011 or later

IMPORTANT: You are not required to use both FLEX 5000 Safety I/O modules and FLEXHA 5000 I/O modules in Logix SIS Redundancy. The requirements are listed in case you use either or both.

  
Components
Software Version
Firmware Revision
Software
Studio 5000 Logix Designer
37.00.00 or later
—
FactoryTalk Linx
6.31.00 or later
—
ControlFLASH Plus
5.00.00 or later
—
GuardLogix 5580 System
GuardLogix 5580 controllers
—
37.011 or later
1756-EN4TR ControlLogix EtherNet/IP communication modules
—
7.001 or later
FLEX 5000 Safety I/O System (5094)
FLEX 5000 EtherNet/IP adapter
—
6.011 or later
FLEX 5000 Safety I/O modules
—
Any
FLEXHA 5000 I/O System (5015)
FLEXHA 5000 EtherNet/IP adapter
—
3.011 or later
FLEXHA 5000 I/O modules
—
3.011 or later

IMPORTANT: You are not required to use both FLEX 5000 Safety I/O modules and FLEXHA 5000 I/O modules in GuardLogix 5580 control systems. The requirements are listed in case you use either or both.


Error Code

If you attempt to upgrade or install a ControlLogix Redundancy System or ControlLogix 5580 controller application and see error code 16#0008 Service Request Error: Unsupported service, you must revert the system to the following software version and firmware revisions.

Component
Software Version
Firmware Revision
Studio 5000 Logix Designer® software
35 or 36 (all versions)
—
ControlLogix 5580 Redundancy System
or
ControlLogix 5580 controller
—
35 or 36 (all revisions)
1756-EN4TR ControlLogix EtherNet/IP communication modules
—
5 or 6 (all revisions)
FLEXHA 5000 EtherNet/IP adapter
—
 2 or earlier (all revisions)
FLEXHA 5000 I/O modules
—
2 or earlier (all revisions)


For more information, see the following:

  

Corrected Anomalies in This Release

This release corrects the following anomalies.

 
 
Studio 5000 bit references to BOOL tags in UDT change after upload (3989388)

In Studio 5000, the references to BOOL array tags in UDTs will change to a different index of the array after uploading from Logix 5570 and 5370 family controllers.
This anomaly first identified in Logix Designer version 32.00.

  
ALMA/ALMD MinDurationACC tag (1529656, 1529657, 2065509)
The ALMA/ALMD MinDurationACC tag description in the online help requires this updated description:

Indicates the current accumulator value for the alarm’s MinDuration timer. Starting in version 29.00 of the Studio 5000 Logix Designer application, this value is no longer used. Value is always 0.
This anomaly will not be corrected in the online help for versions earlier than v36.00. This anomaly first identified in version 33.00.
Partial AOI import sometimes fails to create Alarm (3115573, 2223611)

The Logix Designer application sometimes fails to create an alarm when you do a partial import for an Add-On Instruction (AOI) that contains the alarm. To work around this issue, export and then import the affected project.
This anomaly first identified in version 31.00.
Cannot update value for tag member in DT and LDT data types (2363908)

You can expand and display the bit members for tags using the DT and LDT data types, but you cannot change the values for the bit members. This is expected behavior.
This anomaly first identified in version 36.00.

Selecting Go to Cross Ref prompts Save All (3064189)

When you open a project in the Logix Designer application, select Go to Cross Reference for a tag, and then close the project, the Logix Designer application asks you to save changes even though the project has not changed.

There is no workaround for this issue.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

Opening Extended Properties for new UDT can freeze Logix Designer (3121716)

The Logix Designer application sometimes locks up when you create a new data type and select graphic for one of the properties. To work around this issue, hover your cursor over the application icon in the taskbar and close the empty dialog.
This anomaly first identified in version 36.00.
 

Fatal Error 0xc0000005 on Import from L5X (3161896)

If an application was generated in an XML editor and a move instruction (MOV/MOVE) was created with an empty/missing operand, a Fatal Error occurs on import of the L5X file.

Example of text that would cause the Fatal Error on import:

Example of text that would not cause the Fatal Error on import:

NOTE: The fatal error does not occur when importing L5X created with Logix Designer because the software inserts a “?” in place of the missing operand.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

Toggle Inline Value Display feature can cause Logix Designer to shut down (3818739) 

The Logix Designer application can become unresponsive or shut down when you use the Toggle Inline Value Display setting while these conditions are true:

The error can occur when you are either offline or online with the controller. 

This anomaly corrected in version 37.00.

This anomaly first identified in version 31.00.

Uploading a project from the controller sometimes fails (3314529)

When you attempt to upload a project from a controller running Logix Designer versions 34, 35, or 36, the upload sometimes fails. This anomaly corrected in version 37.00.
This anomaly first identified in version 34.00.
Compiler Error When Locking a License-based Source Protected Routine or AOI (3358813)

A compiler error, Complier Error(0x0A), Call technical support, appears when trying to lock a license-based source protected routine, where at least one InOut parameter is missing a required connection and that InOut parameter is used in the routine that is being source protected and locked.
To work around this anomaly, perform a Controller Verify or Build of the project to determine if any InOut Parameter are missing required connections. This anomaly corrected in version 37.00.
This anomaly first identified in Logix Designer version 32.00.
"Not enough graphic resources" error when performing a search and replace on a tag (3209190)

When you attempt to search and replace a tag name used in multiple programs, the Logix Designer application sometimes displays an error that states "Not enough graphic resources" and sometimes becomes unresponsive.
To work around this anomaly, intermittently close out tag editor windows during the Search and Replace action to free graphic resources. This anomaly corrected in version 37.00.
This anomaly first identified in version 31.00.
Unexpected Verification Error on a Signed Structured Text Add-on Instruction (3332140)

The verification error, “Invalid signature ID. Reseal instruction to resolve.” is reported for a Structured Text Add-on Instruction (AOI) that contains a signature and a nested, unsigned AOI. The error appears after edits are made to the unsigned, nested AOI.
To get past the verification error, the signature must be removed and re-added to the AOI with the reported error. This anomaly corrected in version 37.00.
This anomaly first identified in version 28.00.
Radix Change on Project Upload for Hidden Members of UDT (3084749)

By default, hidden members within a User-defined Data Type (UDT) are defined with a decimal radix. This can be changed in the L5X export of a UDT to another supported radix type.
On project upload, the hidden member tag’s radix would change back to the default decimal style format. This does not affect UDT tag data but could be flagged as a difference when comparing copies of the project file using text comparison tools.

NOTE: If the UDT is edited within the Logix Designer application, this will also cause the tag’s radix to change back to a decimal style format. Avoid editing the UDT within the Logix Designer application if you prefer an alternative radix for the hidden members.


This anomaly corrected in version 36.05, and 37.00.

This anomaly first identified in version 20.00.
Fatal Error 0xc000005 EXCEPTION_ACCESS_VIOLATION on Upload

The Fatal Error occurs on upload if there previously was an Add-on Instruction (AOI) that matched the naming convention from the IEC 61131-3 standard, and that AOI was removed from the project prior to downloading.
To prevent the anomaly, avoid creating AOI mnemonics matching the naming convention from the IEC 61131-3 standard. This anomaly corrected in version 37.00.
This anomaly first identified in version 34.00.

Data type fails to change when using certain EDS AOPs (3690460, 3613600)

The following could occur for EDS AOP devices that use a one-dimensional array, with only one element for the input or output tag in their configuration:

This anomaly has been corrected in the Add-on profile Core released with Logix Designer version 37.00. This anomaly first identified in version 31.00.
Fatal Error When Updating EDS AOP Datatypes (3748086)

A Fatal Error could occur when you select the Upgrade Data Types… button for certain EDS AOP device configurations. The Upgrade Data Types… button is present on the device’s profile if the project environment has been upgraded to support unsigned datatypes. This support was added with the release of Studio 5000 Logix Designer version 36.00.
To work around this anomaly, remove and re-add the EDS AOP device to the I/O configuration, which will upgrade the datatype. This anomaly corrected in version 37.00.
This anomaly first identified in version 34.00.
EDS AOP Module Tags Do Not Reflect Module Definition (3228412)

When you create a new device in the I/O configuration, the module tags in the Controller Tag browser do not reflect the defined module definition.

This can also affect Logix Designer applications with EDS AOP devices that are upgraded to Logix Designer versions 34.00 and later, if Logix Designer version 36.00 or later is installed.
This anomaly is related to the EDS Subsystem installed with Logix Designer version 36.00. This issue only affects EDS AOP devices in 5380/5480/5580 controller applications.
This anomaly corrected in version 37.00.

See technote BF30248 for additional information.
Adding third-party devices to an I-O Link application sometimes causes Logix Designer to error (3598596)

When you add certain third-party devices to a 5032 I-O Link Master application, Logix Designer could display a Fatal Error or an Invalid Name error, preventing the device from being added to the configuration.
This anomaly corrected in version 37.00. This anomaly first identified in version 35.00.
Logix Designer version 36.00 installer fails to install AOP Core when GuardLink EIP Scanner AOP is already installed (3193234, 3185534)

When a Guardlink EIP Scanner 432ES AOP version 1.00.34 is already installed on your Logix Designer workstation and you attempt to install version 36, installation errors occur and the installer fails to install AOP core files.
To work around this issue, uninstall the GuardLink EIP Scanner AOP from your Logix Designer application before installing version 36.00. For more information, see this Knowledgebase article.
This anomaly corrected in version 37.00. This anomaly first identified in version 36.00.
Event Clear Log button and Display Timestamps are disabled for 5032 IO-Link master and 42AF devices (3127835)

When you open the device configuration page with a 5032 IO-Link Master running with a 42AF IO-Link device at default settings, the Clear Log button on the Event Log page is sometimes grayed out.
This anomaly corrected in version 37.00.

This anomaly first identified in version 36.00.
Host Words Missing from EDS AOP Module Tags (3597705)

In 5380, 5480, and 5580 controller applications, the Host Words in a tag configuration could be excluded from an EDS AOP device’s Input, Output, and/or Configuration tags. The individual programming bits are still visible.
This anomaly has been corrected in the Add-on profile Core released with Logix Designer version 37.00. This anomaly first identified in version 34.00.

Partial AOI import sometimes fails to create Alarm (3115573, 2223611, 2223616)

The Logix Designer application sometimes fails to create an alarm when you do a partial import for an Add- On Instruction (AOI) that contains the alarm.
To work around the issue, export and then import the affected project. This anomaly corrected in version 33.04.

This anomaly first identified in version 33.00.

ALMA/ALMD MinDurationACC tag (1529656, 1529657, 2065509)
The ALMA/ALMD MinDurationACC tag description in the online help requires this updated description:
Indicates the current accumulator value for the alarm’s MinDuration timer. Starting in version 29.00 of the Studio 5000 Logix Designer application, this value is no longer used. Value is always 0.
This anomaly will not be corrected in the online help for versions earlier than version 37.00. This anomaly first identified in version 33.00.

Known Anomalies in This Release

This release has the following known anomalies.

Safety IO modules mistakenly appear as available for standard projects on networks configured for Concurrent Communications (3835539)

On networks configured for Concurrent Communications, when you create a project for a standard controller and attempt to add an I/O module, safety I/O modules appear in the list of available modules. However, safety I/O modules are not supported in standard controller projects, and an error appears when you add one:
Failed to create module. An invalid field name was used in a query string.

To work around this issue, do not add safety I/O modules to standard projects. This anomaly first identified in version 36.00.
Toggle Inline Value Display Feature Causes Slow Software Performance (3323352)
Using the Toggle Inline Value Display feature in a Structured text routine can slow software performance when toggling the value display on or off. After many repeated toggles of the value display, the software may become unresponsive.
This anomaly first identified in version 31.00. This anomaly corrected in version 37.00.
FLEXHA 5000 EtherNet/IP adapter shows Execution Failed message when value set in IP Module A/B Category (3738348)
An anomaly occurs when you use a FLEXHA 5000™ EtherNet/IP™ adapter in a Logix Designer project, version 37.00 or later, when you complete these steps:
  1. Add a 5015-AENFTXT adapter, firmware revision 3.011, to a Logix Designer application project, version 37.00 or later.
  2. On the Connection category, inhibit the connection to the module.
  3. Manually change any value except the IP address or Host Name.
  4. Attempt to apply the changes. The attempt fails, and an Execution failed message (16#0C) appears.
Uninhibit the connection to the adapter to resume normal operation. After the adapters resume normal operation, the changes are not applied, and the adapters behave as before the attempted change.
“Profile not found” with Armor PowerFlex AOP v1.03 after installation of version 37.00 (3813135)

After you install Logix Designer version 37.00 when using version 36.00 or any earlier version of Logix Designer present on the workstation, attempting to open or add to the project the Armor PowerFlex AOP causes an error: Profile not found.
This error occurs after any other AOP had been opened or added to the project prior to Armor PowerFlex AOP.

This anomaly first identified in version 37.00, but is applicable to version 33.00 and later after installing version 37.00. This anomaly is not present in version 33.00 and later until installation of 37.00 occurs.

Known Anomalies from Previous Releases

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

Fatal error when trying to create a tag for an undefined program (3907641)

The Logix Designer application experiences a fatal error when attempting to create a tag for an undefined program.

This anomaly first identified in version 36.00.

Message instruction cache connections option displays incorrectly while offline (4166301, 4166302, 4166303, 4166304, 3995824)
If a Message instruction’s Control tag is defined as program-scoped and the options in the Message configuration > Communication tab for Connection is checked and Cache Connections is unchecked, going offline the ACD file will erroneously indicate that both of these options are checked. Performing a save of the application while online will not correct this.
If the offline ACD file is downloaded to the controller, message instructions that have the Cache Connections checkbox unchecked will now have them checked.
This issue only affects 5380, 5480 and 5580 controllers.
To work around this issue, in the application code use an OTU instruction to reset the EN_CC bit in the message control tag.
This anomaly corrected in versions 34.05, 35.04, 36.03, 37.02.
This anomaly first identified in version 32.00.
Upload failure of the application when structured text comments contain specific combination of characters (4006663)

If a Structured Text routine contains a comment which utilizes nested square brackets “[]“and a greater than “>” character immediately following them, Logix Designer will fail the upload from the controller, and you will receive the following error:
Error: Logic reconstruction data may be corrupted

An example of this comment syntax that will cause the upload to fail is as follows:

//[commen[t]]>

This anomaly only affects Structured Text routines in 5380, 5480 and 5580 controllers.

If this type of syntax is required, reduce the number of square brackets and/or remove the greater than character at the end of the comment. For example, the following comment syntax will allow the upload to succeed:
//c[ommen[t]]

//[comme[n]t]>

This anomaly first identified in Logix Designer version 33.00.
Polish special character cannot be added (4004303, 5389633, 5389622)

Using a keyboard to add the Polish character “ą” in the Tag Description popup selects all text in the popup box. The character can be typed in other Tag Description fields.
This anomaly corrected in Logix Designer version 36.05, 37.04, and 38.02.
This anomaly first identified in Logix Designer version 33.00.

High CPU and memory usage in Structured Text (4121969, 4121971, 4004601, 4121967, 4121973)

The Logix Designer application consumes more memory and CPU resources than normal and can go into a “Not Responding” state when inline values are enabled in Structured Text.

This anomaly corrected in versions 34.05, 35.04, 36.04, 37.03.

This anomaly first identified in version 33.00.

Unable to use 1732 or 1734 IO-Link Master with specific IO-Link devices (3652014)
A .NET error or Fatal Error may occur when configuring certain IO-Link devices with the 1732E-8IOLM12R or 1734-4IOL IO-Link Masters. These errors include:
These issues are associated with device IODD files based on IO-Link specification 1.1.3 or later. The 1732 and 1734 IO-Link Masters are designed to be compatible with IO-Link specification version 1.1.2.

To work around this anomaly:

A resolution is available for the 1734-4IOL in v3.00.04 of the 1734-4IOL Add-on Profile (AOP) allowing support for a IODD file that is based on IO-Link specification version 1.1.3.
To prevent the Fatal error, use the IODD file that supports IO-Link version 1.1. This anomaly first identified in version 35.00.

​Anomalous behavior when editing a large Structured Text routine (3838969)

​When editing a large Structured Text routine with outlining, the following issues might occur:

​This anomaly first identified in version 32.00.

When enabling SFC forces, the system displays erroneous information (4041343)

When enabling SFC forces under the following conditions:
Studio 5000 Logix Designer application displays this message:
"Failed to enable SFC forces in the controller. Controller not in correct mode."
Similarly, when attempting to disable SFC forces, the following message appears:
"Failed to disable SFC forces in the controller. Controller not in correct mode."
Additionally, the FORCE LED on the front of the controller does not light up amber.

Despite these messages, SFC forcing functions as expected.

This anomaly first identified in version 33.00.

For more information on when this anomaly was corrected, see the controller firmware release note When enabling SFC forces, the system displays erroneous information

Firmware kit notification during installation of Studio 5000 Logix Designer application (3217771)

During Studio 5000 Logix Designer application installation, a pop-up notification appears indicating the presence of a pre-installed ControlLogix Hydraulic Control Module firmware kit. Acknowledge the notification to continue the installation. 

This notification typically appears when upgrading from a minor software version to versions 34.00 or 35.00. 

There is no workaround to prevent this notification during a silent installation.

This anomaly first identified in version 34.02. 

Safety IO modules incorrectly appear as selectable in standard controller projects in LogixDesigner version 36 (3679519, 3835539)
In Logix Designer version 36, Safety IO modules incorrectly appear as selectable in standard controller projects. This anomaly does not occur in version 37 or 38.
This anomaly first identified in version 36.00.
In 5094-IF8IH Modules, fault input does not indicate a fault on some channels (1313229)
In 5094-IF8IH Modules, during network cable breaks or MP power loss, a fault input does not indicate a fault on some channels. This anomaly first identified in version 34.00.

Upload failure (1024944)

When attempting to upload a project, the Logix Designer application generates these errors and the upload fails:

  • Error code: 731-0
Failed to upload project. Reverting to the last saved copy of [location and file name]
  • Error: [Routine Name]: Logic reconstruction data may be corrupted (displays in Error pane).

To work around this issue, remove long names from the project.

This anomaly first identified in version 32.00.

Tag based alarm does not create on import (1093641)

If Logix based alarms are not verified or created when importing a User-defined Data Type (UDT) that references them, users will experience a controller major non-recoverable fault (MNRF) after download.

This anomaly first identified in version 33.00.

The Logix Designer stops responding when copying motion axes (1170662)

When copying and pasting motion axes between motion groups, the Logix Designer stops responding.

This anomaly first identified in version 32.00.

Public parameter imports as a local tag (910972, Lgx00231568, Lgx00231638, Lgx00231000)

When importing and exporting programs or routines with Public program parameters between projects, the program or routine causes the parameter to appear undefined.

This anomaly first identified in version 32.02.
Tag Browser may disappear when the Watch view is in Auto Hide mode (Lgx00216392)

The Tag Browser may disappear behind the Watch view preventing the user from selecting a tag. This can happen when the Watch view is in Auto Hide mode, the user opens the Tag Browser from the Watch view, and the Tag Browser appears outside the Watch view.

This anomaly first identified in version 32.00.

Use one of these steps to work around the issue:

  • Dock the Watch view by selecting graphic in the Watch title bar.
  • Float the Watch view by selecting graphic in the Watch title bar and selecting Float.

Size the Watch view so the Tag Browser fits inside the Watch view.

Hyperlinks in Vendor Sample Projects.pdf file may not work (Lgx00215047)

Some browsers (particularly the Microsoft Edge browser) may not launch the hyperlinks in the Sample Projects.pdf file when the hyperlinks are configured to open PDF files.   

This anomaly first identified in version 32.00

To work around this issue, open the PDF file with Adobe Acrobat Reader:

  • Right-click the Vendor Sample Projects.pdf file and select Open with Adobe Acrobat Reader.
Logix Designer application runs out of memory with Accelerate 3D Graphics selected in VMware (Lgx00216060)

The Accelerate 3D Graphics setting in VMware sometimes causes the Logix Designer application to run out of memory.

This anomaly first identified in version 32.00.

Use one of these steps to work around this issue:

  • In VMware, turn off the Accelerate 3D Graphics setting.
  • Modify VMware Tools and remove the offending VMware SVGA 3D. This causes the display adapter to revert to Microsoft Basic Display Adapter mode.
  • Upgrade VMware Workstation to version 15, which uses VMware SVGA 3D driver v8.16.1.1.
Selecting all consumed tags causes the Logix Designer application to freeze (Lgx00217420, Lgx00217421, Lgx00217422, Lgx00217118)

In the Tag Editor with Show: Consumed tags displayed, selecting all the consumed tags can cause the Logic Designer application to freeze.

This anomaly first identified in version 32.00.

  • To work around this issue, press Esc. When an error message window appears that asks Do you want to abort the operation, select Yes.
Multiple routines left open for over two days while online with the controller can cause the Logix Designer application to crash (Lgx00217902, Lgx00217946)

Leaving multiple routines open for over two days while online with the controller can cause the Logix Designer application to crash.

This anomaly first identified in version 32.00.

Subroutine called by locked routine through JSR instruction might not show energized power rail (Lgx00218331)

When a locked routine uses a JSR instruction to call a subroutine, Logix Designer sometimes fails to display the power rails in the subroutine as energized. The problem is limited to the incorrect display; the execution flow in the controller is still correct.

This anomaly first identified in version 32.00.

Labels are cut off and dislocated in BOOTP-DHCP Server applications (Lgx00152848)

When the font size in Windows 7 is set to 125%, the labels in the Network Settings and DHCP properties of BOOTP-DHCP Server application are cut off, making them unreadable. They are also dislocated, where they do not match with the proper input fields.

This anomaly first identified in version 23.00.

Input controller tag value after cable break varies (1494865, 1494862, 1494859)
The input controller tag values after a cable break varies based on the channel value at the last inhibition and uninhibition action. This anomaly first identified in version 33.00.

Error in the content of Studio 5000 Logix Designer application generated reports (1421415)

"ACD filename - Label does not exist" appears at the top of the page instead of "ACD filename - Controller Organizer Listing" when using the Generate Report menu option. 

This anomaly first identified in version 33.00.

Fatal error when converting a project to a newer major revision (1476922)]]]
A fatal error sometimes occurs when converting a project to a newer major revision where issues exist in the ChangeLog.
To work around this issue, export from the older project to a .L5K or .L5X file and import the project to a newer major revision to avoid the fatal error.
This anomaly first identified in version 16.00.

Editing Operand Description sometimes results in unexpected display behavior (1354684)

When the same tag description exists on many branches that span an area that extends beyond what is visible on a display and the tag description is edited, the content on the display sometimes jumps upon acceptance of the tag description edit. 

Using the left or right arrow keys causes the screen to focus on the tag description that was just edited.

The anomaly does not occur when the tag description is edited for the rung where the contacts are unique because the tag description only exists in one location.

This anomaly first identified in version 20.00.

Storing Firmware Supervisor files from PowerFlex 755T causes the <ST5LD>  application to stop responding (1518416)

Attempting to store Firmware Supervision files for PowerFlex 755T devices causes the <ST5LD> application to stop responding. The application must be closed using Task Manager.

This anomaly was first identified in version 33.00.

Error when attempting to run a trend (1435208)
The Logix Designer application is unable to run a trend in v29 or earlier after switching communication software from RSLinx Classic to FactoryTalk Linx in another instance of the Logix Designer application v31 and later on the same workstation.
Once a trend is run in the Logix Designer application v31 and later, using FactoryTalk Linx as the communication software, you will receive this error message if you then attempt to run a trend in the Logix Designer application v29 or earlier on the same workstation:
Error: <trend name> - : Can’t open the specified RSLinx driver. For more information, refer to the technical note BF23206.
This anomaly first identified in version 20.00.
This anomaly resolved in version 38.00.
Trends display steps instead of linear line (1093987)

Trends show steps instead of linear line while executing quantums larger than 10ms. Part of trends use physical time instead of virtual time. This anomaly first identified in version 33.00.
Unable to upload project from PLC (1489327)
The Logix Designer application stops performing with attempting to upload a project from the controller on a sequence diagram. For details about this issue, see Tech Note BF28540.
This anomaly first identified in version 34.00.

Can create safety I/O module successfully when Safety Modify Component set to deny (1787414)

You can successfully create an Add-On Profile based safety I/O module without errors when FactoryTalk Security user privileges's Safety Modify Component is set to Deny.

This anomaly first identified in version 35.00.

Can create a 5015-AENFTXT under the 1756-EN2TSC I/O configuration (1882887)
When creating a module under 1756-EN2TSC, 5015-AENFTXT is listed in available modules and can be created successfully. 5015-AENFTXT should only appear under adapters that support concurrent connections, such as 1756-EN4TR major revision 4. Communication between 1756-EN2TSC and 5015-AENFTXT is not supported and will not function.
First reported in version 35.00 and AOP version 28.04.

Direct Add-on-Profile-to-Device Communication Could Result in Time Out Errors or Communication Routing to the Wrong Device (1927272)

Direct Add-on-Profile-to-device communication could result in time out errors or routing the communication to the wrong device in circumstances where all of the following conditions are met:

This applies to configuration data that goes through unconnected communication to the target I/O device (for instance, uploading/downloading device parameters).

This does not apply to I/O data.

This does not apply to commands from the controller (for instance, inhibiting/uninhibiting a device).

Please see technote BF28941 for additional details.

This anomaly first identified in version 20.00.

Removed KNOptimassMfc400 profile (2106380)

The KN profile no longer has a license in the Logix Designer application.

This anomaly first identified in version 32.02.

Some Catalog numbers not displaying correctly in Module Discovery (2001084)

After creating a new L85E v35 project with a 5032 I/O-Link bridge device connected to the Ethernet bus and enabling at least one channel for the I/O-Link, connect Siemens-K20-4DI IO-Link device with the 5032 I/O-Link bridge module, and download the project. Launching Module Discovery from the I/O-Link bus shows some Catalog numbers do not display correctly.

This anomaly first identified in version 35.00.

I/O-Link Module Discovery displays 17.00 (100,1.1001) (1848106)

When creating an L85E project and adding a 5032-Master, after configuring some channels to I/O-Link and downloading the project, launch Module Discovery from the I/O-Link bus. The Revision column shows 17.000 for the I/O-Link devices instead of the expected 1.1 or 1.0.

This anomaly first identified in version 35.00.

L5K file with I/O Device cannot be imported (2047005)

When creating an L85E project using a 5032 master profile on the Ethernet bus and adding the I/O-Link device 42AF-R1MAB1-xx[209] with default setting on the I/O-Link bus, the error Unexpected end of file encountered occurs and the import is not successful.

This anomaly first identified in version 35.00.

Mismatching display resolution and scaling may result in overlapping SFC elements (2122642)

Editing a Sequential Function Chart (SFC)) using a display with a given resolution (for example, 1920 x 1200) and Windows scale setting (for example, 100%), closing the ACD, and then opening the same ACD in another resolution (for example, 3840 x 2160) and Windows scale setting (for example, 150%) may result in overlapping SFC elements.

Studio 5000 Logix Designer Ladder Diagram routines may stop execution after download (2047296)

Studio 5000 Logix Designer ladder diagram routines may stop execution after download to ControlLogix 5580, GuardLogix 5580, CompactLogix 5380, 5480 and Compact GuardLogix 5380 controllers. See Product Notice ID: PN1620 for the specific sequence of events to experience this anomaly.

This anomaly first identified in version 31.00.

Removed KNOptimassMfc400 Add-on profile (2106380)

The KNOptimassMfc400 device Add-on profile is no longer included with the Logix Designer application. This anomaly first identified in version 32.02.

Using specific set of characters in structured text outlining comment, will cause an upload failure into a blank project ACD file (2207451)

Using the ** set of characters with a single-line comment (//) (that is, //**) in a structured text outlining comment (#region\#endregion) causes an upload error into a blank ACD file. The ** characters are used for multi-line comments and using the ** characters with a single-line comment causes this anomaly to occur. 

To work around this issue, put double quotes around the ** characters, such as “**”.

This anomaly first identified in version 31.00.

Attempting to access a controller through a blocked path can freeze the interface (2362117)

When CIP Security is configured, you can access the controller only through the Ethernet port. When you attempt to access the controller through a path blocked by CIP security, the Logix Designer application appears to freeze.
To work around this issue, hover your cursor over the application icon in the taskbar and close the hidden dialog. This anomaly first identified in version 36.00.
Logix Designer version 36.00 installer fails to install AOP Core when GuardLink EIP Scanner AOP is already installed (3185534)
When a Guardlink EIP Scanner 432ES AOP version 1.00.34 is already installed on your Logix Designer workstation and you attempt to install version 36, installation errors occur and the installer fails to install AOP core files.
To work around this issue, uninstall the GuardLink EIP Scanner AOP from your Logix Designer application before installing version 36.00. For more information, see this Knowledgebase article.
This anomaly first identified in version 36.00. This anomaly corrected in version 38.00.

Project Path setting is ignored (3855364)
The Logix Designer application ignores changes to the directory path in the Project Path setting on the Workstation Options dialog. When you modify the default project path, C:\Users\UserName\Documents\Studio\Studio 5000\Projects, the new path does not appear in the Save As dialog, the Open dialog, and the Location field when you create a new file. Also, project backup files continue to be stored in the same directory as the opened .ACD file.
There is no workaround to this issue.

This anomaly first identified in Logix Designer version 31.00.

Error 46477-80042111 Not enough graphics resources cause fatal error (2373621, 3230963, 3230959)
Error 46477-80042111 Not enough graphic resources occurred when performing a search and replace on a tag name for tags used in multiple programs, followed immediately with a fatal error.
This anomaly corrected in version 32.05 and 33.04. This anomaly first identified in version 35.00.
Public parameter imports as a local tag (910972, Lgx00231568, Lgx00231638, Lgx00231000)
When importing and exporting programs or routines with Public program parameters between projects, the program or routine causes the parameter to appear undefined.
This anomaly first identified in version 32.02.

Application Notes

This release has the following application notes.

The Module Info tab within Module Properties will not return module information when utilizing FactoryTalk Linx

Viewing the Module Info tab of any device in the I/O configuration results in the following error:

Internal direct communications error. Call Technical Support.

This error will occur even when the module is connected and successfully communicating with the controller. The error will only occur when utilizing FactoryTalk Linx as the communication software package for Logix Designer.

This is not an anomaly in Logix Designer.

This anomaly in FactoryTalk Linx was addressed in a Patch Update for FactoryTalk Linx. See technote BF28781 for additional details.

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.