TroubleShooting OPC

Get Started. It's Free
or sign up with your email address
TroubleShooting OPC by Mind Map: TroubleShooting OPC

1. What

1.1. Originally OLE for Process Control

1.1.1. OLE - Object Linking and Embedding

1.2. Renamed to Open Platform Communications


2.1. Standards

2.1.1. OPC Alarms & Events

2.1.2. OPC Batch

2.1.3. OPC Historical Data Access

2.1.4. ...More

2.2. Rockwell Only Uses - OPC Data Access 2.0a

3. WHY

3.1. Used to be

3.1.1. AdvisorPC

3.1.2. ControlView

3.2. Issue(s)

3.2.1. Now controls (SLC 500 + ) mean's can't until new product cycle

3.3. Now its like this

4. Communication Path

4.1. Client talks to Server

5. TroubleShooting Steps

5.1. 1 - Divide and Conquer

5.1.1. Check connection between OPC server computer and processor Ethernet - Ping RSWho Data Monitor (right click on Processor) If practical, connect OPC server directly to processor

5.1.2. Check connection between OPC client and OPC server Get 2nd opinion - Can a different OPC client connect (OPC Test Client, Rockwell Software data Client) OPC Test Client If client is on remote computer, try running it on a server

5.2. 2 - Go to the source (the OPC server)

5.2.1. Communication servers are in best position to know what error is

5.2.2. RSLinx diagnostics DDE/OPC Communication Events Active Topics/Items

5.2.3. Check KB 30094

6. Common Problems

6.1. Topic Not configured properly

6.1.1. Causes Topic points to something other than controller Ex - Workstation Wrong Device type Processor Type etc. Mis-spelled name

6.1.2. Identification When clicking on topic, controller not highlighted Communication contains errors as such

6.2. Processor note connected / powered up

6.2.1. Causes Controller is turned off Cable is disconnected

6.2.2. Identification Walk over to chassis and long Ping (if using Ethernet) See if it shows up in RSWho

6.3. Wrong Program Loaded

6.3.1. Causes Wrong downloaded program No program Topic points to wrong controller

6.3.2. Identification Go Online and verify program through Logix or data monitor Check for processor faults or LEDs Check address and type of processor

6.4. Too much traffic (network of processor)

6.4.1. Causes Controller is busy (ladded, MSG, periodic tasks, etc) Network is busy (too many requests and too fast)

6.4.2. Identification Putting controller in Program mode solves problem (if bottleneck is controller) Limiting maximum packets in topics (throttling mech in Linx) DDE/OPC

6.5. Firewall blocks connection to OPC server

6.5.1. Causes Someone undoes changes to Windows firewall (not common) 3rd party or hard/software firewall

6.5.2. Identification OPC Test client fails when selecting the server RSLinx Classis DDE/OPC --> Active Topics/Items shows no topics are act 2222 and 444

6.6. RSLinx Classic is not activated.

6.6.1. Causes No activation was purchased Wrong activation (remote clients required Gateway license)

6.6.2. Identification Linx Lite in titlebar could cause error Remote client needs gateway

6.7. Bad address in packets cause problems for other good addresses.

6.7.1. Causes At least 1 non-existent address in the same packet as other good addresses Causes error on any bit on packet

6.7.2. Identification Clients seem to work initially but stop working as more screens are opened RSLinx communication , "Tag or Item does not exist" --> shows item! Test client can see data, others can not Check bad address

7. Summary

7.1. Always Divide and Conquer to find scope

7.2. Use advantage of communication event logs and diagnostics

7.3. Check KB for errors

7.4. Get 2nd opinion using the OPC Test Client