RSLogix 500™ Release Notes (Version 8.

10)

Programming for SLC 500™ and

MicroLogix™ Families
19 June 2008
Updating Current Caveats
Current Repairs Known Issues
RSLogix 500 Enhancements

Important All Users: RSLogix 500 is supported on workstations running Windows

Vista Business (32-bit), Windows Vista Home Basic (32-bit), Windows 2000, Windows
2000 SP4, Windows XP, Windows XP SP2, Windows Server 2003, Windows Server
2003 SP1, and Windows Server 2003 R2 operating systems. If using FactoryTalk
Services Platform with RSLogix 500 on Windows Vista, Service Pack 1 is required.

Important – For the latest information regarding software platform support, refer to the
Knowledgebase article 42682; http://rockwellautomation.custhelp.com/cgi-
bin/rockwellautomation.cfg/php/enduser/std_adp.php?p_faqid=42682. All
Knowledgebase articles are located at
http://www.rockwellautomation.com/knowledgebase/ .

Microsoft Vista Users: RSLogix 500 requires that you use RSLinx Classic v2.53 or later
when running under Microsoft Vista. While the RSLogix 500 Pro application can be
upgraded to Vista, until RSEmulate 500 is Vista compatible, support will be limited. The
Pro bundle will not be available for version 8.1 until later in 2008. RSLogix 500 Pro
application may be updated to version 8.1 by downloading from the Rockwell
Automation Technical Support website.

RSLogix 500 supports both EVRSI and FactoryTalk Activation. This release of RSLogix 500 will be the
last release to support EVRSI. Refer to the document titled “Activate Your Rockwell Software Products”
that came in the box with your software, and is also available during installation for information on
FactoryTalk Activation.

Updates to the FactoryTalk Services Platform (version 2.10.01, CPR9):

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

Updating RSLogix 500: Back to top

See the Installation note regarding retaining user settings.

Installing an older version of RSLogix over a newer version: In order to install an

older version of RSLogix 5/500 over a newer version, the newer version must be
uninstalled using Add/Remove Programs in the Control Panel. You can install a newer
version (V6.3x or later) without uninstalling the old version first, since the newer version
will handle the uninstall of an older version.

RSLogix 500 and RSLogix Micro cannot be installed on the same computer. If SLC or
other features are needed, you may upgrade RSLogix Micro to RSLogix 500.

Current Enhancements: Back to top

The following is a list of enhancements included in the current release:

• Added support for MicroLogix1400 Series A:

ML1400 processor type support

Function File enhancements (PTOX, PWMX, LCD, HSC, EII, ES)

ASCII data file support

Input and Output file enhancement

Force files for Input and Output enhancement

LCD editing disable property

LCD logo export and import

Subroutine protection

IO Configuration

Channel configuration DNP3 Slave support

New instructions (XPY, LN, LOG, SIN, ASN, COS, ACS, TAN, ATN, RAD, DEG, CPT, RPC, RHC, TDF)

LCD instruction enhancement

Data Log

IMG file export

• Added support for FRN-11 for the SLC 5/03,5/04 and 5/05.

Channel configuration Modbus RTU Master support

Modbus MSG support

 The following is a list of enhancements included in the previous release:

• Added support for Windows Vista Business (32-bit) and Windows Vista Home Basic
(32-bit)

• Updated HTMLHelp format for Windows Vista compatibility.

• Added support for MicroLogix 1100 Series B:

Simple Mail Transfer Protocol (SMTP) support
PWM/PTO configurable from 20kHz to 40kHz
Analog input filters configurable between 10/50/60/250 Hz; Configurable
independently
CIP generic messaging support

• New I/O module support:

1769-IQ32T

1769-OV32T

1769-IF4I

1769-OF4CI

1769-OF4VI

1769-Boolean

1769-IG16

1769-OG16

1769-OB32T

1762-IQ8OW6

1769-IF4FXOF2F

• Added support for firmware revision FRN-10 for the SLC 5/03, 5/04 and 5/05.
Explicit Messaging instructions: CEM, DEM, and EEM for ControlNet, DeviceNet,
and EtherNet
Read Program Checksum instruction: RPC
Security enhancement to prevent access to a secured controller from non-secured
programming software.

• Added FactoryTalk Security LogOn – LogOff, FactoryTalk Activation Adoption,

Standard Personalization Adoption, and Grace Period Adoption.

• Added new and additional information to various online Help topics.

Current Repairs: Back to top

The following product changes and repairs were included when the product was shipped
to you.

The following issues are resolved:

• The communication Path was erased in RSLogix500.

• The program and fault states were not preset for analog output modules of ML1500.

• Importing a SLC library was not handled correctly when using ML1100.

• The Modbus MSG Configuration was lost in the ladder file copy.

• The recipe title was lost when a recipe was saved while online.

• The 1746-NR4 I/O module Excitation Current Text option item returned an error.

• While on-line editing a SLC 500 controller with FRN10 firmware, if a different
version of RSLogix is used to access the controller, the controller may fault.

• Reports truncated some of the Rung comments.

• The selected "Exclude Addresses with symbols or descriptions" option item was not
saved.

• The input data description was not saved in ML1100.

• The Data Table usage for a CIP message was incorrect.

Known Issues: Back to top

The following is a list of known issues at the time the software was released.

• Under Windows Vista, the MSG instruction cannot send email through the SMTP
server. To use this feature, you must use an OS other than Vista.

• Under Windows Vista, if you have User Account Control (UAC) enabled, you may
be prompted to confirm your Administrator privileges when executing certain tasks
(like import/export) in RSLogix 500. If you do not have Administrative privileges,
contact you System Administrator.

• Only one version or edition of RSLogix 500 may be installed within a Windows OS.
• If RSLogix500 V7.0 or V7.10 is used with the MicroLogix1100 Series B processor,
the processor type will be shown as MicroLogix1100 Series A in the software.
RSLogix500 V7.0 or V7.10 may not work normally with the Series B project
(Channel Configuration, IO configuration, RIX file, PTO and PWM function file,
MSG instruction) running in the Series B processor. For detail refer to 1763-
RM001A-EN-P.

• Software will not allow the use of a Floating Point Constant in an SCP instruction.

• RSLogix 500 requires a save before downloading a file that is write protected.

• In the Histogram Save/Load feature, the Load Histogram does not function correctly.

• ML1500 LRP Series C Channel 1 Radio modem; the broadcast message destination
node 1 is not accepted when verifying the project. The error “invalid local DH485
Station Number (0-254) appears. However, 1 is a valid local DH485 station number
when Channel 1 is set for DF1 Radio modem and a broadcast message is desired.

• In order to support the MicroLogix 1100 Series B processor, RSLogix 500 handles
PTO and PWM frequencies (PTO.OF, PTO.OFS, PTO.JF, PWM.OF and PWM.OFS)
as unsigned 16-bit integer(0 ~ 65535) for MicroLogix 1100 Series B. Therefore, if an
older version of RSLogix 500 (v7.0 and v7.10) is used with the MicroLogix 1100
Series B controller compatibility issues will occur; RSLogix 500 display issues: Since
an older version of RSLogix 500 treats PTO/PWM frequencies as signed integers, if a
user uploads a program from a MicroLogix 1100 Series B controller into the
software, a negative frequency value may be displayed. For example, 40kHz is
0x9C40 in hexadecimal. The 0x9C40 is 40000 in unsigned integer, but -25536 in
signed integer. Instruction issues: All the instructions in MicroLogix controller treats
integer as signed integer. 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
in Publication 1763-RM001B-EN-P January 2007.

• In V7.20, if a user enters parameter of "Class" or "Instance" and the value is between 0x100--
0xFFFF(256--65535)) in ML1100 Series B CIP MSG setup screen, the high byte and low byte of this
parameter will be swapped after verify and compile process. For example, "AABB" will change to
"BBAA" after the first time verify, and then "BBAA" will change to "AABB" after the second time verify.
If the V7.20 project with the 0x100--0xFFFF(256--65535) "Class" or "Instance" parameter in ML1100
Series B CIP MSG setting is opened in V7.30 or later, the high byte and low byte of parameter "Class"
or "Instance" may be swapped. The user needs to manually check the value in V7.30 to ensure the
value is what he wants. SLC FRN10 EEM also has the same issue in V7.10 and V7.20, but the range
will be as following: 0x100—0x17F, 0x200--0x27F, 0x300--0x37F, ...... ,0xFD00--0xFD7F, 0xFE00--
0xFE7F, 0xFF00--0xFF7F.

• If a user changes the address description in a data file, the description in the Trend applet can not be
updated.
 Caveats: Back to top

The following is a list of features and functions that are not fully implemented or non-
functional at the time the software was released.

• When opening an .ACH file with Database or native Import A.I. Database file
functions, the user 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
results in errors in the .RSS file

• The projectname.RSS file contains both an on-line and off-line image of your
project. This speeds the process of connecting to a processor. These images can get
unsynchronized; this occurs if you don't save your changes when going from on-line
to off-line. To synchronize the images you must download, upload or save the project
while on-line.

• RSLogix 500 prints Ladder Logic reports as graphic files. The ladder report cannot
be printed to a text file. Other RSLogix 500 reports can be printed to a text file using
the Generic/Text-only printer driver in Windows.

• The following characters may not 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.
We recommend that you export the database to the ASCII CSV format to speed the
replacement of the illegal characters in your symbols.

© Copyright 2008 Rockwell Automation Inc. All Rights Reserved. Printed in the United States of America.

© Copyright 2008 Rockwell Automation Inc. RSLogix 500, RSLogix Micro, RSLinx, PLC-500 A.I. Series, and the Rockwell
Software logo are trademarks of Rockwell Automation Inc. SLC, SLC 500, SLC 5/01, SLC 5/03, SLC 5/04 SLC 5/05 and
MicroLogix are trademarks of the Allen-Bradley Co., Inc. Microsoft, MS-DOS, Windows 95, Windows 98, Windows ME,
Windows NT, Windows 2000, Windows XP, Windows Vista, and Windows Server 2003 are registered trademarks of the
Microsoft Corporation. Other product names mentioned in this document are trademarks or registered trademarks of their
respective companies and are hereby acknowledged.