The following are the system requirements for RSLinx Classic version 3.81.00.

To install RSLinx Classic, you need the following hardware:

• Minimum: Intel Pentium III, 600MHz, with at least 512MB (Megabytes) of RAM.
• Recommended: Intel Pentium 4, 2GHz or faster, 1GB or more RAM.
• This version of RSLinx Classic does not run on Alpha, MIPS, or Power computer processors.
• At least 2.2 GB 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.

To run RSLinx Classic v3.80.00 (CPR 9 SR 8), one of the following operating systems is required:

Supported operating systems

• Windows 8.x
• Windows 7 Professional, Windows 7 Professional SP1, Windows 7 Home Premium SP1, Windows 7 Enterprise SP1, Windows 7 Ultimate SP1 (64-bit), and Windows Embedded Standard 7 SP1
• Windows Vista SP2 (32-bit)
• Windows Server 2012 Standard (64-bit), Windows Server 2012 Datacenter (64-bit), Windows Server 2012 R2 Standard (64-bit), and Windows Server 2012 R2 Datacenter (64-bit)
• Windows Server 2008 SP2 Standard, Windows Server 2008 R2 Standard (64-bit), Windows Server 2008 R2 SP1 Standard (64-bit), and Windows Server 2008 R2 SP1 Enterprise (64-bit)

For the latest information regarding software platform support, refer to the Rockwell Automation Product Compatibility and Download Center .

RSLinx Classic runs on the Microsoft Windows operating systems with limitations. See Considerations when using RSLinx Classic with Microsoft Windows operating systems.

RSLinx Classic v2.57.00 and later requires installation of a compatible version of FactoryTalk Services Platform software. When you install or upgrade RSLinx Classic, make sure you also install or upgrade a compatible version of FactoryTalk Services Platform.

The installation of RSLinx Classic includes Microsoft .NET Framework 3.5 Service Pack 1. During the RSLinx Classic installation, you are prompted to automatically install this component if it is not already present.

For information on the security considerations when using Rockwell Automation products, including:

• File extensions created by Rockwell Automation software, firewall rules, and service dependences, see Rockwell Automation Knowledgebase Answer ID 609492.
• TCP/UDP ports used by Rockwell Automation products, see Rockwell Automation Knowledgebase Answer ID 29402.

The following features have been added in RSLinx Classic v3.81.00.

• Studio 5000 Logix Designer™ v28.00.00 support - This release of RSLinx Classic supports Studio 5000 Logix Designer™ application version 28.00.00 or earlier.

• EDS file registration enhancement - This release of RSLinx Classic improves the EDS file uploading and registration processes in the RSWho within RSLinx Classic. With this function enabled, for an online device whose EDS file is not yet registered, RSLinx Classic v3.80.00 (CPR 9 SR 8) detects the EDS file within the device's firmware upon network browsing. If there is an EDS file found, RSLinx Classic can automatically upload the EDS file from the device and register it. Once registered, the device information shows in RSLinx Classic, and communications to other information within the device are possible. Fixed anomalies - A number of anomalies were fixed in RSLinx Classic v3.80.00 (CPR 9 SR 8).

• In this release, support for the following Microsoft Windows operating systems has been removed:
  • Windows Server 2003 R2 SP2
  • Windows XP SP3 (32-bit)
  • Windows XP Embedded

• In this release, support for the following drivers has been removed:
  • 1784-PCC for ControlNet devices
  • DeviceNet Drivers (1784-PCD/PCIDS)
  • PLC-5 (DH+) Emulator

• 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.

Anomaly Identified as of RSLinx Classic version 3.60.00

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.

Anomaly Identified as of RSLinx Classic version 3.60.00

• RSLinx Classic v2.53.00 (CPR 9) and later supports the 1747-PIC/AIC driver on Windows XP, XP SP1, or XP SP2 only.
• 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.

Anomaly Identified as of RSLinx Classic version 3.60.00

EtherNet/IP driver cannot recognize PLC5 and SLC devices when using Remote subnet.

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.

Anomaly Identified as of RSLinx Classic version 3.60.00

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 work around 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.

Anomaly Identified as of RSLinx Classic version 3.60.00

For the KFD Modem Dialer driver to properly configure and run, the hardware handshaking between the remote modem and the KFD must be disabled.

Anomaly Identified as of RSLinx Classic version 3.60.00

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.

Anomaly Identified as of RSLinx Classic version 3.60.00

Install, upgrade, and downgrade issues with RSLinx Classic v2.57.00 (CPR 9 SR 3) and the Redundancy Module Config Tool (RMCT):

• The RSLinx Classic 2.57.00 (CPR 9 SR 3) Installer also installs RMCT v6.2.10.0. If RMCT v6.2.10.0 is already installed manually with a prior version of RSLinx (before v2.57.00), it may not function or start after upgrading to RSLinx Classic v2.57.00 (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, and click Next to continue. When you restart RSLinx Classic v2.57.00 (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.00, you may see error messages about .dll files failing to unregister. Click OK in the message, and the removal process completes 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.00 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.00 (CPR 9 SR 3). Otherwise, you see an error message and the newer version of the RMCT remains installed after installing RSLinx Classic v2.55.00.

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]

Anomaly Identified as of RSLinx Classic version 3.60.00

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 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 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 896054.

Anomaly Identified as of RSLinx Classic version 3.60.00

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.

Anomaly Identified as of RSLinx Classic version 3.60.00

• Block reads and writes do not work with user defined types (Logix5000 controller).
• RSLinx Classic does not reread a User Defined Structure list for SoftLogix until the topic is stopped and restarted.

Anomaly Identified as of RSLinx Classic version 3.60.00

RSLinx Gateway

RSLinx Classic does not browse Remote Devices via Linx Gateway or SoftLogix drivers configured on a Linx Gateway from a client browsing the gateway.

RSWho Browse

When using RSWho to select a processor for RSLogix5, RSLogix500, or RSLogix Frameworks, you cannot go online to that processor if you select 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.

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). 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]

• RSLinx Classic may exit if click Cancel button when adding a SLC 500 (DH485) Emulator driver.
When adding a SLC 500 (DH485) Emulator driver in RSLinx Classic, if you click Cancel on the Configure SLC 500 (DH485) Emulator Driver dialog box, RSLinx Classic may exit unexpectedly on Windows 7 operating systems. First identified in RSLinx Classic version 2.57.00. [269134]

There is currently no work around for this anomaly.

• RSWho may fail to upload and register all the EDS files from unregistered devices, if there are too many EDS files (for example, 400 files) or multiple RSWho instances (for example, 5 instances). First identified in RSLinx Classic version 3.80.00. [357152]
To work around this problem, upload and register several EDS files (for example, 10 files) with a single RSWho instance each time, or manually upload and register the EDS files using the EDS Hardware Installation Tool.

• If an EDS file is removed using the EDS Hardware Installation Tool while RSLinx Classic is running, the EDS file cannot be uploaded and registered in the RSWho, neither automatically nor manually. First identified in RSLinx Classic version 3.80.00. [357375]
To solve this problem, restart RSLinx Classic to upload and register the EDS file (either automatically or manually).

• FactoryTalk View Studio startup performance tends to degrade over time when there are a large number of devices on the network. First identified in RSLinx Classic version 2.56.00. [218691]
To solve this problem, compact existing harmony topologies through RSLinx Classic:

• In RSLinx Classic menu bar, click File > Compact Harmony, or
• In RSLinx Classic Launch Control Panel, click Tools > Compact Harmony.

Consider the following application notes when using RSLinx Classic v3.81.00:

• 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)
• Run RSLinx Enterprise and RSLinx Classic on the same computer
• Share an RSLinx Enterprise driver with 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 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. 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 uninstall 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 causes 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 does 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.
• RSLinx Classic does not support an entire UDT (User Defined Type) tag as a destination element for unsolicited message. You can only configure a member of the UDT tag as a destination element in a message instruction in the ControlLogix processor.