Release Notes

( 9324-RLDx ) Studio 5000 programming software. All you need for discrete, process, batch, motion, safety etc.
Version 30.02.02 (released 3/2021)

Catalog Number Studio 5000 Logix Designer 

These release notes describe version information for Studio 5000 Logix Designer, version 30.02.02 (released 3/2021).

Requirements

This release has the following requirements.

System requirements for Logix Designer v30.02.02

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

Tip:
Logix Designer can be installed on a personal computer that meets the operating system minimum requirements, but may not meet performance expectations when used in a production system.
Hardware Requirements
Software Requirements

 

Important:
Keep these operating system considerations in mind:
  • Universal C Runtime (CRT) is a Windows operating system component that enables core functionality on the Windows operating system. It was introduced in Windows 10 and distributed to most computers running earlier supported operating systems. On computers that have been kept up-to-date, this component is present.
When installing the Logix Designer application on computers that have not been updated, prompts show to install Universal C Runtime or to update the computer to at least the Microsoft April 2014 update roll-up.
  • While the Windows 8.1 operating system runs on many touch-enabled devices, various features of the Logix Designer application may not be touch-enabled. Most functions are expected to work with touch, but the software has only been tested with a keyboard and mouse.
  • Logix Designer was tested with UAC set to the most restrictive level (Always notify). This version of the Logix Designer application is also expected to operate correctly when UAC is configured for any less restrictive setting.
  
  
Important:
When installing version 30.02 of Logix Designer application, Microsoft .NET Framework 4.6 is installed automatically. However, when installed on 32-bit Windows operating systems, .NET Framework 4.6 causes versions 23.00 and earlier of the Logix Designer application to fail on startup. Also, when previous versions of Logix Designer are installed after version 30.00, .NET Framework 4.6 may cause these earlier versions of the Logix Designer application installation to fail. Refer to the Application Notes section for more information on this issue.

 

Firmware requirements
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 http://compatibility.rockwellautomation.com/Pages/MultiProductDownload.aspx?crumb=112).
Tip:
Most modules use Flash-ROM for the storage of firmware. If a module requires a firmware change, use the ControlFLASH™ tool to perform the update to the Flash-ROM. It is contained in the downloaded image or on a DVD-ROM shipped with the Logix Designer application. Also, automatically update the firmware as part of the project download.
For additional information and assistance in performing a Flash-ROM update, review the ControlFLASH Firmware Upgrade Software User Manual, publication 1756-UM105 http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um105_-en-e.pdf.

Features

This release includes the following system features.

System features for Logix Designer v30.02.02

Logix Designer application version v30.02 has no new or enhanced features or new supported hardware.

New devices supported

The following table list new hardware supported in this release.

Catalog number
Description
Vendor
280E-F23Z-25D
ArmorStart, 3.2A-16.0A, 24V DC, Motor Starter, Direct On-Line (DOL)
Rockwell Automation
281E-F23Z-25D
ArmorStart, 3.2A-16.0A, 24V DC, Motor Starter, Reversing
Rockwell Automation
281E-F12S-10A
ArmorStart Safety, 0.24A-1.2, 24V DC, Motor Starter, Reversing
Rockwell Automation
281E-F12S-10B
ArmorStart Safety, 0.5A-2.5A, 24V DC, Motor Starter, Reversing
Rockwell Automation
281E-F12S-10C
ArmorStart Safety, 1.1A-5.5A, 24V DC, Motor Starter, Reversing
Rockwell Automation
281E-F23S-25D
ArmorStart Safety, 3.2A-16.0A, 24V DC, Motor Starter, Reversing
Rockwell Automation
284E-FVD1P4Z
ArmorStart, 0.5HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD2P3Z
ArmorStart, 1HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD4P0Z
ArmorStart, 2HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD6P0Z
ArmorStart, 3HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD7P6Z
ArmorStart, 5HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD2P3S
ArmorStart Safety, 1HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD4P0S
ArmorStart Safety, 2HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD6P0S
ArmorStart Safety, 3HP, 480V AC, Motor Starter, VFD
Rockwell Automation
284E-FVD7P6S
ArmorStart Safety, 5HP, 480V AC, Motor Starter, VFD
Rockwell Automation
1444-DYN04-01RA
Dynamix Condition Monitor, 2-Port
Rockwell Automation
1732E-8IOLM12R
8 Channel IO-Link Master
Rockwell Automation
1732ES-IB8XOB8
8 Point 24V DC Sink Safety Input, 8 Point 24V DC Source Safety Output
Rockwell Automation
1732ES-IB8XOBV4
8 Point 24V DC Sink Safety Input, 8 Point 24V DC Bipolar (4 sink/source pairs) Safety Output
Rockwell Automation
1732ES-IB16
16 Point 24V DC Sink Safety Input
Rockwell Automation
1756-RMS-SC
8-Channel Isolated RMS Input
Spectrum Controls, Inc.
1769-L37ERMO
CompactLogix 5370 controller
Rockwell Automation
1769-L37ERMOS
CompactLogix 5370 controller
Rockwell Automation
1783-IMS28GN
Stratix 5410 28 Port Switch, 1 Gigabit Uplinks, AC/DC Modular Power Supply, Rack Mount
Rockwell Automation
1783-IMS28GR
Stratix 5410 28 Port Layer 3 Switch, 1 Gigabit Uplinks, AC/DC Modular Power Supply , Rack Mount
Rockwell Automation
2198-ABQE
Encoder Output Emulator, 2-port
Rockwell Automation
2PCA-7844-B101
MMCU EtherNet/IP Adapter
Laird
5069-IA16
16 Point 79V-264V AC Input
Rockwell Automation
5069-OA16
16 Point 85V-264V AC Output
Rockwell Automation
5069-OB8
8 Point 24V DC Output, Source
Rockwell Automation
5069-OW16
16 Point AC/DC Relay Output, N.O
Rockwell Automation
5069-L3100ERM
CompactLogix 5380 controller
Rockwell Automation
5069-L350ERM
CompactLogix 5380 controller
Rockwell Automation
5069-L380ERM
CompactLogix 5380 controller
Rockwell Automation
5069-L46ERMW
CompactLogix 5480 controller
Rockwell Automation
AX8
ThermoVision Camera
FLIR Systems
A3XX                      
ThermoVision Camera
FLIR Systems
ACT350 EtherNet/IP
Weight Transmitter
Mettler-Toledo
ACT350-2P EtherNet/IP
Weight Transmitter
Mettler-Toledo
Memograph_M_RSG45
EtherNet/IP Data Manager
Endress+Hauser
STB3574 EtherNet/IP
Barcode Scanner
Zebra Technologies
Electronic Data Sheets

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



Corrected Anomalies in This Release

This release corrects the following anomalies.

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.

  

Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.

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

Module Info B tab empty (1815893)

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

Consider these work arounds:

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.

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

The Phase Manager and the Equipment Sequence Manager sometimes show a different state of phase when the controller is switched from run to program mode. (Lgx00183769)

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

When controller data and logic memory are low, Logix Designer application sometimes reports that it cannot connect to the controller. (Lgx00179908)

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

Studio 5000 Logix Designer v29.00

When you create a description for a parameter in an Add-On Instruction and then change that description in one instance of the AOI in the Tag Editor, no modification of the description appears for that instance in Parameters and Local Tags when the scope is set to Add-On. (Lgx00185356)

  

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:

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:

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:

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:

Important:
If you retain test edits and the test edits were the cause of the switchover, the test edits can cause the same fault on the redundant controller.


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:

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.

  

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:

External component has thrown an exception."

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:

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:

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.

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 (1090045)

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

This anomaly first identified in version 12.00.
  

Unable to import L5K project containing 1794-IE8HB, 1794-IF8IH, 1794-OE8HB and 1794-OF8IH (986170, Lgx00233674)

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.

  

Command and actual position data not zeroed on axis inhibit (Lgx00230166)

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.

  
Pressing Alt + Tab with the Scope menu open in the Tag Editor caused the Logix Designer application to crash (910996, Lgx00218037, Lgx00217937)

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.

  
FBD JSR instruction rearranged input and return parameters (910966, Lgx00226151, Lgx00225636)

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

This anomaly first identified in version 26.00.

  
Public parameter imports as a local tag (910972, Lgx00231568, Lgx00231638, Lgx00231000)

When importing and exporting programs or routines with Public program parameters between projects, the program or routine causes the parameter to appear undefined. 

This anomaly first identified in version 24.00

  
Add-On Instruction tag members copied incorrectly (Lgx00217794)

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 using indirect addressing to a Boolean tag within an Add-On Instruction data type (Lgx00221328)

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.

  
Invalid Add-On Instruction after upload - multi-dimensioned Add-On Instruction parameter tag (Lgx00224252)

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.

  
BOOL tags did not retain value (Lgx00226143)

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.

  
Time set was wrong by one hour (Lgx00227344)

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.

  
Projects with SMC EX250-SEN1 fail to convert (Lgx00225459)

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.

  
Incorrect verification of structured text routine (Lgx00222019)

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.

  
Polling for source protection licenses caused source protection routines to close (Lgx00220755)

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.

  
Unexpected tag error with GuardLogix controller project and no Logix Designer application GuardLogix activation (Lgx00225577)

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.

  
Fatal error converting v20 project (Lgx00200539)

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.




  
Fault with LBL and JMP on same rung (Lgx00212472)

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.




  
Equipment Sequence tag with a name that contains less than four characters can prevent upload of a project (Lgx00217744, Lgx00218113)

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.




  
Export Add-On Instruction fails to parse on import (Lgx00200761)

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.



  
Import fails on 1756-DHRIO module (Lgx00200538)

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 slows the performance of the Logix Designer application for Compact GuardLogix 5380, CompactLogix 5380, ControlLogix 5580, and GuardLogix 5580 controllers (Lgx00219712, Lgx00207749)

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.

Safety signature takes a long time to upload and save (Lgx00208884)

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.

Update Studio 5000 Logix Designer to support MSXML for DfS compliance (Lgx00193996)

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.


  
Instructions in routines protected with License Based Source Protect give wrong results (Lgx00219002, Lgx00219003)

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.

Cannot download encrypted Add-On Instruction without license after locking online (Lgx00210520)

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.

Trend fails when pen names exceed 474characters (Lgx00204911)

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.

SSV/GSSV causes compiler error and prevents download (Lgx00207344)

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:

Changing an Add-On Instruction alias parameter to a base tag can result in unexpected tag values (Lgx00214079, Lgx00217794)

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:

Adding an EDS Add-On Profile causes fatal error (Lgx00207018)

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.



  
Installing v30.00 or the v30.00 AOP Bundle and adding ENBT, ENT2T, or EN2TR modules causes fatal error (Lgx00210565)

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.

Cross Reference function causes fatal error (Lgx00209066)

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

This anomaly first identified in version 20.04.

Watchdog fault for testing does not clear (Lgx00210766)

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.

Working on a routine in Watch view may cause the application to stop working (Lgx00206952)

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.

Data integrity with CompactLogix 5370 controllers with large I/O sizes (Lgx00206881)

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.

Axes referencing InOut parameters (Lgx00207163)

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.

Selecting Fit to Window in the SFC editor causes fatal error (Lgx00206863)

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.

Reset counter button fails to work (Lgx00215642)

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.

Application sometimes fails when selecting About > Support (Lgx00190760, Lgx00190865)

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.

  
Revision will be 2.001 for 2715 HMI PanelView 5500 HMI (Lgx00191064)

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.

Changing data context for Add-On Instructions did not change description and properties context (Lgx00185356, Lgx00185438, Lgx00185439, Lgx00186196)

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.

Add-On Instruction with user-defined data type received compiler error  (Lgx00211154)

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.

View Terminal profile must include Major Rev 3 (Lgx00191064)

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.

Watch view updated incorrectly and stopped performing when tag cut and pasted (Lgx00206952)

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.

Compiler error when finalizing online edits on ControlLogix 5580, CompactLogix 5480, and CompactLogix 5380 controllers (Lgx00223309)

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 using indirect addressing to a Boolean tag within an Add-On Instruction data type (Lgx00221329)

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.

  
Launching with Ctrl + Shift did not reset Controller Organizer (Lgx199167)

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.

Tag error icon still displayed after deletion of invalid icon (Lgx00228152)

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 performing after multiple cross reference tasks (Lgx00208988)

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.

Upload failed on Equipment Sequence Diagram (Lgx00218115)

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.

About box hyperlink failed (Lgx00190760, Lgx00190865)

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.

Watchdog fault will not clear from fault handler routine (Lgx00212471)

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.

Scanning licenses closed source protection routines (Lgx00220754)

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.

Routines with License Based Source Protection produced inaccurate results (Lgx00219001)

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.

Could not download encrypted Add-On Instruction without license after locking online (Lgx00210519)

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.

FactoryTalk Linx support issue (Lgx00203589)

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.

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.

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.

  

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.

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.

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

  

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.

  

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.

  

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.

  

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

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.

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.

  

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.

Inconsistent forcing behavior with L5X file (Lgx00207500)
When the controller is offline, I/O Forcing works inconsistently in the Tag Editor and in routine editors when working with L5X files. This inconsistency is only observable when the controller is offline. After downloading the project to the controller, the inconsistent behavior is resolved and applying and removing forces works as expected. The risk is possibly downloading a project that appears to not have I/O Forcing installed when it actually does.

Some possible scenarios include:
Tag forcing is observable in Local tags in the Data Editor. I/O forces are installed for Local routines. However, no I/O Forcing appears to be installed. The I/O Forces status is Disabled. The Logic > I/O Forcing > Remove All I/O Forces command is not selectable.

When I/O forces are installed for Local tags, apply a force to a Local tag and then remove the force from the Local tag. Observe that forces are removed from all I/O tags in the routine. Close the routine and reopen it. Observe forcing is restored on the Local tags.

With I/O Forcing installed for Local tags, remove the force from a Local tag and then reapply the force to the Local tag. Observe that forcing appears on the Local tag, but it appears removed from another Local tag. Close the routine and then reopen it to restore the proper forcing on the Local tags.
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.

Important:
If retaining test edits and the test edits were the cause of the switchover, the test edits can cause the same fault on the redundant controller.


  

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.

  

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.

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.

Fatal error when converting a project to a newer major revision (1476922)]]]
A fatal error sometimes occurs when converting a project to a newer major revision where issues exist in the ChangeLog.
To work around this issue, export from the older project to a .L5K or .L5X file and import the project to a newer major revision to avoid the fatal error.
This anomaly first identified in version 16.00.
  

Error when attempting to run a trend (1435208)

The Logix Designer application is unable to run a trend in v29 or earlier after switching communication software from RSLinx Classic to FactoryTalk Linx in another instance of the Logix Designer application v31 and later on the same workstation.

Once a trend is run in the Logix Designer application v31 and later, using FactoryTalk Linx as the communication software, you will receive this error message if you then attempt to run a trend in the Logix Designer application v29 or earlier on the same workstation:

Error: <trend name> - : Can’t open the specified RSLinx driver.

For more information, refer to the technical note BF23206.

This anomaly first identified in version 20.00.

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:

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.

  

Functional Changes

This release has the following functional changes from the previous release.

Functional changes for Logix Designer v30.02.02

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

Installation wizard

The entire installation was automated for ease and convenience. The wizard is used to install Logix Designer and supporting applications. After selecting the software to install, the installer prepares the files needed for that version of software. After the files are prepared, choose from two installation methods:

Tip:
Keep these considerations in mind before installing the Logix Designer application:
  • Some antivirus software blocks or disrupts the Studio 5000 environment installation. If experiencing difficulty, try disabling the antivirus software before installation.
  • Make sure to have Administrator privileges on the computer on which installing the Studio 5000 environment.
Import/Export

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

Release Version
Import/Export Version
30.xx
2.21
29.xx
2.20
28.xx
2.19
27.xx
2.18
26.xx
2.17
24.xx
2.15
23.xx
2.14
21.xx
2.12
20.xx
2.11
19.xx
2.10
18.xx
2.9
17.xx
2.8
16.xx
2.7
15.xx
2.6
14.xx
2.5
13.xx
2.4
12.xx
2.3
11.xx
2.2
10.xx
2.1
9.00
2.0
5.02
1.2
2.xx, 6.xx, 7.xx, 8.xx
1.1
1.21, 1.23
1.0
1.10, 1.11
0.4

Application Notes

This release has the following application notes.

Application notes for Logix Designer v30.02.02

These are the application notes for Logix Designer version 30.02.

Supported Logix Controllers

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

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

The table provides a breakdown of the various Logix 5000 controllers and the initial or minimum version of Logix Designer application that is required to support the controller.

 Controller Catalog Number
Minimum Major Software Version
ControlLogix 1756-L71 Series B
20.00
ControlLogix 1756-L71S Series B
20.01
ControlLogix 1756-L72 Series A
19.00
ControlLogix 1756-L72 Series B
20.00
GuardLogix 1756-L72S Series B
20.00
ControlLogix 1756-L73 Series A
18.00
ControlLogix 1756-L73 Series B
20.00
ControlLogix 1756-L73XT Series B
20.00
GuardLogix 1756-L73S Series B
20.00
GuardLogix 1756-L73SXT Series B
20.00
ControlLogix 1756-L74 Series A
19.00
ControlLogix 1756-L74 Series B
20.00
ControlLogix 1756-L75 Series A
18.00
ControlLogix 1756-L75 Series B
20.00
ControlLogix 1756-L81E Series B
29.00
ControlLogix 1756-L82E Series B
29.00
ControlLogix 1756-L83E Series B
28.00
ControlLogix 1756-L84E Series B
29.00
ControlLogix 1756-L85E Series B
28.00
CompactLogix 1769-L16ER-BB1B Series A
20.00
CompactLogix 1769-L16ER-BB1B Series B
20.00
CompactLogix 1769-L18ER-BB1B Series A
20.00
CompactLogix 1769-L18ER-BB1B Series B
20.00
CompactLogix 1769-L18ERM-BB1B Series A
20.00
CompactLogix 1769-L18ERM-BB1B Series B
20.00
CompactLogix 1769-L19ER-BB1B
28.00
CompactLogix 1769-L24ER-QB1B
20.00
CompactLogix 1769-L24ER-QBFC1B
20.00
CompactLogix 1769-L27ERM-QBFC1B
20.00
CompactLogix 1769-L30ER
20.00
CompactLogix 1769-L30ER-NSE
20.00
CompactLogix 1769-L30ERM
20.00
CompactLogix 1769-L33ER
20.00
CompactLogix 1769-L33ERM
20.00
CompactLogix GuardLogix 1769-L30ERMS
28.00
CompactLogix GuardLogix 1769-L33ERMS
28.00
CompactLogix GuardLogix 1769-L36ERMS
28.00
CompactLogix 1769-L36ERM
20.00
CompactLogix 5069-L306ER
29.00
CompactLogix 5069-L306ERM
29.00
CompactLogix 5069-L310ER
29.00
CompactLogix 5069-L310ERM
29.00
CompactLogix 5069-L310ERM-NSE
29.00
CompactLogix 5069-L3100ERM
30.00
CompactLogix 5069-L320ER
28.00
CompactLogix 5069-L320ERM
29.00
CompactLogix 5069-L330ER
29.00
CompactLogix 5069-L330ERM
29.00
CompactLogix 5069-L340ER
29.00
CompactLogix 5069-L340ERM
28.00
CompactLogix 5069-L350ERM
30.00
CompactLogix 5069-L37ERMO
30.00
CompactLogix 5069-L380ERM
30.00
CompactLogix 5069-L46ERMW
30.00
Microsoft .NET Framework 4.6 may cause failure in earlier versions of the Logix Designer application

When installing version 30.02 of Logix Designer, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:

Follow one of these steps to work around the issue:
VeriSign Universal Root Certification Authority certificate

If the VeriSign Universal Root Certification Authority certificate does not exist on the local computer, the certificate is installed while installing Rockwell Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.

Microsoft Root Certificate Authority 2011 certificate

If the Microsoft Root Certificate Authority 2011 certificate does not exist on the local computer, the certificate is installed while installing Rockwell Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.

Unattended or silent install

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

Command-line parameters

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

 

Parameter
Description
/?
Displays the usage options for installation parameters.
/Q
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended if you are deploying the software installation using an IT tool or script, and do not expect to see any error or restart messages. When using this parameter, your IT tool or script should check the error codes, and respond as needed. For example, if the installation returns error code 1641, then the IT tool or script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
/QS
Unattended Install, install runs in a quiet simple mode and shows progress through the UI, it does not accept any input but still shows error or restart messages.
When using this parameter, you will not have to check the error codes, and the installation will stop and display a prompt if there are error or restart messages. For example, if an immediate restart is required to complete the install, a restart message will be displayed for you to confirm the restart. Installation resumes automatically from the point of interruption after restart.
This parameter is required if /Q is not specified.
/IAcceptAllLicenseTerms
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
/AutoRestart
Automatically restarts the computer after the installation is complete. Used when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used, silent install (/Q) will return either error code 1641 or 3010 if a restart is required, and unattended install (/QS) will result in a confirmation prompt that must be agreed to before the installation is completed.
/SetupLanguage="value"
Specifies which language will be displayed during install process.
The value must be the one of the following:
  • ENU
  • CHS
  • DEU
  • ESP
  • FRA
  • ITA
  • JPN
  • KOR
  • PTB
This parameter is optional. If this parameter is not used, the default language is the current user or operating system user interface language.
/Record
Records the installation options chosen to a recording file.
This parameter is optional.
/Playback
Plays back a recording file to specify the installation options.
This parameter is optional.
/Uninstall
Uninstalls the product.
The Logix Designer application does not support the /Uninstall parameter.
/Product="value"
Specifies which sub-products will be installed.
Only required if sub-products are included with the install package.
If the software does not include sub-products, this parameter is not available.
/ProductLanguage="value"
Specifies the language version of the software being installed.
The value must be the one of the following:
  • ENU
  • CHS
  • DEU
  • ESP
  • FRA
  • ITA
  • JPN
  • KOR
  • PTB
This parameter is optional. If this parameter is not used, the default language is the same as the setup language.
If the software does not support multiple languages, this parameter is not available.
/InstallLocation="value"
Or
/InstallDrive="value"
Specifies the install location or install drive respectively.
This parameter is optional. If this parameter is not used, the default install location is "C:\Program Files (x86)\Rockwell Software".
Some software restricts the installer to change only the drive the software is installed on. Use /? to determine which parameter is supported.
/SerialNumber="value"
Specifies the serial number of the software being installed. This is used to activate the software during installation.
This parameter is optional. If it is not specified, the software must be activated manually after installation if activation is required.
Some software does not require activation. If activation is not required, this parameter is not available.
/ProductKey="value"
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified, the software must be activated manually after installation if activation is required.
Some software does not require activation. If activation is not required, this parameter is not available.
/Version="value"
Specifies the version of the software to activate that corresponds to the product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified, the installer will use the most recent product version available.
Some software does not require activation. If activation is not required, this parameter is not available.
Examples

The following examples show how to use the installation commands.

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

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

Error Code
Value
Description
ERROR_SUCCESS
0
The installation completed successfully.
ERROR_INVALID_PARAMETER
87
One of the parameters was invalid.
ERROR_INSTALL_USEREXIT
1602
The installation was cancelled by the user.
ERROR_INSTALL_FAILURE
1603
A fatal error occurred during installation.
ERROR_BAD_CONFIGURATION
1610
The configuration data for this product is corrupt. Contact your support personnel.
ERROR_SUCCESS_REBOOT_INITIATED
1641
The installer has initiated a restart. After restart, installation will continue.
ERROR_SUCCESS_REBOOT_REQUIRED
3010
A restart is required to complete the installation. After restart, the product is successfully installed.
ERROR_REBOOT_PENDING
3012
Restart of the computer is currently pending. The computer must be restarted before installation can continue.
Versions 18.00 and later require updates to Custom Motion Database

If using a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12.00 through 17.00, update motion database to work with versions 18.00 or later. The table lists the motion database revisions that are used with these application versions.

Version of Application
Motion Database Revision
30.00 / 30.02
11.6.0 [ Motion.mdb format ]
29.00
11.5.0 [ Motion.mdb format ]
28.00
10.5.0 [ Motion.mdb format ]
27.00
10.3.0 [ Motion.mdb format ]
26.01
10.3.0 [ Motion.mdb format ]
24.00
9.24.0 [ Motion.mdb format ]
23.00
9.22.0 [ Motion.mdb format ]
21.03
9.15.0 [ Motion.mdb format ]
21.00
9.8.0 [ Motion.mdb format ]
20.01
8.12.0 [ Motion.mdb format ]
20.00
8.9.0 [ Motion.mdb format ]
19.01 / 19.00
7.5.0 [ Motion.mdb format ]
18.02 / 18.01 / 18.00
6.9.0 [ Motion.mdb format ]
17.01 / 17.00
5.3.0 [ *Motion.md format ]
16.04 / 16.03 / 16.00
4.2.0 [ *Motion.md format ]
15.03 / 15.02/ 15.01 / 15.00
3.24.0 [ *Motion.md format ]
14.01 / 14.00
3.12.0 [ *Motion.md format ]
13.04 / 13.03 / 13.02 / 13.01 / 13.00
3.12.0 [ *Motion.md format ]
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 12.01 / 12.00
3.3.0 [ *Motion.md format ]

* Before using a Custom Motor in version 18.00 or later, convert any Custom Motor currently in a motion database file at revision 5.00 or earlier (Motion.db format) to the newer Motion.mdb format.

To initiate the process of updating the database, 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.

  
 


Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2024 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.