RSLogix 5000 Version 10.05.00 Release Notes – Final System Requirements To use RSLogix 5000 software effectively, your personal computer must meet the following hardware and software requirements. Hardware Requirements The personal computer must meet these minimum requirements: a Pentium 150 MHz processor a minimum of 64 Mb RAM (we recommend 128 Mb) 50 Mb hard disk space free 800 X 600 video resolution any Windows-compatible pointing device Software Requirements You must have installed these software products: The operating system must be either Microsoft® Windows 2000 Professional with Service Pack 1 or with Service Pack 2 or Microsoft® Windows NT® Workstation Version 4.0, with Service Pack 5 or with Service Pack 6a. (RSLogix 5000 software does not support Windows NT 3.51, Windows NT 3.50, Windows 95, nor Windows 3.x operating systems.) RSLinx™ communication software must be installed on the same computer on which the RSLogix 5000 software will be installed. Revision Information Before performing this upgrade, note that Logix5000 controllers and ControlLogix Motion modules in your system must contain a revision of firmware that is compatible with this version of RSLogix 5000. However, previous revisions of network and I/O modules can operate in your system with the new controller firmware contained in this release. Additionally, other software tools such as RSNetWorx for ControlNet and RSLinx have been tested to ensure compatibility with this version of software. Because of this, we recommend that you use the most current versions of these tools. The following tables list the most recent revisions of software and firmware that have been tested and validated together. Software RSLogix 5000 Version RSLinx Version RSNetWorx for RSNetWorx for ControlNet Version DeviceNet Version V10.05.00 / V10.04.00 / 2.30.02 (Build 79) 3.21.00 (Build 43) 3.21.00 (Build 27) V10.03.00 / V10.02.00 / V10.00.00 V9.00.00 2.30.01 (Build 48) 3.00.02 (Build 5) 3.00.02 (Build 11) [3.00 Service Pack 2] [3.00 Service Pack 2] V8.02.00 2.30.00 (Build 47) 3.00.01 (Build 11) 3.00.02 (Build 11) [3.00 Service Pack 1] [3.00 Service Pack 2] V8.00.00 2.30.00 (Build 40) 3.00.00 (Build 27) 3.00.00 (Build 19) V7.02.00 2.20.02 (Build 126) 3.00.00 (Build 27) 3.00.00 (Build 19) V7.00.00 2.20.02 (Build 126) 3.00.00 (Build 18) 18.104.22.168 V6.01.00 2.20.01 (Build 119) 22.214.171.124 126.96.36.199 Service Packs can be downloaded from http://support.automation.rockwell.com. Hardware RSLogix 5000 Version V10.05.00 / V9.00.00 V8.02.00 V8.00.00 V7.02.00 V10.04.00 / V10.03.00 / V10.02.00 / V10.00.00 Controllers ControlLogix L1 – Series A, L1 – Series A, L1 – Series A, L1 – Not applicable L1 – Series A, 1756-L1, -L53, -L55, Version 10.24 Version 9.13 Version 8.20 L53 – Not applicable Version 7.11 -L63 L53 – Series A, L53 – Series A, L53 – Series A, L55 – Series A, L53 – Series A, Version 10.24 Version 9.13 Version 8.14 Version 8.16 Version 7.7 L55 – Series A, L55 – Series A, L55 – Series A, L55 – Series A, Version 10.28 Version 9.14 Version 8.20 Version 7.9 L63 – Series A, Version 10.32 FlexLogix Series A, Not applicable Series A, Not applicable Series A, 1794-L33, -L34 Version 10.16 Version 8.12 Version 7.9 SoftLogix Series A, Not applicable Series A, Not applicable Series A, 1789-L60 Version 10.02 Version 8.02 Version 7.02 CompactLogix L20 – Series A, Not applicable L20 – Series A, Not applicable L20 – Series A, 1769-L20, -L30 Version 10.13 Version 8.14 Version 7.17 L30 – Series A, L30 – Series A, Version 10.13 Version 8.14 DriveLogix5720 Series A, Not applicable Not applicable Not applicable Not applicable PowerFlex 700S Version 10.16 Communication Modules 1756-CNB Series D, Series D, Series D, Series D, Series D, Version 5.27, Version 5.22, Version 5.22, Version 5.22, Version 5.22, Series B, Series B, Series B, Series B, Series B, Version 2.27, Version 2.27, Version 2.27, Version 2.27, Version 2.27, Series A, Series A, Series A, Series A, Series A, Version 1.19 Version 1.19 Version 1.19 Version 1.19 Version 1.19 1756-DNB Series A, Series A, Series A, Series A, Series A, Version 3.010 or Version 3.007 or Version 3.007 or Version 3.005 or Version 3.005 o 2.008 2.008 2.008 2.008 2.008 1756-DHRIO Series B, Series B, Series B, Series B, Series B, Version 2.21 Version 2.21 Version 2.21 Version 2.19 Version 2.19 1756-ENET Series B, Series B, Series B, Series B, Series B, Version 2.6, Version 2.6, Version 2.6, Version 2.6, Version 2.6, Series A, Series A, Series A, Series A, Series A, Version 1.18 Version 1.18 Version 1.18 Version 1.18 Version 1.18 1756-ENBT Series A, Not applicable Not applicable Not applicable Not applicable Version 1.30 Motion Modules 1756-M02AE Series A, Series A, Series A, Series A, Series A, Version 5.2 Version 5.2 Version 3.10 Version 3.10 Version 3.8 1756-M08SE Series A, Series A, Not applicable Not applicable Not applicable Version 2.10 Version 2.9 Firmware Note that all of the modules supported by RSLogix 5000 utilize Flash-ROM for the storage of firmware. If you possess a module that requires a firmware change, the ControlFLASH software tool can be used to perform an update to this Flash-ROM. This software tool and the firmware images for most of the supported modules are contained on a CD- ROM or floppy disks shipped with RSLogix 5000. Please review the manual associated with this tool for additional information and assistance in performing a Flash-ROM update. Starting with RSLogix 5000 V10.00, the ControlFLASH tool can be accessed from within RSLogix 5000 (see the Tools menu) or the firmware can be updated automatically as part of the project download process. In addition, Rockwell Software Technical Support has created a web site from which you can download firmware images for ControlLogix products. Go to http://support.automation.rockwell.com/ControlFlash/ for a matrix detailing the versions of firmware that were released with each of the versions of RSLogix 5000 software, and to download the ControlFLASH firmware kits and release note documents. Note that you will need your RSLogix 5000 serial number to complete the download. Electronic Data Sheets The version of RSLinx provided with RSLogix 5000 includes an updated set of Electronic Data Sheet (EDS) files for Rockwell Automation products. Installing this software ensures that RSLinx and RSNetWorx will be able to work with new versions of firmware. These EDS files are also available separately by contacting technical support (440-646- 5800) or via the internet (http://www.ab.com/networks/eds/) and can be install using the EDS Hardware Installation Tool located in the RSLinx folder in the Windows Start Menu. Choosing Your RSLogix 5000 Package RSLogix 5000 is scalable software solution, used to program and configure any of the Logix5000 family of controller products. Depending on the functionality required one or more product catalog numbers might be needed to acquire the appropriate software functionality. The following table will help you to determine which RSLogix 5000 package is best suited for your application needs. RSLogix 5000 Enterprise Series Bundle Mini Edition Standard Edition Standard / Network Fu Edition Catalog Number 9324-RLD200xxE1 9324-RLD300xxE1 9324-RLD300NXxxE1 9324 Controllers Supported CompactLogix5300 CompactLogix5300 CompactLogix5300 Comp FlexLogix5400 FlexLogix5400 FlexLogix5400 Fle ControlLogix5500 ControlLogix5500 Cont DriveLogix5700 DriveLogix5700 Driv SoftLogix5800 SoftLogix5800 So Ladder Diagram (LD) Fully Supported Fully Supported Fully Supported Full Function Block Diagram (FBD) and Advanced Upload/Download Included Upload/Download Included Upload/Download Included Process and Drive control blocks Editor Available Separately Editor Available Separately Editor Available Separately Full (9324-RLDFBDxxE1, or via 9324-RLDMLPE) FBD PIDE Autotune (requires FBD option) Available Separately Available Separately Available Separately Availa (9323-ATUNExxE1) Sequential Function Chart (SFC) Upload/Download Included Upload/Download Included Upload/Download Included Full (9324-RLDSFCE, or via 9324-RLDMLPE) Editor Available Separately Editor Available Separately Editor Available Separately Structured Text (STX) Upload/Download Included Upload/Download Included Upload/Download Included Full (9324-RLDSTXE, or via 9324-RLDMLPE) Editor Available Separately Editor Available Separately Editor Available Separately Miscellaneous Features: Highly integrated Motion Upload/Download Included Fully Supported Fully Supported Full Graphical Trending N/A Fully Supported Fully Supported Full Drive Executive Available Separately Lite Included Lite Included Li RSNetWorx for ControlNet & DeviceNet Available Separately Available Separately Included Availa (9357-CNETL & 9357-DNETL) RSLinx Lite Included Lite Included Lite Included Li Miscellaneous Files & Tools: Electronic manuals (PDF) Included Included Included Tutorial / Quick Start Included Included Included ControlFLASH w/Controller Firmware Included Included Included FBD ActiveX Faceplates Included Included Included Logix CPU Security Tool Included Included Included Routine Source Protection Tool Included Included Included PLC-5/SLC-500 Translation Tool Included Included Included RSView Demo (50 Tags / 2 Hour Limit) Available Separately Available Separately Available Separately Availa 1756-MVI Development Toolkit Available Separately Available Separately Available Separately Availa Tag Custom Data Monitor Tool Included Included Included Tag Data Upload / Download Tool Included Included Included Upgrades Mini to Standard 9324-RLD2U3xxE1 Standard to Professional Standard to Professional Full t 9324-RLD3U7xxE1 9324-RLD3U7xxE1 9324 Mini to Full 9324-RLD2U6xxE1 Mini to Professional 9324-RLD2U7xxE1 RSLogix 5000 Support Renewal 9324-RLD200xxS1 9324-RLD300xxS1 9324-RLD300xxS1 & 2 9324-R Reinstate 9324-RLD200xxR1 9324-RLD300xxR1 9324-RLD300xxR1 & 2 9324-R 1. Replace xx with the appropriate language code where: DE = German, EN = English, ES = Spanish, FR = French, IT = Italian, PT = Portuguese. 2. Separate support agreement required for RSNetWorx and RSLinx Professional New Features In This Release The following new features and functionality have been added to this release of RSLogix 5000. RSLogix 5000 Enterprise Series (Multiple Revision Support) To support multiple controller versions, RSLogix 5000 makes use of capabilities provided with Windows 2000. While Windows NT4 is still supported, you will be limited to a single controller version if you attempt to run the software on a personal computer running Windows NT4. In addition to supporting Version 10.00 into the future, RSLogix 5000 can also support the installation of one version prior to Version 10.00 (Version 9.00 or earlier) on a computer running Windows 2000. Version 10.00 of RSLogix 5000 provides the infrastructure to support multiple controller versions used by future releases of RSLogix 5000. While Version 10.00 of RSLogix 5000 is still limited to working with only Version 10.00 Logix5000 controllers, this version of controller will continue to be supported in future releases of RSLogix 5000. During installation of RSLogix 5000, you are presented with an option to install support for the versions of controllers you need to use. The software then ensures all of the appropriate software library files, dialog screens, and help files associated with each controller are installed. RSLogix 5000 then ensures that the appropriate portions of the software are used based on the controller version defined in the application data base file (ACD) or by detecting the controller version when attaching to a controller. Controller Firmware Updates from RSLogix5000 When you attempt to download a project created by RSLogix 5000 into a controller, RSLogix 5000 checks to determine if the controller version is compatible with the programming software. In the past when an incompatibility with the controller firmware was detected, you were required to manually locate the ControlFlash tool and perform the firmware update. RSLogix 5000 now provides the ability to locate the firmware and automatically perform the controller firmware update as part of the download process. RSI Security Server Password Protection The RSI Security Server provides centralized user authentication for Logix controller resources. This tool leverages the Windows NT / 2000 user login with password to verify the abilities each user has to modify the contents of a Logix controller, however the password is not stored in the controller. Version 10.00 of RSLogix 5000 provides the ability to work with the security information provided from security server to provide password protection for the Logix5000 family of controllers. The initial support for Security Server in RSLogix 5000 allows you to limit access to maintenance operations such as viewing programs and modifying or forcing tag values, or to only view the controller’s contents, or completely block user access to the controller or its offline file. This integration extends beyond the ability of previous products by storing protection information in the controller to prevent access from a workstation that is not running Security Server. Function Block Diagram Subroutine Support The Function Block Diagram (FBD) language now includes three new blocks: Jump to Subroutine (JSR), Subroutine (SBR) and Return (RET). Subroutines in FBD extend the multi-page capabilities to encapsulate and organize code. They provide better program reuse, increase program readability, and permit FBD routines to operate as functions for LD and FBD languages. The Jump to Subroutine (JSR) passes execution to another routine. This permits a routine created in either a Ladder Diagram (LD) or a FBD to be called from within an FBD routine. The JSR block also has the ability to pass values to and from the called routine and wire them to other blocks. The Subroutine (SBR) block introduces new values or parameters to an FBD routine that are passed from the calling routine. These parameters can then be linked to other blocks in the FBD algorithm via wired connections. Once the FBD routine completes execution, the Return (RET) block is used to return control back to the calling routine, including optional parameters In all three cases (JSR/SBR/RET), input/output parameters are passed by value (a copy is made). The blocks support both atomic and structure tags. However, only atomic data types (BOOL, INT, SINT, DINT, REAL) can be wired to other blocks. Structures are stored into memory where their contents can be utilized with the Input Reference (IREF) block. Function Block Diagram Enhanced PID Autotuning The Function Block Diagram (FBD) Enhanced PID (PIDE) block now provides a built-in autotuning capability. PIDE Autotuning is available as an option to the RSLogix 5000 Mini, Standard and Professional bundles. By using RSLogix 5000, you can configure the simple, open loop autotuning built into the PIDE instruction. Once configured, you can perform autotuning from the PIDE Property dialog in RSLogix 5000, from the ActiveX faceplate for the PIDE block, or from a custom screen created on an operator interface station such as a PanelView. ControlLogix5563 Controller Support RSLogix 5000 now supports the ControlLogix5563 controller for program development when creating a new project. The Logix5563 (1756-L63) controller extends the capabilities of the ControlLogix family by increasing performance, adding a built-in floating point math co-processor, and increasing memory capacity. Programs developed for previous ControlLogix5550 or 5555 controllers may be run on the new Logix5563 by changing the processor type in the Controller Properties dialog. The increased controller capabilities make the Logix5563 platform well suited for process, motion or drive control applications that make extensive use of floating point math. New ControlLogix5555 Models There are two new memory options for the ControlLogix5555 controller. The 1756-M12 offers 750 Kbytes of memory and the 1756-M22 offers 750 Kbytes of RAM plus nonvolatile memory. The memory boards are available in combination with a processor as 1756-L55M12 and 1756-L55M22. They are also available as separate catalog numbers for the memory boards only. Before you replace an existing memory board (1756-M13, -M14, -M16, M23, or -M24) with the -M12 or -M22 you must update the firmware of the controller to Revision 10. Nonvolatile Memory for Additional Controllers These additional controllers include built-in, nonvolatile memory capable of storing user programs and data, ControlLogix5555 with M22, FlexLogix5433, CompactLogix5320 and 5330, and DriveLogix5720 and 5725. Nonvolatile memory removes the need to have a battery to retain programs through power cycles. RSLogix 5000 permits you to store the contents of RAM memory into flash memory and then configure the processor to transfer from Flash memory back to RAM memory on startup or when the RAM memory is found to be empty. Data values retain their state at the time they were stored into flash memory. To configure this feature in RSLogix 5000, navigate to the Controller Properties dialog Nonvolatile Memory tab when online with the controller. Instruction Set Enhancements - ASCII String Extensions The list of instructions that support ASCII string operations has increased by extensions to two existing instructions Compare (CMP) and File Search/Compare (FSC) and the inclusion of two new instructions Upper Case (UPPER) and Lower Case (LOWER). The Ladder Diagram CMP and FSC instructions now include support for ASCII Strings. The CMP instruction allows two strings to be compared using an operator such as EQU, NEQ, GRT, GEQ, LES, and LEQ. This avoids the need to utilize specialized ASCII instructions and improves code readability. The FSC instruction locates the position in an array where a string is found. This instruction supports arrays of strings or an array using a UDT that contains a string as a member of the structure. This provides the ability to perform database lookup operations based on a string of characters. The new Ladder Diagram UPPER and LOWER instructions convert the case of an ASCII string. The UPPER instruction converts all characters in a string to upper case. Similarly, LOWER changes all characters to their lower case equivalent. FLEX I/O Rail CIP Messaging This version of the Logix5000 expands the MSG instruction to perform operations that require the ability to send and receive messages via the FLEX I/O interface bus. Third party devices such as the Prosoft Multi-vendor Interface (MVI) module and Allen-Bradley specialty products such as the 1203-FM1 drive communications Scanport module require this capability. The Prosoft MVI module provides a serial interface that can be programmed to interface to different products and/or protocols. The 1203-FM1 provides the ability for a Logix controller to interface with a drive’s Scanport interface to perform control functions. This permits the ControlLogix5500 and FlexLogix5400 to utilize this module for distributed serial communications in a control system. SERCOS Drive Support with 1756-M08SE Module Starting with Version 9.00, RSLogix 5000 supports the use of 1394C-SJTxx-D and 2098-DSD-xxxx SERCOS Interface digital servo drives. The digital servo drives receive configuration and command signals from the 1756- M08SE module and provide position, velocity and diagnostics information to it over a synchronous fiber optic ring. A maximum of eight (8) axes can be configured per 1756-M08SE module installed in the system. These axes may be used in combination with axes configured on 1756-M02AE modules to address a wide range of motion application needs. The process of configuring axes has also been improved, with simple to use catalog number selection lists that provide default configuration values for numerous parameters. When configuring SERCOS axes on a 1394C-SJTxx- D or 2098-DSD-xxxx drive, all supported and compatible bus regulator, axis amplifier, and motor catalog number selections are automatically displayed in the user interface. Module Support (Catalog Numbers 1756, 1794, 1769, and Other) The RSLogix 5000 programming software now supports configuration of these modules: 1756 1756-M08SE 8 Axis SERCOS Interface 1794 1794-ID2/B – 2 Channel 24V DC Incremental Encoder 1794-IP4/B – 4 Channel 24V DC Frequency Counter 1794-IT8/A – 8 Channel 24V DC Thermocouple/mV Analog Input 1769 1769-IF4XOF2/A – 4 Channel Input/2 Channel Output Low Resolution Analog 1769-IF4/B – 4 Channel Current/Voltage Analog Input 1769-IQ6XOW4/B – 6 Point 24V DC Sink/Source Input, 4 Point AC/DC Relay Output 1769-OA8/B – 8 Point 100V-240V AC Output 1769-OB16/B – 16 Point 24V DC Output, Source 1769-OB16P/B – 16 Point 24V DC Protected Output 1769-OF2/B – 2 Channel Current/Voltage Analog Output 1769-OV16/B – 16 Point 24V DC Output, Sink 1769-OW8/B – 8 Point AC/DC Relay Output 1769-OW8I/B – 8 Point Isolated AC/DC Relay Output Other 1407-CGCM – Combination Generator Control Module WebPak 3000 – WebPak 3000 DC Drive Enhancements In This Release The following enhancements to existing features have been made in this release of RSLogix 5000. Message (MSG) Enhancements - This version includes numerous enhancements to the messaging capabilities of Logix5000. These enhancements provide better programmatic control of the operation of the Message (MSG) instruction and improved message debug tools. Programmatic reconfiguration of communications path, node addresses, message parameters, and source/destination data location permits a single message to target multiple devices through program control. This reduces the number of MSG instructions required for message intensive systems. Programmatic bumpless reconfiguration of I/O modules allows you to reconfigure an I/O module’s settings without resetting the outputs, providing better control of I/O and reducing the effort needed to support advanced modules. SLC floating point and long integer data types ("F” and "L” files) are now supported. The SLC typed read/write message types permit Logix5000 to communicate using these data types with a SLC. Although the SLC string data type (“A” files) are not directly supported, Logix5000 can communicate with a SLC using a PLC5 typed message for strings. Additionally, products that are able to read these types of data from an SLC can now perform similar operations to a Logix5000. Enhanced message debug tools provide 4-byte extended error codes which reduce the ambiguity in error codes and provide an indication of which module generated the run-time error codes. FlexLogix5400 DeviceNet Support - With the combined release of this version of RSLogix 5000 and the NetLinx DeviceNet Scanner card (1788-DNBO), the FlexLogix5400 controller is able to utilize DeviceNet to communicate to distributed I/O devices. This complements the ControlNet communications support already available for the FlexLogix controller. Swap Byte (SWPB) Instruction - The new Ladder Diagram Swap Byte (SWPB) instruction is useful for re-arranging a tag’s contents so that the value is interpreted properly. In some cases, storage of values in memory are different between Logix controllers and 3rd party products. This instruction provides a way to swap the contents of bytes within an INT, DINT, or REAL data type tag. Three modes of operation are provided to reverse the order (16#ABCD - >16#DCBA), perform a word swap (#ABCD -> 16#CDAB), or to perform a high/low byte swap (16#ABCD -> 16#BADC). In addition to operating on stand-alone tags, the SWPB instruction can also utilize array indexing coupled with the JMP/LBL or FOR/JSR instructions to operate on tables of information. Download Performance Improvement – The download communication processing has consolidated multiple interactions into a single interaction to reduce the amount of time required to perform program downloads. Programs that contain a large quantity of tags will see a significant decrease in the time required for these operations. Export Performance Improvement – The export processing has been optimized to reduce the amount of time required to perform a “Save As .L5K” operation. Programs that contain a large quantity of tags with comments will see a significant decrease in the time required exporting. Jump to Subroutine (JSR) Support for BOOL Data Type - This extension of the existing JSR instruction adds to the numeric and structured parameter passing support to include BOOL (bit) data type tags. This eliminates the need to develop code that copies bits into a numeric tag prior to performing a subroutine call. Support for 1771 Analog / Block Transfer over ControlNet - Extends Logix5000 1771 I/O ControlNet support to include analog and advanced modules that utilize block-transfer communications. The existing MSG instruction can now initiate Block Transfer Messaging through 1771-ACNs to 1771 I/O modules, similar to communications over Remote I/O (RIO). Toggle Bit in Data Monitor – The ability to toggle a bit has been added to the Data Monitor. This feature is available for BOOL data type tags only and can be accessed from the pop-up menu or by using Ctrl + T. Support the Windows Keyboard Application Key – Support for the Windows keyboard application key has been implemented in these areas Controller Organizer, Tag Editor, Data Monitor, Ladder Editor, FBD Editor, Data Type Editor, and Cross Reference. The application key located below the right-hand Shift key, displays the context-sensitive menu for the selected object. The same pop-up menus can be displayed by using Shift + F10. Quick view pane – The Controller Organizer has been enhanced to include a quick view pane at the bottom of the view. This display pane provides status information based on what object is selected in the Controller Organizer. New axis types – There are now four motion axis data types where there was only one type in prior releases. The new axis types are AXIS_CONSUMED, AXIS_SERVO, AXIS_SERVO_DRIVE, and AXIS_VIRTUAL. This architectural change was necessary to facilitate the addition of new types of motion axes in this release and in future releases. Axis configuration dialogs – The axis configuration dialogs have been redesigned for better organization and grouping of configuration parameters. Motion group icons – New icons for motion groups and axes have been added to the Controller Organizer. This provides a quick visual display of all axes that are assigned to a motion group. Assigning and reassigning axes can be accomplished using drag and drop or copy and paste. Quick access to configuration properties, faults, status, etc. are accessible via context menus for axes. Direct template data access - This feature permits direct access and use of commonly used axis data with instructions in your program without having to store or retrieve these values through separate GSV/SSV instructions. Axis parameter access using GSV/SSV – The GSV/SSV instructions now provide organized access to axis parameters based on whether the parameter is a configuration, status, or interface attribute. Important Changes In This Release The following items explain changes that have been made for this release in the way that RSLogix 5000 software works, compared to previous releases. Controller Memory Changes This revision of Logix5000 controllers requires more memory than previous revisions: Before upgrading to this revision, check the amount of unused memory that you have in the controller. To upgrade to this revision you may have to add an expansion memory card to the controller or use a larger memory card. To estimate the additional memory that your project will require, use the following table. For additional information about controller memory issues refer to the Knowledgebase document G19984 at http://support.automation.rockwell.com Additional memory to upgrade to firmware revision 10.x If you have this firmware revision (add all that apply): Component Increase per instance 9.x or earlier Tag that uses MESSAGE type 376 bytes 8.x or later Axis tags (-21600 bytes) 8.x or earlier Output cam execution targets 5404 bytes Motion group 32 bytes 7.x or earlier Project 1050 bytes Tags 0.55 bytes (average) Axis tags 21600 bytes Messages that: 2000 bytes Transfer more than 500 bytes of data and Target a controller in the same chassis 6.x or earlier Base tags 24 bytes Alias tags 16 bytes Produced and consumed tags DINT data type 12 bytes REAL data type 12 bytes 6.x Routines 68 bytes 5.x or earlier Routines 116 bytes Import Export Changes Beginning with the V9.00 release, the Import Export Version number will be interpreted as a Major Revision and a Minor Revision (major.minor). Each version of RSLogix 5000 will export *.L5K files with specific IE Version numbers. RSLogix 5000 will import any *.L5K file with the same Major Revision number and the same or lower Minor Revision number. The Major Revision will be incremented when there is a significant change that effects compatibility with previous versions. The Minor Revision will be incremented whenever there is a change in the file format (a new module, an attribute is added, the set of options for an attribute is changed, etc.). Generally, the Minor Revision will be incremented for each release. When attempting to import or paste between versions if the IE Version is invalid an error message will be displayed in the results window. If the major or minor revision number is larger than accepted the message “Error Line xxx: Invalid IE Version number. Can not import/paste into older version of RSLogix 5000” will be displayed. If the major revision number is smaller than accepted the message “Error Line xxx: Invalid IE Version number. See Release Notes for more detail” will be displayed. The Import Export version number has been changed to 2.1. If you have export files (*.L5K) that were created in previous versions of RSLogix 5000 and you attempt to import them in V10.00, an error will be generated. The error message is "Failed to open file *.L5K. Syntax error found while scanning import file." To work around the problem, edit the *.L5K file and change the line IE_VER := x.x;, where x.x may be 1.0 , 1.1, 1.2, or 2.0 to IE_VER := 2.1; save the file and retry the import. The major revision of the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed to 5. If you have export files (*.L5K) that were created in previous versions of RSLogix 5000 and you attempt to import them in V10.00, an error will be generated. The error message is "Error: Line xxx: Invalid catalog number." To work around the problem, edit the *.L5K file, find the MODULE section for the 1756-M02AE and change the line Major := x.x;, where x.x may be 1, 2, or 3 to Major := 5; save the file and retry the import. In addition to the import export changes described above, there have been many changes to motion axis tags and axis object attributes that will result in warning messages when importing older version *.L5K files. These warning messages will be in the format: Warning: Line ###: An error occurred while setting attribute <name_of_attribute> of tag <name_of_axis_tag> (Couldn’t be found). Refer to the descriptions of these motion axis tag and axis object changes elsewhere in the release notes for clarification. The same type of warning message will be displayed if you import objects that previously accepted NA as values. In this release, the not applicable values are exported as <NA>. Motion Objects and Instructions Changes The introduction of SERCOS functionality in the V9.00 release required changes to the motion objects and motion instructions that have been in place since the initial release of RSLogix 5000 up to version 8.02. The changes are in four areas and include: Axis tag member name changes Axis object attribute name changes Axis configuration value changes Motion Instruction changes Axis tag member name changes Some motion axis member name changes have been made to better describe the underlying function. A number of older names were consolidated into a single name in order to simplify the user interface. Some of the older names are no longer supported in the new implementation. See Tables 1 and 2 below. Motion project files which were created with RSLogix 5000 V6.x, V7.x, or V8.x software will be automatically converted in RSLogix 5000 V10.00 software by opening the project (*.ACD) file. The new tag format and attribute names used in V10.00 will be applied in most cases. If your project contains function block diagram routine references to the modified or obsolete attribute names you will have to manually correct them. To find the affected references, in RSLogix 5000 select Logic -> Verify -> Controller and then select Search -> Next Error to navigate to the errors. Table 1 – Axis Tag Member Name Changes Previous Version Name V9.00 / V10.00 Name ACAsyncConnFault ConfigFault ACSyncConnFault ControlSyncFault PotrvlFault PosSoftOvertravelFault NotrvlFault NegSoftOvertravelFault PosErrorFault PositionErrorFault EncCHALossFault FeedbackFault EncCHBLossFault FeedbackFault EncCHZLossFault FeedbackFault EncNsFault FeedbackNoiseFault SyncConnFault ModuleSyncFault HardFault ModuleHardwareFault ServoActStatus ServoActionStatus OutLmtStatus OutputLimitStatus PosLockStatus PositionLockStatus TestStatus ProcessStatus TuneStatus ProcessStatus HomeSwitchStatus HomeInputStatus EventStatus AxisEvent RegEvArmStatus RegEvent1ArmedStatus RegEvStatus RegEvent1Status -n/a RegEvent2ArmedStatus -n/a RegEvent2Status WatchEvArmStatus WatchEventArmedStatus WatchEvStatus WatchEventStatus HomeEvArmStatus HomeEventArmedStatus HomeEvStatus HomeEventStatus AxisTypeStatus ConfigUpdateInProcess PosUnwindStatus ConfigUpdateInProcess MaxPTrvlStatus ConfigUpdateInProcess MaxNTrvlStatus ConfigUpdateInProcess PosErrorTolStatus ConfigUpdateInProcess PosLockTolStatus ConfigUpdateInProcess PosPGainStatus ConfigUpdateInProcess PosIGainStatus ConfigUpdateInProcess VelFfGainStatus ConfigUpdateInProcess AccFfGainStatus ConfigUpdateInProcess VelPGainStatus ConfigUpdateInProcess VelIGainStatus ConfigUpdateInProcess OutFiltBwStatus ConfigUpdateInProcess OutScaleStatus ConfigUpdateInProcess OutOffsetStatus ConfigUpdateInProcess FricCompStatus ConfigUpdateInProcess PotrvlFaultActStatus ConfigUpdateInProcess PosErrorFaultActStatus ConfigUpdateInProcess EncLossFaultActStatus ConfigUpdateInProcess EncNsFaultActStatus ConfigUpdateInProcess DriveFaultActStatus ConfigUpdateInProcess ServoConfigBitsStatus ConfigUpdateInProcess -n/a SERCOSRingFault -n/a Reg1InputStatus -n/a Reg2InputStatus -n/a Registration1Position -n/a Registration2Position -n/a Registration1Time -n/a Registration2Time -n/a AuxFeedbackResolution -n/a MotorFeedbackResolution Table 2 – Obsolete Axis Tag Member Names Previous Version Name MotionFault UpdateStatus MotionFaultBits ServoConfigurationUpdateBits ServoStatusUpdateBits ServoConfigurationBits Axis object attribute name changes Several of the AXIS object attributes have had name changes and in some cases GSV/SSV access changes. See Table 3 below. Table 3 – Axis Object Attribute Name Changes (with GSV/SSV access) Previous Version Name GSV/SSV Access V9.00 / V10.00 Name GSV/SSV Access C2CMapTableInstance GSV Only C2CmapInstance GSV Only RegistrationPosition GSV Only Registration1Position GSV Only TestStatus GSV Only ProcessStatus GSV Only TuneStatus GSV Only ProcessStatus GSV Only EffectiveInertia GSV Only TuneInertia GSV Only TuneVelocityBandwidth GSV Only VelocityServoBandwidth GSV & SSV ServoEventBits GSV Only AxisEventBits GSV Only HomeSequenceType GSV & SSV HomeSequence GSV & SSV MotionConfigurationBits GSV & SSV HomeConfigurationBits GSV & SSV OutputFilterBandwidth GSV & SSV OutputLPFilterBandwidth GSV & SSV OutputScaling GSV & SSV TorqueScaling or VelocityScaling GSV & SSV EncoderLossFaultAction GSV & SSV FeedbackFaultAction GSV & SSV EncoderNoiseFaultAction GSV & SSV FeedbackNoiseFaultAction GSV & SSV MotorEncoderTestIncrement GSV & SSV TestIncrement GSV & SSV -n/a -n/a AuxFeedbackResolution GSV Only -n/a -n/a MotorFeedbackResolution GSV Only Axis configuration value changes Some of the configuration values have been changed to provide a more consistent set of units. The configuration values entered as part of the motion configuration will be automatically updated as part of the database conversion from previous versions of RSLogix 5000. If you referenced these values in your application documentation, these references may need to be changed to account for the change in values. In addition, if you accessed these attributes in GSV or SSV instructions and converted your project to V9.00 there will be Program Conversion Errors (PCE) in your routines indicating the scaling factor changes that you need to be aware of. Once you have accounted for the scaling factor changes, the PCE instructions must be deleted in order for your routine to verify correctly. See Table 4 below. Table 4 – Axis Configuration Value Conversion Changes Previous Version Previous V9.00 / Conversion Factor PCE_MOTION_## Attribute Name Version Units V10.00 Units Error Code 2 2 EffectiveInertia MilliVolts/ KCPS %/ MCPS * 10 01 FrictionCompensation Volts % * 10 02 -5 OutputScaling (velocity) Millivolts/KCPS %/Pos Units * 10 * Conversion 03 per Sec Constant 2 -5 OutputScaling (torque) Millivolts/KCPS %/Pos Units * 10 * Conversion 03 2 per Sec Constant PositionProportionalGain 1/msec 1/sec * 1000 04 TuneSpeedScaling MilliVolts/ KCPS %/ KCPS * 0.01 05 VelocityProportionalGain 1/msec 1/sec * 1000 06 Motion Instruction changes Four motion instructions have been modified. These include the MAR, MDR, MGPS, and MGS. The first two instructions have had a new operand added. This means that when an application program is migrated to V9 or beyond, they will fail verification with an error message that these instructions are missing an operand. Operands for the last two instructions were either added or modified. See Table 5 below. Table 5 – Motion Instruction Changes Instruction V9.00 / V10.00 Change MAR – Motion Arm Registration Added Input Number operand MDR – Motion Disarm Registration Added Input Number operand MGS – Motion Group Stop Removed Inhibit operand and replaced with Stop Mode operand If Inhibit was programmed as Disabled, the new Stop Mode will be Fast Stop If Inhibit was programmed as Enabled, the new Stop Mode will be Fast Disable MGPS – Motion Group Programmed Stop Instruction removed and replaced by MGS If MGPS was programmed, the MGS replacement will be Stop Mode Programmed Anomalies Corrected In This Release RSLogix 5000 A few product deficiencies discovered in Version 10.04 have been corrected in Version 10.05. These include: Module Info page does not identify Flex modules in V10 if V12 or V13 is also installed (x47507) Display warning in the output window if pending edits exist on download (x46955) In previous releases pending edits were automatically accepted before the download. Installing and running V10.04 causes Avaya Message Manager 5.0 to fail to run (x46466) A few product deficiencies discovered in Version 10.03 have been corrected in Version 10.04. These include: Search and Replace does not find all JSR parameters in LD routines (x45414) Hidden members re-referenced for User-Defined Types with addition of new UDT members (x45323) Function block Ramp Soak (RMPS) Initialization ignores segment 0 soak time (x43952) Fatal Error clicking Update Firmware push button (x43899) Scrolling with wheel mouse causes problems with Ladder Editor display (x42338) Importing a newer version L5K file in an older version generates a syntax error (x42255) AutoFlash is not available when minor revision is less than lock step requires (x41874) Output Cam Editor disable OK button in run mode, same as Cam Profile Editor (x41807) Support processor series/major revision identification for AutoFlash (x38761) Go Online, Upload, or Download push buttons not enabled in Who Active dialog or error “Failed to go online with the controller. Unsupported Processor type.” for controllers not supported in current version of RSLogix 5000. (x28918) A few product deficiencies discovered in Version 10.02 have been corrected in Version 10.03. These include: Alias target of an I/O tag can be edited to point to the wrong slot of the rack image (x39268) Fatal Error uploading project from 1756-L63 controller after type changed from 1756-L55 (x38934) Uploading using LogixServices doesn't merge, so comments are lost (x38133) Misleading firmware incompatibility message when connecting online over intermediate communication paths (x38129) Several product deficiencies discovered in Version 10.00 have been corrected in Version 10.02. These include: Fixed a problem with online editing ladder routines in a 1756-L63 controller (x33656) Corrected a Fatal Error during upload from a 1756-L63 controller (x33654) Added an automation interface for RSMACC (x33507) Corrected a problem with duplicate input and output parameters on JSR instructions in FBD routines (x33421) Fixed a Fatal Error going online after a download (x33373) Added activation key support for the Full package and PIDE Autotune in the Professional package (x33301) Corrected a problem switching versions when creating a V11 project from within V10 (x32783) Fixed a problem displaying the splash screen (x32623) Corrected an attribute list error on the serial port after multiple downloads (x32615) Fixed the source protection algorithm for Windows XP (x32614) Corrected the database file compression algorithm (x32613) Fixed a problem with the major revision check for Import (x32611) Many product deficiencies have been addressed since Version 8.02. The most significant of these include: Fatal Error when deleting an open FBD routine referenced in a Ladder Diagram JSR (x27957) Fatal Error when you open a FBD routine, print it, then edit it (x26735) Importing new tags loses descriptions when discard on collision is selected (x23026) RSLogix5000 locks up when searching large program file (x27813) Accessing the Sheet Tool Bar in the FBD Editor with an incomplete wire causes Fatal Error (x25562, x25138) Deleting tag elements in the Tag Editor with a filter of COUNTER or TIMER causes a Fatal Error (x23806, x22223, x22629) Downloading an FBD IREF with alias to boolean array member of a user-defined type tag encounters unexpected error and ultimately Fatal Errors (x23897) Excessive embedded cross reference information in Ladder Logic listings (x23021) RSLogix 5000 Fatal Error when right click in RSTrend window (x22503) Source Protection not encrypted when viewed with traffic analyzer (x21919) Deleting FBD routine when in editor causes Fatal Error (x21742, x21620) Tag references to array elements are changed after upload (x21598) Closing RSLogix 5000 after adding FBD elements causes Fatal Error in Windows 2000 (x19332) Logix5550 / Logix5553 / Logix5555 Refer to the Firmware Release Notes for the Logix5000 family of controllers (Publication 1756-RN004N-EN-E – December 2001) to review the most significant problems that have been fixed. Known Anomalies Keep the following safety concerns/limitations in mind when using this release. Attention – Online Editing Ladder Logic Routines in 1756-L63 Controller If you have a 1756-L63 controller, do not edit its ladder logic routines while online. Online edits could cause serious injury to personnel or damage to equipment. To edit the ladder logic of a 1756-L63 controller while online, first complete the following actions: 1. Update your RSLogix 5000 software to the following revision: If you have this version of Update it to this RSLogix 5000 software: version: 10.00 10.02 or later 11.00 11.11 or later 11.01 11.10 2. While offline, open the RSLogix 5000 project for the controller. 3. Save the project. 4. Download the project to the controller. If you perform an online edit with revision 10.00, 11.00, 11.01, or 11.10 of RSLogix 5000 software, unpredictable controller operation could occur. This may include, but is not limited to: watchdog time of a task expires (major fault type 6, code 1) controller failure (solid red OK LED) Multiple Revision Support with V11.10 and V10.00 During the testing of RSLogix 5000 Version 11.10, a couple of anomalies were detected with Version 10.00 that may result in difficulties working with projects and controllers with these two revisions. A new Version 10.02 was created to address these issues. The following provides additional information on these anomalies: Creating a new V11 project from within V10 fails to switch to V11. If you are using V10.00 and want to create a new V11 project, close RSLogix 5000 V10.00 and run V11.10 directly by navigating to C:\Program Files\Rockwell Software\RSLogix 5000\ENU\v11\Bin and double-clicking on RS5000.exe. (x32783) The V10.00 Source Protection tool does not operate correctly on Windows XP due to changes Microsoft made to the default encryption methods used in Windows XP. To address this issue, a new version of the Source Protection tool is included with Version 10.02. (x32614) When switching between V11 and V10 projects, the splash screen is displayed. While this does not effect the operation, the splash screen may result in confusion about which software is installed and running. This is corrected in Version 10.02. (x32623) RSLogix 5000 Version 11.11 also provides support for new purchasable options, created a new RSLogix 5000 bundle, and modified the feature set of an existing RSLogix 5000 bundle. Because you may purchase these options and use both V10 and V11, Version 10.02 was modified to accommodate these new options and bundle changes. The following list provides additional information on these changes: The new RSLogix 5000 multi-language pack 9324-RLDMLPE enables Function Block Diagram (FBD) in V10.02. The new RSLogix 5000 Full Edition 9324-RLD600ENE is supported by V10.02 with Function Block Diagram (FBD) and Ladder Diagram (LD). The RSLogix 5000 Professional Edition 9324-RLD700NXENE was modified to include the FBD PIDE Autotune feature. The RSLogix 5000 product CD contains Version 11.11 and Version 10.02. If you choose to install both versions, you will be prompted to replace V10.00 automatically. Additionally, V10.02 can be downloaded from the Software Updates website at http://support.rockwellautomation.com/webupdates/. Replacing Tag Names that Include Underscores If you use the Replace in Tag Collections feature to change the names of tags, be careful replacing tag sub-strings that end with an underscore on tags that are structure data types. For example, if you search for tag names that start with “MyTag_” and want to replace it with “MyTag_xx”, and select to Replace All, then the resultant tag name for any structure type tags (COUNTER, TIMER, etc.) may be incorrect. To avoid this problem, specify a string to search for that does not end with an underscore, or replace the tag names one at a time. (x28972) Error Accessing Motion Module Properties After Import The export format for the 1756-M02AE catalog number was corrected in V9.00. If you manually edit an L5K file for a release prior to V9.00 and change the catalog number it will not import correctly. A Fatal Error will occur when you access the module properties. (x28541) . Unsynchronized Messages to the Same Module via ControlNet If you use multiple unsynchronized Block Transfer type message instructions to communicate with a single module, and the path goes via ControlNet to a 1756-DHRIO module and on to Remote I/O devices, you may get an error "connection in use" returned by one of the 1756-CNB modules. To avoid this problem, add interlocking program logic to prevent more than one message at a time being sent to the module. (x28167) Produced/Consumed Tag Problems After Changing the Size of a User-Defined Type When you change the size of a user-defined data type by adding or rearranging members, you also change the size of any tags that reference that data type. If this changes the size of a produced or consumed tag beyond the 500- byte maximum, you may experience program faults during verify, download, or upload operations. To work around this problem, first change your user-defined data type definition so that all produced and consumed tags are smaller than 500 bytes. Then save your project as an L5K file and re-open the L5K file to create a new ACD file before downloading. (x27225) Runtime Error Opening Trend Chart Properties If your computer is running low on registry quota, you may observe a C++ Runtime error when attempting to open the properties of a trend chart in RSLogix 5000. To correct this problem, increase the maximum registry size. The maximum registry size is accessed from the My Computer, System Properties, Performance, Virtual Memory dialog. The recommended size is two times the current size plus 20%. (x26487) . Output Cam Execution Targets Not Converted In previous versions of RSLogix 5000 that supported output cam functionality, the default number of execution targets supported per axis was set to four and you could not modify the number. When downloaded to a controller, enough memory was reserved for four execution targets even if only one was used. In this release of RSLogix 5000, an Output Cam Execution Targets field has been added to the Axis Properties dialog box that allows you to set the needed number of execution targets. If you have routines with Motion Arm Output Cam (MAOC) instructions created in versions of RSLogix 5000 prior to V9.00 and you convert them to V10.00, the MAOC instructions will not operate unless the associated axis tag is manually corrected. The conversion of the previous version instructions set the execution targets for the axis tag to zero, which will cause the MAOC instructions to error when executed. To correct the problem, access the Axis Properties dialog General tab for the axis tag and set the Output Cam Execution Targets value to the correct number for your application. (x25982) . DH485 Protocol Limited to Baud Rate of 19,200 The RSLogix 5000 software will allow you to configure the System Protocol for DH485 and a Serial Port baud rate of 38,400. However the protocol does not support this baud rate and the serial port will not operate correctly if configured this way. Choose a baud rate of 19,200 or less when using the DH485 protocol. (x25526) . Increasing Array Dimension for Structure Data Type Tags Resets Data Values If you use array tags that are structure data types, for example, TIMER or COUNTER, use caution when changing the number of elements in the array. If you increase the array size the data values for all the elements in the array tag will be reset to their default value (typically zero). If you decrease the array size the data values will be preserved. To work around the problem you can export the project, manually edit the array tag dimension and values, and then import the project. (x23665) Produce & Consume Tags Changes As of the V7.00.00 release of RSLogix 5000, these features are obsolete: 1. You will not be allowed to simultaneously Produce and Consume a tag. 2. You will not be allowed to Produce an alias tag. If you have used the above features in a previous release, then when you convert your project to V10.00 the tags involved will be unverified. You will then be required to correct the tag(s) properties. In addition, produced and consumed tags now require more memory in the controller. If you attempt to download a project with a significant number of produced and consumed tags, you may run out of memory on the controller. Refer to the table of Controller Memory Changes for more detail. (x08098) Online correlation failure accepting a large number of pending edits When making online changes to ladder logic, you are limited to accepting changes to 1000 rungs at one time. If you attempt to accept pending edits for more than 1000 rungs, RSLogix 5000 will display an error "Failed to correlate the project with a change in the controller. RSLogix 5000 has been taken offline." You can avoid this problem by accepting pending rung edits before the 1000 rung limit is reached. (x06034) Tag Editor / Data Monitor Expand All with large arrays If your project has large array tags, the Expand All feature may result in a low virtual memory condition and sluggish response. To work around this condition, close all other applications except RSLogix 5000, or expand array tags manually. (21506) Unable to uninstall RSLogix 5000 when disk space is low If there is insufficient disk space on the hard drive, uninstalling RSLogix 5000 may fail with an error message “Unable to locate/process internal binary resource. Please contact your software vendor.” To work around this problem, free up disk space and try to uninstall again. (21195) Programming Over a DF1 Master/Slave Network Programming over a DF1 Master/Slave network is not currently supported in RSLogix 5000. (20596) Download Fails with Communication Time-out 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. (20430) User-Defined Data Type size limits You may not create a data type with more than 512 members either by editing in the Data Type Editor or by importing from a .L5K file. An individual UDT member may be an array with more than 512 elements. (20279, 21723) Program-scoped tag aliased to controller-scoped tag with the same name The Tag Editor will no longer allow you to create a program-scope alias to a controller-scope tag of the same name. If you created projects with this condition in previous releases, they will convert successfully to V9.00, but the controller will fail to upload with the error message “Failed to resolve tag target”. To work around this problem, you can do either of the following things: While online to the controller, change the name of all the program-scoped tags which alias a controller-scoped tag with the same name to something (slightly) different and then upload, or Save the project as an .L5K file (export) and open the .L5K file (import), which will cause the program-scoped tags to become unverified. Delete the program scope tags that are now unverified which will cause the instructions that used the program-scoped tags to re-bind to the controller-scoped tags with the same name. Finally, download the project to the controller. (20249) Motion_Instruction Data Type Size Change As of Version 2.25, tags of type Motion_Instruction are 12 bytes in size. In previous releases of RSLogix 5000, they were 8 bytes. Most users will not be affected by this change. However, 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 databases from previous versions. If you have written logic that relies on the old 8 byte size (for example by doing a COP of a Message_Instruction tag) you will need to verify that your logic is still correct. (20148) Failure to modify the RPI of a consumed tag While attempting to modify the RPI of a consumed tag, the following error may be encountered: "Failed to modify the properties for the tag '<consumed tag name>'. Couldn't be found." To work around the problem, save the project as an .L5K file, then reopen the .L5K file. (19870) Wall Clock Time beyond January 17, 2038 causes RSLogix 5000 to crash A Wall Clock Time in the controller beyond January 17, 2038 will cause RSLogix 5000 to crash. The Wall Clock Time may be set via an SSV instruction or on the Controller Properties dialog Date/Time tab. If the Wall Clock Time is inadvertently set to an invalid value or rolls over from an earlier valid value with the Date/time properties displayed, the RSLogix 5000 software will crash. (17457, 17464) Instances of going online for the first time failing There are intermittent issues with attempts to go online after power-cycling the controller chassis and/or stopping and starting RSLinx that may cause a first time failure. Immediate subsequent attempts will succeed. (09509, 17145) Uploading controllers with multiple aliases to the same data Caution should be used in developing applications that utilize multiple aliases to the same base tag. When such an application is uploaded, the alias may replace base tag operands in the ladder logic. The aliases are alphabetized internally on upload so the replacement operand will be the first alphabetical name (08905, x07909, CR169) Application Notes The following information is provided to help you better understand the behavior of RSLogix 5000 in particular applications or under certain circumstances. RSLogix 5000 RSLogix 5000 Save May Result In Large Project ACD File During a file save operation RSLogix 5000 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 may not be able to compress the information within the ACD file. In order to prevent the loss of project information, RSLogix 5000 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 technical support and provide a copy of your project file, this could help the RSLogix 5000 development team to locate the source of the compression failure. Activation Error Running Multiple Versions Simultaneously If you have both V10.00 and an earlier version of RSLogix installed on your computer, you will observe an activation error if you run V10.00 first and then attempt to run the earlier version simultaneously. To work around this problem, always run the earlier version first and then run V10.00. Default Project Directory and Windows 2000 When using RSLogix 5000 on a Windows 2000 computer, be careful when performing operations with project files that depend on the default project directory. Windows 2000 controls and retains the default directory for the Open, Save As, and New Controller dialogs. 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 is normally used unless you navigate to a different directory within the Open, Save As, or New Controller dialogs. (x28475, x27886) FBD Routine Localized Feedback Wiring Errors In releases prior to 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 problem 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 problem, select a feedback wire in the inner loop that is not also in the outer loop to be the localized feedback wire. (x28963, x27712) FBD Routine Order of Execution for Unwired Blocks If you have a Function Block Diagram routine with function blocks that are not wired together, the execution order is not deterministic. Operations such as Verify Routine or Export/Import may change the execution order unexpectedly for unwired blocks. To define the execution order, you must wire function blocks together. See the Function Block Attributes Order of Execution topic in the RSLogix 5000 Online Help or the Logix5000 Controllers Process Control and Drives Instructions Reference Manual for more information. (x28703, x28681) Motion Module Servo Update Period Changed The Servo Update Period for the 1756-M02AE 2 Axis Analog/Encoder Servo module has been changed from 200 microseconds to 250 microseconds. The servo update period is displayed on the Module Properties dialog 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) Updating Controller Firmware in a DH485 Network If you update the firmware of a controller while it is connected to a DH485 network, communications on the network may stop. To prevent this, disconnect the controller from the DH-485 network before you update the firmware of the controller. (x28491) Online Disconnection after Nonvolatile Store or Load Operation When using any of the controllers with nonvolatile memory, the memory store and memory load operations will take between 30 seconds and approximately 3 minutes to complete. During these operations the RSLogix 5000 software will be taken offline and will require you to manually reconnect. Any other workstations connected to the controller will also be taken offline. If you performed a store operation, or a load operation where your project did not have any online changes, you will be able to go back online immediately and the project will need to be saved. If you performed a load operation, and your project included online changes that you saved since the last store operation, you will be prompted to upload or download before going online. I/O Module List Appears Empty If the list of modules appears empty in the Select Module Type dialog box when you attempt to create a new module, there may be a problem with system DLL files on your computer. Make sure that the version of files on your computer match the compatible version listed in the table below. (x19891, x18680, x06823) DLL Name Compatible Versions Comcat.dll 4.71 5.0 Ole32.dll 4.0 4.71 or later Configuring CRC Error Detection for RSLogix 5000 Software RSLogix 5000 software is configured to use BCC error detection by default when using DF1 serial port communication. CRC error detection can be configured instead of BCC by following these two steps. First, CRC Error Detection must be selected on the Controller Properties dialog 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 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 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 and reduce RSLinx to an icon. If using DF1 communications, in RSLogix 5000 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. Changes in Fatal Error Handling Starting with RSLogix 5000 Version 2.25, there are changes in the way abnormal program terminations will appear. There is now a single format for the Fatal Error dialog, which will appear regardless of the cause of the problem. There is also a single log file generated that records the abnormal events and can be emailed to Customer Support so that the problem can be recorded, diagnosed, and fixed. An abnormal termination of RSLogix 5000 will result in a short period of program unresponsiveness followed by the appearance of a dialog box with the title "RSLogix 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" located in the Temp directory. (C:\Temp on Windows NT4 or C:\Documents and Settings\<username>\Local Settings\Temp on Windows 2000.) Controllers with motion control Be certain that only one controller or SYNCH module in the chassis is enabled as the Coordinated System Time (CST) master. You can enable the feature for a controller by navigating to the Controller Properties dialog Date/Time tab and selecting “Make this controller the Coordinated System Time master”. You can enable the feature for a SYNCH module by navigating to the SYNCH Module Properties dialog Time Mastership tab and selecting “Make this module the Coordinated System Time Master for this chassis”. Communication errors to the servo module(s) will occur if more than one controller or SYNCH module is configured as the CST master. Destination operands for GSV commands Caution should be used in selecting the proper data type for the destination operand of a GSV instruction. Use of mismatched operand data types may result in unexpected results. Refer to the Instruction Set reference manual or the online instruction help to determine the proper data types. Downloading controllers that use more memory than available If a controller utilizing more memory than is available in the physical controller is downloaded, the user will receive an appropriate error message. However, in some instances, the serial port will become inoperative. It is recommended that in this case the controller memory be cleared (power turned off and the battery removed). Multiple owners and/or listeners of 1756 analog modules When using multiple owners and/or listeners of 1756 analog modules, set the Requested Packet Interval (RPI) for all connections to the same value. If different RPIs are used, connections may not recover correctly in a power-up situation. Configuring the DHRIO module When online, if the DHRIO module is configured for DH+ only, this module continuously displays Faulted as its Status on the Module Properties dialog box even when normal communications exist. To avoid this erroneous fault condition, include the DHRIO module in the I/O configuration only if the application uses the Remote I/O features. Note: If the Logix controller is not located in the default slot (slot 0) of the ControlLogix chassis, you must use RSLinx V2.20 or later, or the ControlLogix Gateway Configuration Tool (1756-GTWY) to setup a controller slot for the 1756- DHRIO module. User disk memory utilization If a 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 (typically C:\Temp on Windows NT4 or C:\Documents and Settings\<username>\Local Settings\Temp on Windows 2000). Smaller files with .SEM and .WRK suffixes may be left in your project directory after an abnormal termination and may be deleted. Mapping to remote/network drives When opening RSLogix 5000 project files, note that you must have write permission to the root directory on that (network) drive, as well as write permission for the project file itself. Otherwise, the user will receive a file access error. Offline/Online changes to I/O configuration After changing the configuration of an I/O module while offline, be sure to do a download when you go back online. Otherwise, the offline changes will not take effect and may become undone in the offline file. Application Errors at end of install or at RSLogix 5000 startup on some systems Caused by a corrupted activation key file (evrsi.sys). To correct this problem, contact Rockwell Automation technical support by telephone at 440-646-5800 or by email at RACleAskTheExpert@ra.rockwell.com. Making backups of controller files As with any software package it is strongly encouraged that users save their work frequently and make backup copies of the controller files (project_or_controller_name.ACD). RSLinx with RSLogix 5000 RSLinx Professional Activation Beginning with RSLinx V2.31.00, the RSLogix 5000 Professional activation will also enable the RSLinx Professional version features. Only one professional activation is required for both products. RSLinx / RSView Offline Tag Access RSLinx V2.20 provided the ability to upload the tag list from a running Logix5000 controller. RSLinx then presented these tags via a built in tag monitor tool. Additionally, the tag definitions were made available to other software packages such as RSView, via an OLE for Process Control (OPC) browse component. This permitted you to navigate into a controller to select its tags directly when developing display screens in RSView. RSLogix 5000 V10 and RSLinx 2.30.02 (Build 74) take these capabilities further by providing the ability to do this operation offline. RSLinx can now navigate into a RSLogix 5000 database (ACD) file to provide the same tag access without having to setup and download controllers. This capability reduces system development and startup time and avoids problems resulting from tag name mismatch. Accessing Structures Larger than 64 Kbytes ControlLogix5000 Version 8.x controllers allow you to create user-defined structures larger than 64 Kbytes. Access to these structures in the controller requires you to update to RSLinx V2.30.00 (Build 40) or later for correct operation. Older versions of RSLinx do not operate correctly with these larger structures. Configuring drivers for the 1756-ENET module You configure a driver for communicating from the workstation through the 1756-ENET module by selecting "Configure Drivers ..." from the RSLinx "Communications" menu. In the dialog box, select "Remote Devices via Linx or 1756-ENET Gateway" in the list of available driver types and click on the "Add New" button. Enter the IP address of the ENET module in “Server’s IP Address or HostName”. Ignore the Browse button and the ServerName display. Leave "Remote driver name" blank. Configuring DF1 drivers 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 problems accessing information from I/O modules. DDE interface to the Logix5550 controller DDE links to a Logix5550 controller can be made directly, or by mapping the tags as PLC-5 tags (see Logic/Map PLC/SLC Messages in the RSLogix 5000 main menu). Mapping may be more efficient for large arrays. Problems in prior releases requiring word swapping of REAL data have now been fixed. Starting with the combination of RSLogix 5000 Version 2.25, Logix5550 Version 4.42, and RSLinx 2.10 Service Pack, several performance enhancements were provided for DDE/OPC links to the Logix5550. There are some issues that need to be considered when utilizing these enhancements. The new implementation of DDE links in RSLinx relies on a new trend object in the Logix5550 firmware. While the RSLinx packet optimization transfers data from several controller tags in one packet for increased throughput, the trend object consumes controller memory and communications resources. If existing DDE/OPC applications are converted and exhibit communications problems, several parameters can be adjusted to address the problem. The "System Overhead Timeslice" could be increased, periodic task scan times could be lengthened, or the "Communications Timeout" on the DDE/OPC Topic Configuration could be adjusted.
Pages to are hidden for
"Release Notes Template Build Software"Please download to view full document