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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio Logix Designer v30.00

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

System Requirements Installation notes for Studio 5000 Logix Designer version 29

Review these notes before attempting to install this version of the Studio 5000® environment.

Prior to Installation

Keep the following considerations in mind before you install the Studio 5000 environment.

• Be certain that no copies of Logix Designer application or RSLogix 5000 software are currently running.
• Some antivirus software blocks or disrupts the Studio 5000 environment installation. If you experience difficulty, try disabling your antivirus software before installation and re-enable it after you install the Studio 5000 environment.
• Make sure that you have Administrator privileges on the personal computer on which you want to install the Studio 5000 environment. You will not be able to complete the installation without these privileges.
• Close all other applications before running the setup process.
• Ensure that there are no pending workstation reboot requests from either Windows Update or any installation program. If there is a pending request, reboot the workstation before starting the Studio 5000 environment installation.
• The Logix Designer application has an optimized EDS subsystem. While this provides significantly better installation time, it can cause some compatibility issues with other software packages. The following list shows some of these incompatibilities.

• • Logix Designer application v21 and later
  • RSNetWorx v25 and later
  • RSLinx v3.51 and later
  • Add-On Profiles using Core 9.0 and later
  • DeviceNet Tag Generator

Installing the Software

Follow these steps to install the Studio 5000 environment.

1. Start your personal computer.
2. Insert the Studio 5000 environment installation DVD into your DVD-ROM drive.

• The DVD-ROM should auto-start. If it does not auto-start, run Setup.exe from the root of the DVD.
• The Studio 5000 environment supports multiple versions of the programming software on a single personal computer. With version 10 and later of the application, you may install as many of the later major versions as needed plus one version earlier than version 10 (for example, version 8.02).

3. Follow the directions that appear on your screen.

• Note that the Studio 5000 environment may need to update several system files early in the installation process. These updates will likely require you to restart your personal computer. Be sure to close all other applications before clicking OK to initiate this reboot.
• When prompted for a serial number, enter the 10-digit serial number identifying your software license; otherwise, enter any sequence of characters, not longer than 10 characters.

4. When prompted, click Activate Studio 5000 to complete the activation of the software.
5. Follow the directions that appear on your screen and refer to the FactoryTalk Activation insert for additional information.

6. Click Close to complete the installation.
   
   When the setup utility finishes, an entry for the Studio 5000 environment appears in the program list in the Rockwell Software group.

7. Remove the Studio 5000 environment DVD from the DVD-ROM drive and store it in a safe place.

Starting the Studio 5000 Environment

To start the Studio 5000 environment, from the Start menu, choose All Programs>Rockwell Software>Studio 5000 from the menu.

If Studio 5000 environment does not start up or run properly, keep the following in mind:

• Do you have the correct version of RSLinx Classic software installed? RSLinx Classic software provides communication between the controller and your personal computer.
• Does your computer have enough memory? Running the Studio 5000 Engineering and Design Environment requires a minimum of 4 GB of RAM.

Uninstalling the Software

Follow these steps to uninstall the software when using the default Start menu on the Windows 7, Windows 8, Windows Server 2008R2, or Windows Server 2012 operating system.

1. From Windows Explorer, navigate to Control Panel\Programs\Programs and Features.
2. From this dialog box, double-click Studio 5000 Logix Designer <version>, and follow the prompts to uninstall.
3. If all Studio 5000 Logix Designer <version> applications have been uninstalled, from this dialog box, double-click Studio 5000 Launcher, and follow the prompts to uninstall.

System Requirements Software requirements for Studio 5000 Logix Designer version 29.00

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

The Start Page requires the Adobe Flash Player ActiveX Control to be installed prior to operation of the Start Page.

The Adobe Flash Player ActiveX Control can be downloaded from Adobe’s website at: http://get.adobe.com/flashplayer/

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

• Certain operations related to Factory Talk Security are slower on Windows 7 then they are on Windows 8.
  • Importing or Exporting a FactoryTalk Services Platform secured project
  • Securing a controller or a component of a controller with logical name or permission set
  • Clicking the Security tab in the Controller Properties dialog box.
• 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.80.00 is a component aligned to Logix Designer v28.01. RSLinx Classic v3.80.00 (CPR9 Service Release 8) has been tested, and is compatible, with the following products:
  • FactoryTalk Services Platform v2.80.00
  • RSLinx Enterprise v5.80.00
  • RSNetWorx v25.00.00
  • FactoryTalk Activation Manager v4.00.00
• RSLinx Classic v3.80.00, Logix Designer application v28.01, and device profiles that ship with the Logix Designer application v28.01 are not compatible with:
  • RSNetWorx v11.00.00 or earlier
  • DeviceNet Tag Generator v11.0.20.0

• 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 RSLogix 5000 v16.
• 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.

Cross Product Revision Interaction

Before performing this upgrade, note that Logix5000 controllers and ControlLogix Motion modules in your system must contain a revision of firmware that is compatible with this version of the Logix Designer application. However, earlier versions of network and I/O modules can operate in your system with the new controller firmware contained in this release. Additionally, other software tools such as RSNetWorx for ControlNet and RSLinx Classic software have been tested to be sure of compatibility with this version of software. Because of this, we recommend that you use the most current versions of these tools.

Rockwell Automation’s Product Compatibility and Download Center (PCDC) provides product-related downloads including firmware, release notes, associated software, drivers, tools and utilities. Use the PCDC to determine how different products interact and to compare features and capabilities between different series of products and associated firmware versions.

Use the following URL to browse to the PCDC:

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 list of popular firmware and other downloads, and to view firmware compatibility for a given product. Your Logix Designer application serial number is required to complete the download. .

Firmware for ControlLogix Redundancy

The firmware associated with this standard release version of the programming software does not support redundancy. Software versions 8, 11, 13, 15, 16, 19, 20, and 24 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 list of popular firmware and other downloads, and to view firmware compatibility for a given product. Your programming software serial number is required 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 from Rockwell 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/global/support/downloads.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.

New devices supported

Electronic Data Sheets

1. Connect the device to the computer.
2. Open RSLinx Classic, and browse for the device in RSWho.
3. Once you find the device, right-click it, and select Upload EDS file from device.

Hardware requirements for Studio 5000 Logix Designer version 29

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

Controller Message to Self Addition

In the v29.00 release of Logix Designer, a Message instruction can be configured to perform a message to the controller itself by using "THIS" in the path for the MSG (Message to Self) instruction.

The following table lists functions that a controller can perform on itself.

Click the following URL to browse to the Rockwell Automation Knowledge Base:

https://rockwellautomation.custhelp.com/app/answers/list

Powerflex 755

The Powerflex 755 feature development adds 24-Bit Resolution capability to supported feedback devices and Servo I/O support for Powerflex 755 CIP Motion drives. The 755 CIP Motion drives have also been updated to accept new 11 and 22 Series servo I/O cards that should be placed in slot 7.

Dual configurable Ethernet ports

Controllers such as the CompactLogix 5380 support dual configurable Ethernet ports. Dual configurable Ethernet ports allow pairs of physical Ethernet ports to be configured in either a Linear/DLR or Dual-IP mode. When configured for Linear/DLR mode, both Ethernet ports reside on the same Ethernet network and share IP settings. When configured for Dual-IP mode, both Ethernet ports reside on a different Ethernet network with their own IP settings. 

Support for PanelView 5000 HMI Button Control

The 5x80 family of controllers now supports HMI button control for the PanelView 5000. The new HMIBC instruction interacts with the HMI and provides the following benefits:

• Reduces lag and improved accuracy for manual jog operations.
• Provides greater flexibility than physical buttons with comparable performance.
• Eliminates the need for custom logic to verify active communications.

Instruction-based alarm support

Instruction-based alarms (ALMA, ALMD) are supported on the 5x80 family of controllers in this release.

String Literals

String literal is the representation of a fixed string value within Logix Designer programming languages. Use the string literal feature to assign string literals to a string tag, or assign a string tag to another string tag in the following editors: Structured Text, Ladder Logic, and embedded Structure Text within Sequential Function Chart. This feature is available for the 5x80 family of controllers only.

Kinetix 5700-VPC motor support

The Logix Designer application supports selection, configuration, and control of Rockwell Automation's new Kinetix VPC motors with Interior Permanent Magnet (IPM) technology.

Controller Properties updates

• Improved controller capacity calculation

• Memory tab has been renamed

• Node Count indication

Passive hookup tests do not run when Kinetix 6200 drive is in Shutdown state (Lgx00183678)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Message dialog box for Add-On Profile time synch error should not contain Help button (Lgx00183837)

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

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

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Cannot overwrite existing Add-On Instruction when imported and existing AOIs have the same edit date (Lgx00183585)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

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)

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.

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

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. 

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.

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. 

When an AOI that was sealed in a project that used a specific documentation language (English, for example) is imported into a project where the documentation language is different (Italian, for example), the project cannot be verified.

Important: As a result of a correction of this anomaly, AOI signatures that were signed in a previous version of RSLogix 5000, or Studio 5000 Logix Designer will break upon import or project conversion into version 29.00 of Studio 5000 Logix Designer. You must un-seal and then re-seal each AOI to get a new signature.

This anomaly first identified in version 28.00.00.

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Module Info page shows wrong string (Lgx00006004)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

When the internal state attribute in the Device Identity object is 0, the Module Info page shows the string "Self-Test," but it should display "Self Test or State Unknown.”

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

Logix Designer application does not differentiate between source key names when first five characters of source key names are the same (Lgx00179531)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Empty Action body while editing a Sequential Function Block routine online (Lgx00178412)

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

Position Unwind not calculated correctly on Axis Parameter List dialog box (Lgx00179155)

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

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

Corrected Anomaly with Studio 5000 Logix Designer v29.00

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

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

Using JSR with SBR instruction to pass parameters to routine and RET instruction (Lgx00177196)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Handling of Source Key names is different in v28 project than in a v24 project (Lgx00179531)

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

Guest Users cannot flash 1756-L7x controller firmware using Autoflash (Lgx00183696)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Position unwind not calculated correctly (Lgx00179155)

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

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

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Performance problems during various security actions related to Wibu on Windows 7 (Lgx00171830)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

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

Known Anomaly First Identified as of Firmware Revision 29.011

Catalog Numbers: CompactLogix™ 5380, ControlLogix® 5580

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

This anomaly first identified in version 29.00.

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.

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

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

This anomaly first identified in version 29.00.02. 

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

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

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

This anomaly first identified in version 29.00.02.

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

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

This anomaly first identified in version 29.00.02.

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

When you change the Ethernet/IP Mode from Dual-IP to Linear/DLR on a controller that supports Dual-IP, it is possible that miscommunication can occur if multiple devices on your network use the same IP address on different subnets.

The following example shows one possible configuration that could lead to miscommunication:

In Dual-IP mode, on port A1, the address of Target A on your network is 192.168.1.11. Target A is part of your project configuration. On a separate subnet via a gateway, another device, Target B, is assigned the same address. Target B is not part of your project configuration.

When you make the offline change to the project, Target A is added to the project I/O tree. When you download the project to the controller and switch to Linear/DLR mode using port A1/A2, the controller adopts the port A2 IP settings, with subnet, as the controller IP settings. The device in the I/O tree at 192.168.1.11 is not on the same subnet as the controller, so any communications to the original Target A are directed to the gateway and are sent to Target B. Although Target B was not part of your project configuration, it could receive communication sent to Target A.

This anomaly first identified in version 29.00.02.

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

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

• ALARM_DIGITAL
• ALARM_ANALOG
• HMIBC
• COORDINATE_SYSTEM

This anomaly first identified in version 29.00.02.

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

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)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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)

Cannot delete tag from Safety project (Lgx00184580, Lgx00184569)

Studio 5000 Logix Designer v29.00

Correct Anomaly with Studio 5000 Logix Designer v30.00

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

Studio 5000 Logix Designer v29.00

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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.

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00 

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

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

Studio 5000 Logix Designer v29.00

Correct Anomaly with Studio 5000 Logix Designer v30.00

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

• ALARM_DIGITAL
• ALARM_ANALOG
• HMIBC
• COORDINATE_SYSTEM
  

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

Studio 5000 Logix Designer v29.00

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

Studio 5000 Logix Designer v29.00

Controller displays incorrect date and time (Lgx00182342)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

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

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

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 an MSG instruction as documented in AID 55301 and AID 55305
• Reference the backing tags of the 1715 adapter :S tags and 1715 IO :I tags

This anomaly first identified in version 20.05.

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

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

Known Anomaly First Identified in Version 20.013

Catalog Numbers GuardLogix^® 5570

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

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

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.

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.  

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.

For more information on this anomaly and workarounds, please see technote ID BF30201.

This anomaly first identified in v20.05.

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.

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

Anomaly first identified in Studio 5000 Logix Designer v28

Studio 5000 Logix Designer v28, v29, v30

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

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

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

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

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

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

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

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

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.

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 26.00.

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.

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

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 28.03.

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

This anomaly first identified in version 20.04.

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

This anomaly first identified in version 20.00.

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 26.00.

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

This anomaly first identified in v20.01.

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

This anomaly first identified in version 17.00.

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

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 20.01.

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

This anomaly first identified in version 28.01.

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

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

This anomaly first identified in version 28.00.

To work around this issue:

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

This sequence of events can result in unexpected tag values:

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

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

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

This anomaly first identified in version 18.00.

Follow one of these steps to work around the issue:

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

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

This anomaly first identified in version 20.00.

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

This anomaly first identified in version 20.04.

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 28.00.

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

This anomaly first identified in version 28.03.

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

This anomaly first identified in version 20.01.

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

This anomaly first identified in version 26.00.

Labels are cut off and dislocated in BOOTP-DHCP Server applications (Lgx00152848)

When the font size in Windows 7 is set to 125%, the labels in the Network Settings and DHCP properties of BOOTP-DHCP Server application are cut off, making them unreadable. They are also dislocated, where they do not match with the proper input fields.

This anomaly first identified in version 23.00.

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.

Undefined Tag error (Lgx00190787)

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

This anomaly first identified in version 20.04.02.

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

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

Module Definition Change button with 1756-L71 (Lgx00167916)

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

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

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

Follow these instructions to work around the issue:

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

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

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

Failed to create module library, not registered (Lgx00203463)

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

MCAO default value zero (Lgx00188302)

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

Out of range attribute and ACD file (Lgx00182216)

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

Missing rungs of logic (Lgx00196898)

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

Not enough memory (Lgx00190656)

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

To work around this issue:

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

Do not upload tag data values when saving.

Repeatedly load a few records at a time.

Vendor specific error code (Lgx00137897)

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

Allow Unicast Consumer Connections check box (Lgx00159102)

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

Recent projects overridden (Lgx00197976)

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

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

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

Studio 5000 Logix Emulate™ (Lgx00180272)

Studio 5000 Logix Emulate upload fails with Logix 5000 Services

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

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

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

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

This anomaly first identified in version 28.00.01. 

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

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

This anomaly first identified in version 21.03.

Error when running trend (Lgx00204911)

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

This anomaly first identified in 28.01.

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:

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

Functional Changes in this release for Studio 5000 Logix Designer version 29

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.

Studio 5000 Logix Emulate

In version 29.00 of Studio 5000 Logix Designer, RSLogix 5000 Emulate software has been renamed to Studio 5000 Logix Emulate software. The catalog number has changed from Emulate to Emulate 5570.

Upload button removed from Studio 5000 Launcher

In version 29.00 of Logix Designer, the Upload button has been removed from the Studio 5000 launcher.

Controller Properties Project tab updates

The Download Project Documentation and Extended Properties check box and the Download Custom Properties check box are now on the Controller Properties Project tab. They are selected by default. Rockwell Automation recommends that you always download project documentation. See Download project Documentation and Extended properties in Application notes on page 1 for more information.

Changes to Add-On Instructions (AOI)

The following changes have been made to Add-On Instructions in this release:

• Signatures break for AOIs from earlier releases: As a result of the correction for anomaly Lgx00177571, when you use version 29.00 or later to open a project from a release earlier than version 29.00, the signature breaks for any AOI included in the project. In the same way, when you import an AOI from a project created in a release earlier than version 29.00, the signature breaks for that AOI. You must un-seal and then re-seal each AOI to get a new signature.
• Nesting limit: The nesting limit for AOIs in Logix Designer v29 has decreased from 25 levels deep to 16 levels.
• InOut parameters: The number of InOut parameters permitted within an AOI in Logix Designer v29 has increased from 40 to 64 InOut parameters.

Instruction behavior changes when replacing controllers

Behavior changes occur for some instructions when you replace a ControlLogix 5560 or ControlLogix 5700 controller with a ControlLogix 5580 controller, or replace a CompactLogix 5370 controller with a CompactLogix 5380 controller. Refer to the Replacement Guidelines: Logix5000 Controllers Reference Manual, publication 1756-RM100, for detailed considerations and explanations of the changes that you may have to make to your project when replacing controllers.

Firmware Supervisor with firmware in new DMK file format

In December 2015, firmware for modules may be provided in a new Device Management Kit (DMK) file format, for example, 1756-L73_28.011.dmk. Firmware Supervisor only supports firmware with the NVS and BIN file format.

To use Firmware Supervisor with hardware modules whose firmware is provided in a DMK file format, you must first extract the NVS and BIN files from the DMK file using the DMK Extraction Tool that is installed with ControlFLASH v13.00. Refer to the ControlFLASH online help for instructions on how to use the DMK Extraction Tool.

Controller Memory Changes

This revision of Logix5000 controllers may require more memory than earlier revisions. Before upgrading to this revision, check the amount of unused memory that you have in the controller using the Estimate tool on the Capacity tab of the Controller Properties dialog box.

• For additional information about controller memory issues refer to the Knowledgebase at: http://www.rockwellautomation.com/support/.

For the 5x80 family of controllers, the Capacity tab in the Controller Properties dialog box has been redesigned to show the size of the source code of your application rather than the physical memory the application uses to run. As a result, a new term ‘block’ has been defined that represents a unit of executable code.

The block units are only used for application source code sizes. Data structures and messages are still sized in bytes to support the design and implementation of communication interfaces with other devices.

For more information on migrating to a 5x80 controller, refer to the publication on the Literature Library, Replacement Guidelines: ControlLogix 5560/5570 Controller to ControlLogix 5580 Controller (1756-RM100).

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

The following information is provided to help you better understand the behavior of the Logix Designer application in other applications or under certain circumstances.

When an antivirus application is scanning the dynamic data of the CodeMeter CmActLicense, the Logix Designer application cannot access it. If access fails on multiple attempts, the CmActLicense becomes invalid, and you must restart the computer to clear the error. To avoid this error, consider adding the path for the CmActLicense (the default path is C:\ProgramData\CodeMeter\CmAct) to the antivirus application white list, or excluding the path from the virus scan.

To save changes to a component that is protected with License-Based Source Protection, a CmStick containing the required license must be plugged into the computer running the Logix Designer application.

Make sure you save your edits to a project before removing the CmStick containing the required license. If the license is not present or the license has expired, the Cancel/Retry dialog box appears requesting you to restore the CmStick and click Retry, or click Cancel to close Logix Designer application.

Non-alphanumeric characters in a STRING need an escape carriage

Phase Manager and SequenceManager not available on 5x80 family of controllers

To include or exclude project documentation and extended properties from a downloaded project, select or clear the Download Project Documentation and Extended Properties check box on the Controller Properties dialog box - Project tab.

Downloading project documentation and extended properties to the controller can significantly increase the amount of time it takes to download a project, especially if a project is heavily documented.

Keep the following considerations in mind when you clear Download Project Documentation and Extended Properties check box and download the project to the controller:

• Risk losing project documentation, extended properties and custom properties from the project.
• If extended properties are used in program logic, the download fails. An error in the Error tab states that you cannot access extended properties in logic when extended properties are not downloaded.
• Attempting to add logic to a routine to access extended properties in logic generates an error in the Error tab. The error states that you cannot access extended properties in logic when the extended properties are not downloaded.
• Rung comments and Sequential Function Chart and Function Block Diagram text boxes no longer exist in the controller. Therefore, code comments are no longer synchronized among multiple online workstations.
  • During online editing of rungs, other workstations display only rung comments for rungs that exactly match the rung type for the comment in their offline database. For example, if Workstation 1 performs edits on a Normal rung, Workstation 2 will not display the rung comment while the rung is in any phase of editing or testing (for example, I/R pair). When the edits are assembled and the rung returns to a Normal rung, Workstation 2 will again display its rung comment.
  • Performing online edits of any type on a Sequential Function Chart routine causes other workstations to lose their text box comments for that routine when the edits are accepted. For example, if Workstation 1 begins pending edits on a Sequential Function Chart routine and accepts those edits in any controller mode, when Workstation 2 processes those edits, all text boxes in the Sequential Function Chart routine will become blank, even if they were not modified as part of the edit. Canceling these edits will not restore the text box contents.
  • Performing online edits on a Function Block Diagram routine in Program mode causes other workstations to lose their text box comments for that routine when the edits are accepted. This is the same behavior described for Sequential Function Chart routines. In Run mode, the contents are not lost when pending edits are accepted. They essentially become test edits, and will not be lost until those test edits are subsequently assembled. As in Sequential Function Chart routines, canceling these edits will not restore the text box contents.

A limited number of events that report updates to input and output parameters of data type STRING can be generated at the same time.This affects the generation of events:

• Recording initial values of sequencing parameters
• Recording step input data passed from a sequence to a phase
• Recording phase output data passed from a phase to a sequence
• Recording sequence output parameters updating

When using sequence events, keep these recommendations in mind:

• Equipment Phases and Equipment Sequence should be run in periodic, and not continuous, tasks.
• Set the scan rate of the Equipment Sequence to be faster than the time required for an Equipment Phase to run its state routine logic (not the scan rate, but the time a phase spends executing it’s Running, Holding, Aborting, Stopping, or Resetting state routines).
• The phase changes states faster than the scan rate of the equipment sequence program.
• Generating events will constrain the performance of an equipment sequence.Only generate events when records for executing the sequence are required.
• Under rare and extreme conditions, the controller will not accept an operator command if an event to record the command cannot be generated.The Abort command always succeeds. But under the same conditions, is not recorded with an event.
• Sequence event generation can be affected by Avoid generating more than 60 events and alarms combined per second. Describe different ways that multiple events can be generated simultaneously.

Sequence Manager Applications access to Equipment Sequence data from outside the controller.

• FactoryTalk View Site Edition (SE) restricts the number of simultaneous clients connected to a controller to 50.
• The Sequence Manager Controls should not use VBA to unnecessarily request a refresh of cached sequence configuration data as the refresh blocks client applications from commanding sequences until the refresh is complete.
• It is recommended that the user configure a second Event Client service that subscribes redundantly to generate sequence event data through its own RSLinx Classic service.This ensures losing communications between the Client Service and the controller does not result in a loss of cached event data.

Improper startup synchronization between the ControlLogix or CompactLogix processors, and PowerFlex or Kinetix CIP Motion Enabled Drive may result in movement when none is expected, or lack of movement when movement is expected (sleep mode). In the case of unexpected movement, a Drive Fault with Excessive Position Error is issued. While this is not a common occurrence, the possibility of unexpected motion or lack of motion does exist. (Lgx00173808)

Occasionally, the interpolated reg position of an axis will be out of tolerance. For example, the interpolated reg position of the axis should be around .45 revs, but will sometimes show up as .54 revs. The amount that it is off is consistent. During the 1000 rev move, about 120 will be wrong. The values that are right are very accurate. The values that are wrong are consistently off by the same amount.

The workaround is for most cases is to set the RPI of the O1756-B16IEFS faster than the motion group update time. This will allow the normal sending of data at the RPI to retry the previous schedule(s) before a new set of schedules are created.

This workaround cannot cover all cases because a new schedule may be set to expire before the modules RPI can perform the retry. In those cases, the 1756-OB16IEFS will do its normal Late Schedule processing and update the Schedule Status and LateScheduleCount in the input tag.

Logix Designer shuts down when WIBU detects malicious debugger

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

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:

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

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

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

Method 2:

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

2. 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.
3. Test your changes to ensure that your logic continues to work as expected.

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

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.

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

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.

The appearance of the Equipment Phase Monitor has been updated as part of SequenceManager:

• The command symbols used in the Command Bar of the Equipment Sequence Diagram Monitor have been added to the Phase Monitor.
• The Pause functionality of the Equipment Phase has been redesigned and simplified.
  • Pause and AutoPause buttons toggle enabled or disabled.
  • The Resume button is only enabled when the Equipment Phase is Paused.
  • A single state box is filled when the phase is Paused or unfilled when not-paused.

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