RSLogix 5000 Version 15.

02 Release Notes

Introduction
This help file is designed to introduce you to the RSLogix 5000 product. In this file, you will find information on installing the software,
system requirements, and known limitations in this release.

A Logix5000 system (ControlLogix, CompactLogix, FlexLogix, DriveLogix, and SoftLogix) baseline release consists of a set of
compatible hardware, firmware, and software components that provides system functionality. This release note describes concerns
and issues associated with the components that are included in this Logix5000 system release. Read it 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.
Choosing Your RSLogix 5000 Package
RSLogix 5000 is a scalable software solution, used to program and configure any of the Logix5000 family of controller products.
Depending on the functionality required one or more product catalog numbers might be needed to acquire the appropriate software
functionality. The following table will help you to determine which RSLogix 5000 package is best suited for your application needs.

RSLogix 5000 Enterprise Professional Full Edition Standard / Standard Edition Lite Edition Mini Edition Service Edition***
Series Bundle Edition Network Edition
Catalog Number 9324-RLD700NXyyE* 9324-RLD600yyE* 9324-RLD300NXyyE* 9324-RLD300yyE* 9324-RLD250yyE* 9324-RLD200yyE* 9324-RLD000yyE*
Controllers Supported CompactLogix5300 CompactLogix5300 CompactLogix5300 CompactLogix5300 CompactLogix5300 CompactLogix5300 CompactLogix5300
FlexLogix5400 FlexLogix5400 FlexLogix5400 FlexLogix5400 FlexLogix5400 FlexLogix5400 FlexLogix5400
ControlLogix5500 ControlLogix5500 ControlLogix5500 ControlLogix5500 ControlLogix5500
DriveLogix5700 DriveLogix5700 DriveLogix5700 DriveLogix5700 DriveLogix5700
SoftLogix5800 SoftLogix5800 SoftLogix5800 SoftLogix5800 SoftLogix5800
Ladder Diagram (LD) Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Upload/Download
Included View Only
Function Block Diagram (FBD) Upload/Download Upload/Download Fully Supported Upload/Download Upload/Download
and Advanced Process and Fully Supported Fully Supported Included Included Included Included
Drive control blocks Editor Available Editor Available Editor Available View Only
(9324-RLDFBDENE, or via Separately Separately Separately
9324-RLDMLPE)
FBD PIDE Autotune (requires Included Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately
FBD option)
(9323-ATUNEENE)
Sequential Function Chart Fully Supported Fully Supported Upload/Download Upload/Download Fully Supported Upload/Download Upload/Download
(SFC) Included Included Included Included
(9324-RLDSFCE, or via Editor Available Editor Available Editor Available View Only
9324-RLDMLPE) Separately Separately Separately
Structured Text (ST) Fully Supported Fully Supported Upload/Download Upload/Download Fully Supported Upload/Download Upload/Download
(9324-RLDSTXE, or via 9324- Included Included Included Included
RLDMLPE) Editor Available Editor Available Editor Available View Only
Separately Separately Separately
Phase Manager Fully Supported Fully Supported Upload/Download Upload/Download Upload/Download Upload/Download Upload/Download
(9324-RLDPME) Included Included Included Included Included
Editor Available Editor Available Editor Available Editor Available View Only
Separately Separately Separately Separately
Miscellaneous Features:
Highly integrated Motion Fully Supported Fully Supported Fully Supported Fully Supported Upload/Download Upload/Download Upload/Download
Included Included Included
Graphical Trending Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported Fully Supported
RSMACC Audit Support Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately
DriveExecutive Lite Included Included Included Included Available Separately Available Separately Available Separately
(9303-4DTE01ENE)
RSLogix Emulate 5000 and Included Available Separately Available Separately Available Separately N/A N/A N/A
RSTestStand Lite
(9310-WED200ENE)
RSLinx Classic Professional Lite Included Lite Included Lite Included Lite Included Lite Included Lite Included
Included**
RSLogix Architect Included Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately
(9326-LGXARCHENE)
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 5000 Enterprise Professional Full Edition Standard / Standard Edition Lite Edition Mini Edition Service Edition***
Series Bundle Edition Network Edition
Miscellaneous Files & Tools:
Logix CPU Security Tool Included Included Included Included Included Included Included
Routine Source Protection Included Included Included Included Included Included Included
RSMACC Authenticate Client Included Included Included Included Included Included Included
(Security Server)
Standalone Security Server Included Included Included Included Included Included Included
Explorer
Electronic manuals (PDF) Included Included Included Included Included Included Included
Tutorial / Quick Tour Included Included Included Included Included Included Included
ControlFLASH with Firmware Included Included Included Included Included Included Included
FBD ActiveX Faceplates Included Included Included Included Included Included Included
PLC-5/SLC-500 Translation Included Included Included Included Included Included Included
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
RSLogix 5000 DeviceNet Tag Included Included Included Included Included Included Included
Generator
RSView Demo (50 Tags / 2 Included Available Separately Available Separately Available Separately Available Separately Available Separately Available Separately
Hour Limit)
Upgrades N/A Full to Professional Standard to Standard to Lite to Full Mini to Standard Service to Standard
9324-RLD6U7yyE* Professional Professional 9324-RLD25U6yyE* 9324-RLD2U3yyE* 9324-RLD0U3yyE*
9324-RLD3U7yyE* 9324-RLD3U7yyE*
Lite to Professional Mini to Full Service to Full
The Multi-Language The Multi-Language 9324-RLD25U7yyE* 9324-RLD2U6yyE* 9324-RLD0U6yyE*
Pack (9324- Pack (9324-
RLDMLPE) and the RLDMLPE) and the Mini to Professional Service to
PhaseManager PhaseManager 9324-RLD2U7yyE* Professional
(9324-RLDPME) (9324-RLDPME) 9324-RLD0U7yyE*
options extend options extend
Standard to match Standard to match
Full Full
* Replace yy with the appropriate language code where: DE = German, EN = English, ES = Spanish, FR = French, IT = Italian, PT = Portuguese.
** The RSLogix 5000 Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic.
*** Service Edition requires controller firmware at revision 12 or above.
System Requirements
To use RSLogix 5000 software effectively, your personal computer must meet the following hardware and software requirements.

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

Characteristic Minimum Required Recommended

Processor Pentium II Pentium 3 or better
Speed 450 MHz 733 MHz
RAM Memory 128 Mbytes 256 Mbytes
Hard Disk Space 150 Mbytes free 300 Mbytes free
Video 800x600 pixels 256 colors 1024x768 pixels True Color
Pointing Device Any Windows-compatible Any Windows-compatible
pointing device pointing device

Software Requirements
You must have installed these software products:
ƒ The operating system must be any of these:
ƒ Microsoft® Windows XP Professional with Service Pack 2 or XP Home
ƒ Microsoft® Windows 2000 Professional with Service Pack 1, 2, 3 or 4
ƒ Microsoft® Windows Server 2003
Starting with Version 14, RSLogix 5000 does not support Microsoft® Windows NT® Workstation Version 4.0. RSLogix 5000
software also does not support Windows NT 3.51, Windows NT 3.50, Windows Me, Windows 98SE, Windows 98, Windows 95, or
Windows 3.x operating systems.
ƒ RSLinx™ communication software is not required to install RSLogix 5000; however it is required in order to perform online
communication with controllers.
ƒ Microsoft® .NET Framework Version 1.1 must be installed on the same computer on which the RSLogix 5000 software will be
installed, for version V13.00 and later. This software is included as part of the RSLogix 5000 installation.
Revision Information
Important: The following controllers are no longer supported in this version of RSLogix 5000:
ƒ ControlLogix 1756-L1
ƒ CompactLogix 1769-L20
ƒ CompactLogix 1769-L30
ƒ FlexLogix 1794-L33
ƒ DriveLogix5720 PowerFlex 700S

If you attempt to open a project of any of these controller types, an error message will be displayed and you will be prompted to convert
the project to a supported controller type. Also, note that this version of RSLogix 5000 does not support either of the Safety Controllers:
1756-L61S, 1756-L62S.

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. However, previous revisions 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 have been tested to ensure 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 revisions of software and
firmware that have been tested and validated together.

Software

RSLogix 5000 Version RSLinx Classic RSNetWorx for ControlNet RSNetWorx for DeviceNet RSNetWorx for
Version Version Version EtherNet/IP Version

V15.02 / V15.01 / 2.50.00.20 (CPR 7) 6.00.00 (Build 97) (CPR 6) 6.00.00 (Build 97) (CPR 6) 6.00.00 (Build 97) (CPR 6)
V15.00

V14.01 / V14.00 2.43.01.23 (CPR 6) 5.11.00 (Build 31) (CPR 6) 5.11.00 (Build 31) (CPR 6) 5.11.00 (Build 31) (CPR 6)

V13.04 / V13.03 / 2.42.00 (Build 18) 4.21.00 (Build 50) 4.21.00 (Build 50) 4.21.00 (Build 50)*
V13.02 / V13.01 /
V13.00

V12.06 / V12.05 / 2.41.00 (Build 10) 4.11.00 (Build 47) 4.12.00 (Build 01) 4.11.00 (Build 29)
V12.04 / V12.03 /
V12.02 / V12.01 /
V12.00

V11.16 / V11.15 / 2.40.00 (Build 16) 3.23.00 (Build 11) 3.21.00 (Build 27) Not applicable
V11.14 / V11.13 /
V11.12 / V11.11 /
V11.10

V10.07 / V10.06 / 2.30.02 (Build 79) 3.23.00 (Build 11) 3.21.00 (Build 27) Not applicable
V10.05 / V10.04 /
V10.03 / V10.02 /
V10.00

Service Packs can be downloaded from http://support.rockwellautomation.com.

* RSNetWorx for EtherNet/IP Version 5.00 or higher is required for the Data Integration feature in RSLogix 5000.
Hardware

RSLogix 5000 Version

V15.02 / V15.01 / V14.01 / V14.00 V13.04 / V13.03 / V12.06 / V12.05 / V11.16 / V11.15 / V10.07 / V10.06 /
V15.00 V13.02 / V13.01 / V12.04 / V12.03 / V11.14 / V11.13 / V10.05 / V10.04 /
V13.00 V12.02 / V12.01 / V11.12 / V11.11 / V10.03 / V10.02 /
V12.00 V11.10 V10.00
Controllers

ControlLogix L55 – Series A, L61 – Series A & B, L1 – Series A, L1 – Series A, L1 – Series A, L1 – Series A,
1756-L1, -L53, -L55, Version 15.03 Version 14.2 Version 13.34 Version 12.30 Version 11.35 Version 10.24
-L61, -L61S, -L62, - L61 – Series A & B, L61S – Series B, L55 – Series A, L55 – Series A, L53 – Series A, L53 – Series A,
L62S, -L63, - Version 15.03 Version 14.33 Version 13.34 Version 12.27 Version 11.28 Version 10.24
L60M03SE L62 – Series A & B, L62 – Series A & B, L61 – Series A & B, L61 – Series A & B, L55 – Series A, L55 – Series A,
Version 15.03 Version 14.2 Version 13.44 Version 12.42 Version 11.32 Version 10.28
L63 – Series A & B, L62S – Series B, L62 – Series A & B, L62 – Series A & B, L63 – Series A, L63 – Series A,
Version 15.03 Version 14.33 Version 13.44 Version 12.42 Version 11.27 Version 10.32
L60M03SE – Series L63 – Series A & B, L63 – Series A & B, L63 – Series A & B,
A, Version 15.03 Version 14.2 Version 13.44 Version 12.42
L60M03SE – Series
A, Version 13.10
FlexLogix L34 – Series A & B, Not applicable L33 – Series A, L33 – Series A, L33 – Series A, L33 – Series A,
1794-L33, -L34 Version 15.03 Version 13.33 Version 12.28 Version 11.26 Version 10.16
L34 – Series A & B, L34 – Series A & B, L34 – Series A & B,
Version 13.33 Version 12.28 Version 11.26
CompactLogix L43 – Series A, Not applicable Not applicable Not applicable Not applicable Not applicable
1768-L43 Version 15.03
CompactLogix L31 – Series A, Not applicable L20 – Series A, L20 – Series A, L20 – Series A, L20 – Series A,
1769-L20, -L30, - Version 15.03 Version 13.19 Version 12.17 Version 11.27 Version 10.13
L31, -L32C, -L32E, L32C – Series A, L30 – Series A, L30 – Series A, L30 – Series A, L30 – Series A,
L35CR, -L35E Version 15.03 Version 13.19 Version 12.17 Version 11.27 Version 10.13
L32E – Series A, L31 – Series A, L35E – Series A,
Version 15.03 Version 13.33 Version 12.38
L35CR – Series A, L32C – Series A,
Version 15.03 Version 13.33
L35E – Series A, L32E – Series A,
Version 15.03 Version 13.34
L35CR – Series A,
Version 13.33
L35E – Series A,
Version 13.34
DriveLogix5720 Not applicable Not applicable Series A, Series A, Series A, Series A,
PowerFlex 700S Version 13.15 Version 12.24 Version 11.17 Version 10.16
DriveLogix5730 Series A, Not applicable Series A, Not applicable Not applicable Not applicable
PowerFlex 700S 2 Version 15.03 Version 13.20
SoftLogix Series A, Not applicable Series A, Series A, Series A, Series A,
1789-L60 Version 15.00 Version 13.02 Version 12.02 Version 11.11 Version 10.02
RSLogix Emulate Version 15.00 Not applicable Version 13.00 Version 12.02 Not applicable Not applicable
5000
Communication Modules

1734-ACNR Series A, Series A, Series A, Series A, Series A, Not applicable

Version 1.079 Version 1.078 Version 1.077 Version 1.075 Version 1.075
1734-AENT Series A, Series A, Series A, Series A, Series A, Not applicable
Version 1.033 Version 1.032 Version 1.030 Version 1.030 Version 1.030
1738-ACNR Series A, Series A, Series A, Not applicable Not applicable Not applicable
Version 1.079 Version 1.078 Version 1.077
1738-AENT Series A, Series A, Series A, Not applicable Not applicable Not applicable
Version 1.033 Version 1.032 Version 1.030
1756-CNB, -CNBR Series D, Series D, Series D, Series D, Series D, Series D,
Version 5.46, Version 5.45, Version 5.38, Version 5.36, Version 5.31, Version 5.27,
Series B, Series B, Series B, Series B, Series B, Series B,
Version 2.30, Version 2.30, Version 2.27, Version 2.27, Version 2.27, Version 2.27,
Series A, Series A, Series A, Series A, Series A, Series A,
Version 1.19 Version 1.19 Version 1.19 Version 1.19 Version 1.19 Version 1.19
1756-DHRIO Series D, Series C, Series C, Series C, Series C, Series B,
Version 6.1 Version 5.3 Version 5.3 Version 5.3 Version 5.3 Version 2.21
Series C, Series B, Series B, Series B, Series B,
Version 5.3 Version 2.21 Version 2.21 Version 2.21 Version 2.21
Series B,
Version 2.21
1756-DNB Series A, Series A, Series A, Series A, Series A, Series A,
Version 6.002 Version 6.002 Version 4.005 Version 4.002 Version 3.010 Version 3.010 or
Series B, 2.008
Version 6.002
1756-ENBT Series A, Series A, Series A, Series A, Series A, Series A,
Version 3.6 Version 3.6 Version 2.3 Version 1.61 Version 1.46 Version 1.30
1756-ENET Series B, Series B, Series B, Series B, Series B, Series B,
Version 2.7, Version 2.7, Version 2.7, Version 2.7, Version 2.7, Version 2.6,
Series A, Series A, Series A, Series A, Series A, Series A,
Version 1.18 Version 1.18 Version 1.18 Version 1.18 Version 1.18 Version 1.18
1756-EWEB Series A, Series A, Series A, Series A, Not applicable Not applicable
Version 2.2 Version 2.2 Version 1.2 Version 1.1
1757-FFLD Series A, Series A, Series A, Series A, Not applicable Not applicable
Version 1.1 Version 1.1 Version 1.1 Version 1.1
1768-ENBT Series A, Not applicable Not applicable Not applicable Not applicable Not applicable
Version 1.1
1769-SDN Series B, Series B, Series B, Series B, Series B, Series A,
Version 2.002 Version 2.1 Version 2.1 Version 2.1 Version 2.1 Version 1.1
1784-PCIC, -PCICS Series B, Series B, Series A, Series A, Not applicable Not applicable
Version 4.08 Version 4.08 Version 3.7 Version 3.7
1784-PCIDS Series A, Series A, Series A, Series A, Not applicable Not applicable
Version 2.008 Version 2.008 Version 2.008 Version 2.008
1784-PKTCS Series B, Series B, Series A, Not applicable Not applicable Not applicable
Version 4.08 Version 4.08 Version 3.7
1788-CN2DN Series A, Series A, Series A, Series A, Not applicable Not applicable
Version 1.023 Version 1.023 Version 1.023 Version 1.021
1788-CNC, -CNCR Series A, Series A, Series A, Series A, Series A, Series A,
Version 1.5 Version 1.5 Version 1.5 Version 1.5 Version 1.4 Version 1.4
1788-CNF, -CNFR Series A, Series A, Series A, Series A, Series A, Series A,
Version 1.6 Version 1.5 Version 1.5 Version 1.5 Version 1.4 Version 1.4
1788-DNBO Series A, Series A, Series A, Series A, Series A, Series A,
Version 2.002 Version 2.002 Version 2.002 Version 2.002 Version 1.002 Version 1.002
1788-EN2DN Series A, Series A, Series A, Not applicable Not applicable Not applicable
Version 2.002 Version 1.05 Version 1.05
1788-ENBT Series A, Series A, Series A, Series A, Series A, Not applicable
Version 2.1 Version 2.1 Version 1.28 Version 1.28 Version 1.28
1794-ACN15, Series A, Series A, Series A, Series A, Series A, Series A,
-ACNR15 Version 4.3 Version 4.3 Version 4.2 Version 4.2 Version 4.1 Version 4.1
1794-AENT Series A, Series A, Series A, Series A, Series A, Series A,
Version 2.12 Version 2.12 Version 2.12 Version 2.08 Version 1.90 Version 1.90
56AMXN Series B, Series B, Series B, Series B, Series A, Not applicable
Version 2.1 Version 2.1 Version 2.1 Version 2.1 Version 1.2
Motion Modules

1756-HYD02 Series A, Not applicable Series A, Series A, Not applicable Not applicable
Version 15.01 Version 13.2 Version 12.10
1756-M02AE Series A, Not applicable Series A, Series A, Series A, Series A,
Version 15.01 Version 13.2 Version 12.8 Version 5.5 Version 5.2
1756-M02AS Series A, Not applicable Series A, Not applicable Not applicable Not applicable
Version 15.01 Version 13.6
1756-M03SE Series A, Not applicable Series A, Not applicable Not applicable Not applicable
Version 15.05 Version 13.7
1756-M08SE Series B, Not applicable Series B, Series B, Series B, Series A,
Version 15.05 Version 13.7 Version 12.6 Version 11.7 Version 2.10
Series A, Series A, Series A, Series A,
Version 15.05 Version 13.7 Version 12.6 Version 11.7
1756-M16SE Series A, Not applicable Series A, Series A, Series A, Not applicable
Version 15.05 Version 13.7 Version 12.6 Version 11.7
1768-M04SE Series A, Not applicable Not applicable Not applicable Not applicable Not applicable
Version 15.05
1784-PM02AE Series A, Not applicable Series A, Series A, Series A, Series A,
Version 15.01 Version 13.2 Version 12.12 Version 5.4 Version 5.3
1784-PM16SE Series A, Not applicable Series A, Series A, Not applicable Not applicable
Version 15.05 Version 13.6 Version 12.11
SERCOS Drives

Kinetix6000 Version 1.85 Not applicable Version 1.80 Version 1.069 Version 1.060 Not applicable
(2094 Series)
Ultra3000 Version 1.50 Not applicable Version 1.40 Version 1.33 Version 1.32 Version 1.21
(2098 Series)
8720MC Series Version 3.85 Not applicable Version 3.80 Version 3.069 Version 3.064 Not applicable

1394C Series Version 1.85 Not applicable Version 1.80 Version 1.069 Version 1.060 Version 1.047

Other Products

DriveTools Software Version 3.01 Version 3.01 Version 3.01 Version 2.02 Version 2.02 Version 2.02
Firmware
Note that most of the modules supported by RSLogix 5000 utilize 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 CD-ROM or floppy disks shipped with RSLogix 5000.
Starting with RSLogix 5000 V10.00.00, you can access the ControlFLASH tool from within RSLogix 5000 (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, please review the ControlFLASH manual.

In addition, Rockwell Software Technical Support has created a web site from which you can download firmware images for
ControlLogix products. Go to http://support.rockwellautomation.com/ControlFlash/ for a matrix detailing the versions of firmware that
were released with each of the versions of RSLogix 5000 software, and to download the ControlFLASH firmware kits and release note
documents. Note that you will need your RSLogix 5000 serial number to complete the download.

RSLogix 5000 Separately Installed I/O Configuration Profiles

With Version 13 and above, RSLogix 5000 supports the ability for new I/O Configuration profiles to be delivered independent from the
RSLogix 5000 release. These profiles can be obtained independently and installed on a PC with RSLogix 5000 to extend the I/O
configuration support beyond the capabilities initially supported when RSLogix 5000 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 utilizing one of the supported platforms and the
configuration profile was not included with RSLogix 5000 check with the module / device vendor to determine if one is available.
Additionally, I/O configuration profiles for modules / devices from Rockwell Automation are generally provided with RSLogix 5000.
However, at times a module / 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 Support site http://support.rockwellautomation.com/.
The following table provides a listing of releases and there respective ability to support the field addition of I/O Configuration Profiles:

I/O Platform I/O Profile Communication Initial RSLogix 5000 Version

Methods Supported
Compact I/O (1769) Local to CompactLogix V13.00
Compact Block Safety I/O (1791DS) DeviceNet V14.00
POINT I/O (1734) ControlNet, EtherNet/IP V15.00
ArmorPoint I/O (1738) ControlNet, EtherNet/IP V15.00

Electronic Data Sheets

The version of RSLinx provided with this version of RSLogix 5000 includes an updated set of Electronic Data Sheets (EDS) files for
Rockwell Automation products. Installing this software ensures that RSLinx and RSNetWorx will be able to work with the new versions
of firmware. These EDS files are also available separately by contacting Technical Support (phone 440-646-5800), or via the internet
(http://www.ab.com/networks/eds/). You can install them using the EDS Hardware Installation Tool, located in the RSLinx folder in the
Windows Start Menu.
Installation Notes
Review these notes before attempting to install this version of the RSLogix 5000 software.

Prior to Installation
Keep the following considerations in mind before you install the RSLogix 5000 software:
ƒ Be certain that no copies of RSLogix 5000 are currently running.
ƒ Make sure that you have Administrator privileges (for your Windows 2000 or Windows XP operating system) on the machine on
which you want to install the software. You will not be able to complete the installation without these privileges.
ƒ Close all other applications before running the setup process.
ƒ If you want to perform online communications, you must install RSLinx in addition to RSLogix 5000.

Installing the Software

The following section describes installing RSLogix 5000 software.
1. Start the PC.
2. Insert the RSLogix 5000 installation CD into your CD-ROM drive.
The CD-ROM should autostart. If it does not autostart, run ausetup.exe from the root of the CD.

3. Select Install RSLogix 5000.

Note: If you already have a version of RSLogix 5000 installed on your computer and you are running Windows NT, you will need to
manually uninstall the older version. If you are running Windows 2000 or Windows XP, you may leave the older version installed on
your system.

4. Follow the directions that appear on your screen.

When prompted for a serial number, enter any sequence of characters, not longer than 10 characters. Use the F1 key if you need
help.

5. When prompted, click Yes to complete the activation of the software.

Follow the directions that appear on your screen.

6. Click on Finish to complete the installation.

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 CD of the RSLogix 5000 installation from the CD-ROM drive and store it in a safe place.

Starting RSLogix 5000 software

To start RSLogix 5000 software, click Start and then select Programs > Rockwell Software > RSLogix 5000 Enterprise Series >
RSLogix 5000 from the menu. (Note that if you are installing Version 9.0 or earlier, the path is Programs > Rockwell Software >
RSLogix 5000 > RSLogix 5000.)
If RSLogix 5000 does not start up or run properly, keep the following in mind:
ƒ Do you have the correct version of RSLinx software installed? RSLinx software provides communication between the controller and
your personal computer.
ƒ Does your computer have enough memory? Running RSLogix 5000 requires a minimum of 64 Mb of RAM.
ƒ Is the activation key installed?
Tip
Remember to use the Help function from within the application if you need help with a specific dialog or function. Press [F1] or
click the Help button on a dialog, or select Help from the menu bar.

Uninstalling the Software

To uninstall the software, do the following:
1. Choose Start > Settings > Control Panel.
2. Double click on Add/Remove Programs.
3. From the Add/Remove dialog, select RSLogix 5000-<version> and click OK.
You will be prompted to decide whether you wish to preserve any configuration data you have previously used.
Follow the prompts of the uninstaller, and RSLogix 5000 will be uninstalled from your computer.
New Features in This Release
The following new features and functionality have been added to this release of RSLogix 5000.

Integrated Phase Manager (Unit Batch)

Version 15 of RSLogix 5000 introduces the integration of the S88 phase state model in the Logix5000 controllers and in the
programming environment. The S88 phase state model can be used to easily address complex and simple batch applications. It can
also be used to address packaging applications (PackML). Phase Manager provides improved integration with RSBizWare Batch and
eliminates the need to use complex Phase Logic Interface (PLI) when using RSBizWare Batch. Phases can be sequenced either from
an RSBizWare Batch procedure for complex batch control applications or from a routine (i.e., SFC) in the controller for simpler batch
applications. RSLogix 5000 Version 15 includes a set of new instructions that allow phases to interact with an RSBizWare Batch
procedure or with a routine acting as a procedure in the controller. Additionally, RSLogix 5000 provides a manual phase state control
capability useful for startup and troubleshooting. The Phase Manager is included with RSLogix 5000 Professional and Full Editions and
is available as an option for the other editions (Standard, Mini, Lite). Without this option, phases can be viewed, uploaded and
downloaded but modification is inhibited.

Improved Module Creation

The process of creating modules in the IO Configuration has been improved with a redesign of the Select Module dialog. The new
dialog contains a familiar-looking tree control with modules grouped By Category and By Vendor as well as a means to save frequently
used modules to a Favorites tab. In addition there is a Find button to help you locate a module by entering a portion of the module’s
catalog number or description.

Ability to Add 1756 I/O at Runtime

In order to further extend the applicability of the ControlLogix platform in process applications, Version 15 of RSLogix 5000 provides the
ability to add 1756 I/O at runtime both in the local chassis and in a remote chassis over ControlNet and Ethernet. This feature provides
a method to add a direct connection to 1756 I/O without having to stop the operation of the process application. This feature is only
available in ControlLogix (1756) processors. When using ControlNet, the I/O that is added in a remote chassis goes into the
unscheduled bandwidth of ControlNet. See the Runtime Addition of 1756 ControlNet I/O White Paper (Publication LOGIX-WP006A-
EN-P for additional information and design considerations.

I/O on ControlNet via Unscheduled Bandwidth

Provided along with the ability to add 1756 I/O at runtime via ControlNet feature, is the ability to configure direct connected I/O as
unscheduled over ControlNet. This feature allows you to carry out simple ControlNet installations where scheduled networks are not
required. It is recommended that you use a dedicated ControlNet network or cable just for I/O and route the HMI, Message, and
RSLogix 5000 workstation traffic to a separate network. Be aware that RSNetWorx for ControlNet is required to set the Scheduled
Max (SMax), Unscheduled Max (UMax) and Network Update Time (NUT) and to set media configuration parameters. The Runtime
Addition of 1756 ControlNet I/O White Paper (Publication LOGIX-WP006A-EN-P provides additional information and design
considerations for using unscheduled ControlNet communications for I/O.

Third Party Vendor Sample Projects

Starting with the RSLogix 5000 V12 release, sample projects developed by third party vendors are included with the Rockwell
Automation sample projects. These sample projects are for products that can be used in conjunction with the Logix5000 platforms. To
access these projects, select Help -> Vendor Sample Projects from the RSLogix 5000 main menu. Refer to the documentation included
with the sample projects for support information. New Rockwell Automation sample projects include examples of finding the exact
motor position with Stegmann encoder and DriveLogix, Cam recovery using the MCSV instruction, PowerFlex 4 drives using
Ethernet/IP, absolute homing using Kinetix6000, reading the mode from an SLC or Micro Logix Controller, a Smart Belt System project,
and transmitting and receiving drive data through SynchLink.

CompactLogix 1768-L43 Controller Support

A new controller has been added to the CompactLogix family in this release of RSLogix 5000, the CompactLogix5343 (1768-L43). This
module has 2 MB memory capacity for standard logic programming and tags. This controller makes use of advanced processor
technology similar to the ControlLogix5563. It is unique in that it supports two backplanes of modules. The high speed 1768 backplane
is used for communications and with the Compact backplane is used for I/O.

Module Support (Catalog Numbers 1756, 1768, 1794, 1797, PowerFlex, 1305, 1336, 1397)
The RSLogix 5000 programming software now supports configuration of these modules:

1756
ƒ 1756-CN2 1756 ControlNet Bridge
ƒ 1756-CN2R 1756 ControlNet Bridge
ƒ 1756-CNB/E 1756 ControlNet Bridge
ƒ 1756-CNBR/E 1756 ControlNet Bridge, Redundant Media
ƒ 1756-DHRIO/D 1756 DH+ Bridge/RIO Scanner
ƒ 1756-EN2T 1756 10/100 Mbps Ethernet Bridge, Twisted-Pair Media
ƒ 1756-HSC added user interface 1756 High Speed Counter
ƒ 1756-IA32 32 Point 74V-132V AC Input
 ƒ 1756-M08SEG 8 Axis Generic SERCOS Interface

1768
ƒ 1768-ENBT 1768 10/100 Mbps Ethernet Bridge, Twisted-Pair Media
ƒ 1768-M04SE 4 Axis SERCOS Interface

1784
ƒ 1784-PKTCS PCI-based ControlNet Scanner

1794
ƒ 1794-IB16D 16 Point 24V DC Diagnostic Input, Sink
ƒ 1794-IE8H 8 Channel Analog Input /HART
ƒ 1794-IE12 12 Channel 24V DC Non-Isolated Voltage/Current Analog Input
ƒ 1794-IE8XOE4 8 Input/4 Output 24V DC Non-Isolated Analog
ƒ 1794-OE12 12 Channel 24V DC Non-Isolated Voltage/Current Analog Output
ƒ 1794-OB16D 16 Point 24V DC Diagnostic Output, Source
ƒ 1794-OE8H 8 Channel Analog Output /HART

1797
ƒ 1797-IE8H 8 Channel Analog Input /HART
ƒ 1797-OE8H 8 Channel Analog Output /HART

PowerFlex
ƒ PowerFlex 70 EC-C PowerFlex 70 EC Drive via 20-COMM-C
ƒ PowerFlex 70 EC-E PowerFlex 70 EC Drive via 20-COMM-E
ƒ PowerFlex 700H-C PowerFlex 700H Drive via 20-COMM-C
ƒ PowerFlex 700H-E PowerFlex 700H Drive via 20-COMM-E
ƒ PowerFlex 700S 2P-200V-C PowerFlex 700S Phase 2 Drive (208/240V) via 20-Comm-C
ƒ PowerFlex 700S 2P-200V-E PowerFlex 700S Phase 2 Drive (208/240V) via 20-Comm-E
ƒ PowerFlex 700S 2P-400V-C PowerFlex 700S Phase 2 Drive (400/480V) via 20-Comm-C
ƒ PowerFlex 700S 2P-400V-E PowerFlex 700S Phase 2 Drive (400/480V) via 20-Comm-E
ƒ PowerFlex 700S 2P-600V-C PowerFlex 700S Phase 2 Drive (600V) via 20-Comm-C
ƒ PowerFlex 700S 2P-600V-E PowerFlex 700S Phase 2 Drive (600V) via 20-Comm-E

1305
ƒ 1305-ACDrive-EN1 1305 AC Drive via 1203-EN1

1336
ƒ 1336E-IMPACTDrive-EN1 1336 IMPACT Drive via 1203-EN1
ƒ 1336F-PLUSIIDrive-EN1 1336 PLUS II Drive via 1203-EN1
ƒ 1336R-REGENBrake-EN1 1336 REGEN Brake via 1203-EN1
ƒ 1336T-FORCEDriveCNA-EN1 1336 FORCE Drive (ControlNet Adapter) via 1203-EN1
ƒ 1336T-FORCEDrivePLC-EN1 1336 FORCE Drive (PLC Comm Adapter) via 1203-EN1
ƒ 1336T-FORCEDriveStd-EN1 1336 FORCE Drive (Standard Adapter) via 1203-EN1

1397
ƒ 1397 DigitalDCDrive-EN1 1397 Digital DC Drive via 1203-EN1
Enhancements in This Release

The following enhancements to existing features have been made in this release of RSLogix 5000.

ƒ Help Menu Link to Rockwell Automation Literature Library – The Help Menu in RSLogix 5000 has been updated to include an
internet link to the Rockwell Automation Literature Library web site. This site provides electronic access to the latest PDF copies of
documentation and manuals for Rockwell Automation products. To function properly you will need an internet browser installed on
your PC and access to the internet.
ƒ Report Enhancements Configurable Margins – With this release of RSLogix 5000, you can set the page margins for reports;
left, right, top and bottom to customize the page format for specific needs. To set the margins, select menu File > Page Setup or
from the Generate Report dialog click Page Setup.
ƒ Open “File Copy” of Locked or Read-Only Project – RSLogix 5000 only allows one user to open a project file at a time. In
previous versions when a second user attempted to open the file they were notified that the file was already open and the request
was rejected. In RSLogix 5000 V14, when the second user attempts to open a project file that is already open, they will be
prompted to open a copy of the file. The copied project will be indicated by (File Copy) after the file name in the RSLogix 5000 title
bar. The same mechanism works for projects that have been set as read-only.
ƒ Tag Properties Dialog – The information on the tag properties dialog has been reorganized and streamlined to provide simpler tag
configuration. In addition, the array dimension creation has been rearranged on the tag data type dialog to ensure that data is
maintained when adding a dimension.
ƒ Tag Browser – The tag browser has been enhanced in this release to allow for easier selection of tags. In particular, the new tag
browser allows you to select tags by controller or program scope (or both) and you can filter tags by type. The enhanced tag
browser also provides a visual identification (icon) of the controller tags.
ƒ Tag CSV Export/Import – The tag CSV Export/Import feature has been enhanced to allow for all of the tag attributes to be
exported. This means that produced and consumed tags configuration is now fully supported in the CSV format. Previously you
had to manually re-configure produced/consumed tags after an import operation.
ƒ I/O Configuration Tree View – In this release the I/O Configuration tree view has been changed to closely resemble that of
RSLinx. Specifically, the tree view now shows icons for the chassis, the local controller, and the networks associated with
communication modules. This provides consistency with RSLinx and provides a more intuitive view of the hardware configuration.
ƒ Controller Serial Number Matching – This version of RSLogix 5000 provides a mechanism to match the project (ACD) to a
specific Logix5000 controller by comparing the controller’s serial number stored in the project to the serial number of the target
controller. This allows validation during a download operation that the project is being loaded into the correct controller. This Serial
Number matching feature can be set by opening the Controller Properties dialog and selecting the Advanced tab. Check the Match
Project to Controller option and enter the Logix5000 controller’s Serial Number.
ƒ Change Module Revisions On/Offline – This release of RSLogix 5000, provides the capability to change the major revision for
bridge modules online and offline. With previous versions of RSLogix 5000, it was necessary to go offline, delete the bridge and all
of the modules under it, and then re-enter the bridge module and all of the modules under it.
ƒ Additional Security Granularity – Several new security actions were added to RSLogix 5000 in this release. These additional
security actions provide a finer granularity of options when securing RSLogix 5000. PLEASE NOTE: If security is enabled, when
version 15 is started up for the first time, then these new security actions are automatically added to the RSI Security Server and
set to the default access level. If the default access level is configured as “deny”, some controls will be disabled and this may
make it appear that RSLogix 5000 is not functioning correctly when in fact additional security restrictions have been put in place. If
security is enabled, the new security actions should be reviewed and set to the appropriate access level. (x54686)
ƒ Additional MCLM & MCCM Termination Types – Two new termination types have been added for the coordinated-motion
instructions MLCM and MCCM. The “Follow Contour Constrained Velocity” and “Follow Contour Unconstrained Velocity”
termination types are targeted for applications where it is necessary to maintain the contour (i.e., path), maintain a constant
acceleration/deceleration, and/or maintain a constant velocity on tangential intersections
ƒ MSG Instruction Support for SERCOS-Interface IDN Read/Write – This release of RSLogix 5000 allows the MSG instruction to
be configured for access to SERCOS IDentification Number (IDN) values via two new message types: SERCOS IDN Read and
SERCOS IDN Write. (Requires Motion module firmware revision 15.06 or greater.)
ƒ MSG Instruction Support for Ring Phase – This release of RSLogix 5000 allows the MSG instruction to be configured for
SERCOS Ring Phase control. Two new CIP Generic message Service Types were added for SERCOS Ring Phase Get/Set.
Also, an associated Transition To Phase setting was added to the SERCOS Interface tab of SERCOS module properties.
(Requires Motion module firmware revision 15.06 or greater.)
ƒ Add New UDTs and Delete Un-Referenced UDTs Online – With this version of RSLogix 5000, you are allowed to add, modify,
and delete un-referenced UDTs (User Defined Data-Type) online. With previous versions of RSLogix 5000, this operation was only
allowed while offline. This enhancement will reduce integration and maintenance time.
ƒ Dynamic Axis Inhibit – RSLogix 5000 Integrated Motion axes now have the ability to be dynamically inhibited and uninhibited
during execution of program logic using the new InhibitAxis attribute of the SSV and GSV instructions.
ƒ ControlFLASH Update of SERCOS Drives via SERCOS Ring – This release of RSLogix 5000 supports the direct firmware
update of Rockwell Automation SERCOS drives using ControlFLASH. (Requires Motion module firmware revision 15.06 or
greater.) Additional detail is available in the Application Notes section of these Release Notes; refer to the section entitled
“ControlFLASH Update of Rockwell Automation (RA) Sercos Drives via SERCOS Ring.”
ƒ SFC Action String Indicator Tags – With the introduction of the Sequential Function Chart programming in release v11 of
RSLogix 5000, you have the ability to set a tag as an indicator in an action element. When the logic is executed, the tag’s numeric
value is displayed in the action, providing a convenient way to view status information on the particular operation of that action. In
Version 15 this functionality has been extended to include tags with a STRING data type tag, which now gives you the ability to
displaying a text string in the action.
ƒ Program Limit Increased to 100 – RSLogix 5000 version 13 and earlier limited the number of programs per task to 32. With this
release the limit was increased to 100 for ControlLogix controllers, providing more flexibility in dividing your application into
manageable modules. This increased limit also applies to the new Equipment Phases, which are included as part of the Phase
Manager feature.
Important Changes in This Release
The following items explain changes that have been made in this or previous releases in the way that RSLogix 5000 software works,
compared to previous releases.

Controller Memory Changes

This revision of Logix5000 controllers may require more memory than previous revisions:

• Before upgrading to this revision, check the amount of unused memory that you have in the controller. To upgrade to this revision
you may have to add an expansion memory card to the controller or use a larger memory card.
• To estimate the additional memory that your project will require, use the following table.
• For additional information about controller memory issues refer to the Knowledgebase document G19984 at
http://support.rockwellautomation.com

Additional memory to upgrade to firmware revision 15.x

If you have this

firmware revision
(add all that apply): Component Increase per instance
14.x or earlier Tag that uses COORDINATE_SYSTEM 60 bytes
data type
Axis tags (all AXIS data types) 4 bytes

13.x or earlier Program 12 bytes

Task 4 bytes
User-Defined Data Type 4 bytes
I/O module 16 bytes
Produced or consumed tag 8 bytes

12.x or earlier I/O Module with Comm Format = Rack 90 bytes

Optimization
I/O Module with Comm Format = other than 144 bytes
Rack Optimization
CompactLogix 1769 I/O Module 170 bytes
Bridge Module with Comm Format = None 160 bytes
Bridge Module with Comm Format = Rack 220 bytes
Optimization

11.x or earlier Tags that use MOTION_INSTRUCTION data 4 bytes

type
Tags that use AXIS_SERVO_DRIVE data type 288 bytes
Tags that use all other AXIS_* types 264 bytes
Output cam execution targets 648 bytes
Number of User-Defined Data Types 128 bytes
Indirect addresses in single dimension arrays of (-60 bytes)
a user-defined data type

10.x or earlier Project for a ControlLogix5555 only 1200 bytes

Project for a ControlLogix5563 only 1200 bytes
Programs 12 bytes
Routines 16 bytes

9.x or earlier Project for a ControlLogix5550 only 1200 bytes

Tag that uses MESSAGE type 376 bytes

8.x or later Axis tags (-21600 bytes)

8.x or earlier Output cam execution targets 5404 bytes

Motion group 32 bytes

7.x or earlier Project 1050 bytes

 Tags 0.55 bytes (average)
Axis tags 21600 bytes
Messages that: 2000 bytes
ƒ Transfer more than 500 bytes of data and
ƒ Target a controller in the same chassis

6.x or earlier Base tags 24 bytes

Alias tags 16 bytes
Produced and consumed tags
DINT data type 12 bytes
REAL data type 12 bytes

6.x Routines 68 bytes

Import Export Changes

Import Export Major/Minor Revision – Beginning with the V9.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 will export *.L5K files with specific IE Version
numbers. RSLogix 5000 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 previous 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.

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

RSLogix 5000 Version Import Export Version

15.xx 2.6
14.xx 2.5
13.xx 2.4
12.xx 2.3
11.xx 2.2
10.xx 2.1
9.00 2.0
5.02 1.2
2.xx, 6.xx, 7.xx, 8.xx 1.1
1.21, 1.23 1.0
1.10, 1.11 0.4

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

I/E Format for Structured Text Routines – The Import Export format for Structured Text routines was changed in V12. The
STX_ROUTINE and END_STX_ROUTINE delimiters were changed to ST_ROUTINE and END_ST_ROUTINE, respectively. RSLogix
V12.00 or later software 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 V12 or later Structured Text routine into V11 software will fail.

Online Editing Views for SFC and ST – With the addition of online editing for SFC and ST in V13, 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, so V13 generated L5K
files with SFC or ST online edits should not be imported into previous versions.

Motion Modules Revision – The major revision of the 1756-based motion modules has changed to 13. If you have export files (*.L5K)
that were created in previous versions of RSLogix 5000 and you attempt to import them in V13, an error may be generated. The error
message is "Error: Line xxx: Invalid catalog number." To work around the problem, edit the *.L5K file, find the MODULE section for the
1756-based motion module and change the line Major := x.x to Major := 13; save the file and retry the import.

Multi-line Rung Comments – Beginning with Import Export version 2.2 in V11, multi-line rung comments (with hard
returns) are no longer exported as one long string (in double-quotes). Instead, each line of a multi-line rung comment is on
a separate line in the .L5K file with double-quotes around each line. When imported, the multiple quoted strings are
concatenated to form the rung comment. This improves the readability of the .L5K text file using the existing multiple-
string capability of the rung comment syntax. Note that older formatted rung comments will still import correctly.
Datatypes and Keywords – If you are importing an older version project (prior to V11) 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 V11 as data type names. Normally, user-defined data types which
used 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 problem, 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).

Refer to the descriptions of these motion axis tag and axis object changes elsewhere in the release notes for clarification. 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>.
Anomalies Corrected in This Release

RSLogix 5000

A few product anomalies discovered in Version 15.01 have been addressed in Version 15.02. These include:
• RPI is not fully updated for modules with multi-connection points, such as the 1756-DNB module (x61418)
• Difficulty producing large tag arrays (x61479)
• Online RPI doesn’t match information on tag properties after CSV import. NOTE: Affected projects currently residing in a controller
must be re-downloaded in order to update the online RPI value. (x63398)
• Download of a modified insert (i)-rung uploads as a normal rung (x65421)
• 1794-IE12 Module Properties Configuration Tab shows incorrect voltage/current and configuration ranges (x66189)
• Fatal Error on edit operations after copy/paste of FBD element or SFC element (x66190)
• Motion K-constant Calculate utility does not support fractional rotary Unwind (x66192)
• Unable to select bit zero from the Tag Browser Bit Picker (x66193)

A few product anomalies discovered in Version 15.00 have been addressed in Version 15.01. These include:
• Fatal Error uploading project file (x53813, x59376)
• Paste operation takes much longer in V15 than in previous releases (x57961)
• Cross-reference does not display tags used in Structured Text embedded in SFC logic (x58035, x59130)
• After installing V15.00, 1756-CNB series E erroneously appears as a valid selection for V13 (x58072)
• Find Next becomes stuck on rung (x58117)
• V15.00 Revision Directory doesn’t know about re-release of earlier versions. If you attempt to use RSLogix 5000 with Version
15.00 installed along with Version 11.16, Version 12.06, or Version 13.04 then unexpected behavior will be encountered. (x58394)
• When a boolean tag value is toggled then, if the tag value is rapidly toggled back to its original value, RSLogix 5000 may not
display the new value. (x58934)
• Fatal Error trying to open, cut, or copy and FBD routine (x59110)
• Some characters of exported tag descriptions cannot be viewed using Microsoft Excel. Note that the resolution of this anomaly
involved a change to the file format for the exported CSV file. The format was reverted from UTF-8 format back to the ASCII
format that was used in version 13 and earlier of RSLogix 5000. This enables Microsoft Excel to interpret European characters,
which are represented by extended ASCII symbols. However, Unicode characters cannot be exported to an ASCII formatted CSV
file using version 15.01 of RSLogix 5000. (x59186)
• Opening the Tag Browser and tag auto-completion take longer in V15 than in V13 (x59458)
• Source Key gets corrupted when using Japanese operating system (x59542)
• Function Block Diagram JSR, SBR, and RET blocks are incorrectly marked as verified when there are duplicate inputs or outputs
(x59936)
• Fatal Error creating 1794-IE12 module on ControlNet (x60143)
• Fatal Error removing force tag view has been scrolled and tags expanded/collapsed (x60176)
• Unable to import 1756-IB32 or 1756-OB32 modules (x60278)
• Fatal Error uploading project when using array larger than 65535 in a JSR or SBR (x60328)

Many product anomalies have been addressed since Version 13. The most significant of these include:
ƒ Fatal Error searching within all routines (x55441)
ƒ Unable to upload FBD project from the controller (x55349, x53813)
ƒ Feedback loss with fault action of Status Only may cause unexpected motion (x55065)
ƒ Fatal Error with many Tag Editor windows opened (x54885)
ƒ System Unwind results in absolute moves in the wrong direction (x54814)
ƒ Cross Reference shows OREF as a non-destructive reference (x54357)
ƒ ControlNet schedule data removed if specified .xc file does not exist (x54210)
ƒ Controller fault executing AVE, STD, SRT, or SIZE instruction if Dim-To-Vary input is incorrectly specified (x54081)
ƒ The fractional K-constant entry can calculate numbers incorrectly which causes overflow (x53068)
ƒ Fatal Error deleting an empty FBD text box (x52890)
ƒ Middle portion of long rung omitted from printed report (x52784)
ƒ FBD sheets are deleted when starting a pending edit (x52336)
ƒ Printing ladder routines with the embedded cross reference enabled only the first page is printed (x52092)
ƒ Routines opening unexpectedly during search of routines (x51944)
ƒ During import of an L5K file, the Motor Feedback Resolution attribute for AXIS_SERVO_DRIVE tags is always set to 4000
(x51837)
ƒ Trending causes RSLogix 5000 to adapt operating systems regional settings (x51608)
ƒ Fatal Error with many FBD routines opened (x51542)
ƒ CTree Error when opening project file due to McAfee VirusScan Enterprise software requires disabling scanning of RSLogix
5000.Temp folder (x51417)
ƒ Enter key does not execute highlighted button on Find dialog and Find Next should have focus each time it is launched (x44362,
x49310)
ƒ Rungs imported out of order on partial import of 256 or more rungs (x47746)
ƒ Setting name on unnamed module online appears to work but name is not saved after upload (x47669)
ƒ Browse Logic right/left arrow keys work differently than Controller Organizer (x47018)
ƒ Tag Editor description now only shows top line if embedded CR (x46840)
ƒ The MCLM and MCCM coordinate-motion instructions allow axis Position operands of type INT and DINT, but when the instruction
is executed, the resulting axis position is incorrect (x46651)
ƒ "Invalid Connection size" message does not include incompatible structure name (x45061)
ƒ Almost 'Any' key to Start Pending Rung Edits while online (x44093)
ƒ XML Import (used by Add-On Profiles, Partial Import, Automation Desktop) doesn't work properly if there is an ampersand in the
customer name (x49501)

ControlLogix556x

Refer to the Firmware Release Notes for the ControlLogix family of controllers (Publication 1756-RN603) to review the most significant
anomalies that have been addressed.
Known Anomalies
Keep the following concerns/limitations in mind when using this release.

Watch Pane Allows Data Values to Be Edited After Watch Pane has been Closed
When the Watch Pane is open, it is possible to edit data values. When the Watch Pane is then closed, it may still be possible to edit
data values. This permits data values, which are not visible to the user, to be inadvertently edited. When this condition exists, it will
persist until the user navigates to some other location within RSLogix 5000. Avoid this issue either by using the “View -> Watch” main
menu selection to close the Watch Pane or by navigating to some other location within RSLogix 5000 after closing the Watch Pane.
The problem exists offline as well as online to a controller. (x66439)

RSMacc Audit Does Not Display Unicode Characters

When the description of a task, program, routine, module, trend, etc. is edited, any audit records displayed using RSMacc Audit will not
properly display Unicode characters. (x63773)

RSLogix 5000 Fatal Error Inserting Unicode Characters

RSLogix 5000 employs a feature which allows the user to position the caret on an edit control and, without explicitly opening the edit
control, to begin entering character data from the keyboard. This action will cause RSLogix 5000 to automatically open that edit control
as character data entry continues. For many of the edit controls in RSLogix 5000, using this auto-open feature when inputting Unicode
characters using an Input Method Editor (IME) will result in unexpected behavior or in a Fatal Error.

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 which 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 appears in the upper left corner of the display,
then you have started to input an 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.

(x59649, x59650, x59825)

DriveLogix “Major Fault On Controller…” Checkbox Display Not Consistent with Firmware Behavior
For the DriveLogix5730 controller, the “Major Fault On Controller If Connection Fails While in Run Mode” checkbox on the Connection
tab of the CompactBus 1769 Virtual Backplane Adapter is always displayed as checked. This checkbox cannot be modified.
DriveLogix5730 controller firmware revision 15.04, will always behave as if this checkbox is not checked. When using revision 15.04 of
the DriveLogix5730 firmware, a major fault on the 1769 virtual adapter will not cause the controller to fault. Individual I/O modules can
still be configured to cause the controller to fault in the event of a major fault on an I/O module.

RSLogix 5000 Fatal Error Opening LD Routine with Component Browser Open in ST Editor
When using the Structured Text Editor, there are a number of “browsers” that can be opened to allow selection of RSLogix 5000
components such as tags, routines, programs, etc. Attempting to open a Ladder Diagram routine while one of these component
browsers is displayed in the Structured Text Editor will result in a Fatal Error. This Fatal Error can be avoided by first closing the
component browser, by either selecting an item from the list or clicking the mouse somewhere in the ST Editor window. Note that
besides being used to edit Structured Text routines, the ST Editor is also used to edit Action bodies and Transition conditions in
Sequential Function Chart routines. (x60317)

RSLogix 5000 Fatal Error Importing Obsolete CompactLogix Project

When using version 15 of RSLogix 5000 to import an L5K project file for an obsoleted CompactLogix controller, such as the 1769-L30
controller, the user is prompted to convert the project to a processor type that is supported in V15. If the user selects a processor type
from outside the CompactLogix family of controllers, the import may result in a Fatal Error. This Fatal Error will not occur if a V15
supported CompactLogix processor type, such as the 1769-L31, is selected. Once the CompactLogix project has been successfully
imported, it can then be converted to any other controller type by using the Change Controller button on the Controller Properties
dialog. (x58737, x58966)

Unable to Import CompactLogix Project from RSLogix 5000 Versions prior to Version 10
It is not possible to use version 15 of RSLogix 5000 to import an L5K project file that was created with RSLogix 5000 software versions
prior to version 10 if that project file is for any CompactLogix controller. The project must first be imported using version 10, 11, 12, or
13 of RSLogix 5000. Once the CompactLogix project has been successfully imported, it can then be either (a) exported to a new L5K
file and then imported using version 15 of RSLogix 5000 or (b) directly converted to version 15 of RSLogix 5000 using the Change
Controller button on the Controller Properties dialog. (x58967)

RSLogix 5000 Fatal Error after Declining to Continue with Conversion

When using the Change Controller button on the Controller Properties dialog to convert a project forward to version 15 of RSLogix 5000
while at the same time changing controller type, the user is presented with a warning dialog asking the user to confirm the conversion
operation. If the user then clicks “No”, indicating that they no longer wish to continue with the conversion, the user must wait until the
original project is reloaded. Attempting to perform operations before the project is reloaded, such as opening a file, may result in a
Fatal Error. (x58982)

Security Option for Motion: Modify Configuration Allows Modification on Module Properties
With the security option “Motion: Modify Configuration” configured, you should be prevented from modifying motion configuration. You
are prevented from changing axis association to a module from the Axis Properties dialog but are erroneously allowed to make this
change from the Module Properties dialog. To secure the axis association configuration on the Module Properties dialog, configure the
security option “Module: Modify Properties”. This will secure all of the tabs of the Module Properties dialog, including the Axis
Association tab. (x55583)

RSLogix 5000 Stops Logging Messages to RSMACC/RSAudit after Uninstalling FTAP Version 2.0
As part of the installation of RSLogix 5000 versions V15 and earlier, Factory Talk Diagnostics files versions earlier than 2.00 are also
installed. When Factory Talk Automation Platform (FTAP) version 2.0 is installed (either separately or as part of another product
install), these Factory Talk Diagnostics files are upgraded. If you then uninstall FTAP 2.0, the upgraded Factory Talk Diagnostics files
will no longer function, and RSLogix 5000 will be unable to log audit and diagnostic messages. When this occurs, you can correct the
problem 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 Factory Talk Diagnostics files. (x55161)

Motion Commands May Not Log Messages to RSMACC/RSAudit

Not all motion commands will record the action in the audit log. Specifically, the following operations will not produce logged messages
while online with the equipment:
ƒ Direct Motion Commands
ƒ Hookup Test like “Test Marker”, “Test Feed”, and “Test Command and Feedback”
ƒ Axis tuning actions: “Start tune” and “Apply tuning”
ƒ Clearing faults
These operations may result in axis movement commanded by the user without logging a message to RSMACC/RSAudit. (x46659,
x46660, x46661)

RSLogix 5000 Fatal Error if GDI Objects Exceed OS Limit

If you are working on a large project (especially with a lot of graphical routines) and you perform an operation that causes the number of
GDI objects to exceed 10,000 (on Windows XP) or 16,384 (on Windows 2000), then the result is an RSLogix 5000 fatal error.
Operations which increase the number of GDI Objects include language editors, tag editor, trending, search and replace, and others.
To work around this problem, avoid opening large numbers of editors simultaneously, doing large search and replace operations, and
consider closing and reopening RSLogix 5000 more frequently. (x48079)

File Conversion Issue for Axis Parameters in a Motion Project Referencing MPL-B300 Series Motors
In the Motion database for Version 15 of RSLogix 5000, the Maximum Rated Current (I-rated) value for the MPL-B300 460 volt series of
motors has been lowered by approximately 7%. If a project created in Version 13 or earlier contains an Axis_Servo_Drive type axis
which is configured with an MPL-B300 series motor (B310, B320, B330), then when this project is opened in Version 15, the axis
parameters will be based on this lower Maximum Rated Current value. The values for axis parameters that are calculated based on
Maximum Rated Current will depend on whether the project file being opened is an L5K file or an ACD file.

If the file being opened is an L5K file, then when the file is imported to Version 15, axis parameters that are calculated based on
Maximum Rated Current may be set to the default value of 0.

If the file being opened is an ACD file, then when the file is converted to Version 15, axis parameters that are calculated based on
Maximum Rated Current may be out of range. In this case the user must correct these parameter values on the Axis Properties.

To workaround this problem, for a project containing Axis_Servo_Drive type axes configured with MPL-B310, MPL-B320, or MPL-B330
motors, First, open the ACD file and convert to Version 15, Next, on the Axis Properties of axes configured with MPL-B300 series
motors, verify that proper values are displayed for the following axis parameters.

Torque/Force (on the Tune tab)

Peak Torque/Force Limit (on the Limits tab)
TorqueLimitPositive (accessed using the Set Custom Limits button on the Limits tab)
TorqueLimitNegative (accessed using the Set Custom Limits button on the Limits tab)
 StoppingTorque (accessed using the Set Custom Stop Action button on the Fault Actions tab)

(x56176, x56489)

AutoFlash Updates for Motion Modules Across Bridged Serial Ports

AutoFlash firmware updates of motion modules does not work if the target chassis is reached via a bridged connection over a serial
port. For example, if you navigate from one chassis out the serial port of a controller into the serial port of another controller in a
different chassis which contains motion module(s), you will not be able to AutoFlash update the motion module(s). To workaround this
issue, navigate to the chassis with the motion modules through another communication path that does not involve bridging serial ports
or use the ControlFLASH tool to update the firmware. (x45686)

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 problem, select Aux Rev as the units when configuring a Loop Configuration using
Dual/Auxiliary feedback. (x43750, x43870, x44775)

Motion Group Configfault Bit Only Cleared if Motion Task Starts

In cases where a motion_group.ConfigFault fault is set at initial Program or SERCOS Ring startup, if a Configuration Fault exists for the
Motion Group, the fault will not clear until the motion task can start. With multiple motion modules a Keying error on one can cause this
condition, this can cause potential confusion in tracking the root of the problem, as the fault may not be reflected back to the Group or
Axis Fault icons. Verification that motion task is running can be done via the Motion_Group Properties, Scan Times. (x43689)

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 problem put the controller into Remote Run or Program Mode or unlock the controller.
(x43429, x41415)

Re-aliasing Tags in FBD Input References May Cause Fatal Error During Download
If you have alias tags in FBD Input References (IREFs) and you change the scope of the tag that is aliased, you may get a Fatal Error
in RSLogix 5000 when downloading your project. For example, if you use a program-scoped alias tag MyTagAlias in an IREF and the
base tag MyTag is also program-scoped and then you delete MyTag and re-create MyTag as a controller-scoped tag, the software may
Fatal Error during download. To work around the problem, either avoid changing the scope of alias tags used in IREFs or delete the
IREFs and recreate them after then new base tag has been created. (x42574)

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 a problem with the Windows Help compiler. To display the original topic, click Help Topics and re-
select the original topic. (x 39239)

Structured Text and Project Component References

The Structured Text (ST) Editor manages the references made in application code to project components (e.g. tag names, routine
names, program names, task names, and module names) in order to ensure the application code continually points at the intended
component. This ensures that operations such as a tag rename are reflected in the code automatically, thus avoiding the need to
manually search and replace references within the code after a tag rename has occurred. Note that this operation is identical for both
standalone ST subroutines and ST statements embedded within a SFC routine.

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)

Structured Text Editor Does Not Support REAL#NNN.NN Format

The following syntax is defined by IEC 61131-3 as part of a real literal, REAL#NNN.NN. In the Structured Text language in RSLogix
5000, this syntax is not valid and will not verify. To avoid the problem, do not use strings of this form in RSLogix 5000. (x33122)

SFC Wire Routing in Sequence Loops

In some SFC charts involving sequence loops, the automatic routing of wires may result in the wire passing through the SFC
element(s). In order to correct this wiring problem try these recommendations:
ƒ If a wire passes through an element, move the element to the left or right a few grid spaces. Do not move the branch.
ƒ Move another element connected to the wire the opposite direction a few grid spaces. This will route the wires such that they
will be visible.
ƒ Move elements that are wired to each other into a more vertical alignment. This will adjust the wire paths.
ƒ Move a branch vertically to a different position, to lengthen the vertical distance between elements.
ƒ Jog elements right or left a grid unit at a time to straighten out crooked lines.
ƒ Save your project. (x28417)

Copy/Paste of SFC Elements Displays Incorrect Error Message

If you copy and paste an SFC element (Step, Action, Transition, Stop) one of two error messages will be displayed in the Output
window Errors tab in the format:
Error: B1, Step, Step_001, Tag "Step_001" created. Tag "Step_000" already exists.
Error: B1, Step, Step_006, Tag "Step_006" created. Tag "Step_006" already exists.
In both cases, the name in the error message correctly indicates the name of the tag that was created. This message is reported
regardless of whether a conflict really exists, and in some cases the tag will be renamed unnecessarily. (x32814)

Project Re-Verification Operations

If you perform an operation that requires re-verification of the entire project (e.g. changing the controller type, compacting the database,
or importing) the operation will complete successfully but may take an extended amount of time. Projects with FBD routines with large
blocks (many visible parameters) and numerous input and output references are particularly sensitive to this re-verification time. The
amount of time will vary depending on the complexity and size of the project. (x33403)

Error Accessing Motion Module Properties After Import

The export format for the 1756-M02AE catalog number was corrected in V9.00. If you manually edit an L5K file for a release prior to
V9.00 and change the catalog number it will not import correctly. A Fatal Error will occur when you access the module properties.
(x28541)

Runtime Error Opening Trend Chart Properties

If your computer is running low on registry quota, you may observe a C++ Runtime error when attempting to open the properties of a
trend chart in RSLogix 5000. To correct this problem, increase the maximum registry size. The maximum registry size is accessed from
the My Computer, System Properties, Performance, Virtual Memory dialog. The recommended size is two times the current size plus
20%. (x26487)

Output Cam Execution Targets Not Converted

In previous versions of RSLogix 5000 that supported output cam functionality, the default number of execution targets supported per
axis was set to four and you could not modify the number. When downloaded to a controller, enough memory was reserved for four
execution targets even if only one was used. In this release of RSLogix 5000, an Output Cam Execution Targets field has been added
to the Axis Properties dialog box that allows you to set the needed number of execution targets.

If you have routines with Motion Arm Output Cam (MAOC) instructions created in versions of RSLogix 5000 prior to V9.00 and you
convert them to V13.00, the MAOC instructions will not operate unless the associated axis tag is manually corrected. The conversion of
the previous 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 General tab for the axis tag and set the Output Cam Execution
Targets value to the correct number for your application. (x25982)

DH485 Message Size Limit

Messages sent over a DH485 network are limited to a size of 240 bytes. This limitation is to prevent certain SLC, operator interface,
and other third party devices that cannot handle larger messages from generating communication errors. (x20920)

DH485 Protocol Limited to Baud Rate of 19,200

The RSLogix 5000 software will allow you to configure the System Protocol for DH485 and a Serial Port baud rate of 38,400. However
the protocol does not support this baud rate and the serial port will not operate correctly if configured this way. Choose a baud rate of
19,200 or less when using the DH485 protocol. (x25526)

Produce & Consume Tags Changes

As of the V7.00 release of RSLogix 5000, these features are obsolete:

1. You will not be allowed to simultaneously Produce and Consume a tag.

2. You will not be allowed to Produce an alias tag.

If you have used the above features in a previous release, then when you convert your project to V13.00 the tags involved will be
unverified. You will then be required to correct the tag(s) properties.

In addition, produced and consumed tags now require more memory in the controller. If you attempt to download a project with a
significant number of produced and consumed tags, you may run out of memory on the controller. Refer to the table of Controller
Memory Changes for more detail. (x08098)

Online correlation failure accepting a large number of pending edits

When making online changes to ladder logic, you are limited to accepting changes to 1000 rungs at one time. If you attempt to accept
pending edits for more than 1000 rungs, RSLogix 5000 will display an error "Failed to correlate the project with a change in the
controller. RSLogix 5000 has been taken offline." You can avoid this problem by accepting pending rung edits before the 1000 rung
limit is reached. (x06034)

Tag Editor / Data Monitor Expand All with large arrays

If your project has large array tags, the Expand All feature may result in a low virtual memory condition and sluggish response. To work
around this condition, close all other applications except RSLogix 5000, or expand array tags manually. (21506)

Unable to uninstall RSLogix 5000 when disk space is low

If there is insufficient disk space on the hard drive, uninstalling RSLogix 5000 may fail with an error message “Unable to locate/process
internal binary resource. Please contact your software vendor.” To work around this problem, free up disk space and try to uninstall
again. (21195)

Programming Over a DF1 Master/Slave Network

Programming over a DF1 Master/Slave network is not currently supported in RSLogix 5000. (20596)

Download Fails with Communication Time-out

Under certain conditions (e.g. downloading over a project with a large number of established connections) downloading a project to the
Logix5550 controller may fail with a communication time-out and RSLogix 5000 will be taken offline. If this occurs you should wait about
2 minutes and try to download a second time. If the second attempt to download fails, you should check the communication wiring to
the controller to insure that a cable has not become disconnected, and also to check that the controller still has power. (20430)

User-Defined Data Type size limits

You may not create a data type with more than 512 members either by editing in the Data Type Editor or by importing from an .L5K file.
An individual UDT member may be an array with more than 512 elements. (20279, 21723)

Program-scoped tag aliased to controller-scoped tag with the same name

The Tag Editor will no longer allow you to create a program-scope alias to a controller-scope tag of the same name. If you created
projects with this condition in previous releases, they will convert successfully to V9.00, but the controller will fail to upload with the error
message “Failed to resolve tag target”. To work around this problem, you can do either of the following things:
ƒ While online to the controller, change the name of all the program-scoped tags which alias a controller-scoped tag with the same
name to something (slightly) different and then upload, or
ƒ Save the project as an .L5K file (export) and open the .L5K file (import), which will cause the program-scoped tags to become
unverified. Delete the program scope tags that are now unverified which will cause the instructions that used the program-scoped
tags to re-bind to the controller-scoped tags with the same name. Finally, download the project to the controller. (20249)

Failure to modify the RPI of a consumed tag

While attempting to modify the RPI of a consumed tag, the following error may be encountered: "Failed to modify the properties for the
tag '<consumed tag name>'. Couldn't be found." To work around the problem, save the project as an .L5K file, then reopen the .L5K
file. (19870)

Wall Clock Time beyond January 17, 2038 causes RSLogix 5000 to crash
A Wall Clock Time in the controller beyond January 17, 2038 will cause RSLogix 5000 to crash. The Wall Clock Time may be set via an
SSV instruction or on the Controller Properties dialog Date/Time tab. If the Wall Clock Time is inadvertently set to an invalid value or
rolls over from an earlier valid value with the Date/time properties displayed, the RSLogix 5000 software will crash. (17457, 17464)

Instances of going online for the first time failing

There are intermittent issues with attempts to go online after power-cycling the controller chassis and/or stopping and starting RSLinx
that may cause a first time failure. Immediate subsequent attempts will succeed. (09509, 17145)

Uploading controllers with multiple aliases to the same data

Caution should be used in developing applications that utilize multiple aliases to the same base tag. When such an application is
uploaded, the alias may replace base tag operands in the ladder logic. The aliases are alphabetized internally on upload so the
replacement operand will be the first alphabetical name (08905, x07909, CR169)
Application Notes
The following information is provided to help you better understand the behavior of RSLogix 5000 in particular applications or under
certain circumstances.

RSLogix 5000

Display of non-Unicode Character Fonts in RSLogix 5000

It is recommended that the Microsoft® Windows operating system’s “Language for non-Unicode programs (System Locale)” be
configured to match the localized language of RSLogix 5000 Editions. This is especially true for Chinese, Japanese, and Korean
RSLogix 5000. Not configuring the PC’s operating system’s System Locale to match the language of RSLogix 5000 may result in the
inability of RSLogix 5000 to display certain fonts.

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 (9324-RLD300ZHE), you should select “Chinese (PRC)” for the System Locale.

CTree Errors Opening RSLogix 5000 Projects With McAfee VirusScan Running
With McAfee VirusScan Enterprise Edition 7.1 running, unexpected CTree errors may be seen when RSLogix 5000 project files are
opened. This is caused by files in the temporary RSLogix 5000 folders, AB_xxxx, being modified by the McAfee VirusScan software.
McAfee VirusScan software should be configured to ignore the contents of the AB_xxxx folders.

Starting with RSLogix 5000 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:\Documents and
Settings\<username>\Local Settings\Temp on Windows 2000 and XP). To prevent the CTree errors from occurring, the McAfee
VirusScan software settings can now be configured to ignore the contents of the “RSLogix5000.Temp” folder. (x51417)

RSLogix 5000 Enterprise Series (Multiple Revision Support)

RSLogix 5000 Enterprise Series supports multiple revisions of the programming software on a single personal computer (PC) running
Windows 2000 or XP. With RSLogix 5000 Version 10 and later, you may install as many of the later major versions as needed plus one
version earlier than Version 10 (e.g. V8.02). Note: due to operating system constraints, on a PC running Windows NT only one version
of RSLogix 5000 can be installed at a time.

Motion Objects and Instructions Changes

The introduction of SERCOS functionality in the V9.00 release required changes to the motion objects and motion instructions that have
been in place since the initial release of RSLogix 5000 up to version 8.02. The changes were in four areas and included:
ƒ Axis tag member name changes
ƒ Axis object attribute name changes
ƒ Axis configuration value changes
ƒ Motion Instruction changes

For additional information, refer to Publication 9324-RN001B-EN-P – August 2001 or previous version RSLogix 5000 Release Notes.

MOTION_INSTRUCTION Data Type Change

The MOTION_INSTRUCTION data type changed in V12 and later and the size increased from 12 bytes to 16 bytes. If you have
created User-Defined data types that include members of type MOTION_INSTRUCTION you will lose tag initial values when
you convert your project files from previous versions. To work around this problem, export your project using the pre-V12 version
of RSLogix 5000 and then import the project in V12.02 or later. If you have written logic that relies on the old 12-byte size (for example
by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that your logic is still correct.

The new MOTION_INSTRUCTION data type structure is:

FLAGS DINT
EN BOOL
DN BOOL
ER BOOL
PC BOOL
IP BOOL
AC BOOL
ACCEL BOOL
DECEL BOOL
ERR INT
STATUS SINT
STATE SINT
SEGMENT DINT
 EXERR SINT
Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393) .

Extra Digit of Precision Shown for REAL Data Type

The REAL data type now shows a 32-bit (4-byte) IEEE floating-point value with the following range:
ƒ -3.40282347E38 to -1.17549435E-38 (negative values)
ƒ 0
ƒ 1.17549435E-38 to 3.40282347E38 (positive values)
The REAL data type also stores ±infinity, ±NAN, and -IND, but the software display differs based on the display format.

Display Format: Equivalent:

Real +infinite 1.$
- infinite -1.$
+NAN 1.#QNAN
-NAN -1.#QNAN
-indefinite -1.#IND
Exponential +infinite 1.#INF000e+000
- infinite -1.#INF000e+000
+NAN 1.#QNAN00e+000
-NAN -1.#QNAN00e+000
-indefinite -1.#IND0000e+000

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)

Sequential Function Charts Reset to Initial Step During Online Editing

When performing online editing operations in a Sequential Function Chart (SFC), be aware that switching the executing logic from the
original programming to the test edits version (or vice versa) will reset the chart to the initial step and reset all stored actions. This
occurs regardless of which step(s) and action(s) were active at the time of the switch. To work around this problem, 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 re-position the chart back to the desired
step. (x36331, x43482)

RSLogix 5000 Appears to Lock Up When RSMACC Connection Broken

If RSAudit message logging is enabled and the workstation is unable to connect to the RSMACC server to log messages, RSLogix
5000 experiences intermittent freezes while it is waiting for the message requests to time out. This might cause RSLogix 5000 to
appear as though it has locked up, but if you wait about one minute it will begin responding again. To resolve this problem, either
restore the connection to the RSMACC server or disable the RSAudit message logging. Once a connection has been restored, cached
messages will be logged to the server and RSLogix 5000 will resume normal operation. (x36127)

RSLogix 5000 Save May Result In Large Project ACD File

During a file save operation RSLogix 5000 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 may not be able to compress the information within the ACD file. In order to prevent the loss of project information,
RSLogix 5000 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 technical support and provide
a copy of your project file, this could help the RSLogix 5000 development team to locate the source of the compression failure.

Activation Error Running Multiple Versions Simultaneously

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

Default Project Directory and Windows 2000/XP

When using RSLogix 5000 on a Windows 2000 or XP computer, be careful when performing operations with project files that depend
on the default project directory. Windows 2000 and XP control and retain the default directory for the Open, Save As, and New
Controller dialogs. Be sure to check that the folder selected is the one you wish to use when performing these operations to avoid
mistakenly overwriting your project files. The Project Directory setting in the RSLogix 5000 Tools Options dialog is normally used unless
you navigate to a different directory within the Open, Save As, or New Controller dialogs. (x28475, x27886)

FBD Routine Localized Feedback Wiring Errors

In releases prior to Version 10.00 if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner)
you could download the project to a controller but may have encountered an error when uploading the project. This problem was
caused by selecting multiple localized feedback wires in the outside feedback loop. In this release, this condition will be detected as a
verification error in the routine. To correct this problem, select a feedback wire in the inner loop that is not also in the outer loop to be
the localized feedback wire. (x28963, x27712)

FBD Routine Order of Execution for Unwired Blocks

If you have a Function Block Diagram routine with function blocks that are not wired together, the execution order is not deterministic.
Operations such as Verify Routine or Export/Import may change the execution order unexpectedly for unwired blocks. To define the
execution order, you must wire function blocks together. See the Function Block Attributes Order of Execution topic in the RSLogix
5000 Online Help or the Logix5000 Controllers Process Control and Drives Instructions Reference Manual for more information.
(x28703, x28681)

Describing a Full Circle Using the MCCM Instruction

In order to describe a full circle in a system with 2 axes in a coordinate system, the Direction flag in the MCCM instruction should be
programmed using a code of 2 (CWF - Clockwise Full) or 3 (CCWF - Counterclockwise Full). Due to internal round-off in the floating
point calculations, using a Direction flag of 0 (CW) or 1 (CCW ) with the start and end point being equal (or nearly equal) may result in a
small arc of nearly 0 degrees, instead of a full circle of nearly 360 degrees. (x56812)

Motion Module Servo Update Period Changed

The Servo Update Period for the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed from 200 microseconds to 250
microseconds. The servo update period is displayed on the Module Properties dialog Associated Axes tab. This change in the Servo
Update Period will have no affect on the behavior of existing motion control applications or on the overall performance of the motion
control system. (x28647)

Motion Group Fault No Longer Produces Major Fault in Program Mode

In V12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in
program mode but will produce a Major Fault if the controller is in run or remote run mode. In versions previous to V12.01, the motion
group could produce a major fault while the controller was in program or remote program mode. For example, a store to nonvolatile
memory interrupts the execution of the motion planner, which produces a fault. (x36957)

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, E19, and E20. Average timing changes
observed were 20ms in Version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 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 added the capability to use either RSLinx RSWho and RSLogix 5000 Who Active dialogs to Browse to RA
Sercos drives. Now in Version 15, support has been 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
st
Sercos will 1 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 drive(s) 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 Version
2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver
Version 2.7 or later. (x51766)

Updating Controller Firmware in a DH485 Network

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

Online Disconnection after Nonvolatile Store or Load Operation

When using any of the controllers with nonvolatile memory, the memory store and memory load operations will take between 30
seconds and approximately 3 minutes to complete. During these operations the RSLogix 5000 software will be taken offline and will
require you to manually reconnect. Any other workstations connected to the controller will also be taken offline. If you performed a store
operation, or a load operation where your project did not have any online changes, you will be able to go back online immediately and
the project will need to be saved. If you performed a load operation, and your project included online changes that you saved since the
last store operation, you will be prompted to upload or download before going online.

I/O Module List Appears Empty

If the list of modules appears empty in the Select Module Type dialog box when you attempt to create a new module, there may be a
problem with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version
listed in the table below. (x19891, x18680, x06823)
DLL Name Compatible Versions
Comcat.dll 4.71 5.0
Ole32.dll 4.0 4.71 or later

Configuring CRC Error Detection for RSLogix 5000 Software

RSLogix 5000 software is configured to use BCC error detection by default when using DF1 serial port communication. CRC error
detection can be configured instead of BCC by following these two steps. First, CRC Error Detection must be selected on the Controller
Properties dialog System Protocol tab. Second, the RSLinx DF1 Communications Device Driver must be Auto-Configured so the
driver’s Error Checking will be set to CRC to match the Logix5550 Controller. The process is simplified if non-DF1 communications is
used to select CRC Error Detection in the Logix5550 Controller using RSLogix 5000 software.

To change the error detection, open a project and establish online communications using Ethernet, ControlNet, or DF1 communications
to the target Logix5550 controller. Open the Controller Properties dialog 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 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 and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 select Go Online to re-
establish online communications. This DF1 driver will now communicate only with Logix5550 Controllers that are setup to use CRC
Error Detection.

Changes in Fatal Error Handling

Starting with RSLogix 5000 Version 2.25, there are changes in the way abnormal program terminations will appear. There is now a
single format for the Fatal Error dialog, which will appear regardless of the cause of the problem. There is also a single log file
generated that records the abnormal events and can be emailed to Customer Support so that the problem can be recorded, diagnosed,
and fixed. An abnormal termination of RSLogix 5000 will result in a short period of program unresponsiveness followed by the
appearance of a dialog box with the title "RSLogix Fatal Error" and containing specific details about the cause of the error. In addition,
this information is appended to the file "RSLogix 5000 Fatal Error.Log" located in the Temp directory. (C:\Temp on Windows NT4 or
C:\Documents and Settings\<username>\Local Settings\Temp on Windows 2000 and XP.) Starting with V14.00, the Fatal Error
information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. The new file will be large and should be deleted if not needed
or should be compressed and possibly copied to a CD if it must be sent to Customer Support.

Controllers with Motion Control

Be certain that only one controller or SYNCH module in the chassis is enabled as the Coordinated System Time (CST) master. You can
enable the feature for a controller by navigating to the Controller Properties dialog Date/Time tab and selecting “Make this controller the
Coordinated System Time master”. You can enable the feature for a SYNCH module by navigating to the SYNCH Module Properties
dialog Time Mastership tab and selecting “Make this module the Coordinated System Time Master for this chassis”. Communication
errors to the servo module(s) will occur if more than one controller or SYNCH module is configured as the CST master.

Destination operands for GSV commands

Caution should be used in selecting the proper data type for the destination operand of a GSV instruction. Use of mismatched operand
data types may result in unexpected results. Refer to the Instruction Set reference manual or the online instruction help to determine
the proper data types.

Downloading controllers that use more memory than available

If a controller utilizing more memory than is available in the physical controller is downloaded, the user will receive an appropriate error
message. However, in some instances, the serial port will become inoperative. It is recommended that in this case the controller
memory be cleared (power turned off and the battery removed).

Multiple owners and/or listeners of 1756 analog modules

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

Configuring the DHRIO module

When online, if the DHRIO module is configured for DH+ only, this module continuously displays Faulted as its Status on the Module
Properties dialog box even when normal communications exist. To avoid this erroneous fault condition, include the DHRIO module in
the I/O configuration only if the application uses the Remote I/O features.

Note: If the Logix controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx V2.20 or later, or
the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.

User disk memory utilization

If an RSLogix 5000 session is terminated abnormally, some large temporary files may be left on the hard drive. You should periodically
delete old folders named AB_xxxx from your temporary directory (typically C:\Temp on Windows NT4 or C:\Documents and
Settings\<username>\Local Settings\Temp on Windows 2000 and XP). Smaller files with .SEM and .WRK suffixes may be left in your
project directory after an abnormal termination and may be deleted. Starting with V14.00, the AB_xxxx temporary files will be located in
a folder named RSLogix 5000.Temp, which will be a subfolder of the system defined Temp folder.

Application Errors at end of install or at RSLogix 5000 startup on some systems

Caused by a corrupted activation key file (evrsi.sys). To correct this problem, contact Rockwell Automation technical support by
telephone at 440-646-5800 or by email at [email protected].

RSLinx with RSLogix 5000

Configuring the Ethernet Port on a CompactLogix5532E

You may be prevented from configuring the Ethernet Port of a CompactLogix5532E (1769-L32E) via Channel 0 using RSLinx. To
workaround the problem, use RSLogix 5000 to configure the port (if the 1769-L32E is at Revision 13) or use the BootP utility (which is
enabled for a 1769-L32E at Revision 1).

RSLinx Professional Activation

Beginning with RSLinx V2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Professional version features.
Only one professional activation is required for both products. The RSLogix 5000 Professional Activation must be installed on the
personal computer hard disk in order to activate RSLinx Professional.

Accessing Structures Larger than 64 Kbytes

ControlLogix5000 Version 8.x controllers allow you to create user-defined structures larger than 64 Kbytes. Access to these structures
in the controller requires you to update to RSLinx V2.30.00 (Build 40) or later for correct operation. Older versions of RSLinx do not
operate correctly with these larger structures.

Configuring drivers for the 1756-ENET, 1756-ENBT, and 1756-EWEB modules

You configure a driver for communicating from the workstation through the 1756-ENET, 1756-ENBT, or 1756-EWEB module by
selecting "Configure Drivers ..." from the RSLinx "Communications" menu. In the dialog box, select "Ethernet devices" in the list of
available driver types and click on the "Add New" button.

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

Configuring DF1 drivers

For DF1 point-to-point communications, choose “RS232 DF1 Devices” from the list of available drivers in RSLinx. Then choose
"Logix5550 Serial Port" for DeviceType. We recommend that you do not use the DF1 Polling Master Driver or the DF1 Slave Driver with
RSLogix 5000 software. You may be able to download successfully, but there are problems accessing information from I/O modules.

Offline Tag and UDT Changes Downloaded to the Controller May Cause RSLinx (2.X) To Halt
Communications
RSLinx 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
attempting to access tag information that is no longer present. When this occurs, RSLinx halts the communications to the controller.
To recover, both RSLinx and the software requesting tags from RSLinx must be re-started. To avoid this problem, 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 (e.g. changing a DINT to a SINT). Note that RSLinx
Enterprise Series is able to accommodate these changes without requiring a restart.
Contact Information
For technical assistance, please use the following contacts:
ƒ Technical Support Telephone - 440-646-5800
ƒ Technical Support Fax - 440-646-5801
ƒ World Wide Web - http://support.rockwellautomation.com

When you call:

When you call, you should be at the computer running the Rockwell Software product and be prepared to provide the following
information:
ƒ 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 click About RSLogix 5000
ƒ the product version number
This information also appears in the About box.
ƒ 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
Trademark Information
WINtelligent Series is a registered trademark, and the Rockwell Software logo, RSAlarm, RSAnimator, RSAssistant, RSBatch,
RSBreakerBox, RSButton, RSChart, RSCompare, RSControlRoom, RSData, RSDataPlayer, RSEventMaster, RSGuage,
RSJunctionBox, RSLogix Emulate 5, RSLogix Emulate 500, RSGuardian, RSHarmony, RSKeys, RSLadder, RSLadder 5, RSLadder
500, RSLinx, RSLogix 5, RSLogix 500, RSLogix 5000, RSLogix Frameworks, RSMailman, RSNetWorx for ControlNet, RSNetWorx for
DeviceNet, RSPortal, RSPower, RSPowerCFG, RSPowerRUN, RSPowerTools, RSRules, RSServer32, RSServer, RSServer OPC
Toolkit, RSSidewinderX, RSSlider, RSSnapshot, RSSql, RSToolbox, RSToolPak I, RSToolPak II, RSTools, RSTrainer, RSTrend,
RSTune, RSVessel, RSView32, RSView, RSVisualLogix, RSWheel, RSWire, RSWorkbench, RSWorkshop, SoftLogix 5, A.I. Series,
Advanced Interface (A.I.) Series, AdvanceDDE, ControlGuardian, ControlView, INTERCHANGE, Packed DDE, WINtelligent,
WINtelligent LINX, WINtelligent LOGIC 5, WINtelligent VIEW, WINtelligent RECIPE, WINtelligent VISION, and WINtelligent VISION2
are trademarks of Rockwell Software Inc.
PLC, PLC-2, PLC-3 and PLC-5 are registered trademarks, and Data Highway Plus, DH+, DHII, DTL, MicroLogix, Network DTL,
PowerText, Pyramid Integrator, PanelBuilder, PanelView, PLC-5/250, PLC-5/20E, PLC-5/40E, PLC-5/80E, SLC, SLC 5/01, SLC 5/02,
SLC 5/03, SLC 5/04, SLC 5/05, SLC 500, and ControlLogix are trademarks of the Allen-Bradley Company, Inc.
Microsoft, MS-DOS, Windows, Visual Basic, and .NET Framework are registered trademarks, and Windows NT, Windows 2000,
Windows XP, and Microsoft Access are trademarks of the Microsoft Corporation.
ControlNet is a trademark of ControlNet International.
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
IBM is a registered trademark of International Business Machines Corporation. AIX, PowerPC, Power Series, RISC System/6000 are
trademarks of International Business Machines Corporation.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.
AutoCAD is a registered trademark of Autodesk, Inc.
Portions copyright 1992-2000 FairCom Corporation. "FairCom" and "c-tree Plus" are trademarks of FairCom Corporation and are
registered in the United States and other countries. All Rights Reserved.
All other trademarks are the property of their respective holders and are hereby acknowledged.
 Rockwell Software Inc.

END-USER LICENSE AGREEMENT

IMPORTANT—READ CAREFULLY: This End-User License Agreement (“EULA”) is a legal agreement between you (either an
individual or a single entity) (“You or Licensee”) and Rockwell Software Inc. (“LICENSOR or RSI”) for the software product or products
that You acquired, which includes computer software and may include associated media, printed materials, and “online” or electronic
documentation, as well as any updates (“Software”). An amendment or addendum to this EULA may accompany the Software. YOU
AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE.
IF YOU DO NOT AGREE, DO NOT INSTALL OR USE THE SOFTWARE; YOU MAY RETURN IT ALONG WITH ALL
ACCOMPANYING ITEMS TO YOUR PLACE OF PURCHASE FOR A FULL REFUND.

The Software is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties.
RSI or its Licensors own the title, copyright and other intellectual property rights in the Software. The Software is licensed, not sold.

GRANT OF LICENSE

RSI and its third party licensors grant to You a non-exclusive license to install and use the Software on either: (a) a single computer, or
(b) a network server for access by one user, by way of terminal or computer attached to the network server. Should You choose to
install the Software on additional computers, or increase user access via a network server, You must first acquire a license for each
additional user who will use the Software, with the understanding that at any one point in time (and regardless of the number of media
sets included with the Software), the number of users who are permitted to use the Software may not exceed the number of single-user
licenses you have acquired. This License does not grant You the right to provide or utilize the Software as part of an application service
provider (ASP) service or the like.

If this Software is an upgrade or update to a previous version of an RSI 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.

Any attempted sublicense, rental, sale, lease, or commercial hosting of the Software is prohibited. However, You may transfer your
rights to use the Software on a permanent basis, provided: (1) You transfer this EULA, the Software, and all accompanying written
materials and retain no copies; (2) the recipient agrees to the terms of this EULA; and (3) You first notify RSI in writing of the date of
transfer and the recipient’s full name and address. This EULA will automatically terminate without notice to You if You fail to comply
with its terms.

The Software and the accompanying documentation are copyrighted. Unauthorized copying, reverse assembly, reverse engineering,
decompilation, and creating derivative works based on the Software are prohibited. You may not make copies of the Software except
that You may install the Software into permanent memory of a single storage device provided You keep the original media solely for
backup or archival purposes. You may not copy the accompanying documentation. Ownership and title to the Software is retained by
RSI or its licensors, as applicable.

LIMITED WARRANTY

The Software is warranted for ninety days after its initial delivery to You that it will conform with its accompanying user documentation
supplied by RSI 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. RSI 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 EXTENT PERMITTED BY LAW THE LIMITED WARRANTY IN THIS EULA IS IN LIEU OF ALL OTHER WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.

LIMITATION OF REMEDIES

RSI’s 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 RSI is unable to deliver replacement Software which meets the Limited Warranty specified above, RSI or its reseller will refund
your purchase price.

LIMITATION OF LIABILITY

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL RSI 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 RSI OR ITS RESELLER HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

RSI'S MAXIMUM CUMULATIVE LIABILITY RELATIVE TO ALL OTHER 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. THESE DISCLAIMERS AND LIMITATIONS
OF LIABILITY WILL APPLY REGARDLESS OF ANY OTHER CONTRARY PROVISION OF THIS EULA AND REGARDLESS OF THE
FORM OF ACTION, WHETHER IN CONTRACT, TORT OR OTHERWISE, AND FURTHER WILL EXTEND TO THE BENEFIT OF
RSI’S VENDORS, APPOINTED DISTRIBUTORS AND OTHER AUTHORIZED RESELLERS AS THIRD-PARTY BENEFICIARIES.

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 Licensor for technical support and product updates.

PREPRODUCTION RELEASES

As an accommodation to Licensee, RSI 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. RSI DOES
NOT WARRANT PREPRODUCTION RELEASES.

SAMPLES

The Software may contain samples that are provided as an accommodation to You (“Sample Project Files”). These Sample Project files
are intended to be used for example only. The Sample Project Files may be contained in the Software, documentation (electronic or
printed) or downloaded from the RSI website. RSI and its third party licensors make no representations or warranties regarding Your
use of the Sample Project files and related documentation. All such Sample Project Files are provided "as is". RSI 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.

OTHER PROVISIONS

This EULA shall be governed by the laws of the State of Wisconsin. This EULA, and any amendment or addendum to this EULA that
accompanies the Software is the complete and exclusive agreement between RSI and You, and supersedes all prior agreements,
whether written or oral, relating to the Software provided and the accompanying documentation. This EULA may not be changed or
modified except by an instrument in writing signed by a duly authorized representative of RSI.

LICENSE ADDENDUM TO RSLOGIX END USER LICENSE AGREEMENT

RSLogix License Restriction:

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.

Automation Interface Program:

Rockwell Software Inc. (RSI) has developed a programmatic interface to its RSLogix Software (the “Automation Interface”) and has
provided the same to You as a part of the RSLogix Software. The Automation Interface is intended to provide enhanced functionality to
the RSLogix Software for use by RSI’s customers who use PLCs and in particular provide improved in-process and out-of-process
communications and control capabilities with respect to PLCs. RSI intends these communications and control capabilities to be used
only in accordance with the primary purposes of the RSLogix Software in providing a software platform for the development and
implementation of PLC application programs by or directly on behalf of PLC end-users.

I. Therefore, You are granted a non-exclusive license to use the Automation Interface in conjunction with your use of the RSLogix
Software and application code created by the RSLogix Software but only:
a) in applications programmed by You for use in and for your own PLC control systems within your own factories or industrial
plants including the programming of control systems having PLCs within them which are intended to by 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 PLC control systems operating within its own factory or
industrial plant and the application code developed for each customer is not shared with or among other such end-user
customers.
II. You are not licensed to use the Automation Interface to:
a) provide any of the functional capabilities of the RSLogix Software in or enabled through the RSLogix Automation
Interface, in a non-custom retail product as an ASP service or use the Automation Interface in providing any kind of
subscription service or the like based on the functionality of the RSLogix Software such as for remotely validating or
verifying PLC application code, or
b) provide automated capabilities available to multiple clients or the general public for generating PLC application code,
c) remotely or locally furnish the same software products or services to multiple clients or to the general public except as
permitted in Section I above,
d) create or facilitate any script driven applications that provide functionality or interface with any commercially available
software programs.

PLEASE NOTE: RSI does not include debugging or troubleshooting services for custom applications as a part of our standard support.

Rockwell Software EULA

Doc ID License 03-28-03
RSLogix AI Addm.doc 03-28-03