Application notes

These are the 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:

In Windows Start, search for and open the
Computer Management app
.

Select
Local Users and Groups > Groups
.

Add a local Windows group and name the group Users.

Add the logged in user to that Windows group.

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:

adding a new EDS AOP module.

copy/paste of the EDS AOP module.

import/export of the EDS AOP module.

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.

CIS Benchmarks test results

Studio 5000 Logix Designer v37.00 has been tested on:

CIS Microsoft Windows 10 Enterprise Benchmark v3.0.

CIS Microsoft Windows 11 Enterprise Benchmark v3.0.

Exceptions settings for Studio 5000 Logix Designer v37.00 are listed.

5.60(L1)Ensure 'IIS Admin service (IISADMIN) is set to 'Disable' or 'Not Installed' -- FactoryTalk Alarms and Events requires this service to be enabled

9.3.1 (L1) Ensure 'Windows Firewall: Public: Firewall state' is set to 'On (recommended)' - FactoryTalk Alarms and Events requires this service to be enabled to connect SQL SERVER

5.37 (L1) Ensure 'Windows Mobile Hotspot Service (icssvc)' is set to 'Disabled' - Studio 5000 Logix Designer 21H2

5.43 (L1) Ensure 'Xbox Live Auth Manager (XblAuthManager)' is set to 'Disabled' - Studio 5000 Logix Designer 21H2

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 offline, 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:

Configure System Security Features User Manual (publication SECURE-UM001)

System Security Design Guidelines Reference Manual (publication SECURE-RM001)

Converged Plantwide Ethernet (CPwE) Design and Implementation Guide (publication ENET-TD001)

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:

Temporarily set UAC to Never notify
.

Release
Ctrl + Shift
, click Yes
on the dialog box, and then immediately hold down Ctrl + Shift
.

Open the Logix Designer application, click Tools > Options
to open the Workstation Options
dialog box, and for each Workstation Option category, click Reset Category
.

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)	FactoryTalk Linx or RSLinx Classic
ArmorStart LT (29xe)	FactoryTalk Linx or RSLinx Classic
Drives Profiles
PowerFlex Drives	FactoryTalk Linx or RSLinx Classic
1305	RSLinx Classic
1336	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:

Select Tools > Options
.

In the Workstation Option,
select Structured Text Editor > Font/Color
.

In Font
, choose Courier New
.

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:

Export the version 11 project file to an .L5K file, and then import the .L5K project file into version 21.00 and later.

Convert the project from version 11 to version 12.00 through version 20.00 before converting the project to version 21.00 and later.

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:

5069-L320ERP

5069-L340ERP

1756-L81EP

1756-L83EP

1756-L85EP

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:

When previous versions of Logix Designer are installed after version 30.00, .NET Framework 4.6 may cause installation to fail for these earlier versions of the Logix Designer application.

When installed on 32-bit Windows operating systems, .NET Framework 4.6 causes versions 23.00 and earlier of the Logix Designer application to fail on startup.

Follow one of these steps to work around the issue:

Do not install version 30.00 of the Logix Designer application on a 32-bit Windows operating system on which version 23.00 or earlier of the Logix Designer application is installed.

Contact Rockwell Automation Support for instructions on disabling the Logix Designer Start
page on versions 23.00 or earlier. Disabling the Start
page allows the Logix Designer application to start and run.

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.

To install the software with no user interface using the default settings during the installation process. (Silent install)

Setup.exe /Q /IAcceptAllLicenseTerms

To install the Chinese language version of the software on the D: drive and display the progress, error, or complete messages during installation and restart the computer if necessary. (Unattended install)

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.