02 Labelpoint Programmer S Reference Manual

Release Notes
( 9324-RLDx ) RSLogix 5000 programming software. All you need for discrete, process, batch, motion, safety etc.
Version 20.04.00
Catalog Number RSLogix 5000
These release notes describe version information for DESC:( 9324-RLDx ) RSLogix 5000 programming software. All you need for discrete, process, batch,
motion, safety etc., NAME:RSLogix 5000, SERIES:. VERSION:20.04.00.
System Features
This release includes the following system features.
MDSC – Master Driven Speed Control
System Feature
Logix Firmware/RSLogix 5000 Software 20.011
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L64, 1756-L65, 1756-L61S, 1756-L62S, 1756-L63S, 1756-L63XT, 1756-L71, 1756-L72, 1756-L73,
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
MDSC allows time based moves to be driven by position or velocity information instead of time. The external input can be any virtual or physical axis. There
are several move types that can now be driven by position: MAM (motion axis move), MAJ (motion axis jog), MATC (time based CAMing), MCLM (linear
interpolation) and MCCM (circular interpolation). Operands were added to these instructions to support the Master Driven Speed Control capability.
Additionally, two new instructions were added for Integrated Motion: MDAC for single axis master and slave axis definition, and MDCC for multiple axis master
axis to slave coordinate system definition.
Module Discovery in RSLogix 5000 Software
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
SoftLogix 5800 Version 20.00.00
Catalog Number 1789-L10, 1789-L30, 1789-L60
Module Discovery is a new online capability that can browse the backplane or network to find devices to add to the Logix I/O tree (currently not supported in
CompactLogix controllers). This feature simplifies the user experience for adding devices to the I/O tree by not requiring you to know the exact catalog
number, slot number, or network address. It presents a list of all devices found on the backplane or remote network, identifies which devices already exist in
the project, and provides a Create button for the rest to easily add them to the project. The devices must also support addition online.
graphic

QuickConnect – EtherNet/IP Devices
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
QuickConnect allows EtherNet/IP devices to quickly power up and connect to an EtherNet/IP network. QuickConnect requires a Logix controller with
embedded QuickConnect firmware and support in the I/O platform with embedded QuickConnect firmware (currently select ArmorBlocks).
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/).

Restricted Communication
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
By clicking the 'Restrict Communications Except Through Selected Slots,' software products including RSLinx, RSLogix 5000, and ControlFLASH software will
not be able to communicate with the controller except via communication cards loaded in the selected slots. Communication from the controller to other
devices, such as remote I/O modules and other controllers, are not impacted by this setting. This setting is useful to be sure that configuration changes to
the controller can only be made through selected networks. When this setting is enabled, these software products will not be able to communicate with the
controller via the USB port.
For more information, see the ControlLogix System User Manual publication 1756-UM001.
Security Authority Binding
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
Catalog Number 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B, 1769-
L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, 1769-L36ERM
By checking the Require Matching Security Authority ID for Authentication and Authorization checkbox, you can bind the project file to a specific instance of
the FactoryTalk Security directory. This lets you to verify the identity of the FactoryTalk Security directory that was used to authenticate and authorize users
of a secured project file or secured controller. Once this is assigned, 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 directory.

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.
For more information, see the FactoryTalk Security System Configuration Guide, publication
FTSEC-QS001.
Socket Connections
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
Socket connections in version 20 allow connectivity with non-CIP devices such as printers or scanners, vision systems. Using MSG instructions in RSLogix
5000 software, programs can create, open, and close socket connections with other devices, assuming they have detailed information on how to
communicate to the device. Communication modules that support sockets include 1756 -EWEB and 1768-EWEB, with a 500-byte maximum per data packet
and a maximum of 20 connections, and 1756-EN2x ,1756-EN3TR, and CompactLogix 5730 series controllers, with a 3900-byte maximum per data packet
and a maximum of 32 connections. There are four types of socket connections: UDP Socket (sending and receiving UDP datagrams), TCP Client (RSLogix
5000 software initiates a TCP connection to another device), TCP Server (other devices initiate a TCP connection to RSLogix 5000 software), and TCP
Listen Connection (listens on a specified port for incoming connections).
Automatic Device Configuration for Drives
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
Catalog Numbers 1789-L10, 1789-L30, 1789-L60
This feature supports the automatic device replacement functionality for drives. This makes it easier to perform quick, efficient drive replacement without
requiring any laptop, software, or user intervention aside from wiring in the new drive and setting a network address. Previously, device configuration data
for PowerFlex® drives was kept in the ACD file and had to be manually managed via the AOP of the device. Now, when a module is replaced, the controller
will automatically send last known configuration resident in the controller to the configuration data. Always supported by Sercos and CIP motion drives.
Version 20 extends ADC support to the PowerFlex 755 drives.
Change Detection
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT

When online with a controller, a 64-bit integer is displayed in the Audit Value dialog box, located on the Security tab of the Controller Properties dialog box.
This Audit Value changes every time an event listed in the Changes To Detect configuration dialog box occurs. By inspecting this value, you can quickly
determine if the behavior of a controller has been modified since the last time it was inspected. The Audit Value can be accessed programmatically via the
GSV and MSG instructions, and the Changes to Detect value can be read or written via the GSV, SSV, and MSG instructions. The Change Detection Audit
Value is also exposed as a predefined tag by RSLinx Enterprise software for use in HMI displays or other applications. Additionally, it is included in every
entry of the Controller Log. For more information, see the ControlLogix System User Manual, publication 1756-UM001.
Electronic Data Sheet AOP
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
SoftLogix 5800 Vesion 20.00.00
This feature allows select devices that have properly configured EDS sheets to integrate directly with Logix without the need for a device profile.
This improves the flexibility of the Integrated Architecture by providing a richer integrated experience to more devices.
Logix Tree, Enhancements to Finding-Adding Devices
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
Catalog Number 1769-L16ER-BB1B, 1769-L18ER-BB1B, 1769-L18ERM-BB1B, 1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B,1769-
Enhancements to the Select Module dialog box make it easier to use and find devices. The Select Module dialog box now shows all registered devices. It
also includes new string and category filters, a wildcard search, and a favorites list.
Interpolated Actual Position Acceleration Compensation
System Feature
1756-L74, 1756-L75, 1756-L72S,1756-L73S, 1756-L73XT, 1756-L73SXT
Interpolated axis positions returned by the motion planner when queried now compensate for axis acceleration. This improves the accuracy of the
interpolated position by accounting for axis acceleration.
Support for Unicast Connections to Safety I/O Modules
System Feature
Cat. No. Available As Of
1768-L43, 1768-L43S, 1768- Firmware Revision 20.011/RSLogix 5000 Software
L45, 1768-L45S 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.
System Requirements
This release has the following system requirements.
Hardware Requirements v20
System Requirements
RSLogix 5000 Software 20.x
The personal computer must meet these minimum requirements. Using a computer meeting the recommended characteristics will improve performance.
Characteristic Minimum Required Recommended
Processor Pentium 4 Intel Core i5

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

Installation Notes
Review these notes before attempting to install this version of the RSLogix 5000 software.
Prior to Installation
Keep the following considerations in mind before you install the RSLogix 5000 software:
· Be certain that no copies of RSLogix 5000 software are currently running.
· Make sure that you have Administrator privileges on the personal computer on which you want to install the software. You will not be able to complete the
installation without these privileges.
· If you want to perform online communications, you must install RSLinx Classic software in addition to RSLogix 5000 software.
· Close all other applications before running the setup process.
· Ensure that there are no pending workstation reboot requests from either Windows Update or any installation program. If there is a pending request,
reboot the workstation before starting the RSLogix 5000 installation.
· Refer to the Choosing Your RSLogix 5000 Package section of this document to determine which controllers are supported by your RSLogix 5000
Enterprise Series bundle.
Installing the Software
Follow these steps to install RSLogix 5000 software.
1. Start your personal computer.
2. Insert the RSLogix 5000 installation DVD into your DVD-ROM drive.
The DVD-ROM should auto-start. If it does not auto-start, run Setup.exe from the root of the DVD.
RSLogix 5000 Enterprise Series software supports multiple versions of the programming software on a single personal computer. With RSLogix 5000
software version 10 and later, you may install as many of the later major versions as needed plus one version earlier than version 10 (for example, version
8.02).
3. Follow the directions that appear on your screen.
Note that RSLogix 5000 software version 20 may need to update several system files early in the installation process. These updates will likely require you to
restart your personal computer. Be sure to close all other applications before clicking OK to initiate this reboot.
When prompted for a serial number, enter the 10-digit serial number identifying your software license; otherwise, enter any sequence of characters, not
longer than 10 characters. Use the F1 key if you need help.
Important: The 10-digit serial number is used to determine what functionality to enable while in Grace Period mode. Entering an invalid serial number will
result in the software operating in Service Edition mode, upload/download only, while in Grace Period mode.
4. When prompted, click Yes to complete the activation of the software.
5. Follow the directions that appear on your screen and refer to the FactoryTalk Activation insert for additional information.
Important: When a valid activation cannot be located by the software, the software will enter a seven-day activation grace period, during which you will be
able to run the software with full functionality. If this seven-day grace period ends before a valid activation has been found, you will no longer be able to start
the RSLogix 5000 software.
6. Click Finish to complete the installation.
When the setup utility finishes, an entry for the RSLogix 5000 application program appears in the program list in the Rockwell Software group.
7. Remove the RSLogix 5000 DVD from the DVD-ROM drive and store it in a safe place.
Starting 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:
· Do you have the correct version of RSLinx Classic software installed? RSLinx Classic software provides communication between the controller and your
personal computer.
· Does your computer have enough memory? Running RSLogix 5000 software requires a minimum of 512 MB of RAM.
Uninstalling the Software
Follow these steps to uninstall the software when using the default Start menu on the Windows 7, Windows Vista, Windows XP, Windows Server 2003, or
Windows Server 2008 operating system.
1. From the Start menu, navigate to the Control Panel.
2. From the Programs category, choose Uninstall a program. (for Windows 7, Windows Server 2008 R2)
- From the Programs category, choose Uninstall a program. (for Windows Vista, Windows Server 2008 – Control Panel Home)
- Double-click Programs and Features. (for Windows Vista, Windows Server 2008 – Classic View)
- Double-click Add or Remove Programs. (for Windows XP, Windows Server 2003 R2 SP2 – Classic View)
- Click Add or Remove Programs. (for Windows XP, Windows Server 2003 R2 SP2 – Category View)
3. From this dialog box, double-click RSLogix 5000 <version>.
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 v20
System Requirements

FactoryTalk Services Platform 2.50 or later is not required to run RSLogix 5000 software; however it is required in order to perform some security
functions in RSLogix 5000 software.
RSLinx Classic communication software is not required to install RSLogix 5000 software; however it is required in order to perform online
communication with controllers.
FactoryTalk View SE (CPR 9) software and RSLinx Enterprise communication software are not required to install RSLogix 5000 software; however
these products are required in order to fully use the alarm capabilities introduced with version 16.
Be sure to check the software requirements for other Rockwell Software products that you intend to install to be sure that these products are also
compatible with the system.

Software Requirements v20.04
System Requirements
RSLogix 5000 Software 20.04
Operating system and service pack compatibility:
This version of RSLogix 5000 software has been tested on the following operating systems:
Microsoft Windows 7 Professional (64-bit) with Service Pack 1
Microsoft Windows 7 Home Premium (64-bit) with Service Pack 1
Microsoft Windows 7 Home Premium (32-bit) with Service Pack 1
Microsoft Windows Vista Business (32-bit) with Service Pack 2
Microsoft Windows XP Professional with Service Pack 3
Microsoft Windows Server 2003 R2 Standard Edition with Service Pack 1
Microsoft Windows Server 2008 Standard Edition with Service Pack 2
Microsoft Windows Server 2003 R2 Standard Edition with Service Pack 2
Important: Windows XP Professional with Service Pack 3 and Windows Server 2003 R2 Standard Edition Service Pack 2 require a hotfix from Microsoft to
enable SHA2 certification support.
https://support.microsoft.com/en-us/kb/968730.
This version of RSLogix 5000 software is expected to operate correctly on all other editions and service packs of the following operating systems, but has
not been tested:
Microsoft Windows 7
Microsoft Windows Vista
Microsoft Windows XP (Service Pack 3 or higher)
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008
For operating systems that support User Account Control (UAC), this version of RSLogix 5000 software was tested with UAC set to the most restrictive level
(“Always notify” for Windows 7, or “On” for Vista). This version of RSLogix 5000 software is also expected to operate correctly when UAC is configured for
any less restrictive setting.
RSLogix 5000 software versions earlier than version 19 are not supported on Microsoft Windows 7 operating systems at this time and have not been tested
on those operating systems.
RSLogix 5000 software versions earlier than version 17 are not supported on Microsoft Windows Vista operating systems at this time and have not been
tested on those operating systems. RSLogix 5000 software version 17 is supported on a Microsoft Windows Vista operating system only when User Account
Control (UAC) is turned off.
Running RSLogix 5000 software in conjunction with Fast-User Switching is not supported. Running RSLogix 5000 software in Safe mode is not supported.
Running RSLogix 5000 software via Remote Desktop is not supported.

Corrected Anomalies
This release corrects the following anomalies.
Program-Scope Tag Alias to Controller-Scope Tag (x01858)
Corrected Anomaly
The Tag Editor will no longer allow you to create a program-scope alias to a controller-scope tag of the same name. If you created projects with this condition
in previous releases, they will convert successfully to V9.00, but the controller will fail to upload with the error message “Failed to resolve tag target”. To work
around this problem, you can do either of the following things:
While online to the controller, change the name of all the program-scoped tags which alias a controller-scoped tag with the same name to something
(slightly) different and then upload, or
Save the project as an .L5K file (export) and open the .L5K file (import), which will cause the program-scoped tags to become unverified. Delete the
program scope tags that are now unverified which will cause the instructions that used the program-scoped tags to re-bind to the controller-scoped
tags with the same name. Finally, download the project to the controller.
Project Re-Verification (x33403)
Corrected Anomaly
If you perform an operation that requires re-verification of the entire project (e.g. changing the controller type, compacting the database,
or importing) the operation will complete successfully but may take an extended amount of time. Projects with FBD routines with large
blocks (many visible parameters) and numerous input and output references are particularly sensitive to this re-verification time. The
amount of time will vary depending on the complexity and size of the project. (x33403)
Project Re-Verification Operations (x33403)
Corrected Anomaly
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.
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.
SFC Wire Routing in Sequence Loops (x28417)
Corrected Anomaly
In some SFC charts involving sequence loops, the automatic routing of wires may result in the wire passing through the SFC element(s). In order to correct
this wiring problem try these recommendations:
If a wire passes through an element, move the element to the left or right a few grid spaces. Do not move the branch.
Move another element connected to the wire the opposite direction a few grid spaces. This will route the wires such that they will be visible.
Move elements that are wired to each other into a more vertical alignment. This will adjust the wire paths.
Move a branch vertically to a different position, to lengthen the vertical distance between elements.
Jog elements right or left a grid unit at a time to straighten out crooked lines.
Save your project.
Slow response over VPN Ethernet connection (x145123)
The software is slow when it is communicating with a controller over a VPN Ethernet connection.
A fatal error when Parameter tab is opened (x144803)
Under certain conditions, a fatal error occurs when the Parameter tab is opened in the EDS AOP.
Absolute feedback devices cannot be changed to Incremental (x133547)
The Startup Method on the Axis Properties dialog box cannot be changed to Incremental for Absolute feedback devices.

Communication error reported when uploading/downloading file (x132451)
RSNetWorx for DeviceNet reports a communication error when uploading/download a file to a DeviceLogix device in RSLogix 5000 software.
Copying Instructions To V20 From Earlier Version (x119309)
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.
Cross reference fails to go to referenced location in protected routine (x144398, x159396, x167856)
The Cross Reference dialog box fails to navigate to the referenced location when the routine is protected with the viewable option.
Download Fails with Communication Time-out (x01853)
Corrected Anomaly
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.
Drive faults with an Excessive Position Error fault (x152784)
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.
Failure to modify the RPI of a consumed tag (x03204)
Corrected Anomaly
First Identified as of RSLogix 5000 20.x
While attempting to modify the RPI of a consumed tag, the following error sometimes appears: "Failed to modify the properties for the tag '<consumed tag
name>'. Couldn't be found." To work around this anomaly, save the project as an .L5K file, then reopen the .L5K file.
GDI object leak (x141635)
Graphic device interface (GDI) object leaks occur when expanding the Scope list on the Cross-Reference dialog box and Tag Editor.

Incorrect location information in diagnostic message (x148434)
RSLogix 5000 software logs the wrong location information in the diagnostic message when using a remote session in a terminal services environment.
Inhibit Module yields unexpected results (x139052)
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.
Instances going online for first time failing (x06178, x06022)
Corrected Anomaly
First Identified as of RSLogix 5000 Version 20.x
There are intermittent issues with attempts to go online after power-cycling the controller chassis or stopping and starting RSLinx that sometimes causes a
first time failure. Immediate subsequent attempts will succeed.
Startup delay when no access to internet (x149691)
A long delay or timeout occurs in the software startup when the computer does not have internet access.
Unable to flash firmware with software (x169634)
Unable to use RSLogix 5000 software to flash firmware if the controller contains a new license.

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.
Uploading Controllers with Multiple Aliases (x03160, x07909, CR169)
Corrected Anomaly
Caution should be used in developing applications that utilize multiple aliases to the same base tag. When such an application is uploaded, the alias may
replace base tag operands in the ladder logic. The aliases are alphabetized internally on upload so the replacement operand will be the first alphabetical
name.
Known Anomalies
This release has the following known anomalies.
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.
Miscellaneous Known Anomalies V20
Anomaly
Logix Firmware/RSLogix 5000 Software 20.x

Import of a Project to Controller with Expansion I/O May Not Update Logic that References that I/O
RSLogix 5000 Software No Longer Functioning after Inhibit of Module in Unlocked Instance
Operands Missing After Copy and Paste or Drag and Drop of MDSC Related Motion Instructions to Version 20
Partial Import Online of S-Curve Function Block May Execute with Uninitialized Values
Major Non-Recoverable Fault Removing Alarm Message Tag Association While Online
Failure to Modify the RPI of a Consumed Tag
Instances of Going Online for the First Time Failing
Module: Modify Properties (x72088)
Anomaly
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.
Motion: Modify Configuration (x55583)
Anomaly
With the security action “Motion: Modify Configuration” not granted, you should be prevented from modifying motion configuration. You are prevented from
changing axis association to a module from the Axis Properties dialog but are erroneously allowed to make this change from the Module Properties dialog.
To secure the axis association configuration on the Module Properties dialog, deny access for the security action “Module: Modify Properties”. This will
secure all of the tabs of the Module Properties dialog, including the Axis Association tab.
Navigating Off Table (x103461)
Anomaly
RSLogix 5000 18.x
The RSLogix 5000 application may report a Fatal Error if you click the mouse outside of the RSLogix 5000 application when editing the values in a table on a
configuration tab for some Add-On Profiles. This problem is not observed when the operating system is configured to use the 'Windows Classic' theme. To
avoid this anomaly when the operating system is not configured with the 'Windows Classic' theme, switch to another tab or close the Module Properties
dialog box before navigating to another application.
Note that the Online Help window is treated as an application separate from RSLogix 5000 software. Pressing F1 to display Online Help while editing values
in an Add-On Profile table may result in this Fatal Error. You can use the Help button on the Module Properties dialog box to avoid this error when displaying
Online Help. This anomaly will be corrected with future releases of the Add-On Profiles that exhibit this behavior. For Add-On Profiles installed with version
18.00 of RSLogix 5000 software, the behavior is exhibited by some of the profiles in the following categories: 1732 and 1791 Safety I/O profiles, 1769
Compact I/O profiles, and 1783 profiles. Profiles distributed by vendors other than Rockwell Automation may also exhibit this behavior.
New EDS File Not Displayed (x124959)
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.
Online correlation failure (x06034)
Anomaly
When making online changes to ladder logic, you are limited to accepting changes to 1000 rungs at one time. If you attempt to accept pending edits for
more than 1000 rungs, RSLogix 5000 will display an error "Failed to correlate the project with a change in the controller. RSLogix 5000 has been taken
offline." You can avoid this problem by accepting pending rung edits before the 1000 rung limit is reached.
Opening Trend Chart Properties (x26487)
Anomaly
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%.
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.
Operands Missing V17 (x80000)
Anomaly
Additional operands are required for the MCLM, MCCM, MCCD, and MCS Coordinated Motion instructions in Structured Text as part of the Multi-Axis
Programmable Jerk feature introduced in version 17 of RSLogix 5000 software. When porting any of these instructions to version 17 from an earlier version
of RSLogix 5000 software using copy and paste or drag and drop, the new operands are not automatically inserted This results in instructions that will not
verify. When this occurs, it is necessary to make the appropriate corrections to the pasted instruction. Note that this anomaly does not exist for converted or
imported projects. A suitable work-around for Structured Text instructions may be to use Routine Copy of Structured Text.
Output Cam Execution Targets (x25982)
Anomaly
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.
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.
Remote CompactLogix Controller (x72948)
Anomaly
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.
RSLogix 5000 Software Unresponsive (x129306)
Anomaly
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.
RSNetWorx Software Cannot Download to Controller (x124236)
Anomaly
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.
SERCOS Ring Phase Up (x43750, x43870, x44775)
Anomaly
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.
Slow Launch Times (x125369)
Anomaly
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
SoftLogix SSV Instruction (x59117)
Anomaly
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.)
"Log On to FactoryTalk" Displayed (x124955)
Anomaly
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:
Launch the FactoryTalk Administration Console (available from the Start menu).
Select the Network directory when prompted. (You may need to provide credentials for a user with Administrator privileges in order to continue.)
To allow access for a particular user, navigate to "Network\System\Users and Groups\Users", right-click the Users folder, and choose "New>Windows
Linked User". Then click Add and provide the domain\logon name for the desired user. (You can click Check Names to verify that the name was
found.)
To allow access for all authenticated users, navigate to "Network\System\Users and Groups\User Groups", right-click the User Groups folder, and
choose "New>Windows Linked User Group". Then click Add and type the name of the user group "authenticated users".
The "Log On to FactoryTalk" dialog 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".)
Associated Tag, Non-Recoverable (x77626)
Anomaly
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.
Corrected
Blank Primary Window (x39239)
Anomaly
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.
CIP-Axis effective resolution can get negative number (x136012)
Known Anomaly
On CIP-axis:
Motor Source=NamePlate
Motor_Feedback: select [Hiperface]
the associated Feedback attributes, (in Offline Configuration of Feedback Device) are:
Cycle Resolution: [ ]
Cycle Interpolation: [ ]
Calculate'd Effective Resolution: [ ]
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)
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.
DF1 Master/Slave Network (x08157)
Anomaly
Programming over a DF1 Master/Slave network is not currently supported in RSLogix 5000.
DH485 Message Size Limit (x20920)
Anomaly
Messages sent over a DH485 network are limited to a size of 240 bytes. This limitation is to prevent certain SLC, operator interface, and other third party
devices that cannot handle larger messages from generating communication errors.
DH485 Protocol (x25526)
Anomaly
The RSLogix 5000 software will allow you to configure the System Protocol for DH485 and a Serial Port baud rate of 38,400. However the protocol does not
support this baud rate and the serial port will not operate correctly if configured this way. Choose a baud rate of 19,200 or less when using the DH485
protocol.
Emulated Controller, Select Slot 0(x79666)
Anomaly
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.
Tip: If you change the slot position of the emulator controller on the Controller Properties dialog box to a slot position other than slot 0, you cannot later
return the slot position to 0 on the Controller Properties dialog box. To obtain these results, you must repeat the steps defined above. This also applies if
you convert from a physical controller to an emulated controller.
FBD Routine Pending Edits (x43429, x41415)
Anomaly
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.
GDI Object Leaks, Child Windows (x66929)
Anomaly
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.
GDI Objects Exceed OS Limit (x48079)
Anomaly
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.
Hardware Overtravel Fault (x66998)
Anomaly
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?"
Inserting Unicode Characters (x59649, x59650, x59825)
Anomaly
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.
Logging Messages to RSMACC/RSAudit (x55161)
Anomaly
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.
Structured Text, Editor (x33122)
Anomaly
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.
Structured Text, Project Component References (x32846)
Anomaly
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.
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.)
Unicode Characters, Does Not Display (x63773)
Anomaly
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.
User-Defined Data Type Size Limits (x03090, x06296)
Anomaly
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.
Windows 7 Operating Systems (x111504, x113166, v124864)
Anomaly
RSLogix 5000 19.x
There are a number of issues related to compatibility of RSLogix 5000 software with the Windows 7 operating system. The most significant of these includes
the following:
Although RSLogix 5000 software versions earlier than version 19 can be installed, they are not supported on Windows 7 operating systems. Also note
that some applications and tools cannot be installed on a 64-bit Windows 7 operating system. Most notably, RSLogix 5000 software version 12 and
earlier cannot be installed on a 64-bit Windows 7 operating system.
On some properties dialog boxes, there is no indicator shown when a control has focus. A workaround to display focus indicators is to select the
Windows 7 setting to 'Underline keyboard shortcuts and access keys'. Access this setting by using Personalize>Ease of Access Center>Make the
keyboard easier to use>Underline keyboard shortcuts and access keys. (x113166)
The RSLogix 5000 Clock Update tool does not work properly when it is installed on a 64-bit Windows 7 operating system and executed. (x124864)
Windows Vista Operating System (x81660)
Anomaly
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:
0. Although RSLogix 5000 software versions earlier than version 17 can be installed, they are not supported on Windows Vista operating systems.
1. Although RSLogix 5000 software version 18 is supported with User Account Control (UAC) turned on, RSLogix 5000 software version 17 is supported
only with UAC turned off.
2. On some properties dialog boxes, there is no indicator shown when a control has focus. A workaround to display focus indicators is to select the
Windows Vista setting to ‘Underline keyboard shortcuts and access keys’. Access this setting by using Personalize>Ease of Access>Make the
keyboard easier to use>Underline keyboard shortcuts and access keys. (x113166)
3. The 1784-PCIC(S) driver must be at version 4.06.01 or later. This driver is installed when RSLinx software is installed.

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)
Functional Changes
This release has the following functional changes from the previous release.
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
A new checkbox prevents the Safety Signature from being deleted while the controller is in Run Mode.
Enabling Security for RSLogix 5000 Software
Starting with version 20 of RSLogix 5000 software, security is automatically enabled when FactoryTalk Services Platform software is installed. Installation of
RSSecurity Emulator software and execution of the SetSecKeys.exe utility are no longer required. Also starting with version 20 of RSLogix 5000, security
permissions are obtained exclusively from the FactoryTalk network directory. Note that RSLogix 5000 software versions 19 and earlier still require installation
of RSSecurity Emulator software and execution of the SetSecKeys.exe utility. RSLogix 5000 software versions 19 and earlier can obtain security permissions
from either the Local or Network directory, as configured when RSSecurity Emulator software is installed.
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.

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 Which comes from this
project type of memory
Component Increase/Decrease I/O Data and Safety

Per Instance Logic
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 -76 bytes X
ALARM_ANALOG or ALARM_DIGITAL
data type
Tag that uses ALARM_ANALOG + 4 bytes X
data type
Tag that uses ALARM_DIGITAL + 24 bytes X
data type
Tag that uses MOTION_GROUP + 56 bytes X
data type
Tag that uses + 950 bytes X
COORDINATE_SYSTEM data type
Tag that uses AXIS_CIP_DRIVE + 676 bytes X
data type
Tag that uses AXIS data type other + 672 bytes X
than
AXIS_CIP_DRIVE
Standard produced tag + 4 bytes + (4 bytes X
x number of
consumers)
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-L6xS controller + 1316 bytes X
1768-L4x, 1768-L4xS controller + 1212 bytes X
1769-L23 controller + 2488 bytes X
1769-L31 controller + 2492 bytes X
1769-L32C, 1769-L35CR + 2812 bytes X
controller
1769-L33E, 1769-L35E controller + 2496 bytes X
Then add the following memory requirements to your Which comes
project from this type
of memory
Component Increase/Decrease I/O Data and

Per Instance Logic
NA <no change>
of memory

Per Instance Logic
Program + 8 bytes X
Add-On Instruction + 12 bytes X
Each tag
+ 4 bytes X
In addition, if you use a tag of the types
listed below, increase the memory as
indicated for each instance:
Produced tag + 36 bytes + (24 X
bytes * number of
consumers)
Consumed tag + 24 bytes X
Data access control + 4 bytes per X
symbol
Tag that uses ALARM_ANALOG data - 20 bytes X
type
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 + 786 bytes X
AXIS_GENERIC_DRIVE data type
Tag that uses AXIS data type other than + 818 bytes X
AXIS_SERVO_DRIVE or
AXIS_GENERIC_DRIVE
Tag that uses COORDINATE_SYSTEM + 40 bytes X
data type with no transform dimensions
data type with transform dimensions
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
of memory

Per Instance Logic
Task + 4 bytes X
Program + 4 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 X
* number of
consumers)]
Tag that uses MESSAGE data type + 4 bytes X
Tag that uses ALARM_ANALOG data - 64 bytes X
type
Tag that uses ALARM_DIGITAL data type - 28 bytes X
- 34 bytes
Tag that uses AXIS_SERVO_DRIVE or X
AXIS_GENERIC_DRIVE data type (2 bytes x number of
output cam
execution targets)
- 52 bytes
Tag that uses AXIS data type other than X
AXIS_SERVO_DRIVE or (2 bytes x number of
AXIS_GENERIC_DRIVE output cam
execution targets)
data type of 2 dimensions with 2
transform dimensions
data type of 3 dimensions with 3
transform dimensions
of memory

Per Instance Logic
each instance:
Tag that uses ALARM_ANALOG data + 16 bytes X
type (with no associated tag references)
Tag that uses ALARM_DIGITAL data type + 4 bytes X
(with no associated tag references)
+ 22 bytes
Tag that uses ALARM_ANALOG data X
type (if associated tags are configured for + (9 x the number of
the ALARM_ANALOG tag) 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
Tag that uses the + 132 bytes X
COORDINATE_SYSTEM data type
of memory

Per Instance Logic
Input module + 4 bytes X
each instance:
Produced tag + 12 bytes X
data type
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
of memory

Per Instance Logic
each instance:
Tag that uses the COORDINATE + 60 bytes X
SYSTEM data type
Tag that uses any AXIS data type + 4 bytes X
project from this type of
memory

Per Instance Logic
Task + 4 bytes X
User-defined data type + 4 bytes X
X X
I/O module + 16 bytes
(8 bytes) (8 bytes)
each instance:
Produced tag + 8 bytes X
of memory

Per Instance Logic
I/O module with a comm format = Rack + 90 bytes X
Optimization
I/O module with a comm format = + 144 bytes X
something other than Rack Optimization
(such as a direct connection)
CompactLogix 1769 I/O module + 170 bytes X
Bridge module with a comm format = + 160 bytes X
None
Bridge module with a comm format = + 220 bytes X
Rack Optimization
of memory

Per Instance Logic
User-defined data type
Number of user-defined data types + 128 bytes X
in the controller organizer > Data
Types folder > User-Defined folder
Not the use of that data type in tags
Indirect address (using a tag as the
subscript for an array in an instruction, - 60 bytes X
such as an Array_A[Tag_B]). This
memory change applies only if the array:
uses a structure as its data type
does not use one of these data
types: CONTROL, COUNTER, PID,
or TIMER
has only one dimension (such as
UDT_1[5])
of memory

Per Instance Logic
of memory

Per Instance Logic
each instance:
Tag that uses the MESSAGE data type + 376 bytes X
of memory

Per Instance Logic
Project + 1050 bytes X
Tag + 0.55 bytes X
Message that transfers more than
500 bytes of data and targets a controller + 2000 bytes X
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
of memory

Per Instance Logic
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
of memory

Per Instance Logic
Application Notes
This release has the following application notes.
Application Notes RSLinx Software v20
Data Access Control Compatibility with RSLinx Software
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/).
Configuring the Ethernet Port on a CompactLogix5532E Controller
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).
RSLinx Classic Software Professional Activation
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).
Configuring Drivers for the 1756-ENET, 1756-ENBT, and 1756-EWEB Modules
You configure a driver for communicating from the workstation through the 1756-ENET, 1756-ENBT, or 1756-EWEB module by selecting ‘Configure Drivers
...’ from the RSLinx ‘Communications’ menu. In the dialog box, select ‘Ethernet devices’ in the list of available driver types and click on the ‘Add New’ button.
0. In the Station Mappings, click Add New to add a new mapping line if needed.
0. Enter the IP address of the Ethernet module in the Host Name field. If your network has host name resolution capability, you can use the host name
instead of the IP address
0. You can put up to 63 devices in the configuration of a single Ethernet devices driver.
If you are using RSLinx software version 2.40 or later, you can use the EtherNet/IP driver. This driver will automatically browse for all EtherNet/IP-capable
devices on the local or configured remote subnet. See RSLinx online help for information on this driver. Note that 1756-ENET/A and 1756-ENET/B modules
will not respond to the browse commands. You must use a different driver for these modules.
Configuring DF1 Drivers
For DF1 point-to-point communications, choose ‘RS232 DF1 Devices’ from the list of available drivers in RSLinx software. Then choose ‘Logix5550 Serial
Port’ for DeviceType. 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.
Offline Tag and UDT Changes Downloaded to the Controller may Cause RSLinx Software (version 2.x) to Halt Communications
RSLinx software maintains knowledge of the memory layout of a Logix5000 controller in order to optimize the data access performance when accessing the
data in these controllers. However, changes made to an offline project that are then downloaded can result in RSLinx software attempting to access tag
information that is no longer present. When this occurs, RSLinx software halts the communications to the controller. To recover, both RSLinx software and
the software requesting tags from RSLinx software must be restarted. To avoid this anomaly, use caution when making offline changes to a project and then
downloading to a Logix5000 controller. In particular, changing the size of an array if elements of the array are already on scan, renaming a structure or a
member of a user-defined data type used by a tag that is on scan, or changing the data type of a tag on scan from a larger size to a smaller size (for
example, changing a DINT to a SINT). Note that RSLinx Enterprise Series software is able to accommodate these changes without requiring a restart.
Third-party Software with RSLogix 5000 Software
Data Access Control Compatibility with Third-party Software
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/).

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

02 Labelpoint Programmer S Reference Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 Labelpoint Programmer S Reference Manual

Uploaded by

Copyright:

Available Formats

Release Notes

Characteristic Minimum Required Recommended

Processor Pentium 4 Intel Core i5

Component Increase/Decrease I/O Data and Safety

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

Component Increase/Decrease I/O Data and

You might also like