System requirements for Logix Designer version 27.00.00 (CPR 9 SR 7.4)

To use the Logix Designer application effectively, your personal computer must meet the following hardware and software requirements.

Hardware Requirements

The personal computer must meet these minimum requirements. Using a computer meeting or exceeding the recommended characteristics will improve performance.

Software Requirements

Operating system and service pack compatibility:

• This version of the Logix Designer application has been tested on the following operating systems:
  • Microsoft® Windows® 7 Professional (64-bit) with Service Pack 1
  • Microsoft 7 Home Premium (32-bit) with Service Pack 1
  • Microsoft Windows Server 2008 R2 Standard Edition with Service Pack 1
  • Microsoft Windows 8 Professional (64-bit)
  • Microsoft Windows 8.1 Professional (64-bit)
  • Microsoft Windows Server 2012 Standard Edition (server version of Windows 8)

• 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

For operating systems that support User Account Control (UAC), this version of the Logix Designer application was tested with UAC set to the most restrictive level (Always notify for Windows 7). This version of the Logix Designer application is also expected to operate correctly when UAC is configured for any less restrictive setting.

Running the Logix Designer application in conjunction with Fast-User Switching, in Safe mode, or via Remote Desktop is not supported.

Additional Software Product Considerations

• FactoryTalk Services Platform is required to run this version of the Logix Designer application, as it performs some security functions in the Logix Designer application.
• RSLinx Classic communication software is required as part of the installation of the Logix Designer application, as it handles online communication with controllers.
• RSLinx Classic v3.74.00 is a component aligned to Logix Designer v27.00. RSLinx Classic v3.74.00 (CPR9 Service Release 7.4) has been tested, and is compatible, with the following products:
  • FactoryTalk Services Platform v2.74.00
  • RSLinx Enterprise v5.73.00
  • RSNetWorx v24.05.00
  • FactoryTalk Activation Manager v3.62.11
• RSLinx Classic v3.74.00, Logix Designer application v27.00, and device profiles that ship with the Logix Designer application v27.00 are not compatible with:
  • RSNetWorx v11.00.00 or earlier
  • DeviceNet Tag Generator v11.0.20.0

-1. 1. RSNetWorx and the DeviceNet Tag Generator must be upgraded prior to installing these products.

• FactoryTalk View SE software and RSLinx Enterprise communication software are not required to install the Logix Designer application; however, these products are required in order to fully use the alarm capabilities introduced with version 16.
• Microsoft .NET Framework 4 Language Pack is required to show the localized resources for the components developed by .NET for supported languages of the Logix Designer application v21 and later. You need to download and install Microsoft .NET Framework 4 Language Pack or later on the computer in which the Logix Designer application local language is installed.
• 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.

Revision information

Supported Logix Controllers

While the Logix Designer application 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 application 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 Logix Designer application.

Additionally, if you open a project that is configured for a controller that is no longer supported and the older version of RSLogix 5000 software is not installed, version 13 and later of the application will provide an appropriate warning and will automatically provide the option to convert the project to one of the controllers supported by the release.

The following table provides a breakdown of the various Logix5000 controllers and the initial or minimum version of RSLogix 5000 software that is required and, in case the controller is no longer supported, the last or maximum version of RSLogix 5000 software that provided support for the controller.

¹ Excludes GuardLogix for RSLogix 5000 software version 14.

² Excludes RSLogix 5000 software version 15.

Firmware

Most of the modules supported by the Logix Designer application use Flash-ROM for the storage of firmware. If you possess a module that requires a firmware change, the ControlFLASH software tool can be used to perform an update to this Flash-ROM. This software tool and 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™. Starting with version 10.00.00 of the application, you can access the ControlFLASH tool from within the application (from the Tools menu), or you can automatically update your firmware as part of the project download process.

For additional information and assistance in performing a Flash-ROM update, review the ControlFLASH Firmware Upgrade Software User Manual , publication 1756-UM105 .

In addition, Rockwell Automation Services & Support has created a website from which you can download firmware images for Logix products. Go to http://www.rockwellautomation.com/rockwellautomation/support/firmware/overview.page? for a matrix detailing the revisions of firmware that were released with each of the versions of the application, and to download the ControlFLASH firmware kits and release notes. Note that you will need your Logix Designer application serial number to complete the download.

Firmware for ControlLogix Redundancy

The firmware associated with this standard release version of the Logix Designer application does not support redundancy. RSLogix 5000 software versions 8, 11, 13, 15, 16, 19, and 20 support redundancy, but a separate firmware revision for the hardware in the local chassis is required. The redundancy firmware revisions are released later than the standard revisions are released and are available for download via the same methods as for standard firmware. Go to http://www.rockwellautomation.com/rockwellautomation/support/firmware/overview.page? for a matrix detailing the revisions of redundancy firmware that were released for each of the versions of RSLogix 5000 software, and to download the ControlFLASH firmware kits and release notes. Note that you will need your RSLogix 5000 serial number to complete the download.

Separately Installed I/O Configuration Profiles

With version 13 and later of the application, new I/O configuration profiles can be delivered independently from the application's release. These profiles can be obtained independently and installed on a personal computer with the application to extend the I/O configuration support beyond the capabilities initially supported when the application was released. This capability was initially limited to a single I/O platform, but with each new release, new I/O platforms are added. If you are using one of the supported platforms and the configuration profile for a specific product was not included with the application, check with the module or device vendor to determine if one is available. Additionally, I/O configuration profiles for modules or devices fromRockwell Automation are generally provided with the application. However, at times, a module or device configuration profile may not be completed in time to make a release. In these instances, the I/O configuration profiles will be made available via the Rockwell Automation Services & Support website http://www.rockwellautomation.com/rockwellautomation/support/firmware/overview.page? . The following table provides a listing of versions of the application and their respective ability to support the field addition of I/O configuration profiles.

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. These EDS files are also available separately by contacting Rockwell Automation Services & Support (phone +1 440-646-3434), or using the Internet (http://www.rockwellautomation.com/resources/eds/ ). You can install them by using the EDS Hardware Installation Tool, located in the Rockwell Software>RSLinx>Tools folder in the Windows Start Menu.

System features in Logix Designer version 27.00.00

Logix Designer application version v27.00.00 has these new and enhanced features and new supported hardware.

HMI Button Control instructions

Use HMI Button Control (HMIBC) instructions with a PanelView 5500 Human Machine Interface (HMI) device to allow operators to perform machine control operations, such as jogging a motor. HMIBC instructions also provide built-in communication diagnostics that permit the instruction to automatically reset if communication from the controlling HMI is unavailable. An HMIBC instruction becomes active and enables its output when a PanelView 5500 HMI device starts a button control operation associated with the instruction’s instance tag.

Support for Application Code Manager

Application Code Manager (ACM) is an engineering design tool that facilitates faster application development. When you generate Logix Designer application projects, you can leverage the ACM library to speed the process. You can select the desired library objects needed and provide project-specific configuration data without a need to fully understand all the objects and their dependencies or relationships. Once all the library objects have been selected and configuration is complete you can perform a Logix project bulk build.

All Library Content is configured using the ACM Library Designer (Plug-In) hosted in the Logix Designer application. Once the library object is configured, you can publish it into the ACM database using the Library Object Manager in ACM. All library objects as well as Project configuration is stored in this database. The ACM Library Designer is supported only in Logix Designer version 27 or later.

Enhancements in this release

The following enhancements to existing features have been made in this release of the Logix Designer application:

• Added the Ctrl + Home and Ctrl + End navigation shortcuts in the Sequential Function Chart and Function Block Diagram editors. (x142172)
• Added the ability to copy and paste table content from spreadsheet applications such as Microsoft Excel into the Data Type editor. (x146360)
• In the Relay Ladder Logic, Function Block Diagram, Sequential Function Chart, and Structured Text editors, removed the green color indicator from power rails when a routine’s parent task or program is inhibited, or if the routine is never called. (x139717)
• The expression entry dialog box is now movable in the Ladder editor for CPT, CMP, FAL, and FSC instructions. In previous releases the dialog box could be resized but not moved. (x113849)

Changes in this release

The following items explain changes that have been made in this or earlier releases in the way that the Logix Designer application works, compared to earlier releases.

Controller Memory Changes

This revision of Logix5000 controllers may require more memory than earlier revisions. To estimate additional memory requirements for your application, you can either use the memory estimation tool provided with Logix Designer application or the tables provided in these release notes.

• Before upgrading to this revision, check the amount of unused memory that you have in the controller.
• For additional information about controller memory issues refer to the Knowledgebase at: http://www.rockwellautomation.com/support/ .

To use the memory estimation tool to estimate the amount of controller memory your project requires for I/O, Data, and Logic, convert the project to the controller revision desired and then use the Estimate tool available on the Memory tab of the Controller Properties dialog box.

If you do not have the desired version of Logix Designer application, use the following table to estimate the additional memory that your project may require.

Behavior changes in ControlLogix 5570 controllers

This release includes the following behavior changes for ControlLogix 5570 controllers.

• REAL operands are not allowed in array subscripts.
• Ladder logic does not allow bitwise arithmetic (for example, AND) for REAL operands.
• The nesting or invocation limit for Add-on instructions (AOIs) and Jump to Subroutine (JSR) instructions is set at 25.
  • For AOIs, the limit for InOut parameters is 40.
  • For JSRs, the limit for In parameters and Out parameters is 40.
• An MCR instruction must be the last instruction in a rung.
• A Math Status Flag Consumer (XIC or XIO instructions with S:V, S:C, S:N, or S:Z as operands) must be preceded by at least one Math Status Flag Producer from the same rung.
• Mat Status Flags are not supported in non-RLL languages.
• All rungs must be verified for Routine-level accepts.

Import/Export Changes

Import/Export Formats – Logix Designer application provides the following five different Import/Export file formats:

• Full project exported to an ASCII text file (.L5K)
• Full project exported to an Extensible Markup Language (XML) formatted file (.L5X)
• Tag definitions and program documentation exported to ASCII text files in a Comma Separated Value (.CSV) format

• Tag definitions and program documentation exported to ASCII text files in a Tab Separated Value (.TXT) format
• Partial project exported to an Extensible Markup Language (XML) formatted file (.L5X)

Each of these formats is documented in Logix5000 Controllers Import/Export Reference Manual, publication 1756-RM084, which also describes modifications that can be made for backward compatibility of export format files.

Import/Export Major and Minor Revision – Beginning with the version 9.00 release, the Import/Export version number is interpreted as a Major Revision and a Minor Revision (major.minor). Each version of Logix Designer application exports *.L5K files with specific IE Version numbers. Logix Designer application imports any *.L5K file with the same Major Revision number and the same or lower Minor Revision number. The Major Revision is incremented when there is a significant change that affects compatibility with earlier versions. The Minor Revision is incremented whenever there is a change in the file format (for example, a new module, an attribute is added, or the set of options for an attribute is changed). Generally, the Minor Revision is incremented for each release.

The Import/Export version number for this version of Logix Designer application has been changed. If you export files (*.L5K) that were created in versions of RSLogix 5000 software with an Import/Export version number less than 2, and you attempt to import them in the latest version of the application, an error is generated. The error message is "Failed to open file *.L5K. Syntax error found while scanning the Import file." To work around the anomaly, edit the *.L5K file and change the line IE_VER := x.x;, where x.x may be 1.0, 1.1, or 1.2 to IE_VER := 2.11;, save the file and retry the import.

Import or Paste Error Messages – When attempting to import or paste between versions, if the IE version is invalid, an error message is displayed in the results window. If the major or minor revision number is larger than accepted, the message "Error Line xxx: Invalid IE Version number. Cannot import/paste into older version of RSLogix 5000" is displayed. If the major revision number is smaller than accepted, the message "Error Line xxx: Invalid IE Version number. See Release Notes for more detail" is displayed.

Import/Export Format for Structured Text Routines – The Import/Export format for Structured Text routines was changed in version 12. The STX_ROUTINE and END_STX_ROUTINE delimiters were changed to ST_ROUTINE and END_ST_ROUTINE, respectively. Version 12 or later of the application continues to recognize the obsolete STX_ROUTINE when importing, but exports using the new format. Any attempt to Copy/Paste, Drag/Drop, or Import a version 12 or later Structured Text routine into version 11 software will fail.

Online Editing Views for SFC and ST – With the addition of online editing for SFC and ST in version 13, new LOGIC and END_LOGIC delimiters were added to identify Original, Pending Edits, and Test Edits views in the export file for the SFC and ST languages. These new delimiters are not recognized in older versions of RSLogix 5000 software, so version 13 or later generated .L5K files with SFC or ST online edits should not be imported into versions earlier than version 13.

Data Types and Keywords – If you are importing an older version project (earlier than version 11) you may get the error message "An error occurred while creating DATATYPE xxxx (One or more arguments invalid.)" for some user-defined data types. The likely cause of this error is the use of reserved keywords introduced in version 11 as data type names. Normally, user-defined data types that use keywords are renamed by appending a numeral. If an undefined data type is nested within another data type, it may be that the undefined data type uses a reserved keyword name and causes the error. To work around this anomaly, rename any undefined data types to non-keyword names.

Motion Axis Tags and Axis Object Attributes – In addition to the Import/Export changes described above, there have been many changes to motion axis tags and axis object attributes that result in warning messages when importing older version *.L5K files. These warning messages are in the format:

Warning: Line ###: An error occurred while setting attribute <name_of_attribute> of tag <name_of_axis_tag> (Couldn’t be found).

The same type of warning message is displayed if you import objects that previously accepted NA as values. In this release, the not applicable values are exported as <NA>.

Changes to applications installed with Studio 5000

In this release, the PLC-5/SLC translator tool has been renamed. It is now called the RSLogix Project Migrator. The tool converts RSLogix 5 and RSLogix 500 projects into .L5K files that you can import into Logix Designer. It includes the following enhancements:

• Improved handling of symbol and comment truncation.
• Improved SLC I/O migration.
• Ability to migrate MicroLogix projects.

Adding new case selection in an ST routine can cause Logix Designer to shut down (x166840)

Corrected Anomaly with RSLogix 5000 v27.00

Adding a new case selection in a Structured Text routine can cause the Logix Designer application to shut down. (x166840)

Logix Designer shuts down when WIBU detects malicious debugger (x165361)

Anomaly

Studio 5000 Logix Designer v27.00

When WIBU AxProtector detects a potentially malicious debugger application, Logix Designer shuts down. As a workaround, disable debugging applications that are running on your computer and restart Logix Designer. (x165361)

Adding a new case selection in a Structured Text routine (Lgx00166840)

Adding a new case selection in a Structured Text routine can cause the Logix Designer application to shut down.

This anomaly first identified in version 20.03.

Cannot inhibit or uninhibit digital I/O children of Flex Ethernet adapters. (x168597)

This anomaly first identified in version 23.00.

Selecting any MPAS motor for an AXIS_SERVO_DRIVE axis (Lgx00168128)

Selecting any MPAS motor for an AXIS_SERVO_DRIVE axis, with the A-type feedback (for example, MPAS-A6xxxB-ALM02x), populates incorrect motor feedback data.

This anomaly first identified in version 24.00.

Navigation slow in large Structured Text routines (Lgx00165806)

Navigation is sometimes slow in very large Structured Text routines.

This anomaly first identified in version 26.00.

Error indicator does not appear for partial import (Lgx00159197)

An error indicator does not appear when you attempt to perform a partial import of a program that has been configured to include a Fault Handler or Power-Up Handler.

This anomaly first identified in version 24.00.

Deletion of parent module while adding child results in a fatal error (Lgx00162842)

When deleting a CN2 or EN2T module while adding a child to the module causes a fatal error instead of the "Failed to create module. Parent module no longer exists." error.

This anomaly first identified in version 26.00.

Fatal error after clicking the Program Schedule tab (Lgx00165002)

When editing a Logix Designer project offline, clicking the Program Schedule tab in the Event Task dialog box while the Tag Monitor is opened causes a fatal error. 

This anomaly first identified in version 26.00.

The Logix Designer application not responding while using Go To navigate tag in Add-On Instruction (Lgx00162099)

In the Add- On Instruction dialog box, click the Parameters or Local Tags tab, then open the Go To dialog box and navigate to the specified tag cell, which tag name has 3 level or more (such as xx.xx.xx).

Logix Designer may not respond and may need to be restarted.

This anomaly first identified in version 26.00.

One 2715 HMI PanelView allowed per Logix Designer project (Lgx00167397)

Rockwell recommends limiting the number of 2715 HMI PanelViews to one per Logix Designer project.

This anomaly first identified in version 26.00.

Math status flags in structured text routines block project download to ControlLogix 5570 controllers (Lgx00169037)

In version 27 of the Logix Designer application, project downloads fail for ControlLogix 5570 controllers for projects that contain math status flags in structured text routines.

This anomaly first identified in version 27.00.

Two Cycle timing displayed Actual Utilization Motion (Task I/O Cycle) is twice of Estimated Utilization (Lgx00165236)

When using 2-cycle timing mode, the Task I/O Cycle value under Actual Utilization - Motion on the Axis Schedule tab is not accurate. The actual value is (0.66 * value displayed).

This anomaly first identified in version 26.00.

Logix Designer shuts down when WIBU detects malicious debugger (Lgx00165361)

When WIBU AxProtector detects a potentially malicious debugger application, Logix Designer shuts down. As a workaround, disable debugging applications that are running on your computer and restart Logix Designer.

This anomaly first identified in version 26.00.

One 2715 HMI PanelView allowed per Logix Designer project (Lgx00167397)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

Rockwell recommends limiting the number of 2715 HMI PanelViews to one per Logix Designer project. (Lgx00167397)  

Logix Designer sometimes freezes when renaming input tags in AOIs (Lgx00168629)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

The Logix Designer application sometimes freezes and must be restarted when you rename an input parameter tag in an Add-On Instruction. (x168629)

Removing SD card from controller while flashing firmware can lock up the controller (Lgx00170010)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger (Lgx00168499)

When a project is imported, Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger and the import fails.

This anomaly first identified in version 27.00. 

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.

Logix Designer fails to set default value for ProgrammaticallySendEventTrigger and import fails (Lgx00168499)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Removing SD card from controller while flashing firmware can lock up the controller (Lgx00170010)

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

Logix CPU Security Tool

Known Anomaly First Identified as of Firmware Revision 20.011

RSLogix 5000™ Version 20.00

Studio 5000 Logix Designer™ First Identified as of Version 21.00

Catalog numbers:

• 1756 ControlLogix® L6
• 1756 ControlLogix L7
• 1756 GuardLogix L6
• 1756 GuardLogix® L7
• 5370 CompactLogix™ L1
• 5370 CompactLogix L2
• 5370 CompactLogix L3
• 1789 SoftLogix™

Disable Download Project Documentation and Extended Properties Features (Lgx00135928)

Known Anomaly First Identified As Of Firmware Revision 21.011

Studio 5000 Logix Designer First Identified As Of Version 21.00

Anomaly First identified in Studio 5000 Logix Designer v24.00

Corrected anomaly with Studio 5000 Logix Designer v28.01

Clearing the Enable Alarm check box does not disable the alarm on the 1794-IF8IHNFXT module when it is configured for 4 to 20 milliamps.

When alarm is triggered, clearing the Enable Alarm check box on the Alarm tab does not disable the high and low alarms. The Enable Alarm parameter controls only the Loop/Remote alarms, therefore clearing the Enable Alarm check box disables only the Loop/Remote alarms.

To disable the High and Low alarms, set the "ChxxHAlarmLimit" and "ChxxLAlarmLimit" values in the controller tags to zero, and then clear the Enable Alarm check box on the Alarm tab.

Anomaly

Studio 5000 Logix Designer v26

Anomaly corrected in Studio 5000 Logix Designer v28

When deleting a CN2 or EN2T module while adding a child to the module causes a fatal error instead of the "Failed to create module. Parent module no longer exists." error.

Anomaly

Studio 5000 Logix Designer v26

Anomaly corrected in Studio 5000 Logix Designer v28

When editing a Logix Designer project offline, clicking the Program Schedule tab in the Event Task dialog box while the Tag Monitor is opened causes a fatal error.

Anomaly

Studio 5000 Logix Designer v26

In the Add- On Instruction dialog box, click the Parameters or Local Tags tab, then open the Go To dialog box and navigate to the specified tag cell, which tag name has 3 level or more (such as xx.xx.xx). Logix Designer may not respond and may need to be restarted.

Anomaly

Studio 5000 Logix Designer v26

Anomaly corrected with Studio 5000 Logix Designer v28

When using the Output CAM Editor to make changes to an Output CAM that contains an Alias Tag, you will get a fatal error when you click Apply within the editor. The work around is to use the direct address for the Output CAM operand of the MAOC rather than the alias tag.

Anomaly

Studio 5000 Logix Designer v26

When using License Based Source Protection, Developers and Testers have noticed performance issues with the application at times with the default server configuration list in CodeMeter WebAdmin. If you are is not using any other products that utilize Wibu’ s CodeMeter that require CodeMeter to be configured in a different way, and you do not require license based source protection utilizing a license on the network, you can enter the following configuration to prevent searching the network for licenses and improve performance.

1. Open the CodeMeter WebAdmin window (http://localhost:22350).
2. Click the Configuration tab.
3. Add 127.0.0.1 (the localhost IP address) to the Server Search List.

Math status flags in structured text routines block project download to ControlLogix 5570 controllers (Lgx00169037)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

In version 27 of the Logix Designer application, project downloads fail for ControlLogix 5570 controllers for projects that contain math status flags in structured text routines. (Lgx00169037)

Two Cycle timing displayed Actual Utilization Motion (Task I/O Cycle) is twice of Estimated Utilization (Lgx00165236)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

When using 2-cycle timing mode, the Task I/O Cycle value under Actual Utilization - Motion on the Axis Schedule tab is not accurate. The actual value is (0.66 * value displayed). (Lgx00165236)

Tip: This value is accurately calculated when not using 2-cycle timing mode.  

Forced message is missing when Force Detection is enabled and Monitoring Tag (Lgx00163517)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly correct in Studio 5000 Logix Designer v28

Minimum Reproduction Steps

1. In the Workstation Options dialog box, on the Tag Editor/Data Monitor tab, select the Enable I/O Force Detection check box.

2. Establish a force mask on any data on a module I/O tag.

3. Open the Tag Monitor window that has a tag (or alias to a tag) with forces.

Expected Results

During download, warning messages are shown for each force established. For example:

• Warning: Tag “Local:1:I”: Force detected.”

• Warning: Tag “Local:2:I”: Force detected.”

Actual Result

The presence of an opened Tag Monitor window suppresses the warnings for tag forces.

Tip: During a Verify Controller operation, you will see the warnings for forces that are present.

This anomaly is only during the indication during a download verify.

(Lgx00163517)

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.  

Cannot set the Final Connection for an imported tag when in Remote Run or Program mode (Lgx00165885)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

When the controller is in Remote Run or Program mode, you cannot set the Final Connection for an imported tag. As a workaround, go offline and set the Final Connection for the tag. (Lgx00165885)

Preset and Accum values are not overwritten during import (Lgx00165936)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

When you import a program, the Preset and Accum values are not overwritten, even when you select Overwrite as the Operation on the Import Configuration dialog box. As a workaround, import the program and change the Preset and Accum values after the import is complete. (Lgx00165936) 

Fatal error occurs when adding alarms to a Function Block Diagram when online (Lgx00167922)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly correct in Studio 5000 Logix Designer v28

A fatal error can occur when you add alarms to a Function Block Diagram when online with the controller. As a workaround, add the alarms while offline. (Lgx00167922) 

Find All command fails to find tag names embedded in Structured Text (Lgx00168112)

Anomaly

Studio 5000 Logix Designer v27.00

The Find All command fails to find tag names embedded in Structured Text. (Lgx00168112)

Properties dialog box contains errors for source-protected AOIs (Lgx00168180)

Anomaly

Studio 5000 Logix Designer v27.00

Anomaly corrected in Studio 5000 Logix Designer v28

When you open the Properties dialog box for an Add-On Instruction protected by Source Protection, the dialog box should display only the General tab, and "Source not available" should appear at the bottom of the dialog box. However, the Sheet Layout tab appears (though it cannot be selected), and no text appears at the bottom of the dialog box. (Lgx00168180) 

Project containing AOIs fails to download to a safety controller on second attempt (x168232)

Anomaly

Studio 5000 Logix Designer v27.00

A project containing an Add-On Instruction downloads with errors under the following conditions:

• The project is downloaded to a safety controller with the Download Project Documentation and Extended Properties check box unselected.
• The project is uploaded from the controller and the Logix Designer application is taken offline from the controller.
• When offline, the project is downloaded to the safety controller again with the Download Project Documentation and Extended Properties check box unselected, and the following error occurs:

Invalid signature ID. Reseal instruction to resolve. (x168232)

Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger (x168499)

Anomaly

Studio 5000 Logix Designer v27.00

When a project is imported, Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger and the import fails. (Lgx00168499)

Import Configuration Error pane fails to display expected errors and warnings (Lgx00163240)

Anomaly

Studio 5000 Logix Designer v27.00

The Errors and Warnings pane on the Import Configuration dialog box sometimes fails to display expected errors. (Lgx00163240)

Copy and Paste from one language switching project to another fails to paste project documentation and extended properties (x162447)

Anomaly

Studio 5000 Logix Designer v27.00

Project documentation, extended properties, and custom properties are not included when you copy and paste project components from one language-switching project to another. (x162447)

Output data remains high for inhibited modules during testing (Lgx00177604)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

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

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.

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.

You cannot link a FactoryTalk View Studio SE software, version 6, to a Logix Designer applications that use ALMA or ALMD instructions. You must upgrade your FactoryTalk View Studio SE software to version 7 to link that application to a Logix Designer application that uses the ALMA or ALMD instructions.

Note the following:

• Use FactoryTalk Alarm and Events services. Recommended version is View 8.0 (2.71 CPR 9 SR 7.1)
• The elements related to temporary alarm buffering that were available in pre-v21 releases were replaced with a permanent alarm log. Programming code that used these alarm elements require re-coding.
• Alarms and Events subscription is not supported by v21 and v23 controllers.
• New subscribers support both pre- and post-v24 models.

This anomaly first identified in version 21.00.

When alarm is triggered, clearing the Enable Alarm check box on the Alarm tab does not disable the high and low alarms. The Enable Alarm parameter controls only the Loop/Remote alarms, therefore clearing the Enable Alarm check box disables only the Loop/Remote alarms.

To disable the High and Low alarms, set the ChxxHAlarmLimit and ChxxLAlarmLimit values in the controller tags to zero, and then clear the Enable Alarm check box on the Alarm tab.  

This anomaly first identified in version 24.00.

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

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

This anomaly first identified in version 26.00.

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

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.

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.

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.

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.

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.

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.

Output Cam editor with UDT alias causes a crash when you click Apply (Lgx00161890)

When using the Output CAM Editor to make changes to an Output CAM that contains an Alias Tag, you will get a fatal error when you click Apply within the editor. The work around is to use the direct address for the Output CAM operand of the MAOC rather than the alias tag.

This anomaly first identified in version 20.01.

Copy and Paste from one language switching project to another fails to paste project documentation and extended properties (Lgx00162447)

Project documentation, extended properties, and custom properties are not included when you copy and paste project components from one language-switching project to another.

This anomaly first identified in version 26.00. (fixed in 29)

Forced message is missing when Force Detection is enabled and Monitoring Tag (Lgx00163517)

Minimum Reproduction Steps

1. In the Workstation Options dialog box, on the Tag Editor/Data Monitor tab, select the Enable I/O Force Detection check box.

2. Establish a force mask on any data on a module I/O tag.
3. Open the Tag Monitor window that has a tag (or alias to a tag) with forces.

Expected Results

During download, warning messages are shown for each force established. For example:

• Warning: Tag “Local:1:I”: Force detected.”
• Warning: Tag “Local:2:I”: Force detected.”

Actual Result

The presence of an opened Tag Monitor window suppresses the warnings for tag forces.

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

Cannot set the Final Connection for an imported tag when in Remote Run or Program mode (Lgx00165885)

When the controller is in Remote Run or Program mode, you cannot set the Final Connection for an imported tag. As a workaround, go offline and set the Final Connection for the tag.

This anomaly first identified in version 26.00.

Preset and Accum values are not overwritten during import (Lgx00165936)

When you import a program, the Preset and Accum values are not overwritten during an import, even when you select Overwrite as the Operation on the Import Configuration dialog box. As a workaround, import the program and change the Preset and Accum values after the import is complete.

This anomaly first identified in version 26.00.

Fatal error occurs when adding alarms to a Function Block Diagram when online (Lgx00167922)

A fatal error can occur when you add alarms to a Function Block Diagram when online with the controller. As a workaround, add the alarms while offline.

This anomaly first identified in version 26.00.

Find All command fails to find tag names embedded in Structured Text (Lgx00168112)

The Find All command fails to find tag names embedded in Structured Text.

This anomaly first identified in version 26.01.

Properties dialog box contains errors for source-protected AOIs (Lgx00168180)

When you open the Properties dialog box for an Add-On Instruction protected by Source Protection, the dialog box should display only the General tab, and "Source not available" should appear at the bottom of the dialog box. However, the Sheet Layout tab appears (though it cannot be selected), and no text appears at the bottom of the dialog box.

This anomaly first identified in version 26.01.

Project containing AOIs fails to download to a safety controller on second attempt (Lgx00168232)

A project containing an Add-On Instruction downloads with errors under the following conditions:

• The project is downloaded to a safety controller with the Download Project Documentation and Extended Properties check box unselected.
• The project is uploaded from the controller and the Logix Designer application is taken offline from the controller.
• When offline, the project is downloaded to the safety controller again with the Download Project Documentation and Extended Properties check box unselected, and the following error occurs: Invalid signature ID. Reseal instruction to resolve.

This anomaly first identified in version 26.01.

Logix Designer sometimes freezes when renaming input tags in AOIs (Lgx00168629)

The Logix Designer application sometimes freezes and must be restarted when you rename an input parameter tag in an Add-On Instruction.

This anomaly first identified in version 24.00.

Import Configuration Error pane fails to display expected errors and warnings (Lgx00163240)

The Errors and Warnings pane on the Import Configuration dialog box sometimes fails to display expected errors.

This anomaly first identified in version 24.00. 

Clearing the Enable Alarm check box does not disable the alarm on the 1794-IF8IHNFXT module when it is configured for 4 to 20 milliamps (Lgx00156945, Lgx00158243, Lgx00160986)

When alarm is triggered, clearing the Enable Alarm check box on the Alarm tab does not disable the high and low alarms. The Enable Alarm parameter controls only the Loop/Remote alarms, therefore clearing the Enable Alarm check box disables only the Loop/Remote alarms.

To disable the High and Low alarms, set the "ChxxHAlarmLimit" and "ChxxLAlarmLimit" values in the controller tags to zero, and then clear the Enable Alarm check box on the Alarm tab.

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

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.

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.

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.

Find All search limited to Edit Zones produces incorrect results (Lgx00139950)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Find All search limited to Edit Zones produces incorrect results (Lgx00139950)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

GCC Compile Error occurs when project contains ALMA instructions in FBD routine (Lgx00137675)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Go To dialog context varies within FBD Editor (Lgx00143603)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

The Go To dialog context varies within the Function Block Diagram (FBD) Editor.

This anomaly first identified in version 23.00.01.

Remove Alarm Buffer object from GSV/SSV instructions (Lgx00138886)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Remove the Alarm Buffer object from the GSV/SSV instructions. (Lgx00138886)

This anomaly first identified in version 21.00.03.

Enhanced Cam Editor not fully disabled even when Maintain Project permission has been denied (Lgx00029563)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

The Enhanced Cam Editor is not fully disabled even when Maintain Project permission has been denied for the user.

This anomaly first identified in version 11.16.00.

Firmware cannot be updated after licensed connection key has been revoked (Lgx00168994, Lgx00169634, Lgx00156630)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

When the controller contains firmware that has revoked the licensed connection key for older revisions of software, those older revisions of software cannot establish a connection with the controller in order to flash the controller back to a compatible revision of firmware.

This anomaly first identified in version 21.00.03.

Safety modules fail to instantiate after installation of Ethernet module AOP profile 10.00.3664 (Lgx00170167)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Tool tip for undefined tag in Ladder Editor needs improvement (Lgx00176367)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Commissioning tests stay in testing phase and do not complete (Lgx00177511)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Errors and Warnings pane on Import Configuration dialog box sometimes fails to display errors (Lgx00163240)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Add instruction error code 111, "An Axis With Maximum Acceleration of Zero is Invalid" (Lgx00179479)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Two public parameters aliased to the same local program scoped tag (Lgx00175994)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

When you lock a safety task and generate a signature, Logix deletes all comments in safety task (Lgx00177873)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Tool tip for Dest FAL instruction indicates an undefined tag (Lgx00176367)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Safety Lock LED sometimes fails to show correct status after you restore project from SD card (Lgx00178417)

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

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:

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

Module Info B tab empty (1815893)

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

Consider these work arounds:

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

Application notes for Logix Designer version 27.00.00

These are the application notes for Logix Designer version 27.00.00.

ViewE terminals do not primarily link to Logix Designer tags by name. After you rename a tag in the Logix Designer application, ViewE terminals continue to read and write the tag based on an internal link with the tag until you download the project, power cycle the controller or terminal, or re-deploy the HMI terminal program. After one of these events the HMI attempts to link to the tag using its name to re-establish the connection. Proper procedures have to be followed after renaming a tag to propagate that change to all HMI terminals. (Lgx00126869)

The Wibu-System CodeMeter® suite of applications is installed with Logix Designer application to add resiliency to Logix Designer projects. CodeMeter is typically installed in the C:\Program Files (x86)\CodeMeter folder and the CodeMeter icon may appear on the desktop or in the Windows taskbar.

Refer to the Wibu-Systems website for specific information about CodeMeter.

When the controller contains firmware that has revoked the licensed connection key for older revisions of software, those older revisions of software cannot establish a connection with the controller in order to flash the controller back to a compatible revision of firmware. Errors include "Unable to establish a licensed session with the device" and "Attribute value not settable".

Use ControlFlash to downgrade the firmware. (Lgx00156630)

When upgrading to Logix Designer application v23 or later, any Safety Add-On Instructions that are sealed with a signature in GuardLogix need to be resealed. (Lgx00156316)

In Logix Designer application versions 21 and earlier, Equipment Phase parameters were allowed to alias any in-scope tag. Starting in version 24, Equipment Phase parameters can only alias local, non-parameter tags.

Logix projects designed to work with both FactoryTalk Batch and a Logix internal sequencer program might fail verification when you upgrade to Logix Designer application version 24. You can use the following steps to modify projects with input and output parameter tags (required for FactoryTalk Batch interoperation) that use aliases.

For projects that fail verification, the following errors appear in the errors tab.

Error: Parameter '\T200_Heat.SetPoint_P01': Input and Output parameters cannot alias global tags.

Error: Parameter '\T200_Heat.Temperature_PV': Input and Output parameters cannot alias global tags.

There are two options for resolving the verification errors.

Method 1:

4. Create a new public parameter tag to represent the internal sequencing program parameter.

• • Set the Alias For field of this tag to the same value that was specified in the Alias For field of the unverified Input or Output parameter.
  • Set the Data Type field of this new tag to be the same as that of the unverified Input or Output parameter.

5. Remove the alias from the unverified Input or Output parameter tag and instead create a connection.

• • The connection is from the unverified Input or Output tag to the newly created Public parameter tag. Make sure the data types match for both ends of the connection.

6. Test your changes to ensure that your logic continues to work as expected.

Method 2:

7. Remove the alias to the controller scope tag, from the unverified phase Input or Output parameter

8. If other programs or phases need to access the value of this phase Input or Output parameter, create an InOut parameter in the other program with the connection set to the Input or Output parameter in the first phase.
9. Test your changes to ensure that your logic continues to work as expected.

A patch is required for FactoryTalk Batch if you use the new sequencing parameters in version 24.00. You can find instructions on using the patch from the Rockwell Knowledge Base at this URL (login required):

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/606383

You can download the patch at this URL (login required):

http://compatibility.rockwellautomation.com/Pages/MultiProductDownload.aspx?keyword=Patch

Use FactoryTalk View Studio SE software, version 8 (CPR 9 SR 7.1), to link an application to a Logix Designer application that uses the ALMA or ALMD instructions. You must use FactoryTalk Alarms and Events server version.

Note the following:

• Use FactoryTalk Alarm and Events services. Recommended version is View 8.0 (2.71 CPR 9 SR 7.1)
• The elements related to temporary alarm buffering that were available in pre-v21 releases were replaced with a permanent alarm log. Programming code that used these alarm elements require re-coding.
• Alarms and Events subscription is not supported by v21 and v23 controllers.
• New subscribers support both pre- and post-v24 models.

As a best practice to ensure optimal performance, install the most current version of FactoryTalk Activation on local and centralized activation servers. The most current version is available at the following URL:

http://www.rockwellautomation.com/support/

If you use a remote activation server, refer to the following publication for more information:

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/612825

Starting with version 24, the Logix Designer application supports Input and Output program parameters. If multiple input parameters are created as aliases to the same internal program tag, the Logix Designer application does not report verification errors for the overlap. Similarly, if Output connections are connected to alias tags that alias the same base tag, an overlap error is not reported. To avoid unpredictable results, do not create multiple input parameters that alias the same local tag, or multiple Output parameters from the same program that are connected to aliases that reference the same base tag. (Lgx00148996)

If the product described by the EDS file is to be used in the I/O configuration using EDS AOP, any EDS files that have been registered for RSLogix 5000 software version 19 and earlier must be re-registered after the installation of RSLogix 5000 software version 20 or later.

The Release History and Vendor Sample Project .pdf file will not display until http://localhost is added to the list of Trusted Sites in Internet Explorer.

Storing your project comments and tag descriptions in the controller increases upload/download times.

Be aware of the following:

• If you click the Cancel dialog box during the Finalize portion of the download process, the download process continues to successful completion and you may not be able to access the controller for as long as 10 minutes.
• If the Finalizing portion of the download process takes longer than 10 minutes, the controller can generate a Major Non-recoverable fault (MNRF).

To work around this restriction, clear the Download Project Documentation and Extended Properties check box when downloading the project.

(Lgx00135928)

For 1769-L2y controller types, which were released in RSLogix 5000 software version 20, the Embedded Counters module cannot be properly configured for Pulse External Direction. This anomaly was corrected in version 20.01. 1769-L2y controllers can be properly configured by using the Logix Designer application. However, 1769-L2y projects created by using RSLogix 5000 software version 20.00 will continue to be configured incorrectly.

To correct the configuration, the controller must be recreated in the Logix Designer application. A convenient way to do this import is to use the File > Import Component feature of the Logix Designer application to import your logic from the version 20.00 project to the new version project. This affects the following controller types:

• 1769-L24ER-QB1B
• 1769-L24ER-QBFC1B, and
• 1769-L27ERM-QBFC1B.

With the introduction of the CIP Motion Load Observer enhancement in version 19 of RSLogix 5000 software, the out-of-box calculations for several CIP Axis attributes were impacted. In particular, the Position Loop Bandwidth attribute and the Position Error Tolerance attribute will be automatically adjusted when the Load Coupling is change from Rigid to Compliant and Use Load Ratio is enabled.

When a change to the Load Coupling is applied, the out-of-box Position Loop Bandwidth will be reduced by 90% and the out-of-box Position Error Tolerance will be increased by 90%. This has the effect of loosening the out-of-box Position Gains so that the Motion Load Observer loop response can be tightened.

RSLogix 5000 software version 18 has replaced the concept of Coordinated System Time (CST) Mastership with the more comprehensive notion of Time Synchronization, also referred to as CIP Sync Time Coordination. The Date/Time page of the controller properties has been modified to reflect this change.

For projects created with RSLogix 5000 software version 17 or earlier, if Coordinated System Time Master (CST) is enabled, then the converted project has the Time Synchronization setting enabled. For more information about time synchronization using CIP Sync Time Coordination, refer to the Integrated Architecture and CIP Sync Configuration Application Technique , publication IA-AT003 .

In RSLogix 5000 software version 20, there are enhanced security restrictions to controller CIP objects. Because of this, some CIP Generic messages that are used to write directly to controller object attributes sometimes do not function. Any CIP generic object write that originates external to the controller sometimes fail in version 20 or later of the application. CIP Generic writes that are executed in the controller’s own user program will operate normally.

McAfee virus software version 8.0 ships with a Quick Registry Cleaner component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of the application's classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module.

This anomaly will also prevent the creation and importing of projects. When this condition is encountered, it is necessary to uninstall and reinstall the application. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (Lgx00081691)

If your personal computer is not configured as part of a domain, you sometimes receive the error message "Unknown URL" when attempting to access Online Books or Vendor Sample Projects from the Start Page. This is the result of security enhancements to the Internet Explorer browser.

If Logix Designer application was installed by using the default installation path, the Online Books can be accessed from links provided in pdf files in C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common\<language>\Start Page\Docs\. The Vendor Sample Projects can be accessed from links provided in the file C:\Users\Public\Documents\Studio 5000\Samples\<language>\<version>\Third Party Products\Vendor Sample Projects.pdf.

Access to Online Books and Vendor Sample Projects can be allowed by adding localhost to the allowed Local Internet sites. (Lgx00089165)

The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista or later operating systems. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.

In RSLogix 5000 software version 20, overflow checking for immediate operand values has been extended to all radix formats. Earlier versions of RSLogix 5000 software checked Octal values (that is, 8#nnn) for overflow into a 32-bit integer. Starting with RSLogix 5000 software version 20, immediate operand values of any integer-type radix (Hexadecimal, Decimal, Octal, or Binary) are checked for overflow into a 32-bit integer. The overflow conditions are indicated as errors during the verification process. (Lgx00116816)

The hardwired digital inputs on the Kinetix 6200 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user's application must be written to make proper use of these digital inputs within the context of the associated motion instructions.

Creation of an event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same name. Because Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.

If you currently 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 initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.

Beginning with RSLogix 5000 software version 20, the superimposed motion behavior has changed. In Absolute mode, when Superimposed mode is programmed, the path is shifted by the superimposed motion, except for moves in the following conditions: (1) Sequence of moves using any termination type other than TT0 or TT1, (2) a merge, or (3) when the queue becomes empty.

This change allows for the capability of any path that is drawn on a table moving in either the X or Y direction as a result of superimposed motion to look exactly the same as if it were drawn on a stationary table. In RSLogix 5000 software version 19, the path was not shifted when Superimposed mode is programmed and this was not achievable. (Lgx00122482)

The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there can be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There can also be minor differences in Trapezoidal velocity profiles. Please refer to the Motion Planner, Version 16.03 Application Solution , publication RA-AP031 , for additional details.

In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.

Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (Lgx00072583)

Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types:

• MPL-A
• MPL-B
• 8720SM-xxxS
• TLY-A110T-Hxx

A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: "Axis <tag_name> Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.‟

When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.

In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (.L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: "Warning: During conversion of Axis <tag name> – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.‟

When this warning is encountered, you should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default Motion database values, canceling many previously tuned and saved axis values.

This issue does not exist with database conversion of an .ACD format project file. The motors that are affected are:

• MPF-B310P
• -B320P
• -B330P
• -B4430K
• MPG-A004-031
• -A110-031
• -A11-0-091
• MPL-A310F
• -A430P
• -B420P
• -B4520P
• -B4530F
• -B4530K
• -B580J
• -B980L
• TL-A120P-H
• -A130P-H
• -A220P-H
• A230P-H

A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be seen only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be seen on custom FactoryTalk View SE graphics. Support of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.

Beginning with version 25 of the Logix Designer application, LINT members must be aligned on 8-byte boundaries, and the UDT that contains LINT members should be sized as a multiple of 8 bytes. This impacts you if either of the following situations are true:

• You use this tag as a producer, and at least one consumer (controller) has firmware earlier than version 25.
• You use this tag as a consumer, and the producer (controller) has firmware earlier than version 25.

If you use a tag with LINT members as a producer (Source Tag), for each consumer (controller) that has firmware earlier than version 25, you need to align the LINT members on the 8-byte boundary for the data type of the consumer tag (Target Tag).

If you use a tag with LINT members as a consumer (Target Tag), for the producer (controller) that has firmware earlier than version 25, you need to align the LINT members on the 8-byte boundary for the data type of the producer tag (Source Tag).

For more information, refer to the following topic in the Logix Designer online help:

LINT data types within this tag now align on 8-byte boundaries. Check produce/consume connection.

(Lgx00167772)

The Controller time object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute DateTime, then this logic should be updated to use the new attribute LocalDateTime. You may also need to make other modifications to your application as a result of this change. (Lgx00072073, Lgx00072238)

When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:

• Two Logix5000 revision 16 firmware controllers connected to one POINT output module. One controller connected as an owner, the other controller connected as a listener.
• Two Logix5000 controllers connected to one POINT output module. One controller is at Logix5000 revision 16. The other controller is at Logix5000 firmware revision 15 or earlier.

The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.

Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions sometimes do not properly synchronize workstation time and controller time.

Rockwell Automation recommended that the Microsoft Windows operating system's Language for non-Unicode programs (System Locale) be configured to match the localized language. This is especially true for the Chinese, Japanese, and Korean editions. Not configuring the PC's operating system's System Locale to match the language of the application sometimes results in the inability of the application to show certain fonts.

If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when the application is started. Clicking Change on this warning dialog box will navigate to the operating system dialog box from which you can adjust the System Locale.

The System Locale can then be changed by selecting a new Language for non-Unicode programs (System Locale) on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of the application (9324-RLD300ZHE), you should select Chinese (PRC) for the System Locale.

The REAL data type now shows a 32-bit (4-byte) IEEE floating-point value with the following range:

• -3.40282347E38 to -1.17549435E-38 (negative values)
• 0
• 1.17549435E-38 to 3.40282347E38 (positive values)

The REAL data type also stores ±infinity, ±NAN, and -IND, but what the application shows differs based on the format.

The application also stores and shows the IEEE subnormal range:

• -1.17549421E-38 to -1.40129846E-45 (negative values)
• 1.40129846E-45 to 1.17549421E-38 (positive values)

If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre server to log messages, the Logix Designer application experiences intermittent freezes while it is waiting for the message requests to time out. This might cause the application to appear as though it has locked up, but if you wait about one minute, it will begin responding again.

To resolve this anomaly, either restore the connection to the FactoryTalk AssetCentre server or disable the RSAudit message logging. Once a connection has been restored, cached messages will be logged to the server and the application will resume normal operation. (Lgx00036127)

During a file save operation, the Logix Designer application attempts to compress the contents of a project so that the resulting file (.ACD) requires less disk space. When opening a project, this process is reversed and the contents of the .ACD file are de-compressed. In some instances, the application is not able to compress the information within the .ACD file.

In order to prevent the loss of project information, the Logix Designer application will perform the save without the compression. When this occurs, your .ACD file sometimes become abnormally large, but it is still usable. That is, you can continue to work with the file as you would normally.

If you have version 10.00 or later and also an earlier version of the application installed on your computer, you will observe an activation error if you run the version 10.00 or later version first and then attempt to run the earlier version simultaneously. To work around this anomaly, always run the earlier version first and then run the 10.00 or later version.

With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in the application without any user logic being written. However, if you expect the motor on the AM to perform in the same manner as does the IAM, a Kinetix Axis Module (AM) on the same power rail will require logic to be written.

This logic should monitor the IAM's phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes. (Lgx00071448, Lgx00071717)

If you update the firmware of a controller while it is connected to a DH485 network, communications on the network sometimes stops. To prevent this, disconnect the controller from the DH-485 network before you update the firmware of the controller. (Lgx00028491)

When using any of the controllers with nonvolatile memory, the memory store and memory load operations will take between 30 seconds and approximately 3 minutes to complete. During these operations the Logix Designer application will be taken offline and will require you to manually reconnect.

Any other workstations connected to the controller will also be taken offline. If you performed a store operation, or a load operation where your project did not have any online changes, you will be able to go back online immediately and the project will need to be saved. If you performed a load operation, and your project included online changes that you saved since the last store operation, you will be prompted to upload or download before going online.

There is a log file generated that records abnormal events and that can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of the Logix Designer application will result in a short period of program unresponsiveness followed by the appearance of a dialog box that identifies the fatal error. The dialog box contains specific details about the cause of the error. In addition, this information is appended to the file fatal error log file.

In order to more effectively address software error conditions, starting with version 15.00, the Fatal Error information is also stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. Due to the size of the dump file, special arrangements must be made in order for Technical Support to acquire these files. If it is not needed, the RSLogix 5000 Fatal Error.Dmp file can also be deleted.

These diagnostic files are now located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for the supported operating systems.

When using multiple owners or listeners of 1756 analog modules, set the Requested Packet Interval (RPI) for all connections to the same value. If different RPIs are used, connections sometimes will not recover correctly in a power-up situation.

In version 18 and later of the application, there is an External Access tag attribute, which defines how an external application can access a tag. This functionality is fully supported by RSLinx Classic software version 2.56 and RSLinx Enterprise software version 5.21. Version 18 and later of the application can be used with earlier versions of RSLinx Classic software to go online to a controller; however, earlier versions of RSLinx Classic or RSLinx Enterprise software should not be used as a data server with a controller running firmware revision 18 or later. Unexpected results will be observed when using an earlier version of RSLinx Classic or RSLinx Enterprise software as a data server with a controller running firmware revision 18 or later.

Please see Rockwell Automation Knowledgebase Tech Note #67071 .

RSLinx software maintains knowledge of the memory layout of a Logix5000 controller in order to optimize the data access performance when accessing the data in these controllers. However, changes made to an offline project that are then downloaded can result in RSLinx software attempting to access tag information that is no longer present. When this occurs, RSLinx software halts the communications to the controller.

To recover, both RSLinx software and the software requesting tags from RSLinx software must be restarted. To avoid this anomaly, use caution when making offline changes to a project and then downloading to a Logix5000 controller. In particular:

• Changing the size of an array if elements of the array are already on scan
• Renaming a structure or a member of a user-defined data type used by a tag that is on scan, or
• Changing the data type of a tag on scan from a larger size to a smaller size (for example, changing a DINT to a SINT).

Note that RSLinx Enterprise Series software is able to accommodate these changes without requiring a restart.