OPC error in Process History View

When launching Process History View on workstations, we continually get the following error popup:  CoCreateInstanceEx Failed:  No OPC Connection.  If you click OK, the message goes away and PHV opens successfully, but the error is annoying to the operators.  Does anyone know how to get rid of this issue?

Thanks in advance.

.

5 Replies

  • Can you check if DeltaV OPC DA Server (frsopcdv.exe) is running? Can you open OPCWatchit and verify you can read data?
  • In reply to Lun.Raznik:

    Lun is correct to check that. Next step depends on whether FRSOPCDV is running or not.

    Every DeltaV node runs the OPC Server software. On workstations, it can be licensed with the EXCEL ADDIN license up to 500 tags.

    PHV is the only client that can connect when the OPC Server is not licensed. PHV uses the local OPC server on the Operator station for runtime data in trends. If history data is available, the trend history is drawn, and then the Chart uses local OPC data to trend in real time. This allows both Historized and non-Historized values to be trended on together.

    The default servers in PHV can be set to retrieve data from any node, but for the OPC server, it should always be the local computer OPC server. Note that the Historian and Event Journal server selections have drop down lists to choose from. The OPC server does not.

    Let us know what the frsopcdv.exe process is doing.

    Andre Dicaire

  • In reply to Andre Dicaire:

    frsopcdv.exe is running on the workstation
  • In reply to Andre Dicaire:

    Andre - perhaps this deserves its own thread or maybe considered proprietary - a good subject for a geeky PowerPoint or online course if anyone was ever so motivated, but: The omnipresence of OPC in the various interfaces (Operate, PHV, DeltaV Historian, Control Studio Online) - correct me if I'm wrong - provides some insight into data latency. So when I stare at Control Studio online it's clear that I'm not seeing every cycle of a 1 or 2 second module. Is it the workstation-specific OPC server that provides data from controllers to the various clients, or is it just "along for the ride"? Whether the server is polled / advise and so on is also interesting . . .
  • In reply to John Rezabek:

    Any more insight on this issue? Again, it's not preventing anything, but it's very annoying to the operators.

    Thanks