Hardware Requirements v20

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

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

Software Requirements Product Considerations v20

• 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

Operating system and service pack compatibility:

• 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

• Microsoft Windows 7
• Microsoft Windows Vista
• Microsoft Windows XP (Service Pack 3 or higher)
• Microsoft Windows Server 2008 R2
• Microsoft Windows Server 2008

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.

MDSC – Master Driven Speed Control

System Feature

Logix Firmware/RSLogix 5000 Software 20.011

QuickConnect – EtherNet/IP Devices

System Feature

Logix Firmware/RSLogix 5000 Software 20.011

System Feature

Logix Firmware/RSLogix 5000 Software 20.011

Interpolated Actual Position Acceleration Compensation

System Feature

Logix Firmware/RSLogix 5000 Software 20.011

Change Detection

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.

Support for Unicast Connections to Safety I/O Modules

System Feature

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.

Logix Tree, Enhancements to Finding-Adding Devices

System Feature

Logix Firmware/RSLogix 5000 Software 20.011

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

Socket Connections

System Feature

Logix Firmware/RSLogix 5000 Software 20.011

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/).

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.

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.

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,

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.

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.

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.

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.  

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.

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.

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.

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.

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.

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.

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.

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.

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. 

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.

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

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.

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.

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.

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.

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.

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?"

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.

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:

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.

Operands Missing V17 (x80000)

Anomaly

First identified in RSLogix 5000 Software 17.x

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.

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

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)

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.

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

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. 

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.

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.

"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:

• 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".)

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.

Miscellaneous Known Anomalies V20

• 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

Corrected Anomaly with Studio 5000 Logix Designer 24.01

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)

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. 

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

If you upgrade from 18.x to 19.x

If you upgrade from 17.x to 18.x

If you upgrade from 16.x to 17.x

If you upgrade from 15.x to 16.x

If you upgrade from 14.x to 15.x

If you upgrade from 13.x to 14.x

If you upgrade from 12.x to 13.x

If you upgrade from 11.x to 12.x

If you upgrade from 10.x to 11.x

If you upgrade from 9.x to 10.x

If you upgrade from 8.x to 9.x

If you upgrade from 7.x to 8.x

If you upgrade from 6.x to 7.x

If you upgrade from 5.x to 6.x

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.

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.

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.

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.

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.

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 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:

• The controller is at firmware revisions 18, 19, or 1.008.
• You are using a personal computer with a 64-bit operating system (such as Windows 7 64-bit operating system).

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.

* 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:

• RSLogix 5000 Full Access
• RSLogix 5000 Maintain Project
• RSLogix 5000 Go Online
• RSLogix 5000 View Project

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:

• Two Logix5000 revision 16 firmware controllers connected to one POINT output module. One controller connected as an owner. The other controller connected as a listener.
• Two Logix5000 controllers connected to one POINT output module. One controller is at Logix5000 revision 16. The other controller is at Logix5000 firmware revision 15 or earlier.

The required firmware for the 1734-AENT module is revision 2.003.4 or later, and the required firmware for the 1738-AENT module is revision 2.003.4 or later.

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:

• -3.40282347E38 to -1.17549435E-38 (negative values)
• 0
• 1.17549435E-38 to 3.40282347E38 (positive values)

The REAL data type also stores ±infinity, ±NAN, and -IND, but the software display differs based on the display format.

The software also stores and displays the IEEE subnormal range:

• -1.17549421E-38 to -1.40129846E-45 (negative values)
• 1.40129846E-45 to 1.17549421E-38 (positive values)

RSLogix 5000 Software 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)

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