Release Notes ( 9355-WABx ) RSLinx Classic is the most widely installed communication server in automation today. Version 2.59.02 Catalog Number RSLinx Classic
These release notes describe version information for ( 9355-WABx ) RSLinx Classic is the most widely installed communication server in automation today., version 2.59.02.
System Requirements This release has the following system requirements.
System requirements for RSLinx Classic 2.59.02 To use RSLinx Classic v2.59.02 (CPR 9 Service Release 5), 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 PC processors. 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 communications device or cable. Software requirements To run RSLinx Classic, Microsoft Internet Explorer 6.0 (or later) and Adobe Acrobat Reader 8.1 (or later) is required and one of the following operating systems: Microsoft Windows XP Professional, SP1, SP2, or SP3 [32-bit] Microsoft Windows Server 2003, SP1, SP2, R2, or R2 SP2 [32-bit], or Microsoft Windows Server 2003 R2 Standard SP2 [64-bit] Microsoft Windows Server 2008, SP1, SP2, R2, R2 SP2 [32-bit], or Microsoft Windows Server 2008 Standard SP2, R2 SP1 [64-bit] Microsoft Windows Vista Business SP1, SP2 [32-bit] or Microsoft Windows Vista Home Basic SP1, SP2 [32-bit] Microsoft Windows Vista Home Premium(N) SP1, SP2 [32-bit] or Microsoft Windows Vista Home Premium(N) SP1, SP2 [64-bit] Microsoft Window 7 Professional, SP1 [32-bit] or Microsoft Windows 7 Professional, SP1 [64-bit] Microsoft Window 7 Home Premium [32-bit] or Microsoft Windows 7 Home Premium [64-bit] RSLinx Classic v2.59.02 (CPR 9 Service Release 5) runs on the Microsoft Vista SP1, Windows 7, and Windows Server 2008 operating systems with limitations. 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. For the latest software platform qualification information, refer to Rockwell Knowledgebase Answer ID 42682 42682.. Software compatibility RSLinx Classic v2.59.02 is a component of the latest Rockwell Software Coordinated Product Release (CPR 9 Service Release 5). RSLinx Classic v2.59.02 (CPR 9 Service Release 5) has been tested, and is compatible, with the Rockwell Software CPR 9 Service Release 5 of the following products: FactoryTalk Services Platform (v2.50.00) RSLinx Enterprise (v5.50.00)
System Features This release includes the following system features.
New features for RSLinx Classic 2.59.02 RSLinx Classic v2.59.02 (CPR 9 Service Release 5) The following features have been added in RSLinx Classic v2.59.02 (CPR 9 Service Release 5). Micro850 EDS file is newly supported in RSLinx Classic v2.59.02 (CPR9 Service Release 5). For more hardware support information, refer to Rockwell Knowledgebase Answer ID 58981 58981.. For driver support information, refer to the RSLinx Classic Driver Compatibility Matrix. See Rockwell Knowledgebase Answer ID 58963
RSLinx Classic v2.59.01 (CPR 9 Service Release 5) The following features have been added in RSLinx Classic v2.59.01 (CPR 9 Service Release 5). USB CIP 32 bit driver package is updated to 3.18.02, and USB CIP 64 bit driver package is updated to 1.1.11. For more driver support information, refer to the RSLinx Classic Driver Compatibility Matrix. See Rockwell Knowledgebase Answer ID 58963 58963.. 1756-L71S EDS file is newly supported in RSLinx Classic v2.59.01 (CPR9 Service Release 5). For more hardware support information, refer to Rockwell Knowledgebase Answer ID 58981 58981.. RSLinx Classic v2.59.00 (CPR 9 Service Release 5) The following features have been added in RSLinx Classic v2.59.00 (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 58963 58963.. 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 58981 58981.. RSLinx Classic v2.58.00 (CPR 9 Service Release 4) The following features have been added in RSLinx Classic v2.58.00 (CPR 9 Service Release 4). RSLinx Classic v2.58.00 (CPR 9 SR 4) and later versions displays a message indicates 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 v2.58. Support hot plug and play for Allen Bradley 12 Point Micro810 USB devices. The RSLinx Classic 2.58.00 (CPR 9 SR 4) installation program installs or updates the Microsoft .NET Framework to 3.5 SP1. EvRSI activation is replaced by FactoryTalk Activation since RSLinx Classic v2.58.00 (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. For Rockwell Automation Technical Support in the U.S., call 1 (440) 646-3434. Outside the U.S., see http://www.rockwellautomation.com/locations/. The following 64-bit driver is now supported when installed on a 64-bit operating system: Virtual Backplane Driver 1784-PCIC Driver Ethernet devices EtherNet/IP Driver Remote devices via Linx Gateway RS-232 DF1 devices 1784-U2CN/1784-U2DN USBCIP Devices 1784-PKTX(D)/PCMK for DH+/DH485 devices 1 1784-U2DHP for DH+ devices 2 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. RSLinx Classic v2.57.00 (CPR 9 Service Release 3) The following features have been added in RSLinx Classic v2.57.00 (CPR 9 Service Release 3). The installation program for RSLinx Classic 2.57.00 also installs the necessary FactoryTalk Services Platform (FactoryTalk Services Platform 2.30.00 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 2.57.00 (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. requirements. RSLinx Classic 2.57.00 (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 Linx Gateway RS-232 DF1 devices 1784-PKTX(D)/PCMK for DH+/DH485 devices 1 1784-U2DHP for DH+ devices 2 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 58963 58963.. The RSLinx Classic 2.57.00 (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 2.57.00 (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 CD. Windows Terminal Services (Remote Desktop Connection) are supported in RSLinx Classic 2.57.00 (CPR 9 SR 3) with some restrictions. For more information, refer to Rockwell Knowledgebase Answer ID 68346 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 58981 58981.. 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 v2.56.00 (CPR 9 Service Release 2) The following features have been added in RSLinx Classic v2.56.00 (CPR 9 Service Release 2). Support has been added for the External Access attribute (set in RSLogix 5000, 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 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. The installation program for RSLinx Classic 2.56.00 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 im proves 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 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 58981 58981.. 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 58963 58963.. The automation interface wrapper, RsiOpcAuto.dll, has not been updated with changes from the OPC Foundation for a number of years. 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 64055 64055.. RSLinx Classic v2.55.00 (CPR 9 Service Release 2) The following features have been added in RSLinx Classic v2.55.00 (CPR 9 Service Release 2). RSLinx Classic v2.55.00 (CPR 9 Service Release 2) runs on the Microsoft Vista and Server 2008 operating systems with limitations. Support has been added to view and configure device level ring modules (for example, 1756-EN2TR and 1783-ETAPxx). A n ew p rocessor type, Device with E DS Pa rameters, has been added. Tip: If you used DeviceNet as a processor type in RSLinx Classic v2.54 and earlier, please select Device with EDS Parameters Tip: Parameters when when using RSLinx Classic v2.55, and then complete your DDE/OPC topic configuration as usual. The 1752-L24BBBE module has been added. Tip: If you attempt to configure the 1756-L24BBBE SmartGuard module when using a DeviceNet or USB driver, unexpected communication errors Tip: occur. Support has been added for the 1756-A5XT/B 5 Slot Extended Temperature Chassis. You can now 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 Properti Properties es
.
The EDS files for some devices have been added or updated in this release. For more detailed information, refer to Rockwell Knowledgebase Answer ID 58981 58981.. 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 58963. 58963. The LINT tag type is now supported (excluding instances of RSLinx Classic v2.55.00 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 1784PKTX(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. Use the following procedure to configure the 1784-PKTX(D) driver for RSLinx Enterprise and RSLinx Classic: If you do not already have a 1784-PKTX(D) driver in RSLinx Enterprise, then right-click RSLinx Enterprise, click Add Driver , and select a 1784PKTX(D) driver from the list. The DH+ Driver Properties or DH485 Driver Properties dialog box displays. Verify the information in the dialog box fields is correct, and click OK . Start RSLinx Classic, and click Communications > Configure Drivers. Drivers . The Configure Drivers dialog box displays. From the Available the Available Driver Types list, click the 1784-PKTX(D) driver , and then click Add click Add New . In the Add New RSLinx Classic Driver dialog box, enter a driver name or use the default name. Click OK . The Configure 1784-PKTX/PKTXD dialog box displays. Select the driver type from the Value Value list, and click OK . 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 will be Tip: displayed before each driver is installed. Click Install Install to 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. RSLinx Classic v2.54.00 (CPR 9 Service Release 1) The following features have been added in RSLinx Classic v2.54.00 (CPR 9 Service Release 1): RSLinx Classic v2.54.00 (CPR 9 Service Release 1) runs on the Microsoft Vista operating system with limitations. RSLinx Classic v2.54.00 (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 RSLogix 5000 product 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 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, the 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 The LINT tag type is now supported (excluding instances of RSLinx Classic v2.54.00 on Microsoft Windows 2000 SP4). RSLinx Classic v2.53.00 (CPR 9) The following features have been added in RSLinx Classic v2.53.00 (CPR 9): RSLinx Classic v2.53.00 (CPR 9) runs on the Microsoft Vista operating system with limitations. Support for the 1784-U2DHP Communications Smart Cable. Support for 1756-RM Series A device. RSLinx Classic Lite v2.53.00 (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 v2.52.00 and earlier. RSLinx Classic v2.52.00 (CPR 9) The following features have been added in RSLinx Classic v2.52.00 (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, 130.130.130.130:EIP). This feature eliminates connection failures to Ethernet devices via satellite links. EvRSI activation will be replaced by FactoryTalk Activation 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. For Rockwell Automation Technical Support in the U.S. call 1 (440) 646-3434. Outside the U.S. see http://www.rockwellautomation.com/locations/. In RSLinx Classic v2.52.00 (CPR 9), the software supports a seven day activation grace period, allowing you to access the software regardless of the
valid activations' availability. RSLinx Classic v2.52.00 (CPR 9) can be used on computers with hyperthreading turned on resulting in no performance degradation. All Ro ckwell Software products in this release, including RSLinx Classic, have been tested using the latest anti-virus software. For more detailed information, refer to Rockwell Knowledgebase technical note A16025 note A16025 2633 2633.. RSLinx Classic v2.51.00 (CPR 7) The following features have been added in RSLinx Classic v2.51.00 (CPR 7): 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: IMPORTANT! If you are installing SmartGuard driver on a computer that already has RSLinx Classic installed, make sure to re-start RSLinx Classic after installing the SmartGuard driver. If you do not re-start RSLinx Classic, you will not be able to configure the driver. Although you can communicate over the DeviceNet network through the USB port of the SmartGuard device, the USB-to-DeviceNet bridging capability is limited. For example, you can NOT configure 1734-ADN or 1753-DNSI modules through SmartGuard. Use another DeviceNet interface, such as a 1784-PCD card, to configure these devices. 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 IMPORTANT! Keep the following in mind when working with DH-485 UIC devices. If you plug-in your DH-485 UIC device on a computer that is running Windows 2000 and has 1752-L24BBB SmartGuard controller already installed, the device will not be recognized by the Windows 2000 Plug and Play feature. To fix the problem, follow these steps: 1. Go to Start > Settings > Control Panel > System . On the System Properties dialog box, click the Hardware Hardware Tab. Tab. 2. On the Hardware Tab, click the Device Manager button. 3. In the Device Device Manager window, expand the Universal Serial Bus controllers controllers tree. 4. You will see an entry for FTDI FT8U2xx Device FT8U2xx Device.. Right-click it, and select Properties Properties.. 5. On the Properties dialog box, click the Update driver button button to update the driver. 6. If you change the Station Number (node address) of a DH-485 UIC device without first removing or re-installing the device, the dev ice will stop functioning. If you want to change the Station Number, you must re-install the DH-485 UIC device, and then use the Configure UIC devices dialog box to set the Station Number. Upload EDS file from device. This feature allows you to register the EDS file for your device from within RSLinx Classic by following the steps listed below: 1. Connect your device to the computer. 2. Open RSLinx Classic, and look for the device. 3. Once you find it, right-click right-click it, it, and select the Upload EDS file from device option. device option. 4. Run the EDS wizard to register the EDS file. Autoload and shortcut feature for USB Driver. This feature allows RSLinx Classic t o 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 v2.51.00 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 v2.51.00 no longer supports the 1747-PIC device in Windows 2003 or later.
Corrected Anomalies This release corrects the following anomalies.
Anomalies fixed for RSLinx Classic 2.59.02 The following anomalies were fixed in RSLinx Classic v2.59.02 (CPR 9 Service Release 5): EDS feature group cannot be customized during RSLinx silent mode. [272825] Insufficient error message when setting Ethernet port speed or duplex on 1769-L3y. [272617] RSLC stops serving OPC data when first chance exception occurs. [272608] [272624] 1784-PKTCS Driver cannot be installed on Microsoft Windows Server 2008 SP2 [64-bit] or Microsoft Windows Vista Business SP2 [64-bit] operating system. [272724] Unexpected options set in parallel in RSLinx Classic v2.58.00 EN2T Port Configuration. [ 294099]
Known Anomalies This release has the following known anomalies.
Known anomalies for RSLinx Classic 2.59.02 The following known anomalies exist in RSLinx Classic v2.59.02 (CPR 9 Service Release 5): Micro800 series controllers do not support read/write tags via OPC or Data Monitor. To access the controller data, you can use the Modbus driver of KEPServer Enterprise.
The 1784-PKTX(D)/PCMK driver can not be installed on the Windows Server 2003 R2 [64-bit] operating system. [289762] If you have problems connecting to a device using the 1784-U2DHP driver, disconnect and reconnect the 1784-U2DHP. [269399] RSLogix 5000, starting with version 18, allows you to change the External Access attribute for a tag while online with the controller (for controllers that support External Access). Please be aware of the following issues that 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, 266168] Adding the SLC 500 (DH485) Emulator driver in RSLinx Classic, and then clicking Cancel 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] FactoryTalk View Studio 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] Install, upgrade, and downgrade issues with RSLinx Classic v2.57 (CPR 9 SR 3) and the Redundancy Module Config Tool (RMCT): The RSLinx Classic 2.57 (CPR 9 SR 3) Installer also installs RMCT v6.2.10.0. If RMCT v6.2.10.0 has already been installed manually with a prior version of RSLinx (before v2.57), it may not function or start after upgrading to RSLinx Classic v2.57 (CPR 9 SR 3). To restore RMCT, shut down RSLinx Classic, start Add or Remove Programs from Windows Control Panel. Select Redundancy Module Config Tool, and then click Change/Remove. When the Redundancy Module Config Tool Setup starts, select Repair click Next to continue. When you restart RSLinx Classic v2.57 (CPR 9 SR 3), the RMCT will be restored. If you use Add or Remove Programs to remove the rmct after removing a RSLinx Classic version before v2.57, you may see error messages about .dll files failing to unregister. Click OK OK in the message, and the removal process will complete successfully. If you have already installed a version of the RMCT v6.2.10 or higher, and you want to revert to RSLinx Classic v2.55 or earlier (with the bundled RMCT v5.2.3 or earlier), the current version of the RMCT must be removed prior to removing RSLinx Classic v2.57 (CPR 9 SR 3). Otherwise, you will see an error message and the newer version of the RMCT will remain installed after installing RSLinx Classic v2.55. 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. [261725] To resolve this condition, perform the following steps: 1. Close RSLinx Classic. 2. Click Start > Run. Run . 3. In the Run command line, type: regedit. The Registry Registry Editor appears. appears. 4. In the Registry Key window, window, navigate to HKEY_Local_Machine\Software\Rockwell HKEY_Local_Machine\Software\Rockwell Software\RSLinx\Settings. 5. Under the Settings key, click Edit > New > DWORD DWORD value, and then type the following DWORD name: ACDTimeout. 6. Double-click the DWORD ACDTTimeOut ACDTTimeOut;; the Edit DWORD Value dialog box appears. 7. In the Value Data field, enter a time out value (in seconds) larger larger than the default time out value (21 seconds). Tip: Rockwell Tip: Rockwell Automation suggests a time out value of 180 seconds. This value can then be adjusted based on the number of tags in your controller program. 8. Click OK OK.. 9. Exit the Registry Editor. 10. Run RSLinx Classic again to confirm that the new time out value is sufficient for the number of tags in your controller prog ram. 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. [263358] If you are upgrading a client computer to FactoryTalk Services Platform version 2.30.00 (CPR 9 Service Release 3), ensure you also upgrade the computer hosting the FactoryTalk Network Directory Server to the latest version of the FactoryTalk Services Platform installed on any client computer on your network. Failure to do so might cause unexpected results for RSLogix Architect, RSNetWorx, and RSLogix 5000, version 18. RSLinx Classic v2.53.00 (CPR 9) and later supports the 1747-PIC/AIC driver on Windows XP, XP SP1, or XP SP2 only. Do not give the same name to RSLinx Enterprise shortcuts and RSLinx Classic topics. If a shortcut has the same name as a topic, tags will not be displayed for one of them during a tag browse. If you want to backup/restore your RSLinx Classic configurations, you must have Windows administrator privileges on the computer. If you do not have Windows administrator privileges, you will not be able to backup/restore your RSLinx Classic configurations. Keep the following in mind when working with the SmartGuard 600 safety device: If you are installing SmartGuard driver on a computer that already has RSLinx Classic installed, make sure to re-start RSLinx Classic after installing the SmartGuard driver. If you do not restart RSLinx Classic, you will not be able to configure the driver. Although you can communicate over the DeviceNet network through the USB port of the SmartGuard device, the USB-to-DeviceNet bridging capability is limited. For example, you CANNOT configure 1734-ADN or 1753-DNSI modules through SmartGuard. Use another DeviceNet interface, such as a 1784-PCD card, to configure these devices. Keep the following in mind when working with DH-485 UIC devices: If you plug-in your DH-485 UIC device on a computer that is running Windows and has 1752-L24BBB SmartGuard controller already installed, the device will not be recognized by the Windows Plug and Play feature. To fix the problem, follow these steps: 1. Go to Start > Settings > Control Panel > System. On the System Properties dialog box, click the Hardware Tab. 2. On the Hardware Tab, click the Device Manager button. 3. In the Device Manager window, expand the Universal Serial Bus controllers tree. 4. You will see an entry for FTDI FT8U2xx Device. Right-click it, and click click Properties. 5. On the Properties dialog dialog box, click the Update driver button. button. If you change the Station Number (node address) of a DH-485 UIC device without first removing or re-installing the device, the device will stop functioning. If you want to change the Station Number, you must re-install the DH-485 UIC device, and then use the Configure UIC devices dialog box to set the Station Number. 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 . You cannot use DDE/OPC to read or write data in a Logix processor that has a tag mapped to a PLC/SLC file number and a topic configured as a PLC-3 processor processor type. Use a PLC-5 typed topic instead. When accessing RSLinx Classic Online Help from Help > RSLinx Classic Help Topics, Topics , you see the following error message "An error occurred while trying to start the online help for RSLinx Classic." Topics in compiled help files (.chm), do not display when the help file is opened from a remote computer or UNC path. This affects most online Help
and release notes for Rockwell Software products. If you have installed security update 896358 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 displayed after you click a link. When you try use a Universal Naming Convention (UNC) path to open a Compiled Help Module (.chm) file on a network shared folder, topics in the .chm file do not appear. Windows Server 2003 SP1 and security updates 896358 and 840315 include changes to the InfoTech protocol. Microsoft introduced these changes to reduce security vulnerabilities in HTML Help. As a workaround, open the help files from the installation CD 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 do this but has provided the steps in Microsoft Knowledge Base article 896054 896054.. When RSLinx Classic is re-installed, all security settings that were previously configured for networks and devices are lost. You must redefine these security settings in the Networks and Devices tree, or in RSWho. OPC browse is not supported for .NET OPC applications. If you encounter a condition where you are not getting data from a SLC 500 processor and that processor: refuses a connection from RSLinx Classic, and generates a :6Ah error in the DDE/OPC Communications Event Log (for example, AB_ETH-1\130.130.130.130: S:42 : 09/26/03 - 13:47:28 : 6Ah) you can 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, 130.130.130.130:V4. Offline browsing will not work to an .acd file on a different network machine. The .acd file must be on the local machine. EtherNet/IP driver cannot recognize PLC5 and SLC devices when using Remote subnet. 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. There are no known issues with the KT(X)(D) card. Do not use a network shortcut to go online with RSNetWorx for DeviceNet. RSLinx Classic cannot use interrupts on the KT or KTX drivers when installed in a DELL Optiplex GXPro computer. The KT or KTX card defaults to no interrupts for this computer. If you attempt to autoconfig a DF1 driver and it does not succeed, place the processor in program mode and attempt the autoconfig again. RSLinx Classic does not support DH connected to a KF2. When configuring the WinLinx TCP Client driver with RSLinx Classic Gateway, the Refresh Device List button does not return a list of active stations on a specific network. If you have a disconnected network drive mapping and the server machine is not up, RSLinx Classic hangs for up to two minutes during startup as it checks the dead drive for an activation file. To workaround this, either disconnect the drive mapping if you no longer need it, or if your activations are all on the C drive, add CHECKDRIVES=C to the [Common] section of the %WINDIR%\ROCKSOFT.INI file. Multiple configuring, deleting, and re-configuring KT/KT(X)/PKTX(D)/PCMK devices with RSLinx Classic may result in situations where the ABKT driver reports resource conflicts or memory conflicts in the System Event log. The result is the inability to start the specific instances of drivers reporting the errors. If you encounter this situation, the workaround is to delete all driver instances, reboot Windows NT, and reconfigure the drivers. This limitation only applies to the Windows NT version of the 1784- KT/KT(X)/PKTX(D)/PCMK driver. 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 1794-ACN adapter does not respond to UCMM requests sent from the 1770-KFC driver. RSLinx Classic will not browse Remote Devices via Linx Gateway or SoftLogix drivers configured on a Linx Gateway from a client browsing the gateway. When using RSWho to select a processor for RSLogix5, RSLogix500, or RSLogix Frameworks, you cannot go online to that processor if you selected it using the RSWho "Linx Gateways" driver. To select a processor connected to a Linx Gateway, configure a RSLinx Classic driver using the "Remote Devices via Linx or 1756-ENET Gateway" driver. Only selections made from the RSWho "Linx Gateways" driver are unusable. 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. When running RSLinx Classic as a service in interactive mode (with a logged-in user), you cannot perform secured actions. You will receive the "The user name could not be found" error for all actions because security interprets the RSLinx Classic user of "SYSTEM" running. Therefore, it is not recommended that you use RSLinx Classic Configuration Security when running RSLinx Classic as a service. For the KFD Modem Dialer driver to properly configure and run, the hardware handshaking between the remote modem and the KFD must be disabled. In the RSLinx Classic help file, the Home selection on the Option button does not function properly.
Application Notes This release has the following application notes.
Application notes for RSLinx Classic 2.59.02 Viewing the EDS parameters for a CIP-enabled device 1. Select Start > Rockwell Software > RSLinx > Tools > EDS Hardware Installation Tool . Follow the instructions on the screen to install the EDS file for the CIP-enabled device whose properties you want to view. 2. Select DDE/OPC > Topic Configuration . The DDE/OPC Topic Configuration dialog box is displayed. 3. Click New New.. A new topic is added to the Topic list. 4. Enter a name name for the topic. 5. In RSWho, locate and click the CIP-enabled device whose EDS parameters you want to
6. Click the Data Collection tab. 1. Under Processor Type, Type, click Device with EDS Parameters. 2. If you are using an OPC client client for data acquisition, acquisition, under Polled Messages, Messages, enter 8640000. This allows the OPC client to better control the data update rate. If you are not using an OPC client for data acquisition, go to step 6-3. 3. Under Limit Message Packets, Packets, change the setting to 1. Tip: Initially, enter a value of 1. Later, you can return to this dialog box and slowly increment the value until you reach a point where you are no Tip: longer getting data. At that time, you can then slowly decrement the value until you are receiving data again. 7. Click Apply Apply,, and then click Done Done.. 8. Navigate to your client program (for example, RSView 32 or the OPC Test Client), and locate the topic name that you specifie d in step 4. 9. Click that topic; the Offline Offline branch is displayed. displayed. 10. Click Offline; Offline; all of the parameters for the CIP-enabled CIP-enabled device specified specified in step 5 are displayed.
Displaying large numbers of tags in OPC or the Data Monitor If you have a large number of tags in the controller and recognize that the network performance is low, all of your tags may not be displayed in OPC or the Data Monitor. To resolve this condition, perform the following steps: 1. Close RSLinx Classic. 2. Click Start > Run. Run . 3. In the Run command line, type: regedit . The Registry Editor appears. 4. In the Registry Key window, navigate to HKEY_Local_Machine\Software\Rockwell HKEY_Local_Machine\Software\Rockwell Software\RSLinx\Settings. 5. Under the Settings key, click click Edit > New > DWORD DWORD value, and then type the following DWORD name: ACDTimeout name: ACDTimeout . 6. Double-click the DWORD ACDTTimeOut ACDTTimeOut;; the Edit DWORD Value dialog box appears. 7. In the Value Data field, enter a time out value (in seconds) larger larger than the default time out value (21 seconds). Tip: Rockwell Tip: Rockwell Automation suggests a time out value of 180 seconds. This value can then be adjusted based on the number of tags in your controller program. 8. Click OK OK.. 9. Exit the Registry Editor. 10. Run RSLinx Classic again to confirm that the new time out value is sufficient for the number of tags in your controller program .
Configure the 1784-PKTX(D) driver for RSLinx Enterprise and RSLinx Classic (Vista, Windows 2008, Windows 7) When you are running RSLinx Enterprise and RSLinx Classic on the same computer (running Vista, Windows 2008, or Windows 7), and your RSLinx Enterprise or RSLinx Classic configuration consists of a dual-channel 1784-PKTX(D) driver, you configure the driver for both RSLinx Enterprise and RSLinx Classic. Use the following procedure to configure the 1784-PKTX(D) driver for RSLinx Enterprise and RSLinx Classic: 1. If you do not already have a 1784-PKTX(D) driver in RSLinx Enterprise, then right-click RSLinx Enterprise, click Add Driver , and select a 1784PKTX(D) driver from the list. The DH+ Driver Properties or DH485 Driver Properties Properties dialog box displays. 2. Verify the information in the dialog box fields is correct, and click OK OK.. 3. Start RSLinx Classic, and click Communications > Configure Drivers. Drivers . The Configure Drivers dialog box displays. 4. From the Available Driver Types Types list, click the 1784-PKTX(D) driver , and then click Add New. New. 5. In the Add New RSLinx Classic Driver dialog box, enter a driver name or use the default name. Click OK OK.. The Configure 1784-PKTX/PKTXD dialog box displays. 6. Select the driver driver type from from the Value Value list, and click OK OK..
Running RSLinx Enterprise and RSLinx Classic on the same computer RSLinx Enterprise and RSLinx Classic can run simultaneously on the same computer. This is a common setup if you need to create or edit a program using RSLogix 5, RSLogix 500, and RSLogix 5000 software (which require RSLinx Classic) for use in an application and you must accomplish this using only one computer. Vista, Windows 2008, and Windows 7 operating systems If your RSLinx Enterprise configuration consists of a: Dual-channel 1784-PKTX(D) driver As o f CPR 9 SR 2, RSLinx Enterprise and RSLinx Classic bo th install and use the same 1784-PKTX(D) driver. RSLinx Enterprise uses the first channel (assigned by default and cannot be changed). RSLinx Classic uses the second channel. If you are running on Vista, Windows 2008, or Windows 7 and your RSLinx Enterprise or RSLinx Classic configuration consists of a dual-channel 1784PKTX(D) driver, you configure the driver for both RSLinx Enterprise and RSLinx Classic. NOTE: This NOTE: This applies only to the dual-channel 1784-PKTX(D) driver; the single-channel 1784-PKTX driver can be configured in only one RSLinx product at a time. All operating systems If your RSLinx Enterprise configuration consists of a:
1784-PKTX driver If your RSLinx Enterprise configuration consists of a 1784-PKTX driver, and you need RSLinx Classic to communicate using that same driver, then you must share the driver within RSLinx Enterprise with RSLinx Classic. TIP: You can use this procedure for Vista, Windows 7, and Windows XP operating systems; however, the previous procedure is the preferred method. TIP: Serial-DF1 driver (RS232 DF1 devices) If your RSLinx Enterprise configuration consists of a Serial-DF1 driver (RS232 DF1 devices), and you need RSLinx Classic to communicate using that same driver, then you must share the driver within RSLinx Enterprise with RSLinx Classic. 1784-PCIC(S) driver If your RSLinx Enterprise configuration consists of a 1784-PCIC(S) driver, you configure the driver in RSLinx Enterprise, then add a virtual backplane to RSLinx Classic. The virtual backplane is a sharable component between RSLinx Classic and RSLinx Enterprise. Since the 1784-PCIC(S) plugs into the virtual backplane, it is sharable as well.
Sharing an RSLinx Enterprise driver with RSLinx Classic The Serial-DF1 (RS232 DF1 devices) and 1784-PKTX drivers are configured in RSLinx Enterprise. Therefore, if you already have one of these drivers configured in RSLinx Classic, you must delete it from RSLinx Classic before performing the procedure below. To share one of these RSLinx Enterprise drivers with RSLinx Classic, use the following procedure: Note: This procedure describes the steps used to share a Serial-DF1 driver. However, it is also valid for sharing a 1784-PKTX driver. Note: 1. Start either FactoryTalk View Studio or the FactoryTalk Administration Console and click the Communications tab. 2. On the communications tree, right-click right-click the Ethernet Ethernet driver (EtherNet, (EtherNet, EtherNet), EtherNet), and then click Properties Properties.. The Ethernet Properties dialog box displays. 3. Click the Advanced Advanced tab, tab, and then select Listen on Ethernet/IP Encapsulation Port using the check box. Click OK OK.. 4. If you do not already have a Serial-DF1 driver in RSLinx Enterprise, then right-click RSLinx Enterprise and click Add Driver , and select the Serial DF1 driver from the list. The Serial-DF1 Driver Properties dialog box displays. 5. On the General tab, select Use Auto-configuration. Auto-configuration . Click OK OK.. Note: When you add a 1784-PKTX driver, the DH+ Driver Properties or DH485 Driver Properties dialog box displays. Verify the information in the Note: dialog box fields is correct, and click OK. 6. Start RSLinx Classic, and click Communications > Configure Drivers. Drivers . The Configure Drivers dialog displays. 7. From the Available Driver Types list, Types list, click Remote Devices via Linx Gateway, Gateway , and then click Add New. New. 8. In the Add New RSLinx Classic Driver dialog box, enter a driver name or use the default name. Click OK OK.. The Configure Remote Devices via Linx Gateway dialog displays. 9. Click Browse Browse to refresh the list of drivers. From the Server Name list, select your computer name to display a list of drivers to which you can connect. 10. From the Remote driver name list, click the Serial DF1 driver, and click OK OK.. Note: When Note: When using RSLogix, select the remote driver (e.g., TCP-1) instead of the direct serial DF1 (e.g., AB_DF1-1). 11. Click Close Close to to close the Add New RSLinx Classic Driver dialog box. You now have connectivity for both RSLinx Enterprise and RSLinx Classic clients; the RSLinx Enterprise driver appears in RSLinx Classic. If, after completing this procedure, your local workstation is not displayed, restart the host computer.
Sharing the RSLinx Enterprise virtual backplane with RSLinx Classic The virtual backplane is a sharable component between RSLinx Classic and RSLinx Enterprise. To share the RSLinx Enterprise virtual backplane with RSLinx Classic, use the following procedure: 1. Start either FactoryTalk View Studio or FactoryTalk Administration Console, and click the Communications tab. 2. On the communications tree, tree, right-click right-click the virtual backplane (1789-A17, (1789-A17, Backplane), Backplane), and then click Properties Properties.. The Virtual Backplane Properties dialog box displays. 3. Select Auto Configure and Configure and then click OK OK.. 4. Right-click RSLinx Enterprise and click Add Driver , and select the ControlNet driver (1784-PCIC(S)) from the list. The ControlNet Properties dialog box displays. 5. On the General tab, verify the information information in the dialog box fields is correct, correct, and click OK OK.. 6. Start RSLinx Classic, and click Communications > Configure Drivers. Drivers . The Configure Drivers dialog box displays. 7. From the Available Driver Types, Types, click Virtual Backplane (SoftLogix58xx), (SoftLogix58xx) , and then click Add New. New. 8. In the Add New RSLinx Classic Driver dialog box, enter a driver name or use the default name. Click OK OK.. 9. Click Close Close to close the Configure Drivers dialog box. You now have connectivity for both RSLinx Enterprise and RSLinx Classic clients; the RSLinx Enterprise virtual backplane (1789-A17, Backplane) appears in RSLinx Classic. If, after completing this procedure, your local workstation is not displayed, restart the host computer.
Configure an OPC client to obtain data from a processor using an alias topic To configure an OPC client to obtain data from a processor using an alias topic, perform the following steps: 1. Using one of the real topics associated with the alias topic, browse the target processor to collect names of the OPC Items. 2. Once collected, add the OPC Items to be used in the OPC client. 3. From the OPC client, client, export the tag database to a text file.
4. Open the text file, and replace the topic name with the alias topic name. 5. Save the text file, and import import it into the OPC client tag database. Routing through bridge devices Keep the following in mind when communicating using bridge devices: RSLinx Classic cannot communicate through an external bridge device when using the 1756-DHRIO bridge device with the TCP or CNET driver. The problem exists when the first bridge is a 1756-DHRIO device and the second bridge is not a 1756-DHRIO device (for example, Pyramid Integrator). In this case, the source link ID remains at zero and the response packets fail. The following limitations currently exist: Offlink routing works through one bridge. Offlink routing works through two or more bridges if the first bridge is a 1756-DHRIO module. Offlink routing does not work through two or more bridges if the first bridge is something other than 1756-DHRIO device. You cannot go from a DHRIO module through a 1785-KA bridge device to a DH network. To go from a DHRIO module through a 1785-KA5 bridge device to a DH485 network, the DHRIO module must be configured using the ControlLogix Gateway Configuration tool. For example, if a 1785-KA5 bridge is on a DH+ network at node 4 and the DH485 LinkID is 13, complete the following: 1. Select File > Browse Network. Network . 2. Select the DHRIO module. 3. Go to the routing routing table configuration configuration tab. 4. Right-cli Right-click ck the channel being used and select select Add Module. Module. 5. Select the DH+ Bridge. Bridge . 6. Enter the DH+ node number of the KA5 (4 in this example), and the LinkID of the DH485 (13 in this example). 7. Click Apply Apply.. You can now browse through the KA5 module. Other Application Notes 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 64055 64055.. 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. 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. You must have Windows NT Administrative privileges to install RSLinx Classic and/or configure RSLinx Classic drivers. When receiving unsolicited messages from an SLC 500 processor via a 1785-KA5 Bridge, the DDE topic's remote configuration must be set to Internet mode. Also, in the SLC 500 message instruction, the remote bridge node address must be set to 0. Also, unsolicited messages sent from a PLC or other node to RSLinx Classic will cause errors if no DDE clients or C-API applications are running to receive them. When downloading a program to an SLC 500, stop all data connections active to that station. Under certain instances, the processor may fault if applications continue to poll the SLC during a download. RSLinx Classic will not reread a User Defined Structure list for SoftLogix until the topic is stopped and restarted. RSLinx Classic supports no-interrupt configurations when using Allen-Bradley network cards; however, we recommend assigning an interrupt to increase driver performance. If you have AutoHide on for the task bar, every time you go to the task bar (if animation is on), it reduces your packets/sec speed due to computation times. Do not use the power saver option on your computer when running RSLinx Classic. Use either the BIOS or Control Panel to disable this option.
Windows and RSLinx Classic 2.59.02 issues Windows XP Professional and Windows 2003 You may experience difficulty configuring the 1784-KTC(X) or the 1784-KTX(D) in Windows XP because of how these legacy ISA cards obtain
resources. We recommend using the PCI based cards when using Windows XP. For ControlNet, use the 1784-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. Plug-n-Play drivers for the 1747-UIC, 1784-PCC, 1784-PCD, and SmartGuardUSB-KernelDrivers are located on the RSLinx Classic CD in the PnP_Drivers directory. PnP_Drivers You must have administrative privileges to configure drivers and topics. You must have administrative privileges to use the RS-232 DF1 driver. This driver only displays in RSWho and in the configured drivers list if you have administrative privileges. 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. Windows XP cannot go into stand-by mode if RSLinx Classic has a 1784-PCC or a 1784-PCMK driver running.
onsiderations when using RSLinx Classic 2.59.02 with Windows Vista, Windows 7, or Server 2008 Keep the following in mind when using RSLinx Classic v2.59.02 (CPR 9 Service Release 5) 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 interfac e (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 AR ARE E supported and are available on the Configure Drivers dialog: 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 Linx Gateway The following communication drivers ARE NOT 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 A utomation 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. User Account Control (UAC) 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, User Account Control 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 User Account Control enabled, you are prompted to confirm your 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.
Data Execution Prevention (DEP) settings for RSLinx Classic 2.59.02 Data Execution Prevention Prevention (DEP) is a security feature that is supported by both hardware and software. 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 those settings are supported by Rockwell Software
Note: Rockwell Software recommends that you use the OptIn DEP settings unless you have a specific reason to change them. Note:
DEP Setting
Description
Supported by Rockwell Software Products?
Alway Al waysOn sOn
Full DEP protecti protection on for the entire system system (all applicatio applications ns and components, no exceptions).
No
OptIn
DEP-enabled only for Windows system components and for applications that explicitly “opt in”. This is the default setting for Microsoft Windows XP (Service Pack 2).
Yes
OptOu Outt
DEPDE P-en enab able led d fo forr al alll pr proc oces esse ses s ex exce cept pt th thos ose e th that at ex expl plic icit itly ly “o “opt pt out ut”. ”. This Yes 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 Yes components, no exceptions)
Always Alw aysOff Off
Note: Rockwell Software does not recommend using this setting, since it will make your system more vulnerable to malicious code. 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 setting corresponds to OptOut setting. Tip: Keep the following in mind: Tip: 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. Hardware DEP Settings Hardware DEP uses the processor to mark memory so that code cannot be executed from data regions. When code attempts to execute 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 terminated. Hardware DEP is also enabled as the factory default setting. This feature is turned on or off in the computer BIOS settings. To determine if your hardware supports DEP, refer to the hardware manual or contact your hardware manufacturer. For additional information, see the Microsoft Knowledge base article at: http://support.microsoft.com/kb/875352.
Silent installation for RSLinx Classic 2.59.02 RSLinx Classic v2.59.02 (CPR 9 SR 5) 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
/quiet : quiet, no user interaction
or
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 is not installed, you must install FactoryTalk Services Platform first. If FactoryTalk Services Platform CPR 9, CPR 9 SR 1, or CPR 9 SR 2 is installed, you can optionally update FactoryTalk Services Platform first before you install RSLinx Classic v2.59.02 (CPR 9 SR 5). If RSLinx Classic 2.59.01 (CPR 9 SR 5) is installed using "silent mode", you must manually install the Redundancy Module Config Tool after you complete the RSLinx Classic v2.59.02 installation. To manually install the Redundancy Module Config Tool, run the RMCT Setup program from the RSLinx Classic v2.59.02 (CPR 9 SR 5) installation: \Redist\RSLinx\ENU\Redist\RMCT\DISK1\Setup.exe. If RSLinx Classic 2.59.01 (CPR 9 SR 5) is installed using "silent mode" on 64 bit operating systems, you must manually install x64 driver package after you complete the RSLinx Classic v2.59.02 installation. To manually install x64 driver package, run it from RSlinx Classic 2.59.01 (CPR 9 SR 5) installation: \Redist\RSLinx\ENU\R \Redist\RSLinx\ENU\Redist\KN64Bit\DriverPkgx edist\KN64Bit\DriverPkgx64.msi. 64.msi. If RSLinx Classic 2.59.01 (CPR 9 SR 5) is installed using "silent mode" on 32 bit operating systems, you must manually install USBCIP package after you complete the RSLinx Classic v2.59.02 installation. To manually install USBCIP package, run it from RSlinx Classic 2.59.01 (CPR 9 SR 5) installation: \Redist\RSLinx \Redist\RSLinx\ENU\Redist\U \ENU\Redist\USBCIP\Setup.Exe SBCIP\Setup.Exe If RSLinx Classic 2.59.01 (CPR 9 SR 5) is installed using "silent mode", you must manually install Windows Firewall Configuration Utility after you complete the RSLinx Classic v2.59.02 installation. To manually install Windows Firewall Configuration Utility, run it from RSlinx Classic 2.59.01 (CPR 9 SR 5) installation: \Redist\RSLinx\ENU\Windows Firewall Configuration Utility 1.00.06.msi.
During the RSLinx Classic silent installation, you may see one or two Windows Security dialogs: If the dialog states, "Windows can't verify the publisher of this driver software", please click Install this driver software anyway to anyway to continue the installation. If the dialog asks, "Would you like to install this device software?", please select the Always trust software from Rockwell Automation check box and then click Install Install.. Selecting the check box prevents this dialog from appearing again.
Upgrade instructions for RSLinx Classic 2.59.02 Perform the following steps to upgrade to RSLinx Classic v2.59.02 (CPR 9 Service Release 5): 1. Close your current version of RSLinx Classic. 2. Insert the RSLinx Classic v2.59.02 (CPR 9 Service Release 5) product CD. Perform the installation steps as presen ted on the screen. Tip: The old version of RSLinx Classic that exists on your computer is automatically uninstalled when you install RSLinx Classic v2.59.02 (CPR 9 Tip: Service Release 5). 3. Reboot your computer. computer.
Upgrading the FactoryTalk Services Platform software for RSLinx Classic 2.59.02 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 2.50.00 (CPR 9 Service Release 5), you may also need to upgrade the computer hosting the FactoryTalk Network Directory Server to FactoryTalk Services Platform version 2.50.00. In this release, several products added new Security Policies that will 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 An swer ID 54605 54605.. When upgrading FactoryTalk platform software: When you upgrade to FactoryTalk Services Platform 2.10 (CPR 9) or later 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 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 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 creates it and configures it 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 to the directory. This step allows any user account with Windows Administrator privileges to be able to immediately log on to the directory, without first having to create a FactoryTalk Administrator account. if necessary, updates each FactoryTalk Directory Directory with new product policies, system policies, and support for new features. leaves all original security settings, settings, user accounts and groups, and policy settings unchanged. When upgrading 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 first,, then upgrade the server computer hosting the FactoryTalk Directory Server, and finally, upgrade any remaining run-time server computers last last.. When upgrading client computers from FactoryTalk Automation Platform version 2.00 (CPR 7) , you must must upgrade upgrade client computers first first,, and then upgrade the FactoryTalk Directory server computer last 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 2.10 (CPR 9) or later, 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 2.10 (CPR 9) 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. To upgrade client computers: 1. Before upgrading to FactoryTalk Services Platform, shut down all Rockwell Automation software products running on the compute r. 2. Some Rockwell Automation software produ cts run as services in the background. Before upgrad ing to FactoryTalk Services Platform, you might need to uninstall those products. For details, see the documentation for your product. To upgrade server computers: 1. Before upgrading Facto ryTalk Services Platform, all related services running on the comput er 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 disconnect the computer from the network. This prevents client 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 must disconnect disconnect the computer from the network before performing the upgrade. 3. Some Rockwell Automation software produ cts run as services in the background. Before upgrad ing to FactoryTalk Services Platform, you might need to uninstall those products. For details, see the documentation for your product. 4. When the upgrade is complete, reconnect reconnect the server computer computer to the network. After upgrading the FactoryTalk platform software , you might need to install updates for the products you are using. To identify the installed version of the FactoryTalk platform software: 1. On the Windows Start Start menu, click Control Panel. Panel. 2. Double-click Add or Remove Programs. Programs . 3. In the list of installed programs, either FactoryTalk Automation Platform or FactoryTalk Services Platform appears, Platform appears, with the version number shown beside it.
Copyright © 2017 Rockwell Automation, Inc. All rights reserved. Rockwell Automation, Allen-Bradley, and Rockwell Software are trademarks of Rockwell Automation, Inc. To view a complete list of Rockwell Automation trademarks please click here. Trademarks not belonging to Rockwell Automation are property of their respective companies.
