System requirements for Studio 5000 Logix Designer version v36.00.02

For optimal performance of the Logix Designer application, the personal computer should meet or exceed these hardware and software requirements.

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.

• Intel® Core i5 Standard Power processor (i5-3xxx)
• 8 GB of RAM memory
• 30 GB free hard disk space

• Operating system and service pack compatibility:

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

• Windows® 10 Enterprise
• Windows 10 Professional
• Windows 11 Enterprise
  
• Windows 11 Professional
• Windows Server 2022 Standard
• Windows Server 2022 Datacenter

• Microsoft® .NET Framework 3.5
• Microsoft .NET Framework 4.8

• This version of the Logix Designer application is expected to operate correctly on all other editions and service packs of these operating systems, but has not been tested:

• Windows 8
  
• Windows Server 2019
• Windows Server 2016

• This is a list of the prerequisite software installed with this version of the Logix Designer application:

• FactoryTalk® Services Platform v6.40
• FactoryTalk® Activation Manager v5.01
• FactoryTalk® Linx v6.40

• RSLinx Classic v4.40 is shipped with the Logix Designer application version 36.00.

• FactoryTalk® View Site Edition (SE) software and FactoryTalk Linx communication software are required to use alarming capabilities fully.
• Check the software requirements for other Rockwell Software® products that will be installed to be sure that these products are also compatible with the system.

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

• Windows 10 Professional (64-bit)
• Windows Server 2022 Standard (64-bit)

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

Install one or more functionalities for FactoryTalk Updater:

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.

FactoryTalk Updater Server:

• Communicates with online FactoryTalk Updater Agents to receive collected data.
• Connects to the Product Compatibility and Download Center to retrieve the latest software information.
• Responds to requests from the FactoryTalk Updater Client.
• Supports ~100 online Agents.

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

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.

• To check and download the firmware compatible with this version of the Logix Designer application, use the Product Compatibility and Download Center (http://compatibility.rockwellautomation.com/Pages/MultiProductDownload.aspx?crumb=112).
• Logix 5000 controllers and ControlLogix Motion modules must contain a revision of firmware that is compatible with this version of the Logix Designer application. The firmware images for most of the supported modules are contained on a DVD-ROM shipped with Rockwell Software Studio 5000 Automation Engineering & Design Environment™.

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

System features for Logix Designer v36.00

Logix Designer application version v36.00 has these new and enhanced features.

• Axis Test Mode for Safety

• Granular Safety Signatures

• OPC UA

• Multiple Device Interactions

• Motion Indirect Addressing

• Import all and export all

• Additional safety instruction and operator support

• Updated instruction mnemonics

This table lists new hardware supported in this release.

The version of FactoryTalk Linx software provided with this version of the Logix Designer application includes an updated set of electronic data sheet (EDS) files for Rockwell Automation products. Installing this software ensures that FactoryTalk Linx software and RSNetWorx software will be able to work with the new revisions of firmware. To download and install the latest EDS file, access the Rockwell Automation Services & Support website (http://www.rockwellautomation.com/global/support/downloads.page?).

AlarmSet attribute sometimes displays erroneous value (3109190)

The AlarmSet attribute sometimes displays an erroneous value. However, the display issue does not affect the logic execution.

This anomaly corrected in version 36.00.

This anomaly first identified in version 34.00.

Defined alarm members of UDTs can be lost in editing process (2339160)

Editing an existing UDT that contains alarms and involves UDT nesting can result in a different UDT losing defined alarm members.

This anomaly first identified in version 31.00.

This anomaly corrected in version 36.00.

Dialogs undocked, split, or set to auto-hide provide unpredictable results for F4 key (2335181)

When dialogs in the Logix Designer application are undocked, split, or set to auto-hide, the F4 key produces unexpected results.

This anomaly first identified in version 31.00.

This anomaly corrected in version 36.00.

Structured text block comment can cause crash on upload (2209737)

When you create a comment inside #region and #endregion constructs in a Structured Text routine, the Logix Designer application sometimes crashes when you upload the project from a controller to a new project or into a current project.

This anomaly first identified in version 32.00.

This anomaly corrected in version 36.00.

Cfg_SPRampMaxDev range incorrect on PPID dialog box (2193171)

On the PPID instruction dialog box, the Cfg_SPRampMaxDev parameter allowed values that are outside the correct range.

This anomaly first identified in version 35.00.

This anomaly corrected in version 36.00.

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.

This anomaly corrected in version 36.00.

Fatal Error 0x80042001 when creating an Add-On Defined output parameter in a routine (1731323)

Fatal error 0x80042001 could occur when creating a new control tag for an Add-On Instruction (AOI) and setting the control tag as an output program parameter.

This fatal error will occur when the tag is created directly from the instruction within the routine. 

This fatal error will not occur if the tag is created from the tag data tables.  

Reference technote BF29394 for additional information.

This anomaly first identified in version 31.00.

This anomaly corrected in version 36.00.

Failed to import file occurs during AOI import (2239485)

When an Add On Instruction (AOI) with the same name and one or more matching signature entries is imported with Overwrite option an error occurs. NOTE: The error occurs with signed and unsigned AOIs.

Error message in popup window:  Failed to import file ‘C:\….L5x.’ The import was canceled due to errors.  No changes were made to the project.  See Output Window Errors tab for details.

Error message in Output Window Errors tab:  Error:  Unable to import “AOI name here”, The Import was cancelled due to a name collision (Name=' ').

Workarounds:

Unsigned AOIs: clear the signature history on the AOI that already exists in the ACD file.

Signed AOIs: remove the signature from the AOI that already exists in the ACD file.

This anomaly first identified in version 32.00.

This anomaly corrected in version 36.00 and 36.01.

Fatal Error 0xe0434352 when creating, opening, or interacting with a module’s properties after installing a later version of the Studio 5000 Logix Designer application or after installing a new Add-on Profile (3219935)

Fatal Error 0xe0434352 occurs on creating, opening, or viewing of profiles updated with a web-based interface, including 1756 Ethernet modules, 5069 Ethernet Adapters, 5094 Ethernet adapters, 1734 Ethernet Adapters, and 1756 I/O.

This fatal error could occur after an installation of the Studio 5000 Logix Designer application or a stand-alone Add-On Profile (AOP), which causes an upgrade to all module profiles.

The fix for this anomaly is available in the Add-on Profiles update for the 1756 Analog Modules, v40.14.70. The Add-on Profiles can be downloaded from the Product Compatibility and Download Center. For more information on this anomaly and the solution, please see technote ID BF30201. 

This anomaly first identified in v20.05.

DataExchange fails AML and RDF imports and exports due to incorrect catalog number (1427806)

DataExchange AML and RDF imports and exports fail because the catalog number 5059-HSC2xOB4 is incorrectly listed as 5059-HSC2XOB4 in ModuleType and CatalogServices.

This anomaly corrected in version 36.00.

This anomaly first identified in version 34.00.

PFO Advanced dialog box Clamping limits input range (1585324)

The PFO instruction Advanced dialog box Clamping limits do not update to match the Minimum and Maximum values.

This anomaly only applies to projects using the CompactLogix 5380P and ControlLogix 5580P controllers.

This anomaly corrected in version 36.00.

This anomaly first identified in version 33.00.

Displayed alarm fields may not update when modified programmatically (1541337)

Alarm behavior functions properly with the programmatically modified value; however, the Alarm List and Alarm Properties dialogs box might display values that existed before the programmatic modification.

Saving the file, uploading tags, and reopening the dialogs updates the Alarm List and Alarm Properties to the current value.

This anomaly first identified in version 32.03.

This anomaly corrected in version 36.00.

Logix Designer application Tag-based Alarm extended properties do not auto-populate completely (1957929)

The Logix Designer application tag-based alarm extended property @Alarms does not auto-populate completely in Sequential Function Chart (SFC) or Structured Text (ST) routines. You must manually type out the text in its entirety to access all extended properties.

For example, if your alarm is named MyAlarm, and the input tag is named AlarmInput, you must type:

AlarmInput.@Alarms.MyAlarm.

When you enter the last period, you can select from the list of available extended properties in a dialog box.

This anomaly first identified in version 35.00.

Motion Coordinated Linear Move (MCLM) Instruction Show ??'s for V_X, V_Y, V_Z Axes Positions (2069950)

In the Motion Coordinated Linear Move (MCLM) instruction, if the Position operand is defined with an array tag and the array pointer is set at element 1 or greater, axes V_X, V_Y, V_Z appear as question marks “??” instead of their respective positions.

This anomaly only occurs with direct array references. This will not occur with indirect addressing of the array tag.

This is a display anomaly that does not affect the instruction’s functionality.

This anomaly corrected in version 36.00.

This anomaly first identified in version 33.00.

Fatal Error 0x80042001 when creating an Add-On Defined output parameter in a routine (1731323)

Fatal error 0x80042001 could occur when creating a new control tag for an Add-On Instruction (AOI) and setting the control tag as an output program parameter.

This fatal error will occur when the tag is created directly from the instruction within the routine. 

This fatal error will not occur if the tag is created from the tag data tables.  

Reference technote BF29394 for additional information.

This anomaly first identified in version 31.00.

Changes to a user-defined data type sometimes causes the Logix Designer application to become unresponsive (1170213, 1170044)

Changing user-defined data type (UDT) members when a routine is open, accessing the UDT being changed causes the Logix Designer application to become unresponsive.

This anomaly first identified in version 32.00.

This anomaly corrected in version 36.00.

Upload error: Logic reconstruction data may be corrupted (2180963)

Converting a file to a newer revision that includes structured text application code in a routine or Add-On Instruction with #Region defining the beginning of a collapsible outline segment but omitting the #EndRegion defining the ending results in the verified and downloaded file generating the error Logic reconstruction data may be corrupted during upload.

Issues within the application code can be identified by:

1. Exporting the file as L5K or L5X.
2. Importing the file.
3. Building the file after the import identifies the missing #EndRegion instances with errors.

This anomaly first identified in version 33.00.

This anomaly corrected in version 36.00.

Message datatype cannot compile after upload from controller (1785828, 1789626)

The Logix Designer application cannot compile the ACD file after uploading a program-scoped MSG backing\control tag that is used as an InOut parameter in an Add On Instruction (AOI) to a new ACD file.

This anomaly corrected in versions 33.02, 35.00, and 36.00.

This anomaly first identified in version 34.00.

Failure to import Add-On Instructions with partially matching signature history (2239482, 2239491, 2239489)

An error occurs when attempting to import and overwrite an Add-On Instruction that has a signature history with at least one overlapping entry, and a matching active signature status. The import fails with one of several error messages.

This anomaly corrected in version 33.03, 34.03, 35.01.

This anomaly first identified in version 32.00.

Logix Designer application Tag-based Alarm extended properties do not auto-populate completely (1957929, 1957940)

The Logix Designer application tag-based alarm extended property @Alarms does not auto-populate completely in Sequential Function Chart (SFC) or Structured Text (ST) routines. You must manually type out the text in its entirety to access all extended properties.

For example, if your alarm is named MyAlarm, and the input tag is named AlarmInput, you must type:

AlarmInput.@Alarms.MyAlarm.

When you enter the last period, you can select from the list of available extended properties in a dialog box.

This anomaly corrected in versions 35.01 and 36.00.

This anomaly first identified in version 35.00.

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.

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 corrected in version 37.00.

This anomaly first identified in version 36.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 corrected in version 37.00

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

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 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 corrected in version 37.00.

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.

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:

• <![CDATA[MOV(TagA);]]>

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

• <![CDATA[MOV(TagA,TagB);]]>
• <![CDATA[MOV(TagA,?);]]>

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.

Upload failure (1024944)

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

• Error code: 731-0

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

HMIBC tags permitted in 5580 Redundant applications (3396611)

Logix Designer does not prevent you from including HMIBC type tags in Redundant applications, which can lead to controller Primary, Secondary or simultaneous Primary and Secondary assert and errors when you attempt to upload from the controller into an existing or new application when no assert has occurred.

This anomaly corrected in version 37.00.

First identified in Logix Designer version 33.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:

• You are viewing the logic of an Add-On Instruction that references at least one Logix tag-based alarm.
• The Add-On Instruction logix is in a structured text routine.

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.

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.

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 in the Watch title bar.
• Float the Watch view by selecting in the Watch title bar and selecting Float.

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

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.

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.

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.

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.

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.

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:

• I/O must exist on a different subnet from the controller.
• Layer 3 switches used to separate and manage the routing of communication from the controller network to the network with the I/O.

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.

Module Info B tab empty (1815893)

An anomaly in the AOP core (v26.32.51.0) installed with v34.00 Studio5000 Logix Designer prevents redundant 1715-AENTR and 1715 IO modules Module Info B tab from displaying information while online. 

Consider these work arounds:

• Use an MSG instruction as documented in AID 55301 and AID 55305
• Reference the backing tags of the 1715 adapter :S tags and 1715 IO :I tags

This anomaly first identified in version 20.05.

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.

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.

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.

Logix Designer version 36.00 has these changes in functionality since the last release.

The Logix Designer application no longer allows programmatic write access to Alarm status flag bits.

The maximum days value that you can enter for the TIME and LTIME data types is 106750d.

The EDS Hardware Installation Tool option accessed from the Tools menu is now the Device Description Registration Tool option. Use the Device Description Registration Tool option to export and import EDS files, IO-Link IODD files, and HART DD files between workstations.

EDS AOP will now take advantage of the additional datatype support in Logix Designer. Adding a device using an EDS AOP now uses the data types as defined in the EDS AOP file without conversion. This is a workstation install that updates versions 34 and later for ControlLogix 5580, 5480, and 5380 projects.

In this version of the Logix Designer application, the mnemonics for these instructions have been updated to align with IEC 61131-3 and PLCopen standards. Mnemonics for specific instructions are automatically updated on import and project conversion. The updated mnemonics are:

The Import/Export version number for this version of Logix Designer application is 2.27. The table lists the Import/Export versions for previous releases.

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:

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

5. Select Local Users and Groups > Groups.
6. Add a local Windows group and name the group Users.
7. Add the logged in user to that Windows group.
8. Reboot your computer and reattempt the install.

Logix Designer SDK v1.00 is included in the Studio 5000 Logix Designer Professional Edition installer for v35.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.

Studio 5000 Logix Designer v35.00 has been tested on CIS Microsoft Windows 10 Enterprise (Release 21H2) Benchmark v1.12.0 (L1).

Exceptions settings for Studio 5000 Logix Designer v35.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)

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.

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

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)

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.

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

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.

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.

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.

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:

9. Select Tools > Options.

10. In the Workstation Option, select Structured Text Editor > Font/Color.
11. In Font, choose Courier New.
12. In Size, choose 8. 

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. 

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. 

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)

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.

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.

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

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.

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.

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

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.

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.

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.

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.

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

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.

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.

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

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

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)

• 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)

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

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

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.