RSLinx Classic version 4.00.01 works within the system requirements of all Rockwell Automation® software products.

For the latest compatibility and driver support information, refer to the Rockwell Automation Product Compatibility and Download Center.

Hardware requirements

RSLinx Classic requires the following hardware:

• Intel® Core 2 Duo, 2.8 Ghz processor; 2 GB of memory
• 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.

Software requirements

Operating systems

RSLinx Classic is tested on operating systems installed from original Microsoft® media only. RSLinx Classic runs on either the 32-bit or 64-bit versions of the following Windows® operating systems:

• Windows 7 Enterprise with Service Pack 1
• Windows Embedded Standard 7 with Service Pack 1
• Windows 7 Home Premium with Service Pack 1
• Windows 7 Ultimate with Service Pack 1
• Windows 7 Professional with Service Pack 1
• Windows 8
• Windows 8 Enterprise
• Windows 8 Professional
• Windows 8.1
• Windows 8.1 Enterprise
• Windows 8.1 Professional
• Windows 10 Enterprise*
• Windows 10 Professional*
• Windows 10 IoT Enterprise 2016 Long Term Servicing Branch (LTSB) Embedded**
• Windows Server® 2008 R2 Enterprise Edition with Service Pack 1
• Windows Server 2008 R2 Standard Edition with Service Pack 1
• Windows Server 2012 Standard
• Windows Server 2012 Datacenter
• Windows Server 2012 R2 Standard
• Windows Server 2012 R2 Datacenter
• Windows Server 2016 Standard*
• Windows Server 2016 Datacenter*

*See Operating systems section of Anomalies for notes regarding Windows 10 and Windows Server 2016 support.

**Supported with the Allen-Bradley 61xx family of Industrial Computers or CompactLogix™ 5480 family of controllers.

Software compatibility

RSLinx Classic version 4.00.01 (CPR 9 SR 10) has been tested, and is compatible, with the following products:

• Studio 5000 Logix Designer version 31.00.00 or earlier
• FactoryTalk View version 10.00.00
• FactoryTalk Services Platform version 3.00.00
• FactoryTalk® Activation Manager version 4.00.02

RSLinx Classic version 4.00.01, Studio 5000 Logix Designer version 31.00.00, and device profiles that ship with Studio 5000 Logix Designer version 31.00.00 are not compatible with RSNetWorx version 9.00.00 or earlier. RSNetWorx and the DeviceNet Tag Generator must be upgraded to a version later than 9.00.00 prior to install these products.

The following is the new feature for RSLinx Classic version 4.00.01.

Use Record and playback from the Install user interface to record inputs to a record file and to playback the record on other computers. Record and Playback provides an easier option to using parameters. Also use Record and Playback to customize the installation of components and features.

The following are the corrected anomalies for RSLinx Classic version 4.00.01.

• RSLinx Classic personalized version 3.90.00 cannot be activated with personalized license. First identified in RSLinx Classic version 3.90.00. [364751]
• When using DF1 polling master to dial out to multiple RADKIT modems and poll from each station, after the first successful station poll, RSLinx Classic shows a driver configuration dialog box for a 12 Point Micro810 which cannot be closed. It also disconnects the PLC. First identified in RSLinx Classic version 3.73.00. [364675]
• The ic32ckit.dll file blocks a batch server thread which handles client communication. First identified in RSLinx Classic version 3.90.00. [366336]
• RSLinx Classic may crash when browsing Offline devices. First identified in RSLinx Classic version 3.60.00. [364238]
• RSLinx Classic may crash when processing timer pointer. First identified in RSLinx Classic version 2.59.00. [364725][365088][365089]
• When exiting RSLinx Classic, a crash may happen while a thread is processing an incoming unsolicited message. First identified in RSLinx Classic version 3.60.00. [365040]
• RSLinx Classic may crash when establishing a privileged connection with the exception as invalid parameter. First identified in version 3.60.00. [364948]
• When exiting RSLinx Classic, a crash may happen while a resource being processed has been released. First identified in version 3.60.00. [365385] [365604] [367029]
• RSLinx Classic may crash when clicking the help button on the TCP driver configuration dialog box. First identified in RSLinx Classic version 2.55.00. [365994]
• RSLinx Classic may stop providing data after running 49.7 days. First identified in RSLinx Classic version 2.56.00. [364107]
• RSLinx Classic may crash when saving communications error file. First identified in RSLinx Classic version 2.59.00. [366643]
• RSLinx Classic may crash when selecting a node in Topic configuration. First identified in RSLinx Classic version 2.59.00. [366644]
• RSLinx Classic may crash when removing items from OPCGroup. First identified in RSLinx Classic version 2.59.00. [366645]
• RSLinx Classic may crash when an item that has been released is still requested by client. First identified in RSLinx Classic version 2.59.00. [367137]
• RSLinx Classic may crash when massive devices go offline simultaneously. First identified in RSLinx Classic version 3.60.00. [367090]
• RSLinx Classic may crash when deleting topic. First identified in RSLinx Classic version in RSLinx Classic 3.60.00. [366826]
• RSLinx Classic may not automatically start after restarting the computer. First identified in RSLinx Classic version 3.90.00 [81277]

The following are the known anomalies for RSLinx Classic version 4.00.01.

Operating systems

• When running RSLinx Classic on Windows 10 Professional or Enterprise v1607 operating systems, initiating a network connectivity break by disabling NIC adaptors in Device Manager can cause application failures requiring a restart of the application. This issue was introduced in the Windows 10 v1607 feature build. [363223]

To avoid this problem, run the Microsoft Hotfix outlined in Answer ID 964391 in the Rockwell Automation Knowledgebase. This hotfix was released on December 9, 2016 Windows Update pack. Alternatively, you can run Windows 10 v1511 where this issue is not present.

• Because of the timing of the RSLinx Classic version 3.90.00 release, RSLinx Classic is not fully qualified to run on Windows Server 2016 operating systems. While RSLinx Classic version 3.90.00 does not prevent installation on Windows Server 2016 operating systems, additional changes may be required in order to function properly. [363223]

For more information, refer to Rockwell Automation Knowledgebase Answer ID 964370.

• The PCICS, PKTCS, and PKTX drivers are lack of Microsoft signature to perform Windows 10 secure reboot. [367671], [367672], [367673]

For more information, refer to Rockwell Automation Knowledgebase Answer ID 1036955.

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

The following are the application notes for RSLinx Classic version 4.00.01.

Backup and restore

• When you run the Backup/Restore utility, the Restart RSLinx Classic when finished check box is not available on the Shutdown RSLinx Classic dialog box. 

DDE/OPC

• To receive unsolicited DDE messages from a processor through a DHRIO module, and through an ENET module over an Ethernet network:
1. Select your DDE topic from the DDE/OPC Topic Configuration dialog box.
2. Select Advanced Communication and click Remote.
3. 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 the 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 the 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).

DF1 driver

• The DF1 Polling Master Driver and DF1 Slave Driver do not support hardware handshaking control.

DH+ and DH485

• You cannot download data to a Standard PanelView 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 1770-KF2.
• Duplicate nodes are not detected when configuring a 1784-KT(D) card. When configuring a 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.
• When using auto configuration on a 1770-KF2 or1770-KF3 device, you must set the Station Number to that of the 1770-KF2 or1770-KF3 device 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 1770-KF2 or1770-KF3 device.
• If the 1784-PCMK driver is a duplicate node, all stations in the RSWho appear as a question mark with a red X.
• Since both channels of a PKTXD card share the same interrupt, you cannot configure one channel for SoftLogix 5 and the other for RSLinx Classic. You can configure RSLinx Classic and SoftLogix 5 to use separate PKTX(D) cards.
• If you plug in your DH-485 UIC device on a computer running a Windows or Windows Server operating system, and the computer has already installed the 1752-L24BBB SmartGuard controller, the DH-485 UIC device will not be recognized by the Plug and Play feature. To solve the problem, follow these steps:
1. Press Windows and R on your keyboard to open the Run dialog box.
2. Type devmgmt.msc and click OK to open the Device Manager.
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 Properties.
5. On the Driver tab, click the Update driver 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.

Driver certificate

• Computers running Windows that are not connected to the internet may not verify some of the RSLinx Classic files. This is because the root certificate is not present on the local machine.
1. To correct this issue, the RSLinx Classic installation process adds a certificate verisign-univ.cer issued by VeriSign Universal Root Certification Authority to the Trusted Root Certification Authorities store for a local computer.
2. This certificate can be found in the Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates folder of the Windows Microsoft Management Console MMC.EXE tool’s certificates Snap-in option.

EtherNet and EtherNet/IP

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

FactoryTalk Activation Manager

• If you have disconnected one of the servers used for activation from the network, RSLinx Classic may stop responding for up to two minutes during startup, as it checks the remote server for an activation file.

To work around this, go to Find Available Activations in FactoryTalk Activation Manager, select Update Activation Search Path, and clear the check box of the disconnected server (or delete the path to the server).

Hardware considerations

• This version of RSLinx Classic does not run on Alpha, MIPS, or Power computer processors.
• 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.

Installation

• If you install RSLinx Classic on Windows 8.1 without Windows 8.1 Update (also known as KB2919355), an error message shows and the installation cannot be completed. To solve this problem, install the Windows 8.1 Update and retry the RSLinx Classic installation.
• When you uninstall RSLinx Classic, the DTL32.dll file remains in the system directory if it is locked by another application.
• RSLinx Classic version 4.00.00 may not function properly due to incomplete installation. To solve this problem, obtain Administrator permission to install RSLinx Classic version 4.00.00.

Module statistics

• For 1794-AENT and 1756-ENB modules, module statistics on the Port Diagnostics tab may show zeros even though the modules work properly.

No-interrupt configuration

• RSLinx Classic supports no-interrupt configurations when using Allen-Bradley network cards; however, it is recommended to assign an interrupt to increase driver performance.

OPC Foundation

• RSLinx Classic 2.55 or later does not install the automation interface wrapper rsiopcauto.dll from the OPC Foundation.

The OPC Foundation recommends using the updated automation interface wrapper, OpcDaAuto.dll, which is provided with RSLinx Classic instead of RsiOpcAuto.dll. For more detailed information, refer to Rockwell Knowledgebase Answer ID 64055.

Operating system

• RSLinx Classic is a 32-bit application. While it will function on 64-bit edition of Windows operating systems, the RSLinx Classic Single Node and OEM activations may not operate with a Windows 64-bit application running on the same computer. Windows 64-bit forces 32-bit and 64-bit applications to run in different processes which causes RSLinx Classic Single Node and OEM to see the 64-bit application as running remote and thus prevents it from using the OPC interface. In this case the system should upgrade to RSLinx Gateway to work with 64-bit applications.

Repair software

• If you click Change to repair FactoryTalk Services Platform from Control Panel when UAC is enabled, you may see the error 1722 message.

To work around this, click OK to close the error message, and retry to repair FactoryTalk Services Platform. [276317]

RSWho browse

• RSWho with the RSLinx Gateway cannot be used to go online with a processor in RSLogix 5 or RSLogix 500 software. To select a processor connected to a RSLinx Gateway, configure an RSLinx Classic driver, using the Remote Devices via RSLinx or 1756-ENET Gateway driver.

Running mode

• If RSLinx Classic is running as a service, there is no graphical user interface (GUI). If you need to configure RSLinx Classic, you must be in application mode. To switch between running as a service or application, use the RSLinx Classic Launch Control Panel.

Security considerations

• Information on the security considerations related to using Rockwell Automation products can be found in the Rockwell Automation Knowledgebase, 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 898270.

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 Studio 5000 Logix Designer, for controllers that support External Access attribute, you can change the External Access attribute for a tag while online with the controller.
• The following scenarios may require you to restart RSLinx Classic and data clients:
  • If a controller is replaced with a different controller, even if it has the same program. [265753]
  • If tag attributes for tags on scan are changed and a new program is downloaded to the controller.
  • If tag attributes for tags on scan are changed after an Alias Topic switch. [265756, 266168]

SLC

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

SmartGuard

• If you are installing a 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 are not able to configure the driver.
• Although you can communicate over the DeviceNet network through the USB port of a 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 to configure these devices.

SoftLogix

• RSLinx Classic does not reread a User Defined Structure list for SoftLogix™ until the topic is stopped and restarted.

Unsolicited message

• When receiving unsolicited messages from an SLC 500 processor via a 1785-KA5 bridge device, the DDE topic's remote configuration must be set to Internet mode. In addition, in the SLC 500 message instruction, the remote bridge node address must be set to 0.
• 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.

Unattended or silent install

• Use command-line parameters to perform an unattended or silent installation of the software.

Command-line parameters

• The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").

Parameter	Description
/?	Displays the usage options for installation parameters.
/Q	Silent Install, install runs in a quiet mode without any user interface. This parameter is recommended if you are deploying the software installation using an IT tool or script, and don’t expect to see any error or restart messages. When using this parameter, your IT tool or script should check the error codes, and respond as needed. For example, if the installation returns error code 1641, then the IT tool or script should restart the computer and relaunch the installation after restart. This parameter is required if /QS or /Record is not specified.
/QS	Unattended Install, install runs in a quiet simple mode and shows progress through the UI, it does not accept any input but still shows error or restart messages. When using this parameter, you will not have to check the error codes, and the installation will stop and display a prompt if there are error or restart messages. For example, if an immediate restart is required to complete the install, a restart message will be displayed for you to confirm the restart. Installation resumes automatically from the point of interruption after restart. This parameter is required if /Q or /Record is not specified.
/IAcceptAllLicenseTerms	Acknowledges acceptance of the license terms. This parameter is required for /Q or /QS parameters.
/AutoRestart	Automatically restarts the computer after the installation is complete. Used when a restart is required to complete the installation. This parameter is optional. If this parameter is not used silent install (/Q) will return either error code 1641 or 3010 if a restart is required, and unattended install (/QS) will result in a confirmation prompt that must be agreed to before the installation is completed.
/SetupLanguage="value"	Specifies which language will be displayed during install process. The value must be the one of the following: ENU CHS DEU ESP FRA ITA JPN KOR PTB This parameter is optional. If this parameter is not used, the default language is the current user or operating system user interface language.
/Record	Records the installation options chosen to a recording file. This parameter is optional.
/Playback	Plays back a recording file to specify the installation options. This parameter is optional.
/InstallLocation="value" Or /InstallDrive="value"	Specifies the install location or install drive respectively. This parameter is optional. If this parameter is not used, the default install location is "C:\Program Files (x86)\Rockwell Software". Some software restricts the installer to only change the drive the software is installed on. Use /? to determine which parameter is supported.
/Uninstall	Use to uninstall RSLinx Classic. This parameter is optional.
/SerialNumber="value"	Specifies the serial number of the software being installed. This is used to activate the software during installation. This parameter is optional. If it is not specified the software must be activated manually after installation if activation is required. Some software does not require activation. If activation is not required this parameter is not available.
/ProductKey="value"	Specifies the product key used to get activation keys during installation. This parameter is optional. If it is not specified the software must be activated manually after installation if activation is required. Some software does not require activation. If activation is not required this parameter is not available.
/Version="value"	Specifies the version of the software to activate which corresponds to the product version associated with the SerialNumber and ProductKey. This parameter is optional. If it is not specified the installer will use the most recent product version available. Some software does not require activation. If activation is not required this parameter is not available.

Error codes

• The following table identifies the error codes that can be returned by an installation.

Error Code	Value	Description
ERROR_SUCCESS	0	The installation completed successfully.
ERROR_INVALID_PARAMETER	87	One of the parameters was invalid.
ERROR_INSTALL_USEREXIT	1602	The installation was cancelled by the user.
ERROR_INSTALL_FAILURE	1603	A fatal error occurred during installation.
ERROR_BAD_CONFIGURATION	1610	The configuration data for this product is corrupt. Contact your support personnel.
ERROR_SUCCESS_REBOOT_INITIATED	1641	The installer has initiated a restart. After restart installation will continue.
ERROR_SUCCESS_REBOOT_REQUIRED	3010	A restart is required to complete the installation. After restart the product is successfully installed.

User account

• RSLinx Classic does not start properly when it is configured to run as an administrator, while you attempt to log on as a standard user.

User-defined type

• Block reads and writes do not work with user defined types (for Logix5000 controllers).
• 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.

User documentation

• Topics in .chm (Compiled Help Module) files do not show when the help file is opened from a remote computer or UNC (Universal Naming Convention) path.

To avoid this problem, use one of the following methods:
1. Open the help files from the installation DVD or copy them to a folder on your local computer.
2. If you want the help files to be accessible from a network directory (shared folder), use Registry Editor to modify certain registry entries. For more information, see Microsoft Knowledge Base article 896054.

• If you attempt to view the Support Services (support.hlp) or Activation (copyprot.hlp) information, an error message shows and the online help files are not displayed. To view the Support Services or Activation information, refer to the RSLinx Classic Getting Results Guide.