

This updates the shortcut to reference the proper Driver/device. Once you have selected the proper controller, click ‘Apply’ at the bottom of the screen. Then using the Data Source tree on the right hand side, navigate to the correct driver and controller. To re-link a ‘shortcut’, click on the shortcut.If the driver tree did not expand the shortcut needs to be re-linked. The driver tree on the right should expose the PLC or controller that shortcut is linked to. In the left panel, click on a device/shortcut. On the right you will see the drivers configured in RSLinx and any devices that are communicating via those drivers. In the dialogue that opens you will a list on the left, these are the OPC ‘shortcuts’ or OPC ‘devices’.Click on the DDE/OPC Menu in the toolbar and select Configure OPC Topic Configuration.If that fails, you might have to restart. If it does not open RSLinx might still be configured to Always Run As a Service, repeat step 2. This allows you to open the RSLinx Classic app and change settings. Open the RSLinx Launch Control Panel from the start menu.This is a screenshot of ClearSCADA, showing where you might disable the OPC channel connected to RSLinx.

RSLinx attempts to run automatically when clients attempt to connect. This assumes RSLinx is configured to run as a service already. If you come across a SCADA server that is using RSLinx and it is no longer working here are a few troubleshooting steps you can try to get it working again. RSLinx can have only one instance running at a time. NOTE: When you do this you will no longer be able to open the RSLinx Classic project editor. Rockwell provides a handy control panel for this.

It allows users to connect to Allen Bradley PLCs and PACs as well as Panelview Plus HMIs and other equipment that speaks Ethernet IP, DF1 or DH+ (and their variants). Rockwell Software’s RSLinx is the communication hub for their RSLogix and FactoryTalk programming suites.
