Hardware Requirements v18

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

as Start Page Media, Online Books, or RSLinx) must be uninstalled separately.

Software Requirements Product Considerations v18

0. RSLinx Classic communication software is not required to install RSLogix 5000 software; however it is required in order to perform online communication with controllers.
1. RSLinx Enterprise communication software is not required to install RSLogix 5000 software; however it is required in order to perform alarm notifications using the Logix ALMD and ALMA instructions that were introduced with version 16.00.
2. FactoryTalk View SE (CPR 9) software is not required to install RSLogix 5000 software; however this product is required in order to fully use the alarm capabilities introduced with version 16.03.
3. Microsoft .NET Framework version 1.1 must be installed on the same computer on which RSLogix 5000 software will be installed for version 13.00 and later. This software is included as part of the RSLogix 5000 installation.
4. Microsoft .NET Framework version 2.0 must be installed on the same computer on which RSLogix 5000 software will be installed for version 17.00 and later. This software is included as part of the RSLogix 5000 installation.
5. 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 v18

Operating system and service pack compatibility:

0. This version of RSLogix 5000 software has been tested on the following operating systems:
1. Microsoft Windows Vista Business with Service Pack 2 and User Account Control (UAC) turned on
2. Microsoft Windows XP Professional with Service Packs 3
3. Microsoft Windows Server 2003 R2 Standard Edition with Service Pack 2
4. Microsoft Windows Server 2008 Standard Edition with Service Pack 2
5. 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:
6. Microsoft Windows Vista
7. Microsoft Windows XP
8. Microsoft Windows Server 2003
9. Microsoft Windows Server 2008

Data Access Control

System Feature

Firmware Revision/ Software Version 18.11

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65

Two new tag attributes are available: the External Access and Constant attributes. The External Access attribute defines how an external application (that is, an application outside of RSLogix 5000 software or your application code), such as an HMI, historian, or OPC data server, can access a tag. Options you can configure for the External Access attribute include:

• Read/Write
• Read Only
• None

The Constant attribute is used to keep the tag from being altered by the controller program or by specified users of RSLogix 5000 software. To keep the program from altering the tag, check the Constant attribute in the Tag Properties dialog box or in the Tag Editor.

For more information about tag data access attributes, see the Logix5000 Controllers I/O and Tag Data Programming Manual, publication 1756-PM004.

CIP Motion Using EtherNet/IP Networks

System Feature

Firmware Revision/ Software Version 18.11

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65

Integrated Motion support over the EtherNet/IP network lets you connect ControlLogix and GuardLogix controllers to Kinetix 6500 drives by using ControlLogix EtherNet/IP modules and standard Ethernet media to use Integrated Motion.

In addition to support for the EtherNet/IP network connections, the CIP Motion Axis Properties Category pages and the Motion Database in RSLogix 5000 programming software let you configure the drives and associated components.

Integrated Motion on the EtherNet/IP network features includes the following:

• Integration of Kinetix 6500 drives, I/O, Electronic Operator Interface (EOI) devices, and any other EtherNet/IP module on a common ControlLogix EtherNet/IP module, for example, 1756-EN2F, 1756-EN2T, and 1756-EN2TR modules.

When using CIP Motion, the EtherNet/IP modules (catalog numbers 1756-EN2T, 1756-EN2TF, 1756-EN2TR and 1756-EN3TR) connected to Kinetix 6500 drives must be configured so that the Time Sync Connection parameter, on the Module Definition screen, is configured to be Time Sync and Motion.

This integration includes common programming, configuration, commissioning, and drive maintenance tools

• No need to add SERCOS interface modules for drive control
• Improved axis/drive configuration, commissioning, and diagnostic tools
• Support for any Ethernet topology including STAR, Linear, or Device-level Ring (DLR) networks

A new, predefined Axis type AXIS_CIP_DRIVE has been added in version 18 to support the CIP Motion axis. All configuration of axis parameters and association of the axis to the newly supported Kinetix 6500 CIP Motion drives are performed by using the Axis Properties and Drive Properties of the CIP Motion axis. The CIP Motion axis and Kinetix 6500 EtherNet/IP interface drives are supported by using the 1756- EN2F, 1756-EN2T, 1756-EN2TR or 1756-EN3TR module, configured with Time Synchronization and Motion. CIP Motion uses Unicast control-to-drive communications over EtherNet/IP. A CIP Motion axis supports all existing Integrated Motion instructions with the exception of programmatic Tuning. CIP Motion also provides improved axis and drive configuration, commissioning, and diagnostic tools. For more information about EtherNet/IP-based CIP Motion, refer to the CIP Motion Configuration and Startup User Manual, publication LOGIX-UM003.

CIP Sync Time Coordination

System Feature

Firmware Revision/ Software Version 18.11

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65

Use CIP Sync Time Coordination to synchronize the wall clocks of multiple devices in the system. This is a time synchronization extension to CIP, based on and fully compliant with the IEEE-1588 Standard for a Precision Clock Synchronization Protocol for Network Measurement and Control Systems. This functionality is especially important in applications that provide time-stamped information, for example in applications with Alarms and Events, first-fault detection, data logging, and sequence-of-event operations (SOE). For more information about time synchronization using CIP Synchronized Time Coordination, refer to the Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003.

DF1 Radio Modem Broadcast Support

System Feature First Identified as of:

• Firmware Revision 18.011, 1769-L23E-QB1B, 1769-L23E-QBFC1B, 1769-L23-QBFC1B
• Firmware Revision 18.011, 1769-L31, 1769-L32E, 1769-L32C, 1769-L35E, 1769-L35CR
• Firmware Revision 18.011, 1768-L43, 1768-L45, 1768-L43S, 1768-L45S
• Firmware Revision 16.022, 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65

DF1 Radio Modem support has been expanded to include broadcast capability. The DF1 Radio Modem functionality was initially provided with revision 16. With this expansion to include broadcast capabilities, you can configure a master or slave device to broadcast messages to all other stations in one instance.

RPI Limitations and Negotiated Default for Multicast

System Feature

Firmware Revision/ Software Version 18.11

An RPI limit can be set for produced/consumed tags in applications where multicast communication connections are used. When this option is configured, a producing controller verifies that the RPI of incoming connections are within the produced tag settings. If the consuming tag's RPI falls outside the configured range, a producing controller will reject the incoming RPI and may provide an RPI (default) to the consuming controller. This feature is not available with safety produced/consumed tags.

For more information about RPI Limitations see the Produced and Consumed Tags Programming Manual, publication 1756-PM011.

Active Step Maintained During SFC Online Edit

System Feature

Firmware Revision/ Software Version 18.11

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-L63S, 1756-L63XT, 1756-L64, 1756-L65

Online edits to SFC routines do not always result in the SFC being reset to the initial step. Edits that alter the logic structure of the chart are the only edits that cause the SFC to reset to the initial step.

Add-On Instruction Enhancements

System Feature

Firmware/Software Revision 18

- Add-On Instruction execution performance has been improved when the instruction is scanning false and the EnableInFalse routine is not defined or has been disabled. Typically, an approximate factor of three improvements can be achieved.

- Default Values in an Add-On Instruction definition can be selectively propagated to all Add-On Instruction instances in a project.

- Access to Axis, Coordinate System, Motion Group, and Message tag information is available via GSV and SSV instructions within an Add-On Instruction.

- The GSV instruction can be used to programmatically retrieve key Add-On Instruction information, such as Change History, Revision, Vendor, Name, and Signature.

- The language type of the Logic routine can be changed without redefining the data definition.

- A local tag can be aliased to an Input or Output parameter.

- When Add-On Instruction parameters are added, moved, or modified, all instances of that Add-On Instruction will automatically be adjusted to keep operand tags assigned to the same parameters.

Corrected: RSLogix 5000 Software 18.01

Language Switching Feature, Removing Projects (x87118, x87182)

Anomaly

RSLogix 5000 Software 16.x

When using the Language Switching feature to remove all documentation for a particular language, warnings may be reported if access to any of the documentation is restricted. The text of these warning messages refers to line numbers in files that do not exist and can thus be ignored. The condition that caused the warning messages to be issued, however, is real, and the presence of the messages indicates an attempt to remove documentation whose access is in some way restricted. Among the reasons for this is documentation associated with components that are Secured, Source Protected, Safety Locked, or have a Safety Signature. In order to remove secured or protected components, you will need to first remove these restrictions.

DriveLogix "Major Fault On Controller..." Checkbox Display

Anomaly

RSLogix 5000 Software 16.x

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

Corrected: RSLogix 5000 Software 18.x

Results Window Not Docked (x92062, x95178)

Anomaly

RSLogix 5000 Software 17.x

Fatal Error closing RSLogix 5000 software or the Results windows when the Results window is not docked.

Corrected: RSLogix 5000 Software 18.x

Guard I/O Safety Module Profiles (x94870)

Anomaly

RSLogix 5000 Software 17.x

Guard I/O Safety module profiles may display offline module configuration data when online.

Corrected: RSLogix 5000 Software 18.x

Project Documentation Language Configuration (x93475)

Anomaly

RSLogix 5000 Software 17.x

Documentation imported by using the Project Documentation Language Configuration dialog box is sometimes converted to a single line.

Corrected: RSLogix 5000 Software 18.x

Cross Reference For A Task (x105511)

Anomaly

RSLogix 5000 Software 17.x

Cross Reference for a task does not show EVENT instructions.

Corrected: RSLogix 5000 Software 18.02

1769 Compact I/O Fault (x86275)

Anomaly

RSLogix 5000 Software 17.x

Corrected: RSLogix 5000 Software 18.x

Project Using SQR Function (x90619)

Anomaly

RSLogix 5000 Software 17.x

Fatal Error downloading or estimating memory for a project that uses the SQR function within an array index expression.

Corrected: RSLogix 5000 Software 18.x

Printing a Tag (x90726)

Anomaly

RSLogix 5000 Software 17.x

Fatal Error attempting to print a tag from the Watch Pane.

Corrected: RSLogix 5000 Software 18.x

AutoFlash (x96777)

Anomaly

RSLogix 5000 Software 17.x

AutoFlash lets you select incompatible revisions of firmware when flashing a 1768-L4x Series B controller.

Corrected: RSLogix 5000 Software 18.x

Language Switching Feature, Undo (x93270)

Anomaly

RSLogix 5000 Software 17.x

Unable to undo editing of rung comments when the Language Switching feature is used to make the edits in more than one language. After the failed attempt to undo the changes, subsequent operations may result in a Fatal Error.

Corrected: RSLogix 5000 Software 18.x

Dragging of Language Elements (x89871, x94889)

Anomaly

RSLogix 5000 Software 17.x

Fatal Error. (x89871, x94889)

Corrected: RSLogix 5000 Software 18.x

Copy An InOut Parameter (x97828)

Anomaly

RSLogix 5000 Software 17.x

RSLogix 5000 software stops responding when attempting to copy an InOut parameter with the Tag Editor Data Context configured as '<definition>'.

Corrected: RSLogix 5000 Software 18.x

Ladder Editor Display Workstation (x91150)

Anomaly

RSLogix 5000 Software 17.x

When the Ladder Editor Display Workstation Option "Display Tag Values for Boolean Operands," is not checked, the Ladder Editor display performance is degraded.

Corrected: RSLogix 5000 Software 18.x

Renaming a Tag (x92319)

Anomaly

RSLogix 5000 Software 17.x

Fatal Error renaming a tag in the Ladder Editor while online with Security enabled.

Corrected: RSLogix 5000 Software 18.x

FBD, Pasting An Output Reference (x106135)

Anomaly

RSLogix 5000 Software 17.x

Pasting an output reference by using the FBD Editor may take a long time.

Corrected: RSLogix 5000 Software 18.x

Response Time In A FBD Routine (x96589, x106609)

Anomaly

RSLogix 5000 Software 17.x

When there are a very large number of references to a single tag in an FBD routine, there may be a lengthy response time for some operations (such as starting a pending edit or pasting). General performance improvements in response time have been made for the FBD Editor.

Corrected: RSLogix 5000 Software 18.x

SFC Editor (x83772)

Anomaly

RSLogix 5000 Software 17.x

In the SFC Editor, the scroll rate changes depending on the size of the chart.

Corrected: RSLogix 5000 Software 18.x

SFC, Force Indication Not Cleared (x96769)

Anomaly

RSLogix 5000 Software 17.x

Removing all SFC forces does not always clear the SFC force indication on the Online Toolbar.

Corrected: RSLogix 5000 Software 18.x

Modified AOI Updates (x89742)

Anomaly

RSLogix 5000 Software 17.x

Online import of a modified Add-On Instruction updates offline image but does not download the change to the controller.

Corrected: RSLogix 5000 Software 18.x

Deleting, Moving an Add-On Instruction Parameter (x97526, x104043)

Anomaly

RSLogix 5000 Software 17.x

When performing edits on the Add-On Instruction Definition dialog box, a Fatal Error may result when deleting or moving an Add-On Instruction parameter after selecting a cell in that row of the table.

Corrected: RSLogix 5000 Software 18.x

Indirect Addressing Of A Bit (x96902)

Anomaly

RSLogix 5000 Software 17.x

Use of indirect addressing of an individual bit does not work in an Add-On Instruction.

Corrected: RSLogix 5000 Software 18.x

Drive Polarity Setting (x90376)

Anomaly

RSLogix 5000 Software 17.x

Drive Polarity setting is not downloaded to the controller.

Corrected: RSLogix 5000 Software 18.x

Export (x25260, x90143, x93294)

Anomaly

RSLogix 5000 Software 17.x

Fatal Errors occur during export.

Corrected: RSLogix 5000 Software 18.x

Upload (x101730)

Anomaly

RSLogix 5000 Software 17.x

Fatal Errors occur during upload.

Corrected: RSLogix 5000 Software 18.02

PLC/SLC Mapped Tag (x92883)

Anomaly

RSLogix 5000 Software 17.x

Corrected: RSLogix 5000 Software 18.x

Selecting Data Compare (x93555)

Anomaly

RSLogix 5000 Software 17.x

Fatal Error selecting 'Data Compare' option during Partial Import.

Corrected: RSLogix 5000 Software 18.02

Incorrectly Reference IO Data (x114908)

Anomaly

RSLogix 5000 Software 18.01

When a project created in a version of RSLogix 5000 software earlier than version 18 is opened, and this project contains tags that are aliased to the I/O data of a DeviceNet Bridge module revision 10 or 11, then the alias tags will incorrectly reference the I/O data. This may result in unexpected program execution, or errors may be reported when the project is verified.

Corrected: RSLogix 5000 Software 18.02

Data Type of AXIS_CIP_DRIVE (x114899)

Anomaly

RSLogix 5000 Software 18.01

When project data for a tag having a Data Type of AXIS_CIP_DRIVE is exported to an XML format file (.L5X file format), some of the Axis attributes are not exported. This results in those attributes being assigned default values when the XML file is imported.

Corrected: RSLogix 5000 Software 18.01

1756-ENBT Modules No Longer Displayed (x109295)

Anomaly

RSLogix 5000 Software 18.00

After installing RSLogix 5000 Version 18.00, 1756-ENBT modules are no longer displayed in the I/O tree viewed using RSLogix 5000 Versions 10 or 11.

Miscellaneous Corrected Anomalies V18

• When a Copy File (COP) or Synchronous Copy File (CPS) instruction is executed and the Source and Destination elements overlap, then incorrect values are stored. (x114517)
• When project data for a tag having a Data Type of AXIS_CIP_DRIVE is exported to an XML format file (.L5X file format), some of the Axis attributes are not exported. This results in those attributes being assigned default values when the XML file is imported. (x114899)
• When a project created in a version of RSLogix 5000 software earlier than version 18 is opened, and this project contains tags that are aliased to the I/O data of a DeviceNet Bridge module revision 10 or 11, then the alias tags will incorrectly reference the I/O data. This may result in unexpected program execution, or errors may be reported when the project is verified. (x114908)
• Online import of a modified Add-On Instruction updates offline image but does not download the change to the controller. (x89742)
• Using cut/copy/paste (or drag-and-drop) to copy rungs from a project open with RSLogix 5000 software version 17.00 does not always result in all of the copied rungs being pasted (or dropped) into a project opened with RSLogix 5000 software version 16.03. (x93106)
• Cross Reference for a task does not show EVENT instructions. (x105511)

Corrected: RSLogix 5000 Software 19.x

Renamed Safety Task (x106091)

Anomaly

RSLogix 5000 18.x

If the Safety Task in a GuardLogix project is renamed to something other than 'SafetyTask', then any subsequent Partial Import will result in the Safety Task being renamed back to 'SafetyTask'. The properties of the task 'SafetyTask' will be reset back to default values.

Corrected: RSLogix 5000 Software 19.x

Offline Memory Estimation (x111825)

Anomaly

RSLogix 5000 Software 18.x

Offline memory estimation for 1756-L7x controllers is incorrect.

Corrected: RSLogix 5000 Software 19.x

PLC-5 Controller (x110912)

Anomaly

RSLogix 5000 Software 18.x

When remote data consumed from a PLC-5 controller changes, the updated value is not displayed in RSLogix 5000 software.

Corrected: RSLogix 5000 Software 19.x

Alternate Documentation Language (x114374)

Anomaly

RSLogix 5000 Software 18.x

Fatal Error editing tag description using an alternate documentation language.

Corrected: RSLogix 5000 Software 19.x

Copy Instruction, Source and Destination Overlap (x114495)

Anomaly

RSLogix 5000 18.x

When a Copy File (COP) or Synchronous Copy File (CPS) instruction is executed and the Source and Destination elements overlap, then incorrect values are stored. (x114495)

Corrected: RSLogix 5000 Software 19.x

Axis Properties Revert To Out-Of-Box Values (x113390)

Anomaly

RSLogix 5000 Software 18.x

When a drive whose Electronic Keying is configured as Exact Match is flashed with firmware that changes the minor revision, the motor data in the Axis Properties may revert to the out-of-box values.

Corrected: RSLogix 5000 Software 19.x

LBL Instruction (x111024)

Anomaly

RSLogix 5000 Software 18.x

Fatal Error during download of a Ladder Diagram routine containing online edits of a rung having a LBL instruction.

Corrected: RSLogix 5000 Software 19.x

Cleared Text From Editor Window (x107126)

Anomaly

RSLogix 5000 18.x

When online edits to a large Structured Text routine (around 5000 lines or larger) are accepted, the display of the text in the Structured Text Editor window is cleared. This gives the appearance that all logic in the routine has been removed. In fact the text still exists and the Accept Pending Edits operation was processed. The display can be refreshed by closing and then reopening the Structured Text routine.

Corrected: RSLogix 5000 Software 19.x

Editing FBD Logic (x112193)

Anomaly

RSLogix 5000 Software 18.x

Fatal Error editing FBD logic in an Add-On Instruction when using an alias to a parameter.

Corrected: RSLogix 5000 Software 19.x

Excessive Number Of GDI Objects (x108518)

Anomaly

RSLogix 5000 Software 18.x

Fatal Error while online editing a Sequential Function Chart routine, due to excessive number of GDI objects.

Corrected: RSLogix 5000 Software 19.x

Align Error (x77113)

Anomaly

RSLogix 5000 Software 18.x

Align error checking for the Alarm Deviation Limit values of a PIDE with checking performed by Logix5000 firmware.

Corrected: RSLogix 5000 Software 19.x

Changing Data In ALMD Or ALMA Instruction (x110187)

Anomaly

RSLogix 5000 Software 18.x

Correlation problem changing data in ALMD or ALMA instruction in an FBD routine with more than one user online to the same controller.

Corrected: RSLogix 5000 Software 19.x

223.xxx.xxx.xxx Ethernet address (x111750)

Anomaly

RSLogix 5000 Software 18.x

Unable to use 223.xxx.xxx.xxx as Ethernet address for EN2T and EWEB modules.

Exceed Unwind Position (x113950)

Anomaly

RSLogix 5000 Software 18.x

(x113950)

Module, Importing Using XML Format (x99961)

Anomaly

RSLogix 5000 Software 18.x

When importing a full project using the XML format (L5X), modules that are configured by using Add-On Profiles (AOP) will revert to their default configuration when imported. Note that the exported XML-format project file contains the correct configuration information. This anomaly does not affect L5K import. Projects exported and imported with an L5K file extension will properly retain AOP module configuration information. In addition, AOP module configuration will be retained when opening a project that has been saved with an ACD file extension.

Corrected: RSLogix 5000 Software 19.x

Import Full Project, Add-On Profiles (x99961)

Anomaly

RSLogix 5000 Software 18.x

Full project import of module configured using Add-On Profiles reverts to default configuration. (x99961)

Corrected: RSLogix 5000 Software 20.x

Security Privileges Are Not Refreshed (x104480)

Anomaly

RSLogix 5000 18.x

When security privileges are updated by using the FactoryTalk Administration Console while a project is open in RSLogix 5000 software, the new security privileges will not be enforced until refreshing the privileges in RSLogix 5000 software (Tools>Security>Refresh Privileges). Sometimes this does not properly refresh the privileges in RSLogix 5000 software. When this occurs, you need to exit and restart RSLogix 5000 software to properly refresh the security privileges.

Miscellaneous Known Anomalies V18

• Partial Import Online of S-Curve Function Block May Execute with Uninitialized Values
• Major Non-Recoverable Fault Removing Alarm Message Tag Association While Online
• Module Configuration is Not Imported for Add-On Profiles When Using XML Format
• Failure to Modify the RPI of a Consumed Tag
• Instances of Going Online for the First Time Failing

Generating WinHlp32 Database for Find Tab (x88677)

Corrected Anomaly

RSLogix 5000 Software 16.x

If you are logged on using an account that does not have Administrator privileges, you may be unable to generate the database for the Find tab for RSLogix 5000 Online Help. An error message will be displayed indicating “Unable to display the Find tab” or “WinHlp32 has stopped working”. This error can be resolved by generating the database while logged on using an account with Administrator privileges. If RSLogix 5000 will be used by an account that does not have Administrator privileges, we suggest that the database be created as part of the installation process while still logged on using an account that has Administrator privileges.

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.

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.

Corrected: RSLogix 5000 Software 20.x

AutoFlash Updates (x45686)

Anomaly

RSLogix 5000 Software 16.x

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

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.

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.

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.

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 Open Full L5X Project File (x114197)

Corrected Anomaly

RSLogix 5000 18.x

If you attempt to open a full project import file that uses XML format (.L5X file format) by using a version of RSLogix 5000 software earlier than the version of RSLogix 5000 software from which the project was exported, then the project will not be opened. An error dialog box will be displayed stating 'Controller revision is not supported'. In order to open an L5X format project file, you will need to first launch a version of RSLogix 5000 software that is at or later than the version from which the project was exported. (One way to launch a particular version of RSLogix 5000 software is to use File>New to create a new controller for the selected Revision.) Note that this anomaly does not affect the way that L5K and ACD project files are opened. When an L5K or ACD file is opened, the appropriate version of RSLogix 5000 software will be automatically launched before opening the project.

Unable to Enable Security (x107466)

Anomaly

RSLogix 5000 18.x

The SetSecKeys tool included with RSLogix 5000 software version 17 and earlier do not work with User Account Control (UAC) turned on. When a SetSecKeys tool earlier than file version 18.0.0.0 is executed with UAC turned on, security appears to be enabled, yet security remains disabled in RSLogix 5000 software. If a version of SetSecKeys earlier than file version 18.0.0.0 is used inadvertently, SetSecKeys file versions 18.0.0.0 and later can still be used to enable security. (Note that depending on the operating system, the file version of SetSecKeys.exe can be viewed on either the Details tab or the Version tab of the File Properties dialog box.)

Unexplained motion possibly caused by the application not recognizing the motion database which could cause the motion configuration to change.

Some PlantPAx P_PIDE Add-On Instruction instance values were set to denormalized low REAL values upon import of a P_PIDE 4.00.00 Add-On Instruction into a project that contained a P_PIDE 3.5.xx Add-On Instruction.

This anomaly first identified in version 18.00.

Attempting to import some Add-On Instructions into an existing project generates the error message: Failed to import <file name>. Unable to parse the L5X content.

This anomaly first identified in version 17.00.

To work around this issue, export the Add-On Instruction, modify the file description to remove dashes. Or, open the L5X file in a plain text editor and modify the description to remove dashes. Import the Add-On Instruction.

This sequence of events can result in unexpected tag values:

1. An Add-On Instruction contains an alias parameter that points to a member of a local tag.

2. The alias parameter is changed to a base tag, either by editing the AOI definition directly or by importing a modified Add-On Instruction that overwrites the existing Add-On Instruction.

3. The instance values for the previously aliased parameters now contains unexpected values.

This anomaly first identified in version 18.00.

Follow one of these steps to work around the issue:

• To replace all values in all instances of the modified Add-On Instruction with the default values, double-click the Parameters and Local Tags folder for the modified Add-On Instruction, then click Copy default values in the Monitor Tags window.  This replaces all existing values for tags of this Add-On Instruction type with their default values.
• To replace the values for only the previously aliased parameters, in the Tag Monitor window, select each Add-On Instruction instance from the Data Context menu and then modify the values for the desired parameters.

Watchdog Fault During Prescan (Lgx00113376, Lgx00112413)

IMPORTANT: You cannot configure the prescan watchdog value.

This anomaly first identified in version 18.11.

Unicode Characters, Does Not Display (Lgx00063773)

References In Program Logic Will Not Update (Lgx00125220)

Fatal error on rung edited online (Lgx00127957)

A Fatal Error is reported when performing a copy and paste operation on a rung that is being edited while online.

This anomaly first identified in version 17.01.01.

Safety modules fail to instantiate after installation of Ethernet module AOP profile 10.00.3664 (Lgx00170167)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Generic Ethernet Module Extensions

Software Enhancement

Firmware Revision/ Software Version 16

With version 16 of RSLogix 5000, the Generic Ethernet Module support that is used to interface Logix5000 to 3rd party devices via EtherNet/IP has been extended in a number of ways.

• Generic EtherNet/IP modules can be added at run-time.
• Tags can be consumed from a 3rd party device via the ETHERNET-MODULE Generic profile.
• A Device’s I/O and status connection request can be disabled by setting the “Comm Format” to “None”.
• The instance number for all generic profiles can now be larger than 255.

These extensions provide greater flexibility when using this configuration option and expand the functionality so that 3rd party devices can interact more readily with Logix5000. 

Report Enhancements

Software Enhancement

Firmware/Software Revision 18

The reports capabilities have been enhanced. Reports can be generated for all components in the Controller Organizer, including tasks, programs, equipment phases, routines, and modules. A table of contents is included with generated reports.

HTML Online Help

Software Enhancement

Firmware/Software Revision 18

RSLogix 5000 Online Help uses HTML as the display mechanism. This HTML Help display mechanism replaces the WinHelp display mechanism, which is no longer supported by the Microsoft Corporation. This change affects Online Help for RSLogix 5000 software version 18 and Online Help for Add-On Profiles. Earlier versions of RSLogix 5000 software continue to use the WinHelp display mechanism.

Watch Pane Quick Watch Enhancements

Software Enhancement

Firmware/Software Revision 18

The following enhancements have been made to the Quick Watch Pane:

- Quick Watch Lists can contain a user-selected group of tags and can be assigned a name, allowing the list to be persistent with the RSLogix 5000 project.

- ToolTips now provide more detailed information in the Quick Watch Pane, such as tag scope.

Tag Filtering Enhancements

Software Enhancement      

Firmware/Software Revision 18

The following enhancements have been made to the filtering capabilities of the Tag Editor:

- Tag display can be restricted to names and/or descriptions containing a user-entered filter string.

- A filter capability is available for alias tags.

- A filter capability is available for tags that have been mapped between Safety and standard controller tags.

Quick View Pane Enhancements

Software Enhancement

Firmware/Software Revision 18

The following enhancements have been made to the Quick View Pane:

- More attributes are now shown in the Quick View Pane for items selected in the Controller Organizer.

- The ability to hide and show the Quick View Pane has been provided.

Language Editor User Interface Enhancement

Software Enhancement

Firmware/Software Revision 18

When specifying an operand for an instruction, the text entry field has been enhanced to auto-size, providing additional space for editing the text.

AutoFlash User Interface Enhancement

Software Enhancement

Firmware/Software Revision 18

When using AutoFlash to update firmware for a GuardLogix controller, you are now prompted only once for the firmware revision. Both the primary controller and the partner module are then flashed with the same revision of firmware.

Keep Zoom Centered

Software Enhancement

Firmware/Software Revision 18

When using zoom in the SFC Editor or the FBD Editor, the logic display will remain centered.

Routine Type Selection During Creation

Software Enhancement

Firmware/Software Revision 18

When a new routine is being created, it can now optionally be assigned as the Main, Fault, or Prestate routine.

Equipment Phase Monitoring Enhancements

Software Enhancement

Firmware/Software Revision 18

The following enhancements have been made to provide additional information when monitoring an equipment phase:

- The display shows when logic is associated with a specific phase.

- The display shows when a producing or standing-by phase is active on the display.

- The equipment list shows a textual indication of the current state of each piece of equipment without having to open each one individually.

- Multiple instances of the display can be opened.

Tag Name Wrapping in Ladder Editor

Software Enhancement

Firmware/Software Revision 18

New workstation options allow tag names in logic to wrap, to be truncated, or to be right or left justified.

Application Notes RSLinx Software v18

RSLogix 5000 Software 18.x

In RSLogix 5000 software version 18, there is an External Access tag attribute, which defines how an external application can access a tag. This functionality is fully supported by RSLinx Classic software version 2.56 and RSLinx Enterprise software version 5.21. RSLogix 5000 software version 18 can be used with earlier versions of RSLinx Classic software to go online to a controller; however, earlier versions of RSLinx Classic or RSLinx Enterprise software should not be used as a data server with a controller running version 18 firmware. Unexpected results will be observed when using an earlier version of RSLinx Classic or RSLinx Enterprise software as a data server with a controller running revision 18 firmware.

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

Beginning with RSLinx Classic software version 2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher) version features. Only one professional activation is required for both products. The RSLogix 5000 Professional Activation must be installed on the personal computer hard disk in order to activate RSLinx Classic Professional (RSLinx Classic OEM with version 16 and higher).

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

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 2.40 or later, you can use the EtherNet/IP driver. This driver will automatically browse for all EtherNet/IP-capable devices on the local or configured remote subnet. See RSLinx online help for information on this driver. Note that 1756-ENET/A and 1756-ENET/B modules will not respond to the browse commands. You must use a different driver for these modules.

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

RSLinx software maintains knowledge of the memory layout of a Logix5000 controller in order to optimize the data access performance when accessing the data in these controllers. However, changes made to an offline project that are then downloaded can result in RSLinx attempting to access tag information that is no longer present. When this occurs, RSLinx halts the communications to the controller. To recover, both RSLinx and the software requesting tags from RSLinx must be re-started. To avoid this anomaly, use caution when making offline changes to a project and then downloading to a Logix5000 controller. In particular, changing the size of an array if elements of the array are already on scan, renaming a structure or a member of a user-defined data type used by a tag that is on scan, or changing the data type of a tag on scan from a larger size to a smaller size (e.g. changing a DINT to a SINT). Note that RSLinx Enterprise Series is able to accommodate these changes without requiring a restart.

Application Notes v18

RSLogix 5000 Software 18.x

The following information is provided to help you better understand the behavior of the RSLogix 5000 software in particular applications or under certain circumstances.

EvRSI activation will be replaced by the FactoryTalk Activation utility in a future release. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Services & Support for information on migrating your activations to FactoryTalk Activation.

RSLogix 5000 software version 18 has replaced the concept of Coordinated System Time (CST) Mastership with the more comprehensive notion of Time Synchronization, also referred to as CIP Sync Time Coordination. The Date/Time page of the controller properties has been modified to reflect this change. For projects created with RSLogix 5000 software version 17 or earlier, if Coordinated System Time Master (CST) is enabled, then the converted project will have the Time Synchronization setting enabled. For more information about time synchronization using CIP Sync, refer to publication IA-AT003A-EN-P, “Integrated Architecture and CIP Sync Configuration Application Technique”.

In version 17 of RSLogix 5000 software, the FactoryTalk Security permissions required for creating scheduled programs have changed slightly. As before, to create an unscheduled program, a user will need permission for the "Program: Create" action. To create a program scheduled in a task, however, a user will now need permission for both the "Program: Create" and the "Task: Modify Properties" actions. To create a program scheduled in the Power-Up Handler or Controller Fault Handler, a user will now need permission for both the "Program: Create" and the "'Controller: Modify Properties" actions. (x77816, x77817)

With RSLogix 5000 software versions 17 and earlier, when online SFC edits are tested or untested, the SFC is reset to the initial step and all stored actions are reset. Beginning with version 18.00 of RSLogix 5000 software, many SFC online edits no longer result in this reset. In general, only edits that alter the logic structure of the chart will require the SFC routine to be reset.

McAfee virus software version 8.0 ships with a “Quick Registry Cleaner” component that cleans the registry on a periodic basis. Upon cleaning the registry, the McAfee software removes all existence of RSLogix 5000 classic profiles from the registry. Once this has occurred, you can no longer create, view, or edit any classic profile based module. This anomaly will also prevent the creation and import of projects. When this condition is encountered, it is necessary to uninstall and reinstall the RSLogix 5000 software. A way to avoid the anomaly is to remove the registry cleaner from any QuickClean manual and scheduled scans and/or delete all scheduled QuickClean tasks from the McAfee SecurityCenter UI. (x81691)

RSLogix 5000 software versions 17 and earlier do not support full project import when using an XML format file (.L5X). If you have version 17 or later of RSLogix 5000 software installed along with some earlier version of RSLogix 5000 software and you are currently running that earlier version of software, then the Open/Import Project dialog box will not allow a file with an L5X or XML file extension to be opened for import. To open an L5X format project you must first be sure that RSLogix 5000 software version 17 or later is running. You can do this either by creating a new version 17 project or by opening any existing version 17 project that was saved with an ACD or L5K file extension. Alternatively, you can select the L5X project file in Microsoft Windows Explorer by right-clicking the L5X file name and using the “Open with” menu item to open the file with "Component of the RSLogix 5000 Application". Note that when the RSLogix 5000 software is installed, files with an ACD file extension are configured by default to open this way when selected. You can configure files with L5X and L5K file extensions to also do this through Windows Explorer by manually associating these extensions with the executable file RSLogix5000Loader.exe, typically installed in the directory C:\Program Files\Rockwell Software\RSLogix 5000\Common. (x87808)

The Windows Help (WinHlp32.exe) program is used to display RSLogix 5000 Online Help that is provided in 32-bit .hlp files. Microsoft stopped including this 32-bit Help file viewer in Windows releases beginning with Windows Vista and Windows Server 2008. RSLogix 5000 software versions 18 and later display Online Help in HTML format and do not require this Windows Help program. However, some module profiles may continue to display Online Help using 32-bit .hlp files. In order to properly display Online Help that is provided in 32-bit .hlp files on a Windows Vista or later operating system, you will need to install the Windows Help program. This application is available for download from the Microsoft Download Center. For additional information on downloading and installing the Windows Help program, refer to the Microsoft Knowledgebase article “I cannot open Help files that require the Windows Help (WinHlp32.exe) program”, located at http://support.microsoft.com/?kbid=917607.

If version 16.00 of RSLogix 5000 software is installed after version 17.00 of RSLogix 5000 software or later, Start Pages will fail to load and the message “Server Startup Failure physicalPath=…” will be displayed. In order to restore Start Page functionality it is necessary to re-install the version 17.00 of RSLogix 5000 software or later. Note that this anomaly will not be observed for version 16.03 of RSLogix 5000 software and later. (x76424)

The FBD ActiveX faceplates are not compatible with Microsoft Windows Vista or later operating systems. Instead, use FactoryTalk View SE/ME FBD Global Objects, available with FactoryTalk View SE/ME software version 5.1 or later.

A new motion instruction error has been incorporated in version 17 of RSLogix 5000 software: error code 78 - Not Allowed While Stopping. In addition, an expanded meaning has been incorporated for error code 7 - Shutdown State Error. These errors will now be generated whenever an MGS, MAS=All, or MCS=All is active and a second motion instruction is then executed in sequence while one of these is still active. The second instruction will now report either an error 78 or an error 7. The user must allow the initial MGS, MAS=All, or MCS=All to complete before initiating another motion instruction. (x83819, x85559)

The hardwired digital inputs on the Kinetix 6000 S0 Enhanced Safe Torque-off Drive and S1 Advanced Safety Drive are now populated via 4 hardwired connections representing 7 selectable inputs. With the introduction of these profiles in version 17 of RSLogix 5000 software, users must develop application logic to map these inputs. This must be done via the MSG command, Read_IDN, Write_IDN to SERCOS Identification Number P-0-52, 53, 54, and 55. This data must be rewritten at each power-up of the SERCOS Ring. The user’s application must be written to make proper use of these digital inputs within the context of the associated motion instructions.

Creation of an RSLogix 5000 event task for a SoftLogix controller will result in the creation of a Microsoft Windows event with the same name. Since Windows events are globally scoped among all applications running on the same workstation, names of the event tasks must be chosen carefully so as not to conflict with other Windows events.

If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you will need an updated motion database to work with RSLogix 5000 software version 18. The following table lists the motion database revisions that are used with these RSLogix 5000 software versions.

To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.

When Adobe Reader 6.0 and Adobe Acrobat 6.0 or 7.0 are both installed on the same workstation, attempting to print reports from RSLogix 5000 software may result in a dialog box being displayed with the message “Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?” This issue is documented in the Adobe Knowledgebase article http://kb.adobe.com/selfservice/viewContent.do?externalId=321561&sliceId=2, which also describes the recommended procedure for installing Adobe Acrobat Reader 6.0 and 7.0 on the same workstation. A temporary workaround for printing RSLogix 5000 reports is to click No in the dialog box, in the RSLogix 5000 Print dialog box change the printer name to some other printer, change the printer name back to Adobe PDF, and then click OK to print the document. (x88019)

The performance of the Rockwell Automation Integrated Motion’s motion planner has been improved in the controller firmware associated with version 16.03 of RSLogix 5000 software. As a consequence, there may be minor differences in the velocity profile and the path profiles in some blended and merged moves. The majority of these minor differences manifest themselves in velocity limited moves and in moves programmed using an S-curve velocity profile. There may also be minor differences in Trapezoidal velocity profiles. Please refer to Technical Note “Motion Planner, version 16.03 Application Solution” publication RA-AP-031 for additional details.

The Kinematics Transformation motion control capabilities of ControlLogix that were introduced with firmware revision 16.20 (included with RSLogix 5000 software version 16.03) should only be used with version 16.03 or greater of RSLogix 5000 software. If RSLogix 5000 software version 16.00 is used to upload a project containing one of the four new native geometries from a controller flashed with revision 16.20 firmware or later, then any of these four non-supported geometries will be converted to the default Coordinate System Type of “Cartesian”. The message “attribute list error” will be displayed during the download attempt of an RSLogix 5000 software version 16.03 project containing one of the four new native geometries to a controller flashed with a firmware revision earlier than revision 16.20. (x75769)

Unscheduled Connections are not supported for the current release of the 1757-FFLDC module. Ensure that the “Use Scheduled Connection over ControlNet” checkbox is checked on the Connection tab of all Logix Blocks. (This checkbox is checked by default when a Logix Block is created.)

This application note affects customers who have Beta software for version 17 of RSLogix 5000 software installed on their workstation. The version 17 Install will not offer to uninstall any previous installations of version 17 software. Before installing the released version 17 software, it is necessary to first uninstall the version 17 Beta software using Add/Remove Programs.

This applies only if you are using security with version 16 of RSLogix 5000 software. In order for CPR 7 FactoryTalk Network Directory clients to take advantage of new security actions added in version 16 of RSLogix 5000 software, a utility needs to be run on the CPR 7 FactoryTalk Network Directory Server. This utility is automatically run when version 16 of RSLogix 5000 software is installed. However, if you will not be installing version 16 of RSLogix 5000 software on the FactoryTalk Network Directory Server, it is strongly recommended that you run the utility manually on the server prior to installing or running version 16 of RSLogix 5000 software on other workstations. The utility, named “UpdateActionsInSchema.exe”, can be found in the “System\SecuritySchemaUpdate\” directory on the RSLogix 5000 DVD. Note that upon execution, the utility will provide further instructions.

In version 16, the SFCRESTART attribute has been removed from the PROGRAM class for the GSV and SSV instructions. This attribute was not used in earlier versions of Logix5000, and it will now report a verification error if present.

Existing RSI Security Server installations can be migrated to FactoryTalk Security. The FactoryTalk Security server is provided with the FactoryTalk Service Platform, which can be found on the RSLogix 5000 DVD. See the FactoryTalk Security installation instructions for further migration information.

In version 16, the built-in action groups have been removed from RSLogix 5000 software (for example, Full Access, Maintain Project, Go Online, and View Project). If you are upgrading to RSLogix 5000 software version 16 and continue to use RSI Security Server for Logix security rather than migrating to FactoryTalk, a set of predefined action groups can be found in the RSLogix5000Security.bak file and are for use with version 16. These new action groups for the RSI Security Server are

0. RSLogix 5000 Full Access
1. RSLogix 5000 Maintain Project
2. RSLogix 5000 Go Online
3. RSLogix 5000 View Project

They will be available in the RSI Security server once the RSLogix5000Security.bak file has been imported.

When making changes to a configuration dialog box that contains a Tag tab, you may see an error message displayed indicating that “Tag: Modify Properties” is not granted. Allowed configuration changes to tabs other than the Tag tab are still committed, and this error can be ignored. (x72089)

The release and update of FactoryTalk Security is independent of the release of RSLogix 5000 software. FactoryTalk Security in CPR 9 will support resource groups and action groups. This feature will allow the user to conveniently group resources, like ControlLogix controllers, and actions, like “Tag Create”, for easier security administration.

Due to the operation of single precision floating point arithmetic processing in the controller, intermediate results shown in the Soak time Left of the Ramp/Soak (RMPS) instruction may appear to be inaccurate during the execution of the instruction. This does not cause improper execution of the instruction. (x72583)

Some motor parameter value settings have been changed in the version 17 Motion Database for the following motor types: MPL-A, MPL-B, 8720SM-xxxS, and TLY-A110T-Hxx. A project created in a version earlier than version 17 of RSLogix 5000 software that contains an AXIS_SERVO_DRIVE type axis configured with one of these motors will have its related axis parameters converted when opened in version 17 of RSLogix 5000 software. When this occurs, the following warning message will be displayed: “Axis ‘<tag_name>’ Warning: Parameters for the associated motor have changed, which may have caused changes to some axis parameters. Please verify the axis performance.” When this warning is encountered, you should verify that the axis parameters pertaining to rated current are configured for proper axis operation. You should also validate that the axis is properly configured for your application. As an alternative, you can re-associate the motor to the axis, but in this case, all motor parameters will be reset to default motion database values, canceling any previously tuned and saved non-default axis values.

In the Motion Database earlier than version 16 of RSLogix 5000 software, the Maximum Rated Current (I-rated) value for certain MPF, MPG, MPL, and TL motors were defined with settings from 1% to 7% higher than rated. If a project created in version 15 or earlier contains an AXIS_SERVE_DRIVE type axis configured with one of these motors, then when this project is imported (L5K format project file) into RSLogix 5000 software version 16, the following warning will be generated: “Warning: During conversion of Axis ‘<tag name>’ – Parameters for the associated motor have change, which may have caused changes to some axis parameters. Please verify the axis performance.” When this warning is encountered, the user should verify that the Axis Parameters pertaining to Rated Current are configured for proper axis operation. As an alternative, the user can reassociate the motor to the axis, but in this case all motor parameters will be Reset to default Motion database values, canceling many previously tuned and saved axis values. This issue does not exist with database conversion of an ACD format project file. The motors that are affected are: MPF-B310P, -B320P, -B330P, -B4430K; MPG-A004-031, -A110-031, -A11-0-091; MPL-A310F, -A430P, -B420P, -B4520P, -B4530F, -B4530K, -B580J, -B980L; TL-A120P-H, -A130P-H, -A220P-H, A230P-H.

A new 64-bit Long INTeger data type (LINT) was introduced in version 16 of RSLogix 5000 software. This data type is currently used only for date and time stamps for the analog and digital alarm instructions (ALMA and ALMD). In the CPR 9 release of FactoryTalk View SE, these LINT time stamp values can be displayed only on the Alarm Summary, Alarm Banner, and Alarm Log. LINT time stamps cannot be displayed on custom FactoryTalk View SE graphics. Support for display of LINT time stamp values on custom graphics will be added to a future release of FactoryTalk SE.

The Controller Time Object was modified in version 16 of RSLogix 5000 software to support future alarms and events functionality. Time stamps now use Universal Coordinated Time (UTC), also referred to as Greenwich Mean Time (GMT). If the logic in your application reads or sets the controller clock by using the GSV/SSV attribute “DateTime”, then this logic should be updated to use the new attribute “LocalDateTime”. You may also need to make other modifications to your application as a result of this change. (x72073, x72238)

A Logix5000 Clock Update Tool is included on the RSLogix 5000 DVD. Only revision 2.2.5 or later of this tool should be used with Logix5000 version 16 and later. Older revisions may not properly synchronize workstation time and controller time.

When using a 1734-AENT or a 1738-AENT that is configured in one of the following two cases, you need to upgrade the firmware in the adapter module in order for both controllers to make a connection. The two scenarios are:

0. 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.
1. 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.

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

If the Microsoft Windows operating system is not configured with the recommended System Locale, a warning will be displayed when RSLogix 5000 software is started. Clicking “Change” on this warning dialog box will navigate to the operating system dialog box from which the user can adjust the System Locale.

The System Locale can then be changed by selecting a new “Language for non-Unicode programs (System Locale)” on the Advanced tab of the Regional and Language Options (accessed from Microsoft Windows Control Panel). For example, if you are running the Chinese version of RSLogix 5000 software (9324-RLD300ZHE), you should select “Chinese (PRC)” for the System Locale.

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

Starting with RSLogix 5000 software version 14, the directory structure for temporary RSLogix 5000 folders has been modified so that all AB_xxxx folders now reside within a single folder named “RSLogix 5000.Temp” located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000).

To prevent the CTree errors from occurring, the McAfee VirusScan software settings can be configured to ignore the contents of the “RSLogix5000.Temp” folder. (x51417, x85503)

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

The new MOTION_INSTRUCTION data type structure is:

FLAGS                  DINT

EN                         BOOL

DN                        BOOL

ER                         BOOL

PC                         BOOL

IP                          BOOL

AC                         BOOL

ACCEL                  BOOL

DECEL                  BOOL

ERR                       INT

STATUS               SINT

STATE                  SINT

SEGMENT          DINT

EXERR                  SINT

Note the addition of a new flag AC and a new element EXERR. (x36228, x34556, x33393)

The REAL data type now shows a 32-bit (4-byte) IEEE floating-point value with the following range:

0. -3.40282347E38 to -1.17549435E-38 (negative values)
1. 0
2. 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:

0. -1.17549421E-38 to -1.40129846E-45 (negative values)
1. 1.40129846E-45 to 1.17549421E-38 (positive values)

When performing online editing operations in a Sequential Function Chart (SFC), be aware that switching the executing logic from the original programming to the test edits version (or vice versa) will reset the chart to the initial step and reset all stored actions. This occurs regardless of which steps and actions were active at the time of the switch. To work around this anomaly, you can force the transition with the initial step to false, wait for the routine to execute to the initial step, and then perform the test/un-test operation followed by removal of the force. Also, you could leverage the SFC Reset (SFR) instruction to re-position the chart back to the desired step. (x36331, x43482)

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

During a file save operation RSLogix 5000 software attempts to compress the contents of a project so that the resulting file (ACD) requires less disk space. When opening a project this process is reversed and the contents of the ACD file are de-compressed. In some instances, RSLogix 5000 software may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 software will perform the save without the compression. When this occurs, your ACD file may become abnormally large but it is still usable, that is, you can continue to work with the file as you would normally. However, if you contact Rockwell Automation Services & Support and provide a copy of your project file, this could help the RSLogix 5000 software development team to locate the source of the compression failure.

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

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

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

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

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

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

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

With the new Phase Loss Fault-action, added in version 16, if the Integrated Axis Module (IAM) detects a phase loss fault, the motor attached to that IAM will respond with respect to the phase loss fault action setting as configured in RSLogix 5000 software without any user logic being written. However, a Kinetix Axis Module (AM) on the same power rail will require logic to be written if the user expects the motor on the AM to perform in the same manner as does the IAM. This logic should monitor the IAM’s phase loss status bit, and based on the value of this bit, cause the motor attached to the AM to respond in the same manner as the IAM in regards to axis and drive stopping action. The AM cannot have the Power Loss Fault-action configured; only the IAM can. For more detail see also Kinetix Drive Firmware Release Notes (x71448, x71717).

The Fault Reset timing for Kinetix based Sercos Drives has changed in Drive firmware revision 1.85 to accommodate new checks for reset of the motor commutation angle on the reset of certain drive faults, in particular E05 (IPM), E18 (Overspeed), and E19 (Following Error). Average timing changes observed were 20ms in version 13 associated drive firmware and now up to 400ms, in the RSLogix 5000 software version 15 associated drive firmware for Motion Fault Reset MAFR instruction to complete for clearing the above listed faults. For more detail see also Kinetix Drive Firmware Release Notes. (x55240)

Version 13 of RSLogix 5000 software added the capability to use either RSLinx, RSWho, or RSLogix 5000 Who Active dialog boxes to browse to RA Sercos drives. In version 15, support was added to allow direct firmware update of the RA Sercos drives via ControlFLASH. The SERCOS Ring must be connected and able to reach Phase 2 to use ControlFLASH for firmware update. The ControlFLASH via Sercos will 1st transition the Ring to Phase-0, then re-establish Phase-2, and finally establish Phase-5 on the drive that ControlFLASH will be updating. ControlFLASH of the drives on the Ring must be done one drive node at a time.

Specific firmware revisions must exist on both the Logix MxxSE Sercos Interface motion modules and on the RA Sercos Drives to support ControlFLASH via SERCOS. The Logix MxxSE module must have at minimum revision 15.06, the RA Kinetix Sercos drives must have revision 1.85 or higher, and the RA Ultra Sercos drives must have revision 1.50 or higher. Also required is RSLinx software version 2.42 or later, and if using a 1784-PCICS card for the communication routing, the PCICS card should have current firmware and driver version 2.7 or later. (x51766)

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

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

If the list of modules appears empty in the Select Module Type dialog box when you attempt to create a new module, there may be an anomaly with system DLL files on your computer. Make sure that the version of files on your computer matches the compatible version listed in the table below. (x19891, x18680, x06823)

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

To change the error detection, open a project and establish online communications using Ethernet, ControlNet, or DF1 communications to the target Logix5000 controller. Open the Controller Properties dialog box and select the System Protocol tab. Under Error Detection enable the CRC radio button and select Apply. If using DF1 communications, there will be a short delay and then the RSLogix 5000 information dialog box will display the error: “Failed to modify the DF1 Protocol configuration. Communications timed out.” This is expected and normal for this operation, click OK to acknowledge the error. The other protocols will not display the error. Start RSLinx and select the Communications menu. Under this menu select Configure Drivers… and then Configure… for the desired DF1 driver such as AB_DF1-1. Click on the Auto-Configure button and the text following the list box Error Checking: will change from BCC to CRC. Click on OK to close the dialog box and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 software select Go Online to re-establish online communications. This DF1 driver will now communicate only with Logix5000 Controllers that are setup to use CRC Error Detection.

There is a log file generated that records abnormal events and which can be delivered to Rockwell Automation Services & Support so that the anomaly can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 software will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title "RSLogix 5000 Fatal Error" and containing specific details about the cause of the error. In addition, this information is appended to the file "RSLogix 5000 Fatal Error.Log”. In order to more effectively address software error conditions, starting with version 14.00, the Fatal Error information will be stored in a file named RSLogix 5000 Fatal Error.Dmp. This file, containing the exact memory image at the time the error occurred, greatly extends our ability to determine the cause of the Fatal Error and to address product anomalies if those were the case. The new file will be large. If it must be sent to Rockwell Automation Services & Support, it can be either (a) copied to a CD or (b) posted onto our public FTP site (ftp://ftp.rockwellautomation.com/pub/). The RSLogix 5000 Fatal Error.Dmp file can also be deleted if not needed.

Starting with RSLogix 5000 software version 17.00, these diagnostic files are located in C:\Users\Public\Public Documents\Rockwell Automation\RSLogix 5000\Logs for Windows Vista or in C:\Documents and Settings\All Users\Documents\Rockwell Automation\RSLogix 5000\Logs for Windows XP, Windows Server 2003, and Windows 2000. For RSLogix 5000 software versions earlier than version 17.00, these diagnostic files are located in the directory C:\Documents and Settings\<username>\Local Settings\Temp (for all operating systems).

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

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

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

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

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

If an RSLogix 5000 session is terminated abnormally, some large temporary files may be left on the hard drive. You should periodically delete old folders named AB_xxxx from your temporary directory. Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may also be deleted.

AB_xxxx folders reside within a single folder named “RSLogix 5000.Temp” located under the Temp directory (C:\Users\<username>\AppData\Local\Temp for Windows Vista or C:\Documents and Settings\<username>\Local Settings\Temp for Windows XP, Windows Server 2003, and Windows 2000).

Caused by a corrupted activation key file (evrsi.sys). To correct this anomaly, contact Rockwell Automation Services & Support by telephone at +1 440-646-3434 or by email at RACleAskTheExpert@ra.rockwell.com.

.