• Not Answered

OPC DA communication between App stations of 2 DeltaV Network

How exactly do we use OPC DA connectivity for communication between 2 DeltaV network ? 

Understanding , need to Install OPC DA server with OPC  mirror on the 1 DeltaV Apps. but how should the browsing of servers be as we create the pipes ? Mirror Diagnostics (on one apps )shows 

0xC0040006

The item's access rights do not allow the operation.

DeltaV 14.3.1, using DVS , VM for this test scenario.

Awaiting responses,

5 Replies

  • The error relates to the user security of the OPC Mirror client that connects to the OPC Servers. The Mirror Client needs to run under a DeltaV User that has Write privilege on the destination server. If data is flowing in both directions, then that account must be in both systems and have write access to the modules it is writing to.

    There are two scenarios for writing data. Either it is a user application that allows manual (infrequent) writes to various parameters in the system. Or it is to move data continuously from an outside source to make the data available to the DeltaV system. OPC Mirror is for the latter. In this case, you want to use a landing module assigned to the OPC DA server's Application Station. These are the modules that the OPC Client user account needs to have write access to. You can create a Plant Area for these modules and assign this to the OPC User in user security.

    Continuously writing to module parameters located in a Controller is not recommended as there is a recommended limit of write actions to a controller and too many writes will start impacting the controller's performance as it has to process these as interrupts. Use landing modules to receive data from the other system.

    The two application stations are connected via a third NIC. You should create a local user account on each computer with the same name and Password. Make sure you add it to DeltaV group. In DeltaV User manager, you can create a DeltaV Only account with the same name. This account need not be on any other computers and should not be granted access to any other Plant Areas than the one hosting the destination modules. The user has privilege to read all data, but would only be able to write to the landing modules.

    If you are in a domain, you still need to use local Windows Accounts for OPC DA so that the User account on the compute running OPC Mirror can authenticate its connection to the other computer. Domain accounts will not work. (not sure if it can be made to work, but using the local account does.)

    If you log onto each computer with the local windows/DeltaV account, using the same password, you can run OPCWatchit and confirm the account can write to values in the landing modules. Once that works, you can move onto OPC Mirror.

    Andre Dicaire

  • In reply to Andre Dicaire:

    I am having a similar issue where i am trying to pass OPC data between a DeltaV 14.3.1 system and a 13.3.1 system. You make reference to local windows accounts but both of my app stations are backup domain controllers so there are no local windows accounts and i cant log on locally. This setup worked just fine when my now 14.3.1 system was 12.3.1 but since the upgrade i cant get it to work.
  • In reply to eskrout:

    Are you sure that opc user have same password on both system and into a deltav groups.
  • In reply to LaurentB:

    check also deltavadmin password should be the same on both systems
  • In reply to LaurentB:

    Changes were made to the User and Application security settings for OPC Mirror. The OPC Mirror installation
    now creates a new local Windows group, DeltaVOpcMirrorUsers, which is assigned with the needed database
    permissions. All the OPC Mirror user accounts must be manually added to the group. Please refer to the Books
    Online topic OPC Mirror user accounts needed.