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

RSLinx Classic 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 Datacenter
• Windows Server 2012 Standard Edition
• Windows Server 2012 R2 Datacenter
• Windows Server 2012 R2 Standard Edition

*See Operating systems section of Anomalies for a note regarding Windows 10 support.

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

Software compatibility

RSLinx Classic version 3.90.00 (CPR 9 SR 9) is a component aligned to Studio 5000 Logix Designer® version 30.00.00. RSLinx Classic version 3.90.00 has been tested, and is compatible, with the following products:

• Studio 5000 Logix Designer version 30.00.00 or earlier
• FactoryTalk View version 9.00.00
• FactoryTalk Services Platform version 2.90.00
• FactoryTalk® Activation Manager version 4.00.02

RSLinx Classic version 3.90.00, Studio 5000 Logix Designer version 30.00.00, and device profiles that ship with Studio 5000 Logix Designer version 30.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 installing these products.

RSLinx Classic version 3.90.01 has the following system features and enhanced features:

System features

Compact harmony

This release allows you to compact existing harmony typologies through the RSLinx Classic user interface. With this enhancement, you no longer need to locate and delete harmony files manually from your computer's hard drive. This reduces the waiting time to open RSLinx Classic, or to expand the driver nodes in the RSWho. For more information, see Compact harmony files in RSLinx Classic in the RSLinx Classic Online Help.

Enhanced features

Enhanced installation wizard

The installation setup wizard's user interfaces and installation process are updated to align with other Rockwell Automation software products to improve usability and convenience. For more details, see RSLinx Classic Getting Results Guide.

New operating system support

• Windows 10 Professional
• Windows 10 Enterprise
• Windows 10 IoT Enterprise 2016 Long Term Servicing Branch (LTSB) Embedded

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

• After you set up an OPC topic in RSLinx Classic and connect to an OPC client, the values in the Item Properties dialog box are incorrect. First identified in RSLinx Classic version 3.80.00. [361748]
  In this release, after the same operations on RSLinx Classic, the values in the Item Properties dialog box shows correctly.
  

• For a controller that supports Ethernet/IP mode switching (for example, 5069-L320ER and 5069-L310ER), after you switch the controller’s IP mode from A1/A2: Dual-IP to A1/A2: Linear/DLR, the two Ethernet networks are merged without an warning message. First identified in RSLinx Classic version 3.81.00. [361760]
  In this release, a warning message is added to indicate the networks merging.
  

• When changing the IP address on a module, if the IP changes fail to be saved and the TCP/IP connection is reset (RST), RSLinx Classic does not show an error messages upon this IP change failure. First identified in RSLinx Classic version 3.74.00. [356344]
  In this release, an error message is added to indicate the IP change failure.
  

• After connecting an Allen-Bradley 1790D-0B16 device to a Micro800 DeviceNet Plug-in Module, the Allen-Bradley 1790D-0B16 device shows as an unknown device with a yellow question mark under the Micro800 DeviceNet Plug-in Module in RSLinx Classic. First identified in RSLinx Classic version 3.72.00. [352867]
  In this release, the Allen-Bradley 1790D-0B16 device shows correctly with no question mark.
  

• When using RSLinx Classic version 3.81.00 with Connected Components Workbench, you may randomly experience connection failures to Micro820 devices, or backplane missing upon browsing. First identified in RSLinx Classic version 3.81.00. [363386]
  In this release, RSLinx Classic runs normally with Connected Components Workbench upon the same operation.
  

• RSLinx Classic stops responding on startup with a fully qualified domain name (FQDN) of more than 32 characters. First identified in RSLinx Classic version 3.80.00. [362172]
  In this release, RSLinx Classic runs normally with a fully qualified domain name (FQDN) of more than 32 characters.

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

1770-KFC device

• RSLinx Classic version 2.42.00 or later fails to browse remote ControlLogix controllers under 1770-KFC15 DF1 passthrough. First identified in RSLinx Classic version 2.42.00. [354274]
  There is currently no work around for this anomaly. To communicate with a 1770-KFC15 module via DF1 protocol, use RSLinx Classic version 2.41.00 or earlier.

DH+ and DH485

• If you attempt to go online with a controller through a 1784-PKTX card to a remote DH-485 to DH+ network, RSLogix 5 may stop responding. First identified in RSLinx Classic version 2.55.00. [263358]
  There is currently no work around for this anomaly.

EtherNet and EtherNet/IP

• Devices on previous subnet are not removed after configuration changes. 
If an EtherNet/IP driver's configuration is changed to a new remote Ethernet subnet, the devices browsed on previous Ethernet subnet were not removed. First identified in RSLinx Classic version 3.51.00. [273876]
There is currently no work around for this anomaly.

EDS file upload and registration

• RSWho cannot upload and register EDS files with path length more than 256 bytes.
For an online device whose path length exceeds 256 bytes, RSWho cannot upload and register the EDS file of the device, neither automatically nor manually. First identified in RSLinx Classic version 3.80.00. [357201]
To work around this problem, change the location where the computer is connected, so that the path length of the device is less than 256 bytes.

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 will be released in the December 2016 or January 2017 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.
• RSLinx Classic version 3.90.00 is not tested to run on Windows Embedded 8.1 Industry Professional operating system, while RSLinx Classic does not prevent installation on this operating systems. Additional changes may be required in order to function properly. First identified in RSLinx Classic version 3.90.00. [363223]
To avoid this problem, use another supported operating system that is listed in the System requirements topic.

RSLinx Gateway

• From a client, you cannot browse the Remote Devices via RSLinx Classic Gateway driver, which was configured on a RSLinx Classic Gateway server. First identified in RSLinx Classic version 2.31.00. [21836]
  
There is currently no work around for this anomaly.

Stratix

• RSLinx Classic may stop responding when viewing the module statistics of Stratix 5410 switches on the Port Diagnostics tab. First identified in RSLinx Classic version 3.74.00. [355521]
  
There is currently no work around for this anomaly.

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 version 3.90.01 has the following changes in functionality since the last release:

EDS file updates

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 .

x64 driver package

RSLinx Classic version 3.90.00 (CPR 9 SR 9) x64 driver package includes updates to the following drivers:

• 1747-UIC (DH485)
• 1752-SmartGuard USB
• 1784-PCIC(S) (ControlNet)
• 1784-PKTCS (ControlNet)
• 1784-PKTX (DH485 / DH+ / RIO)
• 1784-U2DHP (DH+)
• Micro800 Remote LCD (208-REMLCD / 820 Remote LCD)
• Micro810
• Virtual Backplane
• USB CIP

In addition, this release of x64 driver package includes a number of enhancements, including USB CIP driver improvements and new driver installation folder C:\Program Files\Rockwell Automation.

The following are the application notes for RSLinx Classic version 3.90.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.

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.

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

• RSLinx Classic 2.55 or later does not install the automation interface wrapper rsiopcauto.dll from the OPC Foundation.
  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.

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:
  
  • 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), 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.