RSLinx Classic Release Notes

Transcription

1 RSLinx Classic v (CPR 9 Service Release 6) Release Notes The RSLinx Classic v (CPR 9 Service Release 6) Release Notes contain information about the following topics: New features System requirements Silent installation Considerations when using RSLinx Classic with Windows Vista, Windows 7, or Server 2008 DEP settings Software compatibility Upgrade instructions Anomalies fixed Known anomalies Windows and RSLinx Classic issues Upgrade the FactoryTalk Services Platform software Application notes 1

2 New features in RSLinx Classic RSLinx Classic v (CPR 9 Service Release 6) The following features have been added in RSLinx Classic v (CPR 9 Service Release 6). For driver support information, refer to the RSLinx Classic Driver Compatibility Matrix. See Rockwell Knowledgebase Answer ID The EDS files for some devices have been added or updated in this release. This includes support for new hardware devices. For more detailed information, refer to Rockwell Knowledgebase Answer ID RSLinx Classic v (CPR 9 Service Release 5.1) The following features have been added in RSLinx Classic v (CPR 9 Service Release 5.1). RSLinx Classic v supports large connection. DTL_CIP_LARGE_CONNECTION_OPEN and DTL_CIP_LARGE_CONNECTION_CLOSE functions are added. To support the large connection function, v20 or later controller and EN2x, v5.x is required. For Rockwell Automation devices, all of the latest 1756 Ethernet bridges (for example, EN2T, EN2TR, EN2F, EN3TR, EN2TXT) support 4002 bytes over Ethernet. The older 1756 Ethernet bridges (for example, ENBT, ENET) and the 1768 bridges (for example, ENBT) do not support the DTL_CIP_LARGE_CONNECTION_OPEN service. Currently, RSLinx Classic does not support large connection over the virtual backplane and USB CIP connection. RSLinx Classic v provides enhanced new algorithm and user interfaces of Ethernet bus browsing for CIP router devices. NAT (Network Address Translation) device support for Ethernet bus browsing is enhanced. See Use RSWho. The Backup and Restore utility allows you to backup and restore topology path information, in addition to the previous information types. RSLinx Classic v EDS subsystem and harmony components are redesigned to significantly reduce installation time. For driver support information, refer to the RSLinx Classic Driver Compatibility Matrix. See Rockwell Knowledgebase Answer ID The EDS files for some devices have been added or updated in this release. This includes support for new hardware devices. For more detailed information, refer to Rockwell Knowledgebase Answer ID RSLinx Classic v (CPR 9 Service Release 5) The following features have been added in RSLinx Classic v (CPR 9 Service Release 5). Micro850 EDS file is newly supported in RSLinx Classic v (CPR9 Service Release 5). For more hardware support information, refer to Rockwell Knowledgebase Answer ID For driver support information, refer to the RSLinx Classic Driver Compatibility Matrix. See Rockwell Knowledgebase Answer ID RSLinx Classic v (CPR 9 Service Release 5) The following features have been added in RSLinx Classic v (CPR 9 Service Release 5). USB CIP 32-bit driver package is updated to , and USB CIP 64-bit driver package is updated to For more driver support information, refer to the RSLinx Classic Driver Compatibility Matrix. See Rockwell Knowledgebase Answer ID

3 1756-L71S EDS file is newly supported in RSLinx Classic v (CPR9 Service Release 5). For more hardware support information, refer to Rockwell Knowledgebase Answer ID RSLinx Classic v (CPR 9 Service Release 5) The following features have been added in RSLinx Classic v (CPR 9 Service Release 5). Data Monitor is now available in all versions of RSLinx Classic, including RSLinx Classic Lite. The following 64-bit driver is now supported when installing on a 64-bit operating system: 1784-PKTCS Driver For more driver support information, refer to the RSLinx Classic Driver Compatibility Matrix, showing which RSLinx Classic drivers are compatible with specific operating systems. See Rockwell Knowledgebase Answer ID The EDS files for some devices have been added or updated in this release. This includes support for new hardware devices. For more detailed information, refer to Rockwell Knowledgebase Answer ID RSLinx Classic v (CPR 9 Service Release 4) The following features have been added in RSLinx Classic v (CPR 9 Service Release 4). RSLinx Classic v (CPR 9 SR 4) and later versions display a message indicating the activation status when you place the cursor over the tray icon in the notification area. If the activation status changes during runtime, the message shows the new status after you restart RSLinx Classic v Support hot plug and play for Allen Bradley 12 Point Micro810 USB devices. The RSLinx Classic (CPR 9 SR 4) installation program installs or updates the Microsoft.NET Framework to 3.5 SP1. EvRSI activation is replaced by FactoryTalk Activation Manager since RSLinx Classic v (CPR 9 Service Release 4). If you are using EvRSI activation, please contact your local Rockwell Automation Sales Office or Technical Support for information on migrating your activations to FactoryTalk Activation Manager. For Rockwell Automation Technical Support in the U.S., call 1 (440) Outside the U.S., see The following 64-bit drivers are now supported when installed on a 64-bit operating system: Virtual Backplane Driver 1784-PCIC Driver Ethernet devices EtherNet/IP Driver Remote devices via RSLinx Gateway RS-232 DF1 devices 1784-U2CN/1784-U2DN USBCIP Devices PKTX(D)/PCMK for DH+/DH485 devices U2DHP for DH+ devices 1. The 1784-PKTX(D)/PCMK driver cannot be installed on the Windows Server 2003 R2 [64-bit] operating system. 2. If you have problems connecting to a device using the 1784-U2DHP driver, disconnect and reconnect the 1784-U2DHP. For more information, refer to the RSLinx Classic Driver Compatibility Matrix, showing which RSLinx Classic drivers are compatible with specific operating systems. See Rockwell Knowledgebase Answer ID The EDS files for some devices have been added or updated in this release. This includes support for new hardware devices. For more detailed information, refer to Rockwell Knowledgebase Answer ID

4 4 RSLinx Classic v (CPR 9 Service Release 3) The following features have been added in RSLinx Classic v (CPR 9 Service Release 3). The installation program for RSLinx Classic also installs the necessary FactoryTalk Services Platform (FactoryTalk Services Platform version CPR 9 SR 3) components if they are not installed or need to be updated. If FactoryTalk Services Platform CPR 9, CPR 9 SR 1 or CPR 9 SR 2 is already installed, the RSLinx Classic installation program updates the necessary components to CPR 9 SR 3. If you cancel the FactoryTalk Services Platform installation, the RSLinx Classic installation program does not update the FactoryTalk Services Platform. If FactoryTalk Services Platform CPR 7 or older is already installed, the RSLinx Classic installation program installs only the required components that are compatible with all versions of FactoryTalk Services Platform. RSLinx Classic (CPR 9 SR 3) can now be installed on 64-bit Microsoft Windows operating systems. For the list of supported operating systems, see System requirements. RSLinx Classic (CPR 9 SR 3) supports the following 64-bit drivers when installed on a 64- bit operating system: Ethernet devices EtherNet/IP Driver Remote devices via RSLinx Gateway RS-232 DF1 devices PKTX(D)/PCMK for DH+/DH485 devices U2DHP for DH+ devices 1. The 1784-PKTX(D)/PCMK driver can not be installed on the Windows Server 2003 R2 [64-bit] operating system. 2. If you have problems connecting to a device using the 1784-U2DHP driver, disconnect and reconnect the 1784-U2DHP. For more information, refer to the RSLinx Classic Driver Compatibility Matrix, showing which RSLinx Classic drivers are compatible with specific operating systems. See Rockwell Knowledgebase Answer ID The RSLinx Classic (CPR 9 SR 3) installation program installs or updates the Microsoft.NET Framework to 2.0 SP1. It no longer installs the.net Framework 1.1. The RSLinx Classic (CPR 9 SR 3) installation program now copies all Electronic Data Sheet (EDS) files to your local computer in a compressed format (Microsoft CAB). You can now get EDS files from your computer instead of needing to insert the RSLinx Classic Installation DVD. Windows Terminal Services (Remote Desktop Connection) are supported in RSLinx Classic (CPR 9 SR 3) with some restrictions. For more information, refer to Rockwell Knowledgebase Answer ID 68346, "RSLinx Classic and Terminal Services" The RSLinx Classic SDK now supports the DTL_INIT_EX function, including the DTL_INIT_FLAGS_STARTUP_RSLINX and DTL_INIT_FLAGS_OPERATION_REFCOUNT flags. For more information, see the RSLinx Classic SDK help. The EDS files for some devices have been added or updated in this release. This includes support for new hardware devices. For more detailed information, refer to Rockwell Knowledgebase Answer ID The EDS file name now appears in the Device Properties dialog box to help you in locating the device EDS file. The 1784-U2DHP serial driver now supports offline/remote messaging over DF1. The new FactoryTalk Activation Manager in CPR 9 SR 3 replaces the old set of FactoryTalk Activation Tools (from CPR 9 SR 2). RSLinx Classic v (CPR 9 Service Release 2) The following features have been added in RSLinx Classic v (CPR 9 Service Release 2). Support has been added for the External Access attribute (set in Logix Designer applilcation, starting with version 18 for controllers that support External Access). The RSLinx Classic Data Table Monitor has a new column, Access Rights, that shows the status of the External Access

5 setting in the controller (Read/Write or Read Only). For controllers that do not support External Access, the Access Rights column always displays Read/Write. For more information, see the description of the Data Table in the Data Table Monitor. The installation program for RSLinx Classic also installs the necessary FactoryTalk Services Platform (FactoryTalk Services Platform version CPR 9 SR 2) components if they are not installed or need to be updated. If FactoryTalk Services Platform CPR 9 or CPR 9 SR 1 is already installed, the RSLinx Classic installation program updates the necessary components to CPR 9 SR 2. If FactoryTalk Services Platform CPR 7 or older is already installed, the RSLinx Classic installation program installs only the required components that are compatible with all versions of FactoryTalk Services Platform. Support has been added for browsing CIP query devices such as the 1797-ACNR, 1794-AENT, and 1794-ACN(R). The ULINT tag type is now supported. You can now uninstall the EDS subsystem and Harmony component installed by RSLinx Classic. Select Start > Rockwell Software > RSLinx > Tools > Uninstall EDS Hardware Installation Tool. You can now stop a driver in RSLinx Classic that is used exclusively by the Autobrowse feature in RSLinx Classic. Added Connected Messaging support for OPC Topic Processor Type "Device w/eds Parameters". This improves the efficiency of the communications in RSLinx Classic, the target device, and any intermediate devices. It increases the amount of data that can be reliably exchanged. It also eliminates the bursts of message requests required when multiple data items are on scan, which often causes overloading of the target device's unconnected buffers and can result in a device lockup. The EDS files for some devices have been added or updated in this release. This includes support for new hardware devices. For more detailed information, refer to Rockwell Knowledgebase Answer ID A new RSLinx Classic Driver Compatibility Matrix has been created, showing which RSLinx Classic drivers are compatible with specific operating systems. For more detailed information, refer to Rockwell Knowledgebase Answer ID For a number of years, there have not been any updates or changes from the OPC Foundation to the automation interface wrapper, RsiOpcAuto.dll. The OPC Foundation recommends using the updated automation interface wrapper, OpcDaAuto.dll, which is now provided with RSLinx Classic instead of RsiOpcAuto.dll. For more detailed information, refer to Rockwell Knowledgebase Answer ID RSLinx Classic v (CPR 9 Service Release 2) The following are additional features in RSLinx Classic v (CPR 9 Service Release 2). RSLinx Classic v (CPR 9 Service Release 2) runs on the Microsoft Vista and Server 2008 operating systems with limitations. See Considerations when using RSLinx Classic with Windows Vista, Windows 7, or Server Support to view and configure device level ring modules (for example, 1756-EN2TR and ETAPxx). For more information, see: View Ethernet status and configuration data for a Device Level Ring-capable module View and configure advanced network parameters for a Device Level Ring-capable module Configure advanced Ethernet port information A new processor type, Device with EDS Parameters, has been added. Tip: If you used DeviceNet as a processor type in RSLinx Classic v and earlier, please select Device with EDS Parameters when using RSLinx Classic v , and then complete your DDE/OPC topic configuration as usual. The 1752-L24BBBE module is included. Tip: If you attempt to configure the 1756-L24BBBE SmartGuard module when using a DeviceNet or USB driver, unexpected communication errors occur. Support for the 1756-A5XT/B 5 Slot Extended Temperature Chassis. 5

6 Obtain the device properties of an unrecognized device (for example, name, vendor, product type and code, revision and serial number, and any fault information present when browsing the device) in RSWho by selecting the unrecognized device, right-clicking the mouse, and selecting Device Properties. The LINT tag type is now supported (excluding instances of RSLinx Classic v on Microsoft Windows 2000 SP4). RSLinx Classic has been successfully tested on dual-core computers. If you are running on Microsoft Windows Vista or Server 2008, RSLinx Enterprise and RSLinx Classic install and use the same dual-channel 1784-PKTX(D) driver. RSLinx Enterprise is assigned to the first channel by default (this cannot be changed). You configure RSLinx Classic to use the second channel. See Configure the 1784-PKTX(D) driver for RSLinx Enterprise and RSLinx Classic for this procedure. If the following communication cards are already installed on your computer, their respective drivers are installed automatically when you install RSLinx Classic: 1784-PCID(S) 1784-PCIC(S) 1784-PKTX(D) 1784-PKTCS Tip: If you are using Microsoft Vista/Windows 2008 Server: During RSLinx Enterprise installation, a Windows Security dialog box is displayed before each driver is installed. Click Install to install the driver and continue product installation. To avoid having to repeat this action for each driver, select Always trust software from "Rockwell Automation." However, if you install these same communication cards on your computer after you install RSLinx Classic, you must manually install their respective drivers from the following path: x:\program Files\Rockwell Automation\Drivers (where x: is the drive you have installed RSLinx Classic). Tip: If you alter the configuration of any one of these cards after installing RSLinx Classic, you must manually configure their respective drivers. For information on configuring the 1784-PKTCS driver, see Manually configuring the 1784-PKTCS driver. RSLinx Classic v (CPR 9 Service Release 1) The following features are additional features in RSLinx Classic v (CPR 9 Service Release 1). RSLinx Classic v (CPR 9 Service Release 1) runs on the Microsoft Vista operating system with limitations. See Considerations when using RSLinx Classic with Windows Vista. RSLinx Classic v (CPR 9 Service Release 1) supports the RSLogix 5000 (v17) partial import online feature. Use this feature to import a ControlLogix project file into a running controller. Refer to the Logix Designer applilcation documentation for more information. Support for the following devices: 1766-LEC MicroLogix 1400 Controller 1756-L65 ControlLogix Controller 1768-L45 CompactLogix Controller 1769-L2x CompactLogix Controller 1769-L23E-QB1B CompactLogix Controller 1769-L23-QBFC1B CompactLogix Controller 1769-L23E-QBFC1B CompactLogix Controller 1756-L63S GuardLogix Safety Controller 1783-Mxxx Managed Switch 1783-MS06T 6 Port Managed Switch Base Unit 1783-MS10T 10 Port Managed Switch Base Unit 1783-MX08T 8 Port Copper Expansion Module 1783-MX08F 8 Port Fiber Expansion Module 1756-EN2TR (Exxx) Two Port Module 6

7 1756-CNB/E Module 1768-CNB and 1768-CNBR Module 1756-CN2/B and 1756-CN2R/B Module 1757-FFLDC Module 1756-DNB/C Module 1784-U2DN Module 1756-RIO Module 1756-EN2F Module 1747-L533 SLC503 Controller 1734-AENTX Module 1783-MSxxx Stratix 8000 Modular Managed Switch 1783-EMSxxx Stratix 6000 Fixed Managed Switch In this release, support for the following drivers has been removed: S-S SD/SD2 for DH+ devices driver 1784-KT/KTX(D) for DH+/DH-485 devices driver 1784-KTC(X) for ControlNet devices RSLinx Classic v (CPR 9) The following are additional features in RSLinx Classic v (CPR 9): RSLinx Classic v (CPR 9) runs on the Microsoft Vista operating system with limitations. See Considerations when using RSLinx Classic with Windows Vista. Support for the 1784-U2DHP Communications Smart Cable. To read about configuring a driver for the 1784-U2DHP Communications Smart Cable, click here. Support for 1756-RM Series A device. RSLinx Classic Lite v (CPR 9) now enables OPC connectivity to FactoryTalk View SE (local and remote), FactoryTalk View ME (local only), and FactoryTalk View Studio. RSLinx Classic for FactoryTalk View (formally RSLinx Classic for RSView) is only required when using RSLinx Classic v and earlier. RSLinx Classic v (CPR 9) The following are additional features in RSLinx Classic v (CPR 9). When configuring an Ethernet driver (AB-ETH), you can append an option (:EIP) to the EtherNet/IP address that specifies the driver will always use the EtherNet/IP protocol for Ethernet devices (for example, :EIP). This feature eliminates connection failures to Ethernet devices via satellite links. EvRSI activation is scheduled to be replaced by FactoryTalk Activation Manager in a future release. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Rockwell Automation Technical Support for information on migrating your activations to FactoryTalk Activation Manager. For Rockwell Automation Technical Support in the U.S. call 1 (440) Outside the U.S. see In RSLinx Classic v , the software supports a seven day activation grace period, allowing you to access the software regardless of the valid activations' availability. RSLinx Classic v can be used on computers with hyperthreading turned on resulting in no performance degradation. All Rockwell Software products in this release, including RSLinx Classic, were tested using the latest anti-virus software. For more detailed information, refer to Rockwell Knowledgebase technical note A RSLinx Classic v The following are additional features in RSLinx Classic v

8 Support for the SmartGuard 600 (Catalog number: 1752-L24BBB) safety device. To read about the SmartGuard USB driver that was added for the device, click here. IMPORTANT! Keep the following in mind when working with the SmartGuard 600 safety device. Support for 1756-EN2T/A, 1756-CN2R/B, 1756-L64, and 1768-CNB devices. Support for DH-485 UIC devices (for example, 1747-UIC device). A DH-485 UIC driver type was added to the list of available drivers. IMPORTANT! Keep the following in mind when working with DH-485 UIC devices. Upload EDS file from device. With this feature, you can register the EDS file for your device from within RSLinx Classic after completing the following steps: 1. Connect your device to the computer. 2. Open RSLinx Classic, and look for the device. 3. Once you find it, right-click it, and click the Upload EDS file from device option. 4. Run the EDS wizard to register the EDS file. Autoload and shortcut feature for USB Driver. With this feature RSLinx Classic can automatically configure itself when connecting to a network interface via a USB port. Supported network interfaces are the 1756-EN2T and the 1756-CN2R. RSLinx Classic v and later does not support the 1784-KT, 1784-KTX(D) and 1784-KTC(X) cards on Windows 2003 R2. They are supported only on Windows 2000 and Windows XP. RSLinx Classic v and later no longer supports the 1747-PIC device in Windows 2003 or later. 8

9 System requirements To use RSLinx Classic v (CPR 9 Service Release 6), your personal computer must meet the following minimum hardware and software requirements: Hardware requirements To install RSLinx Classic, you need the following hardware: A Pentium 100MHz processor with at least 32 Megabytes (MB) of RAM. This version of RSLinx Classic does not run on Alpha, MIPS, or Power computerprocessors. At least 35 MB of available hard drive space; more hard disk space may be required for specific application features. A 16-color, SVGA display with 800 by 600 or greater resolution. A mouse or other Windows-compatible pointing device. An Ethernet card and/or Allen-Bradley communications device or cable. Software requirements For the latest information regarding software platform support, refer to RSLinx Classic v (CPR 9 Service Release 6) runs on the Microsoft Vista SP1, Windows 7, and Windows Server 2008 operating systems with limitations. See Considerations when using RSLinx Classic with Windows Vista, Windows 7, or Server The installation of RSLinx Classic includes Microsoft.NET v3.5 SP1. During the RSLinx Classic installation, you are prompted to automatically install this component if it is not already present. 9

10 Silent installation RSLinx Classic v (CPR 9 SR 6) supports silent mode to install the software without any dialog boxes, messages, or user intervention. The command line syntax is: Setup.exe /q ALLUSERS=1 The command line install has these options: /qb : basic user interface /qn : no user interface /q or /quiet : quiet, no user interaction Please note the following when using silent mode installation: On Windows Vista, Windows 2008, and Windows 7, RSLinx Classic defaults to run as application. If FactoryTalk Services Platform v (CPR 9 SR 6) is not installed, you must install FactoryTalk Services Platform first. If previous versions of FactoryTalk Services Platform is installed, upgrade FactoryTalk Services Platform to v first before you install RSLinx Classic v (CPR 9 SR 6). If RSLinx Classic v (CPR 9 SR 6) is installed using silent mode on a 64-bit operating system, you must manually install x64 driver package after you complete the RSLinx Classic installation. To manually install x64 driver package, run it from RSlinx Classic v (CPR 9 SR 6) installation directory: \Redist\RSLinx\ENU\Redist\KN64Bit\DriverPkgx64.msi. Note: If RSLinx Classic v (CPR 9 SR 6) is installed using silent mode on Microsoft Windows Server bit operating system, after you complete the RSLinx Classic v installation, you must manually install a certificate before the x64 driver package installation. If RSLinx Classic v (CPR 9 SR 6) is installed using silent mode on 32-bit operating systems, you must manually install the USB CIP package after you complete the RSLinx Classic installation. To manually install the USB CIP package, run it from RSlinx Classic v (CPR 9 SR 6) installation directory: \Redist\RSLinx\ENU\Redist\USBCIP\Setup.Exe. Note: If RSLinx Classic v (CPR 9 SR 6) is installed using silent mode on Microsoft Windows XP 32-bit, or Microsoft Windows Server bit operating system, after you complete the RSLinx Classic v installation, you must manually install a certificate before the USB CIP package installation. If RSLinx Classic v (CPR 9 SR 6) is installed using silent mode, you must manually install Windows Firewall Configuration Utility after you complete the RSLinx Classic v installation. To manually install Windows Firewall Configuration Utility, run it from RSlinx Classic v (CPR 9 SR 6) installation directory: \Redist\RSLinx\ENU\Windows Firewall Configuration Utility msi. During the RSLinx Classic silent installation, you may see one or two Windows Security dialog boxes: If the dialog box states, "Windows can't verify the publisher of this driver software", please click Install this driver software anyway to continue the installation. If the dialog box asks, "Would you like to install this device software?", select the Always trust software from Rockwell Automation check box and then click Install. Selecting the check box prevents this dialog box from appearing again. 10

11 Considerations when using RSLinx Classic with Windows Vista, Windows 7, or Server 2008 Keep the following in mind when using RSLinx Classic with Microsoft Windows Vista Business SP1 [32-bit], Microsoft Windows Vista Home Basic SP1 [32-bit], Microsoft Windows 7 [32/64-bit], or Microsoft Windows Server 2008 [32/64-bit]: RSLinx Classic defaults to starting as an application. If RSLinx Classic is running as a service, there is no graphical user interface (GUI). If you need to configure RSLinx Classic, you must be in application mode. To switch between running as a service or application use the RSLinx Classic Launch Control Panel. The following communication drivers are supported and are available on the Configure Drivers dialog box: 1784-U2DHP for DH+ RS-232 DF1 devices Ethernet devices Ethernet/IP Driver 1784-PKTX(D)/PCMK for DH+/DH-485 devices DF1 Polling Master Driver 1784-PCIC(S) for ControlNet devices DF1 Slave Driver DH485 UIC devices Virtual Backplane (SoftLogix 58xx, USB) DeviceNet Drivers (1770-KFD, 1771-SDN, and 1747-SDN) SLC 500 (DH485) Emulator driver SmartGuard USB Driver Remote Devices via RSLinx Gateway The following communication drivers are not supported: 1784-PCC for ControlNet devices 1747-PIC/AIC+ Driver DeviceNet Drivers (1784-PCD/PCIDS) PLC-5 (DH+) Emulator SoftLogix5 driver The DF1 Polling Master Driver and DF1 Slave Driver do not support hardware handshaking control. At the end of the RSLinx Classic installation, the installation program attempts to install the Rockwell Automation USB CIP Driver - this driver is used for Rockwell Automation USB devices and is represented by the 'Virtual Backplane (SoftLogix58xx, USB driver)' type on the Configure Drivers dialog. To successfully install this driver, you must click 'Install this driver software anyway' on the Windows Security dialog that is displayed. RSLinx Classic does not start properly when it is configured to run as an administrator and you attempt to log on as a standard user. When you run the Backup/Restore utility, the Restart RSLinx Classic when finished checkbox is not available on the Shutdown RSLinx Classic dialog box. If you attempt to view the Support Services (support.hlp) or Activation (copyprot.hlp) information, an error message is launched and the online help files are not displayed. To view the Support Services or Activation information, please see the Getting Results Guide for your product. UAC (User Account Control) is a feature of Microsoft Windows Vista that helps protect your computer from damage by programs that attempt to perform administrative tasks on your computer without your knowledge. By default, UAC is active, and prompts you for administrative credentials, or to confirm that an executable file (*.exe) associated with a menu item, button, or other item, is safe to run. If you have UAC enabled, you are prompted to confirm your 11

12 administrator privileges (enter a user name and password) when performing the following RSLinx Classic-specific tasks: Installing RSLinx Classic Running the Backup/Restore Utility Registering EDS files via the EDS Hardware Installation Tool Saving related files (for example, the event log) to the C: drive on your computer. You will be instructed to save to an alternate drive location. Note: If you click Change to repair FactoryTalk Services Platform from Control Panel when UAC is enabled, you may see the error 1722 message. To work around this, click OK to close the error message, and repair FactoryTalk Services Platform again. [276317] 12

13 DEP settings DEP (Data Execution Prevention) is a security feature that is supported by both hardware and software. It is intended to prevent running malicious code in the Microsoft Windows XP (Service Pack 2 and Service Pack 3) and Microsoft Windows Server 2003 (Service Pack 1 and R2) operating systems. DEP Settings The DEP settings determine which applications and components are covered by DEP protection. They apply to both hardware-supported and software DEP features. On computers with the necessary hardware capabilities, hardware-supported DEP features are enabled for the same set of applications and components as the software DEP features. The following table explains the possible DEP settings and if they are supported by Rockwell Software products. Note: Rockwell Software recommends that you use the OptIn DEP settings unless you have a specific reason to change them. DEP Setting Description Supported by Rockwell Software Products? AlwaysOn OptIn OptOut AlwaysOff Full DEP protection for the entire system (all applications and components, no exceptions). DEP-enabled only for Windows system components and for applications that explicitly r;opt in. This is the default setting for Microsoft Windows XP (Service Pack 2). DEP-enabled for all processes except those that explicitly r;opt out. This is the default setting for Microsoft Windows Server 2003 (Service Pack 1 and R2). DEP protection is disabled for the entire system (all applications and components, no exceptions) Note: Rockwell Software does not recommend using this setting, since it will make your system more vulnerable to malicious code. No Yes Yes Yes Changing DEP settings To change the DEP settings, select Control Panel > System > Advanced > Performance Settings > Data Execution Prevention. The Turn on DEP for essential Windows programs and services only setting corresponds to the OptIn setting, and the Turn on DEP for all programs and services except those I select setting corresponds to OptOut setting. Tip: Keep the following in mind: You must be an administrator of your computer to change these settings. You must reboot the computer for the DEP setting changes to take effect. 13

14 Hardware DEP Settings Hardware DEP uses the processor to mark memory so that code cannot be run from data regions. When code attempts to run in these marked areas, the processor generates an exception. If you are using Microsoft Windows XP (Service Pack 2) or Microsoft Windows Server 2003 (Service Pack 1 and R2) operating systems, the offending program is stopped. Hardware DEP is also enabled as the factory default setting. This feature is turned on or off in the computer BIOS settings. To determine whether your hardware supports DEP, refer to the hardware manual or contact your hardware manufacturer. For additional information, see the Microsoft Knowledge base article at: 14

15 Software compatibility RSLinx Classic v (CPR 9 Service Release 6) is a component aligned to FactoryTalk View v RSLinx Classic v has been tested, and is compatible, with the following products: FactoryTalk Services Platform v FactoryTalk Activation Manager v FactoryTalk View v RSLinx Classic v , Logix Designer v21.00, and device profiles that ship with Logix Designer v21.00 are not compatible with: RSNetWorx v or earlier DeviceNet Tag Generator v RSNetWorx and the DeviceNet Tag Generator must be upgraded prior to installing these products. 15

16 RSLinx Classic upgrade instructions Perform the following steps to upgrade to RSLinx Classic v (CPR 9 Service Release 6): 1. Close your current version of RSLinx Classic. 2. Insert the RSLinx Classic v (CPR 9 Service Release 6) product DVD. Perform the installation steps as presented on the screen. Tip: The old version of RSLinx Classic that exists on your computer is automatically uninstalled when you install RSLinx Classic v (CPR 9 Service Release 6). 3. Reboot your computer. 16

17 Anomalies fixed The following anomalies were fixed in RSLinx Classic v (CPR 9 Service Release 6): Autobrowse doesn't take effect after adding Ethernet nodes. [273057] "Unable to continue installing EDS files" error message pops up when silent install RSLinx Classic on Microsoft Windows Server 2003 R2 SP2 [32-bit] operating system. [275953] After the installation of RSLinx Classic, RSLinx Classic runs in RSLinx Classic Lite mode, instead of RSLinx Gateway mode. [276163] Topic configuration path loses after computer restart. [275568] EDS cannot be uploaded successfully when log on as standard user. [274058] 1756-HIST module shows as an unrecognised device in RSLinx Classic v [275453] In RSWho, when remove the second port of a device that has two ports available, extra browsing data appears under the first port. [275991] 17

18 Known anomalies The following known anomalies exist in RSLinx Classic v (CPR 9 Service Release 6): Backup and Restore CFG - DeviceNet CFG - DF1 and DF1(Master and Slave) CFG - DH+ and DH485 CFG - Emulator and Softlogix CFG - EtherNet and EtherNet/IP CFG - SmartGard CFG - USB and Virtual Backplane FactoryTalk Activation Harmony Installation RSLinx Gateway RSWho Browse Server OPC Data (Local) User Documentation 18

19 Backup and Restore If you want to backup or restore the RSLinx Classic configurations, you must have Windows administrator privileges on the computer. If you do not have Windows administrator privileges, you cannot backup or restore the RSLinx Classic configurations. See also Known anomalies i

20 CFG - DeviceNet To configure the KFD Modem Dialer driver, you need to disable the hardware handshaking between the remote modem and the KFD. See also Known anomalies ii

21 CFG - DF1 and DF1(Master and Slave) If you attempt to autoconfig a DF1 driver and it does not succeed, place the processor in program mode and attempt the autoconfig again. See also Known anomalies iii

22 CFG - DH+ and DH485 RSLinx Classic v (CPR 9) and later supports the 1747-PIC/AIC driver on Windows XP, XP SP1, or XP SP2 only. Read the considerations when working with DH-485 UIC devices topic for a list of known anomalies or things to keep in mind when working with the device. You cannot download data to a Standard Panel View on a DH+ network if your computer is connected to the Standard Panel View via RSLinx Classic > EtherNet > 1756-ENBT Backplane > 1756-DHRIO > DH+ network path. RSLinx Classic does not support DH connected to a KF2. Duplicate nodes are not detected when configuring the 1784-KT(D) card. When configuring the 1784-KT(D) card, use a station address that is not in use by another device. The 1770-KF2 and 1770-KF3 do not support offlink messages. Therefore, when using these devices, you cannot browse through bridges such as 1785-KA, 1785-KA5, or 1756-DHRIO. If the 1784-PCMK driver is a duplicate node, all stations in RSWho appear as a question mark with a red X. Since both PKTXD card channels share the same interrupt, you cannot configure one channel of the card for SoftLogix 5 and the other for RSLinx Classic. You can configure RSLinx Classic and SoftLogix 5 to use separate PKTX(D) cards. See also Known anomalies iv

23 CFG - Emulator and Softlogix Adding the SLC 500 (DH485) Emulator driver in RSLinx Classic, and then clicking Cancel on the Configure SLC 500 (DH485) Emulator Driver dialog box may cause RSLinx Classic to exit unexpectedly on Windows Vista, Windows 2008, and Windows 7 operating systems. [269134] See also Known anomalies v

24 CFG - EtherNet and EtherNet/IP EtherNet/IP driver cannot recognize PLC5 and SLC devices when using Remote subnet. When a :6Ah error is generated in the DDE/OPC Communications Event Log (for example, AB_ETH-1\ : S:42 : 09/26/03-13:47:28 : 6Ah), append an option (:V4) to the EtherNet/IP address while configuring an Ethernet driver (AB-ETH) that specifies the driver always uses the legacy CSPV4 protocol for SLC 500 processors. For example, :V4. Devices browsed on previous Ethernet subnet were not removed after the EtherNet/IP driver's configuration is changed to another remote Ethernet subnet. [273876] See also Known anomalies vi

25 CFG - SmartGard Read the considerations when working with the SmartGuard 600 safety device topic for a list of known anomalies or things to keep in mind when working with the device. See also Known anomalies vii

26 CFG - USB and Virtual Backplane If a yellow exclamation is observed on 1784-U2DHP driver on first use, disconnect and reconnect the 1784-U2DHP device, and see if the issue gets resolved. [269399] The Found New Hardware dialog box opens every time when different types of USB devices are plugged into the computer. You can install the driver by selecting the following directory: C:\Program Files\Rockwell Automation\Rockwell Automation USBCIP Driver Package\UsbCipDriver\. [275951] Note: It is assumed that you installed RSLinx Classic on a Windows system at C:\Program Files\Rockwell Software\RSLinx. See also Known anomalies viii

27 FactoryTalk Activation If you have a disconnected server machine, RSLinx Classic hangs for up to two minutes during startup as it checks the remote server for an activation file. To work around this, go to Find Available Activations, select Update Activation Search Path and clear the disconnected server reference check box. See also Known anomalies ix

28 Harmony FactoryTalk View Studio startup performance tends to degrade over time when there are a large number of devices on the network. The solution is to delete the Harmony.HRC and Harmony.RSH files located in "C:\Program Files\Rockwell Software\RSCommon". [218691] See also Known anomalies x

29 Installation If there are a large number of tags in the controller and the network performance is low, all of the tags may not be displayed in OPC or the Data Monitor. To resolve this condition, see Displaying large numbers of tags in OPC or the Data Monitor. [261725] If you are using Microsoft Windows Vista and attempt to go online with a controller through a 1784-PKTX card to a remote DH-485 to DH+ network, RSLogix 5 may crash. See Considerations when using RSLinx Classic with Windows Vista, Windows 7, or Server 2008 for additional information when using the Microsoft Vista operating system. [263358] See also Known anomalies xi

30 RSLinx Gateway From a client, you cannot browse the Remote Devices via RSLinx Classic Gateway driver, which was configured on a RSLinx Classic Gateway server. [21836] See also Known anomalies xii

31 RSWho Browse RSWho with the RSLinx Gateway is unusable to go online to processor in RSLogix5 or RSLogix500 software. To select a processor connected to a RSLinx Gateway, configure an RSLinx Classic driver, using the Remote Devices via RSLinx or 1756-ENET Gateway driver. See also Known anomalies xiii

32 Server OPC Data (Local) Offline browsing does not work to an.acd file on a different network machine. The.acd file must be on the local machine. OPC browse is not supported for.net OPC applications. In Logix Designer, you can change the External Access attribute for a tag while online with the controller (for controllers that support External Access). Note: The following scenarios may require you to restart RSLinx Classic and data clients: If a controller is replaced with a different controller, even if it has the same program. [265753] If tag attributes for tags on scan are changed and a new program is downloaded to the controller. If tag attributes for tags on scan are changed after an Alias Topic switch. [265756, ] See also Known anomalies xiv

33 User Documentation When accessing RSLinx Classic Online Help from Help > RSLinx Classic Help Topics, you see the following error message "An error occurred while trying to start the online help for RSLinx Classic." In the RSLinx Classic help file, the Home selection on the Option button does not function properly. Topics in.chm (Compiled Help Module) files do not display when the help file is opened from a remote computer or a UNC (Universal Naming Convention) path. This affects most Help and Release Notes for Rockwell Software products. Windows Server 2003 SP1 and security updates and include changes to the InfoTech protocol. Microsoft introduced these changes to reduce security vulnerabilities in HTML Help. If you have installed security update , or Windows Server 2003 SP1 or later, you may experience the following symptoms: The features of some of Web applications on the computer no longer work. For example, a topic may not be opened after you click a link. When you try using a UNC path to open a.chm file on a network shared folder, topics in the.chm file do not appear. As a workaround, open the help files from the installation DVD or copy them to a folder on your local computer. If you want the help files to be accessible from a network directory (shared folder), you must use the Registry Editor to modify certain registry entries. Microsoft does not recommend you doing this, but provides the steps in Microsoft Knowledge Base article See also Known anomalies xv

34 Windows and RSLinx Classic v (CPR 9 Service Release 6) issues Windows XP Professional You may experience difficulty configuring the 1784-KTC(X) or the 1784-KTX(D) in Windows XP operating system because of how these legacy ISA cards obtain resources. We recommend using the PCI based cards when using Windows XP operating system. For ControlNet, use the PCIC(S) card, and for DH+ or DH-485, use the 1784-PKTX(D) card. Hardware handshaking with the DF1 polling master and DF1 Slave drivers is not supported in Windows XP operating system. Plug-n-Play drivers for the 1747-UIC, 1784-PCC, 1784-PCD, and SmartGuardUSB-KernelDrivers are located on the RSLinx Classic DVD in the PnP_Drivers directory. You must have administrative privileges to configure drivers and topics. You must have administrative privileges to use the RS-232 DF1 driver. If you have administrative privileges, this driver only displays in RSWho and in the configured drivers list. If you receive an "Unable to open HKCU\Software\Rockwell Software key in the registry!" message, check with your system administrator to get administrative privileges. If RSLinx Classic has a 1784-PCC or a 1784-PCMK driver running, Windows XP operating system cannot go into stand-by mode. 19

35 Upgrade the FactoryTalk platform software FactoryTalk Services Platform installs along with the software products that require it. Installation and upgrade steps vary, depending on which products you are installing or upgrading. For step-by-step instructions, see each product's installation information. If you are upgrading a client computer to FactoryTalk Services Platform version (CPR 9 Service Release 6), you may also need to upgrade the computer hosting the FactoryTalk Network Directory Server to FactoryTalk Services Platform version In this release, several products added new Security Policies that do not function correctly if the FactoryTalk Network Directory Server is not upgraded to include them. For additional information on upgrading a previous version of the FactoryTalk Network Directory Server or updates for the other products that may require updates, see Rockwell Automation Knowledgebase Answer ID Upgrade FactoryTalk platform software: When you upgrade to FactoryTalk Services Platform (CPR 9 SR 6) on a computer that has an earlier version of FactoryTalk Services Platform or FactoryTalk Automation Platform installed, the installation process: Creates a backup file for any existing FactoryTalk Directory already configured on the computer. Should you later need to uninstall the current version and reinstall the earlier version, restore this backup file to return the FactoryTalk Directory to its earlier state. See Restore on an earlier system after upgrading FactoryTalk platform software. Checks for both a Local Directory and a Network Directory on the computer. If a directory is found, the installation process updates it with support for new policies and features, but leaves original security and policy settings unchanged. If either directory has not been created or configured, the installation process does so by automatically adding the local computer account and the local Windows Administrators group to the directory, and by setting a default to grant all new user accounts full access. This step allows any user account with Windows Administrator privileges to immediately log on to the directory, without first having to create a FactoryTalk Administrator account. If necessary, updates each FactoryTalk Directory with new product policies, system policies, and support for new features. Leaves all original security settings, user accounts and groups, and policy settings unchanged. Upgrade computers in a distributed system Upgrade client computers only if the version of the FactoryTalk platform software installed on the FactoryTalk Directory server computer is not compatible with the new versions of the products you are installing. For details about compatible versions of the FactoryTalk platform software, see the documentation provided with your products. If you do need to upgrade client computers, we recommend that you upgrade client computers first, then upgrade the server computer hosting the FactoryTalk Directory Server, and finally, upgrade any remaining run-time server computers last. When upgrading client computers from FactoryTalk Automation Platform version 2.00 (CPR 7), you must upgrade client computers first, and then upgrade the FactoryTalk Directory server computer last. You cannot connect CPR 7 clients to a CPR 9 or later FactoryTalk Network Directory Server. To use the new features available with FactoryTalk Services Platform (CPR 9 SR 6), the FactoryTalk Directory Server computer must be upgraded. Any new features are not supported on a FactoryTalk Directory Server computer that is running an earlier version of the FactoryTalk platform software. If the FactoryTalk Network Directory Server computer is upgraded to FactoryTalk Services Platform (CPR 9 SR 6) or later, then the products installed on all client computers on the network must also be upgraded to compatible versions. For details, see the documentation supplied with your products. Upgrade client computers: 1. Before upgrading to FactoryTalk Services Platform v (CPR 9 SR 6), shut down all Rockwell Automation software products running on the computer. 20

36 2. Some Rockwell Automation software products run as services in the background. Before upgrading to FactoryTalk Services Platform, you might need to uninstall those products. For details, see the user assistance for your product. Upgrade server computers: 1. Before upgrading FactoryTalk Services Platform, all related services running on the computer are automatically shut down. To avoid loss of data, shut down all Rockwell Automation software products running on the computer before beginning the upgrade. 2. Before upgrading a server computer, disconnect the computer from the network. This prevents client computers from accessing the server during the upgrade. If you are running FactoryTalk server products on your computer and you cannot disconnect the computer from the network, uninstall the server products before upgrading FactoryTalk Services Platform on the computer. If you are upgrading the FactoryTalk Network Directory Server computer, you must disconnect the computer from the network before performing the upgrade. 3. Some Rockwell Automation software products run as services in the background. Before upgrading to FactoryTalk Services Platform, you might need to uninstall those products. For details, see the user assistance for your product. 4. When the upgrade is complete, reconnect the server computer to the network. If the installation appears to have stopped responding, see Install appears to stop responding. After upgrading the FactoryTalk platform software, you might need to install updates for the products you are using. See Installing software updates. To identify the installed version of the FactoryTalk platform software: 1. On the Windows Start menu, click Control Panel. 2. Double-click Add or Remove Programs. 3. In the list of installed programs, either FactoryTalk Automation Platform or FactoryTalk Services Platform appears, with the version number shown beside it. 21

37 Application notes Consider the following application notes when using RSLinx Classic v (CPR 9 Service Release 6): View the EDS parameters for a CIP-enabled device Display large numbers of tags in OPC or the Data Monitor Configure the 1784-PKTX(D) driver for RSLinx Enterprise and RSLinx Classic (Vista, Windows 2008, and Windows 7) RSLinx_Enterprise_and_RSLinx_2x_side_by_side_operation Share_a_driver_between_RSLinx_Enterprise_and_RSLinx_Classic Share_the_RSLinx_Enterprise_virtual_backplane_with_RSLinx_Classic Configure an OPC client to obtain data from a processor using an alias topic Rout through bridge devices For a number of years there have not been any changes or updates from the OPC Foundation to the automation interface wrapper, RsiOpcAuto.dll. The OPC Foundation recommends using the updated automation interface wrapper, OpcDaAuto.dll, which is now provided with RSLinx Classic instead of RsiOpcAuto.dll. For more detailed information, refer to Rockwell Knowledgebase Answer ID You cannot configure a 1747-PIC driver while RSLinx Classic is running as a service. Configure a PIC driver only if RSLinx Classic is running as an application, and the Reserve COM Port for Exclusive use by this Driver is enabled. This checkbox ensures RSLinx Classic works properly if you run it as a service. Then, when backing up and restoring the driver, update the COM Port for the PIC on the Communication Port (COM1) in the device manager. Unsolicited messages with a Logix5000 controller on an Ethernet network or a DH+ network. To receive unsolicited DDE messages from a processor through a DHRIO module, and through an ENET module over an Ethernet network, select your DDE topic from the DDE/OPC Topic Configuration dialog box. Then, select Advanced Communication, click Remote, and manually enter the Remote Link ID of the DHRIO channel through which the message is being sent. Newly created DDE topics default to 20 for Limit Maximum Packets. This makes the updates more symmetrical for the group of optimized packets for each topic. For the same functionality on older DDE topics, set Limit Maximum Packets on the DDE/OPC Topic Configuration dialog box, Data Collection tab to 20, or the best value for the PLC and access method. When configuring DDE/OPC topics to receive unsolicited messages from a ControlNet device, from the DDE/OPC Topic Configuration dialog box, select the Advanced Communication tab and select Local route for Local or Remote Addressing. When setting up a DDE topic to a remote processor via ControlLogix Gateway, ensure that unsolicited messages coming to RSLinx Classic to work properly by setting the Remote Link ID to match the Link ID of the remote module (such as DHRIO). Block reads and writes do not work with user defined types (Logix5000 controller). In Windows NT, the PIC/AIC+ and the DF1 Polling Master / Slave drivers (with RTS control enabled only) drivers need their own serial driver (RSSERIAL.SYS rather than SERIAL.SYS) and cannot therefore share an interrupt with another serial device. When using auto configuration on a 1770-KF2/KF3 device, you must set the Station Number to that of the KF2/KF3 before clicking Auto-Configure. Otherwise, Auto-Configure tries to detect the device at the currently selected station, and if the device is a PLC, Auto-Configure configures to the PLC rather than the KF2/KF3. If you restore a Windows NT configuration, and you have a configured KTC(X) or PCMK driver, you must reboot the computer to start the driver. After the first time you configure a 1784-PCC driver in Windows NT, you must reboot your computer before using the driver. The 1784-PCC driver cannot receive unsolicited messages from a processor. For the 1794-AENT and 1756-ENB modules, module statistics on the Port Diagnostics tab display all zeros even though the modules work properly. When you install RSLinx Classic, DTL32.DLL remains in the system directory if it is locked by another application. 22