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

Logix Designer application version v31.01.01 has no new or enhanced features.

This anomaly first identified in version 31.00.00

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

The Logix Designer application generated a fatal error when the slot number was changed on a 1734 module.

This anomaly first identified in version 31.01.

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

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.

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.

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.

Output state user defined value must be 0 when Hold Last State is selected

Studio 5000 Logix Designer v28

A module fault on the 1758-OF8 of: (Code 16#0009) Module Configuration Rejected: Parameter error. Additional Fault Code 16#000e will remain in a fault state after a reset of the slot and when the OK LED is green. As a workaround, the Output State User Defined value must be set to 0 when Hold Last State is selected in the 1756-OF8 module. (Lgx00164117)

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.

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.

Trend restarts from the beginning when Pause is clicked (Lgx00184775)

Studio 5000 Logix Designer v29.00

When you click Pause during trending, the trend sometimes starts over from the beginning. (Lgx00184775)

Phase Manager and Sequence Manager sometimes show different phase states (Lgx00183769)

Studio 5000 Logix Designer v29.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.

Low controller memory can prevent connection to the controller (Lgx00179908)

Studio 5000 Logix Designer v29.00

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

Changing Data Context in Add-On Instructions does not change the description and project documentation in Data Context tab(Lgx00185356, Lgx00185438, Lgx00185439, Lgx00186196)

Anomaly first identified in Studio 5000 Logix Designer v28.00

When you select a tag in the Data Context menu in the Add-On Instruction Parameters and Local Tags dialog box, the Properties pane displays the description and project documentation for a tag from the Add-On Instruction Definition Data Context but not from the Add-On Instruction Instance Data Context. Editing the description and properties in this case does not change the description and properties for the selected Data Context tag, but instead changes the description and properties for the Add-On Instruction Instance Definition.

Follow these instructions to work around the issue:

• View and edit the description and properties from the Program Parameters and Local Tags editor for the instance tag rather than from the Add-On Instruction Parameters and Local Tags editor.

Downloading a PointIO project may cause error 16#0205 (Lgx00190599)

Anomaly first identified in Studio 5000 Logix Designer v28.02

When you add a module to a PointIO rack offline, the module is configured for slot 1 by default. When you update the module profile with the correct slot position and download the project to the controller, error 16#0205 occurs.

Follow these instructions to work around the issue:

• Go offline, remove the module, and add it again in the correct slot.

May not be able to select the correct revision when adding 2715 HMI PanelView 5500 HMI module to Logix Designer (Lgx00191064)

Anomaly first identified in version 30.00

When adding a 2715 HMI PanelView 5500 HMI into the I/O Configuration tree in the Logix Designer application, the Module Definition Revision will be 2.001, even if you are connecting to a V3.xxx PanelView 5500. There is no selection to pick a V3.xxx revision. This will still operate correctly if you choose Compatible Module for the Electronic Keying.

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.

Routines may not indicate an Overflow Fault setting mismatch (Lgx00190654, Lgx00190708)

Anomaly first identified in version 30.00

If you create a routine and lock it, and then change the Report Overflow Faults setting on the Controller Properties dialog box - Advanced tab, the fault reporting behavior might not match what you expect. For example, if you lock a routine with the Report Overflow Faults setting unselected, but then select the setting and download the project to the controller, no overflow would be reported for that routine. If you lock a routine with the Report Overflow Faults setting selected, but then unselect the setting and download the project to the controller, no overflow would be reported for that routine, but you could still experience the possible decrease in runtime performance and increase in download time.

Logix Designer application Launcher can fail when you click About > Support (Lgx00190760, Lgx00190865)

Anomaly first identified in version 30.00

The Logix Designer application Launcher can fail when you click About > Support. This can happen when the Logix Designer application is installed on the Microsoft Windows 10 operating system, you log into Windows with User Access Control (UAC) disabled, and Microsoft Edge is the default browser.

Use one of these steps to work around the issue:

• Enable UAC.
• Set the default browser to an application other than Microsoft Edge.
• Open an Internet Explorer window and browse to Rockwell Automation Support at this URL: http:www.rockwellautomation.com/support/

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

Some PlantPAx P_PIDE Add-On Instruction instance values were set to denormalized low REAL values upon import of a P_PIDE 4.00.00 Add-On Instruction into a project that contained a P_PIDE 3.5.xx Add-On Instruction.

This anomaly first identified in version 18.00.

Major fault in rung calling imported Add-On Instruction (Lgx00230009)

The Logix controller generated a major fault when an Add-On Instruction was imported into the project with an edited import file that was improperly formatted.

This anomaly first identified in version 28.00.

Anomalous behavior sometimes occurred when using indirect addressing to a Boolean tag within an Add-On Instruction data type containing an alias parameter.

This anomaly first identified in version 28.03.

After an Add-On Instruction was downloaded, uploading the project caused one of the Add-On Instruction's multi-dimensioned array parameter tag to become invalid. The Logix Designer application generated the error: USER_CONTROL, op errand 1: Invalid size of array. Argument must match number of dimensions.

This anomaly first identified in version 20.04.

After changing a BOOL tag value to Decimal, and then saving, closing, and reopening the project file, the value had reset to Float. A BOOL tag reset to Float disabled manual changing of the value between 0 and 1.

This anomaly first identified in version 20.00.

Manually setting the time when using CompactLogix 5370 1769-L33ER, 1769-L24ER, 1769-L36ERM, and 5069-L340ERM controllers caused the time to set to the previous hour.

This anomaly first identified in version 30.01.

Converting a version 20.00 project that contains an SMC EX250-SEN1 caused numerous errors and missing logic when verifying the project.

This anomaly first identified in version 28.00.

When working within a Compact GuardLogix or GuardLogix 5370 or ControlLogix or GuardLogix 5570 controller, the structured text routine verified correctly but also generated an error upon exporting and importing an L5X file. Deleting and re-entering the semi-colon from the rung fixed the error.

This anomaly first identified in version 29.00.

A structured text routine showed errors on previous lines of approved code after switching to online edit. Adding and then removing a space on the error line removed the error.

This anomaly first identified in version 31.00.

Following the execution of a specific series of software actions, some or all of the controller's Safety Routines may not execute. These operations include using the Compact Project File feature along with the Delete cached build data option.

This anomaly first identified in version 31.00.

When the Logix Designer application scanned source protection licenses, if licenses were not retrieved, source protected routines were automatically closed.

This anomaly first identified in version 26.00.

Using a GuardLogix controller project and aliasing a standard global tag to a standard local tag while offline, selecting P010_S100_SEQ in the alias section caused the Logix Designer application to generate the error: Failed to set tag "xxx" target component specifier.  Access Denied - This edition of Logix Designer does not permit this action, error identifier 11187-80043B96.

This anomaly first identified in version 30.00.

Trying to upgrade the project in the Controller Properties dialog box, from v20.00.00 to v30.00.00, maintaining the same controller, causes a fatal error.

This anomaly first identified in v20.01.

When using a 1756-L8 controller and using an LBL and JMP to create a loop that produces a watchdog fault, and a rung above the LBL has an NOP, a fault occurs that appears to clear. A return watchdog fault does not clear. This fault occurs when there is a rung above the LBL that has only an NOP.

This anomaly first identified in version 30.00.

In encrypted Add-On Instructions, the boxes in the Alias For column for Input and Output parameters appear editable. However, they are read-only, and an error appears when editing is attempted.

This anomaly first identified in version 31.00.

When an Equipment Sequence contains a tag whose name contains less than four characters, the project fails to upload from the controller.

This anomaly first identified in version 30.00.

To work around this issue, rename the tag with a name that contains at least four characters.

Attempting to import some Add-On Instructions into an existing project generates the error message: Failed to import <file name>. Unable to parse the L5X content.

This anomaly first identified in version 17.00.

To work around this issue, export the Add-On Instruction, modify the file description to remove dashes. Or, open the L5X file in a plain text editor and modify the description to remove dashes. Import the Add-On Instruction.

For the ControlLogix 5380 and 5580 controllers, a Boolean InOut parameter in an Add-On Instruction when referencing the .31 bit of a DINT on the outside of the Add-On Instruction, sets the 22nd bit, not the 32nd bit, of that DINT.

This anomaly first identified in version 30.00.

Resizing columns in the Cross Reference window do not remain after closing and reopening the Cross Reference Window.

This anomaly first identified in version 31.00.

Import module from an L5X file does not work for 1756-DHRIO module in version 30.00.00.

This anomaly first identified in version 30.00.

Adobe Acrobat Reader DC, used by the Start Pages, causes the Logix Designer application to perform slowly. Version 31.00.00 removed the dependency of requiring Adobe Reader and removed the Start Pages. Access Online Books and Vendor Sample Projects from the Help menu.

This anomaly first identified in version 28.00.

For the 1756-L7 and CompactLogix 5370 controllers, Studio 5000 Logix Designer hangs during generation of a safety signature and generate a fault message. Going online with the controller shows the controller contains a safety signature.

This anomaly first identified in version 30.00.

The Logix Designer application has been upgraded to a version of MSXML that is supported by Microsoft.

This anomaly first identified in version 20.01.

Source tag for MSG data cannot be CONSTANT (Lgx00197226)

The Source tag for MSG data cannot be CONSTANT. The solution is, after the rung import is complete, open Controller Tags, select Edit Tags tab, and clear Constant on all the related tags.

This anomaly first identified in version 30.00.

Several instructions (ADD, SUB, MOV) in a routine protected with License Based Source Protection give wrong results. These instructions use arguments that are directly referencing Public parameters from another Program and these Public parameters in the other program are aliases to members of a Local array. When running, the values of these specific arguments are taken from Public parameters within the same Program where the routine resides. The error occurs only when a P&E routine directly references an Input or Public alias parameter belonging to a different program. All version of License Based Source Protect are affected.

This anomaly first identified in version 30.00.

If an encrypted Add-On Instruction has a description on any of its Local tags or routines, and the Add-On Instruction is Locked while Online, then you cannot re-download the Add-On Instruction without the Wibu license.

This anomaly first identified in version 30.00.

The error Communications request too large for network generates when try to run the trend.

This anomaly first identified in version 28.01.

To work around this issue, remove either the controller scoped tag or one of the local parameters.

With 1756-L8 controllers, when an axis, CIP axis, or Virtual axis is referenced via an InOut Parameter, SSV/GSV commands generate a compiler error, and the routine does not download.

This anomaly first identified in version 28.00.

To work around this issue:

• Remove the connection to the axis.
• Use the controller tag directly in the SSV.

This sequence of events can result in unexpected tag values:

1. An Add-On Instruction contains an alias parameter that points to a member of a local tag.

2. The alias parameter is changed to a base tag, either by editing the AOI definition directly or by importing a modified Add-On Instruction that overwrites the existing Add-On Instruction.

3. The instance values for the previously aliased parameters now contains unexpected values.

This anomaly first identified in version 18.00.

Follow one of these steps to work around the issue:

• To replace all values in all instances of the modified Add-On Instruction with the default values, double-click the Parameters and Local Tags folder for the modified Add-On Instruction, then click Copy default values in the Monitor Tags window.  This replaces all existing values for tags of this Add-On Instruction type with their default values.
• To replace the values for only the previously aliased parameters, in the Tag Monitor window, select each Add-On Instruction instance from the Data Context menu and then modify the values for the desired parameters.

When two sessions of the Logix Designer application are online to the same controller and the drives PF755-EENET, revision 14.00.00 Add-On Profile is open in both projects, changing and applying a drive value in one project is not reflected in the other project.

• In the Module Properties dialog box, Connection tab, the two properties RPI and Unicast are not updated. The other properties are updated correctly.
• When the Add-On Profile has an update that is not applied and the project is saved, the changes are saved, but the Add-On Profile shows the update as not applied, and the Apply button is enabled.
• When the Module Properties dialog box, Connection tab is the focus and the Add-On Profile is deleted from the I/O tree, the Logix Designer application stops performing. 
• When the Add-On Profile Overview page is the focus and the Add-On Profile is deleted from the I/O tree, the Add-On Profile does not display the module deleted page or a drive representation of the page.

This anomaly first identified in version 31.00.

Adding a device with an EDS AOP while online causes the Logix Designer application to shut down unexpectedly.

This anomaly first identified in version 30.00.

After installing version 30.00 or the version 30.00 AOP Bundle, adding an ENBT, ENT2T or EN2TR module causes a fatal error.

This anomaly first identified in version 20.00.

The Logix Designer application fails to update the Add-On Instruction definition when changes are made to Add-On Instruction parameters or local tags, but no changes are made to Add-On Instruction logic. For example, deleting a local tag from the Add-On Instruction definition, but not changing the instruction logic, can produce unexpected behavior. This anomaly affects only CompactLogix 5380, Compact GuardLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 controllers.

This anomaly first identified in version 31.00.

Attempting to search a tag’s cross-reference multiple times may cause the software to crash.

This anomaly first identified in version 20.04.

Import sometimes fails when importing a generic module or a communication module with a configurable IP address.

This anomaly first identified in version 31.00.

The Logix Designer application fails to correlate the project when importing a source protected Add-On Instruction.

This anomaly first identified in version 31.00.

The Online Edit Toolbar displays the wrong icons or no icons when the size of the text is set at 125% in the Display Control Panel.

This anomaly first identified in version 31.00.

An immediate value out of range error occurs in the Logix Designer application when the Positive and Negative Travel Limits operands in the SLP instruction are set to a negative value for immediate type values.

This anomaly first identified in version 31.00.

When using LBL and JMP instructions to create a loop to test a watchdog fault, the fault sometimes fails to clear after repeated tests.

This anomaly first identified in version 30.00.

When projects are converted to version 31.00, the layout in SFC routines is sometimes corrupted.

This anomaly first identified in version 31.00.

In large projects containing thousands of tags, component tracking impacts online editing performance in the Studio 5000 Logix Designer application. Component tracking can lead to delays of up to several seconds when finalizing online edits or creating online tags, and the impact can occur both when component tracking is enabled and disabled. This anomaly affects only CompactLogix 5380, Compact GuardLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 controllers.

This anomaly first identified in version 31.00.

When working in a routine, in the Watch view, select Current Routine, then select Quick Watch. Open Controller Tags. In the Tag Editor, cut a tag and paste the tag in the last cell of the Tag Editor. The Logix Designer application may stop performing depending on the user's next action.

This anomaly first identified in version 30.00.

The MVI69E-MBTCP module sometimes sends write commands, even though the write data from the controller to the module has not changed. This results in the module sending inaccurate write data.

This anomaly first identified in version 30.00.

The Logix Designer application stops performing when changing controllers with different number of ports (Lgx00207531)

When changing controller types with different number of ports, opening the Port Configuration tab prior to changing the controller type on the General tab causes a fatal error in the Logix Designer application.

This anomaly first identified in version 31.00.

When an axis, a CIP axis, or a virtual axis is referenced using an InOut parameter, motion commands respond as expected. SSV and GSV commands cause the Logix Designer application to return a compiler error.

This anomaly first identified in version 28.00.

When two SFC routines are open, selecting Fit to Window for one of the routines causes the Logix Designer application to shut down unexpectedly.

This anomaly first identified in version 30.00.

Projects that contain alarm sets sometimes fail to upload from the controller.

This anomaly first identified in version 31.00.

The Reset Counter button on the Controller Properties > Port Diagnostics window sometimes fails to reset the counter.

This anomaly first identified in version 30.00.

The Structured Text editor sometimes runs very slowly, even when offline.

This anomaly first identified in version 31.00.

When the computer running the Logix Designer application is connected to Port 1 on a CompactLogix 5370 or ControlLogix 5370 controller, disabling Port 2 sometimes prevents offline project downloads.

This anomaly first identified in version 31.00.

Removing unused tags in the Logix Designer application version 31.00 can cause a fatal error.

This anomaly first identified in version 31.00.

The controller prevents the Logix Designer application Trend Server from reading a tag when the tag's External Access is set to None.  

This anomaly first identified in version 31.00.

Red flag and error message when attempting import with locked component (Lgx00190571, Lgx00190326)

The Logix Designer application displays a red flag and sometimes the error Unable to overwrite [component] while online. The locked routine already exists in project and there are no differences in locked logic when attempting to use Import to overwrite an existing locked component with an identical locked component.

This anomaly first identified in version 30.00.

The Logix Designer application Launcher sometimes fails when selecting About > Support. This can happen when the Logix Designer application is installed on the Microsoft Windows 10 operating system, the user logs into Windows with User Access Control (UAC) disabled, and Microsoft Edge is the default browser.

This anomaly first identified in version 30.00.

When adding a 2715 HMI PanelView 5500 HMI into the I/O Configuration tree in the Logix Designer application, the Module Definition Revision will be 2.001, even if connecting to a V3.xxx PanelView 5500. There is no selection to pick a V3.xxx revision. This will still operate correctly if Compatible Module for the Electronic Keying is chosen.

This anomaly first identified in version 30.00.

When selecting a tag in the Data Context menu in the Add-On Instruction Parameters and Local Tags dialog, the Properties pane displayed the description and project documentation for a tag from the Add-On Instruction Definition Data Context but not from the Add-On Instruction Instance Data Context. Editing the description and properties in this case did not change the description and properties for the selected Data Context tag, but instead changed the description and properties for the Add-On Instruction Instance Definition.

This anomaly first identified in version 28.00.

When updating an Add-On Instruction by deleting a local tag and the Add-On Instruction parameters definitions were not updated, this could lead to Add-On Instruction parameters being overwritten with values from internal tags in the Add-On Instruction.

This anomaly first identified in version 31.00.

When working with an Add-On Instruction that used user-defined data types and arrays of BOOLs, the Logix Designer application received a compiler error when importing from version 30.00 to version v31.00.

This anomaly first identified in version 30.00.

When copying and pasting multiple function block elements to a new sheet, Studio 5000 Logix Designer crossed the wires over function blocks in the new sheet. 

This anomaly first identified in version 31.00.

When adding a 2715 HMI PanelView 5500 HMI into the I/O Configuration tree in the Logix Designer application, the Module Definition Revision was 2.001, even if connecting to a V3.xxx PanelView 5500. There was no selection to pick a V3.xxx revision. The application still operated correctly if the user chose Compatible Module for the Electronic Keying.

This anomaly first identified in version 30.00.

After adding a negative value in Hookup Tests > Motor and Feedback > Test Distance, an error dialog opened and the Logix Designer application stopped performing. Closing the application required using the Task Manager > End Task function.

This anomaly first identified in version 31.00.

When working in a routine, in the Watch view, select Current Routine, then select Quick Watch. Open Controller Tags. In the Tag Editor, cut a tag and paste the tag in the last cell of the Tag Editor. The Logix Designer application may have stopped performing depending on the user's next action.

This anomaly first identified in version 30.00.

After installing .NET 4.8 Framework, when using the search feature in Alarm Manager > Alarms, the Logix Designer application stopped performing.

This anomaly first identified in version 32.00.

The Logix Designer application had a compiler error when finalizing online edits or when creating a project offline. This anomaly was only present in ControlLogix 5580, CompactLogix 5480, and CompactLogix 5380 controllers, and Windows 10 workstations that use Microsoft AppLocker.

This anomaly first identified in version 28.00.

Anomalous behavior may occur when using indirect addressing to a Boolean tag within an Add-On Instruction data type containing an alias parameter.

This anomaly first identified in version 28.03.

The Logix Designer application experienced a fatal error when following these steps:

• Adding a member to a user-defined data type and applying the change.
• Adding a tag that has the data type of the user-defined data type to a structured text or sequential function chart routine.
• Adding a second new variable to the user-defined data type and applying the change.

This anomaly first identified in version 31.00.

Applying changes after changing the slot number of a 1734 module caused the Logix Designer application to stop performing.

This anomaly first identified in version 31.00.

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 was used and the Windows User Account Control (UAC) setting was set at a level higher than Never notify, a UAC dialog box sometimes appeared 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 did not reset.

This anomaly first identified in version 30.00.

When working with user-defined data types, the Logix Designer application stopped performing under these conditions:

• Edited the user-defined data type and then selected OK or Apply.
• Edited large structures.
• Created a tag in the user-defined data type. Added the data type in a structured text routine without adding the tag to the structure. The tag showed as red. Used the monitor function to add the tag and an element to the data structure.

This anomaly first identified in version 31.00.

In a project with an invalid program parameter that is connected to an I/O tag, after deleting the invalid program parameter connection, the error icon displayed in several areas of the Logix Designer application.

This anomaly first identified in version 30.02.

The Logix Designer application stopped responding when editing a tag in a CASE_OF statement.

This anomaly first identified in version 31.00.

After performing multiple cross reference tasks and closing the window after tasks, the Logix Designer application stopped performing with error 0xc0000005.

This anomaly first identified in version 20.01.

When working with an Equipment Phase diagram, could download project, but could not upload the project. This anomaly applies only to CompactLogix 5370 and ControlLogix 5570 controllers.

This anomaly first identified in version 30.00.

Prior to download and installation of corrected software, do not compact the project with Delete cached build data selected and then go online (without downloading) and generate a safety signature. If you do, the project ACD file will contain this anomaly.

This anomaly is only possible when used with the following Rockwell Automation Safety controller families:

• 5580 GuardLogix, catalog numbers 1756-L8xES(K).
  Note that safety applications implemented with or without a 1756-L8SP(K) safety partner are affected by this anomaly.

• 5380 Compact GuardLogix, catalog numbers 5069-L3xS2(K) and 5069-L3xS3(K)

This anomaly first identified in version 31.00.

The Logix Designer application Launcher sometimes failed when selecting About > Support. This happened when the Logix Designer application was installed on the Microsoft Windows 10 operating system, the user logged into Windows with User Access Control (UAC) disabled, and Microsoft Edge was the default browser.

This anomaly first identified in version 30.00.

When creating a watchdog fault to test a fault handler routine by using LBL and JMP instructions on the same rung, if an NOP rung was above, when a watchdog fault occurs, the fault handler routine will not clear the fault.

This anomaly first identified in version 30.00.

Could not overwrite protected content online (Lgx00190571)

The Logix Designer application displayed a red flag and sometimes the error Unable to overwrite [component] while online. The locked routine already exists in project and there are no differences in locked logic when attempting to use Import to overwrite an existing locked component with an identical locked component.

This anomaly first identified in version 30.00.

When the Logix Designer application scanned licenses on a dongle, when licenses were not retrieved, the application closed the source protection routines.

This anomaly first identified in version 26.00.

Routine protected with License Based Source Protection with arguments that referenced Public parameters from another program that were aliases to members of a Local array, received values from a Public parameter in the program of the routine.

This anomaly first identified in version 30.00.

When online with the controller, a licensed sourced protected Add-On Instruction with descriptions in local tags or routines, could not download the Add-On Instruction without the Wibu license.

This anomaly first identified in version in version 30.00.

When version 30.00 and version 31.00 of the Logix Designer application were both installed on the same computer, and trending had never been run in the version 31.00 of the Logix Designer application, trending failed to run in the version 30.00 of the Logix Designer application. 

This anomaly first identified in version 30.00.

When the Size of each capture option was set to No Limits, the Logix Designer application will show a Trend Server throws an exception error. A TBS file with the trend results is created, but not usable.

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

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.

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

Logix Designer version 31.01.01 has the following changes in functionality since the last release.

The Add On Profile (AOP) library shipped with version 31.00 and later updates many 1756 and 1794 I/O device profiles from Classic Profiles to AOPs. These updated Profiles affect all installed Logix Designer and RSLogix 5000 versions on the workstation. Do not share project .ACD files with these updated 1756 and 1794 I/O device profiles with workstations that have installed an earlier versions of the AOP Bundle. For proper compatibility, make sure all workstations are using version 31.01 when sharing ACD projects with these updated Profiles.

Refer to Rockwell Automation Knowledgebase Answer ID 1075943.

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

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

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

Internal direct communications error. Call Technical Support.

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

This is not an anomaly in Logix Designer.

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

Application notes for Studio 5000 Logix Designer version 31.01.01

The following are the application notes for Logix Designer version 31.01.01.

Supported Logix Controllers

While the programming software continues to extend its functionality with each new release, the physical controllers that it supports will vary. New controllers are added, and in some cases, support for existing controllers may be removed. While a specific controller may not be supported by the current release, the side-by-side installation of multiple versions of the software will, in most cases, provide a means to support the older hardware. If migrating from one controller to another, a project created for one controller can be easily converted to another controller using the Controller Properties configuration dialog box within the software.

If opening a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software will provide an appropriate warning and will automatically provide the option to convert the project to one of the controllers supported by the release.

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

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.

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.

When you install version 30.00.00 of Logix Designer, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause the following issues:

When updating the firmware as part of the project download, the Update Module Firmware dialog box may display an error that it cannot find the location of the updated firmware files.

The installation of ControlFLASH version 15.01 moves the DMK files located in the ControlFLASH installation folder (C:\Program Files (x86)\ControlFLASH for 64-bit operating systems or C:\Program Files\ControlFLASH for 32-bit operating systems) to a new folder located in C:\Users\Public\Documents\Rockwell Automation\Firmware Kits.

Older versions of ControlFLASH and Logix Designer place DMK flash files in previous ControlFLASH file locations.

The work around if ControlFLASH cannot find the location of the DMK files:

1. In the Choose Firmware Revision dialog box, click Browse. ControlFLASH defaults to C:\Users\Public\Documents\Rockwell Automation\Firmware Kits.
2. Depending on the operating system, browse to the location of the DMK files.

For more information, refer to Rockwell Automation Knowledgebase Answer ID 1071313 .

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.

When using a Custom RSLogix 5000 Motion Database in RSLogix 5000 software versions 12.00.00 through 17.00.00, update the motion database to work with versions 18.00.00 or later. The following table lists the motion database revisions that are used with these application versions.

* Before a Custom Motor can be used in version 18.00.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.

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.

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.

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