RSLinx Classic OPC settings

When an OPC client (such as OPC Expert or the FPAM Gateway) connects to an RSLinx Classic Gateway OPC server but the tags show as disconnected and DCOM errors appear in Event Viewer, the most common root cause is that the RSLinx Classic DDE/OPC topics are not pointing to any device. RSLinx Classic sees the PLCs fine in RSWho, but each topic must be explicitly mapped to a controller before the OPC server will serve live data.

1. Symptoms

• OPC client (e.g. OPC Expert) reports disconnected when browsing or reading tags, even though the server is reachable.
• DCOM errors logged in Windows Event Viewer that do not clear after applying standard DCOM fixes.
• RSLinx Classic and RSWho correctly see all devices and PLCs — the problem is downstream of driver connectivity.
• In DDE/OPC Communication Events, entries such as “when loading this topic, it was not possible to resolve the target path” or “invalid topic route — unable to establish communication to device on specified route.”

2. Root Cause

The RSLinx Classic DDE/OPC topics exist but are not bound to a controller. A topic with no device mapping cannot obtain a topic lock, so the OPC server has nothing to serve and the client sees the tags as offline. This is independent of the DCOM security patches — a general DCOM knowledge base article will not resolve it because the underlying topic configuration is the actual fault.

Note. RSLinx Classic only refreshes the topic lock icons in the background, not live in front of you. After editing a topic you must close and reopen the DDE/OPC Topic Configuration window to see the updated lock state. Do not assume a change failed just because the icon did not update immediately.

3. Fix — Map the Topic to Its Controller

1. In RSLinx Classic, open DDE/OPC → Topic Configuration. Confirm the affected topics have no lock icon next to them, which indicates they are not mapped.
2. Highlight the topic that needs to be mapped (for example, a topic named Line1_PLC).
3. Expand the correct driver in the tree on the right (for example, the AB_ETH Ethernet driver) and select the target device/controller the topic should point to.
4. Click Apply at the bottom. When prompted to update, choose Yes.
5. Click another topic in the list, then click back to the mapped topic to confirm the path was retained. The controller on the right should highlight when the topic is selected.
6. Close the DDE/OPC Topic Configuration window completely, then reopen it. The mapped topic should now display a lock icon, confirming a valid topic lock.
7. Repeat for any additional topics that need to be served.

4. Reconnect and Verify the OPC Client

1. In the OPC client (OPC Expert or the target application), reconnect to the RSLinx OPC server. If it was already open, close and reopen the connection so it re-reads the now-locked topics.
2. The previously disconnected tags should come online and display live values instead of disconnected.

5. Confirmation Test — Data Monitor

RSLinx Classic includes a built-in OPC client that is useful for verifying tags independently of the third-party client:

1. In the RSWho window, right-click the target device and select Data Monitor.
2. Data Monitor reads the tags directly from the controller. Use it to confirm a tag exists and is readable.
3. Compare tag names against your OPC client. If a tag does not appear in Data Monitor, either it does not exist in the controller or the client is requesting it with the wrong syntax.
4. To test end to end, write a value to a tag from the OPC test client and confirm the change is reflected in the reading client in real time.

6. Check the Gateway Activation

An RSLinx Gateway OPC server requires a valid gateway activation. Without one it runs in grace mode for only 7 days, after which it stops serving as a gateway.

• Open FactoryTalk Activation Manager → Manage Activations and confirm an RSLinx Gateway activation is present and shown as in use.
• Use Help → About to confirm the version. Avoid versions 5.01.00 and 5.01.01, which were pulled by the developers due to bugs; 5.02 is a known-good version.

7. Notes

• RSLinx Classic supports OPC DA only; it does not support OPC UA. If a UA client is required, the OPC server address is served separately by the client/gateway layer, not by RSLinx Classic itself.
• Confirm the OPC endpoint port is open on any firewall between the client and server before troubleshooting connectivity (check the port the OPC/UA client is configured to use).
• Because the fault is topic configuration rather than DCOM, chasing DCOM Event Viewer errors alone will not resolve the disconnect — verify topic mapping first.