This release has the following requirements.
System requirements for RSLogix 5000 version 16.05
For optimal performance of the RSLogix 5000 software, the personal computer should meet or exceed the following hardware and software requirements.
|
Tip:
|
The RSLogix 5000 software can be installed on a personal computer that
meets the operating system minimum requirements, but may not meet
performance expectations when used in a production system.
|
Hardware Requirements
Software Requirements
|
Important:
|
Keep these operating system considerations in mind:
When installing the RSLogix 5000 software on computers that have
not been updated, a prompt displays to install Universal C Runtime
or to update the computer to at least the Microsoft April 2014 update
roll-up.
|
|
Important:
|
When installing version 16.05 of the RSLogix 5000 software,
Microsoft .NET Framework 4.6 is installed automatically. However,
when installed on 32-bit Windows operating systems, .NET
Framework 4.6 causes versions 23.00.00 and earlier of the software
to fail on startup. Also, when previous versions of the software are
installed after 16.05, 20.05, 24.02, 28.03, 30.00, and later, .NET
Framework 4.6 may cause these earlier versions of the software
installation to fail.
|
Firmware requirements
|
Tip:
|
Most modules use Flash-ROM for the storage of firmware. If a module
requires a firmware change, use the ControlFLASH™ tool to perform the
update to the Flash-ROM. It is contained in the downloaded image or on a
DVD-ROM shipped with the RSLogix 5000 software. Another option is to
update the firmware automatically as part of the project download.
For additional information and assistance in performing a Flash-ROM update,
review the ControlFLASH Firmware Upgrade Software User Manual,
publication 1756-UM105.
|
This release has the following requirements.
Software Requirements v17
Operating system and service pack compatibility:
Note that this will uninstall only the RSLogix 5000 application. Other components that were installed with RSLogix 5000 software (such as Start Page Media, Online Books, or RSLinx) must be uninstalled separately.
Software Requirements Product Considerations v17
Hardware Requirements v17
The personal computer must meet these minimum requirements. Using a computer meeting the recommended characteristics will improve performance.
|
Characteristic
|
Minimum Required
|
Recommended
|
|
Processor
|
Pentium 3 or better
|
Pentium 4 or better
|
|
Speed
|
733 MHz
|
2.8 GHz
|
|
RAM Memory
|
256 MB
|
1 GB
|
|
Hard Disk Space
|
3.0 GB free
|
3.0 GB free
|
|
Optical Drive
|
DVD-ROM Drive
|
DVD-ROM Drive
|
|
Video
|
1024x768 pixels True
Color
|
1280x1024 pixels True
Color
|
|
Pointing Device
|
Any
Windows-compatible
pointing device
|
Any
Windows-compatible
pointing device
|
This release has the following requirements.
Software Requirements v18
Operating system and service pack compatibility:
Software Requirements Product Considerations v18
Hardware Requirements v18
The personal computer must meet these minimum requirements. Using a computer meeting the recommended characteristics will improve performance.
|
Characteristic
|
Minimum Required
|
Recommended
|
|
Processor
|
Pentium 3 or better
|
Pentium 4 or better
|
|
Speed
|
833 MHz
|
2.8 GHz
|
|
RAM Memory
|
512 MB
|
1 GB
|
|
Hard Disk Space
|
3.0 GB free
|
3.0 GB free
|
|
Optical Drive
|
DVD-ROM Drive
|
DVD-ROM Drive
|
|
Video
|
1024x768 pixels True
Color
|
1280x1024 pixels True
Color
|
|
Pointing Device
|
Any
Windows-compatible
pointing device
|
Any
Windows-compatible
pointing device
|
as Start Page Media, Online Books, or RSLinx) must be uninstalled separately.
This release has the following requirements.
Software Requirements Product Considerations v19
Software Requirements v19
Operating system and service pack compatibility:
Hardware Requirements v19
The personal computer must meet these minimum requirements. Using a computer meeting the recommended characteristics will improve performance.
|
Characteristic
|
Minimum Required
|
Recommended
|
|
Processor
|
Pentium 3 or better
|
Pentium 4 or better
|
|
Speed
|
833 MHz
|
2.8 GHz
|
|
RAM Memory
|
512 MB
|
1 GB
|
|
Hard Disk Space
|
3.0 GB free
|
3.0 GB free
|
|
Optical Drive
|
DVD-ROM Drive
|
DVD-ROM Drive
|
|
Video
|
1024x768 pixels True
Color
|
1280x1024 pixels True
Color
|
|
Pointing Device
|
Any
Windows-compatible
pointing device
|
Any
Windows-compatible
pointing device
|
Installation Notes
Review these notes before attempting to install this version of the RSLogix 5000 software.
Keep the following considerations in mind before you install the RSLogix 5000 software:
Follow these steps to install RSLogix 5000 software.
To enable security for RSLogix 5000 software, navigate to the ‘Security’ directory where the application software was installed (C:\Program Files\Rockwell Software\RSLogix 5000\<language>\<version>\Security or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\<language>\<version>\Security by default) and execute the SetSecKeys.exe file.
Important: RSLogix 5000 software version 19 includes a new version of SetSecKeys.exe, file version 19.0.0.0. This newer version:
We recommend that you do not use file versions of SetSecKeys.exe earlier than 19.0.0.0.
Refer to the following Known Anomalies topics for additional information:
Note that once security has been enabled, it cannot be disabled. Only enable security if you plan to use FactoryTalk Security (or Rockwell Software Security Server) to secure actions in RSLogix 5000 software.
To start RSLogix 5000 software, from the Start menu, choose All Programs>Rockwell Software>RSLogix 5000 Enterprise Series>RSLogix 5000 from the menu.
If RSLogix 5000 software does not start up or run properly, keep the following in mind:
Follow these steps to uninstall the software when using the default ‘Start menu’ on the Windows 7, Windows Vista, Windows XP, or Windows Server 2008 operating system.
From the Programs category, choose Uninstall a program. (for Windows Vista, Windows Server 2008 – Control Panel Home)
Double-click Programs and Features. (for Windows Vista, Windows Server 2008 – Classic View)
Double-click Add or Remove Programs. (for Windows XP – Classic View)
Click Add or Remove Programs. (for Windows XP – Category View)
Follow these steps to uninstall the software when using the ‘Classic Start’ menu on the Windows XP operating system and later.
Double-click Programs and Features. (for Windows Vista, Windows Server 2008 – Classic View)
Double-click Add or Remove Programs. (for Windows XP, Windows Server 2003 – Classic View)
Click Add or Remove Programs. (for Windows XP – Category View)
Follow these steps to uninstall the software when using the default ‘Start menu’ on the Windows Server 2003 operating system.
This release has the following requirements.
· Be certain that no copies of RSLogix 5000 software are currently running.
· Make sure that you have Administrator privileges on the personal computer on which you want to install the software. You will not be able to complete the installation without these privileges.
· If you want to perform online communications, you must install RSLinx Classic software in addition to RSLogix 5000 software.
· Close all other applications before running the setup process.
· Ensure that there are no pending workstation reboot requests from either Windows Update or any installation program. If there is a pending request, reboot the workstation before starting the RSLogix 5000 installation.
· Do you have the correct version of RSLinx Classic software installed? RSLinx Classic software provides communication between the controller and your personal computer.
Hardware Requirements v20
The personal computer must meet these minimum requirements. Using a computer meeting the recommended characteristics will improve performance.
|
Characteristic
|
Minimum Required
|
Recommended
|
|
Processor
|
Pentium 4
|
Intel Core i5
|
|
Speed
|
2.4 GHz
|
2.8 GHz
|
|
RAM Memory
|
1 GB
|
8 GB
|
|
Hard Disk Space
|
16 GB free
|
20 GB free
|
|
Graphics Device
|
1024x768, True Color
|
DirectX 9, with WDDM
1.0 or higher driver
|
Software Requirements v20
Operating system and service pack compatibility:
Software Requirements Product Considerations v20
This release has the following requirements.
Software Requirements v20.04
Operating system and service pack compatibility:
This release has the following requirements.
System requirements for RSLogix 5000 version 20.05
For optimal performance of the RSLogix 5000 software, the personal computer should meet or exceed the following hardware and software requirements.
|
Tip:
|
The RSLogix 5000 software can be installed on a personal computer that meets the operating system
minimum requirements, but may not meet performance expectations when used in a production system.
|
Hardware Requirements
Software Requirements
|
Important:
|
Keep these operating system considerations in mind:
When installing the RSLogix 5000 software on computers that have not been updated, a
prompt displays to install Universal C Runtime or to update the computer to at least the
Microsoft April 2014 update roll-up.
|
|
Important:
|
When installing version 20.05 of the RSLogix 5000 software, Microsoft .NET Framework
4.6 is installed automatically. However, when installed on 32-bit Windows operating
systems, .NET Framework 4.6 causes versions 23.00.00 and earlier of the software to
fail on startup. Also, when previous versions of the software are installed after 20.05,
24.02, 28.03, 30.00, and later, .NET Framework 4.6 may cause these earlier versions of
the software installation to fail.
|
Firmware requirements
|
Tip:
|
Most modules use Flash-ROM for the storage of firmware. If a module requires a firmware change, use
the ControlFLASH™ tool to perform the update to the Flash-ROM. It is contained in the downloaded
image or on a DVD-ROM shipped with the RSLogix 5000 software. Another option is to update the
firmware automatically as part of the project download.
For additional information and assistance in performing a Flash-ROM update, review the ControlFLASH
Firmware Upgrade Software User Manual, publication 1756-UM105.
|
This release has the following requirements.
For optimal performance of the RSLogix 5000 software, the personal computer should meet or exceed these hardware and software requirements.
|
|
Tip: The RSLogix 5000 software can be installed on a personal computer
that meets the operating system minimum requirements, but may not meet
performance expectations when used in a production system.
|
|
Important:
|
Keep these operating system considerations in mind:
When installing the RSLogix 5000 software on computers
that have not been updated, a prompt displays to install
Universal C Runtime or to update the computer to at least
the Microsoft April 2014 update roll-up.
|
|
|
Note: The RSLogix 5000 software version 20.06 does not support
SoftLogix.
|
|
|
Tip: Most modules use Flash-ROM for the storage of firmware. If a
module requires a firmware change, use the ControlFLASH™ tool to
perform the update to the Flash-ROM. It is contained in the
downloaded image or on a DVD-ROM shipped with the RSLogix 5000
software. Another option is to update the firmware automatically as
part of the project download.
For additional information and assistance in performing a Flash-ROM
update, review the ControlFLASH Firmware Upgrade Software User
Manual, publication 1756-UM105.
|
This release includes the following system features.
Auto-Save and Recovery
System Feature
Firmware Revision/ Software Version 16
With RSLogix 5000 prior to version 16, in the event of an unexpected shutdown of the workstation, operating system, or application, unsaved edits would be lost. With RSLogix 5000 version 16, RSLogix 5000 can now be configured to automatically create, at a user specified interval, a recovery file for the project file being edited. When opening the project, after an unexpected shutdown, the user is prompted to choose between recovery of the project, saving the recovery file, opening the most recent copy of the project, or canceling the open operation. This feature is enabled by default and the “Save Time Interval” parameter can be configured (1 - 1440 minutes) as one of the Workstation Options.
This release includes the following system features.
Add-On Instructions, User Defined
System Feature First Identified as of:
You can design and configure sets of commonly used instructions to increase project consistency. Similar to the built-in instructions contained in Logix5000 controllers, these instructions you create are called Add-On Instructions. Add-On Instructions reuse common control algorithms. With Add-On Instructions, you can:
Each instruction instance has its own data instance, providing for data isolation and easier debugging and maintenance. AOIs can be created in Ladder Diagram (LD), Function Block Diagram (FBD), or Structured Text (ST) programming languages. Once an AOI has been created, it can be used in any of the programming languages: LD, FBD, ST, or Sequential Function Chart (SFC). AOIs may include most of the RSLogix 5000 built-in instructions as well as other AOIs.
AOIs can be imported and exported to an XML file, allowing for easy portability from one project to another. The CSV Import/Export of the AOI definition is also supported. Source Protection can be used to protect AOI definitions as either no access or view only.
For more information about using Add-On Instructions, see the Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001.
CSV Import/Export of FBD and SFC Text Boxes
System Feature
Firmware Revision/ Software Version 16
Over the course of the previous releases of RSLogix 5000, the ability to export various object descriptions to a Comma Separated Variable (CSV) file has been provided. This allows for creation, editing, translation, and spell checking of descriptions with offline tools, such as Microsoft Excel. With version 16, this feature has been enhanced to also support FBD and SFC text boxes.
Kinematic Transformation Instructions Added
System Feature
Firmware Revision/ Software Version 16.02, 16.03, 16.06, 16.07
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, and 1756-L64
Motion control capabilities have been extended by allowing inverse and forward kinematic transformations. This functionality is targeted for controlling robots used in packaging and pick-and-place applications.
Kinematics transformations are not supported by ControlLogix 1756-L55, SoftLogix, and CompactLogix L4x controllers.The native geometries supported are: two and three axes articulated-dependent and articulated-independent robot geometries, as well as configurable support for three-axes SCARA geometries by leveraging the native geometries. To accomplish this functionality, the coordinate system configuration is enhanced to allow selection of the coordinate system type as either Cartesian or articulated.
Additionally, two new instructions, Motion Coordinated Transform (MCT) and Motion Calculate Transform Position (MCTP), have been added. The MCT allows a “gearing” relationship to be set between two coordinated systems, for example, between a Cartesian coordinate system made by virtual axes and an articulated coordinate system that is made by the robot’s real axes. Once the MCT is active, by simply programming moves on the virtual axes configured in the Cartesian coordinate system it is possible to move the robot in joint coordinates. The MCTP instruction allows the position to be transformed from that of one coordinate system to that of another coordinate system. Typically, the MCTP instruction would be used to calculate the Cartesian position from a given joint position (forward kinematics).
Online Changes in Output CAM Editor
System Feature First Identified as of:
Parameter values can be changed for the output CAM profile either on the grid or by using the graphical view. Insertion and/or deletion of points while in Run mode are not allowed. A new status rectangle icon has been added to the Output CAM Editor dialog to show the state of the control. The color of the rectangle is green when the controller is in Run mode, cyan while in Program mode, and gray while in the offline state.
FactoryTalk Alarms and Events Features
System Feature
Firmware Revision/ Software Version 16.02, 16.03, 16.06, 16.07
Catalog Numbers 1756-L55Mxx, 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, and 1756-L64
Alarms are now embedded in the controller with two new instructions, ALMD and ALMA, available in RSLogix 5000 software.
These instructions will be able to serve alarms information to the FactoryTalk Alarms and Events service, which will then publish this information to RSView SE HMI stations (CPR 9 version of RSView SE is required). Operators will be able to acknowledge, enable, disable, and suppress alarms from displays. Note that each of these new instructions and their associated data utilizes a substantial memory footprint and you should take this into account when estimating the amount of memory that an application will require.
These digital and analog alarm instructions are fully self-contained.
Logix5000 Firmware Supervisor
System Feature First Identified as of:
When a firmware revision mismatch situation exists, this feature enables the controller to update, with no user intervention, the firmware on modules configured in the I/O tree. Use of the Logix5000 Firmware Supervisor with ControlLogix controllers and certain I/O modules enables you to program the controller to complete firmware updates by using a GSV or SSV instruction. Both local and remote modules can be updated while the controller is in Program or Run mode. This feature is supported for all ControlFLASH supported modules that have the “Electronic key” parameter set to “Exact Match”. PowerFlex 70 and 700 drives firmware can also be updated; however, peripheral modules are not supported at this time. All firmware kits are transferred from the workstation and stored onto the controller’s CompactFlash card during a “Store to NVS” operation. This feature makes firmware management simpler, addresses the needs of regulated industries (e.g., Life Sciences), and allows in-the-field updates for OEMs.
In GuardLogix controllers, this system feature is available for use with standard I/O modules.
Home to Torque (Kinetix 2000, 6000, and 7000 drives)
System Feature
Firmware Revision/ Software Version 16.02, 16.03, 16.06, 16.07
Catalog Numbers 1756-L55Mxx, 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, and 1756-L64
Motion homing capabilities have been extended to provide two additional homing modes.
· Torque Level allows the homing position to be set when a configured torque limit is reached.
· Torque Level-Marker lets the homing position to be set when the configured torque limit is reached and feedback marker is detected.
These capabilities allow for enhanced application flexibility by removing the need for a home switch.
Kinetix 2000 Drive Support
System Feature
Firmware Revision/ Software Version 16.02, 16.03, 16.06, 16.07
Catalogue Numbers 1756-L55Mxx, 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, and 1756-L64
The Kinetix 2000 Servo drive 230V ac family is now supported. Power range is 100 W…1.5 kW. The Kinetix 2000 drive can also be configured to operate with single-phase or three-phase power. Enhancements Provided with Previous Firmware Revisions Cat. No. Firmware Revision Enhancement Description
Programmable Jerk Control
System Feature
|
Cat. No.
|
Available As Of
|
|
1756-L61, 1756-L61S,
1756-L62, 1756-L62S,
1756-L63, 1756-L64
|
Firmware Revision 16.022/RSLogix 5000 Software
Version 16
|
|
1768-L43, 1768-L45
|
Firmware Revision 16.024/RSLogix 5000 Software
Version 16
|
You can specify acceleration and deceleration jerk rates on single axis moves directly via operands in the instruction faceplate for S-curve profile motion. Jerk rates for S-curve motion can be specified as either “Units/Sec3”, “% of Maximum”, or a new “% of Time”, letting you optimize the need for speed and smoothness.
The configured maximum jerk rates are accessible programmatically via GSV/SSV instructions. Earlier revision of projects using S-curve velocity profiles will be automatically migrated forward and prepopulate the new Jerk Operands in the MAM, MAJ, and MAS instructions with default values for Jerk rate as “100% of Time”.
GuardLogix Controllers Support Standard ControlLogix Functions
System Feature
Firmware Revision/ Software Version 16.22
Catalog Numbers 1756-L61S, 1756-L62S
GuardLogix controllers support all standard ControlLogix control functions. For standard control, this includes all programming languages (LD, FBD, SFC, and ST), all motion capabilities, and all process capabilities without restriction.
System Install
System Feature
Firmware Revision/ Software Version 16
With version 16 of RSLogix 5000, the installation has been enhanced to provide a more integrated user experience. With this new install it is possible to pick which RSLogix 5000 components, firmware kits, and tools to install. This install also provides easier access to the many optional tools available on the CD.
DF1 Radio Modem Protocol Support
System Feature First Identified as of:
With this revision, the DF1 Radio Modem protocol, already supported by SLC 500 and MicroLogix products, has been implemented and enabled in the ControlLogix, CompactLogix, FlexLogix, and DriveLogix controllers. Legacy and Logix5000 controllers can be mixed and can support both master and slave and store and forward configurations.
Security Log-On/Log-Off
System Feature
Firmware Revision/ Software Version 16
For users who have installed and enabled security, RSLogix 5000 version 16 now provides a convenient way to Log-On and Log-Off the active user of the RSLogix 5000 software. Switching users in versions prior to version 16 required either changing the user logged into the Microsoft Windows or changing the FactoryTalk user via the “Log-on to FactoryTalk” dialog. The Security Log-On/Log-Off feature integrates with the FactoryTalk Security server, also known as the RSAsset Security server, by authenticating the user’s name and password against those that have been configured in FactoryTalk. The FactoryTalk Security server is installed and configured when you install the FactoryTalk Automation Platform (FTAP), available on your RSLogix 5000 version 16 CD. Further information about FactoryTalk Security server is available in FactoryTalk online help.
Instruction Defaults (FBD and SFC Programming Languages)
System Feature
Firmware Revision/ Software Version 16
Version 13 of RSLogix 5000 allowed instruction defaults to be set for the Ladder Diagram (LD) and Structured Text (ST) language editors. With version 16, this enhancement is extended to the Function Block Diagram (FBD) and Sequential Function Chart (SFC) language editors. Use of this feature allows default values to be defined for instruction operands. This is useful for instructions that have many parameters, for example, but not limited to process instructions. Simply enter the operands for the instruction, right-click on the instruction’s faceplate, and select the “Save Instruction Defaults” or “Save Element Defaults” menu option to save the operands as the defaults. Every new instance of the instruction will be automatically populated with the saved default operands. The default operands are saved on a workstation basis. This allows you to set the defaults once and re-use them across multiple projects.
Kinetix 7000 Drive Analog Input Configuration
System Feature
|
Cat. No.
|
Available As Of
|
|
1756-L61, 1756-L61S,
1756-L62, 1756-L62S,
1756-L63, 1756-L63S,
1756-L63XT, 1756-L64
|
Firmware Revision 16.022/RSLogix 5000 Software
Version 16
|
|
1768-L43, 1768-L45
|
Firmware Revision 16.024/RSLogix 5000 Software
Version 16
|
This feature allows an analog device to be connected to the Kinetix 7000 drive analog inputs. The drive transmits to the controller an integer number with a range of -16,384…16,384 representative of the analog value.
The analog values are accessible programmatically via the GSV instruction. These inputs are useful for “converting” applications with load cell (measuring web force on a roller) or “dancer” (measuring web force/position directly) that can be directly connected to the drive controlling the web.
Start Page
System Feature
Firmware Revision/ Software Version 16
With version 16, a new feature called the “Start Page” has been added. The Start Page organizes various resources intended to accelerate the user’s ability to use the software and easily locate relevant information. The Start Page is divided into three parts. The first part, called “Quick Start”, is intended to help first-time customers get started and helps more experienced customers learn or explore how to use the software. The second part, the “Learning Center” provides “What’s New”, “How Do I”, and “Did You Know” types of information. The third part, the “Resource Center” contains links to download sites, online books, and other reference material.
Option to Unicast Producer/Consumer Tags on EtherNet/IP Networks
System Feature First Identified as of:
In RSLogix 5000 software, you can configure Producer and Consumer tag connections to use the Unicast option. Setting the tags to Unicast decreases the network bandwidth and simplifies Ethernet switch configuration.
Logix Date Base Changed
System Feature First Identified as of:
The Logix real-time clock operates as a 64-bit binary number that counts microseconds from a fixed date. Prior to revision 16, the base date was January 1, 1972. Developments with the Common Industrial Protocol (CIP) specification resulted in the selection of a different base date of January 1, 1970 by the Open DeviceNet Vendors Association (ODVA).
The date base that Logix products use has been changed to bring it into alignment with the CIP specification. Additionally, in support of the changes to the real time clock, several other GSV attributes were also added:
Generally, the date and time were accessed via the GSV instruction within a Logix program by using the “DateTime” attribute, which breaks down the date and time to its various components (microsec, sec, min, hour, day, month, year). Applications that use this attribute to the real time clock should not be impacted by this change. However, the time was also available in its 64-bit form by using the “CurrentValue” GSV attribute. A GSV to “CurrentValue” of wall clock was changed to the number of microseconds from the new base date. Any applications that interpreted the old 1972 64-bit number may now require a change.
This release includes the following system features.
System features in RSLogix 5000 version 16.05
There are no new or enhanced features added to the release of RSLogix 5000 software version v16.05.
This release includes the following system features.
Active and Pending Motion
System Feature
Firmware Revision/ Software Version 17.02
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
Firmware Revision/ Software Version 17.06
Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S
A new enumeration, that is Active and Pending Motion, has been added to the Scope variable of the MCCD instruction. Choosing Active and Pending Motion specifies that the changes affect the motion dynamics of the active coordinated motion instruction and any pending coordinated motion instruction in the queue.
This release includes the following system features.
Runtime Partial Import
System Feature
Firmware Revision/ Software Version 17.02
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L64, 1756-L65, 1756-L61S, 1756-L62S, 1756-L63S
Firmware Revision/ Software Version 17.06
Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S
You can now import programs, equipment phases, routines, rungs, and new Add-On Instructions into a running system.
You can add these new components, as well as replace existing programs, equipment phases, and routines, while the system is running. New tags and User-Defined Types will be created as needed with values initialized from the import file. Data values of existing tags will be maintained.
Decorated Data for Import/Export in XML format
System Feature
Firmware Revision/ Software Version 17
Version 17 of RSLogix 5000 software also provides for an alternative format for specifying tag data when exporting or importing using the XML format. This verbose format is used to improve user readability of the tag data values in an XML file.
Program and Routine Partial Import/Export
System Feature
Firmware Revision/ Software Version 17
Version 17 of RSLogix 5000 software extends its capability to import and export project components to also include programs, routines, and equipment phases. These components are imported from and exported to an Extensible Markup Language (XML) file with a .L5X file extension. These text files can be manipulated or created by other tools, allowing the user to create libraries of code to facilitate code reuse.
This release includes the following system features.
Advanced Process Control Instructions
System Feature
Firmware Revision/ Software Version 17.02
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
Firmware Revision/ Software Version 17.06
Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S
Three new instructions targeted for process applications have been added. The new instructions are:
Instructions need to be purchased separately and licensed per use. The catalog numbers and associated use types are:
Kinetix 6000 Advanced Safety Drive (S1) and Enhanced Safe Torque-off Drive (S0)
System Feature
Firmware Revision/ Software Version 17.02
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
Firmware Revision/ Software Version 17.06
Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S
Version 17 provides support for the Kinetix 6000 SERCOS S1 Advanced Safety based family of drives. The safety status can be directly accessed by the user's application via two new SERCOS Axis attributes (GuardStatus and GuardFaults) in the Axis_Servo_Drive data type. The configuration of the S1 Drive's safety parameters is done via an Ethernet WEB based interface and downloaded to the Kinetix6000 drive via this Ethernet connection.
Version 17 provides support for the Kinetix 6000 SERCOS S0 Enhanced Safety based family of drives. The safety status can be directly accessed by the user's application via a bit attribute (SafeOff) in the Axis_Servo_Drive data type.
Full Project Import/Export in XML format
System Feature
Firmware Revision/ Software Version 17
Version 17 of RSLogix 5000 software provides the ability to import and export an entire project using an Extensible Markup Language (XML) file with a .L5X file extension. This is similar to import/export using an ANSI text file with .L5K extension.
GuardLogix Safety Instructions
System Feature
Firmware Revision/ Software Version 17.06
Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S
Several new safety instructions are available with the use of RSLogix 5000 software, version 17 and GuardLogix controller firmware, revision 17. New instructions include:
For more information about these and other safety instructions, see the GuardLogix Safety Application Instruction Set Safety Reference Manual, publication 1756-RM095.
Integrated System Install
System Feature
Firmware Revision/ Software Version 17
The installation of version 17 of RSLogix 5000 software has been further integrated with the installation of other Rockwell Software products that may be bundled with the purchased edition of RSLogix 5000 software. The label on the RSLogix 5000 DVD indicates that it is the first DVD to be installed. The RSLogix 5000 system install then allows for selection of other Rockwell Software products, components, firmware kits, and tools to be installed. All selected items will then be installed in the proper order.
Runtime Detection of Controller Modifications
System Feature
Firmware Revision/ Software Version 17.02
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65
Firmware Revision/ Software Version 17.06
Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S
Online changes to programs and data in a 1756-L6x ControlLogix controller can be tracked via an internal log with change counters. The log includes the type of change and the personal computer identity (Windows login) of the user who made the change. The change log can be stored on the controller's CompactFlash card for offline review. Changes may also be monitored programmatically by reading the change log counter using a Get System Variable (GSV) instruction.
MCD and MCCD Motion Instructions Enhancements
System Feature
Firmware Revision/ Software Version 17
With version 17 of RSLogix 5000 software, the functionality of the Motion Change Dynamics (MCD) instruction was extended to allow for the acceleration and deceleration jerk rates to be also changed for in-process single-axis moves or jogs. These same extensions apply to the Motion Coordinated Change Dynamics (MCCD) instruction, allowing for the acceleration and deceleration jerk rates to be changed for multi-axis coordinate moves or jogs. In addition, enumerations have been added to the MCCD instruction so that the "Active & Pending" motion can be changed dynamically.
This release includes the following system features.
DF1 Radio Modem Broadcast Support
System Feature First Identified as of:
DF1 Radio Modem support has been expanded to include broadcast capability. The DF1 Radio Modem functionality was initially provided with revision 16. With this expansion to include broadcast capabilities, you can configure a master or slave device to broadcast messages to all other stations in one instance.
RPI Limitations and Negotiated Default for Multicast
System Feature
Firmware Revision/ Software Version 18.11
An RPI limit can be set for produced/consumed tags in applications where multicast communication connections are used. When this option is configured, a producing controller verifies that the RPI of incoming connections are within the produced tag settings. If the consuming tag's RPI falls outside the configured range, a producing controller will reject the incoming RPI and may provide an RPI (default) to the consuming controller. This feature is not available with safety produced/consumed tags.
For more information about RPI Limitations see the Produced and Consumed Tags Programming Manual, publication 1756-PM011.
Add-On Instruction Enhancements
System Feature
Firmware/Software Revision 18
- Add-On Instruction execution performance has been improved when the instruction is scanning false and the EnableInFalse routine is not defined or has been disabled. Typically, an approximate factor of three improvements can be achieved.
- Default Values in an Add-On Instruction definition can be selectively propagated to all Add-On Instruction instances in a project.
- Access to Axis, Coordinate System, Motion Group, and Message tag information is available via GSV and SSV instructions within an Add-On Instruction.
- The GSV instruction can be used to programmatically retrieve key Add-On Instruction information, such as Change History, Revision, Vendor, Name, and Signature.
- The language type of the Logic routine can be changed without redefining the data definition.
- A local tag can be aliased to an Input or Output parameter.
- When Add-On Instruction parameters are added, moved, or modified, all instances of that Add-On Instruction will automatically be adjusted to keep operand tags assigned to the same parameters.
CIP Sync Time Coordination
System Feature
Firmware Revision/ Software Version 18.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65
Use CIP Sync Time Coordination to synchronize the wall clocks of multiple devices in the system. This is a time synchronization extension to CIP, based on and fully compliant with the IEEE-1588 Standard for a Precision Clock Synchronization Protocol for Network Measurement and Control Systems. This functionality is especially important in applications that provide time-stamped information, for example in applications with Alarms and Events, first-fault detection, data logging, and sequence-of-event operations (SOE). For more information about time synchronization using CIP Synchronized Time Coordination, refer to the Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003.
Data Access Control
System Feature
Firmware Revision/ Software Version 18.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65
Two new tag attributes are available: the External Access and Constant attributes. The External Access attribute defines how an external application (that is, an application outside of RSLogix 5000 software or your application code), such as an HMI, historian, or OPC data server, can access a tag. Options you can configure for the External Access attribute include:
The Constant attribute is used to keep the tag from being altered by the controller program or by specified users of RSLogix 5000 software. To keep the program from altering the tag, check the Constant attribute in the Tag Properties dialog box or in the Tag Editor.
For more information about tag data access attributes, see the Logix5000 Controllers I/O and Tag Data Programming Manual, publication 1756-PM004.
Active Step Maintained During SFC Online Edit
System Feature
Firmware Revision/ Software Version 18.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65
Online edits to SFC routines do not always result in the SFC being reset to the initial step. Edits that alter the logic structure of the chart are the only edits that cause the SFC to reset to the initial step.
CIP Motion Using EtherNet/IP Networks
System Feature
Firmware Revision/ Software Version 18.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65
Integrated Motion support over the EtherNet/IP network lets you connect ControlLogix and GuardLogix controllers to Kinetix 6500 drives by using ControlLogix EtherNet/IP modules and standard Ethernet media to use Integrated Motion.
In addition to support for the EtherNet/IP network connections, the CIP Motion Axis Properties Category pages and the Motion Database in RSLogix 5000 programming software let you configure the drives and associated components.
Integrated Motion on the EtherNet/IP network features includes the following:
When using CIP Motion, the EtherNet/IP modules (catalog numbers 1756-EN2T, 1756-EN2TF, 1756-EN2TR and 1756-EN3TR) connected to Kinetix 6500 drives must be configured so that the Time Sync Connection parameter, on the Module Definition screen, is configured to be Time Sync and Motion.
This integration includes common programming, configuration, commissioning, and drive maintenance tools
A new, predefined Axis type AXIS_CIP_DRIVE has been added in version 18 to support the CIP Motion axis. All configuration of axis parameters and association of the axis to the newly supported Kinetix 6500 CIP Motion drives are performed by using the Axis Properties and Drive Properties of the CIP Motion axis. The CIP Motion axis and Kinetix 6500 EtherNet/IP interface drives are supported by using the 1756- EN2F, 1756-EN2T, 1756-EN2TR or 1756-EN3TR module, configured with Time Synchronization and Motion. CIP Motion uses Unicast control-to-drive communications over EtherNet/IP. A CIP Motion axis supports all existing Integrated Motion instructions with the exception of programmatic Tuning. CIP Motion also provides improved axis and drive configuration, commissioning, and diagnostic tools. For more information about EtherNet/IP-based CIP Motion, refer to the CIP Motion Configuration and Startup User Manual, publication LOGIX-UM003.
This release includes the following system features.
Integrated Motion on the EtherNet/IP Network Motor Test and Commutation Angle Test
System Feature
Logix Firmware/RSLogix 5000 Software 19.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L72, 1756-L73, 1756-L74, 1756-L75
With RSLogix 5000 software, version 19, support for defining and commissioning third-party motors is available. You can enter motor name plate data directly into RSLogix 5000 software. You can also use Motor test and Commutation angle test utilities to commission the motor. This enhancement eliminates the need to use custom motor data base files for third-party motor support.
Integrated Motion on the EtherNet/IP Network PowerFlex Support
System Feature
Logix Firmware/RSLogix 5000 Software 19.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L72, 1756-L73, 1756-L74, 1756-L75
When operating in the Integrated Motion mode, all the features and benefits of Logix Integrated Motion are available for the PowerFlex 755 drive. This list of features and benefits includes the following:
This release includes the following system features.
CIP Motion Load Observer
System Feature
Logix Firmware/RSLogix 5000 Software 19.11
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L72, 1756-L73, 1756-L74, 1756-L75
The Load Observer is a new servo loop feature that improves servo performance and robustness and simplifies system tuning.
This release includes the following system features.
QuickConnect – EtherNet/IP Devices
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Socket Connections
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Change Detection
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Electronic Data Sheet AOP
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
This improves the flexibility of the Integrated Architecture by providing a richer integrated experience to more devices.
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Logix Tree, Enhancements to Finding-Adding Devices
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Interpolated Actual Position Acceleration Compensation
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Support for Unicast Connections to Safety I/O Modules
System Feature
|
Cat. No.
|
Available As Of
|
|
1768-L43, 1768-L43S,
1768-L45, 1768-L45S
|
Firmware Revision 20.011/RSLogix 5000
Software Version 20
|
Unicast became the standard communication format for EtherNet/IP I/O in version 18 of RSLogix 5000 software. Version 20 of RSLogix 5000 software now allows Logix controllers to communicate with Safety I/O modules via unicast.
Module Discovery in RSLogix 5000 Software
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Restricted Communication
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Security Authority Binding
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Security settings have been moved to a new Security tab on the Controller Properties dialog. The Security Authority box now shows the name of the FactoryTalk Security Authority that is currently being used for authentication and authorization. By checking the "Use only the selected Security Authority for Authentication and Authorization" checkbox, the project file or the controller containing the project file cannot be accessed by any users unless they are authenticated by this specific FactoryTalk Security Authority.
MDSC – Master Driven Speed Control
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
This release includes the following system features.
Restore minor revision compatibility
System Feature First Identified as of Software Version 20.04
RSLogix 5000 software version 20.04 is aimed to restore minor revision compatibility as known prior to version 20. Files created in version 20.01 and 20.03 can be opened in version 20.04. Version 20.04 also allows you to upload and go online with files downloaded from version 20.01 and 20.03.
For more details, please see Rockwell Automation Knowledgebase Tech Note #720913 (http://www.rockwellautomation.com/knowledgebase/).
This release includes the following system features.
System features in RSLogix 5000 version 20.05
RSLogix 5000 software version v20.05 has this new feature.
Product Policies and Securable Actions
The RSLogix 5000 software version 20.05 supports this FactoryTalk Security Action. Configure the FactoryTalk Security settings in the FactoryTalk Administration Console.
|
Module: View Properties
|
View module properties.
Users with this permission can open device profiles and, when
online with the controller, use the profile to directly interact with
modules and carry out actions such as changing IP addresses.
When this permission is denied, users cannot open device
profiles.
|
This release includes the following system features.
RSLogix 5000 software version v20.06 has no new features.
This release corrects the following anomalies.
Inserting Unicode Characters (Lgx00059649, Lgx00059650, Lgx00059825)
This release corrects the following anomalies.
Structured Text, Project Component References (x32846)
Corrected Anomaly
RSLogix 5000 Software 16.x
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.
FBD Routine Pending Edits (x43429, x41415)
Corrected Anomaly
RSLogix 5000 Software 16.x
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.
Structured Text, Editor (x33122)
Corrected Anomaly
RSLogix 5000 Software 16.x
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.
This release corrects the following anomalies.
Corrected: RSLogix 5000 Software 16.03
Ladder Diagram Content (x76521)
Anomaly
RSLogix 5000 Software 16.00
Ladder Diagram content of a source protected Add-On Instruction is lost when a cut/copy/paste or drag-and-drop operation is performed.
Corrected: RSLogix 5000 Software 16.03
Additional Language Versions (x76156)
Anomaly
RSLogix 5000 Software 16.00
Import of additional language versions of alarm message strings using CSV import does not break correlation between the project and the controller. Attempting to go online with the modified project will therefore not result in a download of the new strings to the controller.
Corrected: RSLogix 5000 Software 16.03
Controller with Multiple Users (x76750)
Anomaly
RSLogix 5000 Software 16.00
With more than one user online to the same controller, when one user deletes ladder rungs while another user is also viewing the same routine, RSLogix 5000 will report a Fatal Error.
Corrected: RSLogix 5000 Software 16.03
Parameters and Local tags (x74231)
Anomaly
RSLogix 5000 Software 16.00
Fatal Error sometimes when opening Parameters and Local tags for an Add-On Instruction
Corrected: RSLogix 5000 Software 16.03
Unable to Create Tags (x75015)
Anomaly
RSLogix 5000 Software 16.00
Unable to create tags when using Add-On Instructions with a large number of parameters
Corrected: RSLogix 5000 Software 16.03
Array Indexing (x75190)
Anomaly
RSLogix 5000 Software 16.00
Array indexing fails to offset properly on SoftLogix5800 and Emulate5000.
Corrected: RSLogix 5000 Software 16.03
Copying Rungs from Project (x76796)
Anomaly
RSLogix 5000 Software 16.00
Fatal Error copying rungs from project open with V16.00 to a project open with a previous version of RSLogix 5000.
Corrected: RSLogix 5000 Software 16.03
Empty Rung (x75192)
Anomaly
RSLogix 5000 Software 16.00
When two users are online to the same controller, creating a rung on one workstation can result in an empty rung being created on another workstation attached to the same controller.
Corrected: RSLogix 5000 Software 16.03
CMP and MVM instructions (x74866, x74897)
Anomaly
RSLogix 5000 Software 16.00
CMP and MVM instructions in Add-On Instruction provide erroneous results when using an INT value
Corrected: RSLogix 5000 Software 16.03
ALMD and ALMA Alarm Configuration (x73812)
Anomaly
RSLogix 5000 Software 16.00
Fatal Error displaying time on the status tab for the ALMD and ALMA Alarm Configuration with non-US Regional Settings
Corrected: RSLogix 5000 Software 16.03
L5X import, Add-On Instructions (x77349)
Anomaly
RSLogix 5000 Software 16.00
Failure to upload project containing Add-On Instructions after L5X import to previously downloaded project. Note that the resolution of this anomaly prevents this condition from occurring, but any existing controllers already in this state will not be affected. In order to be able to upload a controller in this state, it is necessary to redownload the project to the controller using RSLogix 5000 version 16.03 or later.
Corrected: RSLogix 5000 Software 16.03
Data Monitor, Displaying Values (x77419)
Anomaly
RSLogix 5000 Software 16.00
A user entered change to the value of a tag array element or a structure member in the Data Monitor will display the user entered value and not the value computed by the executing logic when both of the following conditions occur: (1) the value is not actually being changed by the logic (always computed to be the same value) and (2) the tag is already expanded in the Data Monitor when the Data Monitor is redisplayed.
Corrected: RSLogix 5000 Software 16.03
Using Tags as Indices (x77630)
Anomaly
RSLogix 5000 Software 16.00
When using tags as indices into complex structures, particularly when used as an Add-On Instruction parameter, SoftLogix 5800 and RSEmulate may not access the correct data within that structure.
Corrected: RSLogix 5000 Software 16.03
Find or Replace Dialog (x76342)
Anomaly
RSLogix 5000 Software 16.00
With Find or Replace dialog open, Ladder Diagram instruction operands or values can be inadvertently modified.
Corrected: RSLogix 5000 Software 16.03
JSR instruction, FBD (x77644)
Anomaly
RSLogix 5000 Software 16.00
JSR instruction in Function Block Routine not prohibiting passing of parameters with data types of ALARM_ANALOG, ALARM_DIGITAL, and LINT. Note that the resolution of this anomaly prevents this condition from occurring by reporting a controller verification error, but any projects created with V16.00 will continue to verify and can be downloaded into a controller. When a project containing a JSR with parameters of these data types is downloaded, undesired behaviors will result, including failure to upload or failure to download again.
Corrected: RSLogix 5000 Software 16.03
Invocation of AOI (x74651)
Anomaly
RSLogix 5000 Software 16.00
Invocation of Add-On Instruction (AOI) in Function Block Diagram will not verify if Input parameters containing the AOI name are wired
Corrected: RSLogix 5000 Software 16.03
Ladder Editor, CPU Maxed Out (x74668)
Anomaly
RSLogix 5000 Software 16.00
Workstation CPU maxed out to 100% when opening the Ladder Editor
This release corrects the following anomalies.
Corrected Anomalies in RSLogix 5000 version 16.05
There are no corrected anomalies in RSLogix 5000 version 16.05.
This release corrects the following anomalies.
Miscellaneous Corrected Anomalies V17
This release corrects the following anomalies.
Miscellaneous Corrected Anomalies V18
Corrected: RSLogix 5000 Software 18.01
1756-ENBT Modules No Longer Displayed (x109295)
Anomaly
RSLogix 5000 Software 18.00
After installing RSLogix 5000 Version 18.00, 1756-ENBT modules are no longer displayed in the I/O tree viewed using RSLogix 5000 Versions 10 or 11.
Corrected: RSLogix 5000 Software 18.02
Data Type of AXIS_CIP_DRIVE (x114899)
Anomaly
RSLogix 5000 Software 18.01
When project data for a tag having a Data Type of AXIS_CIP_DRIVE is exported to an XML format file (.L5X file format), some of the Axis attributes are not exported. This results in those attributes being assigned default values when the XML file is imported.
Corrected: RSLogix 5000 Software 18.02
Incorrectly Reference IO Data (x114908)
Anomaly
RSLogix 5000 Software 18.01
When a project created in a version of RSLogix 5000 software earlier than version 18 is opened, and this project contains tags that are aliased to the I/O data of a DeviceNet Bridge module revision 10 or 11, then the alias tags will incorrectly reference the I/O data. This may result in unexpected program execution, or errors may be reported when the project is verified.
This release corrects the following anomalies.
Miscellaneous Corrected Anomalies V19
Corrected: RSLogix 5000 Software 19.01
Alias Tags Incorrectly Reference I/O Data (x115498)
Anomaly
RSLogix 5000 Software 19.00
Fatal Error editing FBD logic in an Add-On Instruction when using an alias to a parameter.
This release corrects the following anomalies.
Corrected: RSLogix 5000 Software 20.01
Safe State Value (x126967, x126968, x127022)
Anomaly
RSLogix 5000 Software 20.00
Safe State Value out does not work for 1794-IE4XOE2, 1794-OE12, and 1794-OE8H modules
Corrected: RSLogix 5000 Software 20.x
Upload Of A Project With Structured Text (x117134)
Anomaly
RSLogix 5000 Software 19.x
Fatal Error during upload of a project with Structured Text containing line break characters.
Corrected: RSLogix 5000 Software 20.x
Download (x117643)
Anomaly
RSLogix 5000 Software 19.x
Fatal Error during download.
Corrected: RSLogix 5000 Software 20.01
1769-L2y Controller (x126251)
Anomaly
RSLogix 5000 Software 20.00
The Embedded Counters module of a 1769-L2y controller cannot be properly configured for Pulse External Direction. Please refer to the Application Notes section of these release notes for additional details.
Corrected: RSLogix 5000 Software 20.01
1747-AENTR Module Connections (x128112)
Anomaly
RSLogix 5000 Software 20.00
Module connections for the 1747-AENTR module do not work properly because the EDS file for the 1747-AENTR module profile should be version 2.1.
This release corrects the following anomalies.
GDI object leak (x141635)
Corrected Anomaly with RSLogix 5000 v20.04
Graphic device interface (GDI) object leaks occur when expanding the Scope list on the Cross-Reference dialog box and Tag Editor.
Startup delay when no access to internet (x149691)
Corrected Anomaly with RSLogix 5000 v20.04
A long delay or timeout occurs in the software startup when the computer does not have internet access.
Safety Add-On Instructions fail to upload (x134580)
Corrected Anomaly with RSLogix 5000 v20.04
Unable to upload Safety Add-On Instructions when the project has a Safety Signature.
Communication error reported when uploading/downloading file (x132451)
Corrected Anomaly with RSLogix 5000 v20.04
RSNetWorx for DeviceNet reports a communication error when uploading/download a file to a DeviceLogix device in RSLogix 5000 software.
Project Re-Verification (x33403)
Corrected Anomaly
RSLogix 5000 Software 17.x
If you perform an operation that requires re-verification of the entire project (e.g. changing the controller type, compacting the database,
Inhibit Module yields unexpected results (x139052)
Corrected Anomaly with RSLogix 5000 v20.04
When a Flex output module is attached to the 1794-AENTR adapter and configured for a rack-optimized connection, selecting the Inhibit Module check box on the Connection tab in the Module Properties dialog box does not inhibit the module as expected.
A fatal error when Parameter tab is opened (x144803)
Corrected Anomaly with RSLogix 5000 v20.04
Under certain conditions, a fatal error occurs when the Parameter tab is opened in the EDS AOP.
Slow response over VPN Ethernet connection (x145123)
Corrected Anomaly with RSLogix 5000 v20.04
The software is slow when it is communicating with a controller over a VPN Ethernet connection.
Drive faults with an Excessive Position Error fault (x152784)
Corrected Anomaly with RSLogix 5000 v20.04
Under certain conditions after a successful CIP connection, the drive faults with an Excessive Position Error fault immediately after being enabled with an MSO direct command.
Incorrect location information in diagnostic message (x148434)
Corrected Anomaly with RSLogix 5000 v20.04
RSLogix 5000 software logs the wrong location information in the diagnostic message when using a remote session in a terminal services environment.
Cross reference fails to go to referenced location in protected routine (x144398, x159396, x167856)
Corrected Anomaly with RSLogix 5000 v20.04
The Cross Reference dialog box fails to navigate to the referenced location when the routine is protected with the viewable option.
Unable to flash firmware with software (x169634)
Corrected Anomaly with RSLogix 5000 v20.04
Unable to use RSLogix 5000 software to flash firmware if the controller contains a new license.
Absolute feedback devices cannot be changed to Incremental (x133547)
Corrected Anomaly with RSLogix 5000 v20.04
The Startup Method on the Axis Properties dialog box cannot be changed to Incremental for Absolute feedback devices.
This release corrects the following anomalies.
Anomalies in RSLogix 5000 version 20.05
This list identifies the anomalies corrected in RSLogix 5000 version 20.05. Use the identification information provided in parentheses to track the anomaly in future releases or for reference when receiving assistance from Customer Support with a related issue.
Corrected Anomalies
Cross Reference
Attempting to search a tag’s cross-reference multiple times may cause the software to crash.
This anomaly first identified in version 20.04.00. (Lgx00188436)
Add On Instructions
Importing an L5K file with a large Add On Instruction in RSLogix 5000 version 20.05 causes the software to crash.
This anomaly first identified in version 20.04.00. (Lgx00184323)
Performance
Adobe Acrobat Reader DC, used by the Start Pages, causes the RSLogix 5000 software to perform slowly. Version 20.05 removed the dependency of requiring Adobe Reader and removed the Start Pages. Access Online Books and Vendor Sample Projects from the Help menu.
This anomaly first identified in version 28.00.00. (Lgx00200373, Lgx00207632)
Security
This anomaly first identified in version 24.01. (Lgx00191095, Lgx00208159)
This anomaly first identified in version 20.04. (Lgx00194474)
This release corrects the following anomalies.
Unexplained motion (1090045, 1090058)
Unexplained motion possibly caused by the application not recognizing the motion database which could cause the motion configuration to change.
This anomaly first identified in version 12.00.
FactoryTalk Activation component causing incompatibility with Stratus (990492)
FactoryTalk Activation component delivered with RSLogix 5000 application v20.05 is incompatible with Stratus solutions.
This anomaly first identified in version 20.00.
AssetCentre Backup and Compare tasks (942415, 981951, 981960, 1600636, 1170050, Lgx00225888)
AssetCentre Backup and Compare tasks run from one to several days without errors but will then start to receive the error *** RETRY *** - Event (0001) Done - State:256 Status: Logix 5000 Error: Failed to open file <file_name>. ExtErr" Could not CoCreate RSLogix5000Services. Please re-install Logix5000.
This anomaly first identified in version 20.01.
Fatal error can occur when editing an RLL rung using ASCII Editor offline (1244059)
Attempting to delete a rung when online without accepting the edits and then going offline and attempting to accept the edits, puts the rung in an error state but does not delete the rung. Attempting to delete the rung code causes the RSLogix 5000 application to crash.
This anomaly first identified in version 32.04.
Tag does not reference valid reference or target (1241943)
When editing the Type and Data Type values in the Tag Properties dialog in a safety project, applying the changes causes an error Failed to modify the properties of the <project_name>. Tag doesn't reference valid object or target.
This anomaly first identified in version 32.00.
This release has the following known anomalies.
Opening Trend Chart Properties (x26487)
Anomaly
RSLogix 5000 Software 16.x
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%.
Logging Messages to RSMACC/RSAudit (x55161)
Anomaly
RSLogix 5000 Software 16.x
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.
Output Cam Execution Targets (x25982)
Anomaly
RSLogix 5000 Software 16.x
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.
Hardware Overtravel Fault (Lgx0x66998)
Soft Overtravel triggers first then sequential hard overtravel does not stop motion", and Technical Note: ID=21500 "How do I get off a Soft Overtravel?"
This anomaly first identified in version 16.00.
This release has the following known anomalies.
This release has the following known anomalies.
Known Anomalies in RSLogix 5000 version 16.05
There are no known anomalies found in this release.
This release has the following known anomalies.
Corrected: RSLogix 5000 Software 18.x
AutoFlash (x96777)
Anomaly
RSLogix 5000 Software 17.x
AutoFlash lets you select incompatible revisions of firmware when flashing a 1768-L4x Series B controller.
Corrected: RSLogix 5000 Software 18.x
FBD, Pasting An Output Reference (x106135)
Anomaly
RSLogix 5000 Software 17.x
Pasting an output reference by using the FBD Editor may take a long time.
Emulated Controller, Select Slot 0(x79666)
Anomaly
RSLogix 5000 Software 17.x
RSLogix 5000 software does not support selection of slot 0 for an RSLogix Emulate 5000 Controller. If you need to emulate a controller in slot 0, you can perform the following steps:
1. With your emulator project open in RSLogix 5000 software, from the File menu choose Save As to export the project to an .L5K file.
2. Launch a text editor (for example, Notepad), and open the .L5K file.
3. Scroll through the content of the .L5K file until you find the MODULE Local section for the Emulator.
4. Locate the Slot entry, and change the value from its current slot value to slot 0 and save the file.
5. In RSLogix 5000 software, import the edited .L5K file.
You can now configure a controller in slot 0 in RSLogix Emulate 5000 software and then download your Emulator project.
Note that this workaround requires that RSLinx Classic software version 2.54.00 or later be used.
Corrected: RSLogix 5000 Software 18.x
Results Window Not Docked (x92062, x95178)
Anomaly
RSLogix 5000 Software 17.x
Fatal Error closing RSLogix 5000 software or the Results windows when the Results window is not docked.
Corrected: RSLogix 5000 Software 18.x
Cross Reference For A Task (x105511)
Anomaly
RSLogix 5000 Software 17.x
Cross Reference for a task does not show EVENT instructions.
Corrected: RSLogix 5000 Software 18.x
Response Time In A FBD Routine (x96589, x106609)
Anomaly
RSLogix 5000 Software 17.x
When there are a very large number of references to a single tag in an FBD routine, there may be a lengthy response time for some operations (such as starting a pending edit or pasting). General performance improvements in response time have been made for the FBD Editor.
Corrected: RSLogix 5000 Software 17.01
Online Help, MCD Instruction Units Documentation (x93146)
Anomaly
RSLogix 5000 Software 17.00
The Motion Change Dynamics (MCD) instruction units for Speed, Acceleration, and Deceleration are incorrectly documented in the Online Help.
Attempting to import some Add-On Instructions into an existing project generates the error message: Failed to import <file name>. Unable to parse the L5X content.
This anomaly first identified in version 17.00.
To work around this issue, export the Add-On Instruction, modify the file description to remove dashes. Or, open the L5X file in a plain text editor and modify the description to remove dashes. Import the Add-On Instruction.
Corrected: RSLogix 5000 Software 18.x
Guard I/O Safety Module Profiles (x94870)
Anomaly
RSLogix 5000 Software 17.x
Guard I/O Safety module profiles may display offline module configuration data when online.
Corrected: RSLogix 5000 Software 17.01
Safety Module Signature (x92835)
Anomaly
RSLogix 5000 Software 17.00
In some situations, after configuring a safety module, the safety module signature may not be displayed properly.
Corrected: RSLogix 5000 Software 18.x
Printing a Tag (x90726)
Anomaly
RSLogix 5000 Software 17.x
Fatal Error attempting to print a tag from the Watch Pane.
Corrected: RSLogix 5000 Software 17.01
Copying Rungs (x90415)
Anomaly
RSLogix 5000 Software 17.00
Using cut/copy/paste (or drag-and-drop) to copy rungs from a project open with RSLogix 5000 version 17.00 does not always result in all of the copied rungs being pasted (or dropped) into a project open with RSLogix 5000 version 16.03.
Corrected: RSLogix 5000 Software 18.x
Renaming a Tag (x92319)
Anomaly
RSLogix 5000 Software 17.x
Fatal Error renaming a tag in the Ladder Editor while online with Security enabled.
Corrected: RSLogix 5000 Software 18.x
Deleting, Moving an Add-On Instruction Parameter (x97526, x104043)
Anomaly
RSLogix 5000 Software 17.x
When performing edits on the Add-On Instruction Definition dialog box, a Fatal Error may result when deleting or moving an Add-On Instruction parameter after selecting a cell in that row of the table.
Corrected: RSLogix 5000 Software 17.01
Incorrect Peak Current Ratings (x92586)
Anomaly
RSLogix 5000 Software 17.00
Incorrect peak current ratings are being used for Kinetix 6000 SERCOS S1 Advanced Safety drives.
Corrected: RSLogix 5000 Software 18.x
Export (x25260, x90143, x93294)
Anomaly
RSLogix 5000 Software 17.x
Fatal Errors occur during export.
Corrected: RSLogix 5000 Software 18.x
Modified AOI Updates (x89742)
Anomaly
RSLogix 5000 Software 17.x
Online import of a modified Add-On Instruction updates offline image but does not download the change to the controller.
Miscellaneous Known Anomalies V17
Corrected: RSLogix 5000 Software 18.02
1769 Compact I/O Fault (x86275)
Anomaly
RSLogix 5000 Software 17.x
Corrected: RSLogix 5000 Software 18.x
Copy An InOut Parameter (x97828)
Anomaly
RSLogix 5000 Software 17.x
RSLogix 5000 software stops responding when attempting to copy an InOut parameter with the Tag Editor Data Context configured as '<definition>'.
Corrected: RSLogix 5000 Software 18.x
Drive Polarity Setting (x90376)
Anomaly
RSLogix 5000 Software 17.x
Drive Polarity setting is not downloaded to the controller.
Corrected: RSLogix 5000 Software 18.02
PLC/SLC Mapped Tag (x92883)
Anomaly
RSLogix 5000 Software 17.x
Corrected: RSLogix 5000 Software 18.x
Project Documentation Language Configuration (x93475)
Anomaly
RSLogix 5000 Software 17.x
Documentation imported by using the Project Documentation Language Configuration dialog box is sometimes converted to a single line.
Corrected: RSLogix 5000 Software 18.x
Ladder Editor Display Workstation (x91150)
Anomaly
RSLogix 5000 Software 17.x
When the Ladder Editor Display Workstation Option "Display Tag Values for Boolean Operands," is not checked, the Ladder Editor display performance is degraded.
Corrected: RSLogix 5000 Software 17.01
Online Help, Recovery Documentation (x93080, x93094)
Anomaly
RSLogix 5000 Software 17.00
Online Help does not document that certain functions of the software may be temporarily disabled during Automatic Project Recovery file generation.
Corrected: RSLogix 5000 Software 18.x
Language Switching Feature, Undo (x93270)
Anomaly
RSLogix 5000 Software 17.x
Unable to undo editing of rung comments when the Language Switching feature is used to make the edits in more than one language. After the failed attempt to undo the changes, subsequent operations may result in a Fatal Error.
Corrected: RSLogix 5000 Software 18.x
SFC Editor (x83772)
Anomaly
RSLogix 5000 Software 17.x
In the SFC Editor, the scroll rate changes depending on the size of the chart.
Corrected: RSLogix 5000 Software 18.x
Indirect Addressing Of A Bit (x96902)
Anomaly
RSLogix 5000 Software 17.x
Use of indirect addressing of an individual bit does not work in an Add-On Instruction.
Corrected: RSLogix 5000 Software 18.x
Selecting Data Compare (x93555)
Anomaly
RSLogix 5000 Software 17.x
Fatal Error selecting 'Data Compare' option during Partial Import.
Corrected: RSLogix 5000 Software 18.x
Upload (x101730)
Anomaly
RSLogix 5000 Software 17.x
Fatal Errors occur during upload.
Corrected: RSLogix 5000 Software 17.01
Rack Connection (x89372, x94009)
Anomaly
RSLogix 5000 Software 17.00
Rack Connection support is not backwards compatible. Support for Rack Connection Type Definition resulted in Type Definition not being backwards compatible in some scenarios.
Corrected: RSLogix 5000 Software 18.x
Project Using SQR Function (x90619)
Anomaly
RSLogix 5000 Software 17.x
Fatal Error downloading or estimating memory for a project that uses the SQR function within an array index expression.
Corrected: RSLogix 5000 Software 18.x
Dragging of Language Elements (x89871, x94889)
Anomaly
RSLogix 5000 Software 17.x
Fatal Error. (x89871, x94889)
Corrected: RSLogix 5000 Software 18.x
SFC, Force Indication Not Cleared (x96769)
Anomaly
RSLogix 5000 Software 17.x
Removing all SFC forces does not always clear the SFC force indication on the Online Toolbar.
Safety modules fail to instantiate after installation of Ethernet module AOP profile 10.00.3664 (Lgx00170167)
Corrected Anomaly with Studio 5000 Logix Designer v29.00
This release has the following known anomalies.
References In Program Logic Will Not Update (Lgx00125220)
Fatal error on rung edited online (Lgx00127957)
A Fatal Error is reported when performing a copy and paste operation on a rung that is being edited while online.
This anomaly first identified in version 17.01.01.
This release has the following known anomalies.
This sequence of events can result in unexpected tag values:
1. An Add-On Instruction contains an alias parameter that points to a member of a local tag.
2. The alias parameter is changed to a base tag, either by editing the AOI definition directly or by importing a modified Add-On Instruction that overwrites the existing Add-On Instruction.
3. The instance values for the previously aliased parameters now contains unexpected values.
This anomaly first identified in version 18.00.
Follow one of these steps to work around the issue:
Some PlantPAx P_PIDE Add-On Instruction instance values were set to denormalized low REAL values upon import of a P_PIDE 4.00.00 Add-On Instruction into a project that contained a P_PIDE 3.5.xx Add-On Instruction.
This anomaly first identified in version 18.00.
This release has the following known anomalies.
Watchdog Fault During Prescan (Lgx00113376, Lgx00112413)
IMPORTANT: You cannot configure the prescan watchdog value.
This anomaly first identified in version 18.11.
This release has the following known anomalies.
Corrected: RSLogix 5000 Software 19.x
Renamed Safety Task (x106091)
Anomaly
RSLogix 5000 18.x
If the Safety Task in a GuardLogix project is renamed to something other than 'SafetyTask', then any subsequent Partial Import will result in the Safety Task being renamed back to 'SafetyTask'. The properties of the task 'SafetyTask' will be reset back to default values.
Module, Importing Using XML Format (x99961)
Anomaly
RSLogix 5000 Software 18.x
When importing a full project using the XML format (L5X), modules that are configured by using Add-On Profiles (AOP) will revert to their default configuration when imported. Note that the exported XML-format project file contains the correct configuration information. This anomaly does not affect L5K import. Projects exported and imported with an L5K file extension will properly retain AOP module configuration information. In addition, AOP module configuration will be retained when opening a project that has been saved with an ACD file extension.
Corrected: RSLogix 5000 Software 19.x
Copy Instruction, Source and Destination Overlap (x114495)
Anomaly
RSLogix 5000 18.x
When a Copy File (COP) or Synchronous Copy File (CPS) instruction is executed and the Source and Destination elements overlap, then incorrect values are stored. (x114495)
Corrected: RSLogix 5000 Software 19.x
Excessive Number Of GDI Objects (x108518)
Anomaly
RSLogix 5000 Software 18.x
Fatal Error while online editing a Sequential Function Chart routine, due to excessive number of GDI objects.
Corrected: RSLogix 5000 Software 19.x
Align Error (x77113)
Anomaly
RSLogix 5000 Software 18.x
Align error checking for the Alarm Deviation Limit values of a PIDE with checking performed by Logix5000 firmware.
Exceed Unwind Position (x113950)
Anomaly
RSLogix 5000 Software 18.x
(x113950)
Corrected: RSLogix 5000 Software 20.x
Security Privileges Are Not Refreshed (x104480)
Anomaly
RSLogix 5000 18.x
When security privileges are updated by using the FactoryTalk Administration Console while a project is open in RSLogix 5000 software, the new security privileges will not be enforced until refreshing the privileges in RSLogix 5000 software (Tools>Security>Refresh Privileges). Sometimes this does not properly refresh the privileges in RSLogix 5000 software. When this occurs, you need to exit and restart RSLogix 5000 software to properly refresh the security privileges.
Miscellaneous Known Anomalies V18
Corrected: RSLogix 5000 Software 19.x
PLC-5 Controller (x110912)
Anomaly
RSLogix 5000 Software 18.x
When remote data consumed from a PLC-5 controller changes, the updated value is not displayed in RSLogix 5000 software.
Corrected: RSLogix 5000 Software 19.x
LBL Instruction (x111024)
Anomaly
RSLogix 5000 Software 18.x
Fatal Error during download of a Ladder Diagram routine containing online edits of a rung having a LBL instruction.
Corrected: RSLogix 5000 Software 19.x
Changing Data In ALMD Or ALMA Instruction (x110187)
Anomaly
RSLogix 5000 Software 18.x
Correlation problem changing data in ALMD or ALMA instruction in an FBD routine with more than one user online to the same controller.
Corrected: RSLogix 5000 Software 19.x
Import Full Project, Add-On Profiles (x99961)
Anomaly
RSLogix 5000 Software 18.x
Full project import of module configured using Add-On Profiles reverts to default configuration. (x99961)
Corrected: RSLogix 5000 Software 19.x
Axis Properties Revert To Out-Of-Box Values (x113390)
Anomaly
RSLogix 5000 Software 18.x
When a drive whose Electronic Keying is configured as Exact Match is flashed with firmware that changes the minor revision, the motor data in the Axis Properties may revert to the out-of-box values.
Corrected: RSLogix 5000 Software 19.x
223.xxx.xxx.xxx Ethernet address (x111750)
Anomaly
RSLogix 5000 Software 18.x
Unable to use 223.xxx.xxx.xxx as Ethernet address for EN2T and EWEB modules.
Corrected: RSLogix 5000 Software 19.x
Alternate Documentation Language (x114374)
Anomaly
RSLogix 5000 Software 18.x
Fatal Error editing tag description using an alternate documentation language.
Corrected: RSLogix 5000 Software 19.x
Editing FBD Logic (x112193)
Anomaly
RSLogix 5000 Software 18.x
Fatal Error editing FBD logic in an Add-On Instruction when using an alias to a parameter.
Corrected: RSLogix 5000 Software 19.x
Offline Memory Estimation (x111825)
Anomaly
RSLogix 5000 Software 18.x
Offline memory estimation for 1756-L7x controllers is incorrect.
Corrected: RSLogix 5000 Software 19.x
Cleared Text From Editor Window (x107126)
Anomaly
RSLogix 5000 18.x
When online edits to a large Structured Text routine (around 5000 lines or larger) are accepted, the display of the text in the Structured Text Editor window is cleared. This gives the appearance that all logic in the routine has been removed. In fact the text still exists and the Accept Pending Edits operation was processed. The display can be refreshed by closing and then reopening the Structured Text routine.
This release has the following known anomalies.
Unable to Open Full Project XML Format File (.L5X) for Project File of Later Version of RSLogix 5000 Software than is Being Executed (Lgx00114197)
This release has the following known anomalies.
Corrected: RSLogix 5000 Software 20.x
Long Delay Modifying a Tag Component Description (x120431)
Anomaly
RSLogix 5000 Software 19.x
Long delays may be observed when modifying a tag component description in a tag of a data type which is a deeply nested user-defined data type. (x120431)
Corrected: RSLogix 5000 Software 20.x
Displaying Tag Browser (x114018)
Anomaly
RSLogix 5000 Software 19.x
Long delay may be observed when displaying the Tag Browser.
Miscellaneous Known Anomalies V19
Corrected: RSLogix 5000 Software 20.x
GDI Limit Exceeded, SFC (x107906)
Anomaly
RSLogix 5000 Software 19.x
Online editing of a Sequential Function Chart can result in the GDI handle limit being exceeded. (x107906)
Corrected: RSLogix 5000 Software 20.x
Project With 100 Or More Produced, Consumed Connections (x115288)
Anomaly
RSLogix 5000 Software 19.x
Downloading a project with more than 100 produced or consumed connections may result in a Fatal Error.
RSLogix 5000 reports fatal error in Ladder instruction (Lgx00125908)
RSLogix 5000 reports a Fatal Error while typing in the tag operand field of a Ladder instruction.
This anomaly first identified in version 19.01.00.
Corrected: RSLogix 5000 Software 20.x
Modifying A Tag Component Description (x123573)
Anomaly
RSLogix 5000 Software 19.x
A partially completed Add-On Instruction can be imported. A project containing an invocation of the Add-On Instruction can be downloaded. Upload can result in a Fatal Error.
Corrected: RSLogix 5000 Software 20.x
USB and DF1 bridging (x45686)
Anomaly
RSLogix 5000 Software 19.x
AutoFLASH of motion modules doesn't work when bridged through USB or DF1. (x45686)
Corrected: RSLogix 5000 Software 20.x
Editing a FBD, Fatal Error (x81527)
Anomaly
RSLogix 5000 Software 19.x
Fatal Error while editing a Function Block Diagram.
Corrected: RSLogix 5000 Software 20.x
Copying Tag Of Type MESSAGE (x113029)
Anomaly
RSLogix 5000 Software 19.x
Fatal Error copying a tag of type MESSAGE from one instance of RSLogix 5000 software to a second instance of RSLogix 5000 software.
Corrected: RSLogix 5000 Software 20.x
SFC Action Opened (x116031)
Anomaly
RSLogix 5000 Software 19.x
Fatal Error saving project with SFC Action opened.
Controller displays incorrect date and time (Lgx00182342)
The controller sometimes displays an incorrect date and time: the year is displayed as a large number (for example, 586,384) and the month, day, and time are incorrect.
This anomaly first identified in version 19.01.00.
Fatal error searching for forces (Lgx00133070)
A Fatal Error can be reported when searching for forces in logic.
This anomaly first identified in version 19.01.00.
This release has the following known anomalies.
Corrected Anomaly with Studio 5000 Logix Designer 24.01
On CIP-axis:
the associated Feedback attributes, (in Offline Configuration of Feedback Device) are:
You can edit or enter these attributes in Offline Configuration of Feedback Device:
Revision | values | Res * Interp | = effective
V18.00 | Defaults | 1024 * 2048 |= 2097152 StartUp=[Incremental]
V18.00 | by hand | 1024 * 2097152 | = 2147483648
V18.00 | by hand | 131072 * 10000000 | = 10240000000
(7 0's)
Revision | values | Res * Interp | = effective
V19.01 | Defaults | 1024 * 2048 |= 2097152 StartUp=[Absolute]
V19.01 | by hand | 1024 * 2097152 | =
-2147483648
V19.00 | by hand | 131072 * 10000000 | = -2071986176
(7 0's)
This release has the following known anomalies.
Trying to upgrade the project in the Controller Properties dialog box, from v20.00.00 to v30.00.00, maintaining the same controller, causes a fatal error.
This anomaly first identified in v20.01.
L1 Controller embedded I/O module firmware (Lgx00127607)
For the L1 controller, the controller’s embedded I/O module firmware may not be updated due to a corrupt embedded I/O module firmware image. For more information, see Rockwell Automation Knowledgebase document 498109.
This anomaly first identified in version 20.01.02.
After installing version 30.00 or the version 30.00 AOP Bundle, adding an ENBT, ENT2T or EN2TR module causes a fatal error.
This anomaly first identified in version 20.00.
Output Cam editor with UDT alias causes a crash when you click Apply (Lgx00161890)
When using the Output CAM Editor to make changes to an Output CAM that contains an Alias Tag, you will get a fatal error when you click Apply within the editor. The work around is to use the direct address for the Output CAM operand of the MAOC rather than the alias tag.
This anomaly first identified in version 20.01.
Long Timeout (Lgx00125029, Lgx00125045)
Once the connection to the powered-up PowerFlex 755 drive has been restored, the firmware supervisor will then successfully update the drive's firmware.
This anomaly first identified in version 20.00.
Vendor specific error code (Lgx00137897)
When the controller attempts to open a connection with a 3rd-party device on
EtherNet/IP, it causes the device to return a vendor specific error (0x01, 0x320). This
error code is interpreted incorrectly in the Logix Designer application Module
Properties dialog box, Connection tab.
This anomaly first identified in version 20.01.02.
Slow Launch Times (Lgx00125369)
Output data remains high for inhibited modules during testing (Lgx00177604)
Corrected Anomaly with Studio 5000 Logix Designer v29.00
The Logix Designer application has been upgraded to a version of MSXML that is supported by Microsoft.
This anomaly first identified in version 20.01.
After performing multiple cross reference tasks and closing the window after tasks, the Logix Designer application stopped performing with error 0xc0000005.
This anomaly first identified in version 20.01.
After changing a BOOL tag value to Decimal, and then saving, closing, and reopening the project file, the value had reset to Float. A BOOL tag reset to Float disabled manual changing of the value between 0 and 1.
This anomaly first identified in version 20.00.
Allow Unicast Consumer Connections check box (Lgx00159102)
When offline in the Logix Designer application, the Allow Unicast Consumer
Connections check box clears or resets itself when changing the Max
Consumers value of a safety product tag for the 1756-L73S/A controller, firmware
version 20.01.00. This does not occur when modifying a standard product tag.
This anomaly first identified in version 20.01.02.
Drive run at small coarse update period (Lgx00132326)
When the drive is running at small coarse update period such that late or lost Drive-to-Controller (D2C) updates are being seen, the Logix controller extrapolates the actual position during the lost D2C updates. The extrapolation algorithm computed the actual position incorrectly that resulted in incorrect velocity. If the actual velocity is plotted, you will see velocity spikes during lost D2C updates.
This anomaly first identified in version 20.01.02.
Tool tip for Dest FAL instruction indicates an undefined tag (Lgx00176367)
Corrected Anomaly with Studio 5000 Logix Designer v29.00
Tool tip for undefined tag in Ladder Editor needs improvement (Lgx00176367)
Corrected Anomaly with Studio 5000 Logix Designer v29.00
Safety Lock LED sometimes fails to show correct status after you restore project from SD card (Lgx00178417)
Corrected Anomaly with Studio 5000 Logix Designer v29.00
Direct Add-on-Profile-to-Device Communication Could Result in Time Out Errors or Communication Routing to the Wrong Device (1927272)
Direct Add-on-Profile-to-device communication could result in time out errors or routing the communication to the wrong device in circumstances where all of the following conditions are met:
This applies to configuration data that goes through unconnected communication to the target I/O device (for instance, uploading/downloading device parameters).
This does not apply to I/O data.
This does not apply to commands from the controller (for instance, inhibiting/uninhibiting a device).
Please see technote BF28941 for additional details.
This anomaly first identified in version 20.00.
Mismatching display resolution and scaling may result in overlapping SFC elements (2122642)
Editing a Sequential Function Chart (SFC)) using a display with a given resolution (for example, 1920 x 1200) and Windows scale setting (for example, 100%), closing the ACD, and then opening the same ACD in another resolution (for example, 3840 x 2160) and Windows scale setting (for example, 150%) may result in overlapping SFC elements.
This release has the following known anomalies.
Component tag deletion causes fatal error (Lgx00129693)
When attempting to delete a component of a tag, such as an array element or a structure member, a dialog box is displayed asking users if they wish to delete the entire tag. Clicking No results in a Fatal Error.
This anomaly first identified in version 20.00.03.
Imported routine fatal error (Lgx00128439)
After configuring the import of a routine, if a tag is renamed and the Show differences only Data Comparison option is selected, a Fatal Error could be reported when the routine is imported.
This anomaly first identified in version 20.00.03.
RUN LED on controller shows wrong state (Lgx00133064)
RUN LED on controller shows wrong state if you overload the system with very fast RPI limits on a CompactLogix controller that is communicating with SDN modules. It may cause the Run LED to incorrectly report Run mode when the controller has not finished its transition to the new mode. If this happens, cycle power to the controller and switch to Program mode when power is applied.
This anomaly first identified in version 20.00.03.
This release has the following known anomalies.
Undefined Tag error (Lgx00190787)
Undefined Tag error displays when spaces are used between commas in the Ladder Editor. Spaces between commas are no longer needed.
This anomaly first identified in version 20.04.02.
Failed to create module library, not registered (Lgx00203463)
Failed to create module library in a project that uses the 1768-L45 controller. The
1768-L45 controller is no longer a supported controller.
This anomaly first identified in version 20.04.02.
After an Add-On Instruction was downloaded, uploading the project caused one of the Add-On Instruction's multi-dimensioned array parameter tag to become invalid. The Logix Designer application generated the error: USER_CONTROL, op errand 1: Invalid size of array. Argument must match number of dimensions.
This anomaly first identified in version 20.04.
Attempting to search a tag’s cross-reference multiple times may cause the software to crash.
This anomaly first identified in version 20.04.
This release has the following known anomalies.
Fatal error can occur when an RLL rung is edited using ASCII Editor offline (1244044)
When the ASCII Editor is used to edit a rung where previously an online pending delete rung edit was accepted offline for the same rung, a fatal error occurs.
This anomaly first identified in version 20.00.
Fatal Error 0xe0434352 when creating, opening, or interacting with a module’s properties after installing a later version of the Studio 5000 Logix Designer application or after installing a new Add-on Profile (3219935)
Fatal Error 0xe0434352 occurs on creating, opening, or viewing of profiles updated with a web-based interface, including 1756 Ethernet modules, 5069 Ethernet Adapters, 5094 Ethernet adapters, 1734 Ethernet Adapters, and 1756 I/O.
This fatal error could occur after an installation of the Studio 5000 Logix Designer application or a stand-alone Add-On Profile (AOP), which causes an upgrade to all module profiles.
The fix for this anomaly is available in the Add-on Profiles update for the 1756 Analog Modules, v40.14.70. The Add-on Profiles can be downloaded from the Product Compatibility and Download Center. For more information on this anomaly and the solution, please see technote ID BF30201.
This anomaly first identified in v20.05.
Errors logged in the Logix Compare Tool and FTAC when running a compare (1170050, Lgx00225888)
When running the Logix Designer Compare Tool or FactoryTalk AssetCentre, the following errors can be logged:
This anomaly is caused by a component of Logix Designer, RSLogix5000Services.exe.
Note this anomaly will only occur with V20.05.00 of the Logix Designer application.
Refer to Knowledgebase document 1129863 for more information.
L1 Controller remove or insert local expansion POINT I/O modules (Lgx00131054)
For the L1 controller, if you remove or insert local expansion POINT I/O modules while under power, you can cause the controller to experience a Major Non-recoverable fault.
This anomaly first identified in version 20.05.00.
FactoryTalk AssetCentre error caused by the Logix Designer application (961951, Lgx00225888)
The following error will appear in FactoryTalk AssetCentre: "ExtErr: Could not CoCreate RSLogix5000Services. Please re-install Logix5000."
This anomaly is caused by a component of the Logix Designer application, RSLogix5000Services.exe, experiencing a fatal error during the compare operation. (View this error in the Windows Event Logs).
While the error in FactoryTalk AssetCentre can affect all asset versions, the version of software causing the error will be apparent in the Windows Event Logs.
This anomaly first identified in version 20.04.
Please refer to Knowledgebase document 1129799 for more information.
Disable Download Project Documentation and Extended Properties features
To include or exclude project documentation and extended properties from a downloaded project, select or clear the
This release has the following known anomalies.
Brand name error on Installation Summary page (1811984)
The Installation Summary page for v20.06 inaccurately states the product name as Studio 5000. It should state the product name as RSLogix 5000.
This anomaly first identified in version 20.06.
Inaccurate size reported for install (1557642, 1822740)
Installing the <rslx5kt> software on a disk other than the C drive causes an inaccurate reporting of the estimated gigabytes required to install the application and the used gigabytes after the installation is complete. The installation fails if there is not enough free space on the C drive, but a warning message does not display to inform you that the installation failed.
This anomaly first identified in version 20.06.
These anomalies are from previous releases but are still known in this release.
Unicode Characters, Does Not Display (Lgx00063773)
Unexplained motion possibly caused by the application not recognizing the motion database which could cause the motion configuration to change.
These anomalies are from previous releases but are still known in this release.
Corrected
Blank Primary Window (Lgx0039239)
Anomaly
RSLogix 5000 Software 16.x
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.
GDI Objects Exceed OS Limit (x48079)
Anomaly
RSLogix 5000 Software 16.x
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.
Memory Estimates for Tags Are Too Low (x75592)
Anomaly
RSLogix 5000 Software 16.x
The amount of controller memory required for tags of ALARM_ANALOG and ALARM_DIGITAL data types is being under estimated by the Memory Estimation feature of the RSLogix 5000 software (Edit -> Controller Properties, “Memory” tab). This can result in a project for which Memory Estimation indicates that the project can be downloaded to a controller, but will report an “out of tag memory” condition when it downloaded.
SERCOS Ring Phase Up (x43750, x43870, x44775)
Anomaly
RSLogix 5000 Software 16.x
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.
Corrected: RSLogix 5000 Software 17.01
Selecting Literature Library Links (x78861)
Anomaly
RSLogix 5000 Software 16.x
Selecting some Literature Library links from Start Pages results in Fatal Error.
Corrected: RSLogix 5000 Software 17.x
Unable to Update 1756-M02AE Module (x71573)
Anomaly
RSLogix 5000 Software 16.x
Using ControlFLASH version 6.00.02, you cannot update the firmware of a 1756-M02AE motion module after a successful update of a controller module. Attempting to do this will generate the error: “#10300 Not enough data received in response of Update”. At this point, the user must exit the ControlFLASH tool and then restart it to allow completion of the 1756-M02AE firmware update. As an alternative, update the 1756-M02AE firmware before updating the controller firmware. In this case, both updates complete properly. Additionally, in the case of firmware updates using AutoFlash, the default sequence is to update controller modules followed by motion modules, which may result in the error “Failed to communicate to the target Device” being generated. The user must then update the 1756-M02AE firmware separately.
Corrected: RSLogix 5000 Software 16.04
Watch List, Deleteing Tags (x75872)
Anomaly
RSLogix 5000 Software 16.03
Fatal Error deleting tags from the Watch list.
Corrected: RSLogix 5000 Software 17.00
RSLogix 5000 Application Non-Responsive (x72467)
Anomaly
RSLogix 5000 Software 16.x
RSLogix 5000 application may be non-responsive when attempting to verify a controller after pasting a coordinate system tag copied from another project.
Corrected: RSLogix 5000 Software 16.04
Lengthy Response Time (x105879, x106519)
Anomaly
RSLogix 5000 Software 16.03
When there are a very large number of references to a single tag in an FBD routine, there may be a lengthy response time for some operations (such as starting a pending edit or pasting). General performance improvements in response time have been made for the FBD Editor.
Corrected: RSLogix 5000 17.x
Boolean Array Passed as InOut Parameter (x77241)
Anomaly
RSLogix 5000 Software 16.x
When performing a download to a SoftLogix 5860 or RSEmulate controller, if the project contains an Add-On Instruction (AOI) which passes a Boolean array to another nested AOI as an InOut parameter, a Fatal Error will occur. The same Fatal Error is observed during memory estimation (Edit -> Controller Properties, “Memory” tab).
Corrected: RSLogix 5000 Software 16.04
Deleting an Add On Instruction (x105875)
Anomaly
RSLogix 5000 Software 16.03
Fatal Error may occur when deleting an Add-On Instruction with logic that references a tag that does not exist.
Corrected: RSLogix 5000 Software 17.01
Add-On Instruction with Aliased Parameters (x87633)
Anomaly
RSLogix 5000 Software 16.x
Fatal Error uploading project containing Add-On Instruction with aliased parameters
Operands Missing V16 (x57337)
Anomaly
First identified in RSLogix 5000 Software 16.x
Additional operands are required for the MAM, MAJ, and MAS Motion instructions (in Ladder Diagram and Structured Text) as part of the Programmable Jerk feature introduced in version 16 of RSLogix 5000. When porting any of these instructions to versions 16 from previous versions of RSLogix 5000 using copy and paste or drag and drop, the new operands are not automatically inserted, resulting in instructions that will not verify. When this occurs the user must make the necessary corrections to the copied instruction. It should be noted that this problem does not exist for converted or imported projects. For Ladder Diagram, a suitable work-around may be to use Partial Export/Import of rungs containing these instructions.
Literal Boolean Input Parameter (x77802)
Anomaly
RSLogix 5000 Software 16.x
When an Add-On Instruction (AOI) containing a literal value for one of its Boolean Input parameters is referenced from a Ladder Diagram routine, an upload of the project will modify the display of the literal value by appending a “.0”. Each time the project is downloaded and re-uploaded, another “.0” is appended, so that after the second download/upload sequence, the project file will not verify and can no longer be downloaded without first editing the modified literal value. The edit may be successfully performed either online or offline. Note, however, that when editing online, because the rung is in an unverified state, the “Finalize All Edits in Program” will not operate. In this case, use of the Accept/Test/Assemble sequence of operations will allow the edit to be completed. This condition does not affect the executing image, which will continue execution using the unmodified literal value. To avoid exposure to this problem, replace the literal value with a reference to a tag having the desired value.
Corrected: RSLogix 5000 Software 17.00
FBD Routine was Optimized (x81630)
Anomaly
RSLogix 5000 Software 16.x
Searching throughan FBD Routine was optimized to reduce the amount of time it takes to perform Search and Replace operations. (x81630)
Associated Tag, Non-Recoverable (x77626)
Anomaly
RSLogix 5000 Software 16.x
In RSLogix 5000 V16.03, the ability to edit the Associated Tag configuration for analog and digital alarm tags has been enabled. If an alarm tag is referenced in executing logic, any attempt while online to remove an Associated Tag for that alarm tag may result in a Major Non-Recoverable Fault in the controller.
Hardware Overtravel Fault (x66998)
Anomaly
RSLogix 5000 Software 16.x
For Kinetix 6000 axes configured in RSLogix 5000, if you have both Soft Overtravel and Hardware Overtravel Limits enabled, and you configure the Soft Overtravel Fault Action as "Status Only", be aware that a Hardware Overtravel Fault Action configured for "Stop Motion" may not "Stop Motion" due to the two faults existing together and the first fault action being set to "Status Only". For more information refer to Technical Note: ID=36709 "2094 Kinetix 6000; Soft Overtravel triggers first then sequential hard overtravel does not stop motion", and Technical Note: ID=21500 "How do I get off a Soft Overtravel?"
Corrected: RSLogix 5000 Software 17.00
Servo Off Error (x77218)
Anomaly
RSLogix 5000 Software 16.x
When the axis is in the Safe-Off mode, an MAS-Gear results in an error 05 (Servo Off Error).
Download Fails with Communication Time-out (x01853)
Corrected Anomaly
RSLogix 5000 Software 16.x
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.
GDI Object Leaks, Child Windows (x66929)
Anomaly
First identified in RSLogix 5000 Software 16.x
Repeatedly opening and closing child windows may cause the number of graphics device interface (GDI) objects to increase when running RSLogix 5000 on Windows XP SP2 or on Windows Server 2003 with the Themes service started. Example child windows include, but are not limited to: the Controller Properties dialog, the Ladder Routine window, and the SFC Routine window. The leaks are minor in nature, but it is possible that unpredictable behavior can occur if the number GDI objects gets excessively high. This issue is documented in the Microsoft Knowledgebase article http://support.microsoft.com/?kbid=319740, which also provides instructions for obtaining a supported hotfix from Microsoft. A temporary work-around is to set the display properties to Windows Classic Theme.
Corrected: Logix Firmware/RSLogix 5000 17.02, 17.06
Indirectly Addressing an Instance Tag (Lgx00077261)
Anomaly
Logix Firmware 16.x
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-63S, 1756-L64
An instance tag is associated with each individual call to an Add-On Instruction (AOI). In Version 16.00 of RSLogix 5000, if this instance tag is a tag array element that is indexed by another tag (referred to as indirect indexing), then execution of the routine will result in undesired behavior (e.g., Major Non-Recoverable Fault, Watch Dog time-out, Major Fault). As an example, in the instruction call to "MyAOI(AOIData[Index])", the value of the tag "index" would be used to select which AOIData tag element is used by the call to MyAOI. In Version 16.03, the use of a tag as an index into an AOI instance tag array will result in a controller verification error, which will prevent the project from being downloaded. Note that the AOI instance tag may be defined as an element of a tag array provided it is referenced using a constant value (e.g., MyAOI(AOIData[2], where the constant 2 references the third element of the AOI tag instance array). Also note that indirect indexing operations may be used for the Input and Output Parameter tags of an AOI without a problem. The ability to use indirect indexing operations for AOI instance tags will be provided in a future version of RSLogix 5000.
Backup Files are Deleted (x75665)
Anomaly
RSLogix 5000 Software 16.x
RSLogix 5000 provides a workstation option to maintain multiple backup copies of the project file each time a save operation is performed. If the backup files are stored on a centralized server that is accessed by multiple workstations, it is important to configure the backup quantity on each workstation to the same number. When RSLogix 5000 accesses a project and saves it, if the backup quantity configured on that workstation is set to a lower number than it is on other workstations, then the extra backup files will be deleted without warning. To avoid losing these backup files make sure that the RSLogix 5000 “Number of Backups” Workstation Option (Tools->Options->Application) on all workstations is set identically.
Corrected: RSLogix 5000 Software 16.04
Paste of User Defined Type (x94806)
Anomaly
RSLogix 5000 Software 16.03
Fatal Error during paste of User Defined Type from a version of RSLogix 5000 that has Multi-language support enabled.
Corrected: RSLogix 5000 Software 17.01
Start Pages (x83020)
Anomaly
RSLogix 5000 Software 16.x
Fatal Error reported from Start Pages if workstation is not connected to the network.
User-Defined Data Type Size Limits (x03090, x06296)
Anomaly
RSLogix 5000 Software 16.x
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.
Remote CompactLogix Controller (x72948)
Corrected Anomaly
RSLogix 5000 Software 16.x
A remote CompactLogix port/controller is created with default electronic keying of “Compatible Keying”. If the firmware in this remote CompactLogix controller is upgraded, it is necessary to also upgrade the firmware for other controllers communicating with this remote controller. There is a workaround for this problem which involves re-importing and downloading the project. First, export the project, and modify the following two attributes for the remote controller MODULE: “CompatibleModule := 0, KeyMask := 2#0000_0000_0000_0000”. Then import the project and download to the controller. This problem has been corrected in RSLogix 5000 Version 16.03 with an enhancement to create the port/controller with default electronic keying of “Disable Keying” and to allow the keying to be edited.
Corrected: RSLogix 5000 Software 17.00
Controller Scope Tag (x07963)
Anomaly
RSLogix 5000 Software 16.x
A warning should be displayed when creation or deletion of a program scope tag cause program logic to rebind to or from a Controller scope tag with the same name.
Corrected: RSLogix 5000 Software 17.00
SFC, FOR or BREAK Instruction (x73342)
Anomaly
RSLogix 5000 Software 16.x
Attempting to execute a program containing a FOR or BREAK instruction that calls a Sequential Function Chart subroutine results in major fault of the SoftLogix5860 controller.
Corrected: RSLogix 5000 Software 17.01
Tag Browser (x87132)
Anomaly
RSLogix 5000 Software 16.x
The Tag Browser was optimized to reduce the amount of time it takes display tags in the Tag Browser.
Project Re-Verification Operations (Lgx00033403)
Corrected Anomaly
RSLogix 5000 Software 16.x
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.
Inserting Unicode Characters (Lgx00059649, Lgx00059650, Lgx00059825)
Anomaly
RSLogix 5000 Software 16.x
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 a Unicode character string with no edit control opened. When this occurs, you can press [Esc] on the keyboard to cancel the input and then open the desired edit control before entering the Unicode character string.
Corrected: RSLogix 5000 Software 16.04
Dragging of Language Elements (x89871, x94889)
Anomaly
RSLogix 5000 Software 16.03
Continued dragging of language elements in any of the four programming language editors (LD, FBD, SFC, or ST) may result in a Fatal Error.
Corrected: RSLogix 5000 17.00
Array Bounds (x77270)
Anomaly
RSLogix 5000 Software 16.x
When a tag of a User Defined Type (UDT) is passed into an Add-On Instruction (AOI), the array bounds may not be properly checked, resulting in either a major fault or a data memory corruption. The conditions when this will occur are (1) a 1-dimensional array of a UDT is passed into an AOI, (2) the UDT contains a member that is an array, and (3) in the AOI logic an operand specifies an immediate member of the UDT array and a variable element of its member array (e.g., array[0].memberArray[x]). A workaround is to use a variable for the UDT array index (e.g., array[ZeroTag].memberArray[x])
Corrected: RSLogix 5000 17.x
FGEN Instruction, Downloading (x73042)
Anomaly
RSLogix 5000 Software 16.x
In an FBD routine, the FGEN instruction has two optional parameters, X2 and Y2. If these parameters are omitted, attempts to download the project to a SoftLogix controller will result in a Fatal Error. The same Fatal Error would also be observed when downloading using RSEmulate. A workaround to avoid this problem involves specifying a dummy tag for the X2 and Y2 parameters. The tag used for X2 and Y2 must be an array of type REAL (e.g., tag of data type REAL[1]). Also, insure that the parameter XY2SIZE has a value of 0, configurable on the Parameters tab of the FGEN instruction properties dialog.
Module: Modify Properties (Lgx00072088)
Anomaly
RSLogix 5000 Software 16.x
With the security action “Motion: Modify Configuration” granted, you should be allowed to modify the motion configuration. You are allowed to change the axis association to a module from the Axis Properties dialog but are erroneously prevented from making this change from the Module Properties dialog. To allow the axis association to be configured on the Module Properties dialog, grant access for the security action “Module: Modify Properties”. This will enable all of the tabs of the Module Properties dialog, including the Axis Association tab.
Unicode Characters, Does Not Display (Lgx00063773)
Anomaly
RSLogix 5000 Software 16.x
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.
Corrected: RSLogix 5000 Software 16.04
Print Routine with Tag Cross-References(x81836)
Anomaly
RSLogix 5000 Software 16.03
No response from RSLogix 5000 software when attempting to print routine with a large number of tag cross-references.
Corrected: RSLogix 5000 Software 17.00
Standard Tag List (x79147)
Anomaly
RSLogix 5000 Software 16.x
Fatal Error selecting tag in Standard Tag list of Safety Tag Mapping dialog box.
Imported Add-On Instruction (x79651)
Anomaly
RSLogix 5000 Software 16.x
When importing an Add-On Instruction (AOI), if referenced AOI’s or User Defined Type’s (UDT’s) already exist in the project but have different structures than what is expected by the imported Add-On Instruction, then the AOI’s local tags may not have the expected default values. If the names, data types, or number of local tags or UDT members in the referenced AOI/UDT have changed, then the layout of the imported AOI’s local tags will differ from the original layout of the exported AOI. The import will attempt to overwrite the default data into the new AOI’s local tags by writing the raw data, byte by byte, from the hexadecimal string in the import file. If the data in the import file is the same size or smaller than the data in the new tags, the import will succeed without displaying a warning; however, the imported values may have been written to completely different local tags than those that were exported, and possibly in a different data format. This condition can happen when an Add-On Instruction is exported without its references.
Corrected: RSLogix 5000 Software 16.04
FactoryTalk AssetCentre server (x105882)
Anomaly
RSLogix 5000 Software 16.03
Fatal Error may occur when the FactoryTalk AssetCentre server is used to upload from a controller into a project that has redundancy enabled.
Motion Impact to Motion Group (x70145, x71388)
Anomaly
RSLogix 5000 Software 16.x
With version 16, there is a slight increase in the overhead for the coarse-update-period rate of the Motion Group when using a 1756-L55 controller. This may appear as a Module Synch Fault when executing a Motion Calculate Cam Profile (MCCM) instruction, especially when running S-Curve profiles with Term type = 2 (command tolerance). This may also be exhibited as a Position error when running several sequential 3-dimensional circles of short arc length using the MCCM instruction with Term type = 2. The workaround is to increase the Motion Group’s coarse-update-period to the next millisecond increment, for example from 4ms to 6ms when using a 1756-MxxSE module. (If running a SERCOS axes, this coarse-update-period must be an even multiple of the SERCOS module cycle time.)
Corrected: RSLogix 5000 17.x
RSLogix 5000 Software Fatal Error When 1756 HART Module Is Deleted From Controller By Another User (x72882)
Anomaly
RSLogix 5000 Software 16.x
The 1756-IF8H and 1756-OF8H HART modules can be configured online using version 16 of RSLogix 5000. If more than one user is accessing the same controller using RSLogix 5000, deleting one of these modules from the I/O Configuration tree will result in a Fatal Error in the RSLogix 5000 application for any other online users who are changing the module definition or who are viewing a confirmation dialog for the deleted module.
Generating WinHlp32 Database for Find Tab (x88677)
Corrected Anomaly
RSLogix 5000 Software 16.x
If you are logged on using an account that does not have Administrator privileges, you may be unable to generate the database for the Find tab for RSLogix 5000 Online Help. An error message will be displayed indicating “Unable to display the Find tab” or “WinHlp32 has stopped working”. This error can be resolved by generating the database while logged on using an account with Administrator privileges. If RSLogix 5000 will be used by an account that does not have Administrator privileges, we suggest that the database be created as part of the installation process while still logged on using an account that has Administrator privileges.
Corrected: RSLogix 5000 Software 17.01
Unable to Set Date/Time (x86590)
Anomaly
RSLogix 5000 Software 16.x
Unable to set Date/Time when RSLogix 5000 is running on a non-English operating system.
Corrected: RSLogix 5000 Software 20.x
AutoFlash Updates (x45686)
Anomaly
RSLogix 5000 Software 16.x
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.
SoftLogix SSV Instruction (x59117)
Anomaly
First identified in RSLogix 5000 Software 16.x
After executing an SSV instruction using SoftLogix, an upload of the project will not retrieve the updated object values. As a workaround, the object attributes can be stored in tags. SSV can then be performed from those tags in an initialization routine. (Note that this is a problem only for the SoftLogix controller; uploads of object values modified by an SSV on other controllers will be successful.)
Corrected: RSLogix 5000 Software 16.04
Configuring Tags During Import of Rungs (x79884)
Anomaly
RSLogix 5000 Software 16.03
Fatal Error may occur when configuring tags during import of rungs from an L5X file.
Corrected: RSLogix 5000 Software 17.00
Undo in Ladder Editor (x74099)
Anomaly
RSLogix 5000 Software 16.x
Undo of value change in Ladder Editor may not revert to original value if display style is also changed.
Corrected: Logix Firmware/RSLogix 5000 Software 17.x
Indirect Indexing (x76136, x77263)
Anomaly
RSLogix 5000 Software 16.x
An instance tag is associated with each individual call to an Add-On Instruction (AOI). In Version 16.00 of RSLogix 5000, if this instance tag is a tag array element that is indexed by another tag (referred to as indirect indexing), then execution of the routine will result in undesired behavior (e.g., Major Non-Recoverable Fault, Watch Dog time-out, Major Fault). As an example, in the instruction call to “MyAOI(AOIData[Index])”, the value of the tag “Index” would be used to select which AOIData tag element is used by the call to MyAOI.
In Version 16.03, the use of a tag as an index into an AOI instance tag array will result in a controller verification error, which will prevent the project from being downloaded. Note that the AOI instance tag may be defined as an element of a tag array provided it is referenced using a constant value (e.g., MyAOI(AOIData[2], where the constant 2 references the third element of the AOI tag instance array). Also note that indirect indexing operations may be used for the Input and Output Parameter tags of an AOI without a problem. The ability to use indirect indexing operations for AOI instance tags will be provided in a future version of RSLogix 5000.
Corrected: RSLogix 5000 Software 17.01
GSV in Add-On Instructions (x75872)
Anomaly
RSLogix 5000 Software 16.x
GSV in Add-On Instruction does not allow Safety class to be selected.
DriveLogix "Major Fault On Controller..." Checkbox Display
Anomaly
RSLogix 5000 Software 16.x
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.
Corrected: RSLogix 5000 Software 18.01
Language Switching Feature, Removing Projects (x87118, x87182)
Anomaly
RSLogix 5000 Software 16.x
When using the Language Switching feature to remove all documentation for a particular language, warnings may be reported if access to any of the documentation is restricted. The text of these warning messages refers to line numbers in files that do not exist and can thus be ignored. The condition that caused the warning messages to be issued, however, is real, and the presence of the messages indicates an attempt to remove documentation whose access is in some way restricted. Among the reasons for this is documentation associated with components that are Secured, Source Protected, Safety Locked, or have a Safety Signature. In order to remove secured or protected components, you will need to first remove these restrictions.
Corrected: RSLogix 5000 Software 16.04
Printing a Report for a Large Project (x106587, x106588)
Anomaly
RSLogix 5000 Software 16.03
A Fatal Error may occur while printing a report for a large project.
These anomalies are from previous releases but are still known in this release.
Operands Missing V17 (x80000)
Anomaly
First identified in RSLogix 5000 Software 17.x
Windows Vista Operating System (x81660)
Anomaly
RSLogix 5000 Software 17.x
There are a number of issues related to compatibility of RSLogix 5000 software with the Windows Vista operating system. The most significant of these includes the following:
These anomalies are from previous releases but are still known in this release.
Unable to Open Full L5X Project File (x114197)
Corrected Anomaly
RSLogix 5000 18.x
If you attempt to open a full project import file that uses XML format (.L5X file format) by using a version of RSLogix 5000 software earlier than the version of RSLogix 5000 software from which the project was exported, then the project will not be opened. An error dialog box will be displayed stating 'Controller revision is not supported'. In order to open an L5X format project file, you will need to first launch a version of RSLogix 5000 software that is at or later than the version from which the project was exported. (One way to launch a particular version of RSLogix 5000 software is to use File>New to create a new controller for the selected Revision.) Note that this anomaly does not affect the way that L5K and ACD project files are opened. When an L5K or ACD file is opened, the appropriate version of RSLogix 5000 software will be automatically launched before opening the project.
Unable to Enable Security (x107466)
Anomaly
RSLogix 5000 18.x
The SetSecKeys tool included with RSLogix 5000 software version 17 and earlier do not work with User Account Control (UAC) turned on. When a SetSecKeys tool earlier than file version 18.0.0.0 is executed with UAC turned on, security appears to be enabled, yet security remains disabled in RSLogix 5000 software. If a version of SetSecKeys earlier than file version 18.0.0.0 is used inadvertently, SetSecKeys file versions 18.0.0.0 and later can still be used to enable security. (Note that depending on the operating system, the file version of SetSecKeys.exe can be viewed on either the Details tab or the Version tab of the File Properties dialog box.)
These anomalies are from previous releases but are still known in this release.
Windows 7 Operating Systems (x111504, x113166, v124864)
Anomaly
RSLogix 5000 19.x
There are a number of issues related to compatibility of RSLogix 5000 software with the Windows 7 operating system. The most significant of these includes the following:
These anomalies are from previous releases but are still known in this release.
XML Full Project (x114197)
Anomaly
RSLogix 5000 20.x
Unable to Open Full Project XML Format File (.L5X) for Project File of Later Version of RSLogix 5000 Software than is Being Executed.
When attempting to open a full project xml format file (.L5X), an error may be reported indicating "Controller Revision not supported". This will occur when the major revision of the xml format file being opened is later than the revision of RSLogix 5000 software being executed.
For example, when executing RSLogix 5000 software version 19, an attempt to open an xml format file for version 20 will report the error. However, when executing RSLogix 5000 software version 20, an attempt to open an xml format file for version 19 will not exhibit the problem. When this error is observed, first switch to the RSLogix 5000 software version for the xml format file, and then open the file. This problem does not affect L5K or ACD files. (x114197)
RSLogix 5000 Software Unresponsive (x129306)
Anomaly
RSLogix 5000 Software 20.x
When the server hosting the FactoryTalk Directory is restarted, RSLogix 5000 software may become unresponsive for about 3-5 minutes. When FactoryTalk Services then become available, RSLogix 5000 software will resume normal operation.
New EDS File Not Displayed (Lgx00124959)
Anomaly
RSLogix 5000 20.x
When a new EDS file is registered from outside RSLogix 5000 software, when RSLogix 5000 software is not running and RSLinx Classic software is running as an application (as opposed to as a service), then the newly registered device will not be available in the Select Module Type dialog box. Note that there is no problem with display of the device when registered outside of RSLogix 5000 software, provided that you first exit the RSLogix 5000 application and shut down the RSLinx Classic application. There is also no problem with display of the device when registered from within the RSLogix 5000 application (such as when using the “ Tools>EDS Hardware Installation Tool” menu). So, if the registered module is not displayed, you can use the “ Tools>EDS Hardware Installation Tool” menu to register the device again.
Long Timeout (x125029, x125045)
Anomaly
First identified in RSLogix 5000 20.x
When a PowerFlex 755 drive loses power during a firmware supervisor update, it can take over 10 minutes for RSLogix 5000 software to report the time out. Once the connection to the powered-up PowerFlex 755 drive has been restored, the firmware supervisor will then successfully update the drive's firmware.
CIP Path Displayed Using AutoFLASH (x124629, x124918)
Anomaly
RSLogix 5000 20.x
When using AutoFLASH to update firmware, a progress dialog box is presented to you during the update. This progress dialog box shows the communication path as ASCII values for the CIP path instead of displaying it in the typical display format such as "AB_ETH-1\10.20.30.40\Backplane\3". This path format is also shown in Audit log messages.
Miscellaneous Known Anomalies V20
Slow Launch Times (x125369)
Anomaly
RSLogix 5000 Software 20.x
When RSLogix 5000 software is launched for the first time after restarting your personal computer, it may take 1 to 3 minutes for RSLogix 5000 software to be available for use. This behavior is also exhibited when launching FactoryTalk Administration Console or any other product that uses FactoryTalk Services Platform. Note that subsequent launches of these applications will not experience this behavior. This is only observed on the first launch of the application after a restart of the personal computer. If you experience launch times significantly longer than 3 minutes, refer to the firewall configuration settings in Tech Note #29402
RSNetWorx Software Cannot Download to Controller (Lgx00124236)
Anomaly
RSLogix 5000 Software 20.x
When attempting to download a project using RSNetWorx software, if the controller firmware is at revision 20 and the controller is in Remote Run mode, then RSNetWorx software will not be able to change the controller mode in order to download. In this case, the controller mode must be changed either by using the keyswitch or by using RSLogix 5000 software version 20.
References In Program Logic Will Not Update (x125220)
Anomaly
RSLogix 5000 20.x
If a project for a CompactLogix controller that is no longer supported is imported as a controller that has expansion I/O, any expansion I/O modules from the original controller are properly moved to the correct expansion slot; however, the references in program logic will not be correspondingly updated. This does not necessarily result in the program failing to verify. Instead, the logic may now be referencing the embedded modules for this controller. This is a problem only when opening a L5K or L5X project file. The references are properly adjusted when opening an ACD file.
"Log On to FactoryTalk" Displayed (Lgx00124955)
Corrected Anomaly with Studio 5000 Logix Designer 24.01
Known Anomaly First Identified as of RSLogix 5000 20.x
When launching RSLogix 5000 software, the "Log On to FactoryTalk" dialog box may be displayed.
This dialog box may be seen when you do not have Administrator privileges on the personal computer and the current user does not exist in the FactoryTalk directory. If this dialog box is cancelled, the RSLogix 5000 software will not be launched. When the dialog box is displayed, entering the credentials for a user that exists in the FactoryTalk Directory will allow RSLogix 5000 software to be launched. Administrator accounts are included in the FactoryTalk Directory by default.
To avoid seeing this dialog box, you can add the current user or user group to the FactoryTalk directory. Follow these steps to add a user or user group to the FactoryTalk directory:
The "Log On to FactoryTalk" dialog bax may also be displayed when using Remote Desktop to connect to the personal computer that is running RSLogix 5000 software. This is due to FactoryTalk Security not recognizing the computer name. To enable access through Remote Desktop for a specific computer, you should add the name of the computer that is initiating the Remote Desktop connection to the "Network\System\Computers and Groups\Computers" folder in the FactoryTalk Administration Console. To allow remote computers to connect using the name of the host computer, open the FactoryTalk Administration Console and log in to the Network directory using your domain credentials. Then navigate to "Network\System\Policies\Security Policy". In the "Computer Policy Settings" section, set "Identify terminal server clients using the name of" to "Server Computer". To allow all computers to connect, set the value of "Require Computer accounts for all client machines" to disabled.
Note that if "Use single sign-on" is set to "disable" in FactoryTalk software, then the "Log on to FactoryTalk" dialog box will be displayed each time RSLogix 5000 software is launched and proper user credentials must be entered in order to continue. (By default, "Use single sign-on" is set to "enable".)
Copying Instructions To V20 From Earlier Version (Lgx00119309)
Corrected Anomaly
RSLogix 5000 20.x
Additional operands are required for the MAJ, MAM, and MATC single-axis Motion instructions and MCLM and MCCM Coordinated Motion instructions as part of the Master-Driven Speed Control (MDCS) feature introduced in version 20 of RSLogix 5000 software. When copying any of these instructions to version 20 from an earlier version of RSLogix 5000 software by using copy and paste or drag and drop, the new operands are not automatically inserted. This results in instructions that will not verify. When this occurs, it is necessary to make the appropriate corrections to the pasted instruction. Note that this anomaly does not exist for converted or imported projects. A suitable workaround for Structured Text instructions may be to use Routine Copy of Structured Text.
These anomalies are from previous releases but are still known in this release.
Web-based Add-on Profiles launch as blank or empty windows with one or multiple instances of Logix Designer running on one PC (5582938, 5766864)
If a space exists in a Windows username and/or the user shell folder path, web-based user interface profiles will launch as an empty window under either of the following conditions:
If multiple instances of Logix Designer are open, the profiles will launch correctly in one of the opened projects. When trying to launch profiles from additional open projects, the profiles will display the blank page.
Workaround: Work in one project of Logix Designer at a time, or log in as a user without spaces in the username.
If the user previously had local administrator privileges that were later revoked, the profiles will display the blank page. User accounts with active local administrator privileges, or usernames that do not contain spaces, are not affected.
Workaround: Create a standard Windows user account that has never been a member of the Administrators group and should not be added to that group in the future. Also, ensure that Logix Designer is not launched using Run as administrator.
This anomaly will be resolved in an upcoming release of Logix Designer Add-on Profiles.
This anomaly first identified in version 20.05.
These anomalies are from previous releases but are still known in this release.
Adding a new case selection in a Structured Text routine (Lgx00166840)
Adding a new case selection in a Structured Text routine can cause the Logix Designer application to shut down.
This anomaly first identified in version 20.03.
This release has the following functional changes from the previous release.
Resizable Horizontal Scroll Bar for Language Editors
Software Enhancement
Firmware Revision/ Software Version 16
With RSLogix 5000 version 16, the horizontal scroll bar for language editors is now resizable. Reducing the size of the horizontal scroll bar increases the available space for routine name tabs, allowing for easier selection and identification of opened routines.
Tag Browser Enhancements
Software Enhancement
Firmware Revision/ Software Version 16
With RSLogix 5000 version 16, the Tag Browser has been enhanced. The Tag Browser now supports the mouse scroll wheel. The Bit Picker for INT and DINT data types now shows which bits are already referenced by an instruction. A description ToolTip has been added for the Bit Picker.
S-Curve MCS stop adjustment via Dynamics Configuration Bits
Software Enhancement
Firmware Revision/ Software Version 16.02, 16.03, 16.06, 16.07
Catalog Numbers 1756-L55Mxx, 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, and 1756-L64
Bits for user definable configuration have been added to the COORDINATE_SYSTEM data type in RSLogix version 16 to allow for more adjustment to the deceleration mechanism for S-Curve profile moves. The DynamicsConfigurationBits attribute allows for configuration setting for these three items:
Generic Ethernet Module Extensions
Software Enhancement
Firmware Revision/ Software Version 16
With version 16 of RSLogix 5000, the Generic Ethernet Module support that is used to interface Logix5000 to 3rd party devices via EtherNet/IP has been extended in a number of ways.
These extensions provide greater flexibility when using this configuration option and expand the functionality so that 3rd party devices can interact more readily with Logix5000.
Source Protected Routines Included in the L5K Export File
Software Enhancement
Firmware Revision/ Software Version 16
Prior to version 16, the source code for protected routines was not included in the L5K export files. With RSLogix 5000 version 16, the encrypted copy of source protected routines is now included in the exported L5K project file, allowing for easier handling and offline manipulation of L5K projects.
AutoFlash for SERCOS Drives
Software Enhancement
Firmware Revision/ Software Version 16
Prior to version 16, the AutoFlash feature allowed users to flash controller and motion module firmware on a project download. In version 16 of RSLogix 5000, the functionality of the AutoFlash feature has been enhanced to also allow for the Kinetix 2000, Kinetix 6000, Kinetix 7000, 1394, Ultra3000, and 8720MC Rockwell Automation SERCOS drives to be firmware flashed. This simplifies the software upgrade process by, in one step, flashing firmware for the controller module, motion modules, and Rockwell Automation SERCOS rings when downloading the application.
AutoFlash for SERCOS Drives
System Feature
Firmware Revision/ Software Version 16.02, 16.03, 16.06, 16.07
Catalog Numbers 1756-L55Mxx, 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, and 1756-L64
The functionality of the AutoFlash feature has been enhanced to allow for the Kinetix 2000, Kinetix 6000, Kinetix 7000, 1394, Ultra3000, and 8720MC Rockwell Automation SERCOS drives to be firmware flashed. This simplifies the software upgrade process by, in one step, flashing firmware for the controller module, motion modules, and Rockwell Automation SERCOS rings when downloading the application.
Find All <tag name> to Row Context Menu Added for Tag Editor / Data Monitor
Software Enhancement
Firmware Revision/ Software Version 16
With RSLogix 5000 version 16, the “Find All <tag name> option has been added to the right-click row context menu in the Tag Editor / Data Monitor.
Ladder Diagram Shorted Branch Verification Warning and Search Option
Software Enhancement
Firmware Revision/ Software Version 16
During startup or debug, a programmer may place a branch, containing no instructions, around a sequence of instructions in the code in order to bypass them. Once this is done, it can be difficult to later find the short. With RSLogix 5000 version 16, the ability to locate these shorts has been made easy by providing both a search option and a configurable verification warning. The existence of shorted branches does not stop download but merely provides a warning that the situation is present.
This release has the following functional changes from the previous release.
Report Enhancements
Software Enhancement
Firmware Revision/ Software Version 16
With RSLogix 5000 version 16, the reports capabilities have been enhanced by including the controller’s properties information. This new report provides a detailed listing of the settings that appear in the controller configuration dialog, including important information like controller type, chassis location, serial port configuration, and the Sequential Function Chart (SFC) execution options.
This release has the following functional changes from the previous release.
Functional changes in RSLogix 5000 version 16.05
RSLogix 5000 software version 16.05 has these changes in functionality since the last release.
Commands removed from the Help menu
Due to compatibility issues with Windows 10, version 16.05 removes the Start Pages and Sample Files commands from the Help menu. If needed, the sample files are located in C:\RSLogix 5000\Projects\Samples.
Windows 10 does not support WinHelp .hlp files
The Help for this version of the software is not supported in Windows 10 and is unavailable for version 16.05 of the RSLogix 5000 software.
MSXML 6.0
This version of RSLogix 5000 software installs MSXML 6.0.
Microsoft .NET Framework 1.1
This version of RSLogix 5000 software removes the dependency of Microsoft .NET Framework 1.1.
Release Notes accessible from the Product Compatibility and Download Center (PCDC)
The release notes for version 16.05 of the RSLogix 5000 software are accessible only from the PCDC.
Import/Export
The Import/Export version number for this version of RSLogix 5000 software is 2.07.00. This table lists the Import/Export versions for previous releases.
|
Release Version
|
Import/Export Version
|
|
16.xx.xx
|
2.07.00
|
|
15.xx.xx
|
2.06.00
|
|
14.xx.xx
|
2.05.00
|
|
13.xx.xx
|
2.04.00
|
|
12.xx.xx
|
2.03.00
|
|
11.xx.xx
|
2.02.00
|
|
10.xx.xx
|
2.01.00
|
|
9.00.00
|
2.00.00
|
|
5.02.00
|
1.02.00
|
|
2.xx.xx, 6.xx.xx, 7.xx.xx, 8.xx.xx
|
1.01.00
|
|
1.21.00, 1.23.00
|
1.00.00
|
|
1.10.00, 1.11.00
|
0.04.00
|
This release has the following functional changes from the previous release.
Alarm Grid Display Mode Added to Tag Monitor
Software Enhancement
Firmware Revision/ Software Version 17
In support of FactoryTalk Alarms and Events, version 17 of RSLogix 5000 software now allows alarm tags with data types of ALARM_ANALOG and ALARM_DIGITAL to be displayed in a grid style.
This release has the following functional changes from the previous release.
Ladder Diagram Parameter Display Optimization Options
Software Enhancement
Firmware Revision/ Software Version 17
With version 17 of RSLogix 5000 software, there are additional Workstation Options for displaying operands on a Ladder Diagram instruction faceplate. These options can be used to reduce the amount of space required for display of the ladder code and to improve the readability of instructions.
Verification Warning if Always False Instructions (AFI) are Present
Software Enhancement
Firmware Revision/ Software Version 17
There is a Workstation Option in version 17 of RSLogix 5000 software that enables a warning to be displayed during verification and download if AFI instructions are present in the project. This option is enabled by default.
Coordinated System Time (CST) Master Existence Check on Download
Software Enhancement
Firmware Revision/ Software Version 17
Applications with Motion Groups and GuardLogix controllers require a target controller to be designated as the Coordinated System Time (CST) master. With version 17 of RSLogix 5000 software, this designation can now be made directly from the Download dialog box.
Forcing Added to Quick Watch Window
Software Enhancement
Firmware Revision/ Software Version 17
The Quick Watch window for version 17 of RSLogix 5000 software now displays the force mask.
Scripting Available for the ControlFLASH tool, version 7.0
Software Enhancement
Firmware Revision/ Software Version 17
The ControlFLASH tool, version 7.0, provided as a tool with version 17 of RSLogix 5000 software, has been enhanced to allow for command line execution and script execution. Both methods provide status for interrogation on success/fail flash operations.
SFR Instruction Filters Routine Types and Step Names
Software Enhancement
Firmware Revision/ Software Version 17
In version 17 of RSLogix 5000 software, the operand pull-down menus for the Sequential Functional Chart Reset (SFR) instruction have been enhanced to display only SFC type routines and only tags of SFC_STEP data type.
Verification Warning if I/O Forces are Present
Software Enhancement
Firmware Revision/ Software Version 17
There is a Workstation Option in version 17 of RSLogix 5000 software that enables a warning to be displayed during verification and download when I/O forces are present in the project. This option is enabled by default.
Toggle Bit Added to Quick Watch Window
Software Enhancement
Firmware Revision/ Software Version 17
The Quick Watch window for version 17 of RSLogix 5000 software now provides a menu option to toggle bit values.
This release has the following functional changes from the previous release.
Language Editor User Interface Enhancement
Software Enhancement
Firmware/Software Revision 18
When specifying an operand for an instruction, the text entry field has been enhanced to auto-size, providing additional space for editing the text.
AutoFlash User Interface Enhancement
Software Enhancement
Firmware/Software Revision 18
When using AutoFlash to update firmware for a GuardLogix controller, you are now prompted only once for the firmware revision. Both the primary controller and the partner module are then flashed with the same revision of firmware.
Tag Name Wrapping in Ladder Editor
Software Enhancement
Firmware/Software Revision 18
New workstation options allow tag names in logic to wrap, to be truncated, or to be right or left justified.
Report Enhancements
Software Enhancement
Firmware/Software Revision 18
The reports capabilities have been enhanced. Reports can be generated for all components in the Controller Organizer, including tasks, programs, equipment phases, routines, and modules. A table of contents is included with generated reports.
Quick View Pane Enhancements
Software Enhancement
Firmware/Software Revision 18
The following enhancements have been made to the Quick View Pane:
- More attributes are now shown in the Quick View Pane for items selected in the Controller Organizer.
- The ability to hide and show the Quick View Pane has been provided.
Keep Zoom Centered
Software Enhancement
Firmware/Software Revision 18
When using zoom in the SFC Editor or the FBD Editor, the logic display will remain centered.
HTML Online Help
Software Enhancement
Firmware/Software Revision 18
RSLogix 5000 Online Help uses HTML as the display mechanism. This HTML Help display mechanism replaces the WinHelp display mechanism, which is no longer supported by the Microsoft Corporation. This change affects Online Help for RSLogix 5000 software version 18 and Online Help for Add-On Profiles. Earlier versions of RSLogix 5000 software continue to use the WinHelp display mechanism.
Equipment Phase Monitoring Enhancements
Software Enhancement
Firmware/Software Revision 18
The following enhancements have been made to provide additional information when monitoring an equipment phase:
- The display shows when logic is associated with a specific phase.
- The display shows when a producing or standing-by phase is active on the display.
- The equipment list shows a textual indication of the current state of each piece of equipment without having to open each one individually.
- Multiple instances of the display can be opened.
Tag Filtering Enhancements
Software Enhancement
Firmware/Software Revision 18
The following enhancements have been made to the filtering capabilities of the Tag Editor:
- Tag display can be restricted to names and/or descriptions containing a user-entered filter string.
- A filter capability is available for alias tags.
- A filter capability is available for tags that have been mapped between Safety and standard controller tags.
Routine Type Selection During Creation
Software Enhancement
Firmware/Software Revision 18
When a new routine is being created, it can now optionally be assigned as the Main, Fault, or Prestate routine.
Watch Pane Quick Watch Enhancements
Software Enhancement
Firmware/Software Revision 18
The following enhancements have been made to the Quick Watch Pane:
- Quick Watch Lists can contain a user-selected group of tags and can be assigned a name, allowing the list to be persistent with the RSLogix 5000 project.
- ToolTips now provide more detailed information in the Quick Watch Pane, such as tag scope.
This release has the following functional changes from the previous release.
Source Protection Enhancements
Software Enhancement
Firmware/Software Version 19
Several enhancements were made to the Source Protection feature in version 19 of RSLogix 5000 software.
- Source protection keys are now masked in the user interface.
- Source protection keys are now case sensitive.
- Additional symbols are now supported in source protection keys.
- Source protection keys can now be named.
This release has the following functional changes from the previous release.
Enabling Security for RSLogix 5000 Software
Software Enhancement
Firmware/Software Version 20
Starting with version 20 of RSLogix 5000 software, security is automatically enabled when FactoryTalk Services Platform software is installed. Installation of RSSecurity Emulator software and execution of the SetSecKeys.exe utility are no longer required. Also starting with version 20 of RSLogix 5000, security permissions are obtained exclusively from the FactoryTalk network directory. Note that RSLogix 5000 software versions 19 and earlier still require installation of RSSecurity Emulator software and execution of the SetSecKeys.exe utility. RSLogix 5000 software versions 19 and earlier can obtain security permissions from either the Local or Network directory, as configured when RSSecurity Emulator software is installed.
V20 Additional Memory Requirements for ControlLogix, GuardLogix, and SoftLogix Controllers
Functional Change Available As Of Version 20
Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L71S, 1756-L72, 1756-L72S, 1756-L73, 1756-L73S, 1756-L73XT, 1756-L73SXT, 1756-L74, 1756-L75
Catalog Numbers 1789-L10, 1789-L30, 1789-L60
If you are upgrading your system through multiple firmware revisions, add all components your application uses for each of the revisions you upgrade through. For example, if you are upgrading from revision 15.x to revision 19.x, total your application components for revisions 15.x to 16.x, 16.x to 17.x, and 17.x to 18.x, and 18. x to 19. x.
If you upgrade from 19.x to 20.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | |||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
Safety |
|
Task |
+ 1312 bytes |
|
X |
|
|
Program |
+ 16 bytes |
|
X |
|
|
Equipment phase |
+ 8 bytes |
|
X |
|
|
Routine |
+ 24 bytes |
|
X |
|
|
Add-On Instruction |
+ 32 bytes |
|
X |
|
|
Project with any tags that use ALARM_ANALOG or ALARM_DIGITAL data type |
-76 bytes |
|
X |
|
|
Tag that uses ALARM_ANALOG data type |
+ 4 bytes |
|
X |
|
|
Tag that uses ALARM_DIGITAL data type |
+ 24 bytes |
|
X |
|
|
Tag that uses MOTION_GROUP data type |
+ 56 bytes |
|
X |
|
|
Tag that uses COORDINATE_SYSTEM data type |
+ 950 bytes |
|
X |
|
|
Tag that uses AXIS_CIP_DRIVE data type |
+ 676 bytes |
|
X |
|
|
Tag that uses AXIS data type other than AXIS_CIP_DRIVE |
+ 672 bytes |
|
X |
|
|
Standard produced tag |
+ 4 bytes + (4 bytes x number of consumers) |
X |
|
|
|
Standard consumed tag |
+ 12 bytes |
X |
|
|
|
Safety produced tag |
+ 4 bytes |
|
|
X |
|
Safety consumed tag |
+ 4 bytes |
|
|
X |
|
I/O module |
+ 8 bytes |
|
X |
|
|
Module input connection |
+ 4 bytes |
|
X |
|
|
Module output connection |
+ 4 bytes |
|
X |
|
|
For each controller (> 1 K bytes change): |
|
|
|
|
|
1756-L6x controller |
+ 1264 bytes |
|
X |
|
|
1756-L6x controller |
+ 1268 bytes |
X |
|
|
|
1756-L6xS controller |
+ 1316 bytes |
|
X |
|
|
1756-L6xS controller |
+ 1312 bytes |
X |
|
|
|
1756-L7x controller |
+ 5588 bytes |
|
X |
|
|
1756-L7x controller |
+ 1296 bytes |
X |
|
|
|
1768-L4x, 1768-L4xS controller |
+ 1212 bytes |
|
X |
|
|
1768-L4x controller |
+ 1292 bytes |
X |
|
|
|
1768-L4xS controller |
+ 1340 bytes |
X |
|
|
|
1768-L4xS controller |
+ 1312 bytes |
|
|
X |
|
1769-L23 controller |
+ 2488 bytes |
X |
|
|
|
1769-L31 controller |
+ 2492 bytes |
X |
|
|
|
1769-L32C, 1769-L35CR controller |
+ 2812 bytes |
X |
|
|
|
1769-L33E, 1769-L35E controller |
+ 2496 bytes |
X |
|
|
If you upgrade from 18.x to 19.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
NA |
<no change> |
|
|
If you upgrade from 17.x to 18.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Program |
+ 8 bytes |
|
X |
|
Equipment phase |
+ 20 bytes |
|
X |
|
Add-On Instruction |
+ 12 bytes |
|
X |
| Each tag
In addition, if you use a tag of the types listed below, increase the memory as indicated for each instance: |
+ 4 bytes |
|
X |
|
Produced tag |
+ 36 bytes + (24 bytes * number of consumers) |
X |
|
|
Consumed tag |
+ 24 bytes |
X |
|
|
Data access control |
+ 4 bytes per symbol |
|
X |
|
Tag that uses ALARM_ANALOG data type |
- 20 bytes |
|
X |
|
Tag that uses ALARM_DIGITAL data type |
+ 28 bytes |
|
X |
|
Tag that uses MOTION_GROUP data type |
+ 76 |
|
X |
|
Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type |
+ 786 bytes |
|
X |
|
Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE |
+ 818 bytes |
|
X |
|
Tag that uses COORDINATE_SYSTEM data type with no transform dimensions |
+ 40 bytes |
|
X |
|
Tag that uses COORDINATE_SYSTEM data type with transform dimensions |
+ 100 bytes |
|
X |
|
Module input connection |
+ 20 bytes |
|
X |
|
Module output connection |
+ 24 bytes |
|
X |
|
Safety controller |
- 8 bytes |
|
X |
|
Safety partner |
- 8 bytes |
|
X |
|
For each controller (> 1k bytes change): |
|
|
|
|
1756-L6x, 1756-L6xS, 1756-L63XT |
+ 16728 bytes |
|
X |
|
1768-L4x, 1768-L4xS |
+ 14448 bytes |
|
X |
|
1769-L2x |
+ 35084 bytes |
X |
|
|
1769-L31 |
+ 14740 bytes |
X |
|
|
1769-L32C, 1756-L35CR |
+ 35400 bytes |
X |
|
|
1769-L32E, 1756-L35E |
+ 35036 bytes |
X |
|
|
1789-L10, 1789-L30, 1789-L60 |
+ 4992 |
X |
|
If you upgrade from 16.x to 17.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Task |
+ 4 bytes |
|
X |
|
Program |
+ 4 bytes |
|
X |
|
Equipment phase |
+ 8 bytes |
|
X |
|
LD routine |
+ 12 bytes |
|
X |
|
FBD routine |
- 8 bytes |
|
X |
|
SFC routine |
+ 28 bytes |
|
X |
|
ST routine |
+ 4 bytes |
|
X |
|
Add-On Instruction |
- 12 bytes |
|
X |
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Produced tag |
+ [4 bytes + (4 bytes * number of consumers)] |
X |
|
|
Consumed tag |
+ 8 bytes |
X |
|
|
Tag that uses MESSAGE data type |
+ 4 bytes |
|
X |
|
Tag that uses ALARM_ANALOG data type |
- 64 bytes |
|
X |
|
Tag that uses ALARM_DIGITAL data type |
- 28 bytes |
|
X |
|
Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type |
- 34 bytes
(2 bytes x number of output cam execution targets) |
|
X |
|
Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE |
- 52 bytes
(2 bytes x number of output cam execution targets) |
|
X |
|
Tag that uses COORDINATE_SYSTEM data type of 2 dimensions with 2 transform dimensions |
+ 20 bytes |
|
X |
|
Tag that uses COORDINATE_SYSTEM data type of 3 dimensions with 3 transform dimensions |
+ 108 bytes |
|
X |
If you upgrade from 15.x to 16.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Tag that uses ALARM_ANALOG data type (with no associated tag references) |
+ 16 bytes |
|
X |
|
Tag that uses ALARM_DIGITAL data type (with no associated tag references) |
+ 4 bytes |
|
X |
|
Tag that uses ALARM_ANALOG data type (if associated tags are configured for the ALARM_ANALOG tag) |
+ 22 bytes
+ (9 x the number of configured, associated tags)
+ (3 x the sum of the bytes used by the data type of each of the configured associated tags)
For example, an analog alarm moved to V16.03 with two Associated Tags – one DINT (4 bytes) and one STRING (88 bytes) would need to add: 22 + 9(2) + 3(92) = 316 bytes |
|
X |
|
Tag that uses the COORDINATE_SYSTEM data type |
+ 132 bytes |
|
X |
If you upgrade from 14.x to 15.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Input module |
+ 4 bytes |
X |
|
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Produced tag |
+ 12 bytes |
X |
|
|
Consumed tag |
+ 4 bytes |
X |
|
|
Tag that uses COORDINATE_SYSTEM data type |
+ 748 bytes |
|
X |
|
Tag the uses any AXIS data type |
+ 800 bytes |
|
X |
|
Task |
+ 20 bytes |
|
X |
|
Program or equipment phase |
+ 24 bytes |
|
X |
|
Routine |
+ 4 bytes |
|
X |
|
Serial port |
+ 1120 bytes |
|
X |
|
Project |
+ 4012 bytes |
|
X |
If you upgrade from 13.x to 14.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Tag that uses the COORDINATE SYSTEM data type |
+ 60 bytes |
|
X |
|
Tag that uses any AXIS data type |
+ 4 bytes |
|
X |
If you upgrade from 12.x to 13.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Program |
+ 12 bytes |
|
X |
|
Task |
+ 4 bytes |
|
X |
|
User-defined data type |
+ 4 bytes |
|
X |
|
I/O module |
+ 16 bytes |
X
(8 bytes) |
X
(8 bytes) |
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Produced tag |
+ 8 bytes |
X |
|
|
Consumed tag |
+ 8 bytes |
X |
|
If you upgrade from 11.x to 12.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
I/O module with a comm format = Rack Optimization |
+ 90 bytes |
|
X |
|
I/O module with a comm format = something other than Rack Optimization (such as a direct connection) |
+ 144 bytes |
|
X |
|
CompactLogix 1769 I/O module |
+ 170 bytes |
|
X |
|
Bridge module with a comm format = None |
+ 160 bytes |
|
X |
|
Bridge module with a comm format = Rack Optimization |
+ 220 bytes |
|
X |
If you upgrade from 10.x to 11.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
User-defined data type
|
+ 128 bytes |
|
X |
Indirect address (using a tag as the subscript for an array in an instruction, such as an Array_A[Tag_B]). This memory change applies only if the array:
has only one dimension (such as UDT_1[5]) |
- 60 bytes |
|
X |
If you upgrade from 9.x to 10.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Program |
+ 12 bytes |
|
X |
|
Routine |
+ 16 bytes |
|
X |
If you upgrade from 8.x to 9.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Tag that uses the MESSAGE data type |
+ 376 bytes |
|
X |
If you upgrade from 7.x to 8.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Project |
+ 1050 bytes |
X |
|
|
Tag |
+ 0.55 bytes |
|
X |
| Message that transfers more than 500 bytes of data and targets a controller in the same chassis
This memory is allocated only when the MSG instruction is enabled. To estimate, count the number of these messages that are enabled and/or cached at one time |
+ 2000 bytes |
X |
|
If you upgrade from 6.x to 7.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
If you use a tag of the types listed below, increase the memory as indicated for each instance: |
|
|
|
|
Base tag |
+ 24 bytes |
|
X |
|
Alias tag |
+ 16 bytes |
|
X |
|
Produced tag DINT 4 |
+ 12 bytes |
|
X |
|
Produced tagREAL 4 |
+ 12 bytes |
|
X |
|
Consumed tag DINT 4 |
+ 12 bytes |
|
X |
|
Consumed tagREAL 4 |
+ 12 bytes |
|
X |
|
Routine |
+ 68 bytes |
|
X |
If you upgrade from 5.x to 6.x
|
Then add the following memory requirements to your project |
Which comes from this type of memory | ||
|
Component |
Increase/Decrease Per Instance |
I/O |
Data and Logic |
|
Routine |
+ 116 bytes |
|
X |
Rotation Order Changed for MCT and MCTP Instructions
Software Enhancement
Firmware/Software Version 20
For the MCT and MCTP Transformation Motion instructions, the Orientation operand specifies the rotation vector for Kinematics transformations. In RSLogix 5000 software version 20, the rotation order has been reversed to apply the order of rotations as first about the X-axis, then about the Y-axis, and then about the Z-axis. This impacts the initial position of any MCT or MCTP instruction that uses a 2-dimensional or 3-dimensional rotation. A 1-dimensional rotation is not affected. See also Technical Note #124945.
Safety Signature Deletion in Run Mode Protection
Software Enhancement
Firmware/Software Version 20
A new checkbox prevents the Safety Signature from being deleted while the controller is in Run Mode.
This release has the following functional changes from the previous release.
Full profile support for 1794-IF8IHNFXT module
Functional Change RSLogix 5000 Software Version 20.04
RSLogix 5000 software version 20.04 includes a full profile for the 1794-IF8IHNFXT module. The full profile includes separate configuration tabs in a Module Properties dialog box to make it easier to enter operational data using a user-interface that provides error checking and user-friendly data.
This release has the following functional changes from the previous release.
Functional changes in RSLogix 5000 version 20.05
RSLogix 5000 version 20.05 has these changes in functionality since the last release.
1756 and 1794 classic profiles upgraded to Add-On Profiles
The Add On Profile (AOP) library shipped with version 20.05 updates many 1756 and 1794 I/O device profiles from Classic Profiles to AOPs. These updated Profiles affect all installed Logix Designer and RSLogix 5000 versions on the workstation. Do not share project .ACD files with these updated 1756 and 1794 I/O device profiles with workstations that have installed an earlier versions of the AOP Bundle. For proper compatibility, make sure all workstations are using version 20.05 when sharing ACD projects with these updated Profiles.
|
Tip:
|
These updated 1756 and 1794 I/O device profiles are also released in the AOP Bundle with version 31
and later.
|
Refer to Rockwell Automation Knowledgebase Answer ID 1075943 for more details and a list of updated device profiles.
Import/Export
The Import/Export version number for this version of RSLogix 5000 software is 2.11.00. This table lists the Import/Export versions for previous releases.
|
Release Version
|
Import/Export Version
|
|
20.xx.xx
|
2.11.00
|
|
19.xx.xx
|
2.10.00
|
|
18.xx.xx
|
2.09.00
|
|
17.xx.xx
|
2.08.00
|
|
16.xx.xx
|
2.07.00
|
|
15.xx.xx
|
2.06.00
|
|
14.xx.xx
|
2.05.00
|
|
13.xx.xx
|
2.04.00
|
|
12.xx.xx
|
2.03.00
|
|
11.xx.xx
|
2.02.00
|
|
10.xx.xx
|
2.01.00
|
|
9.00.00
|
2.00.00
|
|
5.02.00
|
1.02.00
|
|
2.xx.xx, 6.xx.xx, 7.xx.xx, 8.xx.xx
|
1.01.00
|
|
1.21.00, 1.23.00
|
1.00.00
|
|
1.10.00, 1.11.00
|
0.04.00
|
This release has the following functional changes from the previous release.
RSLogix 5000 version 20.06 has this change in functionality since the last release.
These security privileges are not supported in RSLogix 5000 version 20.06.
For additional information on FactoryTalk Security product policies, see Appendix A of the Logix 5000 Controllers Security Programming manual, publication 1756-PM016.
The Import/Export version number for this version of RSLogix 5000 software is 2.11. This table lists the Import/Export versions for previous releases.
|
Release Version
|
Import/Export Version
|
|
20.xx
|
2.11
|
|
19.xx
|
2.10
|
|
18.xx
|
2.09
|
|
17.xx
|
2.08
|
|
16.xx
|
2.07
|
|
15.xx
|
2.06
|
|
14.xx
|
2.05
|
|
13.xx
|
2.04
|
|
12.xx
|
2.03
|
|
11.xx
|
2.02
|
|
10.xx
|
2.01
|
|
9.00
|
2.00
|
|
5.02
|
1.02
|
|
2.xx, 6.xx, 7.xx, 8.xx
|
1.01
|
|
1.21, 1.23
|
1.00
|
|
1.10, 1.11
|
0.04
|
This release has the following application notes.
Legal Notices for RSLogix 5000 version 16.05
Copyright Notice
Copyright © 2018 Rockwell Automation Technologies, Inc. All Rights Reserved. Printed in USA.
This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation Technologies, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation Technologies, Inc. is strictly prohibited. Please refer to the license agreement for details.
End User License Agreement (EULA)
You can view the Rockwell Automation End-User License Agreement ("EULA") by opening the License.rtf file located in your product's install folder on your hard drive.
Other Licenses
The software included in this product contains copyrighted software that is licensed under one or more open source licenses. Copies of those licenses are included with the software. Corresponding Source code for open source packages included in this product are located at their respective web site(s).
Alternately, obtain complete Corresponding Source code by contacting Rockwell Automation via the
Contact form on the Rockwell Automation website:
http://www.rockwellautomation.com/global/about-us/contact/contact.page
Please include "Open Source" as part of the request text.
A full list of all open source software used in this product and their corresponding licenses can be found in the OPENSOURCE folder included with these Release Notes. The default installed location of these licenses is C:\Program Files (x86)\Common Files\Rockwell\Help\<Product>\ReleaseNotes\OPENSOURCE\index.htm.
Trademark Notices
Allen-Bradley, Rockwell Automation, RSAlarm, RSAnimator, RSBatch, RSData, RSLogix, Studio 5000, RSLadder, RSLinx, RSNetWorx, RSPower, RSSidewinderX, RSSql, RSTrainer, RSTrend, RSTune, RSView32, RSView, SoftLogix, AdvanceDDE, ControlView, Packed DDE, WINtelligent, WINtelligent Series, WINtelligent LINX, WINtelligent LOGIC 5, WINtelligent VIEW, WINtelligent RECIPE, WINtelligent VISION, WINtelligent VISION2, PLC-2, PLC-3, PLC-5, Data Highway Plus, Data Highway II, MicroLogix, Network DTL, Pyramid Integrator, PanelBuilder, PanelView, SLC, SLC 500, SLC 5/03, ControlFLASH, FactoryTalk, FactoryTalk Services Platform, FactoryTalk View, Kinetix, CompactLogix, Compact GuardLogix, Compact I/O, GuardLogix, CompactBlock Guard I/O, DH+, FlexLogix, PhaseManager, ControlLogix, and SequenceManager are trademarks of Rockwell Automation, Inc.
Any Rockwell Automation software or hardware not mentioned here is also a trademark, registered or otherwise, of Rockwell Automation, Inc.
Other Trademarks
CmFAS Assistant, CmDongle, CodeMeter, CodeMeter Control Center, and WIBU are trademarks of WIBU-SYSTEMS AG in the United States and/or other countries. Intel is a trademark of Intel Corporation. Microsoft and Windows are trademarks of Microsoft Corporation. ControlNet, DeviceNet, EtherNet/IP are trademarks of ODVA, Inc.
All other trademarks are the property of their respective holders and are hereby acknowledged.
Warranty
This product is warranted in accordance with the product license. The product’s performance may be affected by system configuration, the application being performed, operator control, maintenance, and other related factors. Rockwell Automation is not responsible for these intervening factors. The instructions in this document do not cover all the details or variations in the equipment, procedure, or process described, nor do they provide directions for meeting every possible contingency during installation, operation, or maintenance. This product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the accompanying software may have changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this document or the software at any time without prior notice. It is your responsibility to obtain the most current information available from Rockwell when installing or using this product.
Environmental Compliance
Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page
Contact Rockwell Automation
Customer Support Telephone — 1.440.646.3434
Online Support — http://www.rockwellautomation.com/support/
Application notes for RSLogix 5000 version 16.05
These are the application notes for RSLogix 5000 software version 16.05.
Supported Logix Controllers
While the programming software continues to extend its functionality with each new release, the physical controllers that it supports vary. New controllers are added, and in some cases, support for existing controllers may be removed. While a specific controller may not be supported by the current release, the side-by-side installation of multiple versions of the software provide, in most cases, a means to support the older hardware. If migrating from one controller to another, a project created for one controller can be easily converted to another controller using the Controller Properties configuration dialog box within the software.
If opening a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software provides an appropriate warning and automatically provides the option to convert the project to one of the controllers supported by the release.
The table provides a breakdown of the various Logix 5000 controllers and the initial or minimum version of RSLogix 5000 application required to support the controller.
|
Controller Catalog Number
|
Minimum Major
Software Version
|
|
ControlLogix 1756-L55
|
6.00.002
|
|
ControlLogix 1756-L60M03SE
|
6.00.002
|
|
ControlLogix 1756-L61 Series A
|
12.00.00
|
|
ControlLogix 1756-L61 Series B
|
12.00.00
|
|
GuardLogix 1756-L61S Series B
|
14.00.001
|
|
ControlLogix 1756-L62 Series A
|
12.00.00
|
|
ControlLogix 1756-L62 Series B
|
12.00.00
|
|
GuardLogix 1756-L62S Series B
|
14.00.001
|
|
ControlLogix 1756-L63 Series A
|
10.00.00
|
|
ControlLogix 1756-L63 Series B
|
12.00.00
|
|
ControlLogix 1756-L63XT Series B
|
16.00.00
|
|
ControlLogix 1756-L64 Series B
|
16.00.00
|
|
CompactLogix 1768-L43 Series A
|
15.00.00
|
|
CompactLogix 1768-L43 Series B
|
16.03.00
|
|
CompactLogix 1768-L45 Series A
|
16.03.00
|
|
CompactLogix 1768-L45 Series B
|
16.03.00
|
|
CompactLogix 1769-L31
|
13.00.002
|
|
CompactLogix 1769-L32C
|
13.00.002
|
|
CompactLogix 1769-L32E
|
13.00.002
|
|
CompactLogix 1769-L35CR
|
13.00.002
|
|
CompactLogix 1769-L35E
|
12.00.002
|
|
DriveLogix 5730 PowerFlex 700S 2
|
8.00.002
|
|
FlexLogix 1794-L34
|
6.00.002
|
|
SoftLogix 1789-L60
|
6.00.00
|
1 Excludes RSLogix 5000 software version 15.
2 Excludes GuardLogix software version 14.
Microsoft® .NET Framework 4.6 may cause failure in earlier versions of the RSLogix 5000 application
When installing version 16.05 of RSLogix 5000, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:
Do not install version 16.05 of the RSLogix 5000 software on a 32-bit Windows operating system on which any version of the software is installed.
A higher upgrade is already installed on the computer
When installing RSLogix 5000 software version 16.05, the installation fails with the message "A higher upgrade is already installed" when FactoryTalk® Linx™ 6.0 software is installed on the computer. The installation fails on RSLinx Enterprise 5.90.
To avoid this problem, do one of these options.
For more information, refer to Rockwell Automation Knowledgebase Answer ID 1072383.
MSXML 4.0
This version of the software does not install or use MSXML 4.0. MSXML 4.0 has security risks associated with it and is no longer supported by Microsoft. For more information about MSXML and its availability, see the MSXML Roadmap. When installing products or components made by other vendors that use MSXML 4.0, contact the vendor for questions about the security risk associated with MSXML 4.0.
Unattended or silent install
Use command-line parameters to perform an unattended or silent installation of the software.
Installation Command-line parameters
The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").
|
Parameter
|
Description
|
|
/?
|
Displays the usage options for installation parameters.
|
|
/Q
|
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation
using an IT tool or script, and don’t expect any error or restart messages.
When using this parameter, check the error codes, and respond as needed.
For example, if the installation returns error code 1641, then the IT tool or
script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
|
|
/QS
|
Unattended Install, install runs in a quiet simple mode and shows progress
through the UI, it does not accept any input but still shows error or restart
messages.
When using this parameter, the installation will stop and display a prompt if
there are error or restart messages. For example, if an immediate restart is
required to complete the install, a restart message will be displayed to confirm
the restart. Installation resumes automatically from the point of interruption
after restart.
This parameter is required if /Q is not specified.
|
|
/IAcceptAllLicenseTerms
|
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
|
|
/AutoRestart
|
Automatically restarts the computer after the installation is complete. Used
when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used silent install (/Q) will
return either error code 1641 or 3010 if a restart is required, and unattended
install (/QS) will result in a confirmation prompt that must be agreed to before
the installation is completed.
|
|
/Record
|
Records the installation options chosen to a recording file.
This parameter is optional.
|
|
/Playback
|
Plays back a recording file to specify the installation options.
This parameter is optional.
|
|
/Repair
|
Runs a repair operation on the installed products.
This parameter is optional.
|
|
/Uninstall
|
Uninstalls the product.
This parameter is optional.
|
|
/SetupLanguage="value"
|
Specifies which language will be displayed during install process.
The value must be the one of the following:
This parameter is optional. If this parameter is not used, the default language
is the current user or operating system user interface language.
|
|
/Product="value"
|
Specifies which sub-products will be installed.
Only required if sub-products are included with the install package.
If the software does not include sub-products this parameter is not available.
|
|
/ProductLanguage="value"
|
Specifies the language version of the software being installed.
The value must be the one of the following:
This parameter is optional. If this parameter is not used, the default language
is the same as the setup language.
If the software does not support multiple languages this parameter is not
available.
|
| /InstallLocation="value"
Or
/InstallDrive="value"
|
Specifies the install location or install drive respectively.
This parameter is optional. If this parameter is not used, the default install
location is "C:\Program Files (x86)\Rockwell Software".
Some software restricts the installer to only change the drive the software is
installed on. Use /? to determine which parameter is supported.
|
|
/IgnoreWarning
|
Specifies that the setup ignores warnings and continues.
This parameter is optional. If it is not specified, the setup exits when a
warning occurs.
|
|
/SerialNumber="value"
|
Specifies the serial number of the software being installed. This is used to
activate the software during installation.
This parameter is optional. If it is not specified the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required this
parameter is not available.
|
|
/ProductKey="value"
|
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required this
parameter is not available.
|
|
/Version="value"
|
Specifies the version of the software to activate which corresponds to the
product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified the installer will use the most
recent product version available.
Some software does not require activation. If activation is not required this
parameter is not available.
|
Examples
The following examples show how to use the installation commands.
Setup.exe /Q /IAcceptAllLicenseTerms
Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /InstallDrive=D:
Error codes
The following table identifies the error codes that can be returned by an installation.
|
Error Code
|
Value
|
Description
|
|
ERROR_SUCCESS
|
0
|
The installation completed successfully.
|
|
ERROR_INVALID_PARAMETER
|
87
|
One of the parameters was invalid.
|
|
ERROR_INSTALL_USEREXIT
|
1602
|
The installation was cancelled by the user.
|
|
ERROR_INSTALL_FAILURE
|
1603
|
A fatal error occurred during installation.
|
|
ERROR_BAD_CONFIGURATION
|
1610
|
The configuration data for this product is corrupt. Contact your
support personnel.
|
|
ERROR_REBOOT_CONTINUE
|
1641
|
A reboot is required to continue to installation.
|
|
ERROR_SUCCESS_REBOOT_REQUIRED
|
3010
|
A restart is required to complete the installation. After restart the
product is successfully installed.
|
|
ERROR_REBOOT_PENDING
|
3012
|
A restart is pending and is required before the installation can
continue.
|
|
ERROR_SUCCESS_NOT_APPLICABLE
|
3013
|
The installation cannot proceed because the products are
already installed.
|
This release has the following application notes.
Application Notes v17
RSLogix 5000 Software 17.x
The following information is provided to help you better understand the behavior of the RSLogix 5000 software in particular applications or under certain circumstances.
EvRSI activation will be replaced by the FactoryTalk Activation utility in a future release. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Services & Support for information on migrating your activations to FactoryTalk Activation.
In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to create an unscheduled program, a user will need permission for the "Program: Create" action. To create a program scheduled in a task, however, a user will now need permission for both the "Program: Create" and the "Task: Modify Properties" actions. To create a program scheduled in the Power-Up Handler or Controller Fault Handler, a user will now need permission for both the "Program: Create" and the "'Controller: Modify Properties" actions. (x77816, x77817)
McAfee virus software version 8.0 ships with a “Quick Registry Cleaner” component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of RSLogix 5000 classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module. This anomaly will also prevent the creation and import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (x81691)
Version 17 of RSLogix 5000 software provides for the ability to import and export projects using an XML format file (.L5X). If earlier versions of RSLogix 5000 software are installed on the same workstation, it may sometimes appear as if you are unable to open an XML project file. This will occur if the currently executing version of RSLogix 5000 software is one which does not support import/export of project files using XML format. Before attempting to open an XML format project file, the currently executing version of RSLogix 5000 software must be one that supports import of XML project files. A particular version of RSLogix 5000 software can be started by doing one of the following: open an archive file (.ACD) that was last saved using the desired version of RSLogix 5000 software, create a new controller and specify that it be created using the desired version of RSLogix 5000 software, or import a text file (.L5K) and specify that it be imported to the desired version of RSLogix 5000 software. (x87808)
If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software or later, Start Pages will fail to load and the message “Server Startup Failure physicalPath=…” will be displayed. In order to restore Start Page functionality it is necessary to re-install the version 17.00 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of RSLogix 5000 software and later. (x76424)
The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.
A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819, x85559)
The hardwired digital inputs on the new Kinetix6000 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user’s application must be written to make proper use of these digital inputs within the context of the associated motion instructions.
Creation of an RSLogix 5000 event task will result in the creation of a Microsoft Windows event with the same name. Since Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.
If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 16, you will need an updated motion database to work with RSLogix 5000 software version 17. To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.
When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from RSLogix 5000 software may result in a dialog box being displayed with the message “Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?” This issue is documented in the Adobe Knowledgebase article http://kb.adobe.com/selfservice/viewContent.do?externalId=321561&sliceId=2, which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation. A temporary workaround for printing RSLogix 5000 reports is to click No in the dialog box, in the RSLogix 5000 Print dialog box change the printer name to some other printer, change the printer name back to Adobe PDF, and then click OK to print the document. (x88019)
The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there may be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There may also be minor differences in Trapezoidal velocity profiles. Please refer to Technical Note “Motion Planner, version 16.03 Application Solution” publication RA-AP-031 for additional details.
The Kinematics Transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000 software version 16.03) should only be used with version 16.03 or greater of RSLogix 5000 software. If RSLogix 5000 software version 16.00 is used to upload a project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported geometries will be converted to the default Coordinate System Type of “Cartesian”. The message “attribute list error” will be displayed during the download attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision earlier than revision 16.20. (x75769)
Unscheduled Connections are not supported for the current release of the 1757-FFLDC module. Ensure that the “Use Scheduled Connection over ControlNet” checkbox is checked on the Connection tab of all Logix Blocks. (This checkbox is checked by default when a Logix Block is created.)
This application note affects customers who have Beta software for version 17 of RSLogix 5000 software installed on their workstation. The version 17 Install will not offer to uninstall any previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software using Add/Remove Programs.
This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed. However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named “UpdateActionsInSchema.exe”, can be found in the “System\SecuritySchemaUpdate\” directory on the RSLogix 5000 DVD. Note that upon execution, the utility will provide further instructions.
In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.
Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Service Platform, which can be found on the RSLogix 5000 DVD. See the FactoryTalk Security installation instructions for further migration information.
In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups for the RSI Security Server are
They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.
When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed indicating that “Tag: Modify Properties” is not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)
The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9 will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix controllers, and actions, like “Tag Create”, for easier security administration.
Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time Left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (x72583)
Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types: MPL-A, MPL-B, 8720SM-xxxS, and TLY-A110T-Hxx. A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: “Axis ‘<tag_name>’ Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.” When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.
In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: “Warning: During conversion of Axis ‘<tag name>’ – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.” When this warning is encountered, the user should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, the user can reassociate the motor to the axis, but in this case all motor parameters will be Reset to default Motion database values, canceling many previously tuned and saved axis values. This issue does not exist with database conversion of an ACD format project file. The motors that are affected are: MPF-B310P, -B320P, -B330P, -B4430K; MPG-A004-031, -A110-031, -A11-0-091; MPL-A310F, -A430P, -B420P, -B4520P, -B4530F, -B4530K, -B580J, -B980L; TL-A120P-H, -A130P-H, -A220P-H, A230P-H.
A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.
The Controller Time Object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute “DateTime”, then this logic should be updated to use the new attribute “LocalDateTime”. You may also need to make other modifications to your application as a result of this change. (x72073, x72238)
A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions may not properly synchronize workstation time and controller time.
When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:
The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.
We recommended that the Microsoft Windows operating system’s “Language for non-Unicode programs (System Locale)” be configured to match the localized language of the RSLogix 5000 software edition. This is especially true for the Chinese, Japanese, and Korean RSLogix 5000 software editions. Not configuring the PC’s operating system’s System Locale to match the language of RSLogix 5000 software may result in the inability of RSLogix 5000 software to display certain fonts.
If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when RSLogix 5000 software is started. Clicking “Change” on this warning dialog box will navigate to the operating system dialog box from which the user can adjust the System Locale.
The System Locale can then be changed by selecting a new “Language for non-Unicode programs (System Locale)” on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of RSLogix 5000 software (9324-RLD300ZHE), you should select “Chinese (PRC)” for the System Locale.
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 software version 14, the directory structure for temporary RSLogix 5000 folders has been modified so that all AB_xxxx folders now reside within a single folder named “RSLogix 5000.Temp” located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000).
To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the “RSLogix5000.Temp” folder. (x51417, x85503)
The MOTION_INSTRUCTION data type changed in version 12 and later and the size increased from 12 bytes to 16 bytes. If you have created User-Defined data types that include members of type MOTION_INSTRUCTION you will lose tag initial values when you convert your project files from earlier versions. To work around this anomaly, export your project using the pre-version 12 version of RSLogix 5000 software and then import the project in version 12.02 or later. If you have written logic that relies on the old 12-byte size (for example by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that your logic is still correct.
The new MOTION_INSTRUCTION data type structure is:
FLAGS DINT
EN BOOL
DN BOOL
ER BOOL
PC BOOL
IP BOOL
AC BOOL
ACCEL BOOL
DECEL BOOL
ERR INT
STATUS SINT
STATE SINT
SEGMENT DINT
EXERR SINT
Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393)
The REAL data type now shows a 32-bit (4-byte) IEEE floating-point value with the following range:
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
- infinite
+NAN
-NAN
-indefinite
|
1.$
-1.$
1.#QNAN
-1.#QNAN
-1.#IND
|
|
Exponential
|
+infinite
- infinite
+NAN
-NAN
-indefinite
|
1.#INF000e+000
-1.#INF000e+000
1.#QNAN00e+000
-1.#QNAN00e+000
-1.#IND0000e+000
|
The software also stores and displays the IEEE subnormal range:
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 steps and actions were active at the time of the switch. To work around this anomaly, 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)
If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre (RSMACC) server to log messages, RSLogix 5000 software experiences intermittent freezes while it is waiting for the message requests to time out. This might cause RSLogix 5000 software to appear as though it has locked up, but if you wait about one minute it will begin responding again. To resolve this anomaly, either restore the connection to the FactoryTalk AssetCentre (RSMACC) server or disable the RSAudit message logging. Once a connection has been restored, cached messages will be logged to the server and RSLogix 5000 software will resume normal operation. (x36127)
During a file save operation RSLogix 5000 software attempts to compress the contents of a project so that the resulting file (ACD) requires less disk space. When opening a project this process is reversed and the contents of the ACD file are de-compressed. In some instances, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may become abnormally large but it is still usable, that is, you can continue to work with the file as you would normally. However, if you contact Rockwell Automation Services & Support and provide a copy of your project file, this could help the RSLogix 5000 software development team to locate the source of the compression failure.
If you have version 10.00 or later and an earlier version of RSLogix 5000 software installed on your computer, you will observe an activation error if you run the version 10.00 or later version first and then attempt to run the earlier version simultaneously. To work around this anomaly, always run the earlier version first and then run the version 10.00 or later version.
Be careful when performing operations with project files that depend on the default project directory. The Windows operating system controls and retains the default directory for the Open, Save As, and New Controller dialog boxes. Be sure to check that the folder selected is the one you wish to use when performing these operations to avoid mistakenly overwriting your project files. The Project Directory setting in the RSLogix 5000 Tools Options dialog box is normally used unless you navigate to a different directory within the Open, Save As, or New Controller dialog boxes. (x28475, x27886)
In releases earlier than version 10.00 if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner) you could download the project to a controller but may have encountered an error when uploading the project. This anomaly was caused by selecting multiple localized feedback wires in the outside feedback loop. In this release, this condition will be detected as a verification error in the routine. To correct this anomaly, select a feedback wire in the inner loop that is not also in the outer loop to be the localized feedback wire. (x28963, x27712)
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)
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)
The Servo Update Period for the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed from 200 microseconds to 250 microseconds. The servo update period is displayed on the Module Properties dialog box Associated Axes tab. This change in the Servo Update Period will have no affect on the behavior of existing motion control applications or on the overall performance of the motion control system. (x28647)
In version 12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in program mode but will produce a Major Fault if the controller is in run or remote run mode. In versions earlier than version 12.01, the motion group could produce a major fault while the controller was in program or remote program mode. For example, a store to nonvolatile memory interrupts the execution of the motion planner, which produces a fault. (x36957)
With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in RSLogix 5000 software without any user logic being written. However, a Kinetix Axis Module (AM) on the same power rail will require logic to be written if the user expects the motor on the AM to perform in the same manner as does the IAM. This logic should monitor the IAM’s phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes (x71448, x71717).
The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate new checks for reset of the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing changes observed were 20ms in version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)
Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA Sercos drives via ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating. ControlFLASH of the drives on the Ring must be done one drive node at a time.
Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the RA Sercos Drives to support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives must have revision 1.85 or higher, and the RA Ultra Sercos drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later. (x51766)
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)
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.
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 an anomaly with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680, x06823)
|
DLL Name
|
Compatible Versions
| |
|
Comcat.dll
|
4.71
|
5.0
|
|
Ole32.dll
|
4.0
|
4.71 or later
|
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 box 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 box and select the System Protocol tab. Under Error Detection enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000 information dialog box will display the error: “Failed to modify the DF1 Protocol configuration. Communications timed out.” This is expected and normal for this operation, click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC. Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software select Go Online to re-establish online communications. This DF1 driver will now communicate only with Logix5550 Controllers that are setup to use CRC Error Detection.
There is a log file generated that records abnormal events and which can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 software will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title "RSLogix 5000 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”. In order to more effectively address software error conditions, starting with version 14.00, the Fatal Error information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. The new file will be large. If it must be sent to Rockwell Automation Services & Support, it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). The RSLogix 5000 Fatal Error.Dmp file can also be deleted if not needed.
Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for Windows Vista or in C:\Documents and Settings\All Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000. For RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\<username>\Local Settings\Temp (for all operating systems).
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.
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).
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.
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 software version 2.20 or later, or the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.
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. Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may also be deleted.
AB_xxxx folders reside within a single folder named “RSLogix 5000.Temp” located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000).
Caused by a corrupted activation key file (evrsi.sys). To correct this anomaly, contact Rockwell Automation Services & Support by telephone at +1 440-646-3434 or by email at RACleAskTheExpert@ra.rockwell.com.
Application Notes RSLinx Software v17
RSLogix 5000 Software 17.x
You may be prevented from configuring the Ethernet Port of a CompactLogix5532E (1769-L32E) via Channel 0 using RSLinx. To workaround the anomaly, use RSLogix 5000 software 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).
Beginning with RSLinx Classic software version 2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher) version features. Only one professional activation is required for both products. The RSLogix 5000 Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher).
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.
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.
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 anomalies accessing information from I/O modules.
This release has the following application notes.
Application Notes RSLinx Software v18
RSLogix 5000 Software 18.x
In RSLogix 5000 software version 18, there is an External Access tag attribute, which defines how an external application can access a tag. This functionality is fully supported by RSLinx Classic software version 2.56 and RSLinx Enterprise software version 5.21. RSLogix 5000 software version 18 can be used with earlier versions of RSLinx Classic software to go online to a controller; however, earlier versions of RSLinx Classic or RSLinx Enterprise software should not be used as a data server with a controller running version 18 firmware. Unexpected results will be observed when using an earlier version of RSLinx Classic or RSLinx Enterprise software as a data server with a controller running revision 18 firmware.
You may be prevented from configuring the Ethernet Port of a CompactLogix5532E (1769-L32E) via Channel 0 using RSLinx. To workaround the anomaly, use RSLogix 5000 software 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).
Beginning with RSLinx Classic software version 2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher) version features. Only one professional activation is required for both products. The RSLogix 5000 Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher).
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.
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.
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 anomalies accessing information from I/O modules.
RSLinx software maintains knowledge of the memory layout of a Logix5000 controller in order to optimize the data access performance when accessing the data in these controllers. However, changes made to an offline project that are then downloaded can result in RSLinx 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 anomaly, use caution when making offline changes to a project and then downloading to a Logix5000 controller. In particular, changing the size of an array if elements of the array are already on scan, renaming a structure or a member of a user-defined data type used by a tag that is on scan, or changing the data type of a tag on scan from a larger size to a smaller size (e.g. changing a DINT to a SINT). Note that RSLinx Enterprise Series is able to accommodate these changes without requiring a restart.
Application Notes v18
RSLogix 5000 Software 18.x
The following information is provided to help you better understand the behavior of the RSLogix 5000 software in particular applications or under certain circumstances.
EvRSI activation will be replaced by the FactoryTalk Activation utility in a future release. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Services & Support for information on migrating your activations to FactoryTalk Activation.
RSLogix 5000 software version 18 has replaced the concept of Coordinated System Time (CST) Mastership with the more comprehensive notion of Time Synchronization, also referred to as CIP Sync Time Coordination. The Date/Time page of the controller properties has been modified to reflect this change. For projects created with RSLogix 5000 software version 17 or earlier, if Coordinated System Time Master (CST) is enabled, then the converted project will have the Time Synchronization setting enabled. For more information about time synchronization using CIP Sync, refer to publication IA-AT003A-EN-P, “Integrated Architecture and CIP Sync Configuration Application Technique”.
In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to create an unscheduled program, a user will need permission for the "Program: Create" action. To create a program scheduled in a task, however, a user will now need permission for both the "Program: Create" and the "Task: Modify Properties" actions. To create a program scheduled in the Power-Up Handler or Controller Fault Handler, a user will now need permission for both the "Program: Create" and the "'Controller: Modify Properties" actions. (x77816, x77817)
With RSLogix 5000 software versions 17 and earlier, when online SFC edits are tested or untested, the SFC is reset to the initial step and all stored actions are reset. Beginning with version 18.00 of RSLogix 5000 software, many SFC online edits no longer result in this reset. In general, only edits that alter the logic structure of the chart will require the SFC routine to be reset.
McAfee virus software version 8.0 ships with a “Quick Registry Cleaner” component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of RSLogix 5000 classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module. This anomaly will also prevent the creation and import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (x81691)
RSLogix 5000 software versions 17 and earlier do not support full project import when using an XML format file (.L5X). If you have version 17 or later of RSLogix 5000 software installed along with some earlier version of RSLogix 5000 software and you are currently running that earlier version of software, then the Open/Import Project dialog box will not allow a file with an L5X or XML file extension to be opened for import. To open an L5X format project you must first be sure that RSLogix 5000 software version 17 or later is running. You can do this either by creating a new version 17 project or by opening any existing version 17 project that was saved with an ACD or L5K file extension. Alternatively, you can select the L5X project file in Microsoft Windows Explorer by right-clicking the L5X file name and using the “Open with” menu item to open the file with "Component of the RSLogix 5000 Application". Note that when the RSLogix 5000 software is installed, files with an ACD file extension are configured by default to open this way when selected. You can configure files with L5X and L5K file extensions to also do this through Windows Explorer by manually associating these extensions with the executable file RSLogix5000Loader.exe, typically installed in the directory C:\Program Files\Rockwell Software\RSLogix 5000\Common. (x87808)
The Windows Help (WinHlp32.exe) program is used to display RSLogix 5000 Online Help that is provided in 32-bit .hlp files. Microsoft stopped including this 32-bit Help file viewer in Windows releases beginning with Windows Vista and Windows Server 2008. RSLogix 5000 software versions 18 and later display Online Help in HTML format and do not require this Windows Help program. However, some module profiles may continue to display Online Help using 32-bit .hlp files. In order to properly display Online Help that is provided in 32-bit .hlp files on a Windows Vista or later operating system, you will need to install the Windows Help program. This application is available for download from the Microsoft Download Center. For additional information on downloading and installing the Windows Help program, refer to the Microsoft Knowledgebase article “I cannot open Help files that require the Windows Help (WinHlp32.exe) program”, located at http://support.microsoft.com/?kbid=917607.
If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software or later, Start Pages will fail to load and the message “Server Startup Failure physicalPath=…” will be displayed. In order to restore Start Page functionality it is necessary to re-install the version 17.00 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of RSLogix 5000 software and later. (x76424)
The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista or later operating systems. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.
A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819, x85559)
The hardwired digital inputs on the Kinetix 6000 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user’s application must be written to make proper use of these digital inputs within the context of the associated motion instructions.
Creation of an RSLogix 5000 event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same name. Since Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.
If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you will need an updated motion database to work with RSLogix 5000 software version 18. The following table lists the motion database revisions that are used with these RSLogix 5000 software versions.
|
RSLogix 5000 Version
|
Motion Database Revision
|
|
18.00
|
6.7.0
|
|
17.01 / 17.00
|
5.3.0
|
|
16.04 / 16.03 / 16.00
|
4.2.0
|
|
15.03 / 15.02 / 15.01 / 15.00
|
3.24.0
|
|
14.01 / 14.00
|
3.12.0
|
|
13.04 / 13.03 / 13.02 / 13.01 / 13.00
|
3.12.0
|
|
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 12.01 / 12.00
|
3.3.0
|
To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.
When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from RSLogix 5000 software may result in a dialog box being displayed with the message “Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?” This issue is documented in the Adobe Knowledgebase article http://kb.adobe.com/selfservice/viewContent.do?externalId=321561&sliceId=2, which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation. A temporary workaround for printing RSLogix 5000 reports is to click No in the dialog box, in the RSLogix 5000 Print dialog box change the printer name to some other printer, change the printer name back to Adobe PDF, and then click OK to print the document. (x88019)
The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there may be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There may also be minor differences in Trapezoidal velocity profiles. Please refer to Technical Note “Motion Planner, version 16.03 Application Solution” publication RA-AP-031 for additional details.
The Kinematics Transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000 software version 16.03) should only be used with version 16.03 or greater of RSLogix 5000 software. If RSLogix 5000 software version 16.00 is used to upload a project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported geometries will be converted to the default Coordinate System Type of “Cartesian”. The message “attribute list error” will be displayed during the download attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision earlier than revision 16.20. (x75769)
Unscheduled Connections are not supported for the current release of the 1757-FFLDC module. Ensure that the “Use Scheduled Connection over ControlNet” checkbox is checked on the Connection tab of all Logix Blocks. (This checkbox is checked by default when a Logix Block is created.)
This application note affects customers who have Beta software for version 17 of RSLogix 5000 software installed on their workstation. The version 17 Install will not offer to uninstall any previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software using Add/Remove Programs.
This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed. However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named “UpdateActionsInSchema.exe”, can be found in the “System\SecuritySchemaUpdate\” directory on the RSLogix 5000 DVD. Note that upon execution, the utility will provide further instructions.
In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.
Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Service Platform, which can be found on the RSLogix 5000 DVD. See the FactoryTalk Security installation instructions for further migration information.
In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups for the RSI Security Server are
They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.
When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed indicating that “Tag: Modify Properties” is not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)
The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9 will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix controllers, and actions, like “Tag Create”, for easier security administration.
Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time Left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (x72583)
Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types: MPL-A, MPL-B, 8720SM-xxxS, and TLY-A110T-Hxx. A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: “Axis ‘<tag_name>’ Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.” When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.
In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: “Warning: During conversion of Axis ‘<tag name>’ – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.” When this warning is encountered, the user should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, the user can reassociate the motor to the axis, but in this case all motor parameters will be Reset to default Motion database values, canceling many previously tuned and saved axis values. This issue does not exist with database conversion of an ACD format project file. The motors that are affected are: MPF-B310P, -B320P, -B330P, -B4430K; MPG-A004-031, -A110-031, -A11-0-091; MPL-A310F, -A430P, -B420P, -B4520P, -B4530F, -B4530K, -B580J, -B980L; TL-A120P-H, -A130P-H, -A220P-H, A230P-H.
A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.
The Controller Time Object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute “DateTime”, then this logic should be updated to use the new attribute “LocalDateTime”. You may also need to make other modifications to your application as a result of this change. (x72073, x72238)
A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions may not properly synchronize workstation time and controller time.
When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:
The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.
We recommended that the Microsoft Windows operating system’s “Language for non-Unicode programs (System Locale)” be configured to match the localized language of the RSLogix 5000 software edition. This is especially true for the Chinese, Japanese, and Korean RSLogix 5000 software editions. Not configuring the PC’s operating system’s System Locale to match the language of RSLogix 5000 software may result in the inability of RSLogix 5000 software to display certain fonts.
If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when RSLogix 5000 software is started. Clicking “Change” on this warning dialog box will navigate to the operating system dialog box from which the user can adjust the System Locale.
The System Locale can then be changed by selecting a new “Language for non-Unicode programs (System Locale)” on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of RSLogix 5000 software (9324-RLD300ZHE), you should select “Chinese (PRC)” for the System Locale.
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 software version 14, the directory structure for temporary RSLogix 5000 folders has been modified so that all AB_xxxx folders now reside within a single folder named “RSLogix 5000.Temp” located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000).
To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the “RSLogix5000.Temp” folder. (x51417, x85503)
The MOTION_INSTRUCTION data type changed in version 12 and later and the size increased from 12 bytes to 16 bytes. If you have created User-Defined data types that include members of type MOTION_INSTRUCTION you will lose tag initial values when you convert your project files from earlier versions. To work around this anomaly, export your project using the pre-version 12 version of RSLogix 5000 software and then import the project in version 12.02 or later. If you have written logic that relies on the old 12-byte size (for example by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that your logic is still correct.
The new MOTION_INSTRUCTION data type structure is:
FLAGS DINT
EN BOOL
DN BOOL
ER BOOL
PC BOOL
IP BOOL
AC BOOL
ACCEL BOOL
DECEL BOOL
ERR INT
STATUS SINT
STATE SINT
SEGMENT DINT
EXERR SINT
Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393)
The REAL data type now shows a 32-bit (4-byte) IEEE floating-point value with the following range:
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
- infinite
+NAN
-NAN
-indefinite
|
1.$
-1.$
1.#QNAN
-1.#QNAN
-1.#IND
|
|
Exponential
|
+infinite
- infinite
+NAN
-NAN
-indefinite
|
1.#INF000e+000
-1.#INF000e+000
1.#QNAN00e+000
-1.#QNAN00e+000
-1.#IND0000e+000
|
The software also stores and displays the IEEE subnormal range:
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 steps and actions were active at the time of the switch. To work around this anomaly, 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)
If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre (RSMACC) server to log messages, RSLogix 5000 software experiences intermittent freezes while it is waiting for the message requests to time out. This might cause RSLogix 5000 software to appear as though it has locked up, but if you wait about one minute it will begin responding again. To resolve this anomaly, either restore the connection to the FactoryTalk AssetCentre (RSMACC) server or disable the RSAudit message logging. Once a connection has been restored, cached messages will be logged to the server and RSLogix 5000 software will resume normal operation. (x36127)
During a file save operation RSLogix 5000 software attempts to compress the contents of a project so that the resulting file (ACD) requires less disk space. When opening a project this process is reversed and the contents of the ACD file are de-compressed. In some instances, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may become abnormally large but it is still usable, that is, you can continue to work with the file as you would normally. However, if you contact Rockwell Automation Services & Support and provide a copy of your project file, this could help the RSLogix 5000 software development team to locate the source of the compression failure.
If you have version 10.00 or later and an earlier version of RSLogix 5000 software installed on your computer, you will observe an activation error if you run the version 10.00 or later version first and then attempt to run the earlier version simultaneously. To work around this anomaly, always run the earlier version first and then run the version 10.00 or later version.
Be careful when performing operations with project files that depend on the default project directory. The Windows operating system controls and retains the default directory for the Open, Save As, and New Controller dialog boxes. Be sure to check that the folder selected is the one you wish to use when performing these operations to avoid mistakenly overwriting your project files. The Project Directory setting in the RSLogix 5000 Tools Options dialog box is normally used unless you navigate to a different directory within the Open, Save As, or New Controller dialog boxes. (x28475, x27886)
In releases earlier than version 10.00 if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner) you could download the project to a controller but may have encountered an error when uploading the project. This anomaly was caused by selecting multiple localized feedback wires in the outside feedback loop. In this release, this condition will be detected as a verification error in the routine. To correct this anomaly, select a feedback wire in the inner loop that is not also in the outer loop to be the localized feedback wire. (x28963, x27712)
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)
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)
The Servo Update Period for the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed from 200 microseconds to 250 microseconds. The servo update period is displayed on the Module Properties dialog box Associated Axes tab. This change in the Servo Update Period will have no affect on the behavior of existing motion control applications or on the overall performance of the motion control system. (x28647)
In version 12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in program mode but will produce a Major Fault if the controller is in run or remote run mode. In versions earlier than version 12.01, the motion group could produce a major fault while the controller was in program or remote program mode. For example, a store to nonvolatile memory interrupts the execution of the motion planner, which produces a fault. (x36957)
With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in RSLogix 5000 software without any user logic being written. However, a Kinetix Axis Module (AM) on the same power rail will require logic to be written if the user expects the motor on the AM to perform in the same manner as does the IAM. This logic should monitor the IAM’s phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes (x71448, x71717).
The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate new checks for reset of the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing changes observed were 20ms in version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)
Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA Sercos drives via ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating. ControlFLASH of the drives on the Ring must be done one drive node at a time.
Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the RA Sercos Drives to support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives must have revision 1.85 or higher, and the RA Ultra Sercos drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later. (x51766)
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)
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.
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 an anomaly with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680, x06823)
|
DLL Name
|
Compatible Versions
| |
|
Comcat.dll
|
4.71
|
5.0
|
|
Ole32.dll
|
4.0
|
4.71 or later
|
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 box 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 Logix5000 Controller. The process is simplified if non-DF1 communications is used to select CRC Error Detection in the Logix5000 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 Logix5000 controller. Open the Controller Properties dialog box and select the System Protocol tab. Under Error Detection enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000 information dialog box will display the error: “Failed to modify the DF1 Protocol configuration. Communications timed out.” This is expected and normal for this operation, click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC. Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software select Go Online to re-establish online communications. This DF1 driver will now communicate only with Logix5000 Controllers that are setup to use CRC Error Detection.
There is a log file generated that records abnormal events and which can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 software will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title "RSLogix 5000 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”. In order to more effectively address software error conditions, starting with version 14.00, the Fatal Error information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. The new file will be large. If it must be sent to Rockwell Automation Services & Support, it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). The RSLogix 5000 Fatal Error.Dmp file can also be deleted if not needed.
Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for Windows Vista or in C:\Documents and Settings\All Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000. For RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\<username>\Local Settings\Temp (for all operating systems).
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.
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).
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.
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 Logix5000 controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx software version 2.20 or later, or the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.
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. Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may also be deleted.
AB_xxxx folders reside within a single folder named “RSLogix 5000.Temp” located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000).
Caused by a corrupted activation key file (evrsi.sys). To correct this anomaly, contact Rockwell Automation Services & Support by telephone at +1 440-646-3434 or by email at RACleAskTheExpert@ra.rockwell.com.
.
This release has the following application notes.
Application Notes RSLinx Software v19
RSLogix 5000 Software 19.x
In RSLogix 5000 software version 18 and later, there is an External Access tag attribute, which defines how an external application can access a tag. This functionality is fully supported by RSLinx Classic software version 2.56 and RSLinx Enterprise software version 5.21. RSLogix 5000 software version 18 and later can be used with earlier versions of RSLinx Classic software to go online to a controller; however, earlier versions of RSLinx Classic or RSLinx Enterprise software should not be used as a data server with a controller running firmware revision 18 or later. Unexpected results will be observed when using an earlier version of RSLinx Classic or RSLinx Enterprise software as a data server with a controller running firmware revision 18 or later. Please see Rockwell Automation Knowledgebase Technote #67071 (http://www.rockwellautomation.com/knowledgebase/).
You may be prevented from configuring the Ethernet Port of a CompactLogix5532E controller (catalog number 1769-L32E) via Channel 0 by using RSLinx software. To workaround the anomaly, use RSLogix 5000 software to configure the port (if the 1769-L32E controller is at revision 13) or use the BootP utility (which is enabled for a 1769-L32E controller at revision 1).
Beginning with RSLinx Classic software version 2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher) version features. Only one professional activation is required for both products. The RSLogix 5000 Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher).
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.
If you are using RSLinx software version 2.40 or later, you can use the EtherNet/IP driver. This driver will automatically browse for all EtherNet/IP-capable devices on the local or configured remote subnet. See RSLinx online help for information on this driver. Note that 1756-ENET/A and 1756-ENET/B modules will not respond to the browse commands. You must use a different driver for these modules.
For DF1 point-to-point communications, choose ‘RS232 DF1 Devices’ from the list of available drivers in RSLinx software. Then choose ‘Logix5550 Serial Port’ for DeviceType. 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 anomalies accessing information from I/O modules.
RSLinx software maintains knowledge of the memory layout of a Logix5000 controller in order to optimize the data access performance when accessing the data in these controllers. However, changes made to an offline project that are then downloaded can result in RSLinx software attempting to access tag information that is no longer present. When this occurs, RSLinx software halts the communications to the controller. To recover, both RSLinx software and the software requesting tags from RSLinx software must be restarted. To avoid this anomaly, use caution when making offline changes to a project and then downloading to a Logix5000 controller. In particular, changing the size of an array if elements of the array are already on scan, renaming a structure or a member of a user-defined data type used by a tag that is on scan, or changing the data type of a tag on scan from a larger size to a smaller size (for example, changing a DINT to a SINT). Note that RSLinx Enterprise Series software is able to accommodate these changes without requiring a restart.
Some third-party data servers use data access methods for which Rockwell Automation does not publicly publish information. Starting with RSLogix 5000 software version 18, data access methods were changed to support the Data Access Control feature. As a result, some issues may be observed when using these data servers with controllers running revision 18 firmware. Please see Rockwell Automation Knowledgebase Technote #67071 (http://www.rockwellautomation.com/knowledgebase/).
Application Notes v19
RSLogix 5000 Software 19.x
The following information is provided to help you better understand the behavior of the RSLogix 5000 software in particular applications or under certain circumstances.
EvRSI activation will be replaced by the FactoryTalk Activation utility in a future release. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Services & Support for information on migrating your activations to FactoryTalk Activation.
With the introduction of the CIP Motion Load Observer enhancement in version 19 of RSLogix 5000 software, the out-of-box calculations for several CIP Axis attributes were impacted. In particular, the Position Loop Bandwidth attribute and the Position Error Tolerance attribute will be automatically adjusted when the Load Coupling is change from Rigid to Compliant and Use Load Ratio is enabled. When a change to the Load Coupling is applied, the out-of-box Position Loop Bandwidth will be reduced by 90% and the out-of-box Position Error Tolerance will be increased by 90%. This has the effect of loosening the out-of-box Position Gains so that the Motion Load Observer loop response can be tightened.
RSLogix 5000 software version 18 has replaced the concept of Coordinated System Time (CST) Mastership with the more comprehensive notion of Time Synchronization, also referred to as CIP Sync Time Coordination. The Date/Time page of the controller properties has been modified to reflect this change. For projects created with RSLogix 5000 software version 17 or earlier, if Coordinated System Time Master (CST) is enabled, then the converted project will have the Time Synchronization setting enabled. For more information about time synchronization using CIP Sync Time Coordination, refer to the Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003.
In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to create an unscheduled program, a user will need permission for the ‘Program: Create’ action. To create a program scheduled in a task, however, a user will now need permission for both the ‘Program: Create’ and the ‘Task: Modify Properties’ actions. To create a program scheduled in the Power-Up Handler or Controller Fault Handler, a user will now need permission for both the ‘Program: Create’ and the ‘'Controller: Modify Properties’ actions. (x77816, x77817)
With RSLogix 5000 software version 17 and earlier, when performing online editing operations in a Sequential Function Chart (SFC), switching the executing logic from the original programming to the test edits version (or vice versa) resets the chart to the initial step and resets all stored actions. Beginning with version 18.00 of RSLogix 5000 software, many SFC online edits no longer result in this reset. In general, only edits that alter the logic structure of the chart will require the SFC routine to be reset.
In cases when a reset is required, you can force the transition with the initial step to false, wait for the routine to execute to the initial step, and then perform the test/un-test operation followed by removal of the force. Also, you could leverage the SFC Reset (SFR) instruction to reposition the chart back to the desired step. (x36331, x43482)
McAfee virus software version 8.0 ships with a ‘Quick Registry Cleaner’ component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of RSLogix 5000 classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module. This anomaly will also prevent the creation and import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (x81691)
RSLogix 5000 software versions 16 and earlier do not support full project import when using an XML format file (.L5X). If you have version 17 or later of RSLogix 5000 software installed along with some earlier version of RSLogix 5000 software and you are currently running that earlier version of software, then the Open/Import Project dialog box will not allow a file with an L5X or XML file extension to be opened for import. To open an L5X format project you must first be sure that RSLogix 5000 software version 17 or later is running. You can do this either by creating a new version 17 project or by opening any existing version 17 project that was saved with an ACD or L5K file extension. Alternatively, you can select the L5X project file in Microsoft Windows Explorer by right-clicking the L5X file name and using the ‘Open with’ menu item to open the file with ‘Component of the RSLogix 5000 Application’. Note that when the RSLogix 5000 software is installed, files with an ACD file extension are configured by default to open this way when selected. You can configure files with L5X and L5K file extensions to also do this through Windows Explorer by manually associating these extensions with the executable file RSLogix5000Loader.exe, typically installed in the directory C:\Program Files\Rockwell Software\RSLogix 5000\Common or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common. (x87808)
After installing RSLogix 5000 software version 19, you may see the Tools>Online Books menu item. If this menu item is selected, Adobe Reader will report that ‘This file cannot be found.’ This error occurs when using RSLogix 5000 software version 19 or later if RSLogix 5000 software version 18 had also been installed on the same personal computer. The Online Books installed with version 18 software were accessed by using the Custom Tools Menu (Tools>Online Books). The Online Books installed with version 19 and later access the Online Books by using the Start Page Resource Center. With version 19 installed, the Custom Tools Menu item for version 18 Online Books remains on the Tools menu, but is no longer used. Once RSLogix 5000 software version 19 has been installed, the unused ‘Online Books’ Custom Tools Menu item can be manually removed by choosing Tools>Custom Tools. Then on the Custom Tools dialog box, select ‘Online Books’, click Delete, and then click OK to apply the change and close the dialog box. (x111895)
If your personal computer is not configured as part of a domain, you may receive the error message ‘Unknown URL’ when attempting to access Online Books or Vender Sample Projects from the Start Page. This is the result of security enhancements to the Internet Explorer browser. If RSLogix 5000 software was installed by using the default installation path, the Online Books can be accessed from links provided in the file C:\Program Files\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf, and the Vendor Sample Projects can be accessed from links provided in the file C:\RSLogix 5000\Projects\Samples\<language>\<version>\Third Party Products\Vendor Sample Projects.pdf. Access to Online Books and Vender Sample Projects can be allowed by adding ‘localhost’ to the allowed Local Intranet sites. (x89165)
The Windows Help (WinHlp32.exe) program is used to display RSLogix 5000 Online Help that is provided in 32-bit .hlp files. The Microsoft Corporation stopped including this 32-bit Help file viewer in Windows releases beginning with Windows Vista and Windows Server 2008 operating systems. RSLogix 5000 software version 18 and later display Online Help in HTML format and do not require this Windows Help program. However, some module profiles may continue to display Online Help by using 32-bit .hlp files. To properly display Online Help that is provided in 32-bit .hlp files on a Windows Vista or later operating system, you need to install the Windows Help program. This application is available for download from the Microsoft Download Center. For additional information on downloading and installing the Windows Help program, refer to the Microsoft Knowledgebase article ‘I cannot open Help files that require the Windows Help (WinHlp32.exe) program’, located at http://support.microsoft.com/?kbid=917607. ( x109600)
If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software or later, Start Pages will fail to load and the message ‘Server Startup Failure physicalPath=…’ will be displayed. In order to restore Start Page functionality it is necessary to re-install the version 17.00 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of RSLogix 5000 software and later. (x76424)
The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista or later operating systems. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.
A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819, x85559)
The hardwired digital inputs on the Kinetix 6000 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user’s application must be written to make proper use of these digital inputs within the context of the associated motion instructions.
Creation of an RSLogix 5000 event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same name. Since Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.
If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you will need an updated motion database to work with RSLogix 5000 software version 18. The following table lists the motion database revisions that are used with these RSLogix 5000 software versions.
|
RSLogix 5000 Software Version
|
Motion Database Revision
|
|
19.01 / 19.00
|
7.5.0
[ Motion.mdb format
]
|
|
18.02 / 18.01 / 18.00
|
6.9.0
[ Motion.mdb format
]
|
|
17.01 / 17.00
|
5.3.0
[ *Motion.md format ]
|
|
16.04 / 16.03 / 16.00
|
4.2.0
[ *Motion.md format ]
|
|
15.03 / 15.02 / 15.01 / 15.00
|
3.24.0 [ *Motion.md
format ]
|
|
14.01 / 14.00
|
3.12.0 [ *Motion.md
format ]
|
|
13.04 / 13.03 / 13.02 / 13.01 / 13.00
|
3.12.0 [ *Motion.md
format ]
|
|
12.06 / 12.05 / 12.04 / 12.03 / 12.02 /
12.01 / 12.00
|
3.3.0
[ *Motion.md format ]
|
* Before a Custom Motor can be used in RSLogix 5000 software version 18 or later, any Custom Motor currently in a motion database file at revision 5 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.
To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.
When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from RSLogix 5000 software may result in a dialog box being displayed with the message ‘Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?’ This issue is documented in the Adobe Knowledgebase article http://kb.adobe.com/selfservice/viewContent.do?externalId=321561&sliceId=2, which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation. A temporary workaround for printing RSLogix 5000 reports is to click No in the dialog box, in the RSLogix 5000 Print dialog box change the printer name to some other printer, change the printer name back to Adobe PDF, and then click OK to print the document. (x88019)
The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there may be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There may also be minor differences in Trapezoidal velocity profiles. Please refer to the Motion Planner, Version 16.03 Application Solution, publication RA-AP031, for additional details.
The Kinematics Transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000 software version 16.03) should only be used with version 16.03 or greater of RSLogix 5000 software. If RSLogix 5000 software version 16.00 is used to upload a project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported geometries will be converted to the default Coordinate System Type of ‘Cartesian’. The message ‘attribute list error’ will be displayed during the download attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision earlier than revision 16.20. (x75769)
Unscheduled Connections are not supported for the current release of the 1757-FFLDC module. Ensure that the ‘Use Scheduled Connection over ControlNet’ checkbox is checked on the Connection tab of all Logix Blocks. (This checkbox is checked by default when a Logix Block is created.)
This application note affects customers who have Beta software for version 17 of RSLogix 5000 software installed on their workstation. The version 17 Install will not offer to uninstall any previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software using Add/Remove Programs.
This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed. However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named ‘UpdateActionsInSchema.exe’, can be found in the ‘System\SecuritySchemaUpdate\’ directory on the RSLogix 5000 DVD. Note that upon execution, the utility will provide further instructions.
In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.
Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Service Platform, which can be found on the RSLogix 5000 DVD. See the FactoryTalk Security installation instructions for further migration information.
In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups for the RSI Security Server are
They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.
When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed indicating that ‘Tag: Modify Properties’ is not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)
The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9 will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix controllers, and actions, like ‘Tag Create’, for easier security administration.
Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time Left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (x72583)
Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types: MPL-A, MPL-B, 8720SM-xxxS, and TLY-A110T-Hxx. A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: ‘Axis ‘<tag_name>’ Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.’ When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.
In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: ‘Warning: During conversion of Axis ‘<tag name>’ – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.’ When this warning is encountered, the user should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, the user can reassociate the motor to the axis, but in this case all motor parameters will be reset to default Motion database values, canceling many previously tuned and saved axis values. This issue does not exist with database conversion of an ACD format project file. The motors that are affected are: MPF-B310P, -B320P, -B330P, -B4430K; MPG-A004-031, -A110-031, -A11-0-091; MPL-A310F, -A430P, -B420P, -B4520P, -B4530F, -B4530K, -B580J, -B980L; TL-A120P-H, -A130P-H, -A220P-H, A230P-H.
A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.
The Controller Time Object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute ‘DateTime’, then this logic should be updated to use the new attribute ‘LocalDateTime’. You may also need to make other modifications to your application as a result of this change. (x72073, x72238)
A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions may not properly synchronize workstation time and controller time.
When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:
The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.
We recommended that the Microsoft Windows operating system’s ‘Language for non-Unicode programs (System Locale)’ be configured to match the localized language of the RSLogix 5000 software edition. This is especially true for the Chinese, Japanese, and Korean RSLogix 5000 software editions. Not configuring the PC’s operating system’s System Locale to match the language of RSLogix 5000 software may result in the inability of RSLogix 5000 software to display certain fonts.
If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when RSLogix 5000 software is started. Clicking ‘Change’ on this warning dialog box will navigate to the operating system dialog box from which the user can adjust the System Locale.
The System Locale can then be changed by selecting a new ‘Language for non-Unicode programs (System Locale)’ on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of RSLogix 5000 software (9324-RLD300ZHE), you should select ‘Chinese (PRC)’ for the System Locale.
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 software version 14, the directory structure for temporary RSLogix 5000 folders has been modified so that all AB_xxxx folders now reside within a single folder named ‘RSLogix 5000.Temp’ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000 operating systems).
To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the ‘RSLogix5000.Temp’ folder. (x51417, x85503)
The MOTION_INSTRUCTION data type changed in version 12 and later and the size increased from 12 bytes to 16 bytes. If you have created User-Defined data types that include members of type MOTION_INSTRUCTION you will lose tag initial values when you convert your project files from earlier versions. To work around this anomaly, export your project using the pre-version 12 version of RSLogix 5000 software and then import the project in version 12.02 or later. If you have written logic that relies on the old 12-byte size (for example by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that your logic is still correct.
The new MOTION_INSTRUCTION data type structure is:
FLAGS DINT
EN BOOL
DN BOOL
ER BOOL
PC BOOL
IP BOOL
AC BOOL
ACCEL BOOL
DECEL BOOL
ERR INT
STATUS SINT
STATE SINT
SEGMENT DINT
EXERR SINT
Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393)
The REAL data type now shows a 32-bit (4-byte) IEEE floating-point value with the following range:
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
- infinite
+NAN
-NAN
-indefinite
|
1.$
-1.$
1.#QNAN
-1.#QNAN
-1.#IND
|
|
Exponential
|
+infinite
- infinite
+NAN
-NAN
-indefinite
|
1.#INF000e+000
-1.#INF000e+000
1.#QNAN00e+000
-1.#QNAN00e+000
-1.#IND0000e+000
|
The software also stores and displays the IEEE subnormal range:
If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre (RSMACC) server to log messages, RSLogix 5000 software experiences intermittent freezes while it is waiting for the message requests to time out. This might cause RSLogix 5000 software to appear as though it has locked up, but if you wait about one minute it will begin responding again. To resolve this anomaly, either restore the connection to the FactoryTalk AssetCentre (RSMACC) server or disable the RSAudit message logging. Once a connection has been restored, cached messages will be logged to the server and RSLogix 5000 software will resume normal operation. (x36127)
During a file save operation RSLogix 5000 software attempts to compress the contents of a project so that the resulting file (ACD) requires less disk space. When opening a project this process is reversed and the contents of the ACD file are de-compressed. In some instances, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may become abnormally large but it is still usable, that is, you can continue to work with the file as you would normally. However, if you contact Rockwell Automation Services & Support and provide a copy of your project file, this could help the RSLogix 5000 software development team to locate the source of the compression failure.
If you have version 10.00 or later and an earlier version of RSLogix 5000 software installed on your computer, you will observe an activation error if you run the version 10.00 or later version first and then attempt to run the earlier version simultaneously. To work around this anomaly, always run the earlier version first and then run the version 10.00 or later version.
Be careful when performing operations with project files that depend on the default project directory. The Windows operating system controls and retains the default directory for the Open, Save As, and New Controller dialog boxes. Be sure to check that the folder selected is the one you wish to use when performing these operations to avoid mistakenly overwriting your project files. The Project Directory setting in the RSLogix 5000 Tools Options dialog box is normally used unless you navigate to a different directory within the Open, Save As, or New Controller dialog boxes. (x28475, x27886)
In releases earlier than version 10.00 if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner) you could download the project to a controller but may have encountered an error when uploading the project. This anomaly was caused by selecting multiple localized feedback wires in the outside feedback loop. In this release, this condition will be detected as a verification error in the routine. To correct this anomaly, select a feedback wire in the inner loop that is not also in the outer loop to be the localized feedback wire. (x28963, x27712)
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)
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)
The Servo Update Period for the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed from 200 microseconds to 250 microseconds. The servo update period is displayed on the Module Properties dialog box Associated Axes tab. This change in the Servo Update Period will have no affect on the behavior of existing motion control applications or on the overall performance of the motion control system. (x28647)
In version 12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in program mode but will produce a Major Fault if the controller is in run or remote run mode. In versions earlier than version 12.01, the motion group could produce a major fault while the controller was in program or remote program mode. For example, a store to nonvolatile memory interrupts the execution of the motion planner, which produces a fault. (x36957)
With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in RSLogix 5000 software without any user logic being written. However, a Kinetix Axis Module (AM) on the same power rail will require logic to be written if the user expects the motor on the AM to perform in the same manner as does the IAM. This logic should monitor the IAM’s phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes (x71448, x71717).
The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate new checks for reset of the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing changes observed were 20ms in version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)
Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA Sercos drives via ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating. ControlFLASH of the drives on the Ring must be done one drive node at a time.
Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the RA Sercos Drives to support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives must have revision 1.85 or higher, and the RA Ultra Sercos drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later. (x51766)
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)
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.
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 an anomaly with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680, x06823)
|
DLL Name
|
Compatible Versions
| |
|
Comcat.dll
|
4.71
|
5.0
|
|
Ole32.dll
|
4.0
|
4.71 or later
|
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 box 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 Logix5000 controller. The process is simplified if non-DF1 communications is used to select CRC Error Detection in the Logix5000 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 Logix5000 controller. Open the Controller Properties dialog box and select the System Protocol tab. Under Error Detection enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000 information dialog box will display the error: ‘Failed to modify the DF1 Protocol configuration. Communications timed out.’ This is expected and normal for this operation; click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC. Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software select Go Online to re-establish online communications. This DF1 driver will now communicate only with Logix5000 controllers that are set up to use CRC Error Detection.
There is a log file generated that records abnormal events and which can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 software will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title ‘RSLogix 5000 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’. In order to more effectively address software error conditions, starting with version 14.00, the Fatal Error information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. The new file will be large. If it must be sent to Rockwell Automation Services & Support, it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). The RSLogix 5000 Fatal Error.Dmp file can also be deleted if not needed.
Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or in C:\Documents and Settings\All Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000 operating systems. For RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\<username>\Local Settings\Temp (for all operating systems).
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.
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).
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.
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 Logix5000 controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx software version 2.20 or later, or the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.
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. Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may also be deleted.
AB_xxxx folders reside within a single folder named ‘RSLogix 5000.Temp’ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000 operating systems).
Caused by a corrupted activation key file (evrsi.sys). To correct this anomaly, contact Rockwell Automation Services & Support by telephone at +1 440-646-3434 or by email at RACleAskTheExpert@ra.rockwell.com.
.
This release has the following application notes.
Application Notes v20
RSLogix 5000 Software 20.x
Product Resiliency Improvement
This release includes enhancements intended to improve product resiliency to potentially disruptive activities. These enhancements have been verified to not affect product safety, performance, expected life, configuration, or operation of the product. Rockwell Automation advises customers to follow good Industrial Control System (ICS) security practices that include regular product updates. To ensure authenticity, obtain product updates and new releases directly from Rockwell Automation.
Product resiliency includes, but is not limited to, security topics related to tamper prevention and detection, intellectual property management and source protection, and user authentication and authorization.
Offline interactions between minor versions
Starting with version 20.03, ACD projects converted to version 20.03 cannot be opened in prior versions.
Online interactions between controller and application
Starting with version 20.03:
Support of minor versions
The RSLogix 5000 software only supports the installation of a single minor release of the software on a computer. Therefore, version 20.03 of the software CANNOT run on the same computer as previous minor releases of v20.
In order to support a system that runs v20.03 and earlier versions of v20 releases, leverage the use of separate computers or use virtualization.
Indirect Addressing within Add-On Instruction Logic Using RSLogix 5000 Software Version 20.01
If your project uses indirect addressing in an Add-On Instruction, you need to be aware of two compatibility items when using RSLogix 5000 software version 20.01 and Logix5000 controller firmware revision 20.012.
First, you should consider RSLogix 5000 software version 20.01 and Logix5000 controller firmware revision 20.012 to be lock stepped. This means that you should not use the following:
You should also be aware that the signature for the safety Add-On Instructions will change when the project is downloaded to a controller. On download, you will receive a warning indicating that the Add-On Instructions needs to be revalidated.
For further information, please see Rockwell Automation Knowledgebase Tech Note #481124 (http://www.rockwellautomation.com/knowledgebase/).
EvRSI Replaced by FactoryTalk Activation Manager
Beginning with RSLogix 5000 software version 20, EvRSI activation has been replaced by the FactoryTalk Activation Manager utility. EvRSI activation will not be able to activate RSLogix 5000 software version 20. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Services & Support for information on migrating your activations to FactoryTalk Activation.
Unable to Connect to 1756-L7x Controller Using USB Port
For the 1756-L7x controllers, if you meet both of the following conditions, you will not be able to update or connect through RSLogix 5000 software to your 1756-L7x controller using the USB port:
If you meet both conditions, you will have to update the controller or connect through RSLogix 5000 software through a different means, such as Ethernet.
1769-L2y Controllers Cannot Be Properly Configured Using RSLogix 5000 Software Version 20.00
For 1769-L2y controller types, which were newly released in RSLogix 5000 software version 20, the Embedded Counters module cannot be properly configured for Pulse External Direction. This anomaly was corrected in version 20.01. 1769-L2y controllers can be properly configured by using RSLogix 5000 software version 20.01. However, 1769-L2y projects created by using RSLogix 5000 software version 20.00 will continue to be configured incorrectly. To correct the configuration, the controller must be recreated in RSLogix 5000 software. You may find it convenient to use the File > Import Component feature of RSLogix 5000 software to port your logic from the version 20.00 project to the new version 20.01 project. This affects the following controller types: 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, and 1769-L27ERM-QBFC1B.
Out-of-Box CIP Axis Position Loop Gain Values Adjusted with Load Observer
With the introduction of the CIP Motion Load Observer enhancement in version 19 of RSLogix 5000 software, the out-of-box calculations for several CIP Axis attributes were impacted. In particular, the Position Loop Bandwidth attribute and the Position Error Tolerance attribute will be automatically adjusted when the Load Coupling is change from Rigid to Compliant and Use Load Ratio is enabled. When a change to the Load Coupling is applied, the out-of-box Position Loop Bandwidth will be reduced by 90% and the out-of-box Position Error Tolerance will be increased by 90%. This has the effect of loosening the out-of-box Position Gains so that the Motion Load Observer loop response can be tightened.
Time Synchronization Replaces CST Time Mastership with Version 18.00 or Later
RSLogix 5000 software version 18 has replaced the concept of Coordinated System Time (CST) Mastership with the more comprehensive notion of Time Synchronization, also referred to as CIP Sync Time Coordination. The Date/Time page of the controller properties has been modified to reflect this change. For projects created with RSLogix 5000 software version 17 or earlier, if Coordinated System Time Master (CST) is enabled, then the converted project will have the Time Synchronization setting enabled. For more information about time synchronization using CIP Sync Time Coordination, refer to the Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003.
“Attribute Value not Settable” Reported Using AutoFLASH from Logix Firmware Revision 20 to an Earlier Revision
When attempting to download a project by using RSLogix 5000 software version 19 or earlier, if the controller firmware is at revision 20 and the controller is in Remote Run mode, then the version 19 software will not be able to change the controller mode in order to AutoFLASH the controller with revision 19 firmware. In this case, the controller mode must be changed either by using the keyswitch or by using RSLogix 5000 software version 20. (x123924)
CIP Generic Writes to Controller Objects that Originate from Another Controller May Fail
In RSLogix 5000 software version 20 there are enhanced security restrictions to controller CIP objects. Because of this some CIP Generic messages used to write directly to controller object attributes may not function. Any CIP generic object write that originates external to the controller may fail in RSLogix 5000 software version 20. CIP Generic writes that are executed in the controller’s own user program will operate normally.
Security Permissions Changed for Program Creation
In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to create an unscheduled program, a user will need permission for the ‘Program: Create’ action. To create a program scheduled in a task, however, a user will now need permission for both the ‘Program: Create’ and the ‘Task: Modify Properties’ actions. To create a program scheduled in the Power-Up Handler or Controller Fault Handler, a user will now need permission for both the ‘Program: Create’ and the ‘'Controller: Modify Properties’ actions. (x77816, x77817)
Testing SFC Online Edits No Longer Always Requires the Chart to Reset with Version 18.00 or Later
With RSLogix 5000 software version 17 and earlier, when performing online editing operations in a Sequential Function Chart (SFC), switching the executing logic from the original programming to the test edits version (or vice versa) resets the chart to the initial step and resets all stored actions. Beginning with version 18.00 of RSLogix 5000 software, many SFC online edits no longer result in this reset. In general, only edits that alter the logic structure of the chart will require the SFC routine to be reset.
In cases when a reset is required, you can force the transition with the initial step to false, wait for the routine to execute to the initial step, and then perform the test/un-test operation followed by removal of the force. Also, you could leverage the SFC Reset (SFR) instruction to reposition the chart back to the desired step. (x36331, x43482)
Can’t Create, View, or Edit Modules Based on Classic Profile After McAfee QuickClean
McAfee virus software version 8.0 ships with a ‘Quick Registry Cleaner’ component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of RSLogix 5000 classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module. This anomaly will also prevent the creation and import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (x81691)
L5X File List Not Filtered on Windows 7 Operating System
When performing a Partial Import online, the list of files displayed on the Import dialog box is filtered to show only files of the selected component type (for example, Program, Routine, Data Type, Equipment Phase). This filtering is not supported by the Windows 7 operating system. The Import dialog box will therefore show all L5X format files when running RSLogix 5000 software on a Windows 7 operating system. The icon and ToolTip for the component file will identify the file type. (x105789, x112515, x113267)
Unable to Open Full Project XML format file (.L5X) from Open/Import Project Dialog Box
RSLogix 5000 software versions 16 and earlier do not support full project import when using an XML format file (.L5X). If you have version 17 or later of RSLogix 5000 software installed along with some earlier version of RSLogix 5000 software and you are currently running that earlier version of software, then the Open/Import Project dialog box will not allow a file with an L5X or XML file extension to be opened for import. To open an L5X format project you must first be sure that RSLogix 5000 software version 17 or later is running. You can do this either by creating a new version 17 project or by opening any existing version 17 project that was saved with an ACD or L5K file extension. Alternatively, you can select the L5X project file in Microsoft Windows Explorer by right-clicking the L5X file name and using the ‘Open with’ menu item to open the file with ‘Component of the RSLogix 5000 Application’. Note that when the RSLogix 5000 software is installed, files with an ACD file extension are configured by default to open this way when selected. You can configure files with L5X and L5K file extensions to also do this through Windows Explorer by manually associating these extensions with the executable file RSLogix5000Loader.exe, typically installed in the directory C:\Program Files\Rockwell Software\RSLogix 5000\Common or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common. (x87808)
Adobe Reader Error Selecting ‘Online Books’ from the Tools Menu
After installing RSLogix 5000 software version 19, you may see the Tools>Online Books menu item. If this menu item is selected, Adobe Reader will report that ‘This file cannot be found.’ This error occurs when using RSLogix 5000 software version 19 or later if RSLogix 5000 software version 18 had also been installed on the same personal computer. The Online Books installed with version 18 software were accessed by using the Custom Tools Menu (Tools>Online Books). The Online Books installed with version 19 and later access the Online Books by using the Start Page Resource Center. With version 19 installed, the Custom Tools Menu item for version 18 Online Books remains on the Tools menu, but is no longer used. Once RSLogix 5000 software version 19 has been installed, the unused ‘Online Books’ Custom Tools Menu item can be manually removed by choosing Tools>Custom Tools. Then on the Custom Tools dialog box, select ‘Online Books’, click Delete, and then click OK to apply the change and close the dialog box. (x111895)
Unknown URL Attempting to Access Online Books or Vender Sample Projects from Start Page
If your personal computer is not configured as part of a domain, you may receive the error message ‘Unknown URL’ when attempting to access Online Books or Vender Sample Projects from the Start Page. This is the result of security enhancements to the Internet Explorer browser. If RSLogix 5000 software was installed by using the default installation path, the Online Books can be accessed from links provided in the file C:\Program Files\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf, and the Vendor Sample Projects can be accessed from links provided in the file C:\RSLogix 5000\Projects\Samples\<language>\<version>\Third Party Products\Vendor Sample Projects.pdf. Access to Online Books and Vender Sample Projects can be allowed by adding ‘localhost’ to the allowed Local Intranet sites. (x89165)
Online Help from 32-bit .hlp Files is Not Displayed
The Windows Help (WinHlp32.exe) program is used to display RSLogix 5000 Online Help that is provided in 32-bit .hlp files. The Microsoft Corporation stopped including this 32-bit Help file viewer in Windows releases beginning with Windows Vista and Windows Server 2008 operating systems. RSLogix 5000 software version 18 and later display Online Help in HTML format and do not require this Windows Help program. However, some module profiles may continue to display Online Help by using 32-bit .hlp files. To properly display Online Help that is provided in 32-bit .hlp files on a Windows Vista or later operating system, you need to install the Windows Help program. This application is available for download from the Microsoft Download Center. For additional information on downloading and installing the Windows Help program, refer to the Microsoft Knowledgebase article ‘I cannot open Help files that require the Windows Help (WinHlp32.exe) program’, located at http://support.microsoft.com/?kbid=917607. (x109600)
Start Pages Won’t Work if Version 16.00 Is Installed After Other Versions
If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software or later, Start Pages will fail to load and the message ‘Server Startup Failure physicalPath=…’ will be displayed. In order to restore Start Page functionality it is necessary to re-install the version 17.00 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of RSLogix 5000 software and later. (x76424)
Function Block Diagram (FBD) ActiveX Faceplates are Not Compatible with Windows Vista or Later
The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista or later operating systems. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.
Overflow Checking Improved for Immediate Operand Values
In RSLogix 5000 software version 20, overflow checking for immediate operand values has been extended to all radix formats. Earlier versions of RSLogix 5000 software checked Octal values (i.e., 8#nnn) for overflow into a 32-bit integer. Starting with RSLogix 5000 software version 20, immediate operand values of any integer-type radix (Hexadecimal, Decimal, Octal, or Binary) are checked for overflow into a 32-bit integer. The overflow conditions are indicated as errors during the verification process. (x116816)
First Use of Drive Profile by User Who Did Not Install the Add-On Profiles Will Require Media Access
When a drive profile is first accessed, any user other than the user who installed the Drives Add-On Profiles version 4.02 or earlier will need access to the install media. When accessing the drive profile either by importing a project or by creating a drive in the I/O configuration tree, the user will be prompted with the following: “enter an alternate path to a folder containing the installation package ‘RADrives_PF7.msi’”. The user must then provide the path on the installation media to ...\ENU\MP\RADrives\RADrives_PF7.msi. These Add-On Profiles may have been installed either separately or as part of the installation of RSLogix 5000 software version 20.01. (x128249)
Manual Tune Fields Are Active When Servo is Disabled
In RSLogix 5000 software version 20, the Manual Tune parameters are enabled and editable when online for either the On or Off setting for the Servo parameter of a CIP_AXIS_DRIVE axis type. (x122492)
Motion Instruction Error Generated for Stop_All or MGS Active and Pending Motion Instruction
A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819, x85559)
Kinetix 6000 S0 and S1 Safety Drive with RSLogix 5000 Digital Inputs Configuration
The hardwired digital inputs on the Kinetix 6000 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user’s application must be written to make proper use of these digital inputs within the context of the associated motion instructions.
RSLogix 5000 Event Task Names can Conflict with Microsoft Windows Event Names
Creation of an RSLogix 5000 event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same name. Since Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.
Versions 18 and Later Require Updates to Custom Motion Database
If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you will need an updated motion database to work with RSLogix 5000 software versions 18 or later. The following table lists the motion database revisions that are used with these RSLogix 5000 software versions.
|
RSLogix 5000 Software Version
|
Motion Database Revision
|
|
20.03/20.01
|
8.12.0
[ Motion.mdb format ]
|
|
20.00
|
8.9.0
[ Motion.mdb format ]
|
|
19.01 / 19.00
|
7.5.0
[ Motion.mdb format ]
|
|
18.02 / 18.01 / 18.00
|
6.9.0
[ Motion.mdb format ]
|
|
17.01 / 17.00
|
5.3.0
[ *Motion.md format ]
|
|
16.04 / 16.03 / 16.00
|
4.2.0
[ *Motion.md format ]
|
|
15.03 / 15.02 / 15.01 / 15.00
|
3.24.0
[ *Motion.md format ]
|
|
14.01 / 14.00
|
3.12.0
[ *Motion.md format ]
|
|
13.04 / 13.03 / 13.02 / 13.01 / 13.00
|
3.12.0
[ *Motion.md format ]
|
|
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 12.01 / 12.00
|
3.3.0
[ *Motion.md format ]
|
* Before a Custom Motor can be used in RSLogix 5000 software version 18 or later, any Custom Motor currently in a motion database file at revision 5 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.
To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.
Error May Be Displayed When Attempting to Print to Adobe PDF
When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from RSLogix 5000 software may result in a dialog box being displayed with the message ‘Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?’ This issue is documented in the Adobe Knowledgebase article http://kb.adobe.com/selfservice/viewContent.do?externalId=321561&sliceId=2, which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation. A temporary workaround for printing RSLogix 5000 reports is to click No in the dialog box, in the RSLogix 5000 Print dialog box change the printer name to some other printer, change the printer name back to Adobe PDF, and then click OK to print the document. (x88019)
GSV of PositionFeedback1 Attribute Reports Verification Error
In RSLogix 5000 software version 20, the PositionFeedback1 is now an integer value. When configuring a GSV of the PositionFeedback1 attribute, a destination tag value of type DINT is now required. (x123873)
Superimposed Motion Shifts Path
Beginning with RSLogix 5000 software version 20, the superimposed motion behavior has changed. In Absolute mode, when Superimposed mode is programmed, the path is shifted by the superimposed motion, except for moves in the following conditions: (1) Sequence of moves using any termination type other than TT0 or TT1, (2) a merge, or (3) when the queue becomes empty. This allows for the capability of any path that is drawn on a table moving in either the X or Y direction as a result of superimposed motion to look exactly the same as if it were drawn on a stationary table. In RSLogix 5000 software version 19, the path was not shifted when Superimposed mode is programmed and this was not achievable. (x122482)
Enhancements to Motion Planner may Affect Motion Profiles
The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there may be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There may also be minor differences in Trapezoidal velocity profiles. Please refer to the Motion Planner, Version 16.03 Application Solution, publication RA-AP031, for additional details.
Kinematics Transformations, Additional Native Geometry Support Compatibility Issues
The Kinematics Transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000 software version 16.03) should only be used with version 16.03 or greater of RSLogix 5000 software. If RSLogix 5000 software version 16.00 is used to upload a project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported geometries will be converted to the default Coordinate System Type of ‘Cartesian’. The message ‘attribute list error’ will be displayed during the download attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision earlier than revision 16.20. (x75769)
Version 17 Installation Does Not Automatically Uninstall Version 17 Beta Versions
This application note affects customers who have Beta software for version 17 of RSLogix 5000 software installed on their workstation. The version 17 Install will not offer to uninstall any previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software using Add/Remove Programs.
Using Security with Version 16 RSLogix 5000 Software and CPR 7 FactoryTalk Network Directory Server
This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed. However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named ‘UpdateActionsInSchema.exe’, can be found in the ‘System\SecuritySchemaUpdate\’ directory on the RSLogix 5000 DVD. Note that upon execution, the utility will provide further instructions.
SFCRESTART Attribute Removed for GSV/SSV
In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.
Migrating to FactoryTalk Security (from RSI Security Server)
Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Services Platform, which can be found on the RSLogix 5000 DVD. See the FactoryTalk Security installation instructions for further migration information.
Removal of Built-in Action Groups for Security
In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups for the RSI Security Server are:
They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.
Tag Modify Properties is Required to Update Configuration Dialog Boxes Having a Tag Tab
When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed indicating that ‘Tag: Modify Properties’ is not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)
FactoryTalk Security – Resource and Action Groups Coming With FactoryTalk CPR 9 Release
The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9 will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix controllers, and actions, like ‘Tag Create’, for easier security administration.
Ramp/Soak (RMPS) Results Appear to be in Error
Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time Left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (x72583)
Opening Pre-Version 17 Project with Axis may Generate Warning for Axis Performance Verification
Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types: MPL-A, MPL-B, 8720SM-xxxS, and TLY-A110T-Hxx. A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: ‘Axis ‘<tag_name>’ Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.’ When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.
File Import of Axis with MPx Motors may Generate Warning for Axis Performance Verification
In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: ‘Warning: During conversion of Axis ‘<tag name>’ – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.’ When this warning is encountered, the user should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, the user can reassociate the motor to the axis, but in this case all motor parameters will be reset to default Motion database values, canceling many previously tuned and saved axis values. This issue does not exist with database conversion of an ACD format project file. The motors that are affected are: MPF-B310P, -B320P, -B330P, -B4430K; MPG-A004-031, -A110-031, -A11-0-091; MPL-A310F, -A430P, -B420P, -B4520P, -B4530F, -B4530K, -B580J, -B980L; TL-A120P-H, -A130P-H, -A220P-H, A230P-H.
LINT Time Stamp Values Not Displayed with FactoryTalk View SE Utility
A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.
Controller Time Object Changed in Version 16 of RSLogix 5000 Software
The Controller Time Object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute ‘DateTime’, then this logic should be updated to use the new attribute ‘LocalDateTime’. You may also need to make other modifications to your application as a result of this change. (x72073, x72238)
Use New Clock Update Tool with Logix5000 Version 16 and Later Software
A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions may not properly synchronize workstation time and controller time.
Firmware Update Required for 1734 and 1738 Ethernet Point Adapters
When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:
The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.
Display of Non-Unicode Character Fonts in RSLogix 5000 Software
We recommended that the Microsoft Windows operating system’s ‘Language for non-Unicode programs (System Locale)’ be configured to match the localized language of the RSLogix 5000 software edition. This is especially true for the Chinese, Japanese, and Korean RSLogix 5000 software editions. Not configuring the PC’s operating system’s System Locale to match the language of RSLogix 5000 software may result in the inability of RSLogix 5000 software to display certain fonts.
If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when RSLogix 5000 software is started. Clicking ‘Change’ on this warning dialog box will navigate to the operating system dialog box from which the user can adjust the System Locale.
The System Locale can then be changed by selecting a new ‘Language for non-Unicode programs (System Locale)’ on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of RSLogix 5000 software (9324-RLD300ZHE), you should select ‘Chinese (PRC)’ for the System Locale.
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 software version 14, the directory structure for temporary RSLogix 5000 folders has been modified so that all AB_xxxx folders now reside within a single folder named ‘RSLogix 5000.Temp’ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000 operating systems).
To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the ‘RSLogix5000.Temp’ folder. (x51417, x85503)
MOTION_INSTRUCTION Data Type Change
The MOTION_INSTRUCTION data type changed in version 12 and later and the size increased from 12 bytes to 16 bytes. If you have created User-Defined data types that include members of type MOTION_INSTRUCTION you will lose tag initial values when you convert your project files from earlier versions. To work around this anomaly, export your project using the pre-version 12 version of RSLogix 5000 software and then import the project in version 12.02 or later. If you have written logic that relies on the old 12-byte size (for example by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that your logic is still correct.
The new MOTION_INSTRUCTION data type structure is:
FLAGS DINT
EN BOOL
DN BOOL
ER BOOL
PC BOOL
IP BOOL
AC BOOL
ACCEL BOOL
DECEL BOOL
ERR INT
STATUS SINT
STATE SINT
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:
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
- infinite
+NAN
-NAN
-indefinite
|
1.$
-1.$
1.#QNAN
-1.#QNAN
-1.#IND
|
|
Exponential
|
+infinite
- infinite
+NAN
-NAN
-indefinite
|
1.#INF000e+000
-1.#INF000e+000
1.#QNAN00e+000
-1.#QNAN00e+000
-1.#IND0000e+000
|
The software also stores and displays the IEEE subnormal range:
RSLogix 5000 Software Appears to Lock Up When FactoryTalk AssetCentre (RSMACC) Connection Broken
If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre (RSMACC) server to log messages, RSLogix 5000 software experiences intermittent freezes while it is waiting for the message requests to time out. This might cause RSLogix 5000 software to appear as though it has locked up, but if you wait about one minute it will begin responding again. To resolve this anomaly, either restore the connection to the FactoryTalk AssetCentre (RSMACC) server or disable the RSAudit message logging. Once a connection has been restored, cached messages will be logged to the server and RSLogix 5000 software will resume normal operation. (x36127)
RSLogix 5000 Software Save May Result In Large Project ACD File
During a file save operation RSLogix 5000 software attempts to compress the contents of a project so that the resulting file (ACD) requires less disk space. When opening a project this process is reversed and the contents of the ACD file are de-compressed. In some instances, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may become abnormally large but it is still usable, that is, you can continue to work with the file as you would normally. However, if you contact Rockwell Automation Services & Support and provide a copy of your project file, this could help the RSLogix 5000 software development team to locate the source of the compression failure.
Activation Error Running Multiple Versions Simultaneously
If you have version 10.00 or later and an earlier version of RSLogix 5000 software installed on your computer, you will observe an activation error if you run the version 10.00 or later version first and then attempt to run the earlier version simultaneously. To work around this anomaly, always run the earlier version first and then run the version 10.00 or later version.
Default Project Directory
Be careful when performing operations with project files that depend on the default project directory. The Windows operating system controls and retains the default directory for the Open, Save As, and New Controller dialog boxes. Be sure to check that the folder selected is the one you wish to use when performing these operations to avoid mistakenly overwriting your project files. The Project Directory setting in the RSLogix 5000 Tools Options dialog box is normally used unless you navigate to a different directory within the Open, Save As, or New Controller dialog boxes. (x28475, x27886)
FBD Routine Localized Feedback Wiring Errors
In releases earlier than version 10.00 if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner) you could download the project to a controller but may have encountered an error when uploading the project. This anomaly was caused by selecting multiple localized feedback wires in the outside feedback loop. In this release, this condition will be detected as a verification error in the routine. To correct this anomaly, select a feedback wire in the inner loop 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 box Associated Axes tab. This change in the Servo Update Period will have no effect on the behavior of existing motion control applications or on the overall performance of the motion control system. (x28647)
Motion Group Fault No Longer Produces Major Fault in Program Mode
In version 12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in program mode but will produce a Major Fault if the controller is in run or remote run mode. In versions earlier than version 12.01, the motion group could produce a major fault while the controller was in program or remote program mode. For example, a store to nonvolatile memory interrupts the execution of the motion planner, which produces a fault. (x36957)
Phase Loss Fault-action for AM vs. IAM on Kinetix 2000 & 6000 Drives
With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in RSLogix 5000 software without any user logic being written. However, a Kinetix Axis Module (AM) on the same power rail will require logic to be written if the user expects the motor on the AM to perform in the same manner as does the IAM. This logic should monitor the IAM’s phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes (x71448, x71717).
Motion Axis Fault Reset MAFR Timing Changed on Kinetix Drives to Accommodate Motor Commutation
The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate new checks for reset of the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing changes observed were 20ms in version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)
ControlFLASH Update of Rockwell Automation (RA) Sercos Drives via SERCOS Ring
Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA Sercos drives via ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating. ControlFLASH of the drives on the Ring must be done one drive node at a time.
Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the RA Sercos Drives to support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives must have revision 1.85 or higher, and the RA Ultra Sercos drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later. (x51766)
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 an anomaly with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680, x06823)
|
DLL Name
|
Compatible Versions
| |
|
Comcat.dll
|
4.71
|
5.0
|
|
Ole32.dll
|
4.0
|
4.71 or later
|
Configuring CRC Error Detection 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 box 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 Logix5000 controller. The process is simplified if non-DF1 communications is used to select CRC Error Detection in the Logix5000 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 Logix5000 controller. Open the Controller Properties dialog box and select the System Protocol tab. Under Error Detection enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000 information dialog box will display the error: ‘Failed to modify the DF1 Protocol configuration. Communications timed out.’ This is expected and normal for this operation; click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC. Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software select Go Online to re-establish online communications. This DF1 driver will now communicate only with Logix5000 controllers that are set up to use CRC Error Detection.
Fatal Error Handling
There is a log file generated that records abnormal events and which can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 software will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title ‘RSLogix 5000 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’. In order to more effectively address software error conditions, starting with version 14.00, the Fatal Error information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. The new file will be large. If it must be sent to Rockwell Automation Services & Support, it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). The RSLogix 5000 Fatal Error.Dmp file can also be deleted if not needed.
Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or in C:\Documents and Settings\All Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000 operating systems. For RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\<username>\Local Settings\Temp (for all operating systems).
Destination Operands for GSV Commands
Caution should be used in selecting the proper data type for the destination operand of a GSV instruction. Use of mismatched operand data types 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 Logix5000 controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx software version 2.20 or later, or the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.
User Disk Memory Utilization
If 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. Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may also be deleted.
AB_xxxx folders reside within a single folder named ‘RSLogix 5000.Temp’ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000 operating systems).
Application Notes RSLinx Software v20
RSLogix 5000 Software 20.x
In RSLogix 5000 software version 18 and later, there is an External Access tag attribute, which defines how an external application can access a tag. This functionality is fully supported by RSLinx Classic software version 2.56 and RSLinx Enterprise software version 5.21. RSLogix 5000 software version 18 and later can be used with earlier versions of RSLinx Classic software to go online to a controller; however, earlier versions of RSLinx Classic or RSLinx Enterprise software should not be used as a data server with a controller running firmware revision 18 or later. Unexpected results will be observed when using an earlier version of RSLinx Classic or RSLinx Enterprise software as a data server with a controller running firmware revision 18 or later. Please see Rockwell Automation Knowledgebase Technote #67071 (http://www.rockwellautomation.com/knowledgebase/).
You may be prevented from configuring the Ethernet Port of a CompactLogix5532E controller (catalog number 1769-L32E) via Channel 0 by using RSLinx software. To workaround the anomaly, use RSLogix 5000 software to configure the port (if the 1769-L32E controller is at revision 13) or use the BootP utility (which is enabled for a 1769-L32E controller at revision 1).
Beginning with RSLinx Classic software version 2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher) version features. Only one professional activation is required for both products. The RSLogix 5000 Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher).
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.
If you are using RSLinx software version 2.40 or later, you can use the EtherNet/IP driver. This driver will automatically browse for all EtherNet/IP-capable devices on the local or configured remote subnet. See RSLinx online help for information on this driver. Note that 1756-ENET/A and 1756-ENET/B modules will not respond to the browse commands. You must use a different driver for these modules.
For DF1 point-to-point communications, choose ‘RS232 DF1 Devices’ from the list of available drivers in RSLinx software. Then choose ‘Logix5550 Serial Port’ for DeviceType. 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 anomalies accessing information from I/O modules.
RSLinx software maintains knowledge of the memory layout of a Logix5000 controller in order to optimize the data access performance when accessing the data in these controllers. However, changes made to an offline project that are then downloaded can result in RSLinx software attempting to access tag information that is no longer present. When this occurs, RSLinx software halts the communications to the controller. To recover, both RSLinx software and the software requesting tags from RSLinx software must be restarted. To avoid this anomaly, use caution when making offline changes to a project and then downloading to a Logix5000 controller. In particular, changing the size of an array if elements of the array are already on scan, renaming a structure or a member of a user-defined data type used by a tag that is on scan, or changing the data type of a tag on scan from a larger size to a smaller size (for example, changing a DINT to a SINT). Note that RSLinx Enterprise Series software is able to accommodate these changes without requiring a restart.
Some third-party data servers use data access methods for which Rockwell Automation does not publicly publish information. Starting with RSLogix 5000 software version 18, data access methods were changed to support the Data Access Control feature. As a result, some issues may be observed when using these data servers with controllers running revision 18 firmware. Please see Rockwell Automation Knowledgebase Technote #67071 (http://www.rockwellautomation.com/knowledgebase/).
This release has the following application notes.
1756 Analog I/O Profile Not Retaining Engineering Units (1486580)
1756 Analog I/O Add-on Profiles allow users to set custom Engineering Units per channel, and these are stored as extended properties in the Studio 5000 Logix Designer application, versions 21 and later.
RSLogix 5000, versions 20 and earlier, does not support extended properties. When you use a 1756 Analog I/O Add-on Profile in RSLogix 5000, versions 20 and earlier, custom Engineering Units are not stored in the profile.
This release has the following application notes.
Application Notes v20.04
RSLogix 5000 Software 20.04
Product Resiliency Improvement
This release includes enhancements intended to improve product resiliency to potentially disruptive activities. These enhancements have been verified to not affect product safety, performance, expected life, configuration, or operation of the product. Rockwell Automation advises customers to follow good Industrial Control System (ICS) security practices that include regular product updates. To ensure authenticity, obtain product updates and new releases directly from Rockwell Automation.
Product resiliency includes, but is not limited to, security topics related to tamper prevention and detection, intellectual property management and source protection, and user authentication and authorization.
Support of minor versions
RSLogix 5000 software version 20.04 is aimed to restore minor revision compatibility as known prior to version 20. Files created in version 20.01 and 20.03 can be opened in version 20.04. Version 20.04 also allows you to upload and go online with files downloaded from version 20.01 and 20.03.
For more details, please see Rockwell Automation Knowledgebase Tech Note # 720913 (http://www.rockwellautomation.com/knowledgebase/).
EvRSI Replaced by FactoryTalk Activation Manager
Beginning with RSLogix 5000 software version 20, EvRSI activation has been replaced by the FactoryTalk Activation Manager utility. EvRSI activation will not be able to activate RSLogix 5000 software version 20. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Services & Support for information on migrating your activations to FactoryTalk Activation.
Unable to Connect to 1756-L7x Controller Using USB Port
For the 1756-L7x controllers, if you meet both of the following conditions, you will not be able to update or connect through RSLogix 5000 software to your 1756-L7x controller using the USB port:
If you meet both conditions, you will have to update the controller or connect through RSLogix 5000 software through a different means, such as Ethernet.
1769-L2y Controllers Cannot Be Properly Configured Using RSLogix 5000 Software Version 20.00
For 1769-L2y controller types, which were newly released in RSLogix 5000 software version 20, the Embedded Counters module cannot be properly configured for Pulse External Direction. This anomaly was corrected in version 20.01. 1769-L2y controllers can be properly configured by using RSLogix 5000 software version 20.01. However, 1769-L2y projects created by using RSLogix 5000 software version 20.00 will continue to be configured incorrectly. To correct the configuration, the controller must be recreated in RSLogix 5000 software. You may find it convenient to use the File > Import Component feature of RSLogix 5000 software to port your logic from the version 20.00 project to the new version 20.01 project. This affects the following controller types: 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, and 1769-L27ERM-QBFC1B.
Out-of-Box CIP Axis Position Loop Gain Values Adjusted with Load Observer
With the introduction of the CIP Motion Load Observer enhancement in version 19 of RSLogix 5000 software, the out-of-box calculations for several CIP Axis attributes were impacted. In particular, the Position Loop Bandwidth attribute and the Position Error Tolerance attribute will be automatically adjusted when the Load Coupling is change from Rigid to Compliant and Use Load Ratio is enabled. When a change to the Load Coupling is applied, the out-of-box Position Loop Bandwidth will be reduced by 90% and the out-of-box Position Error Tolerance will be increased by 90%. This has the effect of loosening the out-of-box Position Gains so that the Motion Load Observer loop response can be tightened.
Time Synchronization Replaces CST Time Mastership with Version 18.00 or Later
RSLogix 5000 software version 18 has replaced the concept of Coordinated System Time (CST) Mastership with the more comprehensive notion of Time Synchronization, also referred to as CIP Sync Time Coordination. The Date/Time page of the controller properties has been modified to reflect this change. For projects created with RSLogix 5000 software version 17 or earlier, if Coordinated System Time Master (CST) is enabled, then the converted project will have the Time Synchronization setting enabled. For more information about time synchronization using CIP Sync Time Coordination, refer to the Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003.
“Attribute Value not Settable” Reported Using AutoFLASH from Logix Firmware Revision 20 to an Earlier Revision
When attempting to download a project by using RSLogix 5000 software version 19 or earlier, if the controller firmware is at revision 20 and the controller is in Remote Run mode, then the version 19 software will not be able to change the controller mode in order to AutoFLASH the controller with revision 19 firmware. In this case, the controller mode must be changed either by using the keyswitch or by using RSLogix 5000 software version 20. (x123924)
CIP Generic Writes to Controller Objects that Originate from Another Controller May Fail
In RSLogix 5000 software version 20 there are enhanced security restrictions to controller CIP objects. Because of this some CIP Generic messages used to write directly to controller object attributes may not function. Any CIP generic object write that originates external to the controller may fail in RSLogix 5000 software version 20. CIP Generic writes that are executed in the controller’s own user program will operate normally.
Security Permissions Changed for Program Creation
In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to create an unscheduled program, a user will need permission for the ‘Program: Create’ action. To create a program scheduled in a task, however, a user will now need permission for both the ‘Program: Create’ and the ‘Task: Modify Properties’ actions. To create a program scheduled in the Power-Up Handler or Controller Fault Handler, a user will now need permission for both the ‘Program: Create’ and the ‘'Controller: Modify Properties’ actions. (x77816, x77817)
Testing SFC Online Edits No Longer Always Requires the Chart to Reset with Version 18.00 or Later
With RSLogix 5000 software version 17 and earlier, when performing online editing operations in a Sequential Function Chart (SFC), switching the executing logic from the original programming to the test edits version (or vice versa) resets the chart to the initial step and resets all stored actions. Beginning with version 18.00 of RSLogix 5000 software, many SFC online edits no longer result in this reset. In general, only edits that alter the logic structure of the chart will require the SFC routine to be reset.
In cases when a reset is required, you can force the transition with the initial step to false, wait for the routine to execute to the initial step, and then perform the test/un-test operation followed by removal of the force. Also, you could leverage the SFC Reset (SFR) instruction to reposition the chart back to the desired step. (x36331, x43482)
Can’t Create, View, or Edit Modules Based on Classic Profile After McAfee QuickClean
McAfee virus software version 8.0 ships with a ‘Quick Registry Cleaner’ component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of RSLogix 5000 classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module. This anomaly will also prevent the creation and import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (x81691)
L5X File List Not Filtered on Windows 7 Operating System
When performing a Partial Import online, the list of files displayed on the Import dialog box is filtered to show only files of the selected component type (for example, Program, Routine, Data Type, Equipment Phase). This filtering is not supported by the Windows 7 operating system. The Import dialog box will therefore show all L5X format files when running RSLogix 5000 software on a Windows 7 operating system. The icon and ToolTip for the component file will identify the file type. (x105789, x112515, x113267)
Unable to Open Full Project XML format file (.L5X) from Open/Import Project Dialog Box
RSLogix 5000 software versions 16 and earlier do not support full project import when using an XML format file (.L5X). If you have version 17 or later of RSLogix 5000 software installed along with some earlier version of RSLogix 5000 software and you are currently running that earlier version of software, then the Open/Import Project dialog box will not allow a file with an L5X or XML file extension to be opened for import. To open an L5X format project you must first be sure that RSLogix 5000 software version 17 or later is running. You can do this either by creating a new version 17 project or by opening any existing version 17 project that was saved with an ACD or L5K file extension. Alternatively, you can select the L5X project file in Microsoft Windows Explorer by right-clicking the L5X file name and using the ‘Open with’ menu item to open the file with ‘Component of the RSLogix 5000 Application’. Note that when the RSLogix 5000 software is installed, files with an ACD file extension are configured by default to open this way when selected. You can configure files with L5X and L5K file extensions to also do this through Windows Explorer by manually associating these extensions with the executable file RSLogix5000Loader.exe, typically installed in the directory C:\Program Files\Rockwell Software\RSLogix 5000\Common or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common. (x87808)
Adobe Reader Error Selecting ‘Online Books’ from the Tools Menu
After installing RSLogix 5000 software version 19, you may see the Tools>Online Books menu item. If this menu item is selected, Adobe Reader will report that ‘This file cannot be found.’ This error occurs when using RSLogix 5000 software version 19 or later if RSLogix 5000 software version 18 had also been installed on the same personal computer. The Online Books installed with version 18 software were accessed by using the Custom Tools Menu (Tools>Online Books). The Online Books installed with version 19 and later access the Online Books by using the Start Page Resource Center. With version 19 installed, the Custom Tools Menu item for version 18 Online Books remains on the Tools menu, but is no longer used. Once RSLogix 5000 software version 19 has been installed, the unused ‘Online Books’ Custom Tools Menu item can be manually removed by choosing Tools>Custom Tools. Then on the Custom Tools dialog box, select ‘Online Books’, click Delete, and then click OK to apply the change and close the dialog box. (x111895)
Unknown URL Attempting to Access Online Books or Vender Sample Projects from Start Page
If your personal computer is not configured as part of a domain, you may receive the error message ‘Unknown URL’ when attempting to access Online Books or Vender Sample Projects from the Start Page. This is the result of security enhancements to the Internet Explorer browser. If RSLogix 5000 software was installed by using the default installation path, the Online Books can be accessed from links provided in the file C:\Program Files\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf or C:\Program Files (x86)\Rockwell Software\RSLogix 5000\Common\<language>\Docs\top level linking.pdf, and the Vendor Sample Projects can be accessed from links provided in the file C:\RSLogix 5000\Projects\Samples\<language>\<version>\Third Party Products\Vendor Sample Projects.pdf. Access to Online Books and Vender Sample Projects can be allowed by adding ‘localhost’ to the allowed Local Intranet sites. (x89165)
Online Help from 32-bit .hlp Files is Not Displayed
The Windows Help (WinHlp32.exe) program is used to display RSLogix 5000 Online Help that is provided in 32-bit .hlp files. The Microsoft Corporation stopped including this 32-bit Help file viewer in Windows releases beginning with Windows Vista and Windows Server 2008 operating systems. RSLogix 5000 software version 18 and later display Online Help in HTML format and do not require this Windows Help program. However, some module profiles may continue to display Online Help by using 32-bit .hlp files. To properly display Online Help that is provided in 32-bit .hlp files on a Windows Vista or later operating system, you need to install the Windows Help program. This application is available for download from the Microsoft Download Center. For additional information on downloading and installing the Windows Help program, refer to the Microsoft Knowledgebase article ‘I cannot open Help files that require the Windows Help (WinHlp32.exe) program’, located at http://support.microsoft.com/?kbid=917607. (x109600)
Start Pages Won’t Work if Version 16.00 Is Installed After Other Versions
If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software or later, Start Pages will fail to load and the message ‘Server Startup Failure physicalPath=…’ will be displayed. In order to restore Start Page functionality it is necessary to re-install the version 17.00 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of RSLogix 5000 software and later. (x76424)
Function Block Diagram (FBD) ActiveX Faceplates are Not Compatible with Windows Vista or Later
The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista or later operating systems. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.
Overflow Checking Improved for Immediate Operand Values
In RSLogix 5000 software version 20, overflow checking for immediate operand values has been extended to all radix formats. Earlier versions of RSLogix 5000 software checked Octal values (i.e., 8#nnn) for overflow into a 32-bit integer. Starting with RSLogix 5000 software version 20, immediate operand values of any integer-type radix (Hexadecimal, Decimal, Octal, or Binary) are checked for overflow into a 32-bit integer. The overflow conditions are indicated as errors during the verification process. (x116816)
First Use of Drive Profile by User Who Did Not Install the Add-On Profiles Will Require Media Access
When a drive profile is first accessed, any user other than the user who installed the Drives Add-On Profiles version 4.02 or earlier will need access to the install media. When accessing the drive profile either by importing a project or by creating a drive in the I/O configuration tree, the user will be prompted with the following: “enter an alternate path to a folder containing the installation package ‘RADrives_PF7.msi’”. The user must then provide the path on the installation media to ...\ENU\MP\RADrives\RADrives_PF7.msi. These Add-On Profiles may have been installed either separately or as part of the installation of RSLogix 5000 software version 20.01. (x128249)
Manual Tune Fields Are Active When Servo is Disabled
In RSLogix 5000 software version 20, the Manual Tune parameters are enabled and editable when online for either the On or Off setting for the Servo parameter of a CIP_AXIS_DRIVE axis type. (x122492)
Motion Instruction Error Generated for Stop_All or MGS Active and Pending Motion Instruction
A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819, x85559)
Kinetix 6000 S0 and S1 Safety Drive with RSLogix 5000 Digital Inputs Configuration
The hardwired digital inputs on the Kinetix 6000 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user’s application must be written to make proper use of these digital inputs within the context of the associated motion instructions.
RSLogix 5000 Event Task Names can Conflict with Microsoft Windows Event Names
Creation of an RSLogix 5000 event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same name. Since Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.
Versions 18 and Later Require Updates to Custom Motion Database
If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you will need an updated motion database to work with RSLogix 5000 software versions 18 or later. The following table lists the motion database revisions that are used with these RSLogix 5000 software versions.
|
RSLogix 5000 Software Version
|
Motion Database Revision
|
|
20.04
|
9.22.0 [ Motion.mdb format ]
|
|
20.03/20.01
|
8.12.0 [ Motion.mdb format ]
|
|
20.00
|
8.9.0 [ Motion.mdb format ]
|
|
19.01 / 19.00
|
7.5.0 [ Motion.mdb format ]
|
|
18.02 / 18.01 / 18.00
|
6.9.0 [ Motion.mdb format ]
|
|
17.01 / 17.00
|
5.3.0 [ *Motion.md format ]
|
|
16.04 / 16.03 / 16.00
|
4.2.0 [ *Motion.md format ]
|
|
15.03 / 15.02 / 15.01 / 15.00
|
3.24.0 [ *Motion.md format ]
|
|
14.01 / 14.00
|
3.12.0 [ *Motion.md format ]
|
|
13.04 / 13.03 / 13.02 / 13.01 / 13.00
|
3.12.0 [ *Motion.md format ]
|
|
12.06 / 12.05 / 12.04 / 12.03 / 12.02 /
12.01 / 12.00
|
3.3.0 [ *Motion.md format ]
|
* Before a Custom Motor can be used in RSLogix 5000 software version 18 or later, any Custom Motor currently in a motion database file at revision 5 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.
To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.
Error May Be Displayed When Attempting to Print to Adobe PDF
When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from RSLogix 5000 software may result in a dialog box being displayed with the message ‘Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?’ This issue is documented in the Adobe Knowledgebase article http://kb.adobe.com/selfservice/viewContent.do?externalId=321561&sliceId=2, which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation. A temporary workaround for printing RSLogix 5000 reports is to click No in the dialog box, in the RSLogix 5000 Print dialog box change the printer name to some other printer, change the printer name back to Adobe PDF, and then click OK to print the document. (x88019)
GSV of PositionFeedback1 Attribute Reports Verification Error
In RSLogix 5000 software version 20, the PositionFeedback1 is now an integer value. When configuring a GSV of the PositionFeedback1 attribute, a destination tag value of type DINT is now required. (x123873)
Superimposed Motion Shifts Path
Beginning with RSLogix 5000 software version 20, the superimposed motion behavior has changed. In Absolute mode, when Superimposed mode is programmed, the path is shifted by the superimposed motion, except for moves in the following conditions: (1) Sequence of moves using any termination type other than TT0 or TT1, (2) a merge, or (3) when the queue becomes empty. This allows for the capability of any path that is drawn on a table moving in either the X or Y direction as a result of superimposed motion to look exactly the same as if it were drawn on a stationary table. In RSLogix 5000 software version 19, the path was not shifted when Superimposed mode is programmed and this was not achievable. (x122482)
Enhancements to Motion Planner may Affect Motion Profiles
The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there may be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There may also be minor differences in Trapezoidal velocity profiles. Please refer to the Motion Planner, Version 16.03 Application Solution, publication RA-AP031, for additional details.
Kinematics Transformations, Additional Native Geometry Support Compatibility Issues
The Kinematics Transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000 software version 16.03) should only be used with version 16.03 or greater of RSLogix 5000 software. If RSLogix 5000 software version 16.00 is used to upload a project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported geometries will be converted to the default Coordinate System Type of ‘Cartesian’. The message ‘attribute list error’ will be displayed during the download attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision earlier than revision 16.20. (x75769)
Version 17 Installation Does Not Automatically Uninstall Version 17 Beta Versions
This application note affects customers who have Beta software for version 17 of RSLogix 5000 software installed on their workstation. The version 17 Install will not offer to uninstall any previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software using Add/Remove Programs.
Using Security with Version 16 RSLogix 5000 Software and CPR 7 FactoryTalk Network Directory Server
This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed. However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named ‘UpdateActionsInSchema.exe’, can be found in the ‘System\SecuritySchemaUpdate\’ directory on the RSLogix 5000 DVD. Note that upon execution, the utility will provide further instructions.
SFCRESTART Attribute Removed for GSV/SSV
In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.
Migrating to FactoryTalk Security (from RSI Security Server)
Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Services Platform, which can be found on the RSLogix 5000 DVD. See the FactoryTalk Security installation instructions for further migration information.
Removal of Built-in Action Groups for Security
In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups for the RSI Security Server are:
They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.
Tag Modify Properties is Required to Update Configuration Dialog Boxes Having a Tag Tab
When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed indicating that ‘Tag: Modify Properties’ is not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)
FactoryTalk Security – Resource and Action Groups Coming With FactoryTalk CPR 9 Release
The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9 will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix controllers, and actions, like ‘Tag Create’, for easier security administration.
Ramp/Soak (RMPS) Results Appear to be in Error
Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time Left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (x72583)
Opening Pre-Version 17 Project with Axis may Generate Warning for Axis Performance Verification
Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types: MPL-A, MPL-B, 8720SM-xxxS, and TLY-A110T-Hxx. A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: ‘Axis ‘<tag_name>’ Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.’ When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.
File Import of Axis with MPx Motors may Generate Warning for Axis Performance Verification
In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: ‘Warning: During conversion of Axis ‘<tag name>’ – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.’ When this warning is encountered, the user should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, the user can reassociate the motor to the axis, but in this case all motor parameters will be reset to default Motion database values, canceling many previously tuned and saved axis values. This issue does not exist with database conversion of an ACD format project file. The motors that are affected are: MPF-B310P, -B320P, -B330P, -B4430K; MPG-A004-031, -A110-031, -A11-0-091; MPL-A310F, -A430P, -B420P, -B4520P, -B4530F, -B4530K, -B580J, -B980L; TL-A120P-H, -A130P-H, -A220P-H, A230P-H.
LINT Time Stamp Values Not Displayed with FactoryTalk View SE Utility
A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.
Controller Time Object Changed in Version 16 of RSLogix 5000 Software
The Controller Time Object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute ‘DateTime’, then this logic should be updated to use the new attribute ‘LocalDateTime’. You may also need to make other modifications to your application as a result of this change. (x72073, x72238)
Use New Clock Update Tool with Logix5000 Version 16 and Later Software
A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions may not properly synchronize workstation time and controller time.
Firmware Update Required for 1734 and 1738 Ethernet Point Adapters
When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:
The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.
Display of Non-Unicode Character Fonts in RSLogix 5000 Software
We recommended that the Microsoft Windows operating system’s ‘Language for non-Unicode programs (System Locale)’ be configured to match the localized language of the RSLogix 5000 software edition. This is especially true for the Chinese, Japanese, and Korean RSLogix 5000 software editions. Not configuring the PC’s operating system’s System Locale to match the language of RSLogix 5000 software may result in the inability of RSLogix 5000 software to display certain fonts.
If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when RSLogix 5000 software is started. Clicking ‘Change’ on this warning dialog box will navigate to the operating system dialog box from which the user can adjust the System Locale.
The System Locale can then be changed by selecting a new ‘Language for non-Unicode programs (System Locale)’ on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of RSLogix 5000 software (9324-RLD300ZHE), you should select ‘Chinese (PRC)’ for the System Locale.
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 software version 14, the directory structure for temporary RSLogix 5000 folders has been modified so that all AB_xxxx folders now reside within a single folder named ‘RSLogix 5000.Temp’ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000 operating systems).
To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the ‘RSLogix5000.Temp’ folder. (x51417, x85503)
MOTION_INSTRUCTION Data Type Change
The MOTION_INSTRUCTION data type changed in version 12 and later and the size increased from 12 bytes to 16 bytes. If you have created User-Defined data types that include members of type MOTION_INSTRUCTION you will lose tag initial values when you convert your project files from earlier versions. To work around this anomaly, export your project using the pre-version 12 version of RSLogix 5000 software and then import the project in version 12.02 or later. If you have written logic that relies on the old 12-byte size (for example by doing a COP of a MOTION_INSTRUCTION tag) you will need to verify that your logic is still correct.
The new MOTION_INSTRUCTION data type structure is:
FLAGSDINT
ENBOOL
DNBOOL
ERBOOL
PCBOOL
IPBOOL
ACBOOL
ACCELBOOL
DECELBOOL
ERRINT
STATUSSINT
STATESINT
SEGMENTDINT
EXERRSINT
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:
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
- infinite
+NAN
-NAN
-indefinite
|
1.$
-1.$
1.#QNAN
-1.#QNAN
-1.#IND
|
|
Exponential
|
+infinite
- infinite
+NAN
-NAN
-indefinite
|
1.#INF000e+000
-1.#INF000e+000
1.#QNAN00e+000
-1.#QNAN00e+000
-1.#IND0000e+000
|
The software also stores and displays the IEEE subnormal range:
RSLogix 5000 Software Appears to Lock Up When FactoryTalk AssetCentre (RSMACC) Connection Broken
If RSAudit message logging is enabled and the workstation is unable to connect to the FactoryTalk AssetCentre (RSMACC) server to log messages, RSLogix 5000 software experiences intermittent freezes while it is waiting for the message requests to time out. This might cause RSLogix 5000 software to appear as though it has locked up, but if you wait about one minute it will begin responding again. To resolve this anomaly, either restore the connection to the FactoryTalk AssetCentre (RSMACC) server or disable the RSAudit message logging. Once a connection has been restored, cached messages will be logged to the server and RSLogix 5000 software will resume normal operation. (x36127)
RSLogix 5000 Software Save May Result In Large Project ACD File
During a file save operation RSLogix 5000 software attempts to compress the contents of a project so that the resulting file (ACD) requires less disk space. When opening a project this process is reversed and the contents of the ACD file are de-compressed. In some instances, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may become abnormally large but it is still usable, that is, you can continue to work with the file as you would normally. However, if you contact Rockwell Automation Services & Support and provide a copy of your project file, this could help the RSLogix 5000 software development team to locate the source of the compression failure.
Activation Error Running Multiple Versions Simultaneously
If you have version 10.00 or later and an earlier version of RSLogix 5000 software installed on your computer, you will observe an activation error if you run the version 10.00 or later version first and then attempt to run the earlier version simultaneously. To work around this anomaly, always run the earlier version first and then run the version 10.00 or later version.
Default Project Directory
Be careful when performing operations with project files that depend on the default project directory. The Windows operating system controls and retains the default directory for the Open, Save As, and New Controller dialog boxes. Be sure to check that the folder selected is the one you wish to use when performing these operations to avoid mistakenly overwriting your project files. The Project Directory setting in the RSLogix 5000 Tools Options dialog box is normally used unless you navigate to a different directory within the Open, Save As, or New Controller dialog boxes. (x28475, x27886)
FBD Routine Localized Feedback Wiring Errors
In releases earlier than version 10.00 if you had a Function Block Diagram routine that contained nested feedback loops (outer and inner) you could download the project to a controller but may have encountered an error when uploading the project. This anomaly was caused by selecting multiple localized feedback wires in the outside feedback loop. In this release, this condition will be detected as a verification error in the routine. To correct this anomaly, select a feedback wire in the inner loop 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 box Associated Axes tab. This change in the Servo Update Period will have no effect on the behavior of existing motion control applications or on the overall performance of the motion control system. (x28647)
Motion Group Fault No Longer Produces Major Fault in Program Mode
In version 12.01 and later, a motion group that is configured as General Fault Type: Major Fault, will no longer produce a Major Fault in program mode but will produce a Major Fault if the controller is in run or remote run mode. In versions earlier than version 12.01, the motion group could produce a major fault while the controller was in program or remote program mode. For example, a store to nonvolatile memory interrupts the execution of the motion planner, which produces a fault. (x36957)
Phase Loss Fault-action for AM vs. IAM on Kinetix 2000 & 6000 Drives
With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in RSLogix 5000 software without any user logic being written. However, a Kinetix Axis Module (AM) on the same power rail will require logic to be written if the user expects the motor on the AM to perform in the same manner as does the IAM. This logic should monitor the IAM’s phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes (x71448, x71717).
Motion Axis Fault Reset MAFR Timing Changed on Kinetix Drives to Accommodate Motor Commutation
The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate new checks for reset of the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing changes observed were 20ms in version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)
ControlFLASH Update of Rockwell Automation (RA) Sercos Drives via SERCOS Ring
Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA Sercos drives via ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating. ControlFLASH of the drives on the Ring must be done one drive node at a time.
Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the RA Sercos Drives to support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives must have revision 1.85 or higher, and the RA Ultra Sercos drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later. (x51766)
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 an anomaly with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680, x06823)
|
DLL Name
|
Compatible Versions
| |
|
Comcat.dll
|
4.71
|
5.0
|
|
Ole32.dll
|
4.0
|
4.71 or later
|
Configuring CRC Error Detection 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 box 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 Logix5000 controller. The process is simplified if non-DF1 communications is used to select CRC Error Detection in the Logix5000 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 Logix5000 controller. Open the Controller Properties dialog box and select the System Protocol tab. Under Error Detection enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000 information dialog box will display the error: ‘Failed to modify the DF1 Protocol configuration. Communications timed out.’ This is expected and normal for this operation; click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC. Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software select Go Online to re-establish online communications. This DF1 driver will now communicate only with Logix5000 controllers that are set up to use CRC Error Detection.
Fatal Error Handling
There is a log file generated that records abnormal events and which can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 software will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title ‘RSLogix 5000 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’. In order to more effectively address software error conditions, starting with version 14.00, the Fatal Error information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. The new file will be large. If it must be sent to Rockwell Automation Services & Support, it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). The RSLogix 5000 Fatal Error.Dmp file can also be deleted if not needed.
Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or in C:\Documents and Settings\All Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000 operating systems. For RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\<username>\Local Settings\Temp (for all operating systems).
Destination Operands for GSV Commands
Caution should be used in selecting the proper data type for the destination operand of a GSV instruction. Use of mismatched operand data types 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 Logix5000 controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx software version 2.20 or later, or the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756-DHRIO module.
User Disk Memory Utilization
If 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. Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may also be deleted.
AB_xxxx folders reside within a single folder named ‘RSLogix 5000.Temp’ located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista, Windows Server 2008, and Windows 7 operating systems, or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000 operating systems).
This release has the following application notes.
Application notes for RSLogix 5000 version 20.05
These are the application notes for RSLogix 5000 version 20.05.
Supported Logix Controllers
While the programming software continues to extend its functionality with each new release, the physical controllers that it supports vary. New controllers are added, and in some cases, support for existing controllers may be removed. While a specific controller may not be supported by the current release, the side-by-side installation of multiple versions of the software provide, in most cases, a means to support the older hardware. If migrating from one controller to another, a project created for one controller can be easily converted to another controller using the Controller Properties configuration dialog box within the software.
If opening a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software provides an appropriate warning and automatically provides the option to convert the project to one of the controllers supported by the release.
The table provides a breakdown of the various Logix 5000 controllers and the initial or minimum version of RSLogix 5000 application required to support the controller.
|
Controller Catalog Number
|
Minimum Major
Software Version
|
|
ControlLogix 1756-L61 Series A
|
12.00.00
|
|
ControlLogix 1756-L61 Series B
|
12.00.00
|
|
GuardLogix 1756-L61S Series B
|
14.00.001
|
|
ControlLogix 1756-L62 Series A
|
12.00.00
|
|
ControlLogix 1756-L62 Series B
|
12.00.00
|
|
GuardLogix 1756-L62S Series B
|
14.00.001
|
|
ControlLogix 1756-L63 Series A
|
10.00.00
|
|
ControlLogix 1756-L63 Series B
|
12.00.00
|
|
ControlLogix 1756-L63XT Series B
|
16.00.00
|
|
GuardLogix 1756-L63S Series B
|
17.00.00
|
|
ControlLogix 1756-L64 Series B
|
16.00.00
|
|
ControlLogix 1756-L65
|
17.00.00
|
|
ControlLogix 1756-L71 Series B
|
20.00.00
|
|
ControlLogix 1756-L71S Series B
|
20.01.00
|
|
ControlLogix 1756-L72 Series A
|
19.00.00
|
|
ControlLogix 1756-L72 Series B
|
20.00.00
|
|
GuardLogix 1756-L72S Series B
|
20.00.00
|
|
ControlLogix 1756-L73 Series A
|
18.00.00
|
|
ControlLogix 1756-L73 Series B
|
20.00.00
|
|
ControlLogix 1756-L73XT Series B
|
20.00.00
|
|
GuardLogix 1756-L73S Series B
|
20.00.00
|
|
GuardLogix 1756-L73SXT Series B
|
20.00.00
|
|
ControlLogix 1756-L74 Series A
|
19.00.00
|
|
ControlLogix 1756-L74 Series B
|
20.00.00
|
|
ControlLogix 1756-L75 Series A
|
18.00.00
|
|
ControlLogix 1756-L75 Series B
|
20.00.00
|
|
CompactLogix 1768-L43 Series A
|
15.00.00
|
|
CompactLogix 1768-L43 Series B
|
16.03.00
|
|
CompactLogix 1768-L43S Series A
|
18.00.00
|
|
CompactLogix 1768-L45 Series A
|
16.03.00
|
|
CompactLogix 1768-L45 Series B
|
16.03.00
|
|
CompactLogix 1768-L45S Series A
|
18.00.00
|
|
CompactLogix 1769-L16ER-BB1B Series
A
|
20.00.00
|
|
CompactLogix 1769-L16ER-BB1B Series
B
|
20.00.00
|
|
CompactLogix 1769-L18ER-BB1B Series
A
|
20.00.00
|
|
CompactLogix 1769-L18ER-BB1B Series
B
|
20.00.00
|
|
CompactLogix 1769-L18ERM-BB1B
Series A
|
20.00.00
|
|
CompactLogix 1769-L18ERM-BB1B
Series B
|
20.00.00
|
|
CompactLogix 1769-L23E-QB1
|
17.00.00
|
|
CompactLogix 1769-L23E-QBFC1
|
17.00.00
|
|
CompactLogix 1769-L23-QBFC1
|
17.00.00
|
|
CompactLogix 1769-L24ER-QB1B
|
20.00.00
|
|
CompactLogix 1769-L24ER-QBFC1B
|
20.00.00
|
|
CompactLogix 1769-L27ERM-QBFC1B
|
20.00.00
|
|
CompactLogix 1769-L30ER
|
20.00.00
|
|
CompactLogix 1769-L30ER-NSE
|
20.00.00
|
|
CompactLogix 1769-L30ERM
|
20.00.00
|
|
CompactLogix 1769-L31
|
13.00.002
|
|
CompactLogix 1769-L32C
|
13.00.002
|
|
CompactLogix 1769-L32E
|
13.00.002
|
|
CompactLogix 1769-L33ER
|
20.00.00
|
|
CompactLogix 1769-L33ERM
|
20.00.00
|
|
CompactLogix 1769-L35CR
|
20.00.002
|
|
CompactLogix 1769-L35E
|
12.00.002
|
|
CompactLogix 1769-L36ERM
|
20.00.00
|
|
SoftLogix 1789-L60
|
6.00.00
|
1 Excludes RSLogix 5000 software version 15.
2 Excludes GuardLogix software version 14.
Microsoft® .NET Framework 4.6 may cause failure in earlier versions of the RSLogix 5000 application
When installing version 20.05 of RSLogix 5000, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:
A higher upgrade is already installed on the computer
When installing RSLogix 5000 version 20.05, the installation fails with the message "A higher upgrade is already installed" when FactoryTalk® Linx™ 6.0 software is installed on the computer. The installation fails on RSLinx Enterprise 5.90.
To avoid this problem, do one of these options.
For more information, refer to Rockwell Automation Knowledgebase Answer ID 1072383.
Firmware update files may not be located in the search paths configured in ControlFLASH
When updating the firmware as part of the project download, the Update Module Firmware dialog box may display an error that it cannot find the location of the updated firmware files.
The installation of ControlFLASH version 15.01 moves the DMK files located in the ControlFLASH installation folder (C:\Program Files (x86)\ControlFLASH for 64-bit operating systems or C:\Program Files\ControlFLASH for 32-bit operating systems) to a new folder located in C:\Users\Public\Documents\Rockwell Automation\Firmware Kits.
Older versions of ControlFLASH and Logix Designer place DMK flash files in previous ControlFLASH file locations.
The work around if ControlFLASH cannot find the location of the DMK files:
For more information, refer to Rockwell Automation Knowledgebase Answer ID 1071313.
Failed to go online with the controller error message appears twice when communications module is not located in a trusted slot
When attempting to go online with a controller that is set up to only allow communications through trusted slots, a failed to go online with the controller error message appears if the communication module is not located in a trusted slot.
Clicking OK to close the error message causes the error message to appear again. Click OK again to close error message.
When a Flex I/O module is attached to Flex Ethernet adapter, select Compatible Module or Disable Keying as the Electronic Keying option in the classic Flex I/O profile
When a Flex I/O module is attached to a 1794-AENT adapter, on the General tab in the classic profile, select either Compatible Module or Disable Keying as the Electronic Keying option. Even though Exact Match is available as an Electronic Keying option, Flex modules do not use the Exact Match keying option. Electronic keying is based on an external Flex ID value which does not depend on the module's minor revision.
Versions 18.00.00 and later require updates to Custom Motion Database
When using a Custom RSLogix 5000 Motion Database in RSLogix 5000 software versions 12.00.00 through 17.00.00, update the motion database to work with versions 18.00.00 or later. The table lists the motion database revisions used with these application versions.
|
Version of Application
|
Motion Database Revision
|
|
20.05.00
|
12.2.0 [ Motion.mdb format ]
|
|
20.01.00
|
8.12.00 [ Motion.mdb format ]
|
|
20.00.00
|
8.09.00 [ Motion.mdb format ]
|
|
19.01.00 / 19.00.00
|
7.05.00 [ Motion.mdb format ]
|
|
18.02.00 / 18.01.00 / 18.00.00
|
6.09.00 [ Motion.mdb format ]
|
|
17.01.00 / 17.00.00
|
5.03.00 [ *Motion.md format ]
|
|
16.04.00 / 16.03.00 / 16.00.00
|
4.02.00 [ *Motion.md format ]
|
|
15.03.00 / 15.02.00 / 15.01.00 / 15.00.00
|
3.24.00 [ *Motion.md format ]
|
|
14.01.00 / 14.00.00
|
3.12.00 [ *Motion.md format ]
|
|
13.04.00 / 13.03.00 / 13.02.00 / 13.01.00 / 13.00.00
|
3.12.00 [ *Motion.md format ]
|
|
12.06.00 / 12.05.00 / 12.04.00 / 12.03.00 / 12.02.00 /
12.01.00 / 12.00.00
|
3.03.00 [ *Motion.md format ]
|
* Before a Custom Motor can be used in version 18.00.00 or later, any Custom Motor currently in a motion database file at revision 5.00.00 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.
To initiate the process of getting the database updated, please email the request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if the current database includes non-Rockwell motors.
MSXML 4.0
This version of the software does not install or use MSXML 4.0. MSXML 4.0 has security risks associated with it and is no longer supported by Microsoft. For more information about MSXML and its availability, see the MSXML Roadmap. When installing products or components made by other vendors that use MSXML 4.0, contact the vendor for questions about the security risk associated with MSXML 4.0.
Unattended or silent install
Use command-line parameters to perform an unattended or silent installation of the software.
Command-line parameters
The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").
|
Parameter
|
Description
|
|
/?
|
Displays the usage options for installation parameters.
|
|
/Q
|
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended if you are deploying the software installation
using an IT tool or script, and do not expect to see any error or restart
messages. When using this parameter, your IT tool or script should check the
error codes, and respond as needed. For example, if the installation returns
error code 1641, then the IT tool or script should restart the computer and
relaunch the installation after restart.
This parameter is required if /QS is not specified.
|
|
/QS
|
Unattended Install, install runs in a quiet simple mode and shows progress
through the UI, it does not accept any input but still shows error or restart
messages.
When using this parameter, you will not have to check the error codes, and
the installation will stop and display a prompt if there are error or restart
messages. For example, if an immediate restart is required to complete the
install, a restart message will be displayed for you to confirm the restart.
Installation resumes automatically from the point of interruption after restart.
This parameter is required if /Q is not specified.
|
|
/IAcceptAllLicenseTerms
|
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
|
|
/AutoRestart
|
Automatically restarts the computer after the installation is complete. Used
when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used, silent install (/Q) will
return either error code 1641 or 3010 if a restart is required, and unattended
install (/QS) will result in a confirmation prompt that must be agreed to before
the installation is completed.
|
|
/SetupLanguage="value"
|
Specifies which language will be displayed during install process.
The value must be the one of the following:
This parameter is optional. If this parameter is not used, the default language
is the current user or operating system user interface language.
|
|
/Record
|
Records the installation options chosen to a recording file.
This parameter is optional.
|
|
/Playback
|
Plays back a recording file to specify the installation options.
This parameter is optional.
|
|
/Uninstall
|
Uninstalls the product.
|
|
/Product="value"
|
Specifies which sub-products will be installed.
Only required if sub-products are included with the install package.
If the software does not include sub-products, this parameter is not available.
|
|
/ProductLanguage="value"
|
Specifies the language version of the software being installed.
The value must be the one of the following:
This parameter is optional. If this parameter is not used, the default language
is the same as the setup language.
If the software does not support multiple languages, this parameter is not
available.
|
| /InstallLocation="value"
Or
/InstallDrive="value"
|
Specifies the install location or install drive respectively.
This parameter is optional. If this parameter is not used, the default install
location is "C:\Program Files (x86)\Rockwell Software".
Some software restricts the installer to change only the drive the software is
installed on. Use /? to determine which parameter is supported.
|
|
/SerialNumber="value"
|
Specifies the serial number of the software being installed. This is used to
activate the software during installation.
This parameter is optional. If it is not specified, the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required, this
parameter is not available.
|
|
/ProductKey="value"
|
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified, the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required, this
parameter is not available.
|
|
/Version="value"
|
Specifies the version of the software to activate that corresponds to the
product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified, the installer will use the most
recent product version available.
Some software does not require activation. If activation is not required, this
parameter is not available.
|
Examples
The following examples show how to use the installation commands.
Setup.exe /Q /IAcceptAllLicenseTerms
Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /InstallDrive=D:
Error codes
The following table identifies the error codes that can be returned by an installation.
|
Error Code
|
Value
|
Description
|
|
ERROR_SUCCESS
|
0
|
The installation completed successfully.
|
|
ERROR_INVALID_PARAMETER
|
87
|
One of the parameters was invalid.
|
|
ERROR_INSTALL_USEREXIT
|
1602
|
The installation was cancelled by the user.
|
|
ERROR_INSTALL_FAILURE
|
1603
|
A fatal error occurred during installation.
|
|
ERROR_BAD_CONFIGURATION
|
1610
|
The configuration data for this product is corrupt. Contact your
support personnel.
|
|
ERROR_SUCCESS_REBOOT_INITIATED
|
1641
|
The installer has initiated a restart. After restart, installation
will continue.
|
|
ERROR_SUCCESS_REBOOT_REQUIRED
|
3010
|
A restart is required to complete the installation. After restart,
the product is successfully installed.
|
|
ERROR_REBOOT_PENDING
|
3012
|
Restart of the computer is currently pending. The computer
must be restarted before installation can continue.
|
This release has the following application notes.
These are the application notes for RSLogix 5000 version 20.06.
Supported Logix Controllers
While the programming software continues to extend its functionality with each new release, the physical controllers that it supports vary. New controllers are added, and in some cases, support for existing controllers may be removed. While a specific controller may not be supported by the current release, the side-by-side installation of multiple versions of the software provide, in most cases, a means to support the older hardware. If migrating from one controller to another, a project created for one controller can be easily converted to another controller using the Controller Properties configuration dialog box within the software.
If opening a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software provides an appropriate warning and automatically provides the option to convert the project to one of the controllers supported by the release.
The table provides a breakdown of the various Logix 5000 controllers and the initial or minimum version of RSLogix 5000 application required to support the controller.
|
Controller Catalog Number
|
Minimum Major
Software Version
|
|
ControlLogix 1756-L61 Series A
|
12.00
|
|
ControlLogix 1756-L61 Series B
|
12.00
|
|
GuardLogix 1756-L61S Series B
|
14.001
|
|
ControlLogix 1756-L62 Series A
|
12.00
|
|
ControlLogix 1756-L62 Series B
|
12.00
|
|
GuardLogix 1756-L62S Series B
|
14.001
|
|
ControlLogix 1756-L63 Series A
|
10.00
|
|
ControlLogix 1756-L63 Series B
|
12.00
|
|
ControlLogix 1756-L63XT Series B
|
16.00
|
|
GuardLogix 1756-L63S Series B
|
17.00
|
|
ControlLogix 1756-L64 Series B
|
16.00
|
|
ControlLogix 1756-L65
|
17.00
|
|
ControlLogix 1756-L71 Series B
|
20.00
|
|
ControlLogix 1756-L71S Series B
|
20.01
|
|
ControlLogix 1756-L72 Series A
|
19.00
|
|
ControlLogix 1756-L72 Series B
|
20.00
|
|
GuardLogix 1756-L72S Series B
|
20.00
|
|
ControlLogix 1756-L73 Series A
|
18.00
|
|
ControlLogix 1756-L73 Series B
|
20.00
|
|
ControlLogix 1756-L73XT Series B
|
20.00
|
|
GuardLogix 1756-L73S Series B
|
20.00
|
|
GuardLogix 1756-L73SXT Series B
|
20.00
|
|
ControlLogix 1756-L74 Series A
|
19.00
|
|
ControlLogix 1756-L74 Series B
|
20.00
|
|
ControlLogix 1756-L75 Series A
|
18.00
|
|
ControlLogix 1756-L75 Series B
|
20.00
|
|
CompactLogix 1768-L43 Series A
|
15.00
|
|
CompactLogix 1768-L43 Series B
|
16.03
|
|
CompactLogix 1768-L43S Series A
|
18.00
|
|
CompactLogix 1768-L45 Series A
|
16.03
|
|
CompactLogix 1768-L45 Series B
|
16.03
|
|
CompactLogix 1768-L45S Series A
|
18.00
|
|
CompactLogix 1769-L16ER-BB1B Series
A
|
20.00
|
|
CompactLogix 1769-L16ER-BB1B Series
B
|
20.00
|
|
CompactLogix 1769-L18ER-BB1B Series
A
|
20.00
|
|
CompactLogix 1769-L18ER-BB1B Series
B
|
20.00
|
|
CompactLogix 1769-L18ERM-BB1B
Series A
|
20.00
|
|
CompactLogix 1769-L18ERM-BB1B
Series B
|
20.00
|
|
CompactLogix 1769-L23E-QB1
|
17.00
|
|
CompactLogix 1769-L23E-QBFC1
|
17.00
|
|
CompactLogix 1769-L23-QBFC1
|
17.00
|
|
CompactLogix 1769-L24ER-QB1B
|
20.00
|
|
CompactLogix 1769-L24ER-QBFC1B
|
20.00
|
|
CompactLogix 1769-L27ERM-QBFC1B
|
20.00
|
|
CompactLogix 1769-L30ER
|
20.00
|
|
CompactLogix 1769-L30ER-NSE
|
20.00
|
|
CompactLogix 1769-L30ERM
|
20.00
|
|
CompactLogix 1769-L31
|
13.002
|
|
CompactLogix 1769-L32C
|
13.002
|
|
CompactLogix 1769-L32E
|
13.002
|
|
CompactLogix 1769-L33ER
|
20.00
|
|
CompactLogix 1769-L33ERM
|
20.00
|
|
CompactLogix 1769-L35CR
|
20.002
|
|
CompactLogix 1769-L35E
|
12.002
|
|
CompactLogix 1769-L36ERM
|
20.00
|
1 Excludes RSLogix 5000 software version 15.
2 Excludes GuardLogix software version 14.
When installing version 20.05 of RSLogix 5000, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:
When installing RSLogix 5000 version 20.06, the installation fails with the message "A higher upgrade is already installed" when FactoryTalk® Linx™ 6.0 software is installed on the computer. The installation fails on RSLinx Enterprise 5.90.
To avoid this problem, do one of these options.
For more information, refer to Rockwell Automation Knowledgebase Answer ID 1072383.
When updating the firmware as part of the project download, the Update Module Firmware dialog box may display an error that it cannot find the location of the updated firmware files.
The installation of ControlFLASH version 15.01 moves the DMK files located in the ControlFLASH installation folder (C:\Program Files (x86)\ControlFLASH for 64-bit operating systems or C:\Program Files\ControlFLASH for 32-bit operating systems) to a new folder located in C:\Users\Public\Documents\Rockwell Automation\Firmware Kits.
Older versions of ControlFLASH and Logix Designer place DMK flash files in previous ControlFLASH file locations.
The work around if ControlFLASH cannot find the location of the DMK files:
For more information, refer to Rockwell Automation Knowledgebase Answer ID 1071313.
When attempting to go online with a controller that is set up to only allow communications through trusted slots, a failed to go online with the controller error message appears if the communication module is not located in a trusted slot.
Clicking OK to close the error message causes the error message to appear again. Click OK again to close error message.
When a Flex I/O module is attached to a 1794-AENT adapter, on the General tab in the classic profile, select either Compatible Module or Disable Keying as the Electronic Keying option. Even though Exact Match is available as an Electronic Keying option, Flex modules do not use the Exact Match keying option. Electronic keying is based on an external Flex ID value which does not depend on the module's minor revision.
When using a Custom RSLogix 5000 Motion Database in RSLogix 5000 software versions 12.00 through 17.00, update the motion database to work with versions 18.00 or later. The table lists the motion database revisions used with these application versions.
|
Version of Application
|
Motion Database Revision
|
|
20.06
|
14.39.00 [ Motion.mdb format ]
|
|
20.05
|
12.2.0 [ Motion.mdb format ]
|
|
20.01
|
8.12.00 [ Motion.mdb format ]
|
|
20.00
|
8.09.00 [ Motion.mdb format ]
|
|
19.01/ 19.00
|
7.05.00 [ Motion.mdb format ]
|
|
18.02 / 18.01 / 18.00
|
6.09.00 [ Motion.mdb format ]
|
|
17.01 / 17.00
|
5.03.00 [ *Motion.md format ]
|
|
16.04 / 16.03 / 16.00
|
4.02.00 [ *Motion.md format ]
|
|
15.03 / 15.02 / 15.01 / 15.00
|
3.24.00 [ *Motion.md format ]
|
|
14.01 / 14.00
|
3.12.00 [ *Motion.md format ]
|
|
13.04 / 13.03 / 13.02 / 13.01 / 13.00
|
3.12.00 [ *Motion.md format ]
|
|
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 12.01/ 12.00
|
3.03.00 [ *Motion.md format ]
|
* Before a Custom Motor can be used in version 18.00 or later, any Custom Motor currently in a motion database file at revision 5.00 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.
To initiate the process of getting the database updated, please email the request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if the current database includes non-Rockwell motors.
This version of the software does not install or use MSXML 4.0. MSXML 4.0 has security risks associated with it and is no longer supported by Microsoft. For more information about MSXML and its availability, see the MSXML Roadmap. When installing products or components made by other vendors that use MSXML 4.0, contact the vendor for questions about the security risk associated with MSXML 4.0.
Use command-line parameters to perform an unattended or silent installation of the software.
This table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").
|
Parameter
|
Description
|
|
/?
|
Displays the usage options for installation parameters.
|
|
/Q
|
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation
using an IT tool or script, and don’t expect any error or restart messages.
When using this parameter, check the error codes, and respond as needed.
For example, if the installation returns error code 1641, then the IT tool or
script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
|
|
/QS
|
Unattended Install, install runs in a quiet simple mode and shows progress
through the UI, it does not accept any input but still shows error or restart
messages.
When using this parameter, the installation will stop and display a prompt if
there are error or restart messages. For example, if an immediate restart is
required to complete the install, a restart message will be displayed to confirm
the restart. Installation resumes automatically from the point of interruption
after restart.
This parameter is required if /Q is not specified.
|
|
/IAcceptAllLicenseTerms
|
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
|
|
/AutoRestart
|
Automatically restarts the computer after the installation is complete. Used
when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used silent install (/Q) will
return either error code 1641 or 3010 if a restart is required, and unattended
install (/QS) will result in a confirmation prompt that must be agreed to before
the installation is completed.
|
|
/Record
|
Records the installation options chosen to a recording file.
This parameter is optional.
|
|
/Playback
|
Plays back a recording file to specify the installation options.
This parameter is optional.
|
|
/ftsp-s
|
Specifies the FactoryTalk directory scope for restore. Only "Global" and
"Local" scopes are supported.
This parameter is optional.
|
|
/ftsp-bak
|
Specifies the location where the restore file can be found.
This parameter is optional.
|
|
/ftsp-pp
|
Specifies the plain text used to decrypt the backup file.
This parameter is optional.
|
|
/ftsp-value=enable/disable
|
Specifies to enable or disable the option Require computer accounts for all
client machines in Security Policy. The option is used to determine whether
or not a client computer account must exist in the directory to login.
This parameter is optional.
|
|
/DirectoryServer
|
Specifies the directory server name.
This parameter is optional. If it is not specified, the setup turns on HTTPS for
communication, and a TLS certificate must be configured after installation.
|
|
/NoHTTPS
|
Specifies that the setup turns off HTTPS.
This parameter is optional. If it is not specified, the setup turns on HTTPS for
communication, and a TLS certificate must be configured after installation.
|
|
/Uninstall
|
Uninstalls the product.
The Logix Designer application does not support the /Uninstall option.
|
|
/SetupLanguage="value"
|
Specifies which language is displayed during install process.
The value must be the one of these:
This parameter is optional. If this parameter is not used, the default language
is the current user or operating system user interface language.
|
|
/ProductLanguage="value"
|
Specifies the language version of the software being installed.
The value must be the one of these:
This parameter is optional. If this parameter is not used, the default language
is the same as the setup language.
If the software does not support multiple languages this parameter is not
available.
|
| /InstallLocation="value"
Or
/InstallDrive="value"
|
Specifies the install location or install drive respectively.
This parameter is optional. If this parameter is not used, the default install
location is "C:\Program Files (x86)\Rockwell Software".
Some software restricts the installer to only change the drive the software is
installed on. Use /? to determine which parameter is supported.
|
|
/IgnoreWarning
|
Specifies that the setup ignores warnings and continues.
This parameter is optional. If it is not specified, the setup exits when a
warning occurs.
|
|
/SerialNumber="value"
|
Specifies the serial number of the software being installed. This is used to
activate the software during installation.
This parameter is optional. If it is not specified the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required this
parameter is not available.
|
|
/ProductKey="value"
|
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required this
parameter is not available.
|
|
/Version="value"
|
Specifies the version of the software to activate which corresponds to the
product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified the installer uses the most
recent product version available.
Some software does not require activation. If activation is not required this
parameter is not available.
|
These examples show how to use the installation commands.
This table identifies the error codes that can be returned by an installation.
|
Error Code
|
Value
|
Description
|
|
ERROR_SUCCESS
|
0
|
The installation completed successfully.
|
|
ERROR_INVALID_PARAMETER
|
87
|
One of the parameters was invalid.
|
|
ERROR_INSTALL_USEREXIT
|
1602
|
The installation was cancelled by the user.
|
|
ERROR_INSTALL_FAILURE
|
1603
|
A fatal error occurred during installation.
|
|
ERROR_BAD_CONFIGURATION
|
1610
|
The configuration data for this product is corrupt. Contact your
support personnel.
|
|
ERROR_REBOOT_CONTINUE
|
1641
|
A reboot is required to continue to installation.
|
|
ERROR_SUCCESS_REBOOT_REQUIRED
|
3010
|
A restart is required to complete the installation. After restart the
product is successfully installed.
|
|
ERROR_REBOOT_PENDING
|
3012
|
A restart is pending and is required before the installation can
continue.
|
|
ERROR_SUCCESS_NOT_APPLICABLE
|
3013
|
The installation cannot proceed because the products are
already installed.
|
|
ERROR_SUCCESS_WARNING_REBOOT
|
3014
|
The installation succeeded with warnings. Check the installation
log file for details. To complete the installation, restart the
computer.
|
|
|
1
|