Access Denied dialog box does not appear when users without FactoryTalk Security access attempt to modify Motion Configuration (Lgx00184951)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio Logix Designer v30.00

When a user without Motion: Modify Configuration security credentials attempts to modify the motion configuration, an Access Denied dialog box does not appear.

System requirements for Studio 5000 Logix Designer version 30.xx

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

Hardware Requirements

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

Software Requirements

• Operating system and service pack compatibility:
  • Windows® 7 Professional (64-bit) with Service Pack 1
  • Windows 8.1 Professional (64-bit) with April 2014 Update Roll-up
  • Windows 10 Professional (64-bit) version 1607
  • Windows Server 2008 R2 Standard Edition with Service Pack 1
  • Microsoft Windows 8.1 Professional (64-bit)
  • Windows Server 2012 Standard Edition
  • Windows Server 2016

• .NET Framework 4.6

• This version of Logix Designer is expected to operate correctly on all other editions and service packs of the following operating systems but has not been tested:
  • Microsoft Windows 7
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows 8
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Windows 10
• The following prerequisite software is required with this version of Logix Designer application and will be installed when you install this release:
  • FactoryTalk® Services Platform v2.90.00
  • FactoryTalk® Activation Manager v4.00.02
  • RSLinx Classic v3.90.00
  • RSLinx Enterprise v5.90.00

• On Windows 8 and later, the Adobe® Flash Player ActiveX Control is included with the operating system. On Windows 7, the Adobe® Flash Player ActiveX Control must be downloaded and installed to operate the Logix Designer Start page. The Adobe Flash Player ActiveX Control can be downloaded from Adobe’s website at this URL: http://get.adobe.com/flashplayer/
• FactoryTalk® View Site Edition (SE) software and RSLinx® Enterprise communication software are required in order to fully use alarming capabilities.

• Be sure to check the software requirements for other Rockwell Software® products that you intend to install to be sure that these products are also compatible with the system.

• Logix5000 controllers and ControlLogix Motion modules in your system 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™.

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 )

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

Controller Message to Self

System Feature as of Firmware Revision 29.011

Catalog Numbers: CompactLogix™ 5380, ControlLogix® 5580

You can use a CIP Generic MSG to SELF to disable the Ethernet port, diagnostic web pages, and 4-character display.

For the 4-character display, you have these options:

• Disable the LCD Display (Project Name, Link Status, Port Status, and IP address not shown)
• Turn off just the Project name and Link Status messages
• Turn off just the Network Configuration messages (IP address)

Filter buttons missing when importing rungs into an AOI (Lgx00156489, Lgx00179907, Lgx00183130, Lgx00183131, Lgx00183132, Lgx00183133)

Anomaly

Studio 5000 Logix Designer v27.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When you import rungs into an Add-On Instruction, the following filter options are missing when you click Final Name on the Configure Tag References pane of the Import Configuration dialog box:

• Input

• Output

• InOut

• Local Filter

Only the Show controller tags and Show program tags check boxes are available.  

Creating alias for Cam, Cam Profile, or Output Cam tag generates error (Lgx00180076, Lgx00180235, Lgx00186575)

Corrected Anomaly with Studio 5000 Logix Designer v29.00, v28.02, and v30.00

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

1. Power down the controller.
2. Disconnect the controller battery.
3. Wait five minutes.
4. Reconnect the battery.
5. When the controller powers up, re-download the project.
   

Cannot delete tag from Safety project (Lgx00184580, Lgx00184569)

Studio 5000 Logix Designer v29.00

Correct Anomaly with Studio 5000 Logix Designer v30.00

Link error sometimes occurs after new module has been created (Lgx00179911, Lgx00164891)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Instructions incorrect in Structured Text Editor when using drag-and-drop on more than one instruction (Lgx00184727)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When you copy instructions from the Ladder Editor to the Structured Text Editor using drag-and-drop, the instructions are incorrect in the Structured Text Editor when you copy multiple instructions at the same time. (Lgx00184727, Lgx00165518)

As a workaround, copy the instructions from the Ladder Editor to the Structured Text Editor by copying them one at a time.

Tag properties sometimes disappear from Properties pane for AOI tags (Lgx00184764, Lgx00184554)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When you update or insert a value for an Add-On Instruction tag and then click outside the Tag editor, the tag properties disappear from the Tag Properties pane. The tag properties reappear when you select the updated tag.

Standard tags mapped to safety tags sometimes cannot be edited in secure project (Lgx00184776, Lgx00184571)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Users attempting to edit a standard tag that is mapped to a safety tag in a secured project sometimes cannot edit the standard tag.

New FactoryTalk Security users sometimes fail to appear in FactoryTalk Security when Logix Designer is open (Lgx00184021, Lgx00184586)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00 

When you add a new user in FactoryTalk Security while the Logix Designer application is open, the new user sometimes does not appear in FactoryTalk Security until you close the Logix Designer application.

Changing 5380 Controller EtherNet/IP Mode incorrectly modifies MSG path port (Lgx00184756)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When you change the Ethernet/IP Mode on a 5380 controller, the Logix Designer application sometimes incorrectly modifies the communication path for an MSG instruction.

Controller displays incorrect date and time (Lgx00182342)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

The controller sometimes displays an incorrect date and time: the year is displayed as a large number (for example, 586,384) and the month, day, and time are incorrect.   

Possible communication with wrong device on 5380 controller when changing Ethernet/IP Mode (Lgx00185070, Lgx00184949)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When converting CompactLogix 5380, CompactLogix 5480 and ControlLogix 5580 projects, Invalid hostDataTypeID can cause fatal error (Lgx00185197, Lgx00181352)

Studio 5000 Logix Designer v29.00

Correct Anomaly with Studio 5000 Logix Designer v30.00

When creating Event task, Event configuration list can show unexpected module tags (Lgx00179922, Lgx00162453)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Several object-backed tags can be incorrectly created as local tags (Lgx00183744, Lgx00182809)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

• ALARM_DIGITAL
• ALARM_ANALOG
• HMIBC
• COORDINATE_SYSTEM
  

Safety Task Prevents Event Instruction from Triggering a Standard Task (Lgx00172306, Lgx00180423)

Corrected Anomaly in Firmware Revision 30.011 and Studio 5000 Logix Designer^® v30.00 

Known Anomaly First Identified in Version 20.013

Catalog Numbers GuardLogix^® 5570

If a project uses an event instruction in the Safety Task to trigger a Standard Task, the instance number for that Standard Task is locked into the Safety Task once a Safety Signature is created.

If you re-download the application, the instance number for the Standard Task changes. This does not change the instance number that is already locked into the Safety Task. This can cause the Safety Task to prevent the event instruction from triggering the Standard task, a major non-recoverable fault on the controller, or the Standard Task to not execute correctly.

MGSD can cause Group Overlap faults in systems with large number of axes (Lgx00174272,  Lgx00174469)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

The Motion Group Shutdown (MGSD) instruction can cause a Motion Group Overlap fault when used in a project that contains a large number of axes and the Coarse Update Rate is set too low.

As a workaround, increase the motion group's coarse update rate.  

• GuardLogix 5570 Family with firmware versions earlier than 30.011
• Compact GuardLogix 5370 family with firmware versions earlier than 30.011
• GuardLogix 5560 family with firmware versions 20.018 or earlier (latest firmware is version 20.018)

• GuardLogix 5580 family SIL2/SIL3, all firmware versions
• Compact GuardLogix 5380 family SIL2/SIL3, all firmware versions

Anomaly first identified in Studio 5000 Logix Designer v28.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

On CompactLogix 5370, ControlLogix 5570, Compact GuardLogix 5370, and GuardLogix 5570 controllers, ladder logic routines that are secured by Source Protection, both source-key protection and license-based protection, sometimes execute incorrectly after they have been overwritten by an online partial import.

Anomaly first identified in Studio 5000 Logix Designer v20.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

A fatal error may occur while online and deleting a new routine which hasn’t had assignment committed.

Anomaly first identified in Studio 5000 Logix Designer v20.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Wire auto-routing in Function Block Diagram has excessive cross patterns in certain configurations. 

Anomaly first identified in Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Some flags for ALARM_ANALOG and AXIS_CIP_DRIVE tags, when used in a Function Block Diagram (FBD), cause a compiler error when the project is downloaded to CompactLogix 5380, CompactLogix 5480, and ControlLogix 5580 controllers. In CompactLogix 5370, ControlLogix 5570, Compact GuardLogix 5370, and GuardLogix 5570 controllers, the download fails but appears to succeed.

To convert projects affected by this issue from earlier releases to version 30 and later, you must save the project as an .L5x or .L5k file and then import the project into version 30 or later.

Anomaly first identified in Studio 5000 Logix Designer v20.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

The default scope for tag creation defaults to Program if the program name happens to be the same as the controller name.

Anomaly first identified in Studio 5000 Logix Designer v21.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

In versions 21 and later, the Tag Overlay feature no longer warns about edits in the UDT editor, and descriptions in the UDT are editable.

Anomaly first identified in Studio 5000 Logix Designer v28.01

Corrected Anomaly with Studio 5000 Logix Designer v30.00

A compile error can occur when using an Add-On Instruction alias parameter and the Add-On Instruction is embedded inside a user-defined datatype (UDT).

Anomaly first identified in Studio 5000 Logix Designer v27.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

The Logix Designer application sometimes fails to upload the latest version of a cached XML file.

Anomaly first identified in Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Some unicode characters, such as quotation marks, cause project documentation and extended properties to fail to upload from the controller when the characters appear at the beginning of the content.

Anomaly first identified in Studio 5000 Logix Designer v28.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Project documentation and extended properties for associated tags sometimes fail to upload from the controller.

Anomaly first identified in Studio 5000 Logix Designer v28.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

The default value of Motion Control Axis Object (MCAO) Attribute 608, Zero Speed, is 0, which can cause problems in vertical-load applications.

Anomaly first identified in Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When overwriting a rung with the importing logic as Finalize Edit, the deleted rung still appears in the routine after the Finalize Edits action is complete.

Anomaly first identified in Studio 5000 Logix Designer v28.01

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Specifying a bit in an INT or SINT tag in a JSR, SBR, or RET instruction can cause a major non-recoverable fault (MNRF).

Anomaly first identified in Studio 5000 Logix Designer v28.01

Corrected Anomaly with Studio 5000 Logix Designer v30.00

Extra rung comments in ladder logic are sometimes created when rungs containing comments created in a project configured for US English are imported into a project not configured for language switching.

Anomaly first identified in Studio 5000 Logix Designer v29.00

When the Logix Designer application starts up without Internet connectivity and with no security enabled, it can take up to two minutes to process a login.

FactoryTalk AssetCentre error caused by the Logix Designer application (961951, Lgx00225888)

The following error will appear in FactoryTalk AssetCentre: "ExtErr: Could not CoCreate RSLogix5000Services. Please re-install Logix5000." 

This anomaly is caused by a component of the Logix Designer application, RSLogix5000Services.exe, experiencing a fatal error during the compare operation. (View this error in the Windows Event Logs).

While the error in FactoryTalk AssetCentre can affect all asset versions, the version of software causing the error will be apparent in the Windows Event Logs.

This anomaly first identified in version 20.04.

Please refer to Knowledgebase document 1129799 for more information.

Disable Download Project Documentation and Extended Properties features

To include or exclude project documentation and extended properties from a downloaded project, select or clear the

5069 Compact I/O Firmware Files Not Stored to SD Card (00185281)

Known Anomaly First Identified as of Firmware Revision 29.011

Catalog Numbers: CompactLogix™ 5380, ControlLogix® 5580

Automatic Firmware Update (Firmware Supervisor) does not store the firmware files for 5069 Compact I/O™ modules to the Secure Digital (SD) card.

This anomaly first identified in version 29.00.

Filter buttons missing when importing rungs into an AOI (Lgx00156489)

When you import rungs into an Add-On Instruction, the following filter options are missing when you click Final Name on the Configure Tag References pane of the Import Configuration dialog box:

• Input
• Output
• InOut
• Local Filter

Only the Show controller tags and Show program tags check boxes are available.

This anomaly first identified in version 23.00.

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

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.

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

This anomaly first identified in version 29.00.02.

Changing 5380 Controller EtherNet/IP Mode incorrectly modifies MSG path port (Lgx00184756)

When you change the Ethernet/IP Mode on a 5380 controller, the Logix Designer application sometimes incorrectly modifies the communication path for an MSG instruction.

This anomaly first identified in version 29.00.02.

Several object-backed tags can be incorrectly created as local tags (Lgx00183744)

The Logix Designer application normally reports an error and does not allow you to configure an object-backed tag as a local tag. However, for the following data types, the Logix Designer application incorrectly allows you to configure an object-backed tag as a local tag:

• ALARM_DIGITAL
• ALARM_ANALOG
• HMIBC
• COORDINATE_SYSTEM

This anomaly first identified in version 29.00.02.

MGSD can cause Group Overlap faults in systems with large number of axes (Lgx00174272)

The Motion Group Shutdown (MGSD) instruction can cause a Motion Group Overlap fault when used in a project that contains a large number of axes and the Coarse Update Rate is set too low.

As a workaround, increase the motion group's coarse update rate.

This anomaly first identified in version 28.00.01. 

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

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.

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/

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.

Redundancy-enabled Projects Sometimes Fail to Upload from The Controller Unless Original Download File Exists (Lgx00191976)

Corrected Anomaly as of Studio 5000 Logix Designer® v30.01.00 and v31.00.00

Known Anomaly first identified in version 30.00.00 of Studio 5000 Logix Designer

When you attempt to upload a redundancy-enabled project from the controller, the upload fails unless your computer contains the same project file that was originally downloaded.

The Studio 5000 Logix Designer application gives an error that the project has redundancy disabled and controller firmware with a minor revision of .49 is required.

Rungs missing in routine after online edit with Logix Designer (Lgx00196898, Lgx00200753, Lgx00201030)

Anomaly first identified in Studio 5000 Logix Designer v28

Studio 5000 Logix Designer v28, v29, v30

Corrected Anomaly in Studio 5000 Logix Designer v30.01, v28.03

If online changes are made to a ladder logic routine within a ControlLogix 5580 or CompactLogix 5380 controller and those changes are assembled or tested, and subsequently removed, all rungs within the routine may be removed when the Go Online command in Logix Designer application is used to initiate the edit.

The rungs appear as missing within the Logix Designer editor. Controller projects that have been online edited continue to operate as expected until the Go Online command is used and a subsequent download of the resulting project file is performed.

All of the following conditions must be met for this anomaly to occur:

• The routine must have been created using the Logix Designer ladder logic editor.
• Online edits occurred and edits have been assembled or tested.
• Edits made to a ladder routine have been removed through a cancel operation or re-editing the routine to back out changes that have been made such that the resulting routine has not changed.
• Open a file in Studio 5000 Logix Designer application that does not have the changes and use the Go Online command to connect to the edited controller, forcing correlation of the online version with the offline version.

If these conditions are met, when the affected routine is opened in the Logix Designer ladder logic editor, all rungs within that routine are missing and the number of rungs reported by the Controller Organization within Logix Designer is zero. If the affected routine is opened an empty rung is added and project validation fails. However, if the affected routine is not opened, project validation will pass and allow download of the application to the controller with the affected routine now missing all rungs within the controller.

Important - The rungs appear as missing within the Logix Designer ladder editor, but controller projects that have been online edited continue to operate as expected within the controller until downloaded.

For complete information, see Knowledgebase article 1063358: Product Notice 2017-10-002 Logix Designer Ladder Logic Editor Missing All Rungs in a Routine when Online with Correlation after Online Edits are removed in ControlLogix 5580 and CompactLogix 5380.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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

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.

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

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.

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.

Routines do not warn on Overflow Fault Setting Mismatch (Lgx00190654, Lgx00190708)

When creating a routine and locking it, and then changing the Report Overflow Faults setting on the Controller Properties dialog box - Advanced tab, the fault reporting behavior might not match what is expected. For example, when locking a routine with the Report Overflow Faults setting unselected, but then selecting the setting and downloading the project to the controller, no overflow would be reported for that routine. If locking a routine with the Report Overflow Faults setting selected, but then clearing the setting and downloading the project to the controller, no overflow would be reported for that routine, but there might be a decrease in runtime performance and increase in download time.
This anomaly first identified in version 30.00.00.

Importing an L5K file (Lgx00194470)

Importing an L5K file for a 1756-DHRIO module in Studio 5000 Logix Designer version 30.00.00 causes a fatal error.
This anomaly first identified in version 30.00.00.

Module Definition Change button with 1756-L73 (Lgx00199251)

When creating a new project with a 1756-L73 controller on EtherNet/IP, adding a 1794-AENTR module, clicking the Change button under Module Definition, changing the Rack Connection, and then the Chassis Size, causes the Logix Designer application to lock and lose functionality.

This anomaly first identified in version 30.00.00.

Scaling automatically changes when axis properties page opens (Lgx00198118)

When opening an axis property page, if the system is missing the associated motor data because the custom motor file CMF may not have been installed, the property page could potentially reset the Load Type attribute. Additional data related to the Load Type is then modified. To correct this anomaly, if the motor data file cannot be found, the axis attribute is left in its current state.
This anomaly first identified in version 30.00.00.

Stator Leakage Reactance value incorrect in version 29.00.00 and version 30.00.00 (Lgx00198187)

The value for the Induction Motor Stator Leakage Reactance and the Induction Motor Rotor Leakage Reactance were incorrectly being set to the same value when an Induction motor was selected from the Motion Database. This has been corrected.
This anomaly first identified in version 30.00.00.

Coordinated System attributes internal access rules for GSV and SSV tag (Lgx00190407)

Several Coordinated system attributes indicated that they supported GSV access when they did not support this access. This has been corrected.
This anomaly first identified in version 30.00.00.

Start Pending Edits via Ctrl + Shift + S causes undocked Structured Text routine to lose focus (Lgx00204976)

When the Structured Text routine is in a pending routine edits state, the focus is moved to the Logix Designer application main window. The Structured Text routine state should be in Start Pending Routine and the focus should be on the Structured Text routine.
This anomaly first identified in version 30.00.00.

Not enough storage (Lgx00195006)

Not enough storage is available to complete this operation error displays when downloading, importing, or exporting a large number of SFC routines.
This anomaly first identified in version 30.00.00.

Copy function causes fatal error (Lgx00195320)

Fatal error occurs in Studio 5000 Logix Designer when copying a user-defined data type from a RSLogix 5000^® project version 21.00.00 or earlier into a project version 21.00.00 or later.
This anomaly first identified in version 30.00.00.

Search option causes fatal error (Lgx00196741)

Performing a Find Next in the Find in Routines dialog box while in a tag window causes the Logix Designer application to stop performing. This occurs when the Find in Routines dialog box is closed after performing a search in a routine.
This anomaly first identified in version 30.00.00.

Perform one of the following workarounds to address this issue:

Leave the Find dialog box open after performing a search. When opening a controller or program tag window, the Find dialog box updates the settings and works correctly.

Always open the Find dialog box first via Search > Find. For example, open a tag window and then open the Find dialog box. The Find in Tags dialog box opens.

Upgrading revision (Lgx00197111)

Attempting to upgrade the revision of a project from version 20.01.00 to version 30.00.00 while maintaining the same controller, causes a fatal error in the Logix Designer application.
This anomaly first identified in version 30.00.00.

Perform one of the following workarounds to address this issue:

Upgrade the revision to version 24.00.00 and then upgrade version 24.00.00 to version 30.00.00.

Export the L5K file in version 20.00.00. Create a new project in Studio 5000 Logix Designer using the From Import option. Import the exported L5K file back into the version 20.00.00 project.

Cannot overwrite Source Protected content online (Lgx00190326)

When content in a program is source protected, the modified content cannot be import into the project after it has been downloaded.
This anomaly first identified in version 30.00.00.

Redundancy switchover with test edits issue with Change Detection (Lgx00189950, Lgx00190153)

When redundancy is enabled but test edits of a tracked routine are not retained, and switchover occurs with test edits running, the Tracked State value on the redundant controller shows the tracked state value of the controller with test edits, even though the test edits are not running in the redundant controller.
This anomaly first identified in version 30.00.00.

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.

Upload fails with mismatch redundancy-enabled project file (Lgx00191976, Lgx00191570)

When attempting to upload a redundancy-enabled project from the controller, the upload fails unless the computer contains a version of the project file that was originally downloaded.
This anomaly first identified in version 30.00.00.

SSV/GSV on axis via InOut parameter (Lgx00207344)

When an axis is referenced via an InOut parameter, SSV/GSV commands return an error when building or downloading the application. This issue is also found when working with CIP and virtual axes. This is an issue with CompactLogix 5380, CompactLogix 5480, and ControlLogix 5580 controllers.

This anomaly first identified in version 30.00.

To work around this issue, remove the connection to the axis and set Usage to Public and Alias For to a controller tag.

Import from L5K file fails (Lgx00200538)

An import from an L5X file fails with a failed to import error. The import aborts and no changes are made to the project.

This anomaly first identified in version 30.00.

MSG instruction source data cannot be set to constant (Lgx00197226)

The Source Tag data for a MSG cannot be declared Constant.

This anomaly first identified in version 30.00.

Update to supported MSXML 6 (Lgx00193996)

Logix Designer application is using an older version of MSXML. Upgrade to version MSXML6 or a later version supported by Microsoft.

This anomaly first identified in version 30.00.

Incorrect bit set by Add-On Instruction (Lgx00209370)

For CompactLogix 5380 and ControlLogix 5580 controllers, a Boolean InOut parameter in an Add-On Instruction referenced to .31 bit of a DINT on the outside of the Add-On Instruction sets the .22 bit and not the .32 bit of the DINT. (Lgx00209370)

This anomaly first identified in version 30.00.

To work around this issue:

1. Do not use the bit.
2. Do not use InOut parameters if not needed.
3. Refer to the bit by an indirect address.

Creating watchdog fault with LBL and JMP (Lgx00212472)

When creating a watchdog fault to test fault handler routine with L8 controllers, if using LBL and JMP to create loop that will produce a watchdog fault and there is an NOP rung above the LBL a fault occurs.

This anomaly identified in version 30.00.

To work around this issue, delete the NOP rung or add an output instruction, such as an OTE or MOV, between the LBL and JP instructions

Source Protection causes incorrect value references (Lgx00219002)

Instructions in a routine protected with License Based Source Protection use arguments that are directly referencing Public parameters from another program. These Public parameters in the other program are aliases to members of a Local array. When running, the values of the specific arguments are taken from a Public parameter within the same program where the routine resides and not taken from the other program. When the routine is not protected, the values of the instruction argument are correct.

This anomaly first identified in version 30.00.

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

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.

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)

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.

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

Studio 5000 Logix Designer v29.00

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

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

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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

This anomaly first identified in version 20.04.

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

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.

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

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.

Undefined Tag error (Lgx00190787)

Undefined Tag error displays when spaces are used between commas in the Ladder Editor. Spaces between commas are no longer needed.

This anomaly first identified in version 20.04.02.

L5X file type allows spaces in Alias Tag name (Lgx00155383)

A tag name in an L5X file that contained spaces was imported and opened in a project. A space is not permitted in tag names and spaces cannot be entered in tag names in the Tag Editor.
This anomaly first identified in version 21.03.02.

Module Definition Change button with 1756-L71 (Lgx00167916)

When creating a new project with a 1756-L71 controller on EtherNet/IP, adding a 1756-CNB module, clicking the Change button under Module Definition, and then switching the input or output module, causes the Logix Designer application to lock and lose functionality.
This anomaly first identified in version 23.00.00.

Error changing slot positions for Point I/O module (Lgx00190599)

When adding a module to a Point I/O rack offline, the module is configured for slot 1 by default. When updating the module profile with the correct slot position and downloading the project to the controller, error 16#0205 occurs.
This anomaly first identified in version 28.02.01.

Follow these instructions to work around the issue:

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

Converting a generic Ethernet safety module to a later version (Lgx00195596)

If a project containing a generic Ethernet safety module is converted from one version of the Logix Designer application to a later version, changes to the safety configuration signature ID are not deleted. The connection to the safety device keeps running after the safety configuration signature is changed. If the generic Ethernet safety module is deleted and re-added to the project, then the safety configuration signature works as expected.
This anomaly first identified in version 24.00.00.

Failed to create module library, not registered (Lgx00203463)

Failed to create module library in a project that uses the 1768-L45 controller. The 1768-L45 controller is no longer a supported controller.
This anomaly first identified in version 20.04.02.

MCAO default value zero (Lgx00188302)

Axis attribute number 608, Zero Speed, had its default value changed from 0.00 to 1.0% Motor Rated. This change was made to address potential problems in vertical-load applications.
This anomaly first identified in version 28.00.00.

Out of range attribute and ACD file (Lgx00182216)

It is possible for users to push an axis attribute out of range. This is typically done when an SSV is in the controller, and the user saves or uploads the project. Save the file by exporting it as an L5K or L5X file. Upon import of the L5K file, the out of range attribute is corrected and a waning message opens. Upon import of an L5X file, the axis is deleted. This deletion of the L5X file is by design.
This anomaly first identified in version 28.00.00.

Missing rungs of logic (Lgx00196898)

When going online with the controller with an existing project, the uploaded copy of the project has missing rungs of logic. When the project is uploaded to a new project, the rungs of logic show in the project.
This anomaly first identified in version 28.02.00.

Not enough memory (Lgx00190656)

The Logix Designer application runs out of memory when uploading a large amount of tag data at one time.
This anomaly first identified in version 28.02.01.

To work around this issue:

Free up memory before saving. For example, close all routine windows, tag editors, and property pages.

Do not upload tag data values when saving.

Repeatedly load a few records at a time.

Vendor specific error code (Lgx00137897)

When the controller attempts to open a connection with a 3rd-party device on EtherNet/IP, it causes the device to return a vendor specific error (0x01, 0x320). This error code is interpreted incorrectly in the Logix Designer application Module Properties dialog box, Connection tab.
This anomaly first identified in version 20.01.02.

Allow Unicast Consumer Connections check box (Lgx00159102)

When offline in the Logix Designer application, the Allow Unicast Consumer Connections check box clears or resets itself when changing the Max Consumers value of a safety product tag for the 1756-L73S/A controller, firmware version 20.01.00. This does not occur when modifying a standard product tag.
This anomaly first identified in version 20.01.02.

Recent projects overridden (Lgx00197976)

When opening a project in Studio 5000 Logix Designer, all Studio 5000 Logix Designer and RSLogix 5000 recent projects are overridden by the most recent saved project.
This anomaly first identified in version 21.03.02.

Fatal error when saving RSNetWorx™ for EtherNetIP project (Lgx00192550)

Studio 5000 Logix Designer has a fatal error when saving a project using an RSNetWorx for EtherNet/IP file that is embedded in a 1756-EN2T in slot 0 and a 1756-L73S in slot 1/2 during the merging connection output step.
This anomaly first identified in version 27.00.01.

Studio 5000 Logix Emulate™ (Lgx00180272)

Studio 5000 Logix Emulate upload fails with Logix 5000 Services

An ACD file uploads successfully from AssetCentre but with the error message Can't open the specified RSLinx driver.
This anomaly first identified in version 24.01.00.

The Logix Designer application crashes after multiple cross references (Lgx00208989)

Logix Designer crashes with the error 0xc0000005 after selecting Go to Cross Reference and then closing the open window more than three times.

This anomaly first identified in version 21.03.

Error when running trend (Lgx00204911)

Running a trend generates a Communication request too large for network error.

This anomaly first identified in 28.01.

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.

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

• Use an MSG instruction as documented in AID 55301 and AID 55305.
• Reference the backing tags of the 1715 adapter :S tags and 1715 IO :I tags. This anomaly first identified in version 20.05.

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.

Functional changes in Studio 5000 Logix Designer version 30

Studio 5000 Logix Designer version 30.00 has the following changes in functionality since the last release.

Installation wizard

The entire installation has been automated for ease and convenience. The wizard is used to install Logix Designer and supporting applications on your system. After you select the software you want to install, the installer prepares the files needed for that version of software. After the files are prepared you choose from two installation methods:

• Install now - Installs the components available on your system using the recommended settings.
• Customize - You choose which components to install.

Tip: Keep the following considerations in mind before installing the Logix Designer application:

• Some antivirus software blocks or disrupts the Studio 5000 environment installation. If you experience difficulty, try disabling your antivirus software before installation.
• Make sure that you have Administrator privileges on the computer on which you want to install the Studio 5000 environment.

Changes to FactoryTalk Security permissions

• In this version of Logix Designer, a routine name and description can be modified when the Routine: Modify Properties permission is allowed. In earlier versions, both the Routine: Modify Properties and Routine: View Logic permissions had to be allowed before a routine name and description could be changed.

• Similarly, an Add-On Instruction name and description can be modified when the Add-On Instruction: Modify Properties permission is allowed. In earlier versions, both the Add-On Instruction: Modify Properties and Add-On Instruction: View Logic permissions had to be allowed a routine name and description could be changed.

• The permission to export routines and Add-On Instructions has been decoupled from the Project: Export permission. Users can export routines and Add-On Instructions only when the Add-On Instruction: Export and Routine: Export permissions are set to Allow. The project export fails if the Export permission is not allowed for all routines and Add-On Instructions.

Import/Export

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

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

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 you decide to migrate 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 you open 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.

If you uninstall the CodeMeter kit, which is installed with the FactoryTalk® Activation Manager, the Logix Designer application fails to uninstall. To restore the CodeMeter kit, uninstall the FactoryTalk Activation Manager and then reinstall it.

The Phase Manager and SequenceManager features are not available for CompactLogix 5380, CompactLogix 5480, and ControlLogix 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, you need to add an escape carriage.

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

• When previous versions of Logix Designer are installed after version 30, .NET 4.6 may cause installation to fail for these earlier versions of the Logix Designer application.
• When installed on 32-bit Windows operating systems, .NET 4.6 causes versions 23 and earlier of the Logix Designer application to fail on startup.

Follow one of these steps to work around the issue:

• Do not install version 30 of the Logix Designer application on a 32-bit Windows operating system on which you also run version 23 or earlier of the Logix Designer application.
• Contact Rockwell Automation Support for instructions on disabling the Logix Designer Start page on versions 23 or earlier. Disabling the Start page allows the Logix Designer application to start and run.

When you use 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 (AOI) included in the project. In the same way, when you import an AOI from a project created in a release earlier than version 29.00, the signature breaks for that AOI. You must un-seal and then re-seal each AOI to get a new signature.

Kinetix® Encoder Emulator RPI must match the Motion Task update rate

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

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.

If you use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you need an updated motion database to work with versions 18 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 or later, any Custom Motor currently in a motion database file at revision 5 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.

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

     Setup.exe /Q /IAcceptAllLicenseTerms

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

    Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /InstallDrive=D:

Application Note First Identified Studio 5000 Logix Designer Version 24.00

When using Logix Designer application v24.00 and later to open a prior version .ACD file containing a module referenced by an instruction and also a program-scoped tag of the same name as the module, an “Invalid data type” error occurs during verification.

To work around this error, rename either the module or the tag and ensure all instructions correctly reference the module.