Hardware Requirements v17

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

1. Be certain that no copies of RSLogix 5000 software are currently running.
2. 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.
3. When installing on a workstation running the Windows Vista operating system, turn off User Account Control (UAC).
4. If you want to perform online communications, you must install RSLinx Classic software in addition to RSLogix 5000 software.
5. Close all other applications before running the setup process.
6. 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.

1. Start the personal computer.

1. Insert the RSLogix 5000 installation DVD into your DVC-ROM drive.

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

1. Follow the directions that appear on your screen and refer to the FactoryTalk Activation insert for additional information.

1. Click Finish to complete the installation.

1. Remove the RSLogix 5000 DVD from the DVD-ROM drive and store it in a safe place.

1. Do you have the correct version of RSLinx Classic software installed? RSLinx Classic software provides communication between the controller and your personal computer.
2. Does your computer have enough memory? Running RSLogix 5000 software requires a minimum of 256 MB of RAM.

1. Choose Start>Settings>Control Panel.

1. Double-click Add/Remove Programs. (Windows XP, Windows Server 2003, Windows 2000),

1. From this dialog box, double-click “RSLogix 5000 <version>”.

1. Choose Start>Control Panel.

1. Double-click Add/Remove Programs. (Windows XP, Windows Server 2003),

1. From this dialog box, double-click “RSLogix 5000 <version>”.

1. Choose Start>Settings>Control Panel>Add/Remove Programs.

1. From this dialog box, double-click “RSLogix 5000 <version>”.

Note that this will uninstall only the RSLogix 5000 application. Other components that were installed with RSLogix 5000 software (such as Start Page Media, Online Books, or RSLinx) must be uninstalled separately.

Software Requirements Product Considerations v17

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.

Software Requirements v17

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 and Home Basic with Service Pack 1 and User Account Control (UAC) turned off
2. Microsoft Windows XP Professional with Service Packs 2 and 3
3. Microsoft Windows Server 2003 R2 Standard Edition with Service Pack 2
4. Microsoft Windows 2000 Professional with Service Pack 4

0. 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:
1. Microsoft Windows Vista
2. Microsoft Windows XP
3. Microsoft Windows Server 2003
4. Microsoft Windows 2000

Advanced Process Control Instructions

System Feature

Firmware Revision/ Software Version 17.02

Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65

Firmware Revision/ Software Version 17.06

Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S

Three new instructions targeted for process applications have been added. The new instructions are:

• Internal Model Control (IMC) – Compares actual process error against error calculated by an internal first order lag plus deadtime model.
• Coordinated Control (CC) – Controls a single process variable by manipulating as many as three different control variables.
• Modular Multivariable Control (MMC) – Controls two process variables to their setpoints using up to three control variables.

Instructions need to be purchased separately and licensed per use. The catalog numbers and associated use types are:

• 9324-RLDAPCENE – provides a license to use the instructions in RSLogix 5000 and provides a license to use them in a single Logix controller.
• 9324-RLDAPCCLENE - provides a license to use the instructions in an additional controller, pay-to-deploy.

Runtime Partial Import

System Feature

Firmware Revision/ Software Version 17.02

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

Firmware Revision/ Software Version 17.06

Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S

You can now import programs, equipment phases, routines, rungs, and new Add-On Instructions into a running system.

You can add these new components, as well as replace existing programs, equipment phases, and routines, while the system is running. New tags and User-Defined Types will be created as needed with values initialized from the import file. Data values of existing tags will be maintained.

MCD and MCCD Motion Instructions Enhancements

System Feature

Firmware Revision/ Software Version 17

With version 17 of RSLogix 5000 software, the functionality of the Motion Change Dynamics (MCD) instruction was extended to allow for the acceleration and deceleration jerk rates to be also changed for in-process single-axis moves or jogs. These same extensions apply to the Motion Coordinated Change Dynamics (MCCD) instruction, allowing for the acceleration and deceleration jerk rates to be changed for multi-axis coordinate moves or jogs. In addition, enumerations have been added to the MCCD instruction so that the "Active & Pending" motion can be changed dynamically.

Active and Pending Motion

System Feature

Firmware Revision/ Software Version 17.02

Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65

Firmware Revision/ Software Version 17.06

Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S

A new enumeration, that is Active and Pending Motion, has been added to the Scope variable of the MCCD instruction. Choosing Active and Pending Motion specifies that the changes affect the motion dynamics of the active coordinated motion instruction and any pending coordinated motion instruction in the queue.

Decorated Data for Import/Export in XML format

System Feature

Firmware Revision/ Software Version 17

Version 17 of RSLogix 5000 software also provides for an alternative format for specifying tag data when exporting or importing using the XML format. This verbose format is used to improve user readability of the tag data values in an XML file.

Full Project Import/Export in XML format

System Feature

Firmware Revision/ Software Version 17

Version 17 of RSLogix 5000 software provides the ability to import and export an entire project using an Extensible Markup Language (XML) file with a .L5X file extension. This is similar to import/export using an ANSI text file with .L5K extension.

Integrated System Install

System Feature

Firmware Revision/ Software Version 17

The installation of version 17 of RSLogix 5000 software has been further integrated with the installation of other Rockwell Software products that may be bundled with the purchased edition of RSLogix 5000 software. The label on the RSLogix 5000 DVD indicates that it is the first DVD to be installed. The RSLogix 5000 system install then allows for selection of other Rockwell Software products, components, firmware kits, and tools to be installed. All selected items will then be installed in the proper order.

Program and Routine Partial Import/Export

System Feature

Firmware Revision/ Software Version 17

Version 17 of RSLogix 5000 software extends its capability to import and export project components to also include programs, routines, and equipment phases. These components are imported from and exported to an Extensible Markup Language (XML) file with a .L5X file extension. These text files can be manipulated or created by other tools, allowing the user to create libraries of code to facilitate code reuse.

Runtime Detection of Controller Modifications

System Feature

Firmware Revision/ Software Version 17.02

Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65

Firmware Revision/ Software Version 17.06

Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S

Online changes to programs and data in a 1756-L6x ControlLogix controller can be tracked via an internal log with change counters. The log includes the type of change and the personal computer identity (Windows login) of the user who made the change. The change log can be stored on the controller's CompactFlash card for offline review. Changes may also be monitored programmatically by reading the change log counter using a Get System Variable (GSV) instruction.

GuardLogix Safety Instructions

System Feature

Firmware Revision/ Software Version 17.06

Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S

Several new safety instructions are available with the use of RSLogix 5000 software, version 17 and GuardLogix controller firmware, revision 17. New instructions include:

• Nine Metal Forming Instructions
• Three Muting Instructions (for Light Curtains)
• Six Dual Channel Instructions
• A Safety Mat Instruction
• A Configurable Redundant Output Instruction
• A Two Hand Run Station Enhanced Instruction

For more information about these and other safety instructions, see the GuardLogix Safety Application Instruction Set Safety Reference Manual, publication 1756-RM095.

Kinetix 6000 Advanced Safety Drive (S1) and Enhanced Safe Torque-off Drive (S0)

System Feature

Firmware Revision/ Software Version 17.02

Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65

Firmware Revision/ Software Version 17.06

Catalog Numbers 1756-L61S, 1756-L62S, 1756-L63S

Version 17 provides support for the Kinetix 6000 SERCOS S1 Advanced Safety based family of drives. The safety status can be directly accessed by the user's application via two new SERCOS Axis attributes (GuardStatus and GuardFaults) in the Axis_Servo_Drive data type. The configuration of the S1 Drive's safety parameters is done via an Ethernet WEB based interface and downloaded to the Kinetix6000 drive via this Ethernet connection.

Version 17 provides support for the Kinetix 6000 SERCOS S0 Enhanced Safety based family of drives. The safety status can be directly accessed by the user's application via a bit attribute (SafeOff) in the Axis_Servo_Drive data type.

Corrected: Logix Firmware/RSLogix 5000 17.02, 17.06

Indirectly Addressing an Instance Tag (Lgx00077261)

Anomaly

Logix Firmware 16.x

Catalog Numbers 1756-L61, 1756-L61S, 1756-L62, 1756-L62S, 1756-L63, 1756-63S, 1756-L64

An instance tag is associated with each individual call to an Add-On Instruction (AOI). In Version 16.00 of RSLogix 5000, if this instance tag is a tag array element that is indexed by another tag (referred to as indirect indexing), then execution of the routine will result in undesired behavior (e.g., Major Non-Recoverable Fault, Watch Dog time-out, Major Fault). As an example, in the instruction call to "MyAOI(AOIData[Index])", the value of the tag "index" would be used to select which AOIData tag element is used by the call to MyAOI. In Version 16.03, the use of a tag as an index into an AOI instance tag array will result in a controller verification error, which will prevent the project from being downloaded. Note that the AOI instance tag may be defined as an element of a tag array provided it is referenced using a constant value (e.g., MyAOI(AOIData[2], where the constant 2 references the third element of the AOI tag instance array). Also note that indirect indexing operations may be used for the Input and Output Parameter tags of an AOI without a problem. The ability to use indirect indexing operations for AOI instance tags will be provided in a future version of RSLogix 5000.

Corrected: RSLogix 5000 Software 17.01

Start Pages (x83020)

Anomaly

RSLogix 5000 Software 16.x

Fatal Error reported from Start Pages if workstation is not connected to the network.

Corrected: RSLogix 5000 Software 17.01

Tag Browser (x87132)

Anomaly

RSLogix 5000 Software 16.x

The Tag Browser was optimized to reduce the amount of time it takes display tags in the Tag Browser.

Corrected: RSLogix 5000 Software 17.01

Unable to Set Date/Time (x86590)

Anomaly

RSLogix 5000 Software 16.x

Unable to set Date/Time when RSLogix 5000 is running on a non-English operating system.

Corrected: RSLogix 5000 Software 17.01

Selecting Literature Library Links (x78861)

Anomaly

RSLogix 5000 Software 16.x

Selecting some Literature Library links from Start Pages results in Fatal Error.

Corrected: RSLogix 5000 Software 17.x

Unable to Update 1756-M02AE Module (x71573)

Anomaly

RSLogix 5000 Software 16.x

Using ControlFLASH version 6.00.02, you cannot update the firmware of a 1756-M02AE motion module after a successful update of a controller module. Attempting to do this will generate the error: “#10300 Not enough data received in response of Update”. At this point, the user must exit the ControlFLASH tool and then restart it to allow completion of the 1756-M02AE firmware update. As an alternative, update the 1756-M02AE firmware before updating the controller firmware. In this case, both updates complete properly. Additionally, in the case of firmware updates using AutoFlash, the default sequence is to update controller modules followed by motion modules, which may result in the error “Failed to communicate to the target Device” being generated. The user must then update the 1756-M02AE firmware separately.

Corrected: RSLogix 5000 Software 16.04

Watch List, Deleteing Tags (x75872)

Anomaly

RSLogix 5000 Software 16.03

Fatal Error deleting tags from the Watch list.

Corrected: RSLogix 5000 Software 17.00

Controller Scope Tag (x07963)

Anomaly

RSLogix 5000 Software 16.x

A warning should be displayed when creation or deletion of a program scope tag cause program logic to rebind to or from a Controller scope tag with the same name.

Corrected: RSLogix 5000 Software 17.00

RSLogix 5000 Application Non-Responsive (x72467)

Anomaly

RSLogix 5000 Software 16.x

RSLogix 5000 application may be non-responsive when attempting to verify a controller after pasting a coordinate system tag copied from another project.

Corrected: RSLogix 5000 Software 17.00

Undo in Ladder Editor (x74099)

Anomaly

RSLogix 5000 Software 16.x

Undo of value change in Ladder Editor may not revert to original value if display style is also changed.

Corrected: RSLogix 5000 Software 17.00

Standard Tag List (x79147)

Anomaly

RSLogix 5000 Software 16.x

Fatal Error selecting tag in Standard Tag list of Safety Tag Mapping dialog box.

Corrected: RSLogix 5000 Software 17.00

FBD Routine was Optimized (x81630)

Anomaly

RSLogix 5000 Software 16.x

Searching throughan FBD Routine was optimized to reduce the amount of time it takes to perform Search and Replace operations. (x81630)

Corrected: RSLogix 5000 Software 17.00

SFC, FOR or BREAK Instruction (x73342)

Anomaly

RSLogix 5000 Software 16.x

Attempting to execute a program containing a FOR or BREAK instruction that calls a Sequential Function Chart subroutine results in major fault of the SoftLogix5860 controller.

Corrected: RSLogix 5000 17.00

Array Bounds (x77270)

Anomaly

RSLogix 5000 Software 16.x

When a tag of a User Defined Type (UDT) is passed into an Add-On Instruction (AOI), the array bounds may not be properly checked, resulting in either a major fault or a data memory corruption. The conditions when this will occur are (1) a 1-dimensional array of a UDT is passed into an AOI, (2) the UDT contains a member that is an array, and (3) in the AOI logic an operand specifies an immediate member of the UDT array and a variable element of its member array (e.g., array[0].memberArray[x]). A workaround is to use a variable for the UDT array index (e.g., array[ZeroTag].memberArray[x])

Corrected: RSLogix 5000 17.x

Boolean Array Passed as InOut Parameter (x77241)

Anomaly

RSLogix 5000 Software 16.x

When performing a download to a SoftLogix 5860 or RSEmulate controller, if the project contains an Add-On Instruction (AOI) which passes a Boolean array to another nested AOI as an InOut parameter, a Fatal Error will occur. The same Fatal Error is observed during memory estimation (Edit -> Controller Properties, “Memory” tab).

Corrected: RSLogix 5000 Software 17.01

GSV in Add-On Instructions (x75872)

Anomaly

RSLogix 5000 Software 16.x

GSV in Add-On Instruction does not allow Safety class to be selected.

Corrected: RSLogix 5000 Software 17.01

Add-On Instruction with Aliased Parameters (x87633)

Anomaly

RSLogix 5000 Software 16.x

Fatal Error uploading project containing Add-On Instruction with aliased parameters

Corrected: RSLogix 5000 17.x

FGEN Instruction, Downloading (x73042)

Anomaly

RSLogix 5000 Software 16.x

In an FBD routine, the FGEN instruction has two optional parameters, X2 and Y2. If these parameters are omitted, attempts to download the project to a SoftLogix controller will result in a Fatal Error. The same Fatal Error would also be observed when downloading using RSEmulate. A workaround to avoid this problem involves specifying a dummy tag for the X2 and Y2 parameters. The tag used for X2 and Y2 must be an array of type REAL (e.g., tag of data type REAL[1]). Also, insure that the parameter XY2SIZE has a value of 0, configurable on the Parameters tab of the FGEN instruction properties dialog.

Corrected: RSLogix 5000 17.x

RSLogix 5000 Software Fatal Error When 1756 HART Module Is Deleted From Controller By Another User (x72882)

Anomaly

RSLogix 5000 Software 16.x

The 1756-IF8H and 1756-OF8H HART modules can be configured online using version 16 of RSLogix 5000. If more than one user is accessing the same controller using RSLogix 5000, deleting one of these modules from the I/O Configuration tree will result in a Fatal Error in the RSLogix 5000 application for any other online users who are changing the module definition or who are viewing a confirmation dialog for the deleted module.

Corrected: RSLogix 5000 Software 17.01

Rack Connection (x89372, x94009)

Anomaly

RSLogix 5000 Software 17.00

Rack Connection support is not backwards compatible. Support for Rack Connection Type Definition resulted in Type Definition not being backwards compatible in some scenarios.

Corrected: RSLogix 5000 Software 17.01

Safety Module Signature (x92835)

Anomaly

RSLogix 5000 Software 17.00

In some situations, after configuring a safety module, the safety module signature may not be displayed properly.

Corrected: RSLogix 5000 Software 17.01

Online Help, Recovery Documentation (x93080, x93094)

Anomaly

RSLogix 5000 Software 17.00

Online Help does not document that certain functions of the software may be temporarily disabled during Automatic Project Recovery file generation.

Corrected: RSLogix 5000 Software 17.01

Copying Rungs (x90415)

Anomaly

RSLogix 5000 Software 17.00

Using cut/copy/paste (or drag-and-drop) to copy rungs from a project open with RSLogix 5000 version 17.00 does not always result in all of the copied rungs being pasted (or dropped) into a project open with RSLogix 5000 version 16.03.

Corrected: RSLogix 5000 Software 17.01

Online Help, MCD Instruction Units Documentation (x93146)

Anomaly

RSLogix 5000 Software 17.00

The Motion Change Dynamics (MCD) instruction units for Speed, Acceleration, and Deceleration are incorrectly documented in the Online Help.

Corrected: RSLogix 5000 Software 17.01

Incorrect Peak Current Ratings (x92586)

Anomaly

RSLogix 5000 Software 17.00

Incorrect peak current ratings are being used for Kinetix 6000 SERCOS S1 Advanced Safety drives.

Miscellaneous Corrected Anomalies V17

• Implied convergence in a Sequential Function Chart can result in more than one step on the same thread being active at the same time. (x74140)
• Fatal Error may occur when deleting an Add-On Instruction with logic that references a tag that does not exist. (x74775)
• When the axis is in the Safe-Off mode, an MAS-Gear results in an error 05 (Servo Off Error). (x77218)
• A Rotary Positive MAM move may cause the axis to move in a negative direction. (x80848)

Generating WinHlp32 Database for Find Tab (x88677)

Corrected Anomaly

RSLogix 5000 Software 16.x

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

Corrected: RSLogix 5000 Software 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.

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.

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.

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.

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.

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.

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.

Miscellaneous Known Anomalies V17

• 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

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

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.

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. 

Coordinated System Time (CST) Master Existence Check on Download

Software Enhancement

Firmware Revision/ Software Version 17

Applications with Motion Groups and GuardLogix controllers require a target controller to be designated as the Coordinated System Time (CST) master. With version 17 of RSLogix 5000 software, this designation can now be made directly from the Download dialog box.

Forcing Added to Quick Watch Window

Software Enhancement

Firmware Revision/ Software Version 17

The Quick Watch window for version 17 of RSLogix 5000 software now displays the force mask.

Toggle Bit Added to Quick Watch Window

Software Enhancement

Firmware Revision/ Software Version 17

The Quick Watch window for version 17 of RSLogix 5000 software now provides a menu option to toggle bit values.

Verification Warning if I/O Forces are Present

Software Enhancement

Firmware Revision/ Software Version 17

There is a Workstation Option in version 17 of RSLogix 5000 software that enables a warning to be displayed during verification and download when I/O forces are present in the project. This option is enabled by default.

Scripting Available for the ControlFLASH tool, version 7.0

Software Enhancement

Firmware Revision/ Software Version 17

The ControlFLASH tool, version 7.0, provided as a tool with version 17 of RSLogix 5000 software, has been enhanced to allow for command line execution and script execution. Both methods provide status for interrogation on success/fail flash operations.

Verification Warning if Always False Instructions (AFI) are Present

Software Enhancement

Firmware Revision/ Software Version 17

There is a Workstation Option in version 17 of RSLogix 5000 software that enables a warning to be displayed during verification and download if AFI instructions are present in the project. This option is enabled by default.

Ladder Diagram Parameter Display Optimization Options

Software Enhancement

Firmware Revision/ Software Version 17

With version 17 of RSLogix 5000 software, there are additional Workstation Options for displaying operands on a Ladder Diagram instruction faceplate. These options can be used to reduce the amount of space required for display of the ladder code and to improve the readability of instructions.

SFR Instruction Filters Routine Types and Step Names

Software Enhancement

Firmware Revision/ Software Version 17

In version 17 of RSLogix 5000 software, the operand pull-down menus for the Sequential Functional Chart Reset (SFR) instruction have been enhanced to display only SFC type routines and only tags of SFC_STEP data type.

Alarm Grid Display Mode Added to Tag Monitor

Software Enhancement

Firmware Revision/ Software Version 17

In support of FactoryTalk Alarms and Events, version 17 of RSLogix 5000 software now allows alarm tags with data types of ALARM_ANALOG and ALARM_DIGITAL to be displayed in a grid style.

Application Notes RSLinx Software v17

RSLogix 5000 Software 17.x

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

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

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

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.

Application Notes v17

RSLogix 5000 Software 17.x

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

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

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

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

Version 17 of RSLogix 5000 software provides for the ability to import and export projects using an XML format file (.L5X). If earlier versions of RSLogix 5000 software are installed on the same workstation, it may sometimes appear as if you are unable to open an XML project file. This will occur if the currently executing version of RSLogix 5000 software is one which does not support import/export of project files using XML format. Before attempting to open an XML format project file, the currently executing version of RSLogix 5000 software must be one that supports import of XML project files. A particular version of RSLogix 5000 software can be started by doing one of the following: open an archive file (.ACD) that was last saved using the desired version of RSLogix 5000 software, create a new controller and specify that it be created using the desired version of RSLogix 5000 software, or import a text file (.L5K) and specify that it be imported to the desired version of RSLogix 5000 software. (x87808)

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

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

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

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

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

If you currently use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 16, you will need an updated motion database to work with RSLogix 5000 software version 17. To initiate the process of getting the database updated, please email your request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if your current database includes non-Rockwell motors.

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

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

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

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

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

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

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

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

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

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 Logix5550 Controller. The process is simplified if non-DF1 communications is used to select CRC Error Detection in the Logix5550 Controller using RSLogix 5000 software.

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

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

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

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

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

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

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

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

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

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

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