Professional Documents
Culture Documents
Relnote PDF
Relnote PDF
Relnote PDF
A Logix5000 system (ControlLogix, GuardLogix, CompactLogix, Compact GuardLogix, and SoftLogix) baseline release consists of a set
of compatible hardware, firmware, and software components that provide system functionality. These release notes describe new
functionality, concerns, and issues associated with the components that are included in this Logix5000 system release. Read this
document carefully to avoid potential hazardous conditions. If you need more information about a particular issue or have other
questions, contact your local Rockwell Automation representative.
We recommend that you also review the information concerning any version of RSLogix 5000 software that has occurred between the
version you are currently using and version 20 of RSLogix 5000 software, before you update RSLogix 5000 software. The RSLogix
5000 Release History can be accessed during RSLogix 5000 software installation. At the Rockwell Software Common Setup installation
Step 1, select RSLogix 5000 and then click View Release Notes for Selected Product. (Refer to the Installation Notes section of this
document for additional details on installing the RSLogix 5000 software.)
RSLogix 5000 Enterprise Professional Full Edition Standard / Standard Edition Lite Edition Mini Edition Service Edition**
Series Bundle* Edition Network Edition
Advanced Process Control Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately Upload/Download
instructions – Runtime license and View Only
for one controller
(9324-RLDAPCCLENE)
Highly integrated Motion Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Upload/Download
and View Only
Graphical Trending Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported
DriveExecutive Lite Included Included Included Included Available Separately Available Separately Available Separately
(9303-4DTE01ENE)
FBD PIDE Autotune (requires Included Included Available Separately Available Separately Available Separately Available Separately Available Separately
FBD option)
(9323-ATUNEENE)
FuzzyDesigner Available as a Available as a Available as a Available as a Available as a Available as a N/A
(9324-RLDFZYENE) Separate Application Separate Application Separate Application Separate Application Separate Application Separate Application
Redundancy Included Included Included Included N/A N/A Included
RSLogix Emulate 5000 Included Available Separately Available Separately Available Separately N/A N/A Available Separately
(9310-WED200ENE)
Passwords / Security
Routine Source Protection Included Included Included Included Included Included Included
Security Server Emulator Included Included Included Included Included Included Included
(FTAP Install Required –
include on disk)
FactoryTalk Security Server Included Included Included Included Included Included Included
Support (FTAP Install
Required – included on disk)
System Configuration /
Network / Communications
RSLinx Classic Lite Included Lite Included Lite Included Lite Included Lite Included Lite Included Lite Included
RSLinx Enterprise Included Included Included Included Included Included Included
RSNetWorx for ControlNet, Included Available Separately Included Available Separately Available Separately Available Separately Available Separately
DeviceNet, EtherNet/IP
(9357-CNETL3, 9357-
DNETL3,
9357-ENETL3 individually or
9357-ANETL3 combined)
RSLogix Architect Stand Alone License Activated with Activated with Activated with Available Separately Available Separately Available Separately
(9326-LGXARCHENE) Included RSLogix 5000 RSLogix 5000 RSLogix 5000
Web Download License License License
Required Web Download Web Download Web Download
Required Required Required
Miscellaneous Files & Tools
Electronic manuals (PDF) Included Included Included Included Included Included Included
Start Page Included Included Included Included Included Included Included
ControlFLASH with Firmware Included Included Included Included Included Included Included
ClearKeeper Included Included Included Included Included Included Included
PLC-5/SLC 500 Translation Included Included Included Included Included Included Included
Tool
RSLogix 5000 IEC61131-3 Included Included Included Included Included Included Included
Translation Tool
Tag Data Upload / Download Included Included Included Included Included Included Included
Tool
RSLogix 5000 Project Included Included Included Included Included Included Included
Compare Tool
Tag Custom Data Monitor Included Included Included Included Included Included Included
Tool
DeviceNet Node Included Included Included Included Included Included Included
Commissioning Tool
Logix5000 Task Monitor Included Included Included Included Included Included Included
Logix5000 Clock Update Tool Included Included Included Included Included Included Included
Logix5000 Data Preserve Included Included Included Included Included Included Included
Tool
CGCM PID Calculator Included Included Included Included Included Included Included
RSLogix 5000 DeviceNet Tag Included Included Included Included Included Included Included
Generator
Safety Reaction Time Tool Included Included Included Included Included Included Included
GuardLogix Safety Estimator Included Included Included Included Included Included Included
FactoryTalk View SE Demo Included Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately
(50 Tags / 2 Hour Limit)
RSLogix 5000 Upgrades: Use Step Forward (http://www.ab.com/stepforward/)
* RSLogix 5000 software now ships with only concurrent licensing. Software is designed to use highest functionality license first. For example, if Standard, Full and Professional
licenses are availableon the FactoryTalk Activation server, RSLogix 5000 software will use the highest functionality license first (that is, Professional).
** Service Edition requires controller firmware at revision 12 or later.
*** The Structured Text editor option is required to program SFC Actions and SFC Transitions using the Structured Text language.
Hardware Requirements
The personal computer must meet these minimum requirements. Using a computer meeting or exceeding the recommended
characteristics will improve performance.
Software Requirements
Operating system and service pack compatibility:
This version of RSLogix 5000 software has been tested on the following operating systems:
Microsoft Windows 7 Professional (64-bit) with Service Pack 1
Microsoft Windows 7 Home Premium (64-bit) with Service Pack 1
Microsoft Windows 7 Home Premium (32-bit) with Service Pack 1
Microsoft Windows Vista Business (32-bit) with Service Pack 2
Microsoft Windows XP Professional with Service Pack 3
Microsoft Windows Server 2008 R2 Standard Edition with Service Pack 1
Microsoft Windows Server 2008 Standard Edition with Service Pack 2
Microsoft Windows Server 2003 R2 Standard Edition with Service Pack 2
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:
Microsoft Windows 7
Microsoft Windows Vista
Microsoft Windows XP (Service Pack 3 or higher)
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008
Microsoft Windows Server 2003
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.
RSLogix 5000 software versions earlier than version 19 are not supported on Microsoft Windows 7 operating systems at this time
and have not been tested on those operating systems.
RSLogix 5000 software versions earlier than version 17 are not supported on Microsoft Windows Vista operating systems at this
time and have not been tested on those operating systems. RSLogix 5000 software version 17 is supported on a Microsoft
Windows Vista operating system only when User Account Control (UAC) is turned off.
Running RSLogix 5000 software in conjunction with Fast-User Switching is not supported. Running RSLogix 5000 software in Safe
mode is not supported. Running RSLogix 5000 software via Remote Desktop is not supported.
While RSLogix 5000 software continues to extend its functionality with each new release, the physical controllers that it supports will
vary. New controllers are added, and in some cases support for existing controllers may be removed. While a specific controller may
not be supported by the current release, the side-by-side installation of multiple versions of RSLogix 5000 software will in most cases
provide a means to support the older hardware. If you decide to migrate from one controller to another, a project created for one
controller can be easily converted to another controller via the Controller Properties configuration dialog box within RSLogix 5000
software.
Additionally, if you open a project that is configured for a controller that is no longer supported and the older version of RSLogix 5000
software is not installed, RSLogix 5000 software version 13 and later will provide an appropriate warning and will automatically provide
the option to convert the project to one of the controllers supported by the release.
The following table provides a breakdown of the various Logix5000 controllers and the initial or minimum version of RSLogix 5000
software that is required and, in case the controller is no longer supported, the last or maximum version of RSLogix 5000 software that
provided support for the controller.
Before performing this upgrade, note that Logix5000 controllers and ControlLogix Motion modules in your system must contain a
revision of firmware that is compatible with this version of RSLogix 5000 software. However, earlier versions of network and I/O
modules can operate in your system with the new controller firmware contained in this release. Additionally, other software tools such
as RSNetWorx for ControlNet and RSLinx Classic software have been tested to be sure of compatibility with this version of software.
Because of this, we recommend that you use the most current versions of these tools. The following tables list the most recent versions
of software and firmware that have been tested and validated together.
Software
18.02 / 18.01 / 18.00 2.10.02.24 2.21.00.1180 2.56.00.13 5.21.00 10.00.00 10.00.00 10.00.00
(CPR 9 SR 2) (CPR 9 SR 2) (CPR 9 SR 2) (CPR 9 SR 2) (Build 26) (Build 26) (Build 26)
(CPR 9 SR 2) (CPR 9 SR 2) (CPR 9 SR 2)
Controllers
ControlLogix L61 – Series A & B, L61 – Series A & B, L61 – Series A & B, L61 – Series A & B, L55 – Series A, L55 – Series A,
1756-L1, -L53, -L55, Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.22 Version 15.03
-L61, -L62, -L63, L62 – Series A & B, L62 – Series A & B, L62 – Series A & B, L62 – Series A & B, L61 – Series A & B, L61 – Series A & B,
-L64, -L65, Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.22 Version 15.03
-L63XT, L63 – Series A & B, L63 – Series A & B, L63 – Series A & B, L63 – Series A & B, L62 – Series A & B, L62 – Series A & B,
-L60M03SE Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.22 Version 15.03
L64 – Series B, L64 – Series B, L64 – Series B, L64 – Series B, L63 – Series A & B, L63 – Series A & B,
Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.22 Version 15.03
L65 – Series B, L65 – Series B, L65 – Series B, L65 – Series B, L64 – Series B, L60M03SE – Series A,
Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.22 Version 15.03
L63XT – Series B, L60M03SE – Series A, L60M03SE – Series A,
Version 20.12 Version 17.04 Version 16.22
ControlLogix, L71 – Series B, L72 – Series A, L73 – Series A, Not Applicable Not Applicable Not Applicable
-L71,-L72, -L73, -L74, Version 20.12 Version 19.13 Version 18.11
-L75, L72 – Series A & B, L73 – Series A, L75 – Series A,
-L73XT Version 20.12 Version 19.13 Version 18.11
L73 – Series A & B, L74 – Series A,
Version 20.12 Version 19.13
L74 – Series A & B, L75 – Series A,
Version 20.12 Version 19.13
L75 – Series A & B,
Version 20.12
L73XT – Series B,
Version 20.12
GuardLogix L61S – Series B, L61S – Series B, L61S – Series B, L61S – Series B, L61S – Series B, Not Applicable
1756-L61S, -L62S, Version 20.12 Version 19.11 Version 18.11 Version 17.08 Version 16.22
-L63S L62S – Series B, L62S – Series B, L62S – Series B, L62S – Series B, L62S – Series B,
Version 20.12 Version 19.11 Version 18.11 Version 17.08 Version 16.22
L63S – Series B, L63S – Series B, L63S – Series B, L63S – Series B,
Version 20.12 Version 19.11 Version 18.11 Version 17.08
GuardLogix L71S – Series B, Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable
-L71S,-L72S,-L73S, Version 20.12
-L73SXT L72S – Series B,
Version 20.12
L73S – Series B,
Version 20.12
L73SXT – Series B,
Version 20.12
CompactLogix L43 – Series A & B L43 – Series A & B L43 – Series A & B L43 – Series A & B L43 – Series A & B, L43 – Series A,
1768-L43, -L45 Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.24 Version 15.03
L45 – Series A & B L45 – Series A & B L45 – Series A & B L45 – Series A & B L45 – Series A & B,
Version 20.12 Version 19.11 Version 18.11 Version 17.04 Version 16.24 (only
available with V16.03
and later)
Compact GuardLogix L43S – Series A L43S – Series A L43S – Series A Not Applicable Not Applicable Not Applicable
1768-L43S, -L45S Version 20.12 Version 19.11 Version 18.11
L45S – Series A L45S – Series A L45S – Series A
Version 20.12 Version 19.11 Version 18.11
CompactLogix L16ER-BB1B Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable
1769-L16ER-BB1B, – Series A
-L18ER-BB1B, Version 20.12
-L18ERM-BB1B, L18ER-BB1B
-L24ER-QB1B, – Series A
-L24ER-QBFC1B, Version 20.12
-L27ERM-QBFC1B, L18ERM-BB1B
-L30ER, – Series A
-L30ER-NSE, Version 20.12
-L30ERM, L24ER-QB1B
-L33ER, – Series A
-L33ERM, Version 20.12
-L36ERM, L24ER-QBFC1B
– Series A
Version 20.12
L27ERM-QBFC1B
– Series A
Version 20.12
L30ER – Series A
Version 20.12
L30ER-NSE – Series A
Version 20.12
L30ERM – Series A
Version 20.12
L33ER – Series A
Version 20.12
L33ERM – Series A
Version 20.12
L36ERM – Series A
Version 20.12
Communication
Modules
Motion Modules
Kinetix 6500 S0/S1 Version 2.010 Version 2.001 Version 1.011 Not Applicable Not Applicable Not Applicable
CIP-Drive
(2094-EN02D Series)
SERCOS Drives
Kinetix 7000 Version 1.105 Version 1.105 Version 1.105 Version 1.097 Version 1.097 Version 1.085
(2099 Series)
Kinetix 6200 S0/S1 Version 1.045 Version 1.035 Version 1.032 Version 1.003 Not Applicable Not Applicable
(2094-SE02F Series)
Kinetix 6000 Version 1.123 Version 1.116 Version 1.111 Version 1.99 Version 1.95 Version 1.85
(2094 Series)
Kinetix 6000M Version 1.003 Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable
(MDx-SBxx-Q-S
Series)
Kinetix 2000 Version 1.99 Version 1.99 Version 1.98 Version 1.98 Version 1.97 Not Applicable
(2093 Series)
Ultra3000 Version 1.53 Version 1.53 Version 1.53 Version 1.52 Version 1.52 Version 1.50
(2098 Series)
8720MC Series Version 3.85 Version 3.85 Version 3.85 Version 3.85 Version 3.85 Version 3.85
1394C Series Version 1.87 Version 1.87 Version 1.87 Version 1.87 Version 1.85 Version 1.85
Other Products
DriveTools Software Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable Version 3.01
ControlLogix Not Applicable Not Applicable Not Applicable Not Applicable Version 16.5x Version 15.6x
Standard Platform
Redundancy
ControlLogix Not Yet Available Version 19.5x Not Applicable Not Applicable Version 16.8x Not Applicable
Enhanced Platform
Redundancy
* This is a digitally signed revision of firmware. This module supports both signed and unsigned firmware. There may be compatibility issues if you attempt to update from a signed
revision of firmware to an unsigned revision of firmware. Please refer to the release notes for the specific module for details.
Note that most of the modules supported by RSLogix 5000 software use Flash-ROM for the storage of firmware. If you possess a
module that requires a firmware change, the ControlFLASH software tool can be used to perform an update to this Flash-ROM. This
software tool and the firmware images for most of the supported modules are contained on a DVD-ROM shipped with RSLogix 5000
software. Starting with RSLogix 5000 software, version 10.00.00, you can access the ControlFLASH tool from within RSLogix 5000
software (from the Tools menu), or you can automatically update your firmware as part of the project download process.
For additional information and assistance in performing a Flash-ROM update, review the ControlFLASH Firmware Upgrade Kit Quick
Start, publication 1756-QS105.
In addition, Rockwell Automation Services & Support has created a website from which you can download firmware images for Logix
products. Go to http://support.rockwellautomation.com/ControlFLASH/ for a matrix detailing the revisions of firmware that were released
with each of the versions of RSLogix 5000 software, and to download the ControlFLASH firmware kits and release notes. Note that you
will need your RSLogix 5000 serial number to complete the download.
The firmware associated with this standard release version of RSLogix 5000 software does not support redundancy. RSLogix 5000
software versions 8, 11, 13, 15, 16, and 19 support redundancy, but a separate firmware revision for the hardware in the local chassis
is required. The redundancy firmware revisions are released later than the standard revisions are released and are available for
download via the same methods as for standard firmware. Go to http://support.rockwellautomation.com/ControlFLASH/ for a matrix
detailing the revisions of redundancy firmware that were released for each of the versions of RSLogix 5000 software, and to download
the ControlFLASH firmware kits and release notes. Note that you will need your RSLogix 5000 serial number to complete the download.
With version 13 and later, RSLogix 5000 software supports the ability for new I/O configuration profiles to be delivered independent
from the RSLogix 5000 software release. These profiles can be obtained independently and installed on a personal computer with
RSLogix 5000 software to extend the I/O configuration support beyond the capabilities initially supported when RSLogix 5000 software
was released. This capability was initially limited to a single I/O platform but with each new release new I/O platforms are added. If you
are using one of the supported platforms and the configuration profile for a specific product was not included with RSLogix 5000
software, check with the module or device vendor to determine if one is available. Additionally, I/O configuration profiles for modules or
devices from Rockwell Automation are generally provided with RSLogix 5000 software. However, at times a module or device
configuration profile may not be completed in time to make a software release. In these instances, the I/O configuration profiles will be
made available via the Rockwell Automation Services & Support website
http://support.rockwellautomation.com/ControlFLASH/LogixProfiler.asp. The following table provides a listing of RSLogix 5000 software
versions and their respective ability to support the field addition of I/O configuration profiles.
The version of RSLinx Classic software provided with this version of RSLogix 5000 software includes an updated set of electronic data
sheet (EDS) files for Rockwell Automation products. Installing this software ensures that RSLinx Classic software and RSNetWorx
software will be able to work with the new revisions of firmware. These EDS files are also available separately by contacting Rockwell
Automation Services & Support (phone +1 440-646-3434), or via the Internet (http://www.rockwellautomation.com/resources/eds/). You
can install them by using the EDS Hardware Installation Tool, located in the Rockwell Software>RSLinx>Tools folder in the Windows
Start Menu.
Prior to Installation
Keep the following considerations in mind before you install the RSLogix 5000 software:
Be certain that no copies of RSLogix 5000 software are currently running.
Make sure that you have Administrator privileges on the personal computer on which you want to install the software. You will not
be able to complete the installation without these privileges.
If you want to perform online communications, you must install RSLinx Classic software in addition to RSLogix 5000 software.
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 RSLogix 5000 installation.
Refer to the Choosing Your RSLogix 5000 Package section of this document to determine which controllers are supported by
your RSLogix 5000 Enterprise Series bundle.
2. Insert the RSLogix 5000 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.
RSLogix 5000 Enterprise Series software supports multiple versions of the programming software on a single personal computer.
With RSLogix 5000 software version 10 and later, you may install as many of the later major versions as needed plus one version
earlier than version 10 (for example, version 8.02).
Note that RSLogix 5000 software version 20 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. Use the F1 key if you need help.
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 software operating in Service Edition mode, upload/download only, while in Grace Period
mode.
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 software, the software will enter a seven-day activation grace period,
during which you will be able to run the software 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 RSLogix 5000 software.
When the setup utility finishes, an entry for the RSLogix 5000 application program appears in the program list in the Rockwell
Software group.
7. Remove the RSLogix 5000 DVD from the DVD-ROM drive and store it in a safe place.
To start RSLogix 5000 software, from the Start menu, choose All Programs>Rockwell Software>RSLogix 5000 Enterprise
Series>RSLogix 5000 from the menu.
Tip
Remember to use the Help function from within the application if you need help with a specific dialog box or function. Press [F1] or
click the Help button on a dialog box, or select Help from the menu bar.
Follow these steps to uninstall the software when using the default „Start menu‟ on the Windows 7, Windows Vista, Windows XP, or
Windows Server 2008 operating system.
2. From the Programs category, choose Uninstall a program. (for Windows 7, Windows Server 2008 R2)
From the Programs category, choose Uninstall a program. (for Windows Vista, Windows Server 2008 – Control Panel Home)
Double-click Programs and Features. (for Windows Vista, Windows Server 2008 – Classic View)
Double-click Add or Remove Programs. (for Windows XP – Classic View)
Click Add or Remove Programs. (for Windows XP – Category View)
Follow these steps to uninstall the software when using the „Classic Start‟ menu on the Windows XP operating system and later.
2. From the Programs category, choose Uninstall a program. (for Windows Vista, Windows Server 2008 – Control Panel Home)
Double-click Programs and Features. (for Windows Vista, Windows Server 2008 – Classic View)
Double-click Add or Remove Programs. (for Windows XP, Windows Server 2003 – Classic View)
Click Add or Remove Programs. (for Windows XP – Category View)
Follow these steps to uninstall the software when using the default „Start menu‟ on the Windows Server 2003 operating system.
You will be prompted to decide whether you wish to preserve any application settings you have previously configured. Follow the
prompts of the uninstaller, and RSLogix 5000 software will be uninstalled from your computer.
Note that this will uninstall only the RSLogix 5000 application. Other components that were installed with RSLogix 5000 software (such
as Start Page Media, Online Books, or RSLinx) must be uninstalled separately.
Restricted Communications
In RSLogix 5000 software version 20, there is a new field on the Security tab of the Controller Properties dialog box that allows for
communications to the Logix5000 controller to be restricted. By checking “Restrict Communications Except Through Selected Slots”,
some software products including RSLinx software, RSLogix 5000 software, and ControlFLASH software will only be able to
communicate with the controller by communications cards loaded in the selected slots. Communication from the controller to other
devices (such as, remote I/O modules or other controllers) are not impacted by this setting. This setting is useful to ensure that
configuration changes to the controller can only be made through selected slots. When this setting is enabled, these software products
will not be able to communicate with the controller via the USB port or serial port located on the front of the controller. This feature is
available only for the 1756 and 1768 families of controllers. For more information, see the ControlLogix System User Manual,
publication 1756-UM001.
Change Detection
When online with a controller, a 64 bit integer is displayed in the Audit Value text box, located on the Security tab of the Controller
Properties dialog box. The Audit Value is a unique value that is generated when a project is downloaded to the controller or loaded from
removable storage. This value is updated when an event occurs. Some events will always cause an Audit Value change, while others
are selectable based on the settings of the Detection Specification. By inspecting this value, you can quickly determine if the behavior
of a controller has been modified since the last time it was inspected. The Audit Value can be accessed programmatically via the GSV
and MSG instructions, and the Changes to Detect value can be read or written via the GSV, SSV, and MSG instructions. The Change
Detection Audit Value is also exposed as a predefined tag by RSLinx Enterprise software for use in HMI displays or other applications.
Additionally, it is included in Controller Log entries. For more information, see the ControlLogix System User Manual, publication 1756-
UM001.
Finding/Adding Devices to the Logix Tree – Enhancements to the Select Module Type dialog box make it easier to use and find
devices. The Select Module Type dialog box now shows all registered devices. It also includes new string and category filters, a
wild card search, and a favorites list.
Enabling Security for RSLogix 5000 Software – Starting with version 20 of RSLogix 5000 software, security is automatically
enabled when FactoryTalk Services Platform software is installed. Installation of RSSecurity Emulator software and execution of
the SetSecKeys.exe utility are no longer required. Also starting with version 20 of RSLogix 5000, security permissions are obtained
exclusively from the FactoryTalk network directory. Note that RSLogix 5000 software versions 19 and earlier still require installation
of RSSecurity Emulator software and execution of the SetSecKeys.exe utility. RSLogix 5000 software versions 19 and earlier can
obtain security permissions from either the Local or Network directory, as configured when RSSecurity Emulator software is
installed.
Safety Signature Deletion in Run Mode Protection – A new checkbox prevents the Safety Signature from being deleted while
the controller is in Run Mode.
Rotation Order Changed for MCT and MCTP Instructions – For the MCT and MCTP Transformation Motion instructions, the
Orientation operand specifies the rotation vector for Kinematics transformations. In RSLogix 5000 software version 20, the rotation
order has been reversed to apply the order of rotations as first about the X-axis, then about the Y-axis, and then about the Z-axis.
This impacts the initial position of any MCT or MCTP instruction that uses a 2-dimensional or 3-dimensional rotation. A 1-
dimensional rotation is not affected. See also Technical Note #124945.
This revision of Logix5000 controllers may require more memory than earlier revisions. To estimate additional memory requirements for
your application, you can either use the memory estimation tool provided with RSLogix 5000 software or the tables provided in these
release notes.
Before upgrading to this revision, check the amount of unused memory that you have in the controller.
For additional information about controller memory issues refer to the Knowledgebase document G19984 at
http://www.rockwellautomation.com/support/.
To use the memory estimation tool to estimate the amount of controller memory your project requires for I/O, Data, and Logic, convert
the project to the controller revision desired and then use the Estimate tool available on the Memory tab of the Controller Properties
dialog box.
If you do not have the desired version of RSLogix 5000 software, use the following table to estimate the additional memory that your
project may require.
Import/Export Changes
Import/Export Formats – RSLogix 5000 software provides the following five different Import/Export file formats:
Full project exported to an ASCII text file (.L5K)
Full project exported to an Extensible Markup Language (XML) formatted file (.L5X)
Tag definitions and program documentation exported to ASCII text files in a Comma Separated Value (.CSV) format
Tag definitions and program documentation exported to ASCII text files in a Tab Separated Value (.TXT) format
Partial project exported to an Extensible Markup Language (XML) formatted file (.L5X)
Each of these formats is documented in Logix5000 Controllers Import/Export Reference Manual, publication 1756-RM084, which also
describes modifications that can be made for backward compatibility of export format files.
Import/Export Major and Minor Revision – Beginning with the version 9.00 release, the Import/Export version number will be
interpreted as a Major Revision and a Minor Revision (major.minor). Each version of RSLogix 5000 software will export *.L5K files with
specific IE Version numbers. RSLogix 5000 software will import any *.L5K file with the same Major Revision number and the same or
lower Minor Revision number. The Major Revision will be incremented when there is a significant change that affects compatibility with
earlier versions. The Minor Revision will be incremented whenever there is a change in the file format (a new module, an attribute is
added, the set of options for an attribute is changed, etc.). Generally, the Minor Revision will be incremented for each release.
Import or Paste Error Messages – When attempting to import or paste between versions if the IE version is invalid an error message
will be displayed in the results window. If the major or minor revision number is larger than accepted the message „Error Line xxx:
Invalid IE Version number. Cannot import/paste into older version of RSLogix 5000‟ will be displayed. If the major revision number is
smaller than accepted the message „Error Line xxx: Invalid IE Version number. See Release Notes for more detail‟ will be displayed.
Import/Export Format for Structured Text Routines – The Import/Export format for Structured Text routines was changed in version
12. The STX_ROUTINE and END_STX_ROUTINE delimiters were changed to ST_ROUTINE and END_ST_ROUTINE, respectively.
RSLogix software, version 12 or later will continue to recognize the obsolete STX_ROUTINE when importing, but will export using the
new format. Any attempt to Copy/Paste, Drag/Drop, or Import a version 12 or later Structured Text routine into version 11 software will
fail.
Online Editing Views for SFC and ST – With the addition of online editing for SFC and ST in version 13, new LOGIC and
END_LOGIC delimiters were added to identify Original, Pending Edits, and Test Edits views in the export file for the SFC and ST
languages. These new delimiters are not recognized in older versions of RSLogix 5000 software, so version 13 or later generated L5K
files with SFC or ST online edits should not be imported into versions earlier than version 13.
Data Types and Keywords – If you are importing an older version project (earlier than version 11) you may get the error message „An
error occurred while creating DATATYPE xxxx (One or more arguments invalid.)‟ for some user-defined data types. The likely cause of
this error is the use of RSLogix 5000 reserved keywords introduced in version 11 as data type names. Normally, user-defined data
types that use keywords are renamed by appending a numeral. If an undefined data type is nested within another data type, it may be
that the undefined data type uses a reserved keyword name and causes the error. To work around this anomaly, rename any undefined
data types to non-keyword names.
Motion Axis Tags and Axis Object Attributes – In addition to the Import/Export changes described above, there have been many
changes to motion axis tags and axis object attributes that will result in warning messages when importing older version *.L5K files.
These warning messages will be in the format:
Warning: Line ###: An error occurred while setting attribute <name_of_attribute> of tag <name_of_axis_tag> (Couldn‟t be found).
The same type of warning message will be displayed if you import objects that previously accepted NA as values. In this release, the
not applicable values are exported as <NA>.
A few product anomalies discovered in version 20.00 have been addressed in version 20.01. These include the following:
The Embedded Counters module of a 1769-L2y controller cannot be properly configured for Pulse External Direction. Please refer
to the Application Notes section of these release notes for additional details. (x126251)
Safe State Value out does not work for 1794-IE4XOE2, 1794-OE12, and 1794-OE8H modules. (x126967, x126968, x127022)
Module connections for the 1747-AENTR module do not work properly because the EDS file for the 1747-AENTR module profile
should be version 2.1. (x128112)
Many product anomalies have been addressed since version 19. The most significant of these include the following:
AutoFLASH of motion modules doesn‟t work when bridged through USB or DF1. (x45686)
Fatal Error while editing a Function Block Diagram. (x81527)
Security privileges are not refreshed in RSLogix 5000 software when updated using FactoryTalk Administration Console with a
project open. Note that in version 20 of RSLogix 5000 Security privileges are now updated every 5 minutes. (x104480)
A renamed Safety Task will be reconfigured if the task is imported using partial import. (x106091)
Accepting pending edits for a large Structured Text routine clears text from the language editor window. (x107126)
Online editing of a Sequential Function Chart can result in the GDI handle limit being exceeded. (x107906)
Fatal Error copying a tag of type MESSAGE from one instance of RSLogix 5000 software to a second instance of RSLogix 5000
software. (x113029)
CIP Motion position may exceed the configured unwind position. (x113950)
Long delay may be observed when displaying the Tag Browser. (x114018)
Downloading a project with more than 100 produced or consumed connections may result in a Fatal Error. (x115288)
Fatal Error saving project with SFC Action opened. (x116031)
Fatal Error during upload of a project with Structured Text containing line break characters. (x117134)
Fatal Error during download. (x117643)
Long delays may be observed when modifying a tag component description in a tag of a data type which is a deeply nested user-
defined data type. (x120431)
A partially completed Add-On Instruction can be imported. A project containing an invocation of the Add-On Instruction can be
downloaded. Upload can result in a Fatal Error. (x123573)
Issues Related to Compatibility of RSLogix 5000 Software with Windows 7 Operating Systems
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: (x111504)
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)
Issues Related to Compatibility of RSLogix 5000 Software with Windows Vista Operating Systems
There are a number of issues related to compatibility of RSLogix 5000 software with the Windows Vista operating system. The most
significant of these includes the following: (x81660)
Although RSLogix 5000 software versions earlier than version 17 can be installed, they are not supported on Windows Vista
operating systems.
Although RSLogix 5000 software version 18 and later are supported with User Account Control (UAC) turned on, RSLogix 5000
software version 17 is supported only with UAC turned off.
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 Vista setting to „Underline keyboard shortcuts and access keys‟. Access this setting by using
Personalize>Ease of Access>Make the keyboard easier to use>Underline keyboard shortcuts and access keys. (x113166)
The 1784-PCIC(S) driver must be at version 4.06.01 or later. This driver is installed when RSLinx software is installed.
Newly Registered EDS Add-On Profile May Not Always Be Displayed in the Select Module Type Dialog
Box
When a new EDS file is registered from outside RSLogix 5000 software, when RSLogix 5000 software is not running and RSLinx
Classic software is running as an application (as opposed to as a service), then the newly registered device will not be available in the
Select Module Type dialog box. Note that there is no problem with display of the device when registered outside of RSLogix 5000
software, provided that you first exit the RSLogix 5000 application and shut down the RSLinx Classic application. There is also no
problem with display of the device when registered from within the RSLogix 5000 application (such as when using the “Tools>EDS
Hardware Installation Tool” menu). So, if the registered module is not displayed, you can use the “Tools>EDS Hardware Installation
Tool” menu to register the device again. (x124959)
Unable to Open Full Project XML Format File (.L5X) for Project File of Later Version of RSLogix 5000
Software than is Being Executed
When attempting to open a full project xml format file (.L5X), an error may be reported indicating “Controller Revision not supported”.
This will occur when the major revision of the xml format file being opened is later than the revision of RSLogix 5000 software being
executed. For example, when executing RSLogix 5000 software version 19, an attempt to open an xml format file for version 20 will
report the error. However, when executing RSLogix 5000 software version 20, an attempt to open an xml format file for version 19 will
not exhibit the problem. When this error is observed, first switch to the RSLogix 5000 software version for the xml format file, and then
open the file. This problem does not affect L5K or ACD files. (x114197)
Import of a Project to Controller with Expansion I/O May Not Update Logic that References that I/O
If a project for a CompactLogix controller that is no longer supported is imported as a controller that has expansion I/O, any expansion
I/O modules from the original controller are properly moved to the correct expansion slot; however, the references in program logic will
not be correspondingly updated. This does not necessarily result in the program failing to verify. Instead, the logic may now be
referencing the embedded modules for this controller. This is a problem only when opening a L5K or L5X project file. The references
are properly adjusted when opening an ACD file. (x125220)
RSLogix 5000 Software No Longer Functioning after Inhibit of Module in Unlocked Instance
There is a problem when more than one instance of RSLogix 5000 software is online to the same controller and one of the instances of
RSLogix 5000 software is configured as “Locked”. When an attempt is made to inhibit a module on the instance of RSLogix 5000
software which is not locked, then an error is properly reported; however, that instance of RSLogix 5000 software may no longer
function properly. Unexpected errors will be reported during editing (such as “Unknown transaction error”, and that instance may be
taken offline. When this occurs it is necessary restart that instance of RSLogix 5000 software. (x125228)
Major Non-Recoverable Fault Removing Alarm Message Tag Association While Online
In RSLogix 5000 software version 16.03, the ability to edit the Associated Tag configuration for analog and digital alarm tags was
enabled. If an alarm tag is referenced in executing logic, any attempt while online to remove an Associated Tag for that alarm tag may
result in a Major Non-Recoverable Fault in the controller. (x77626)
Unable to Communicate with Remote CompactLogix Controller at Different Major Revision of Firmware
A remote CompactLogix port/controller is created with default electronic keying of „Compatible Keying‟. If the firmware in this remote
CompactLogix controller is upgraded, it is necessary to also upgrade the firmware for other controllers communicating with this remote
controller. There is a workaround for this anomaly that involves re-importing and downloading the project. First, export the project, and
modify the following two attributes for the remote controller MODULE: „CompatibleModule := 0, KeyMask := 2#0000_0000_0000_0000‟.
Then import the project and download to the controller. This anomaly has been corrected in RSLogix 5000 software version 16.03 with
an enhancement to create the port/controller with default electronic keying of „Disable Keying‟ and to allow the keying to be edited.
(x72948)
Operands Missing After Copy and Paste or Drag and Drop of MDSC Related Motion Instructions to
Version 20
Additional operands are required for the MAJ, MAM, and MATC single-axis Motion instructions and MCLM and MCCM Coordinated
Motion instructions as part of the Master-Driven Speed Control (MDCS) feature introduced in version 20 of RSLogix 5000 software.
When copying any of these instructions to version 20 from an earlier version of RSLogix 5000 software by using copy and paste or drag
and drop, the new operands are not automatically inserted. This results in instructions that will not verify. When this occurs, it is
necessary to make the appropriate corrections to the pasted instruction. Note that this anomaly does not exist for converted or imported
projects. A suitable workaround for Structured Text instructions may be to use Routine Copy of Structured Text. (x119309)
Operands Missing After Copy and Paste or Drag and Drop of Coordinated Motion Instructions to
Version 17
Additional operands are required for the MCLM, MCCM, MCCD, and MCS Coordinated Motion instructions in Structured Text as part of
the Multi-Axis Programmable Jerk feature introduced in version 17 of RSLogix 5000 software. When copying any of these instructions
to version 17 from an earlier version of RSLogix 5000 software using copy and paste or drag and drop, the new operands are not
automatically inserted. This results in instructions that will not verify. When this occurs, it is necessary to make the appropriate
corrections to the pasted instruction. Note that this anomaly does not exist for converted or imported projects. A suitable workaround for
Structured Text instructions may be to use Routine Copy of Structured Text. (x80000)
Operands Missing After Copy and Paste or Drag and Drop of Motion Instructions to Version 16
Additional operands are required for the MAM, MAJ, and MAS Motion instructions (in Ladder Diagram and Structured Text) as part of
the Programmable Jerk feature introduced in version 16 of RSLogix 5000 software. When porting any of these instructions to version 16
from earlier versions of RSLogix 5000 software by using copy and paste or drag and drop, the new operands are not automatically
inserted, resulting in instructions that will not verify. When this occurs you must make the necessary corrections to the copied
instruction. It should be noted that this anomaly does not exist for converted or imported projects. For Ladder Diagram, a suitable
workaround may be to use Partial Export/Import of rungs containing these instructions. (x57337)
SoftLogix Controller Does Not Retrieve Object Values Set By SSV Instruction
After executing an SSV instruction using a SoftLogix controller, an upload of the project will not retrieve the updated object values. As a
workaround, the object attributes can be stored in tags. SSV can then be performed from those tags in an initialization routine. (Note
that this is an anomaly only for the SoftLogix controller; uploads of object values modified by an SSV on other controllers will be
successful.) (x59117)
To avoid this Fatal Error when entering Unicode characters, the edit control should be explicitly opened before beginning to enter
character data from the keyboard. In most cases, pressing [Enter] on the keyboard will open the edit control that has the caret. In other
cases, a single click or double-click of the mouse is required.
When using an IME to input Unicode characters, if the small IME character input dialog box appears in the upper left corner of the
display, then you have started to input a Unicode character string with no edit control opened. When this occurs, you can press [Esc] on
the keyboard to cancel the input and then open the desired edit control before entering the Unicode character string.
Long Timeout if PowerFlex 755 Drive Loses Power During Update by Firmware Supervisor
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. (x125029, x125045)
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:
Launch the FactoryTalk Administration Console (available from the Start menu).
Select the Network directory when prompted. (You may need to provide credentials for a user with Administrator privileges in order
to continue.)
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”. Then click Add and provide the domain\logon name for the desired user. (You can click
Check Names to verify that the name was found.)
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”. Then click Add and type the name of the user group
“authenticated users”.
The “Log On to FactoryTalk” dialog box may also be displayed when using Remote Desktop to connect to the personal computer that is
running RSLogix 5000 software. This is due to FactoryTalk Security not recognizing the computer name. To enable access through
Remote Desktop for a specific computer, you should add the name of the computer that is initiating the Remote Desktop connection to
the “Network\System\Computers and Groups\Computers” folder in the FactoryTalk Administration Console. To allow remote computers
to connect using the name of the host computer, open the FactoryTalk Administration Console and log in to the Network directory using
your domain credentials. Then navigate to “Network\System\Policies\Security Policy”. In the “Computer Policy Settings” section, set
“Identify terminal server clients using the name of” to “Server Computer”. To allow all computers to connect, set the value of “Require
computer accounts for all client machines” to disabled.
Note that if “Use single sign-on” is set to “disable” in FactoryTalk software, then the “Log On to FactoryTalk” dialog box will be displayed
each time RSLogix 5000 software is launched and proper user credentials must be entered in order to continue. (By default, “Use single
sign-on” is set to “enable”.)
RSLogix 5000 Software Becomes Temporarily Unresponsive Waiting for FactoryTalk Services
When the server hosting the FactoryTalk Directory is restarted, RSLogix 5000 software may become unresponsive for about 3-5
minutes. When FactoryTalk Services then become available, RSLogix 5000 software will resume normal operation. (x129306)
RSNetWorx Software Cannot Download to Controller at Version 20 Firmware That is in Run Mode
When attempting to download a project using RSNetWorx software, if the controller firmware is at revision 20 and the controller is in
Remote Run mode, then RSNetWorx software will not be able to change the controller mode in order to download. In this case, the
controller mode must be changed either by using the keyswitch or by using RSLogix 5000 software version 20. (x124236)
Logix CPU Security Tool Does Not Work with RSLogix 5000 Software Version 20
When using the Logix CPU Security Tool to browse to a controller with Logix 5000 firmware version 20, you will be presented with a
dialog box that indicates “Unable to connect to controller. Communications have timed out.” This does not affect the ability to use this
tool with earlier revisions of Logix5000 firmware. (x129277)
Slow Launch Times for RSLogix 5000 Software after Restarting Personal Computer
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. (x125369)
Security Option for Module: Modify Properties Prevents Modification on Motion Configuration
With the security action „Motion: Modify Configuration‟ granted, you should be allowed to modify the motion configuration. You are
allowed to change the axis association to a module from the Axis Properties dialog box but are erroneously prevented from making this
change from the Module Properties dialog box. To allow the axis association to be configured on the Module Properties dialog box,
grant access for the security action „Module: Modify Properties‟. This will enable all of the tabs of the Module Properties dialog box,
including the Axis Association tab. (x72088)
RSLogix 5000 Software Stops Logging Messages to FactoryTalk AssetCentre (RSMACC) After
Uninstalling FTAP Version 2.0
As part of the installation of RSLogix 5000 software version 15 and earlier, FactoryTalk Diagnostics files versions earlier than 2.00 are
also installed. When FactoryTalk Automation Platform (FTAP) version 2.0 is installed (either separately or as part of another product
install), these FactoryTalk Diagnostics files are upgraded. If you then uninstall FTAP 2.0, the upgraded FactoryTalk Diagnostics files will
no longer function, and RSLogix 5000 software will be unable to log audit and diagnostic messages. When this occurs, you can correct
the anomaly by simply re-installing FTAP 2.0. In order to avoid getting into this situation, you should not uninstall FTAP 2.0 without first
uninstalling all products that make use of FactoryTalk Diagnostics files. (x55161)
Motion SERCOS Ring Phase Up Issue if Auxiliary Feedback Units Aux_Mm or Aux_Inch
If a motion Axis_Servo_Drive axis is configured with a Loop Configuration using auxiliary feedback, there are 3 choices for the units for
Drive Counts per: Aux Rev, Aux Inch, Aux Millimeter. Only the default Aux Rev is valid for RA SERCOS Drives. Selecting Aux Inch or
Aux Millimeter will cause a SERCOS Ring phase up fault at Phase 3. The SERCOS Fault reported will be „Position Data Scaling –
Invalid attribute value‟. To workaround the anomaly, select Aux Rev as the units when configuring a Loop Configuration using
Dual/Auxiliary feedback. (x43750, x43870, x44775)
Hardware Overtravel (OT) Fault Does Not Always Stop Motion when Soft OT Fault Action = Status Only
For Kinetix 6000 axes configured in RSLogix 5000 software, if you have both Soft Overtravel and Hardware Overtravel Limits enabled,
and you configure the Soft Overtravel Fault Action as „Status Only‟, be aware that a Hardware Overtravel Fault Action configured for
„Stop Motion‟ may not „Stop Motion‟ due to the two faults existing together and the first fault action being set to „Status Only‟. For more
information refer to Technical Note: ID=36709 „2094 Kinetix 6000; Soft Overtravel triggers first then sequential hard overtravel does not
stop motion‟, and Technical Note: ID=21500 „How do I get off a Soft Overtravel?‟ (x66998)
Unable to Perform FBD Routine Pending Edits in Hard Run or Controller Locked Modes
You are restricted from performing FBD routine pending edits when the controller is in Hard Run mode (keyswitch) or the controller is
locked by another user. To work around this anomaly put the controller into Remote Run mode or Program mode or unlock the
controller. (x43429, x41415)
Displaying Secondary Online Help Window May Cause Blank Primary Window
If you have a primary help window displayed and you open a help topic which displays a secondary window, the primary window may
become blank. This is the result of an anomaly with the Windows Help compiler. To display the original topic, click Help Topics and re-
select the original topic. (x39239)
In the ST Editor, when a parameter is entered, the software automatically interprets the text utilizing a precedence scheme in the
following order: ST key words, tag names, routine names, program names, task names, module names, instruction names, function
names, and enumeration (used in GSV/SSV instructions or the motion family of instructions). When a full routine verification is
performed, the software is able to rationalize the parameter name with the appropriate project component based on its use within the
instruction. For example, the first parameter in a JSR is a routine name, or a reference within a GSV may be a program name.
However, if the two different project components utilize the same name, a rename operation may result in an unintended change to a
parameter reference. A warning is generated during verify that this may have occurred. The warning is „There is more than one project
component with the same name as the referenced parameter. Ensure the correct reference or keyword is used in ST logic and re-
verify‟.
Example 1
1. Create a tag named A and a routine named A
2. Enter the statement JSR( A ); in an ST routine. At this point, the ST references the tag A.
3. Verify the ST routine (directly or during a download). At this point, the system determines that this is a JSR instruction and that the
parameter is a routine. Now the reference is to routine A.
Example 2
1. Create a tag named A and routines named A and B.
2. Enter the statement JSR( A ); in an ST routine. At this point, the ST references the tag A. Close the routine.
3. Rename tag A to B. All references to the tag now have the new name B.
4. Open the ST routine.
5. In the ST, the name was changed to B, so the statement is now JSR( B );.
6. Verify the ST routine (directly or during a download). At this point, the system determines that this is a JSR instruction and that the
parameter is a routine. However, the routine B is referenced not the intended routine A.
The warning during verify is generated for both of the above cases. You need to check that the correct component or keyword is being
referenced if this warning appears.
To avoid these warnings and ensure that you are referencing the correct item at all times, avoid naming tags, routines, programs, tasks,
and modules with the same name. Also avoid using names that are the same as instruction names or parameter enumerations used in
GSV/SSV instructions or the motion family of instructions. (x32846)
If you have routines with Motion Arm Output Cam (MAOC) instructions created in versions of RSLogix 5000 software earlier than
version 9.00 and you convert them to version 13.00, the MAOC instructions will not operate unless the associated axis tag is manually
corrected. The conversion of the earlier version instructions set the execution targets for the axis tag to zero, which will cause the
MAOC instructions to error when executed. To correct the problem, access the Axis Properties dialog box General tab for the axis tag
and set the Output Cam Execution Targets value to the correct number for your application. (x25982)
Indirect Addressing within Add-On Instruction Logic Using RSLogix 5000 Software Version 20.01
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
in RSLogix 5000 software.
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
(http://www.rockwellautomation.com/knowledgebase/).
1769-L2y Controllers Cannot Be Properly Configured Using RSLogix 5000 Software Version 20.00
For 1769-L2y controller types, which were newly 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 RSLogix 5000 software version 20.01. 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
RSLogix 5000 software. You may find it convenient to use the File > Import Component feature of RSLogix 5000 software to port your
logic from the version 20.00 project to the new version 20.01 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 with Version 18.00 or Later
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.
CIP Generic Writes to Controller Objects that Originate from Another Controller May Fail
In RSLogix 5000 software version 20 there are enhanced security restrictions to controller CIP objects. Because of this some CIP
Generic messages used to write directly to controller object attributes may not function. Any CIP generic object write that originates
external to the controller may fail in RSLogix 5000 software version 20. CIP Generic writes that are executed in the controller‟s own
user program will operate normally.
Testing SFC Online Edits No Longer Always Requires the Chart to Reset with Version 18.00 or Later
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 could leverage the SFC Reset (SFR)
instruction to reposition the chart back to the desired step. (x36331, x43482)
Can‘t 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 RSLogix 5000 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
import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to
avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled
QuickClean tasks from the McAfee SecurityCenter UI. (x81691)
Unable to Open Full Project XML format file (.L5X) from Open/Import Project Dialog Box
RSLogix 5000 software versions 16 and earlier do not support full project import when using an XML format file (.L5X). If you have
version 17 or later of RSLogix 5000 software installed along with some earlier version of RSLogix 5000 software and you are currently
running that earlier version of software, then the Open/Import Project dialog box will not allow a file with an L5X or XML file extension to
be opened for import. To open an L5X format project you must first be sure that RSLogix 5000 software version 17 or later is running.
You can do this either by creating a new version 17 project or by opening any existing version 17 project that was saved with an ACD or
L5K file extension. Alternatively, you can select the L5X project file in Microsoft Windows Explorer by right-clicking the L5X file name
and using the „Open with‟ menu item to open the file with „Component of the RSLogix 5000 Application‟. Note that when the RSLogix
5000 software is installed, files with an ACD file extension are configured by default to open this way when selected. You can configure
files with L5X and L5K file extensions to also do this through Windows Explorer by manually associating these extensions with the
executable file RSLogix5000Loader.exe, typically installed in the directory C:\Program Files\Rockwell Software\RSLogix 5000\Common
or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common. (x87808)
Unknown URL Attempting to Access Online Books or Vender Sample Projects from Start Page
If your personal computer is not configured as part of a domain, you may receive the error message „Unknown URL‟ when attempting to
access Online Books or Vender Sample Projects from the Start Page. This is the result of security enhancements to the Internet
Explorer browser. If RSLogix 5000 software 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 Vender Sample Projects can be allowed by adding „localhost‟ to the
allowed Local Intranet sites. (x89165)
Start Pages Won‘t Work if Version 16.00 Is Installed After Other Versions
If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software 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 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of
RSLogix 5000 software and later. (x76424)
Function Block Diagram (FBD) ActiveX Faceplates are 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.
First Use of Drive Profile by User Who Did Not Install the Add-On Profiles Will Require 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)
Motion Instruction Error Generated 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)
RSLogix 5000 Event Task Names can Conflict with Microsoft Windows Event Names
Creation of an RSLogix 5000 event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same
name. Since 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.
* Before a Custom Motor can be used in RSLogix 5000 software 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.
Using Security with Version 16 RSLogix 5000 Software 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.
They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.
Tag Modify Properties is Required to Update Configuration Dialog Boxes Having a Tag Tab
When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed 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 Coming With FactoryTalk CPR 9 Release
The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9
will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix
controllers, and actions, like „Tag Create‟, for easier security administration.
File Import of Axis With MPx Motors may Generate Warning for 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, the user should verify that the Axis Parameters pertaining to Rated Current are
configured for proper axis operation. As an alternative, the user can reassociate 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 Displayed 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 displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time
stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom
graphics will be added to a future release of FactoryTalk SE.
Use New Clock Update Tool with Logix5000 Version 16 and Later Software
A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with
Logix5000 version 16 and later. Older revisions may 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.
If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when
RSLogix 5000 software is started. Clicking „Change‟ on this warning dialog box will navigate to the operating system dialog box from
which the user 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 RSLogix 5000 software (9324-RLD300ZHE), you should select „Chinese (PRC)‟ for the System Locale.
Starting with RSLogix 5000 software version 14, the directory structure for temporary RSLogix 5000 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 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).
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)
Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393)
The REAL data type also stores ±infinity, ±NAN, and -IND, but the software display differs based on the display format.
The software also stores and displays the IEEE subnormal range:
-1.17549421E-38 to -1.40129846E-45 (negative values)
1.40129846E-45 to 1.17549421E-38 (positive values)
RSLogix 5000 Software Save May Result In Large Project ACD File
During a file save operation RSLogix 5000 software 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, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of
project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may
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 RSLogix 5000 software
development team to locate the source of the compression failure.
Motion Axis Fault Reset MAFR Timing Changed on Kinetix Drives to Accommodate Motor
Commutation
The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate 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 and now up to 400ms, in the RSLogix
5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed
faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)
ControlFLASH Update of Rockwell Automation (RA) 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 RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA 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 RA Sercos Drives to
support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives
must have revision 1.85 or higher, and the RA 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)
To change the error detection, open a project and establish online communications using Ethernet, ControlNet, or DF1 communications
to the target Logix5000 controller. Open the Controller Properties dialog box and select the System Protocol tab. Under Error Detection
enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000
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; click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx
and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver
such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC.
Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software 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.
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).
Note: 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.
In the Station Mappings, click Add New to add a new mapping line if needed.
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 online 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.
Offline Tag and UDT Changes Downloaded to the Controller may Cause RSLinx Software (version 2.x)
to Halt Communications
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.
When you call, you should be at the computer running the Rockwell Software product and be prepared to provide:
The product serial number on the Activation disk labels.
You can find the serial number online. On the RSLogix 5000 menu, click Help and then About RSLogix 5000.
The product version number.
You can find the product version number online. On the RSLogix 5000 menu, click Help and then About RSLogix 5000.
The hardware you are using.
The exact wording/exact error codes of any messages that appear on the screen.
A description of what happened, and what you were doing when the problem occurred.
A description of how you tried to solve the problem.
IMPORTANT—READ THIS AGREEMENT CAREFULLY: This End-User License Agreement (“EULA”) is a legal contract
between you (either an individual or a single entity) (“You or Licensee”) and Rockwell Automation, Inc. ("Rockwell
Automation”) for the software product or products that Rockwell Automation licenses to You, which includes computer
software and may include associated media (“Software”). Rockwell Automation may also license to You printed materials,
and “online” or electronic documentation ("Documentation"). An amendment or addendum to this EULA may accompany
the Software. ROCKWELL AUTOMATION IS WILLING TO LICENSE THE SOFTWARE AND DOCUMENTATION TO
YOU ONLY ON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS AND CONDITIONS IN THIS
AGREEMENT. YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING,
COPYING, OR OTHERWISE USING THE SOFTWARE. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF
ANOTHER PERSON OR A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU
HAVE FULL AUTHORITY TO BIND THAT PERSON, COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO
NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE SOFTWARE,
AND PROMPTLY RETURN THE SOFTWARE WITH ALL ACCOMPANYING ITEMS TO YOUR PLACE OF PURCHASE
FOR A FULL REFUND. IF YOU DOWNLOADED THE PROGRAM, CONTACT THE PARTY FROM WHOM YOU
ACQUIRED IT.
This Software is licensed to You -- not sold. Your rights to use the Software are only those rights specified in this EULA.
GRANT OF LICENSE
Provided You comply with all the terms and conditions of this EULA, Rockwell Automation and its third party licensors
grant You a non-exclusive license to install and use the Software on a single computer, a network server, or on multiple
computers owned or leased by the Licensee provided the number of installations and users is not greater than the number
of valid software activations purchased.
If the Software You have acquired is a client application utilizing FactoryTalk® Activation and You have acquired a
concurrent activation, You may distribute and install an unrestricted number of copies of the client Software on computers
or networks owned or leased by the Licensee provided the number of users accessing or using the Software concurrently
does not exceed the number of valid software activations You purchased.
If the Software You have acquired is a server application, You are permitted to create or access a single instance of the
server application. You are not permitted to install multiple instances of the server application unless You have purchased
multiple server activations.
If the Software You have acquired is licensed to You based upon a capacity or runtime measurement, including but not
limited to a specific number of users, units, processors, assets, active tags or screens, You agree not to take any actions
to exceed this capacity. If You desire additional capacity for your Software, You agree to purchase such additional
capacity only from Rockwell Automation or its authorized distributors and resellers.
If the Software You have acquired is used in a virtualized environment, whether in a client or server application, the
number of concurrently used virtual environments or instances may not exceed the number of valid software activations
You purchased.
If the Software You have acquired is used in conjunction with Microsoft SQL Server, You may be provided with a
Microsoft SQL Server license during installation. If the Software includes limited license rights for Microsoft SQL Server,
You agree to only use such Microsoft SQL Server in conjunction with the Software, and You will acquire from Microsoft
any licenses to Microsoft SQL Server that exceeds the rights provided to You under this Software.
This License does not grant You the right to provide or utilize the Software as an application service provider or the like.
Any attempted sublicense, rental, sale, lease, transfer or commercial hosting of the Software is prohibited. If the Software
requires a software activation process, such as FactoryTalk® Activation, You agree to follow this activation process as
part of the license to You under this EULA.
If this Software is an upgrade or update to a previous version of a Rockwell Automation product, You may not transfer the
prior version to another user. This EULA supersedes any prior license with respect to Your use of the Software.
LIMITED WARRANTY
The Software is warranted for ninety days after its initial delivery to You that it will substantially conform with its
Documentation supplied by Rockwell Automation at the time of initial delivery of the Software. Defective media will be
replaced without charge if returned during the warranty period. This warranty shall be void if You attempt to modify the
Software in any way. Rockwell Automation makes no representation or warranty, express or implied, that the operation of
the Software will be uninterrupted or error free, or that the functions contained in the Software will meet or satisfy Your
intended use or requirements; You assume complete responsibility for decisions made or actions taken based on
information obtained using the Software.
TO THE MAXIMUM EXTENT PERMITTED BY LAW THE FOREGOING LIMITED WARRANTY IS IN LIEU OF ALL
OTHER WARRANTIES, EXPRESS OR IMPLIED, AND ROCKWELL AUTOMATION DISCLAIMS ANY AND ALL
IMPLIED WARRANTIES OR CONDITIONS, INCLUDING (WITHOUT LIMITATION) ANY WARRANTY OF TITLE,
NONINFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE OR ANY WARRANTY UNDER UCITA.
SOME COUNTRIES AND STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE
EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY
ALSO HAVE OTHER RIGHTS WHICH VARY FROM COUNTRY TO COUNTRY OR STATE TO STATE.
LIMITATION OF REMEDIES
Rockwell Automation entire liability and Your exclusive remedy for breach of the Limited Warranty shall be:
1. The replacement of the Software not meeting the Limited Warranty specified above which is returned with proof of
purchase; or
2. If Rockwell Automation is unable to deliver replacement Software which meets the Limited Warranty specified above,
You may terminate this EULA by returning or destroying the Software as provided herein, and Rockwell Automation or its
reseller will refund Your purchase price.
LIMITATION OF LIABILITY
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL ROCKWELL AUTOMATION
OR ITS THIRD PARTY LICENSORS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, PUNITIVE, OR
CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF
PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR LOST SAVINGS,
FOR LOSS OF PRIVACY, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF
OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF ROCKWELL
AUTOMATION OR ITS RESELLER HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME COUNTRIES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. ROCKWELL
AUTOMATION'S MAXIMUM CUMULATIVE LIABILITY RELATIVE TO ALL CLAIMS AND LIABILITIES, INCLUDING
THAT WITH RESPECT TO DIRECT DAMAGES AND OBLIGATIONS UNDER ANY INDEMNITY, WHETHER OR NOT
INSURED, WILL NOT EXCEED THE COST OF THE SOFTWARE GIVING RISE TO THE CLAIM OR LIABILITY. ALL OF
THESE DISCLAIMERS AND LIMITATIONS OF REMEDIES AND/OR LIABILITY WILL APPLY REGARDLESS OF ANY
OTHER CONTRARY PROVISION OF THIS EULA OR ANY OTHER AGREEMENT BETWEEN YOU AND ROCKWELL
AUTOMATION AND REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT OR OTHERWISE,
AND FURTHER WILL EXTEND TO THE BENEFIT OF ROCKWELL AUTOMATIONVENDORS, APPOINTED
DISTRIBUTORS AND OTHER AUTHORIZED RESELLERS AS THIRD-PARTY BENEFICIARIES.
This EULA takes effect upon Your use of the Software and remains effective until terminated for any reason. You may
terminate it at any time by destroying all copies of the Software and Documentation in Your possession. It will also
automatically terminate if You fail to comply with any term or condition of this EULA. You agree on termination of this
EULA to either return to Rockwell Automation or destroy all copies of the Software and Documentation in Your
possession. If this Software has been licensed to You as part of a subscription service, this EULA shall terminate after
the period of the subscription has lapsed.
THIS SOFTWARE WILL CEASE TO OPERATE AT THE EXPIRATION OF YOUR LICENSE TERM, OR WHENEVER
THE SOFTWARE IS UNABLE TO LOCATE FACTORYTALK® ACTIVATION. THIS SOFTWARE WILL CONTINUE TO
OPERATE FOR 7 DAYS WITHOUT FACTORYTALK® ACTIVATION TO PROVIDE USERS A GRACE PERIOD FOR
RENEWING APPLICABLE LICENSES OR RESOLVING YOUR FACTORYTALK® ACTIVATION ISSUE. IMPORTANT:
DURING THE GRACE PERIOD, PRODUCT FEATURES IN EXCESS OF THAT ORIGINALLY LICENSED MAY BE
ACCESSIBLE. LICENSEE IS NOT AUTHORIZED TO USE FEATURES IN EXCESS OF THAT ORIGINALLY
LICENSED.
ACADEMIC USE
If this Software was purchased for academic or research use by an educational institution, it may be used for teaching and
research purposes only. Commercial use of the Software is prohibited if the software was intended for educational use.
Only the instructor/professor registered to the Software is eligible to contact Rockwell Automation for technical support
and product updates. If this Software is Arena simulation software: (i) You have the right to make copies of the Software
(the media excluding activation) solely for academic, teaching and research purposes; and (ii) You also agree to comply
with the terms of the Arena Software Academic License Guidelines provided at the end of this EULA.
PREPRODUCTION RELEASES
As an accommodation to Licensee, Rockwell Automation may provide Licensee with a preproduction release of the
Software (often labeled a “beta release”). These releases are not suitable for production use. SUCH RELEASES ARE
PROVIDED ON AN “AS IS” BASIS. ROCKWELL AUTOMATION DOES NOT WARRANT PREPRODUCTION
RELEASES.
SAMPLES
The Software may include samples, plug-ins, UI components and/or reports that are provided as an accommodation to
You (“Samples”). These Samples are intended to be used for example purposes or to provide additional complimentary
features. The Samples may be contained in the Software, Documentation (electronic or printed) or downloaded from the
Rockwell Automation website. Rockwell Automation and its third party licensors make no representations or warranties
regarding Your use of the Samples and related Documentation. All such Samples are provided "as is". Rockwell
Automation disclaims all warranties with regard to this information, including all implied warranties and conditions of
merchantability, fitness for a particular purpose, title and non-infringement.
If You are a branch or agency of the United States Government, the following provision applies. The Software and
Documentation are comprised of "commercial computer software" and "commercial computer software documentation" as
such terms are used in 48 C.F.R. 12.212 (SEPT 1995) and are provided to the Government (i) for acquisition by or on
behalf of civilian agencies, consistent with the policy set forth in 48 C.F.R. 12.212; or (ii) for acquisition by or on behalf of
units of the Department of Defense, consistent with the policies set forth in 48 C.F.R. 227.7202-1 (JUN 1995) and
227.7202-3 (JUN 1995).
EXPORT CONTROLS
You acknowledge that the Software is subject to the export control laws and regulations of the United States and any
amendments thereof. You agree that You will not directly or indirectly transfer or use the Software except in compliance
with applicable U.S. export laws and regulations.
You agree that Rockwell Automation may audit your use of the Software for compliance with these terms, upon
reasonable notice. In the event that such audit reveals any use of the Software by You other than in full compliance with
the terms of this EULA, You shall reimburse Rockwell Automation for all reasonable expenses related to such audit in
addition to any other liabilities You may incur as a result of such non-compliance.
OWNERSHIP
The Software and Documentation are protected by copyright and other intellectual property laws and treaties. Rockwell
Automation or its licensors own the title, copyright, and other intellectual property rights in the Software and
Documentation. The Software and Documentation is licensed, not sold. Nothing in this EULA constitutes a waiver of our
rights under U.S. or international copyright law or any other law.
This EULA shall be governed by the laws of the State of Wisconsin, without regard to any conflict of laws provisions. The
United Nations Convention on the International Sale of Goods will not apply. You agree to bring any action in connection
with this EULA or the Software exclusively in the state or federal courts of Wisconsin, and You further agree to the
jurisdiction of the state and federal courts of Wisconsin for any action that Rockwell Automation brings against You.
You may not separate component parts of the Software for independent use. The Software may contain third party
software which requires notices and/or additional terms and conditions. Such required third party notices and/or
additional terms and conditions are identified in the help or about screens and license.txt or readme text files of the
Software and are made a part of and incorporated by reference into this EULA. By accepting this EULA, You agree to
review such terms and conditions set forth therein, if any, and your use of the Software will be deemed to be your
acceptance thereof.
This EULA, and any amendment or addendum to this EULA that accompanies the Software is the complete and exclusive
agreement between Rockwell Automation and You, and supersedes all prior agreements, whether written or oral, relating
to the Software provided and the Documentation. This EULA may not be changed or modified except by an instrument in
writing signed by a duly authorized representative of Rockwell Automation. If for any reason a court of competent
jurisdiction finds any provision of this EULA or portion thereof, to be unenforceable, that provision of the EULA shall be
enforced to the maximum extent permissible so as to affect the intent of the parties, and the remainder of this EULA shall
continue in full force and effect.
The parties acknowledge that they have required the EULA to be drafted in English. Les parties reconnaissent avoir
exigé la rédaction en anglais du Contrat. In the event of a conflict between the English and other language versions, the
English version will prevail.
If the Software is RSLogix, this License does not grant You the right to provide or utilize the Software as part of or in
connection with a third party service or software application that interacts with the Software: (a) without You manually
inputting all commands (e.g. local or remote keyboard emulation without manual keyboard input would be prohibited); or
(b) by providing or applying automated instructions or scripting technology to the Software. If this Addendum is being
provided for an update of Software that did not contain the above RSLogix License Restriction when it was originally
licensed to You, your earlier rights of use shall apply for the update if You were previously using the Software in the
manner now restricted.
Rockwell Automation has developed a programmatic interface to its RSLogix Software (the “Automation Interface”). The
Automation Interface is intended to provide enhanced functionality between Rockwell Automation software products.
I. RSLogix 5 and 500. Access to the Automation Interface is provided with some versions of RSLogix 5 and 500 and in
these cases, You are granted a non-exclusive license to use the Automation Interface in conjunction with your use of the
RSLogix 5 and 500 Software and application code created by the RSLogix 5 and 500 Software, but only:
a) in applications programmed by You for use in and for your own control systems within your own facilities,
including the programming of control systems having controllers within them which are intended to be resold as
equipment systems with a substantial value added component, or
b) in applications custom developed for your individual customers, where each application so developed is owned
and used exclusively by a single customer end-user who owns one or more control systems operating within its
own facility and the application code developed for each customer is not shared with or among other such end-
user customers.
II. RSLogix 5000. Access to the Automation Interface has not been provided to You with RSLogix 5000 Software and
accordingly, You are not granted a license to use the Automation Interface in conjunction with your use of the RSLogix
5000 Software.
III. Additional restrictions for all RSLogix Software, including any RSLogix tools. You are not licensed to use the
Automation Interface or the RSLogix5000 Command Line Tool to:
PLEASE NOTE: Rockwell Automation does not include debugging or troubleshooting services for custom applications as
a part of our standard support.
The Software may include additional software tools or utilities, including, but not limited to the following: RSLogix
Command Line Tool, BootP-DHCP Server, Combination Generator Control Module (CGCM), ClearKeeper, DeviceNet
Node Commissioning Tool, Logix CPU Security Tool, Logix5000 Clock Update Tool, Logix5000 PLM Sync Utility,
Logix5000 Task Monitor Tool, RSLogix 5000 Compare Tool, RSLogix 5000 DeviceNet Tag Generator, RSLogix 5000
Data Preserve Download Tool, RSLogix 5000 Faceplates, RSLogix 5000 IEC61131-3 Translation Tool, Tag Data Monitor
Tool, Tag Import Utility, and Tag Upload Download Tool.
Provided you are an authorized licensee of a RSLogix5000 software product and fully comply with this Agreement and
any amendments and addendums, you have been provided with a license to these software tools or utilities under this
Agreement on a complimentary basis in “AS IS” condition for Licensee internal use without any representation, support or
warranty whatsoever. Licensee assumes the entire risk of using these additional complimentary software tools and
utilities. LICENSOR DISCLAIMS ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
The runtime feature of Arena permits non-licensed users within Your organization to execute certain models created by
this Software (some restrictions may apply to the number of modeling constructs and the users’ ability to revise a model).
Runtime models may be executed only if the organization owns an active commercial Arena license or the individual has
access to the separately purchased runtime activation.
This documentation, whether, illustrative, printed, "online" or electronic (hereinafter "Documentation") is intended for use
only as a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware. The
Documentation should only be used as a learning tool by qualified professionals.
The variety of uses for the hardware, software and firmware (hereinafter "Products") described in this Documentation,
mandates that those responsible for the application and use of those Products must satisfy themselves that all necessary
steps have been taken to ensure that each application and actual use meets all performance and safety requirements,
including any applicable laws, regulations, codes and standards in addition to any applicable technical documents.
In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter "Rockwell
Automation") be responsible or liable for any indirect or consequential damages resulting from the use or application of
the Products described in this Documentation. Rockwell Automation does not assume responsibility or liability for
damages of any kind based on the alleged use of, or reliance on, this Documentation.
No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or software
described in the Documentation and is only included for illustrative training purposes.
Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell
Automation or third-party provided instructions, warnings, recommendations and documentation;
ensuring that only properly trained personnel use, operate and maintain the Products at all times;
staying informed of all Product updates and alerts and implementing all updates and fixes; and
all other factors affecting the Products that are outside of the direct control of Rockwell Automation.
Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation
is prohibited.
LICENSE ADDENDUM TO END USER LICENSE AGREEMENT FOR ARENA SOFTWARE ACADEMIC LICENSE
GUIDELINES
The educating of new users and the research conducted with Arena simulation software is invaluable to Rockwell
Automation. This is one reason why Rockwell Automation will continue to offer Arena to academic users at a significant
discount. In order to enable us to continue to our academic program, we take our end user license agreement (EULA)
very seriously and expect our users to abide by the established academic use of the software for strictly educational and
research purposes. This document is meant to provide guidelines for using ArenaAcademic Licensing.
DEFINITION OF ACADEMIC
An academic license may be purchased by any accredited institution where the main focus is on educating students
and/or providing research. Many commercial organizations also have an academic component that offers training or
teaching, such as service companies and hospitals. The organization focus cannot be on supporting external systems,
such as non-profit / for-profit hospitals, technology institutes, or think tanks. Unless education is the primary service
delivered by the institution, it will be considered to be commercial unless prior written authorization from Rockwell
Automation is obtained.
ACADEMIC USERS
Use of the license seats are bound to the college/department that has purchased the seats (for example, if the
engineering department purchased the seats, the software can be used only by that college, not shared with the business
college). Only currently enrolled and/or registered students and currently employed professors and staff within the
purchasing college/department are authorized to use Arena academic software. This includes currently enrolled and/or
registered students who are currently enrolled in a course in the license-owning college or in a multidisciplinary course
included in the license-owning college. Upon request by Rockwell Automation, you agree to provide proof of such
enrollment and/or employment.
Use of the academic-licensed software for commercial use is a violation of the end user license agreement (EULA). The
use of the Arena academic licensed software is not permitted for commercial, professional, commercial training, or other
for-profit purposes. While it is common for sponsoring corporations to provide funding for projects, that funding should be
in the form of a grant to the academic institution and not to the individual groups, professors/advisors guiding the research
or student project work, or other affiliated groups established by or employing the professors/advisors within the
institution. This includes instances where the academic user has an ongoing relationship (other research projects) with the
corporate sponsor. Money transfer can also be characterized where an internal “cost equalization” takes place between
departments or organizations. Use of the academic license for commercial purposes could result in revocation of the
academic-licensed software.
The distribution of the model (.doe), program file (.p), templates (.tpl and .tpo) for a study is prohibited without approval by
Rockwell Automation. Data and visuals (including displaying animations that use file types like .avi, .wav, etc.) may be
presented as part of analysis that is publicly shared (e.g., contained within a published thesis or paper). If the commercial
institution and/or organization outside of the license-holding college participating in the research or study request the
model and/or templates for the study, please contact the Arena sales representative in your region for assistance on how
to transfer the model legally.
RESEARCH
Rockwell Automation encourages the use of Arena software for conducting independent academic research. The Arena
academic version can be used for not-for-profit research outside of the classroom setting, where the primary goal of the
research is to solve a general problem with the results being publicly shared and published. Research outside of these
bounds including for-profit and/or outside of the classroom setting where the research is conducted to solve a specific
problem for an organization (both internal and external) is not permissible use of the Arena academic software. For
clarification and/or should research be outside of academic use research guidelines, please contact your local sales
representative for information on the appropriate university research licensing.
Rockwell Automation encourages the use of Arena for senior- and other classroom-related projects. These projects
include undergraduate, graduate and doctorate theses. This experience enables students to use simulation to solve real-
world problems and exposes recipient companies to the benefits derived from the use of simulation. These efforts must
be undertaken as not-for-profit to comply with academic-use guidelines. Distribution of model(s) and/or template(s) must
also adhere to the aforementioned guidelines.
Rockwell Automation encourages the use of Arena in students‟ cooperative education and internship assignments. This
experience provides a valuable learning tool in utilizing simulation in solving real-world problems. However, the use of
academic licensing for these assignments is forbidden. It is the responsibility of the company (including adjoining
institutes, hospitals, technology institutes, etc.) sponsoring the assignment to obtain the appropriate commercial licensing.
The use of the evaluation version is permitted.