Monday, November 5, 2012

5 Things About Connecting To DeltaV OPC Server

Configuring an OPC client to talk to DeltaV's OPC Server is a chore. And surprisingly, there's not a lot of Google-ready goodies on the matter.

To rectify that situation, here's a list of the Top 5 things you need to know about OPC.DeltaV.1

5. OPC Remote - required client software

OPC Remote refers to the software you need to install on the OPC Client to be able to talk to DeltaV OPC.  I found this strange because when I was the PI OPC Interface to a KEPServerEX, OSI provided all the software for the OPC client and Kepware provided all the software for the OPC server.

Whatever the case, you need to execute OPCRemote.exe on each machine you designate as an OPC client. This package contains the requirements and diagnostic tools like OPC WatchIt.

4. OPC WatchIt! - diagnostic tool

This Windows application is a single form that let's you connect to the DeltaV OPC Server.  It's installed on the DeltaV Application Station and you ought to run it there to see if the OPC Server is up.

If it's working on the App Station, but not on the client machine, you know that you have a connectivity problem.  If it's working on the client machine, you know you're close to getting data flowing.

3. FrsOpcDv

The DeltaV OPC Server does NOT run as it's own Windows Service.
Taskmgr FrsOpcDv
 As in, if you type services.msc and go hunting through that list, you won't find anything that resembles the OPC server.   But if you type taskmgr and look through the programs that are running, you'll see FrsOpcDv.exe.  That, right there, is the DeltaV OPC Server.

This means that when you're setting up DCOM settings that you need to visit this entry in DCOM Config.

2. Local User Account is Your Only Option

There's only one way to connect to DeltaV OPC Server and that's with a local user account.  The one that's pre-configured is called, "DeltaVAdmin."  This account has to exist on the DeltaV App Station as well as the PROPLUS for the data to get sent.

What's crazier is that DeltaV is hard-coded to block anonymous access, which means your OPC client must be running as DeltaVAdmin (or equivalent).  If you're connecting DeltaV to a PI-OPC Interface, make sure the interface is running as "DeltaVAdmin".  This is basically your only option to getting it to work: you cannot use the local SYSTEM account.

1. DeltaVAdmin Needs DCOM Permissions

It follows that you need to create a local user on your OPC client called DeltaVAdmin.  It also follows that you need to grant this local DeltaVAdmin user Local and Remote authorities:

  • Local Access
  • Remote Access
  • Local Launch 
  • Remote Launch
  • Local Activation
  • Remote Activation
That's basically the list of things I wish I knew going into connecting to a DeltaV system via OPC.

Need A Pro Onsite?


Saulo said...

Very interesting. Congratulations!! Your text is highly instructive. I experienced all these peculiarities of the DeltaV OPC in an application where my system sends the data to the client system, which in turn feeds a PI. We had several mishaps until all the fine adjustments to be made​​, but now everything is running ok.

Hoyt Velasquez said...

This is a very helpful post. Those who are dealing with similar server situations are surely grateful for this. Thanks for sharing.

Unknown said...


Thank you for the Kepware endorsement! We appreciate your support. I would love to ask you a few questions about your experience with DeltaV and OPC. If you have time, shoot me an email:
[email protected]

Thanks again,

Unknown said...


I am having some trouble connecting DeltaV OPC server with a HIMA station. Kindly drop a mail at your convenience to [email protected]

Thank you

Unknown said...

Folks, I am trying to connect Delta V OPC server (version 9.3) to the latest ignition sofware. They are runnin on the same application station to eliminate the need to setup the profile for remote client (described in this blog). So far I have unsuccessful to get these 2 to communicate using the OPC COM connection. I have tried every combination that I can think off and still does not coomunnicate.

did anybpody has attempted to dosimilar setup in the past? is there any gotchas that you can think of?

Thank you.

James said...


Thank you so much for posting about OPC and DeltaV connectivity. There was enough information here to point me in the right direction to get our PI OPC Interface working again after a DeltaV App station rebuild.

PI Tech support were very good as usual troubleshooting with me but determined the problem was at the DeltaV side and they didn't have the knowledge to help further.

Interestingly our PI Interfaces run under a DeltaV domain account and not DeltaVAdmin, but the solution for us was resetting the DeltaVAdmin local user account password on the PI Interface machine (which existed but I don't recall ever setting this up manually).

I am told that during the App station rebuild a different DeltaVAdmin password was set, but then corrected back to the original a little later.

Thanks again!

Anonymous said...

#1 and #2 is wrong; there is no need to use DeltaVAdmin for a OPC DA Client (installed locally on the DeltaV Application Station or on a remote computer). I did that personnaly at least 50 times, with DeltaV v3 till DeltaV v12 (I've left Emerson in 2014).

Unknown said...

I found strange the need of OPC Remote for Delta V. Many OPC servers I tested and use need nothing installed in client machine beside the OPC Core Components. I tried but I couldn't find why Emerson provide the solution this way. Does anyone know that?

Unknown said...

Forgot to say it is a very good help for users dealing with Delta V and OPC connections.