configure Node in Node Adminstration for third party OPC server
I share the same problem when it comes to connect 800xa to a OPC Server. I get the same result: service in initilize.
Have you succeeded in this? and if so, how?
did you add a pseudo server in "node adminstration structure"?
Voted best answer
There are few reasons to add a pseudo server; I can only think of two right now:
1) To enable RNRP System Alarms from a "foreign" node running RNRP, e.g. a domain controller to be seen in 800xA System Alarm/Event Lists
2) As a placeholder / marker to document nodes involved in the system.
a) Please check that the remote OPC server is reporting "OPC_STATUS_RUNNING" status on GetStatus() calls. This can be checked with e.g. the built-in OPC DA test client, advdsopcclient.exe
b) Please verify that the account the OPC server is running under can do callbacks to the connectivity server node. Again, use the advdsopcclient.exe and test that after creating an OPC group, clicking "Advise" do return OK.
Can you please describe the problem in breif,
Is it you are expecting 3rd party OPC communication with 800xA system?
Here you want to create a common transfer account to establish the communication between the two machines, you can select any one of the server from 800xA side(ex:Aspect or IM )& make the DCOM settings in both the 3rd party OPC machine & 800xA server.
OR you want 800xA with any ABB propetiery connect ex:800M Connect?
For 800M connect OPC server to work you have to add controllers identity(primary IP address) to the OPC server panel (both DA and AE) before creating OPC datasource definition under control network.
I've tried asking a member a question regarding this problem:
I want to connect 800xa to a Ifix OPC server Node.
But I don't know if I must add the Ifix Server to the Node Administration Structure in Plant explorer? Is it okay to add third party servers to the Node Admin Struct?
In my case the 800xa Servers and Ifix servers i in the same domain.
No, you do not need to add a foreign server node to the Node Administration Structure.
The purpose of inserting a pseudo-server node is to enable RNRP alarm/event (if the foreign server is installed with RNRP) to appear in workplace alarm/event lists. Without insertion of pseudo-server, only RNRP monitor will present node state.
Please go ahead with checking my other suggestions:
a) server state
b) possibility to perform callback via DCOM
Regarding Node adminstration structure I interpret your answer that I could add the third party server in Node administration Structure as placeholder for network hierarchy. This will clarify the task adding a node in Service provider aspect:
This Is my result verfiying:
Solved it !
Okay it suddenly started to work. My steps
1) In Control structure, new object "Generic OPC Server Network"
2) In the wizard selected CS-server, then selected a arbitrary OPC server.
(This creates a Service group and provider in Service structure).
3) Then in "service structure" the newly created "Service provider" under "Special Configuration" I choose a Remote OPC Node and then press apply.
4) Now choose a OPC server Identity (Under the same tab as OPC Node). Press apply.
5) then under tab Configuration uncheck and apply the Enable box, then check and apply. Now the state is : service
Just in case you didn't see my comments:
I actually got to solve the problem following Stefan's recommendations and by making new tests using OPC simulators. My conclusions for all the readers:
- As stated by Stefan, DCOM configuration has to be configured taking into account bi-directional communication.
- It is very important to identify the users that run the remote opc server service in order to configure correctly the log-on parameters.
- Firewall and antivirus software can give some trouble, check the correct configuration for your application.
- The OPCDA Service provider is configured using the field "Remote Node", with the name of the node in the network, when you press the Refresh button you should be able to see the name of the remote opc server. The service must run on the 800xA node where DCOM has been configured, once you enable the service it should go from Initialize to Service if everything is correct. If you still have DCOM or users issues it will stay in Initialize.