Studio Logix Designer 24.001 Release Notes

Release Notes
( 9324-RLDx ) Studio 5000 programming software. All you need for discrete, process, batch, motion, safety etc.
Version 21.00.04 (released 2/2017)
Catalog Number Studio 5000 Logix Designer
These release notes describe version information for ( 9324-RLDx ) Studio 5000 programming software. All you need for discrete, process, batch, motion,
safety etc., version 21.00.04 (released 2/2017).
Requirements
This release has the following requirements.
Software Requirements Product Considerations v21
System Requirements
Logix Designer 21.x

FactoryTalk Services Platform 2.51 or later is required to run the Logix Designer application. It is required in order to perform some security functions
in the Logix Designer application.
RSLinx Classic communication software is required as part of the installation of the Logix Designer application. RSLinx Classic communication software
is required in order to perform online communication with controllers.
RSLinx Classic v3.51.00 is a component aligned to Logix Designer v21.00. RSLinx Classic v3.51.00 (CPR9 Service Release 5.1) has been tested, and
is compatible, with the following products:
FactoryTalk Services Platform v2.51.00
RSLinx Enterprise v5.51.00
RSNetWorx v21.00.00
FactoryTalk Activation Manager v3.51.00
RSLinx Classic v3.51.00, Logix Designer application v21.00, and device profiles that ship with the Logix Designer application v21.00.00 are not
compatible with:
RSNetWorx v11.00.00 or earlier
DeviceNet Tag Generator v11.0.20.0
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.
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.

Software Requirements v21
System Requirements
Logix Designer 21.x
Operating system and service pack compatibility:
0. This version of RSLogix 5000 software has been tested on the following operating systems:
1. Microsoft Windows 7 Professional (64-bit) with Service Pack 1
2. Microsoft Windows 7 Home Premium (64-bit) with Service Pack 1
3. Microsoft Windows 7 Home Premium (32-bit) with Service Pack 1
4. Microsoft Windows Server 2003 R2 Standard Edition with Service Pack 1
5. This version of RSLogix 5000 software is expected to operate correctly on all other editions and service packs of the following operating systems, but
has not been tested:
6. Microsoft Windows 7
7. Microsoft Windows Server 2008 R2
For operating systems that support User Account Control (UAC), this version of RSLogix 5000 software was tested with UAC set to the most restrictive level
(“Always notify” for Windows 7, or “On” for Vista). This version of RSLogix 5000 software 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.
Hardware Requirements v21
System Requirements
Logix Designer 21.x
The personal computer must meet these minimum requirements. Using a computer meeting the recommended characteristics will improve performance.
Characteristic Minimum Required Recommended
Processor Pentium 4 Intel Core i5

Speed 2.8 GHz 2.8 GHz
RAM Memory 2 GB 8 GB
Hard Disk Space 16 GB free 20 GB free
Graphics Device DirectX 9, with WDDM 1.0 DirectX 9, with WDDM 1.0

or higher driver or higher driver

Installation Notes
Logix Designer 21.x
Review these notes before attempting to install this version of the Studio 5000 Engineering and Design Environment.
Prior to Installation
Keep the following considerations in mind before you install the Studio 5000 Engineering and Design Environment:
Be certain that no copies of Logix Designer application or RSLogix 5000 software are currently running.
Make sure that you have Administrator privileges on the personal computer on which you want to install the Studio 5000 Engineering and Design
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 Engineering and Design Environment installation.
Version 21 of the Logix Designer application has optimized the 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.
Installing one of the following software versions:
· Logix Designer application v21
· RSNetWorx v21
· RSLinx v3.51
· Add-On Profiles using Core 9.0
· DeviceNet Tag Generator
will cause prior versions of RSNetWorx and the DeviceNet Tag Generator to become inoperable.
Important: During the installation of Logix Designer application, version 21.03, the installation stops and a dialog box opens if an incompatible version of
RSNetWorx software is detected on the PC. Upgrade RSNetWorx software to version 21 or uninstall it from your PC, and restart the Studio 5000 Engineering
and Design Environment installation.
Refer to the Choosing a Logix Designer application package section of this document to determine which controllers are supported by your series
bundle.
Installing the Software
Follow these steps to install the Studio 5000 Engineering and Design Environment.
1. Start your personal computer.
2. Insert the Studio 5000 Engineering and Design 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 Engineering and Design 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 Engineering and Design Environment version 21 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.
Important: The 10-digit serial number is used to determine what functionality to enable while in Grace Period mode. Entering an invalid serial number will
result in the application operating in Service Edition mode, upload and download only, while in Grace Period mode.
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.
Important: When a valid activation cannot be located by the application, the application will enter a seven-day activation grace period, during which you will
be able to run the application with full functionality. If this seven-day grace period ends before a valid activation has been found, you will no longer be able to
start the Logix Designer application.
6. Click Close to complete the installation.
When the setup utility finishes, an entry for the Studio 5000 Engineering and Design Environment appears in the program list in the Rockwell Software
group.
7. Remove the Studio 5000 Engineering and Design Environment DVD from the DVD-ROM drive and store it in a safe place.
Starting the Studio 5000 Engineering and Design Environment
To start the Studio 5000 Engineering and Design Environment, from the Start menu, choose All Programs>Rockwell Software>Studio 5000 from the
menu.
If Studio 5000 Engineering and Design 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 2 GB of RAM.
Uninstalling the Software
Follow these steps to uninstall the software when using the default Start menu on the Windows 7 or Windows Server 2008 operating system.
1. From the Start menu, choose Control Panel.
(for Windows 7, Windows Server 2008 R2) From the Programs category, choose Uninstall a program.
(for Windows Server 2008 – Control Panel Home) From the Programs category, choose Uninstall a program.
(for Windows Server 2008 – Classic View) Double-click Programs and Features.
2. From this dialog box, double-click Studio 5000 Logix Designer <version>.
3. If all Studio 5000 Logix Designer <version> applications have been uninstalled, from this dialog box, double-click Studio 5000 Launcher.
Note: This will uninstall only the Studio 5000 Engineering and Design Environment. Other components that were installed with the Studio 5000 Engineering
and Design Environment (such as Start Page Media, Online Books, or RSLinx) must be uninstalled separately.
Features
This release includes the following system features.
CIP-Sync Enabled Logix (1756) and Armor-Block (1732E), SOE-Input and Scheduled-Output Modules
Software Feature
Firmware Revision/ Software Version 21
Version 21 of the Logix Designer application extends the capability of Sequence of Events (SOE) Input modules and Scheduled Output sourcing modules
with the introductions of:

Armor Block 1732E-IB8MSOER and 1732E-OB8M8SR modules for On-Machine DIO, and
1756-IB16ISOE and 1756-OB16IEFS modules for Logix based IO.
These modules provide CIP Sync technology on EtherNet/IP based RA I/O platforms: 1732 Armor Block for On-Machine DIO, and 1756 Logix based IO.
They provide significant enhancement in SOE and Schedules Output functionality used in many applications such as Motion Registration and Camming
(MAOC), Packaging & Material Sorting, and 1st Fault Monitoring.
Extended Tag Properties
System Feature
Firmware Revision/ Software Version 21.011
Catalog Numbers 1756-L71, 1756-L72, 1756-L73, 1756-L74, 1756-L75, 1756-L73XT, 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-
L7SPXT
Catalog Numbers 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-
L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM
You can use Extended Properties to define additional information about a tag or structure of tags.
The Logix Designer application, version 21 or later, provides the option to specify Engineering Units and Min/Max Values for numeric tags, Engineering Units
and state information for Boolean tags.
Extended properties are also available for user defined data types, arrays, or other complex data structures.
HMI Connectivity and Performance Improvements
System Feature
L7SPXT
HMI communication drivers can perform Rockwell Automation-approved symbolic data reads. Symbolic reads improve the read performance and eliminate
errors being returned when the HMI attempts to collect data.
For more information, see the Logix5000™ Data Access Programming Manual, publication 1756-PM020.
Kinetix 5500 CIP-Motion Servo Drives
Software Feature
Version 21 of the Logix Designer application extends the capability of highly integrated motion on the EtherNet/IP network (CIP-Motion) with a new family of
Kinetix 5500 CIP-Motion Servo Drives, which is part of Rockwell Automation's MidRange solution Portfolio. The catalog selection is for 6 drives in this family
and includes 2198-H003-ERS through 2198-H078-ERS.
CIP Motion provides improved axis and drive configuration, commissioning, and diagnostic tools. The Kinetix5500 family of Servo Drives provides an external
common AC/DC bus to reduce hardware requirements and provides for scalability. Also, both power transmission and feedback are now combined through a
single cable.
The new motor family that is compatible with this Servo Drive is VP low inertia servo motors. VPL-A(230v) and VPL-B(460v) motors support Hiperface DSL
feedback. For more information about the Kinetix 5500 CIP-Motion Servo Drive, refer to the Kinetix 5500 Servo Drives User Manual, publication no. 2198-
UM001.
Kinetix 6000M Integrated Drive-Motor systems
Software Feature
Version 21 of the Logix Designer application extends the capability of highly integrated motion on SERCOS network with a new family of Integrated Drive-
Motor system, Bulletin 2094 Kinetix 6000M, part of Rockwell Automation's on-machine System solution Portfolio. Kinetix 6000M combines Rockwell
Automation's MP-Series servo motor and Kinetix 6000 servo drive technology into a single compact package. This on-machine solution integrates
seamlessly with Rockwell Automation's Kinetix 6000 and Kinetix 6200 multi-axis servo drive systems on SERCOS interface.
This on-machine package provides significant space saving, machine control simplification, and is designed to help reduce wiring time and simplify cabling.
The Integrated Drive-Motor system allows for as many as 16 Kinetix 6000M Integrated Drive-Motor units to be connected to the Kinetix 6000M power
interface module using one hybrid power cable and one SERCOS motion network cable. The Kinetix 6000 and 6200 Servo drives support SIL2/PLd Safe
Torque-Off safety circuitry. The products required are the 2094 Kinetix 6000M Power Interface module, and the MDF Kinetix 6000M Integrated Drive-Motors,
(6 catalogs at 400Volt motors, supporting with Brake or Non-Brake).
For more information about the Kinetix 6000M SERCOS based system, refer to the Kinetix 6000M Integrated Drive-Motor User Manual, publication no. 2094-
UM003.
Studio 5000 Engineering and Design Environment and Logix Designer Application
Software Feature
Version 21 of the application is the first release that re-brands RSLogix 5000 software to Logix Designer application, and embeds the Logix Designer
application as a key component of Studio 5000 Engineering and Design Environment. The Studio 5000 Engineering and Design Environment is the new
launch point for components of the integrated architecture, providing the infrastructure to share data, share design time components, and share runtime
components between traditionally independent automation development tasks.
Pre-scan of Add-On Instruction Behavior
System Feature
L7SPXT
The Pre-scan behavior of Add-On Instructions has been enhanced. This enhancement can affect Pre-scan behavior of Add-On Instructions when indirect
addressing is used.
This enhancement can improve the Add-On Instruction initialization behavior when indirect addressing is used.
For more information, see Rockwell Automation Knowledgebase document 481124.
You can access the Rockwell Automation Knowledgebase at: http://www.rockwellautomation.com/rockwellautomation/support/overview.page?
Project Documentation Stored in Controller
System Feature
L7SPXT
The Logix Designer application, version 21, provides the option to store all of your project documentation, including comments, tag descriptions, and other
key descriptors of the project in the controller.
Other project descriptions can be stored online, such as routine descriptions and task descriptions.
Uploading a project now restores all of the original project documentation without having to find the original ACD file.
Corrected Anomalies
This release corrects the following anomalies.
Unable to Open Full L5X Project File (x114197)
Corrected Anomaly
RSLogix 5000 18.x
If you attempt to open a full project import file that uses XML format (.L5X file format) by using a version of RSLogix 5000 software earlier than the version of
RSLogix 5000 software from which the project was exported, then the project will not be opened. An error dialog box will be displayed stating 'Controller
revision is not supported'. In order to open an L5X format project file, you will need to first launch a version of RSLogix 5000 software that is at or later than
the version from which the project was exported. (One way to launch a particular version of RSLogix 5000 software is to use File>New to create a new
controller for the selected Revision.) Note that this anomaly does not affect the way that L5K and ACD project files are opened. When an L5K or ACD file is
opened, the appropriate version of RSLogix 5000 software will be automatically launched before opening the project.

Corrected anomalies for Studio 5000 Logix Designer v21.00
Under certain conditions, the presence, absence, or insertion of a Secure Digital card can cause the controller to generate a Major Non-Recoverable
fault. For more information, see Rockwell Automation Knowledgebase document 495063. (x130075)
For the L1 controller, the controller’s embedded I/O module firmware may not be updated due to a corrupt embedded I/O module firmware image. For
more information, see Rockwell Automation Knowledgebase document 498109. (x127607)
When the drive is running at small coarse update period such that late or lost Drive-to-Controller (D2C) updates are being seen, the Logix controller
extrapolates the actual position during the lost D2C updates. The extrapolation algorithm computed the actual position incorrectly that resulted in
incorrect velocity. If the actual velocity is plotted, you will see velocity spikes during lost D2C updates. (x132326)
For the L1 controller, if you remove or insert local expansion POINT I/O modules while under power, you can cause the controller to experience a
Major Non-recoverable fault. (x131054)
RUN LED on controller shows wrong state if you overload the system with very fast RPI limits on a CompactLogix controller that is communicating with
SDN modules. It may cause the Run LED to incorrectly report Run mode when the controller has not finished its transition to the new mode. If this
happens, cycle power to the controller and switch to Program mode when power is applied. (x133064)
RSLogix 5000 reports a Fatal Error while typing in the tag operand field of a Ladder instruction. (x125908)
A Fatal Error is reported when performing a copy and paste operation on a rung that is being edited while online. (x127957)
After configuring the import of a routine, if a tag is renamed and the Show differences only Data Comparison option is selected, a Fatal Error could be
reported when the routine is imported. (x128439)
When attempting to delete a component of a tag, such as an array element or a structure member, a dialog box is displayed asking users if they wish
to delete the entire tag. Clicking No results in a Fatal Error. (x129693)
A Fatal Error can be reported when searching for forces in logic. (x133070)
RSLogix 5000 sometimes reports a Fatal Error when verifying or saving the project when very long tags of type STRING are present. (x133889)

Generating WinHlp32 Database for Find Tab (x88677)
Corrected Anomaly
RSLogix 5000 Software 16.x
If you are logged on using an account that does not have Administrator privileges, you may be unable to generate the database for the Find tab for RSLogix
5000 Online Help. An error message will be displayed indicating “Unable to display the Find tab” or “WinHlp32 has stopped working”. This error can be
resolved by generating the database while logged on using an account with Administrator privileges. If RSLogix 5000 will be used by an account that does
not have Administrator privileges, we suggest that the database be created as part of the installation process while still logged on using an account that has
Administrator privileges.
Corrected: Logix Firmware/RSLogix 5000 Software 20.012
Corrected: SoftLogix 5800 Version 20.01.00
Home to Torque Level (Lgx125135, Lgx00127942)
Anomaly
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-
L72S, 1756-L73, 1756-L73S, 1756-L73XT, 1756-L73XT, 1756-L74, 1756-L75 Version 20.011
Catalog Numbers 1789-L10, 1789-L30, 1789-L60
The 'Home to Torque Level - Marker' on SERCOS drives operated correctly in version 19.00.00. but does not in version 20.00.00. This functionality is now
fixed. 'Home to Torque' without marker was not affected.

Known Anomalies
This release has the following known anomalies.
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
Windows 7 Operating Systems (x111504, x113166, v124864)
Anomaly
RSLogix 5000 19.x
There are a number of issues related to compatibility of RSLogix 5000 software with the Windows 7 operating system. The most significant of these includes
the following:
Although RSLogix 5000 software versions earlier than version 19 can be installed, they are not supported on Windows 7 operating systems. Also note
that some applications and tools cannot be installed on a 64-bit Windows 7 operating system. Most notably, RSLogix 5000 software version 12 and
earlier cannot be installed on a 64-bit Windows 7 operating system.
On some properties dialog boxes, there is no indicator shown when a control has focus. A workaround to display focus indicators is to select the
Windows 7 setting to 'Underline keyboard shortcuts and access keys'. Access this setting by using Personalize>Ease of Access Center>Make the
keyboard easier to use>Underline keyboard shortcuts and access keys. (x113166)
The RSLogix 5000 Clock Update tool does not work properly when it is installed on a 64-bit Windows 7 operating system and executed. (x124864)
Modification of Add-On Instruction change date containing embedded UDT (Lgx0136323)
Corrected
Studio 5000 Logix Designer 21.00
An anomaly is present for tracking the change date of an Add-On Instruction that contains a user-defined data type (UDT). In Prior releases, when this
embedded UDT had a modification of the UDT name, the Add-On Instruction it was embedded in would update its change date. In this current release, this
has been noted to account for changes in individual members within the UDT as well as the description or comments for each member of the UDT. Now for
any modification of the embedded UDT, the Add-On Instruction change date will reflect this modification and update its change date value. This anomaly is
limited to the first nested layer of a UDT only. If a nested UDT is modified, then this modification will not be captured as a change date for the Add-On
Instruction at this time.
ALMA and ALMD Instructions in Logix Designer
CORRECTED with Firmware Revision 24.011
Studio 5000 Logix Designer Version 24.00
Known Anomaly First Identified as of Firmware Revision 21.011
Catalog Numbers:
1756 ControlLogix L7
1756 GuardLogix L7
5370 CompactLogix L1
Even though controllers that use firmware revision 21.011 or later can use ALMA and ALMD instructions, FactoryTalk View Studio SE software, versions 6
and 7, cannot connect to a Logix Designer application that uses firmware revision 21.011 or later and uses ALMA or ALMD instructions.
IMPORTANT: This anomaly applies to the use of ALMA and ALMD instructions only. Tag-based alarming systems that use FactoryTalk Alarms and Events
functionality work as expected.
IMPORTANT: This anomaly applies to the use of ALMA and ALMD instruction only. Tag-based alarming systems that use FactoryTalk Alarms and Events
functionality work as expected with FactoryTalk View Studio SE software, version 6.
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
Catalog Numbers:
- 1756 ControlLogix L7
- 17
56 GuardLogix L7
- 5370 CompactLogix L1
IMPORTANT: The following restrictions apply to enabling or disabling the Download Project Documentation and Extended Properties feature and should be
considered collectively. Any, or none, of these restrictions might apply to your application.
Restriction #1
Storing your project comments and tag descriptions in the controller can increase 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 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 checkbox when downloading the project.
Restriction #2
IMPORTANT: This restriction exists only in environments that use multi-workstation development.
If you are using multi-workstation development, we strongly recommend that you configure the Logix Designer project to include all project documentation
and extended properties when downloading a project to the controller.
This configuration setting is the default setting.
A Logix Designer project can lose content from the text boxes for routines written in either Function Block Diagram (FBD) or Sequential Function Chart (SFC)
programming languages when both of the following conditions exist:
• Multiple workstations are online with the controller.
• The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared.
When project edits are made at one workstation, the content in the text boxes of edited routines are deleted from all of the other workstations in the
environment.
To work around this restriction, configure the Logix Designer project so that the Download Project Documentation and Extended Properties checkbox is
checked.
IMPORTANT: Consider the following:
• This anomaly does not apply if your Logix Designer project uses Ladder Logic (LL) or Structured Text (ST) programming languages.
• A restriction applies to when you check the Download Project Documentation and Extended Properties checkbox.
Restriction #3
IMPORTANT: This restriction exists only in environments that use multi-workstation development.
If you are using multi-workstation development, we strongly recommend that you configure the Logix Designer project to include all project documentation
and extended properties when downloading a project to the controller.
A Logix Designer project can temporarily lose content in the Rung Comments sections when all of the following conditions exist:
• Multiple workstations are online with the controller.
• The Logix Designer project uses the Ladder Logic programming language.
When project edits are made at one workstation, the content in the Rung Comments sections for the project rungs is briefly hidden in all of the other
workstations in the environment.
When rung edits are finalized on the workstation that is making edits, the content in the Rung Comments sections for the project rungs reappears in the in all
of the other workstations in the environment.
To work around this anomaly, configure the Logix Designer project so that the Download Project Documentation and Extended Properties checkbox is
checked.

Corrected: Logix Firmware/Studio 5000 Software 21.011
Log On to FactoryTalk Dialog Box Displays When Launching RSLogix 5000 (00124955)
Known Anomaly First Identified as of:
Firmware Revision 20.011, 1769-L23E-QB1B, 1769-L23E-QBFC1B, 1769-L23-QBFC1B
Firmware Revision 20.011, 1769-L31, 1769-L32C, 1769-L32E,1769-L35CR, 1769-L35E
Firmware Revision 20.011, 1768-L43, 1768-L43S, 1768-L45, 1768-L45S
When launching RSLogix™ 5000 software, the Log On to FactoryTalk® dialog box can display. This dialog box can be seen when you do not have
Administrator privileges on the personal computer and the current user does not exist in the FactoryTalk directory. If this dialog box is canceled, the RSLogix
5000 software is not launched. When the dialog box is displayed, entering the credentials for a user that has Administrator privileges on the personal
computer allows RSLogix 5000 software to be launched.
To avoid seeing this dialog box, you can add the current user or user group to the FactoryTalk directory. Follow these steps to add a user or user group to
the FactoryTalk directory.
1. Launch the FactoryTalk Administration Console (available from the Start menu).
2. Select the Network directory when prompted.
(In some cases, to continue, you need to provide credentials for a user with Administrator privileges.)
3. To allow access for a particular user, navigate to Network\System\Users and Groups\Users, right-click the Users folder and choose New>Windows
Linked User.
4. Click Add and provide the domain\logon name for the desired user.
(You can click Check Names to verify that the name was found.)
5. To allow access for all authenticated users, navigate to Network\System\Users and Groups\User Groups, right-click the User Groups folder and
choose New>Windows Linked User Group.
6. Click Add and type the name of the user group, Authenticated Users.
The Log On to FactoryTalk dialog box can also be displayed when you are using Remote Desktop to connect to the personal computer running RSLogix
5000 software.
This dialog box appears because FactoryTalk Security does not recognize the computer name. To enable access through Remote Desktop for a specific
computer, you must add the name of the computer initiating the Remote Desktop connection to the Network\System\Computers and Groups\Computers
folder in the FactoryTalk Administration Console.
To allow all computers to connect, follow these steps.
1. Open the FactoryTalk Administration Console and log in to the Network directory with your domain credentials.
2. Navigate to Network\System\Security Policy. In the Computer Policy Settings section, set Identify terminal server clients with the name of to Server
Computer.
IMPORTANT: If Use single sign-on is set to disable in FactoryTalk software, then the Log On to FactoryTalk dialog box is displayed each time RSLogix 5000
software is launched. When this is launched, proper user credentials must be entered to continue. (By default, ‘Use single sign-on’ is set to enable.)
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
1789 SoftLogix™
The Logix CPU security tool does not work with Version 20 and greater controllers.
Logix Designer Not Able to Download Project
Studio 5000 Logix Designer Version 21.00
Catalog Numbers
- 1756 GuardLogix L7
Your Logix Designer application project will not download in the following conditions:
• The controller ’s programming code uses minimum or maximum extended properties in code elements tag name.@MIN or tag name@MAX.
To work around this restriction, check the Download Project Documentation and Extended Properties checkbox when configuring the project.
Long Timeout (x125029, x125045)
Anomaly
First identified in RSLogix 5000 20.x
When a PowerFlex 755 drive loses power during a firmware supervisor update, it can take over 10 minutes for RSLogix 5000 software to report the time out.
Once the connection to the powered-up PowerFlex 755 drive has been restored, the firmware supervisor will then successfully update the drive's firmware.
MCS Instruction (Lgx00133646, Lgx00133127)
Catalog Numbers
- 1756 GuardLogix L7
- 5370 CompactLogix L1 (1769-L18ERM-BB1B only)
- 5370 CompactLogix L2 (1769-L27ERM-QBFC1B only)
- 5370 CompactLogix L3 (1769-L30ERM, 1769-L33ERM, 1769-L36ERM only)
In the Logix Designer application, version 21, stopping coordinated motion by using a Motion Coordinated Stop (MCS) All instruction could take longer than
expected if the following conditions existed:
• The MCS All instruction is executed when the coordinate motion instruction is accelerating, decelerating, or blending with another instruction.
• The duration of the acceleration or deceleration is very short, for example, 10 coarse update periods or fewer.
• The configured maximum deceleration of any axis in the coordinate system is significantly lower, for example, 50% or less, than programmed maximum
deceleration of the MCS instruction.
S-curve Function Executes with Uninitialized Values
Corrected as of:
Known Anomaly First Identified as of:
When you perform a Partial Import Online (PIO) of a function block routine that contains S-curve function blocks across Logix platforms, set the Initialize bit in
the backing tag control structure of all S-curve instructions. This configuration causes the S-curve instructions to reinitialize themselves.
Failure to set the Initialize bit in the backing tag control structure of all S-curve instructions, can cause the S-curve function block to execute with uninitialized
values.
Functional Changes
This release has the following functional changes from the previous release.
Soft Overtravel Recovery Changes

Software Enhancement
Changes have been made to make recovery from a Soft Overtravel (SOT) condition on an Axis-Cip-Drive easier.
A SOT fault is currently defined such that the following conditions cause the fault:
The commanded position is on or beyond the SOT position.
The commanded motion is in the direction of the overtravel.
Complete the following tasks to recover from the SOT fault:
1. Reset the SOT fault.
2. If the drive is disabled, enable it.
3. Command motion in the opposite direction of the SOT position.
These conditions occur as a result of this anomaly correction:
The SOT fault will not immediately recur if the drive is enabled outside of the SOT position range.
No SOT exceptions will be generated when the axis is in the Stopped state.
1747-AENTR
The 1747-AENTR adapter supports up to 30 modules (in slots 1 through 30) and up to 3 chassis. Each SLC rack module is allowed one exclusive owner
connection, up to 5 input only connections, and up to 5 listen only connections. The AENTR adapter supports a maximum of 96 class 1 connections. Rack
connections are not supported. Up to 8 concurrent class 3 connections are supported for connected explicit messaging.
FBD input and output references show base tag name:
In the Function Block Editor, if an Input Reference (IREF) or an Output Reference (OREF) is an alias tag, then the base tag name can now also be shown, in
much the same way as base tags are shown in other Logix Designer programming language editors.
HMI Connectivity Performance Improvements
HMI communication drivers can now perform symbolic reads of the data table, which enables better performance to HMIs using published interfaces to Logix
Controllers. Refer to the Logix5000 Data Access Programming Manual, publication no. 1756-PM020 for more information.

Importing a UDT with an updated member list
Studio 5000 Logix Designer version 21.00
Importing a User Defined Data Type (UDT) with an updated member list can change instruction tag references for existing or imported logic. In the Import
Configuration dialog box, an icon appears next to each affected UDT.
Refer to the 1756-PM019 Logix 5000 Controllers Import/Export Project Components Programming Manual and the Logix Designer online help for more
information.

Motion Axis Output Cam Expansion
The Motion Axis Output Cam (MAOC) instruction now supports additional devices for scheduling. Up to 16 scheduled outputs are now supported.
RSNetWorx can be accessed directly from the Controller Organizer
Logix Designer application now provides the ability to launch RSNetWorx and to schedule a network from the Controller Organizer. While you can still do this
from the Module Properties dialog box, it is now possible to do this from the context menu for a bridge or scanner module for ControlNet, Ethernet, or
DeviceNet.

Application Notes
This release has the following application notes.
Application Notes RSLinx Software v21
Logix Designer 21.x
Data access control compatibility with RSLinx software
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 (https://rockwellautomation.custhelp.com/app/answers/list).
Configuring the Ethernet port on a CompactLogix5532E controller
You are sometimes prevented from configuring the Ethernet Port of a CompactLogix5532E controller (catalog number 1769-L32E) via Channel 0 using
RSLinx software. To work around the anomaly, use the Logix Designer application to configure the port (if the 1769-L32E controller is at revision 13) or use
the BootP utility (which is enabled for a 1769-L32E controller at revision 1).
RSLinx Classic software Professional activation
Beginning with RSLinx Classic software version 2.31.00, the Logix Designer application Professional activation will also enable the RSLinx Classic
Professional (RSLinx Classic OEM with version 16 and higher) version features. Only one professional activation is required for both products. The Logix
Designer application Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic Professional (RSLinx
Classic OEM with version 16 and higher).
Configuring drivers for the 1756-ENET, 1756-ENBT, and 1756-EWEB modules
You configure a driver for communicating from the workstation through the 1756-ENET, 1756-ENBT, or 1756-EWEB module by selecting Configure Drivers
from the RSLinx Communications menu. In the dialog box, select Ethernet devices in the list of available driver types and click the Add New button.
If needed, in the Station Mappings, click Add New to add a new mapping line.
Enter the IP address of the Ethernet module in the Host Name field. If your network has host name resolution capability, you can use the host name
instead of the IP address
You can put up to 63 devices in the configuration of a single Ethernet devices driver.
If you are using RSLinx software version 2.40 or later, you can use the EtherNet/IP driver. This driver will automatically browse for all EtherNet/IP-capable
devices on the local or configured remote subnet. See RSLinx Help for information on this driver. Note that 1756-ENET/A and 1756-ENET/B modules will not
respond to the browse commands. You must use a different driver for these modules.
Configuring DF1 drivers
For DF1 point-to-point communications, choose RS232 DF1 Devices from the list of available drivers in RSLinx software. Then choose Logix5550 Serial
Port for DeviceType. Rockwell Automation recommends that you do not use the DF1 Polling Master Driver or the DF1 Slave Driver with the Logix Designer
application. You may be able to download successfully, but there are anomalies accessing information from I/O modules.
Offline tag and UDT Changes causing RSLinx software to halt communication
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.
Third-party software with Logix Designer application
Data access control compatibility with third-party software
Some third-party data servers use un-tested data access methods not published in the Logix5000 Data Access manual. To assure controller integrity and
overall system performance and reliably, Version 18 of RSLogix 5000 software only supported documented published methods for writes. Starting in Version
21 of the Logix Designer application, Logix controllers will only support published communications methods for both reads and writes. As a result, some third
party data access packages may need to re-write or re-design their drivers to use a published communications method. Please see Rockwell Automation
knowledgebase technical note 67071.

Application Notes v21
Logix Designer 21.x
The following information is provided to help you better understand the behavior of the Logix Designer in particular applications or under certain
circumstances.
Product Resiliency Improvement
This release includes enhancements intended to improve product resiliency to potentially disruptive activities. These enhancements have been verified to
not affect prodcut safety, performance, expected life, configuration, or operation of the product. Rockwell Automation advises customers to follow good
Industrial Control System (ICS) security practices that include regular product updates. To ensure authenticity, obtain product updates and new releases
directly from Rockwell Automation. Product resiliency includes, but is not limited to, security topics related to tamper prevention and detection, intellectual
property management and source protection, and user authentication and authorization.
Offline interactions between minor versions
Starting with version 21.03, ACD projects converted to version 21.03 and later cannot be opened in prior versions.
Onlne interactions between controller and application
Starting with version 21.03,
Source protected components exported from v21.03 or later cannot be imported by version 21.00.
Logix Designer application version 21.03 cannot go online with a controller that was downloaded by version 21.00. However, Logix Designer
application is able to upload a project from version v21.00, and convert the project to v21.03 or later. The project then needs to be downloaded to the
controller in order to go online with v21.03 or later.
Projects downloaded from v21.03 or later cannot be uploaded by Logix Designer application version 21.00, and version 21.00 cannot go online with a
controller that was downloaded by version 21.03.
Support of minor versions
The Logix Designer application only supports the installation of a single minor release of the application on a computer. Therefore, version 21.03 or later
versions of the application CANNOT run on the same computer as Logix Designer application version 21.00.
In order to support a system that runs version 21.03 and version 21.00, leverage the use of separate computers or use virtualization.
Required to re-register EDS files after upgrading to version 20 or version 21 of the application
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.
Resources cannot be found in the Online Books section of the Start Page
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.
Application crashes after importing the 1734-IB8 module
If you import the 1734-IB8 module into version 15 and later of the application, the application crashes. The workaround is to not import the 1734-IB8 module
into the application. (x122918)
OpenRSLogix5000 command generates an error when trying to select Routine name
When you select a routine using the OpenRSLogix5000 command in FactoryTalk View, an error displays that tells you that RSLogix 5000 is not installed. To
fix this issue, contact Technical Support to obtain a new revision directory dll.
Opening or creating data types causes the application to crash with older version of FTA
If FactoryTalk Activation version 4.0 or earlier is installed on your computer, opening or creating data types from the Controller Organizer causes the Logix
Designer application to crash. To prevent this from happening, use FactoryTalk Activation version 4.1 with Logix Designer application version 21.
Download Project Documentation and Extended Properties
Your Logix Designer application project will not download in the following conditions:
The project is configured such that the Download Project Documentation and Extended Properties check box is cleared.
The controller's programming code uses minimum or maximum extended properties in code elements tag.@MIN or tag.@MAX.
To work around this restriction, check the Download Project Documentation and Extended Properties check box when configuring the project.
Download duration is slow for certain projects
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.
IMPORTANT: Be aware that a restriction applies to clearing the Download Project Documentation and Extended Properties check box in a multi-workstation
development application. (x135928)
Fatal error occur when attempt to go online with the controller
A false time stamp in the controller caused a fatal error to occur when you attempt to go online with the controller. Additionally, the application is not
processing dates that are out of range when attempting to convert them to string format, which causes the application to crash.
Use the following workaround to correct the controller's time stamp.
1. Open the project ACD file.
2. Select something other than the top node in the Controller Organizer. For example, click Unscheduled Programs.
3. Go online with the controller.
4. Open the Controller Properties Date/Time tab. The Date and Time will show as ??.
5. Click Set Date, Time and Zone from Workstation.
Use the following workaround to correct the out of range dates.
1. Perform the workaround for the controller's time stamp first (see above).
It is critical to get the controller's time fixed. Otherwise, any new faults that are generated will also have false time stamps and will cause the controller to
crash.
2. From the Communication menu, choose Clear Faults (if any).
This will clear any major faults that exist. DO NOT attempt to do this from the Major Faults tab of the Controller Properties dialog box.
3. Purge all existing minor faults by generating new ones so that the older false times faults are dropped.
DO NOT attempt to clear minor faults from the Minor Faults tab of the Controller Properties dialog box.
4. To create minor faults, add a new rung online to an existing running routine.
5. Test edits on the new rung to generate several minor faults.
6. Untest edits.
7. Go to the Controller Properties dial box - Minor Faults tab and clear the minor faults.
At this point, the controller's time stamp should be corrected and all faults that captured false time stamps should be cleared or purged.
Note that there is also the option to remove the batteries and power cycle the controllers. This will likely reset the controller's time stamp back to Jan. 1,
1998. This solution requires you to take the controller offline.
Rockwell Automation suggests that you investigate how the controller's time is getting a false value so that the problem does not repeat itself. (x135741)
Indirect addressing within Add-On Instruction logic
If your project uses indirect addressing in an Add-On Instruction, you need to be aware of two compatibility items when using RSLogix 5000 software version
20.01 and Logix5000 controller firmware revision 20.012.
First, you should consider RSLogix 5000 software version 20.01 and Logix5000 controller firmware revision 20.012 to be lock stepped. This means that you
should not use the following:
RSLogix 5000 software version 20.00 with Logix5000 controller firmware revision 20.012. If you use this combination and an index out of range error is
found, the controller will experience a major recoverable fault, which will be displayed as an unknown fault type.
RSLogix 5000 software version 20.01 with Logix5000 controller firmware revision 20.011.
You should also be aware that the signature for the safety Add-On Instructions will change when the project is downloaded to a controller. On
download, you will receive a warning indicating that the Add-On Instructions needs to be revalidated.
For further information, please see Rockwell Automation Knowledgebase Tech Note #481124).
EvRSI replaced by FactoryTalk Activation Manager
Beginning with RSLogix 5000 software version 20, EvRSI activation has been replaced by the FactoryTalk Activation Manager utility. EvRSI activation will not
be able to activate the Logix Designer application. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell
Automation Services & Support for information on migrating your activations to FactoryTalk Activation.
1769-L2y controllers cannot be properly configured
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.
Out-of-Box CIP Axis Position Loop Gain values adjusted with Load Observer
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.
Time Synchronization replaces CST Time Mastership
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 will
have 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.
Attribute Value not Settable reported using AutoFLASH from Logix firmware revision 20 to an earlier revision
When attempting to download a project by using RSLogix 5000 software version 19 or earlier, if the controller firmware is at revision 20 or later and the
controller is in Remote Run mode, then the version 19 software will not be able to change the controller mode in order to AutoFLASH the controller with
revision 19 firmware. In this case, the controller mode must be changed either by using the keyswitch or by using version 20 or later of the application.
(x123924)
CIP Generic writes to controller objects that originate from another controller failing
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.
Security permissions changed for program creation
In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to
create an unscheduled program, you need permission for the Program: Create action. To create a program scheduled in a task, however, you now need
permission for both the Program: Create and the Task: Modify Properties actions. To create a program scheduled in the Power-Up Handler or Controller
Fault Handler, you now need permission for both the Program: Create and the Controller: Modify Properties actions. (x77816, x77817)
Testing SFC online edits no longer always requires chart to reset
With RSLogix 5000 software version 17 and earlier, when performing online editing operations in a Sequential Function Chart (SFC), switching the executing
logic from the original programming to the test edits version (or vice versa) resets the chart to the initial step and resets all stored actions. Beginning with
version 18.00 of RSLogix 5000 software, many SFC online edits no longer result in this reset. In general, only edits that alter the logic structure of the chart
will require the SFC routine to be reset.
In cases when a reset is required, you can force the transition with the initial step to false, wait for the routine to execute to the initial step, and then perform
the test/un-test operation followed by removal of the force. Also, you can leverage the SFC Reset (SFR) instruction to reposition the chart back to the
desired step. (x36331, x43482)
Cannot create, view, or edit modules based on Classic Profile after McAfee QuickClean
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. (x81691)
L5X file list not filtered on Windows 7 operating system
When performing a Partial Import online, the list of files displayed on the Import dialog box is filtered to show only files of the selected component type (for
example, program, routine, data type, equipment phase). This filtering is not supported by the Windows 7 operating system. The Import dialog box will
therefore show all .L5X format files when running the Logix Designer application on a Windows 7 operating system. The icon and ToolTip for the component
file will identify the file type. (x105789, x112515, x113267)
Adobe Reader error selecting Online Books from the Tools menu
After installing RSLogix 5000 software version 19, you may see the Tools>Online Books menu item. If this menu item is selected, Adobe Reader will report
that "This file cannot be found." This error occurs when using version 19 or later of the application if RSLogix 5000 software version 18 had also been
installed on the same personal computer.
The Online Books installed with version 18 software were accessed by using the Custom Tools Menu (Tools>Online Books). The Online Books installed with
version 19 and later access the Online Books by using the Start Page Resource Center. With version 19 installed, the Custom Tools Menu item for version
18 Online Books remains on the Tools menu, but is no longer used. Once RSLogix 5000 software version 19 has been installed, the unused Online Books
Custom Tools Menu item can be manually removed by:
1. Choosing Tools>Custom Tools.
2. In the Custom Tools dialog box, select Online Books.
3. Click Delete.
4. Click OK to apply the change and close the dialog box. (x111895)
Unknown URL attempting to access Online Books or Vendor Sample Projects from Start Page
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 the file C:\Program
Files\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf or C:\Program Files (x86)\Rockwell Software\RSLogix
5000\Common\<language>\Docs\top level linking.pdf, and the Vendor Sample Projects can be accessed from links provided in the file C:\RSLogix
5000\Projects\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. (x89165)
Help from 32-bit .hlp files is not displayed
The Windows Help (WinHlp32.exe) program is used to display Help that is provided in 32-bit .hlp files. The Microsoft Corporation stopped including this 32-
bit Help file viewer in Windows releases beginning with Windows Vista and Windows Server 2008 operating systems. Version 18 and later of the application
display Help in HTML format and does not require this Windows Help program. However, some module profiles may continue to display Help by using 32-bit
.hlp files.
To properly display Help that is provided in 32-bit .hlp files on a Windows Vista or later operating system, you need to install the Windows Help program. This
application is available for download from the Microsoft Download Center. For additional information on downloading and installing the Windows Help
program, refer to the Microsoft Knowledgebase article I cannot open Help files that require the Windows Help (WinHlp32.exe).
Start Pages will not work if version 16.00 is installed after other versions
If version 16.00 of RSLogix 5000 software is installed after version 17.00 or later, Start Pages will fail to load and the message "Server Startup Failure
physicalPath=… " will be displayed. In order to restore Start Page functionality, it is necessary to re-install the version 17.00 or later. Note that this anomaly
will not be observed for version 16.03 and later. (x76424)
Function Block Diagram (FBD) ActiveX Faceplates not compatible with Windows Vista or later
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.
Overflow checking improved for Immediate Operand values
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. (x116816)
First use of Drive profile when Add-On Profiles not installed requires media access
When a drive profile is first accessed, any user other than the user who installed the Drives Add-On Profiles version 4.02 or earlier will need access to the
install media. When accessing the drive profile either by importing a project or by creating a drive in the I/O configuration tree, the user will be prompted with
the following: "Enter an alternate path to a folder containing the installation package „RADrives_PF7.msi ”. ” The user must then provide the path on the
installation media to ...\ENU\MP\RADrives\RADrives_PF7.msi. These Add-On Profiles may have been installed either separately or as part of the
installation of RSLogix 5000 software version 20.01. (x128249)
Manual Tune fields active when Servo disabled
In version 20 or later, the Manual Tune parameters are enabled and editable when online for either the On or Off setting for the Servo parameter of a
CIP_AXIS_DRIVE axis type. (x122492)
Motion instruction error for Stop_All or MGS Active and Pending Motion instruction
A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an
expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or
MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either
an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819,
x85559)
Kinetix 6000 S0 and S1 Safety Drive with Digital Inputs configuration
The hardwired digital inputs on the Kinetix 6000 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.
Event task names can conflict with Microsoft Windows Event names
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.
Versions 18 and later require updates to Custom Motion Database
If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you will 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.
Version of Application Motion Database Revision
21.03 / 21.00 9.8.0 [ Motion.mdb format ]
20.00 8.9.0 [ Motion.mdb format ]
18.02 / 18.01 / 18.00 6.9.0 [ Motion.mdb format ]
17.01 / 17.00 5.3.0 [ *Motion.md format ]
16.04 / 16.03 / 16.00 4.2.0 [ *Motion.md format ]
15.03 / 15.02 / 15.01 / 15.00 3.24.0 [ *Motion.md format ]
14.01 / 14.00 3.12.0 [ *Motion.md format ]
13.04 / 13.03 / 13.02 / 13.01 / 13.00 3.12.0 [ *Motion.md format ]
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 3.3.0 [ *Motion.md format ]
12.01 / 12.00
Error sometimes displayed when attempting to print to Adobe PDF
When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from the Logix Designer
application sometimes result in a dialog box being displayed with the message "Unable to find Adobe PDF resource files. Do you want to run the installer in
repair mode?‟ This issue is documented in the Adobe Knowledgebase article http://helpx.adobe.com/acrobat/kb/error-unable-create-pdf-resource.html,
which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation.
A temporary workaround for printing reports is:
Click No in the dialog box.
In the Print dialog box, change the printer name to some other printer.
Change the printer name back to Adobe PDF.
Click OK to print the document. (x88019)
GSV of PositionFeedback1 attribute reports verification error
In version 20 and later, the PositionFeedback1 is now an integer value. When configuring a GSV of the PositionFeedback1 attribute, a destination tag value
of type DINT is now required. (x123873)
Superimposed motion shifts path
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. (x122482)
Enhancements to Motion Planner may affect motion profiles
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.
Kinematics transformations, additional native geometry support compatibility issues
The Kinematics transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000
software version 16.03) should only be used with version 16.03 or greater of the application. If RSLogix 5000 software version 16.00 is used to upload a
project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported
geometries will be converted to the default Coordinate System Type of Cartesian. The message attribute list error will be displayed during the download
attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision
earlier than revision 16.20. (x75769)
Version 17 installation does not automatically uninstall version 17 Beta versions
For users who have Beta software for version 17 of RSLogix 5000 software installed on their workstation, the version 17 install will not offer to uninstall any
previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software
using Add/Remove Programs.
Using Security with version 16 and CPR 7 FactoryTalk Network Directory Server
This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take
advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory
Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed.
However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you
run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named
UpdateActionsInSchema.exe, can be found in the System\SecuritySchemaUpdate\ directory on the RSLogix 5000 DVD. Note that upon execution, the
utility will provide further instructions.
SFCRESTART attribute removed for GSV/SSV
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.
Migrating to FactoryTalk Security (from RSI Security Server)
Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Services
Platform, which can be found on the DVD. See the FactoryTalk Security installation instructions for further migration information.
Removal of built-in action groups for Security
In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View
Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to
FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups
for the RSI Security Server are:
RSLogix 5000 Full Access
RSLogix 5000 Maintain Project
RSLogix 5000 Go Online
RSLogix 5000 View Project
Tag Modify Properties required to update Configuration dialog boxes with Tag tab
When making changes to a configuration dialog box that contains a Tag tab, you sometimes see an error message indicating that Tag: Modify Properties is
not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)
FactoryTalk Security resource and action groups and FactoryTalk CPR 9 release
The release and update of FactoryTalk Security is independent of the release of the Logix Designer application. FactoryTalk Security in CPR 9 will support
resource groups and action groups. This feature will allow you to conveniently group resources, like ControlLogix controllers, and actions, like Tag Create,
for easier security administration.
Ramp/Soak (RMPS) results appear to be in error
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. (x72583)
Opening pre-version 17 project with Axis and Axis Performance Verification
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.
File import of Axis with MPx motors and Axis Performance Verification
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
LINT time stamp values not shown with FactoryTalk View SE Utility
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.
Controller time object changed in version 16
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. (x72073, x72238)
Use new Clock Update Tool with Logix5000 version 16 and later
A Logix5000 Clock Update Tool is included on the DVD. 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.
Firmware update required for 1734 and 1738 Ethernet Point adapters
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.
Non-Unicode character fonts
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.
CTree errors opening projects with McAfee VirusScan running
With McAfee VirusScan Enterprise Edition 7.1 running, unexpected CTree errors are sometimes seen when project files are opened. This is caused by files
in the temporary folders, AB_xxxx, being modified by the McAfee VirusScan software. McAfee VirusScan software should be configured to ignore the
contents of the AB_xxxx folders.
Starting with RSLogix 5000 software version 14, the directory structure for temporary folders has been modified so that all AB_xxxx folders now reside within
a single folder named RSLogix 5000.Temp located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Server 2008 and
Windows 7 operating systems.
To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the RSLogix5000.Temp
folder. (x51417, x85503)
MOTION_INSTRUCTION data type change
The MOTION_INSTRUCTION data type changed in version 12 and later and the size increased from 12 bytes to 16 bytes. If you have created User-Defined
data types that include members of type MOTION_INSTRUCTION, you will lose tag initial values when you convert your project files from earlier versions.
To work around this anomaly, export your project using a version earlier than version 12 of the application and then import the project in version 12.02 or
later. If you have written logic that relies on the old 12-byte size (for example by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that
your logic is still correct.
The new MOTION_INSTRUCTION data type structure is:
FLAGS DINT
EN BOOL
DN BOOL
ER BOOL
PC BOOL
IP BOOL
AC BOOL
ACCEL BOOL
DECEL BOOL
ERR INT
STATUS SINT
STATE SINT
SEGMENTDINT
EXERR SINT
Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393)
Extra digit of precision shown for REAL data type
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)
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
Format: Equivalent:
+infinite 1.$
Real
- infinite -1.$
+NAN 1.#QNAN
-NAN -1.#QNAN
-indefinite -1.#IND
+infinite 1.#INF000e+000
Exponential
- infinite -1.#INF000e+000
+NAN 1.#QNAN00e+000
-NAN -1.#QNAN00e+000
-indefinite -1.#IND0000e+000
Application appears to lock up when RSMACC connection broken
If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre (RSMACC) 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 (RSMACC) 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. (x36127)
Save sometimes results in large project .ACD file
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. However, if you contact
Rockwell Automation Services & Support and provide a copy of your project file, this could help the Logix Designer application development team to locate
the source of the compression failure.
Activation error running multiple versions simultaneously
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.
Default project directory
Be careful when performing operations with project files that depend on the default project directory. The Windows operating system controls and retains the
default directory for the Open, Save As, and New Controller dialog boxes. Be sure to check that the folder selected is the one you wish to use when
performing these operations to avoid mistakenly overwriting your project files. The Project Directory setting in the Tools Options dialog box is normally used
unless you navigate to a different directory within the Open, Save As, or New Controller dialog boxes. (x28475, x27886)
FBD routine localized feedback wiring errors
In releases earlier than version 10.00, if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner) you could
download the project to a controller but sometimes encounter an error when uploading the project. This anomaly was caused by selecting multiple localized
feedback wires in the outside feedback loop. In this release, this condition will be detected as a verification error in the routine. To correct this anomaly,
select a feedback wire in the inner loop to be the localized feedback wire that is not also in the outer loop. (x28963, x27712)
FBD routine order of execution for unwired blocks
If you have a Function Block Diagram routine with function blocks that are not wired together, the execution order is not deterministic. Operations such as
Verify Routine or Export/Import sometimes change the execution order unexpectedly for unwired blocks. To define the execution order, you must wire function
blocks together. See the Function Block Attributes Order of Execution topic in the Help or the Logix5000 Process Control Drives Instructions Reference
Manual, publication no. 1756-RM006 for more information. (x28703, x28681)
Describing a full circle using the MCCM instruction
In order to describe a full circle in a system with 2 axes in a coordinate system, the Direction flag in the MCCM instruction should be programmed using a
code of 2 (CWF - Clockwise Full) or 3 (CCWF - Counterclockwise Full). Due to internal round-off in the floating point calculations, using a Direction flag of 0
(CW) or 1 (CCW ) with the start and end point being equal (or nearly equal) sometimes results in a small arc of nearly 0 degrees, instead of a full circle of
nearly 360 degrees. (x56812)
Motion module Servo Update Period changed
The Servo Update Period for the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed from 200 microseconds to 250 microseconds. The
servo update period is displayed on the Module Properties dialog box Associated Axes tab. This change in the Servo Update Period will have no effect on
the behavior of existing motion control applications or on the overall performance of the motion control system. (x28647)
Motion Group Fault no longer produces Major Fault in Program mode
In version 12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in program mode but
will produce a Major Fault if the controller is in Run or Remote Run mode. In versions earlier than version 12.01, the motion group could produce a major
fault while the controller was in Program or Remote program mode. For example, a store to nonvolatile memory interrupts the execution of the motion
planner, which produces a fault. (x36957)
Phase Loss Fault-action for AM versus IAM on Kinetix 2000 & 6000 drives
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. (x71448, x71717)
Motion Axis Fault reset MAFR timing changed on Kinetix drives
The Fault Reset timing for Kinetix based SERCOS Drives has changed in Drive firmware revision 1.85. The change accommodates new checks for reset of
the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing
changes observed were 20ms in version 13 associated drive firmware. Now up to 400ms, in RSLogix 5000 software version 15 and later, associated drive
firmware for Motion Fault Reset MAFR instruction average timing changes can be observed to complete for clearing the above listed faults. For more detail
see also Kinetix Drive Firmware Release Notes. (x55240)
ControlFLASH update of Rockwell Automation SERCOS Drives via SERCOS Ring
Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to Rockwell
Automation SERCOS drives. In version 15, support was added to allow direct firmware update of the Rockwell Automation SERCOS drives via
ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos
will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating.
ControlFLASH of the drives on the Ring must be done one drive node at a time.
Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the Rockwell Automation SERCOS Drives to support
ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the Rockwell Automation Kinetix Sercos drives must have
revision 1.85 or higher, and the Rockwell Automation Ultra SERCOS drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42
or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later.
(x51766)
Updating controller firmware in a DH485 network
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. (x28491)
Online disconnection after non-volatile store or load operation
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.
I/O module list appears empty
If the list of modules appears empty in the Select Module Type dialog box when you attempt to create a new module, there could be an anomaly with system
DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680,
x06823)
DLL Name Compatible Versions
Comcat.dll 4.71 5.0
Ole32.dll 4.0 4.71 or

later
Configuring CRC error detection
The Logix Designer application is configured to use BCC error detection by default when using DF1 serial port communication. CRC error detection can be
configured instead of BCC by following these two steps.
CRC Error Detection must be selected on the Controller Properties dialog box System Protocol tab.
The RSLinx DF1 Communications Device Driver must be Auto-Configured so that the driver's Error Checking will be set to CRC to match the Logix5000
controller. The process is simplified if non-DF1 communications is used to select CRC Error Detection in the Logix5000 controller.
To change the error detection:
1. Open a project and establish online communications using Ethernet, ControlNet, or DF1 communications to the target Logix5000 controller.
2. Open the Controller Properties dialog box and select the System Protocol tab.
3. Under Error Detection, enable the CRC radio button and select Apply.
If you are using DF1 communications, there will be a short delay and then the information dialog box will display the error: "Failed to modify the DF1 Protocol
configuration. Communications timed out.‟ This is expected and normal for this operation.
4. Click OK to acknowledge the error.
The other protocols will not display the error.
5. Start RSLinx and select the Communications menu.
6. Select Configure Drivers.
7. Select Configure for the desired DF1 driver, such as AB_DF1-1.
8. Click the Auto-Configure button and the text following the list box Error Checking will change from BCC to CRC.
9. Click OK to close the dialog box and reduce RSLinx to an icon.
10. If you are using DF1 communications, in the Logix Designer application, select Go Online to re-establish online communications.
This DF1 driver will now communicate only with Logix5000 controllers that are set up to use CRC Error Detection.
Fatal error handling
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 14.00, the Fatal Error information will be 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. The new file will be large. If it must be sent to Rockwell Automation Services & Support,
it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). if it is not needed, the RSLogix 5000
Fatal Error.Dmp file can also be deleted.
Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell
Automation\RSLogix 5000\Logs for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or in C:\Documents and Settings\All
Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000 operating systems. For
RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\
<username>\Local Settings\Temp (for all operating systems).
Destination operands for GSV commands
Caution should be used in selecting the proper data type for the destination operand of a GSV instruction. Use of mismatched operand data types
sometimes result in unexpected results. Refer to the Instruction Set reference manual or the Help instructions to determine the proper data types.
Downloading controllers that use more memory than available
If a controller utilizing more memory than is available in the physical controller is downloaded, you will receive an appropriate error message. However, in
some instances, the serial port will become inoperative. It is recommended that in this case, the controller memory be cleared (power turned off and the
battery removed).
Multiple owners or listeners of 1756 analog modules
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.
Configuring the DHRIO module
When online with the controller, if the DHRIO module is configured for DH+ only, this module continuously displays Faulted as its Status on the Module
Properties dialog box, even when normal communications exist. To avoid this erroneous fault condition, include the DHRIO module in the I/O configuration
only if the application uses the Remote I/O features.
If the Logix5000 controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx software version 2.20 or later, or the
ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.
User disk memory utilization
If a Logix Designer application session is terminated abnormally, some large temporary files could be left on the hard drive. You should periodically delete
old folders named AB_xxxx from your temporary directory. Smaller files with .SEM and .WRK suffixes could be left in your project directory after an abnormal
termination and can also be deleted.
AB_xxxx folders reside within a single folder named "RSLogix 5000.Temp‟ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp
for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for
Windows XP, Windows Server 2003, and Windows 2000 operating systems).

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

Studio Logix Designer 24.001 Release Notes

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Studio Logix Designer 24.001 Release Notes

Transféré par

Droits d'auteur :

Formats disponibles

Release Notes

Characteristic Minimum Required Recommended

Processor Pentium 4 Intel Core i5

Graphics Device DirectX 9, with WDDM 1.0 DirectX 9, with WDDM 1.0

Comcat.dll 4.71 5.0

Ole32.dll 4.0 4.71 or

Vous aimerez peut-être aussi