System requirements for RSLogix 500 v. 10.00

Supported Operating Systems:

• Windows® 8.1 (32-bit or 64-bit)
• Windows Server 2008 and 2012
• Windows 7 (32-bit or 64-bit)
• Windows Vista® with Service Pack, or later

RSLogix 500 v. 8.10 and later require a valid serial number for installation. This ensures the serial number information is readily available for technical support and allows the correct edition of RSLogix to be activated when using FactoryTalk® concurrent activations.

RSLogix 500 v. 10.00 supports FactoryTalk Activation. For information about FactoryTalk Activation refer to Activate Your Rockwell Software Products, which came with your software (and is also available during installation).

Windows Vista Users: RSLogix 500 requires that you use RSLinx® Classic v. 2.53 or later when running under Windows Vista. To run RSEmulate 500 under Windows Vista, RSLinx Classic v. 2.55 or later is required.

Windows 7 Users: RSLogix 500 requires that you use RSLinx Classic v. 3.71.00 or later when running under Microsoft® Windows® 7.

FactoryTalk Services Platform:

FactoryTalk Services Platform has been updated to version 2.74.00, CPR 9 SR 7.4. Please refer to the Release Notes for FactoryTalk Services Platform for more information. We advise that you use the Notify Me by Email option to keep up to date on changes in FactoryTalk Services Platform.

Updating RSLogix500:

Installing an older version of RSLogix over a newer version: In order to install an older version of RSLogix 500 over a newer version, you must first uninstall the newer version by using the Window's Control Panel's Add/Remove Programs. You can install a newer version (v. 6.3x or later) without uninstalling the old version first.

RSLogix 500 and RSLogix Micro cannot be installed on the same computer.

Current enhancements in RSLogix 500 v. 10.00

The following enhancements in this release of RSLogix 500 are:

• Support for SLC™ controllers:
  • 1747-L531 F
  • 1747-L532 F
  • 1747-L533 F
  • 1747-L541 D
  • 1747-L543 D
  • 7147-L551 D
  • 1747-L552 D
  • 1747-L553 D
• Web-based online help supports multi-platform browsers, robust searches, individual user preferences, and bookmarks.
• Support for Windows 2012 OS
• Update the current version of FactoryTalk Activation v. 3.62.11, CPR 9 SR 6.1.
• Update the current version of RSLinx Classic v. 3.74.00, CPR 9 SR 7.4.
• Update the current version of FactoryTalk Services Platform v. 2.74.00, CPR 9 SR 7.4.
• RSLogix Project Migrator is included with this release of RSLogix 500. With Integrated Architecture Builder, RSLogix Project Migrator helps migrate from SLC 500 or MicroLogix controllers to Logix controllers.

Fixed anomalies in RSLogix 500 v. 10.00

The following is a list of anomalies fixed in this version of RSLogix 500.

• FactoryTalk Security failed to install when upgrading to FTView 8.0 CPR9 SR 7 with RSLogix 500.
• RSLogix 5000® supports two-byte attributes but RSLogix 500 only supported a one-byte attribute when configured in a MicroLogix 1100/1400 CIP Generic MSG instruction. The MicroLogix 1100/1400 firmware and RSLogix 500 software now support two-byte attributes by moving the values into the RIX file via ladder logic. (Customer ticket 4002001080.)
• With MicroLogix 1400 Series B FRN 12, the S:1/5 Forces Enabled bit can be cleared in the offline file to disable forces. When forces are disabled (S:1/5=0), the Enable All Forces option was available in the drop down box. However, selecting this option did not enable forces. The resolutions with ML1100B/ML1400B, for this release are:
  • The Enable All Forces option is active regardless of whether forces are installed. In previous releases, if forces were not installed, the Forces Disabled option was inactive, and the Forces Enabled option was always active.
  • When online and forces are installed, the Force Enable/Disable down-arrow is inactive.
• If a file was open and the network connection is lost and then restored, RSLogix 500 was not be able to save the file.  Resolved in this release.
• Resolved the MicroLogix project build error for 1746-NO8V module.
• Corrected the 1746 NR8 Module Excitation current selection. Changed 0.5 mAmp to 0.25 mAmp.
• MicroLogix 1400 Series B FRN 12 can clear the Forces Enabled bit, S:1/5, in the offline file. Once the file is is downloaded to the controller, forces are disabled. However, RSLogix 500 v9.0 and earlier, automatically set this bit in the offline file, thus re-enabling forces without any user intervention. This occurred when:

-1. 1. 1. Once the S:1/5 bit is cleared (Forces Disabled), save and close the file. When the file is reopened, S:1/5 will be set again (Forces Enabled).
          Once the S:1/5 bit is cleared (Forces Disabled), download the file and go online - forces are disabled. Go offline and S:1/5 will be set again (Forces Enabled) in the offline file.
    2. This issue is resolved in this release. RSLogix 500 does not set this bit without user intervention in any MicroLogix controller.

• Resolved the issue where a user-defined footer bitmap does not show up in the print preview.
• This release of RSLogix 500 allows for default domain names of two characters.
• In the DNP3 Data Set Descriptor window when you opened the 5th element PTYP page, multiple Element 5 Prototype Configuration tabs appeared on the window. Resolved in this release.
• In the DNP3 Data Set Descriptor window, when the descriptor had the maximum of 10 data elements and the tenth element was a prototype, when you opened the tenth element's PTYP page for descriptor, and clicked OK, the system crashed. Resolved in this release.

Known anomalies in RSLogix 500 v. 10.00

The following is a list of known anomalies at the time this version of RSLogix 500 was released.

• Selecting Cross Reference for an address in the ladder editor is slow when online with a SLC 5/05 processor with a project containing many complex instructions such as EEM, DEM, CEM, and MSG.
• Under Windows Vista or later operating systems, or as an admin on a virtual machine, if User Account Control (UAC) is enabled, you may be prompted to confirm your Administrator privileges when executing certain tasks (like import/export). If you do not have Administrative privileges, contact your System Administrator.
• Online editing of a rung with an LBL instruction fails on an SLC 500 processor in remote run mode if the matching JMP instruction exists in the project and UNTEST is selected. One workaround is to put the LBL instruction on its own rung.
• In a MicroLogix™ 1200 or MicroLogix 1500 project, if a CLR instruction with an HSC:0.ACC or HSC:1.ACC operand exists in the rung with a nested branch (for example:BST XIC B3:0/0 CLR HSC:1.ACC NXB ADD 0 N12:1 N7:0 BND), the project verification will fail and a compiler error will be displayed.
• RSLogix 500 will not allow the use of a Floating Point constant in an SCP instruction.
• With a MicroLogix 1500 LRP Series C Channel 1 Radio modem, the broadcast message destination node 1 is not accepted when verifying the project. The error message invalid local DH-485 Station Number (0-254) displays even though 1 is a valid local DH-485 station number when Channel 1 is set for DF1 Radio modem and a broadcast message is requested.
• In order to support the MicroLogix 1100 Series B controller, RSLogix 500 handles PTO and PWM frequencies (PTO.OF, PTO.OFS, PTO.JF, PWM.OF, and PWM.OFS) as unsigned 16-bit integers (0 - 65535) for MicroLogix 1100 Series B. If you are using an older version of RSLogix 500 (version 7.0 and version 7.10) with the MicroLogix 1100 Series B controller, there will be compatibility issues. These include:
  • RSLogix 500 display issues: Because an older version of RSLogix 500 treats PTO/PWM frequencies as signed integers, if you upload a program from a MicroLogix 1100 Series B controller into the software, a negative frequency value may be displayed. For example, 40 kHz is 0x9C40 in hexadecimal. The hexadecimal value 0x9C40 is 40000 in unsigned integer, but -25536 in signed integer.
  • Instruction issues: All instructions in MicroLogix controllers treat integers as signed integers. Therefore, unsigned integers in PTO/PWM function file elements need to be treated carefully when they are used in the variables for instructions. An undesired result may be returned or math overflow may be detected during instruction executions. A workaround should be used such as copying PTO/PWM frequencies to long integer before manipulation. For greater detail refer to Appendix F: How to use 40kHz PTO/PWM of MicroLogix 1100 Series B Controller, publication 1763-RM001.
• If the address description in a data file is changed, the description in the Trend applet cannot be updated.
• When changing DNP3 Data Set configuration from Data Element (DAEL) to Prototype (PTYP) several times, RSLogix 500 may stop responding. In this event, restart RSLogix 500.

Application notes for RSLogix 500 v. 10.00

This section describes the behavior of the RSLogix 500 software in particular applications or under certain circumstances.

• You can only install one version or edition of RSLogix 500 or RSLogix Micro™ within a Windows operating system.
• When opening an .ACH file with Database or native Import A.I. Database file functions, you must open the file as an Administrator. Otherwise, the database in the .ACH file cannot be imported or the native Import A.I. Database file process will fail.
• Do not perform online saves with the Excel database editor (Pro only) open as it causes errors in the .RSS file
• If you are using RSLinx® to perform DDE communications with a processor and you download a project to the same processor, the download may fail. If this occurs, the processor loads its default program. To avoid this situation cease DDE communications to your target processor when you plan to download a project to the same processor.
• The project file (projectname.RSS) contains both an online and offline image of your project. This speeds the process of connecting to a processor. These images can become unsynchronized; this occurs if you do not save your changes when going from online to offline. To synchronize the images, you must download, upload, or save the project while online.
• The project file (projectname.RSS) contains all database- and project-related files. If you need to share a project with someone, provide them with the projectname.RSS file and they will receive all project-related information. When sharing RSLogix database information with other Rockwell Automation Software programs, like RSView®32, you must use the Save database as external file check box on the File>Save As dialog box to make the database file available to that program.
• RSLogix 500 prints ladder logic reports as graphic files. The ladder report cannot be printed as a text file. Other RSLogix 500 reports can be printed as a text file using the Windows text-only printer driver.
• The following characters cannot be used in RSLogix 500 symbols, ` ~!@#$%^&*()-+={}[]|\\:;""'<>?,./ . If you have used these characters in a previous release of RSLogix 500, the symbols will appear in your ladder views and reports; however, you cannot modify the symbol.

-1. 1. We recommend that you export the database to the ASCII CSV format to help locate illegal symbol characters.

Legal Notices in RSLogix 500 v. 10.00

Copyright notice

© 2015 Rockwell Automation, Inc. All rights reserved. Printed in USA.

This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation, Inc. is strictly prohibited. Please refer to the license agreement for details.

End User License Agreement (EULA)

You can view the Rockwell Automation End-User License Agreement ("EULA") by opening the License.rtf file located in your product's install folder on your hard drive.

Trademark Notices

Rockwell Software, Advanced Interface Series, RSLogix, RSLogix Micro, MicroLogix, ControlLogix, SLC, Rockwell Automation, RSAssetSecurity, RSLinx, SCANport, RSEmulate, FactoryTalk Services Platform, FactoryTalk Diagnostics, PowerFlex, RSTrend and FactoryTalk Security are trademarks of Rockwell Automation, Inc.

Any Rockwell Automation software or hardware not mentioned here is also a trademark, registered or otherwise, of Rockwell Automation, Inc.

Other Trademarks

Microsoft, Excel, Visual Basic, Windows and ActiveX are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Adobe, Reader, and Acrobat are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Intel is either a registered trademark or trademark of Intel Corporation in the United States and/or other countries.

All other trademarks are the property of their respective holders and are hereby acknowledged.

Warranty

This product is warranted in accordance with the product license. The product’s performance may be affected by system configuration, the application being performed, operator control, maintenance, and other related factors. Rockwell Automation is not responsible for these intervening factors. The instructions in this document do not cover all the details or variations in the equipment, procedure, or process described, nor do they provide directions for meeting every possible contingency during installation, operation, or maintenance. This product’s implementation may vary among users.

This document is current as of the time of release of the product; however, the accompanying software may have changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this document or the software at any time without prior notice. It is your responsibility to obtain the most current information available from Rockwell when installing or using this product.

Environmental compliance

Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

Contact Rockwell

Customer Support Telephone — 1.440.646.3434
Online Support — http://www.rockwellautomation.com/support/