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.

• Operating system and service pack compatibility:
  • Windows® 10 Professional (64-bit) version 20H2
  • Windows Server 2012 R2 Standard Edition
  • Windows Server 2016
  • Windows Server 2019

• Microsoft .NET Framework 3.5 SP1
• 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 10
  • Windows 7 Professional (64-bit) with Service Pack 1
  • Windows 8.1
  • Windows Server 2012
• These prerequisite software are required with this version of the Logix Designer application and installs with this release:
  • FactoryTalk® Services Platform v6.20.00
  • FactoryTalk® Activation Manager v4.04.14
  • FactoryTalk® Linx™ v6.20.00
  • RSLinx Classic v4.20.00\

• FactoryTalk® View Site Edition (SE) software and FLEX Ex communication software are required to use alarming capabilities fully.  

• Check the software requirements for other Rockwell Software® products that install 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 2016 Standard (64-bit)
• Windows Server 2012 R2 Standard (64-bit)

Windows 10 v1703 or later is the recommended operating system if running this software with a 2K or 4K High Resolution Display with scaling up to 125%.

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

• The firmware associated with this release version of the programming software does not support redundancy. Redundancy firmware revisions are released later than the standard revisions and are available for download from the Product Compatibility and Download Center.

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.

The Logix Designer application version v32.04 has no new features or enhancements.

This table lists new hardware that is supported in the 32.01 release.

This table lists new hardware that is supported in the v32.00 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 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?).

License Source Protection and locked content not compatible (925976, Lgx00229625, Lgx00229626)

When importing, cutting, copying, or pasting License Source Protected and locked routines and Add-On Instructions that contain GSV or SSV instructions, an error message states that Licensed Source Control content is newer and not compatible. Licensed Source Protected and locked routines and Add-On Instructions that do not contain GSV or SSV import, cut, copy, and paste without an error message.

This anomaly first identified in version 31.00.

A comment in an imported routine in a Structured Text Add-On Instruction loses the closing parenthesis upon import forcing the user to add the closing parenthesis to successfully download the file.

This anomaly first identified in version 32.03.

To work around this issue, add a space before the forward slash (* /*).

The Logix Designer application experienced a fatal error after attempting to copy and paste an Add-On Instruction with multiple tabs open.

This anomaly first identified in version 31.00.

Editing the data type of an Add-On Instruction tag from a small to larger size in bytes using the Parameters and Local Tags Editor caused the Logix Designer application to stop performing.

This anomaly first identified in version 32.00.

Invoking an Add-On Instruction index causes the Logix Designer application to stop responding (910975, Lgx00231424, Lgx00231768, Lgx00232214)

Invoking an Add-On Instruction with tag based alarms, an array with 100 elements, and a DINT index assigned a constant value, caused the Logix Designer application to stop responding.

This anomaly first identified in version 32.00.

The Logix Designer application that is saved in version 32.02 with License Source Protection opened as an expired license in the Logix Designer application version v32.03.

This anomaly first identified in version 32.03.

The Logix Designer application experiences a fatal error when two users make online edits to a Structured Text routine. If one of the users edits a protected and unlocked Structured Text routine, the other user receives a fatal error.

This anomaly first identified in version 32.03.

In the Axis Properties > Actions dialog boxes, unavailable options for associated modules were displayed as selectable options instead of unavailable (gray) options.

This anomaly first identified in version 32.03.

The Other folder was missing from the Import Content structure when Motion content was imported using the Import Configuration dialog box.

This anomaly first identified in version 32.02.

Selecting Help>About Logix Designer on the main menu and then selecting the http://support.rockwellautomation.com link did not open the support web page.

This anomaly first identified in version 31.00.

Using the ALT + dash keys to close tabbed routine windows caused the Logix Designer application to stop responding.

This anomaly first identified in version 31.00.

When choosing to install the Logix Designer application in a location other than the default drive, some items, such as HTML help, installed to the default location instead of the location the user chose. This anomaly is corrected only in the English version of the Logix Designer application.

This anomaly first identified in version 31.00.

The Studio 5000 Logix Designer Service Edition does not allow users to edit the controller IP Address when Manually configure IP settings is enabled. This is expected behavior and not an anomaly.

This anomaly first identified in version 31.00.

When using a PowerFlex 527 drive in Frequency Control mode, if Current Vector Limit was set to 0.0%, it would cause faults in the drive or axis.

This anomaly first identified in version 32.00.

The Logix Designer application displayed information for CPT (Compute) instruction expression tag tooltips differently in version 31.01 and earlier. The tooltip displayed tag information, such as the name, associated data type, scope, and value. In version 32.00, the expression tag tooltip displayed tags as Undefined.

This anomaly first identified in version 32.00.

Selecting File > Print Options > Ladder Listing > Font/Color or Tools > Options Ladder Editor > Font/Color did not print the selected color. Tools > Options Ladder Editor > Font/Color changed the color in the Logix Designer application but not the print file.

This anomaly first identified in version 32.02.

Verifying a project that contains an alarm definition input that is an InOut parameter returns no error, but fails to download.

This anomaly first identified in version 32.00.

When the Scope menu was open in the Tag Editor, pressing Alt + Tab to switch to another window caused the Logix Designer application to crash.

This anomaly first identified in version 30.00.

The Logix Designer application experienced a fatal error when verifying a routine that contained an Equipment Sequence.

This anomaly first identified in version 31.01.

When editing an Equipment Sequence in Run mode in the Studio 5000 Logix Emulate application, the Logix Designer application stopped performing.

This anomaly first identified in version 32.00.

Enabling the Bookmark toolbar in the Logix Designer application caused fatal error 0xc0000005 when the workstation display scaling is set to 125%.

This anomaly first identified in version 31.00.

Running FactoryTalk Batch version 14.00 with FactoryTalk Linx 6.20 and the Logix Designer application version 33.00 causes the Batch sequence step to stick in the UPLOADHELD state when FactoryTalk Batch reads the sequence outputs SEQ_REAL, SEQ_DINT, SEQ_BOOL, and SEQ_STRING. To enable access for FactoryTalk Batch, existing ACD files sometimes require export and import to ensure the sequence data type properties are set correctly for access.

This anomaly first identified in version 32.00.

When offline with the project, selecting Routine Overview on the SFC toolbar can cause an unreadable overview to open in the Routine Overview window.

This anomaly first identified in version 32.00.

Online edit does not assemble, no test edits present dialog box displayed (918357)

Online edit to a rung that included a rung comment was not finalized in versions 32.00, 32.01, and 32.02 fails to assemble in version 32.03 and gives the user an information dialog that no test edits are present.

This anomaly first identified in version 32.00. 

To work around this issue, update all workstations to version 32.04.

The Logix Designer application stopped responding with the error 0xc0000005 after switching SFC routines while online in edit mode.

This anomaly first identified in version 33.00.

The Logix Designer application experienced a fatal error when FBD functions were added to Add-On Instructions FBD logic routines in the FBD Editor.

This anomaly first identified in version 32.00.

Copying and pasting a string in an FBD instruction added unreadable characters after the semicolon, causing a verification error.

This anomaly first identified in version 32.00.

Set JSR in SFC routine caused verification errors (910973, Lgx00233736, Lgx00233703)

Accepting pending edits on a set JSR in an SFC routine produced the error "Conflict exists in project verification state. Internal error. Call Technical Support." A dialog box contained the message "Program 'MainTask_Program' does not have Test Edits." But the routine verified without error.

This anomaly first identified in version 33.00.

RMPS instruction displays question marks (910968, Lgx00232638, Lgx00232366)

In the RMPS instruction Parameters Properties dialog box, Segment values displayed when the Ramp, Soak, and Soak Time values were set to REAL Array values. If these properties were part of a user-defined data type, question marks displayed in the property fields but the RMPS instruction executed.

This anomaly first identified in version 32.01.

Editing an FBD JSR instruction properties sometimes reverses the order of input and return parameters.

This anomaly first identified in version 26.00.

After the user started to type in the Structured Text Editor, the editor stopped responding and the Logix Designer application shut down. The error did not occur when the Show Completion Prompt when Typing checkbox (Tools>Options>Structured Text Editor>Show Completion Prompt when Typing) was cleared in the Workstations Options dialog box.

This anomaly first identified in version 31.00.

Starting online editing in an SFC routine changed the backslash to a double colon, causing the Logix Designer application to not accept the edits or to verify the routine.

Typing or pasting text that contains a tag name with underscores in a new line of an ST routine caused the Logix Designer application to stop performing.

This anomaly first identified in version 32.02.

Attempting to create a parameter or tag in the New Parameter or Tag dialog box caused the Logix Designer application to stop performing after adding a CPT expression.

This anomaly first identified in version 31.02.

A \ is added before the name of a routine that contains a PCLF (Equipment Phase Clear Failure) instruction under two conditions:

• The project file was uploaded from the controller and a \ appeared in front of each routine name that contained a PCLF instruction.
• Part of the project was correlating and \ was added to the routine name when the rung with the PCLF instruction also referred to tag-based alarms with extended properties.

The addition of the \ to the routine name will not cause a verification error, but it causes a compiler error that prevents download.

This anomaly first identified in version 32.02.

After finalizing online edits, rungs may be displayed in the incorrect order. While finalizing your edits an error "Main Routine Object does not Exist" will occur indicating that your edits did not finalize. But, rung edits where finalized. This anomaly only occurs in projects that have unchecked download project documentation and use rung comments. Upload the project to correct the rung order view.    

This anomaly only affects: ControlLogix 5570, GuardLogix 5570, CompactLogix 5370, and Compact GuardLogix 5370

This anomaly first identified in version 32.03.

Unable to change standard program scope alias to a standard controller tag (910983, Lgx00231934, Lgx00231485)

In a project with the Safety Signature applied, attempting to delete a new standard program that is aliased to a standard controller tag caused an error in the Logix Designer application.

This anomaly first identified in version 31.00.

Following a Partial Import while Online (PIO) that contains rung comments, after deleting a single rung it may appear as two rungs were deleted. After upload, ladder logic rungs display correctly.

This anomaly first identified in version 32.03.

This anomaly corrected in version 32.04.

When indirect addressing is performed on a BOOL array inside of an Add-On Instruction, unexpected execution behavior can occur.

• Major recoverable faults can occur. The major fault will be a Type 4, Code 20. When the major fault is investigated, the indirect address will be found to be within bounds.
• Application execution is not correct. Data that is indexed is not read or written.

Not all application projects will be affected by this anomaly and may appear and disappear after downloads.

For more information on this anomaly, refer to Knowledgebase document 1129157.

This anomaly first identified in version 32.03.

For installation that do not use the default installation path, PowerFlex UDC AOP v5.08 install does not calculate disk space correctly. It could fail during installation if there is not enough free hard drive space.

This anomaly first identified in version 32.04

Slow Launch Times (x125369)

Anomaly

RSLogix 5000 Software 20.x

When RSLogix 5000 software is launched for the first time after restarting your personal computer, it may take 1 to 3 minutes for RSLogix 5000 software to be available for use. This behavior is also exhibited when launching FactoryTalk Administration Console or any other product that uses FactoryTalk Services Platform. Note that subsequent launches of these applications will not experience this behavior. This is only observed on the first launch of the application after a restart of the personal computer. If you experience launch times significantly longer than 3 minutes, refer to the firewall configuration settings in Tech Note #29402

Anomalous behavior when editing a Large Structured Text Routine (4002439, 4002441, 4002442, 4002443, 3838969)

• The line in focus changes during an edit.
• The regions of text do not completely expand or collapse when commanded using keyboard shortcuts.
• The application experiences a Fatal Error.

This anomaly first identified in version 32.00.

Web-based profiles launch as blank or empty windows with multiple instances of Logix Designer running on one PC (5582938)

If a space exists in a Windows username and/or the user shell folder path, and multiple Logix Designer projects are open, web-based user interface profiles will launch as an empty window.

The profiles will launch correctly in a single instance of Logix Designer or in one of the opened projects but trying to launch profiles from additional open projects will display the anomaly.

To work around the anomaly

• Work in one project of Logix Designer at a time.

• Log in as a user with no spaces in the username.

This anomaly will be resolved in an upcoming release of Logix Designer Add-on Profiles.

This anomaly first identified in version 20.00

When FactoryTalk Security Modify Logic access is denied, FBD properties are sometimes inaccessible (Lgx00184895)

Studio 5000 Logix Designer v29.00

When Modify Logic access is denied but View Logic access is allowed in FactoryTalk security settings, users sometimes cannot open the Properties dialog box in the Function Block Diagram editor. (Lgx00184895)

As a workaround, select the FBD instruction and press Alt + Enter to open the Properties dialog box.

Changing Data Context for AOI does not change metadata context (Lgx00185356)

Studio 5000 Logix Designer v29.00

Error when using Import to overwrite an existing locked component (Lgx00190571)

Anomaly first identified in Studio 5000 Logix Designer v30.00

The Logix Designer application displays a red flag and/or error ("Unable to overwrite [component] while online. The locked routine already exists in project and there are no differences in locked logic") when you attempt to use Import to overwrite an existing locked component with an identical locked component.

Use one of the following steps to work around the issue:

• If the option is available, select Use Existing for the affected components.
• Unlock and lock the affected components.
• Do not included affected components in the content being imported.

IOT instruction may decompile incorrectly (Lgx00176073, Lgx00188026, Lgx00188027, Lgx00188028)

Anomaly first identified in Studio 5000 Logix Designer v26.00

IOT instruction may decompile incorrectly. If you upload a rung containing, for example, "IOT(MyProduceOrConsumeArrayTag)," it can incorrectly upload or decompile as "IOT(MyProduceOrConsumeArrayTag[0])".

Tracked State Value for Redundant Controller May Not Be Correct After A Switchover (Lgx00189950, Lgx00190153, Lgx00190152)

Corrected Anomaly in Firmware Revision 31.051

Known Anomaly first identified in version 30.00

Catalog Numbers: ControlLogix® 5570 Redundant Controllers

When you enable redundancy but do not retain test edits of a tracked routine, and switchover occurs with test edits running, the Tracked State value on the redundant controller will show the tracked state value of the controller with test edits, even though the test edits are not running in the redundant controller.

Follow one of these steps to work around the issue:

• On the redundant controller (after the switchover, the new primary controller), make a test edit, then undo the test edit. The Tracked State value should now be correct.
• Configure redundancy to retain test edits.

RSLogix 5000 Clock Update tool does not work properly on 64-bit Windows 7 (Lgx00124864)

The RSLogix 5000 Clock Update tool does not work properly when it is installed on a 64-bit Windows 7 operating system and executed.

Cannot add 1734-OBV2S modules to I/O configuration (1145619)

When attempting to add a 1734-OBV2S module to the I/O configuration in the Logix Designer application, installed on Windows 10 OS, these errors display:

• "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore the error and attempt to continue.

• "Failed to create model. There was an unspecified failure."

Performing the same workflow in Studio 5000 Logix Designer, installed on Windows 7 OS, does not result in these errors occurring.

Utilizing the application file created on the Windows 7 OS on a Windows 10 OS can still result in errors occurring:

• Module import of Windows 7 OS created file in Windows 10 OS fails when importing module. Error message "Module import failed. No additional information available."
• Fatal error occurs in Studio 5000 Logix Designer when making 1734-OBV2S module configuration changes in Windows 10 OS with file created with Windows 10 OS.

For additional information, refer to this Knowledgebase article: ID: BF26936

This anomaly first identified in version 24.00.

Fatal error can occur accessing an EtherNet/IP Safety device properties in multi-workstation environments of mixed versions of Add-On Profiles (1097239)

RSLogix 5000 Module Profile Core versions earlier than version 26.00 impacts EtherNet/IP Add-On Profile (AOP) device monitoring in Studio 5000 Logix Designer projects versions 24.00 or later.

In a multi-workstation environment where different versions of module AOP exist, it is possible that a mismatch of the version occurs in the ACD file.  When this mismatch is present, a fatal error results when accessing the properties of the Ethernet/IP Safety Device, such as when viewing device properties or copying the device.

To work around this issue, ensure installed device AOP versions match in all multi-workstations.

This anomaly first identified in version 24.00.

Module import error: Failed to set the ParentModPortId property (00228682)

When exporting an Ethernet node from a controller's I/O configuration and importing it into an I/O configuration of another project, an error can occur when both of the following conditions are met:

• The exported node is from under the embedded Ethernet port of a 5580, 5370, 5380, or 5480 controller.
• The node is imported under a 1756 Ethernet communication module.

Error: Line #: Failed to set the 'ParentModPortId' property (No port was found with the given port number)

Refer to Knowledgebase document 1130964 for more information.

Using the shortcut combination Alt, plus, and dash did not close routine windows and caused the Logix Designer application to become unresponsive. This effects versions 31.00 and later.

This anomaly first identified in version 31.00.

Tag based alarms may not properly import into a new or existing application (1086149)

If a tag-based alarm is defined in an Add-On Instruction (AOI), depending on the export file type used, the tag-based alarm may not properly import into a new or existing application.

If the export file type is an L5K file, the import will properly occur.

If the export file type is an L5X file, the import will not properly occur, and the tag-based alarm is not created. The import will occur, and no errors or warnings are provided. If the user application code attempts to access the tag-based alarm, a controller MNRF/Assert will occur and the <Product-Name_RSL5K> application will log a Type 1, Code 60 or 61 error.

This anomaly first identified in version 31.01.

This anomaly corrected in version 34.00.

Tag Based alarms are not supported as InOut parameters for a Program Parameter or Add-On Instruction (965162)

The Studio 5000 Logix Designer application fails verification if an InOut Program Parameter or an InOut Add-On Instruction parameter is associated with an alarm or alarm definition. InOut parameters are not supported for use with alarms or alarm definitions.

Changes to a User-Defined Datatype could cause the Studio 5000 Logix Designer application to become unresponsive (1145396)

Changing User-Defined data Type (UDT) members when a routine is open causes the Studio 5000 Logix Designer application to become unresponsive.

Duplicate pass through description (1087654)

When pass through descriptions are enabled and a description in assigned to a UDT array element, the sub-elements will show the description text twice.

Fatal error can occur when an RLL rung is edited using ASCII Editor offline (1244044)

When the ASCII Editor is used to edit a rung where previously an online pending delete rung edit was accepted offline for the same rung, a fatal error occurs.

This anomaly first identified in version 20.00.

Unexplained motion possibly caused by the application not recognizing the motion database which could cause the motion configuration to change.

Warnings about unable to set attributes for map connection will be observed while importing an L5K project file that contains any of the following modules: 1794-IE8HB, 1794-IF8IH, 1794-OE8HB and 1794-OF8IH. Use and L5X project export or delete the modules before exporting to L5K.  

This anomaly first identified in version 30.00.

When attempting to upload modules from the controller, the Logix Designer application generates these errors:

• Error: Couldn't be found
• Error: Failed to upload modules

This anomaly first identified in version 32.00.

When an axis gets inhibited, the axis command and actual positions are set = 0.0000. When the axis is uninhibited, the command and actual positions return to their previous values.

This anomaly first identified in version 28.00.

Incorrect calculation of Motion Counters per Unwind Cycle (1108548)

The Logix Designer application calculated an incorrect number of Motion Counts/Unwind Cycle value.

This anomaly first identified in version 32.00.

After a project has been built or has been downloaded to the controller, and a JSR, an SBR, and an RET instruction block are added to the Function Block routine, the Logix Designer application does not update the cached project. If the project is downloaded to the controller again, the cached, unchanged project is downloaded.

This anomaly first identified in version 32.00.

Choose one of these steps to work around this issue:

• Select File > Compact > Delete cached build data to compact the database.
• In addition to adding the JSR, SBR, and RET Function Block instructions, add an additional Function Block element.
• Add the JSR, SBR, and RET Function Block instructions, delete them, and add them again.
• Move an existing Function Block element within the sheet.

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.

Using AutoFlash multiple times to update the firmware in a controller sometimes causes this error to appear:

Failed to update firmware. Either the target device does not support Flash updates using this programming tool or the target hardware revision is not compatible with the selected version of firmware.

This anomaly first identified in version 32.00.

Use one of these steps to work around this issue:

• Close the open project, reopen the project, and try the flash again.
• Shut down the Logix Designer application, restart it, and try the flash again.

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.

The new tag row disappears when entering a new tag name and description in the Tag Editor in a Safety project.

This anomaly first identified in version 32.00.

To work around this issue, close and reopen the Tag Editor.

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.

Source protected routine or Add-On Instruction not executing after download (1312820, Lgx00233725)

Licensed-based Source Protected routines or Add-On Instructions in a Logix Designer application stop executing after a download, when a routine or Add-On Instruction is locked online and previously compiled data was deleted during the Compact operation.  See technote 1132965 for additional details.

This anomaly first identified in version 30.00.

Axis Properties do not reflect SSV changes to bit attributes (00234015, 1063469)

After executing an SSV instruction on a motion axis, the instruction correctly sets the attribute value, but the axis properties does not reflect the change.  See technote BF27663 for additional details.

This anomaly first identified in version 31.00.

Changing the Major Revision Keying of a Kinetix Drive sometimes affects Axis Parameters (1010610, 1010618)

Changing the firmware Major Revision Keying in the properties of a Kinetix drive could affect the scaling (Load Type parameter), as well as other axis parameters, of the associated CIP Motion Axis. This sometimes causes motor performance changes, different from their original configuration. See technote BF27045 for additional details.

This anomaly first identified in version 32.00.

Not enough graphics resources to perform the operation requested. Closing windows will free graphic resources (1623620)

Closing SFC routines online in run mode causes a Windows GDI object memory leak. When this occurs, this window’s operating system dialog box may appear.

When the anomaly occurs, the online project can be saved but opening any other windows results in the dialog box appearing.

The workaround is to close the Logix Designer application session and start a new Logix Designer application session.

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

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.

Error: 1746-HSCE Failed to modify properties. Connection failure. (1685002)

Error Failed to modify properties. Connection failure. occurs when changing the configuration of a 1746-HSCE module connected to a 1747-AENTR while online.

The same error occurs with the 1746-HSCE2 module after the above-described error occurs with the 1746-HSCE module. Following a controller download, no configuration errors occur when changing the configuration of a 1746-HSCE2 module until an error occurs while attempting to change the configuration of a 1746-HSCE module connected to a 1747-AENTR while online.

To work around this issue, consider:

• Using a version of the Studio 5000 Logix Designer application other than v32.xx.
• When using v32.xx of the Studio 5000 Logix Designer application, make changes to the 1746-HSCE module offline and download those changes to avoid the anomaly, which prevents online property modification.

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

Invalid extended property error when verifying logic (1376604)

If the index tag of an indirectly addressed array is a Program-Scope, Local parameter for the program in which the logic exists, the logic will incorrectly fail verification.

To work around the error, change the index tag to a Program-Scope, Public parameter or a Controller Scope tag.

This anomaly first identified in version 32.03.

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.

SSV attribute must be uploaded (1721849)

When working with the Get System Value (GSV) and Set System Value (SSV) instructions in standard and safety tasks, the SSV attributes must be uploaded to be saved to the project.

This anomaly first identified in v32.00.

Incorrect Verification error on CASE…OF Statement in Structured Text (Lgx00224358)

A CASE…OF statement could be verified out of order, causing the verification error, Conflict exists in project verification state. Internal error.

To workaround the error, choose either of the following workarounds:

• In Studio 5000, select File → Compact → Delete cached build data to compact the database.

or

• Export the file to an L5K or an L5X file, and then re-import in Studio 5000.

This anomaly corrected in version 33.00.

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

Changing nested UDT to main UDT removes defined alarms from the nested UDT (2339160, 2339163, 2339161)

Changing a nested UDT structure of a tag removes alarms set for the other tags that contain a similar UDT structure.

This anomaly corrected in version 34.05, 35.05.

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

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.

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.

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.

​Function Block Diagram Add-On Instruction does not verify with tag-based alarm attribute references (2334449)​

When referencing two or more alarm attributes from the same alarm in a Function Block Diagram Add-On Instruction (AOI), the references won’t verify and will display the following error.​

“Another language element’s data overlaps with this one. You can use cross-reference to find other instances of this data.”​

This anomaly is not present in Ladder or Structured Text AOIs.​

This anomaly was corrected in version 36.00.

This anomaly first identified in version 31.00.

​Fatal error when Copying in Ladder Logic, Function Block Diagram, or Sequential Function Chart routines (LGX00223558)

​Fatal error 0x80042847 occurs when the clipboard cannot be accessed while performing a copy of ladder rungs. This could occur when holding down the copy shortcut CTRL + C for approximately 30 seconds.

​The fix for this anomaly is to show an error, ​OpenClipboard Failed​, that can be acknowledged without closing the software.

This anomaly was corrected in version 33.00.

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

• ​​The line in focus changes during an edit.
• ​The text regions do not fully expand or collapse when commanded using keyboard shortcuts.
• ​The application encounters a fatal error.

​This anomaly first identified in version 32.00.

Error 12740-0 Failed to import file when importing AOI with FactoryTalk Security (1301873)

Exporting an AOI using FactoryTalk Security and selecting the checkbox for Use only the selected Security Authority… results in the error shown below during the import of the AOI.

To work around this issue, clear the checkbox for Use only the selected Security Authority… during AOI export. The AOI is imported without error.

Refer to Knowledgebase BF27265 for additional information.

This anomaly first identified in version 30.00.

This anomaly is corrected in version 33.00.

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

• You launch Controller Properties and attempt to change the controller type. 
• You open a CAM Editor and scroll within the editor window.

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

Functional changes for Studio 5000 Logix Designer, version 32.04.00

The Logix Designer application version 32.04.00 has these functionality changes.

When transitioning from Run to Program mode, a blinking Run LED indicates that the controller is currently processing the mode change request. The Run LED changes to a solid on once the controller has entered Run mode.

In this release, bit addressing of USINT, UINT, UDINT, ULINT, and LINT is not supported for ONS, OSF, and OSR instructions.

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. (Lgx00230366, Product Safety Advisory 2017-10-002)

Importing an Add-On instruction into a project using a CompactLogix 5380 and GuardLogix 5580 controller from a project using a GuardLogix 5570 controller generates a warning that the Add-On Instruction safety signature changes after download. (Lgx00221440)

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

Application notes for Studio 5000 Logix Designer, version 32.04.00

These are the application notes for the Logix Designer application version 32.04.00.

PanelView is now compatible with version 21.05 Add-On Profiles. 

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

While the programming software continues to extend its functionality with each new release, the supported physical controllers 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, in most cases, provides a means to support the older hardware. If migrating from one controller to another, a project that is created for one controller is 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 provides an appropriate warning and automatically provides 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 the 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 to contain the 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 this table as a guide for the recommended communication software to use with select modules.

Starting with version 31.00 of the 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 Workstation Options, select Structured Text Editor > Font/Color.
3. In Font, choose Courier New.
4. In Size, choose 10. 

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

• Export the version 11.00 project file to a .L5K file, and then import the .L5K project file into version 21.00 and later.
• Convert the project from version 11.00 to version 12.00 through version 20.00 before converting the project to version 21.00 and later. 

The Logix Designer application sometimes exceed memory when multiple large routines are opened and resized to fit the full window using the View>Zoom>Fit to Window command. To work around this Instead 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 was never run in the version 31.00 of the 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 and reinstall the FactoryTalk Activation Manager.

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.

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 the Logix Designer application, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:

• When previous versions of the Logix Designer application are installed after version 30.00, .NET Framework 4.6 sometimes 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 application 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 that is created in a release earlier than version 29.00, the signature breaks for that Add-On Instruction. Unseal and then reseal 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.

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.

Some Boolean members of the AsixSafetyFaults 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. This 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.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 relock them. Download the project with the relocked 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 that are 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 that are made by other vendors that use MSXML 4.0, contact the vendor for questions about the security risk that is associated with MSXML 4.0.

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

The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").

The following 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)

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

The Logix Designer application version 32.00 supports CIP Security. However, its default communications software is RSLinx Classic. To enable CIP Security communication with controllers, FactoryTalk Linx must be selected as the communications software. To do this:

Open the Logix Designer application.

Close any open projects.

On the menu, select Communications > Select Communication Software.

In Select Communication Software, choose FactoryTalk Linx, then select OK.

A verification message appears with information about some controllers not being supported by FactoryTalk Linx. Select OK.

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.