800xA OPCDA Service Provider Configuration for Third Party OPC on a non-system node
System is as follows: 2 Redundant AS/CS, 1 Operation Station and one external server with a third party OPC Server.
Following the instructions in the System Configuration Manual to configure the 800xA System as a Client has not been enough to get it working. I'm trying to figure out how to configure the Service Provider manually. I'm able to import all the groups and tags from the OPC Server to the Control Structure but the service will stay in "Initialize". DCOM configuration seems to be alright as it was tested succesfully with other client software.
Service Provider Definition, Special Configuration Tab is configured with the remote opc server name, and the OPC Server Identity accordingly.
In Configuration Tab i'm not sure if I have to configure Node as my AS/CS or as the remote node (non-system). If so, do I have to add this node on the node structure as a pseudo server?
Thanks in advance for any answers.
Please check the DCOM settings again and make sure that common local user (eg.OPC User) has been created in both OPC Server and OPC client machines with all necessary permissions and the same user has been pointed in DCOM settings as well.
You must to run the service provider in 800xA Node where DCOM settings are configured e.g. CS (or) AS.
For more details,please refer 3BDS011222-510_en_System_800xA_5.1_Configuration.pdf
If you couldn't manage to fix the issue, please conatct your regional support center for the assistance.
I wonder if the problem could be bidirectional DCOM settings not in order?
If you as a starter read the answer I wrote on this thread (http://www402.abbext.com/OPC-client-dont-item-values-ABB-OPC-q1940667.aspx) you will notice that some OPC interfaces (asynchronous calls) are bidirectional and need DCOM setting in both ends.
If you flip the server/client sides of slide 6 in my attachment on that thread, you have your configuration (800xA acting as client to an external OPC server over DCOM).
The fact that you seem to succeed in uploading the remote OPC server tells me that you have setup the OPC DA Connector service correctly and managed to get the external OPC server to "accept 800xA as client", but to enable asynchronous calls, the OPC server must be able to post callbacks to the 800xA connectivity server.
Unless client and server share same workgroup or domain (which makes things with DCOM much easier) the user account running the external OPC server (check in the external OPC server's Task Manager) must:
a) exists as a local user in the 800xA server where the OPC Connector service run
b) have same password as on the OPC server side
c) DCOM settings in xA side must allow that user account to "access" the OPC DA Connector service.