Release Notes

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

Catalog Number Studio 5000 Logix Designer 

These release notes describe version information for Studio 5000 Logix Designer, version 37.00.01 (released 1/2025).

Requirements

This release has the following requirements.

 
System requirements for Studio 5000 Logix Designer version 37.00
For optimal performance of the Logix Designer application, the personal computer should meet or exceed these hardware and software requirements.

graphic Tip: The Logix Designer application can be installed on a personal computer that meets the operating system minimum requirements but may not meet performance expectations when used in a production system.


Hardware requirements

Software requirements

NOTE: This release is not intended to run on a 32-bit operating system. All operating systems listed are the 64-bit variant.
  

IMPORTANT: Keep these operating system considerations in mind:
When installing the Logix Designer application on computers that have not been updated, a prompt displays to install Universal C Runtime or to update the computer to at least the Microsoft April 2014 update roll-up.
  
  

Preferred operating systems

Preferred operating systems are prioritized for support, testing, and post-release patch qualifications. These operating systems are preferred for this release:
High Resolution Display support

If running this software with a 2K or 4K High Resolution Display with scaling up to 125% you can expect acceptable results.

FactoryTalk Updater version 4.20.00 installation

Install one or more functionalities for FactoryTalk Updater.

NOTE: The FactoryTalk Updater Agent is included in the installation package for Logix Designer version 37. FactoryTalk Updater Server and FactoryTalk Updater Client are available in a separate installation package.

Agent

FactoryTalk Updater Agent collects information and activation license data from the Rockwell Automation software installed on the computer. Install the FactoryTalk Updater Agent on each computer that requires data collection. This is the default functionality installed with most Rockwell Automation software.
Server

FactoryTalk Updater Server:
Tip: To avoid issues, limit FactoryTalk Updater Server installations to one instance per intranet.
graphic

Client

FactoryTalk Updater Client is the user interface that displays information collected by the FactoryTalk Updater Server. Install FactoryTalk Updater Client to display information from the intranet.
Firmware requirements

NOTE: Tip: Most modules use Flash-ROM for the storage of firmware. If a module requires a firmware change, use the ControlFLASH™ tool or the ControlFLASH Plus® tool to perform the update to the Flash-ROM. These tools are contained in the downloaded image or on a DVD-ROM shipped with the Logix Designer application. Another option is to update the firmware automatically as part of the project download.
For additional information and assistance in performing a Flash-ROM update, review the ControlFLASH Firmware Upgrade Software User Manual,
publication 1756-UM105, or the ControlFLASH Plus Quick Start Guide, publication CFP-QS001.

Rockwell Automation test environment

Rockwell Automation tests software products under a standard configuration of operating systems and antivirus software. For additional information, see the Knowledgebase Document ID: PN24 - Rockwell Software Products and Antivirus Software.
  
 

Features

This release includes the following system features.

System features for Logix Designer version 37.00
Logix Designer application version 37.00 has these new and enhanced features.

New features
In this version of the Logix Designer application, you can activate redundancy on GuardLogix 5580 controllers.
In this version of the Logix Designer application, it is possible to turn on or off standard user-task-runtime-tag-data crossloading to achieve stable and repeatable scan times for the highest priority standard task. As a result, the Synchronize Redundancy Data after Execution option is now available for synchronizing redundancy data after execution.
In the Advanced Redundancy Configuration dialog box, the option Retain Test Edits on Switchover is now called Retain Test Edits in Standard Programs on Switchover for safety controllers.
This version of the Logix Designer application adds the ability to turn on OPC UA access for a controller port. This version of Logix Designer application also adds the ability to generate reports that describe the OPC UA enablement state of each port.
Use the new Instruction Toolbox to find and insert instructions into a routine. The Instruction Toolbox lists all the instructions that are supported in the logic editor you are using. Select an instruction to add it to a routine. Enter a term in the search box to find a specific instruction. The Instruction Toolbox appears for each logic editor and the legacy Language Element toolbar is now hidden by default.
Enhanced features
In this version of the Logix Designer application, CONCAT instruction performance is optimized for the case where one string is appended to another.
  • AOIs support data types containing alarm definitions as InOut parameters
In Logix Designer versions 37 and later, Add-On Instructions (AOIs) support the use of data types containing alarm definitions as InOut parameters. However, alarm conditions and alarm sets within these InOut parameters cannot be accessed programmatically at any level. Use InOut parameters with alarm definitions primarily for data transfer between AOI instances and calling logic.
For the SIZE instruction, scan time has been shortened and restrictions on data types for the input operand have been lifted.
Online help content for the Logix Designer application is now both installed on your computer and posted on Rockwellautomation.com, making it accessible in online searches. The online help content on Rockwellautomation.com will always contain the most up-to-date information.

graphic Tip: If you create bookmarks to specific pages in the help on Rockwellautomation.com, you will need to update them when you upgrade to a new version of the Logix Designer application.

Corrected Anomalies in This Release

This release corrects the following anomalies.

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.
“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 in This Release

This release has the following known anomalies.

Time Synchronization page shows no data for some languages on 1756-EN4TR devices (5246469)
The Time Synchronization page shows no data for 1756-EN4TR devices in the Logix Designer application localized for these languages:
To work around this issue, re-install the Logix Designer application using a language not affected by this problem.
This anomaly first identified in version 37.00.

Known Anomalies from Previous Releases

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

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.

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.


  

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.


A Message Instruction (MSG) Cache Connections option is not reflected properly while offline (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 first identified in Logix Designer version 32.00.
This anomaly corrected in version 38.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)

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 first identified in Logix Designer version 33.00.

  

​High CPU and Memory Usage in Structured Text (4004601)

​The Logix Designer application experiences elevated memory & CPU usage and can go into a “Not Responding” state when inline values are enabled in Structured Text.

​This anomaly first identified in version 33.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.
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.

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. 

Fatal Error when Accessing Controller Properties or a CAM Editor with a Structured Text Routine Open and Toggle Inline Values Enabled (3848611)

Fatal Error 0xc0000005 EXCEPTION_ACCESS_VIOLATION appears under the following conditions when Toggle Inline Values is enabled, and a Structured Text Routine is visible, and:

Workaround: To address this, refrain from performing the above actions while the Toggle Inline Values feature is enabled.

This anomaly first identified in version 32.00.00.


​

​​

​

​

​​

​


  
Safety IO modules incorrectly appear as selectable in standard controller projects in LogixDesigner version 36 (3679519)
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:

Failed to upload project. Reverting to the last saved copy of [location and file name]

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

This anomaly first identified in version 32.00.


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:

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:

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:

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.

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.

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

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.

Functional Changes

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

Functional changes for Logix Designer version 37.00
Logix Designer version 37.00 has these changes in functionality since the last release.

Online help is posted on Rockwellautomation.com

Online help content for the Logix Designer application is now both installed on your computer and posted on Rockwellautomation.com, making it accessible in online searches. The online help content on Rockwellautomation.com will always contain the most up-to-date information.

graphic Tip: If you create bookmarks to specific pages in the help on Rockwellautomation.com, you will need to update them when you upgrade to a new version of the Logix Designer application.

To set the Help page source in the Logix Designer application:
  1. On the main menu, select Tools > Options.
  2. For Help page source, select one of these options:
    • Always ask. When you first select Help in the Logix Designer application, a dialog asks whether to display locally installed help files or files on rockwellautomation.com. This is the default setting.
    • Local. Displays help files installed on the hard drive of the computer running the Logix Designer application.
    • Online. Displays the latest help content from rockwellautomation.com.

Enabling redundancy sets safety task priority to 1

Enabling redundancy affects the priority of the safety task:

No longer supporting the Emulate 5570 and other controllers with serial ports​

This version of the Logix Designer application no longer supports controllers with serial ports:

UsingLegacyMnemonics attribute converts legacy mnemonics to standard

When creating an import file independent of Logix Designer, use the new UsingLegacyMnemonics="true" attribute to convert legacy mnemonics to the standard mnemonics introduced in Logix Designer version 36. This attribute is most applicable in the following scenario:

Import/Export

The Import/Export version number for this version of the Logix Designer application is 2.28. The table lists the Import/Export versions for previous releases.
  
Release Version
Import/Export Version
37.xx
2.28
36.xx
2.27
35.xx
2.26
34.xx
2.25
33.xx
2.24
32.xx
2.23
31.xx
2.22
30.xx
2.21
29.xx
2.20
28.xx
2.19
27.xx
2.18
26.xx
2.17
24.xx
2.15
23.xx
2.14
21.xx
2.12
20.xx
2.11
19.xx
2.10
18.xx
2.09
17.xx
2.08
16.xx
2.07
15.xx
2.06
14.xx
2.05
13.xx
2.04
12.xx
2.03
11.xx
2.02
10.xx
2.01
9.00
2.00
5.02
1.02
2.xx, 6.xx, 7.xx, 8.xx
1.01
1.21, 1.23
1.00
1.10, 1.11
0.04


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.

Application notes for Logix Designer version 37.00

Constant property applied to a safety input tag can result in primary controller or safety partner (SIL3) assert during application save to nonvolatile memory

Configuring the safety input module tag property as Constant will result in a controller assert or safety partner assert when a safety signature has been configured.

The assert occurs when the controller application is saved to nonvolatile memory. A repeating controller assert occurs when you select load options “Uninitialized memory” or “On Power Up.”
Structured Text logical expression limited to only six operators

In the Structured Text editor, you can assemble only six OR statements in an expression. This issue first reported in version 36.00 as anomaly 3547261.
Armor PowerFlex Add-on profile is not included with Logix Designer version 37.00

Logix Designer version 37.00 does not include the Armor PowerFlex Add-on profile.

Logix Designer SDK Installation Error when Installing Studio 5000 Logix Designer PRO Edition

The following installation error could occur when installing Logix Designer SDK on an Operating System with language settings set to any language other than English.

An error occurred while applying security settings. Users is not a valid user or group. This could be a problem with the package, or a problem connecting to a domain controller on the network. Check your network connection and select Retry or Cancel to end the install.
To work around the error:
  1. In Windows Start, search for and open the Computer Management app.
  2. Select Local Users and Groups > Groups.
  3. Add a local Windows group and name the group Users.
  4. Add the logged in user to that Windows group.
  5. Reboot your computer and reattempt the install.
Logix Designer SDK v2.00 is included in the Studio 5000 Logix Designer Professional Edition installer for v37.00. This is not a Studio 5000 Logix Designer anomaly. But you can experience this issue when installing Studio 5000 Logix Designer and selecting the option to install the Logix Designer SDK.

Adding an EDS AOP device updates the Output module-defined datatype

For certain EDS AOP devices, when multiple devices are added to the I/O configuration, there will be a change to the Output module-defined data type created. The module-defined tags are identical, but the Output module-defined timestamp increments for each device created. This occurs for:
This issue affects environments that have upgraded to support unsigned datatypes. This support was added with the release of Studio 5000 Logix Designer version 36.00. This issue was first reported as anomaly 3592228. The anomaly has been addressed in the Add-on profile Core released with V37.00.

CIS Benchmarks test results
Studio 5000 Logix Designer v37.00 has been tested on:
Reference: Recommended guidelines for hardening software, computer, device, and network systems and infrastructure (CIS Benchmarks)

Mitigation for Microsoft DCOM Hardening patch

In response to Microsoft Distributed Component Object Model (DCOM) Hardening patch (MS KB5004442), the minimum DCOM authentication level used by Rockwell Automation products was raised to Packet Integrity.

IMPORTANT: Installing this product’s latest version with earlier unpatched versions of other FactoryTalk products or products using Classic OPC DA connections may cause a loss of connectivity due to the difference in DCOM authentication level used. For additional information, see the Knowledgebase Document ID: IN39461 - Microsoft DCOM Hardening Information TOC.


Microsoft releases the DCOM Hardening patch in response to CVE-2021-26414. This patch elevates the minimum DCOM authentication level that is required to establish a DCOM connection. DCOM is used by many Rockwell Automation products and may be affected by the change that is made by the Microsoft patch. For additional information about the affected Rockwell Automation products, see the Knowledgebase Document ID: PN1581 - Product Notification 2022-01-001 - Rockwell Automation products unable to establish proper DCOM connection after installing Microsoft DCOM Hardening patch (MS KB5004442).
Rung comments lost when going online with a controller

When going online with the controller with the Download Project Documentation and Extended Properties option cleared, online edits did not save after making online edits to Ladder Logic routines, saving and copying the project, going oNine, and then going online with the copied project. (Lgx00230263, Lgx00230366, Lgx00230369, Product Safety Advisory 2017-10-002)
Motion Import Tool version 3.0 required for importing CMF

You must upgrade to version 3.0 of the Motion Import Tool to import a Custom Motor File (CMF). Version 3.0 is required so that CMF/Motor Data can be imported into the MotionDB in the new admin location.
Security requirements

To help meet secure system design requirements, review these publications:
To learn about implementing CIP Security, see CIP Security with Rockwell Automation Products (publication SECURE-AT001).

Supported Logix controllers

While the programming software continues to extend its functionality with each new release, the physical controllers that it supports will vary. New controllers are added, and in some cases, support for existing controllers may be removed. While a specific controller may not be supported by the current release, the side-by-side installation of multiple versions of the software will, in most cases, provide a means to support the older hardware. If migrating from one controller to another, a project created for one controller can be easily converted to another controller using the Controller Properties configuration dialog box within the software.
If opening a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software will provide an appropriate warning and will automatically provide the option to convert the project to one of the controllers supported by the release.
The table provides a breakdown of the various Logix 5000 controllers and the initial or minimum version of Logix Designer application that is required to support the controller.
  
ControlLogix 1756-L71 Series B
20.00
ControlLogix 1756-L71S Series B
20.01
ControlLogix 1756-L72 Series A
19.00
ControlLogix 1756-L72 Series B
20.00
GuardLogix 1756-L72S Series B
20.00
ControlLogix 1756-L73 Series A
18.00
ControlLogix 1756-L73 Series B
20.00
ControlLogix 1756-L73XT Series B
20.00
GuardLogix 1756-L73S Series B
20.00
GuardLogix 1756-L73SXT Series B
20.00
GuardLogix 1756-L81ES Series A
31.00
GuardLogix 1756-L82ES Series A
31.00
GuardLogix 1756-L83ES Series A
31.00
GuardLogix 1756-L84ES Series A
31.00
GuardLogix 1756-L85ES Series A
36.00
GuardLogix 1756-L8SP Series A
31.00
ControlLogix 1756-L74 Series A
19.00
ControlLogix 1756-L74 Series B
20.00
ControlLogix 1756-L75 Series A
18.00
ControlLogix 1756-L75 Series B
20.00
ControlLogix 1756-L81E Series B
29.00
ControlLogix 1756-L81E-NSE
33.00
ControlLogix 1756-L81EP
33.00
ControlLogix 1756-L82E Series B
29.00
ControlLogix 1756-L82E-NSE
33.00
ControlLogix 1756-L83E Series B
28.00
ControlLogix 1756-L83E-NSE
33.00
ControlLogix 1756-L83EP
33.00
ControlLogix 1756-L84E Series B
29.00
ControlLogix 1756-L84E-NSE
33.00
ControlLogix 1756-L85E Series B
28.00
ControlLogix 1756-L85E-NSE
33.00
ControlLogix 1756-L85EP
33.00
CompactLogix 1769-L16ER-BB1B Series A
20.00
CompactLogix 1769-L16ER-BB1B Series B
20.00
CompactLogix 1769-L18ER-BB1B Series A
20.00
CompactLogix 1769-L18ER-BB1B Series B
20.00
CompactLogix 1769-L18ERM-BB1B Series A
20.00
CompactLogix 1769-L18ERM-BB1B Series B
20.00
CompactLogix 1769-L19ER-BB1B
28.00
CompactLogix 1769-L24ER-QB1B
20.00
CompactLogix 1769-L24ER-QBFC1B
20.00
CompactLogix 1769-L27ERM-QBFC1B
20.00
CompactLogix 1769-L30ER
20.00
CompactLogix 1769-L30ER-NSE
20.00
CompactLogix 1769-L30ERM
20.00
CompactLogix 1769-L33ER
20.00
CompactLogix 1769-L33ERM
20.00
CompactLogix 1769-L37ERM
31.00
CompactLogix 1769-L38ERM
31.00
CompactLogix GuardLogix 1769-L30ERMS
28.00
CompactLogix GuardLogix 1769-L33ERMS
28.00
CompactLogix GuardLogix 1769-L36ERMS
28.00
CompactLogix GuardLogix 1769-L37ERMS
31.00
CompactLogix GuardLogix 1769-L37ERMOS
30.00
CompactLogix GuardLogix 1769-L38ERMS
31.00
CompactLogix 1769-L36ERM
20.00
CompactLogix 1769-L37ERMO
30.00
CompactLogix 5069-L306ER
29.00
CompactLogix 5069-L306ERM
29.00
CompactLogix 5069-L306ERMS3
32.00
CompactLogix 5069-L310ER
29.00
CompactLogix 5069-L310ERM
29.00
CompactLogix 5069-L310ERM-NSE
29.00
CompactLogix 5069-L310ERMS3
32.00
CompactLogix 5069-L3100ERM
30.00
CompactLogix 5069-L3100ERMS3
32.00
CompactLogix 5069-L320ER
28.00
CompactLogix 5069-L320ERMS3
32.00
CompactLogix 5069-L320ERM
32.00
CompactLogix 5069-L320ERP
33.00
CompactLogix 5069-L330ER
29.00
CompactLogix 5069-L330ERM
29.00
CompactLogix 5069-L330ERMS3
32.00
CompactLogix 5069-L340ER
29.00
CompactLogix 5069-L340ERM
28.00
CompactLogix 5069-L340ERMS3
32.00
CompactLogix 5069-L340ERP
33.00
CompactLogix 5069-L350ERM
30.00
CompactLogix 5069-L350ERMS3
32.00
CompactLogix 5069-L360ERMS3
32.00
CompactLogix 5069-L380ERM
30.00
CompactLogix 5069-L4100ERMW
32.00
CompactLogix 5069-L4200ERMW
32.00
CompactLogix 5069-L430ERMW
32.00
CompactLogix 5069-L450ERMW
32.00
CompactLogix 5069-L46ERMW
30.00
Compact GuardLogix 5069-L306ERMS2
31.00
Compact GuardLogix 5069-L306ERMS3
32.00
Compact GuardLogix 5069-L310ERMS2
31.00
Compact GuardLogix 5069-L320ERMS2
31.00
Compact GuardLogix 5069-L330ERMS2
31.00
Compact GuardLogix 5069-L340ERMS2
31.00
Compact GuardLogix 5069-L350ERMS2
31.00
Compact GuardLogix 5069-L380ERMS2
31.00
Compact GuardLogix 5069-L3100ERMS2
31.00
Compact GuardLogix 5069-L306ERS2
31.00
Compact GuardLogix 5069-L310ERS2
31.00
Compact GuardLogix 5069-L320ERS2
31.00
Compact GuardLogix 5069-L330ERS2
31.00
Compact GuardLogix 5069-L340ERS2
31.00
Compact GuardLogix 5069-L350ERS2
31.00
Compact GuardLogix 5069-L380ERS2
31.00
Compact GuardLogix 5069-L3100ERS2
31.00

Launching with Ctrl + Shift does not reset Controller Organizer

One method to restore or reset Workstation Options is to hold Ctrl + Shift, launch the Logix Designer application, and continue to hold Ctrl + Shift until the application is fully launched.
However, when this restore method is used and the Windows User Account Control (UAC) setting is set at a level higher than Never notify, a UAC dialog box sometimes appears containing the following message:
Do you want to allow this app to make changes to your device?

Clicking Yes on the dialog box while continuing to hold Ctrl + Shift, the Workstation Options are not reset. To reset Workstation Options, use one of these workarounds:


FactoryTalk Linx compatibility
Some device properties, online functions, communication drivers, and FactoryTalk Security authentication with Studio 5000 Logix Designer are not supported with FactoryTalk Linx. Use the following table as a guide for the recommended communication software to use with select modules.
ArmorStart Ethernet (28xe)
RSLinx Classic
ArmorStart LT (29xe)
RSLinx Classic
Drives Profiles
  • PowerFlex Drives
  • 1305
  • 1336
  • FactoryTalk Linx
  • RSLinx Classic
  • RSLinx Classic
GuardMaster and GuardLink (440C-CR30-22BBB)
  • RSLinx Classic (v3.0100 and earlier)
  • FactoryTalk Linx (v3.02.00 and later)
HIPROM
  • 1788-EN2PAR
  • 1788-CN2PAR
  • 1788-EN2FFR
  • 1788-CN2FFR
 
  • RSLinx Classic
  • RSLinx Classic
  • RSLinx Classic
  • RSLinx Classic
IO-Link Block (1732E-8IOLM12R IO Link)
FactoryTalk Linx
IO-Link Point (1734-4IOL)
FactoryTalk Linx


Default font type and size for Structured Text Editor

Starting with version 31.00 of Logix Designer application, the default font type size for the Structured Text Editor changed from Courier New size 8 to Consolas size 10. Since the Sequential Function Chart (SFC) Action uses structured text to execute assignments and instructions, this change makes the SFC Action larger causing the overlap of the SFC elements in projects converted from version 30.00 and earlier to version 31.00 and later.
To get the same SFC layout as in v30.00 and earlier:
  1. Select Tools > Options.
  2. In the Workstation Option, select Structured Text Editor > Font/Color.
  3. In Font, choose Courier New.
  4. In Size, choose 8.

Converting a project with Function Block Diagram text boxes from version 11 of the RSLogix 5000 software to version 21.00 and later

To convert a project with a Function Block Diagram routine with text boxes from version 11 of RSLogix 5000 software to version 21.00 and later, use one of these steps:

Resize multiple large SFC routines using Fit to Width command

The Logix Designer application may exceed memory when multiple large Sequential Function Chart (SFC) routines are opened and resized to fit the full window using the View>Zoom>Fit to Window command. To work around this issue, use the View>Zoom>Fit to Width command to set the zoom of the selected routines so that the entire width of the routine fits within the routine windows.
Trend server sometimes fails for multiple versions of the Logix Designer application

When versions 30.00 and 31.00 of the Logix Designer application are both installed on the same computer, and trending has never been run in the version 31.00 Logix Designer application, trending fails to run in the version 30.00 Logix Designer application. RSLinx Classic is the default communication software for Trend Server, which causes this behavior. After switching between FactoryTalk Linx and RSLinx Classic, the trend will not work for version 30.00. (Lgx00203589)
Add-On Instruction module references

Starting with version 24.00 of the Logix Designer application, modules can be accessed via module references. Because of this, program-scoped tags with the same names as modules ignore those modules in terms of logic references. For version 24.00 and later, when attempting to access modules via module reference from within the Logix Designer application, a warning message opens. If converting from a version earlier than version 24.00, the application returns a verification error.
Uninstalling the CodeMeter® kit causes Logix Designer uninstall to fail

If uninstalling the CodeMeter kit, which is installed with the FactoryTalk® Activation Manager, the Logix Designer application fails to uninstall. To restore the CodeMeter kit, uninstall the FactoryTalk Activation Manager and then reinstall it.
SequenceManager not available on Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 controllers

The SequenceManager feature is not available for Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 controllers in this release of the Logix Designer application.
However, SequenceManager is available on these Process controllers:

Non-alphanumeric characters in a STRING need an escape carriage

When editing existing standard STRINGs or entering a new STRING, if there is a non-alphanumeric character in the STRING, such as a space, period or apostrophe, add an escape carriage.
Microsoft® .NET Framework 4.6 may cause failure in earlier versions of the Logix Designer application
For installations of version 32.00 of Logix Designer, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:
Signatures break for Add-On Instructions from earlier releases

When using version 29.00 or later to open a project from a release earlier than version 29.00, the signature breaks for any Add-On Instruction included in the project. In the same way, when importing an Add-On Instruction from a project created in a release earlier than version 29.00, the signature breaks for that Add-On Instruction. Un- seal and then re-seal each Add-On Instruction to get a new signature.
Kinetix® Encoder Emulator RPI must match the Motion Task update rate

The Requested Packet Interval (RPI) setting for the Kinetix Encoder Emulator must match the Motion Group Base Update period. If the RPI setting and the Motion Group Base Update period do not match, output can fail from the Encoder Emulator.
Drive safety instructions Boolean members

Some Boolean members of the AxisSafetyFaults attribute were renamed and some were added to support the drive safety instructions. If a member of the AxisSafetyFaults is used in logic, the logic will not compile until the old axis Boolean attribute is replaced with the new name.
Versions 18.00 and later require updates to Custom Motion Database

When using a Custom RSLogix 5000 Motion Database in RSLogix 5000 software versions 12.00 through 17.00, update the motion database to work with versions 18.00 or later. The table lists the motion database revisions that are used with these application versions.
  
Version of application
Motion Database revision
37.00
15.1.0 [ Motion.mdb format ]
36.00
14.50.00 [ Motion.mdb format ]
35.01
14.50.00 [ Motion.mdb format ]
35.00
14.43.00 [ Motion.mdb format ]
34.02 / 34.03
14.45.00 [ Motion.mdb format ]
34.00 / 34.01
14.39.00 [ Motion.mdb format ]
33.02 / 33.03
14.45.00 [ Motion.mdb format ]
33.01
14.31.00 [ Motion.mdb format ]
33.00 / 33.00.02
14.24.00 [ Motion.mdb format ]
32.00 / 32.01 / 32.02 / 32.03 / 32.04
13.04.00 [ Motion.mdb format ]
31.00/ 31.02
12.02.00 [ Motion.mdb format ]
30.00
11.06.00 [ Motion.mdb format ]
29.00
11.05.00 [ Motion.mdb format ]
28.00
10.05.00 [ Motion.mdb format ]
  
27.00
10.03.00 [ Motion.mdb format ]
26.01
10.03.00 [ Motion.mdb format ]
24.00
9.24.00 [ Motion.mdb format ]
23.00
9.22.00 [ Motion.mdb format ]
21.03
9.15.00 [ Motion.mdb format ]
21.00
9.08.00 [ Motion.mdb format ]
20.01
8.12.00 [ Motion.mdb format ]
20.00
8.09.00 [ Motion.mdb format ]
19.01 / 19.00
7.05.00 [ Motion.mdb format ]
18.02 / 18.01 / 18.00
6.09.00 [ Motion.mdb format ]
17.01/ 17.00
5.03.00 [ *Motion.md format ]
16.04 / 16.03 / 16.00
4.02.00 [ *Motion.md format ]
15.03 / 15.02/ 15.01 / 15.00
3.24.00 [ *Motion.md format ]
14.01 / 14.00
3.12.00 [ *Motion.md format ]
13.04 / 13.03/ 13.02 / 13.01 / 13.00
3.12.00 [ *Motion.md format ]
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 12.01 / 12.00
3.03.00 [ *Motion.md format ]

* Before a Custom Motor can be used in version 18.00 or later, any Custom Motor currently in a motion database file at revision 5.00 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.
To initiate the process of getting the database updated, please email the request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if the current database includes non-Rockwell motors.
Locked routines from earlier releases must be unlocked and re-locked before download

When using version 32.00 to open a project from a release earlier than version 32.00, any routines that are locked in the project will not download to a controller. Before downloading the project, open the project in version 32.00, unlock the routines, and then re-lock them. Download the project with the re-locked routines to the controller.
MSXML 4.0

This version of Studio 5000 Logix Designer application does not install or use MSXML 4.0. MSXML 4.0 has security risks associated with it and is no longer supported by Microsoft. For more information about MSXML and its availability, see the MSXML Roadmap. When installing products or components made by other vendors that use MSXML 4.0, contact the vendor for questions about the security risk associated with MSXML 4.0.
Unattended or silent install

Use command-line parameters to perform an unattended or silent installation of the software.

Installation command-line parameters

Use command Setup.exe /? to display the usage options for installation parameters. Command-line parameters are case-insensitive. If a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").
Examples
These examples show how to use the installation commands.
Setup.exe /Q /IAcceptAllLicenseTerms
Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /InstallDrive=D:

Error codes

This table identifies the error codes that can be returned by an installation.

 

ERROR_SUCCESS
0
The installation completed successfully.
ERROR_INVALID_PARAMETER
87
One of the parameters was invalid.
ERROR_INSTALL_USEREXIT
1602
The installation was cancelled by the user.
ERROR_INSTALL_FAILURE
1603
A fatal error occurred during installation.
ERROR_BAD_CONFIGURATION
1610
The configuration data for this product is corrupt. Contact
your support personnel.
ERROR_REBOOT_CONTINUE
1641
A reboot is required to continue the installation.
ERROR_SUCCESS_REBOOT_REQUIRED
3010
A restart is required to complete the installation. After restart
the product is successfully installed.
ERROR_REBOOT_PENDING
3012
A restart is pending and is required before the installation can
continue.
ERROR_SUCCESS_NOT_APPLICABLE
3013
The installation cannot proceed because the products are
already installed.
ERROR_SUCCESS_WARNING_REBOOT
3014
The installation succeeded with warnings. Check the
installation log file for details. To complete the installation, restart the computer.

Delay when opening a 1756-EN4TR Add-on Profile when configured as adapter pair

The 1756-EN4TR Add-on Profile takes 10-15 seconds to fully load content while online with a controller if all of the following conditions are true.

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