OPC client dont get item values from ABB OPC
Hello again! Sorry my bad english.
The task is to receive data to Honeywell server from ABB OPC server.
Today i tried to receive data from ABB OPC. I used for this DataSpy programm. It's can connect to ABB server but didnt see data from it(CantSeeItemsFromHone.jpg). Then i localy (ABB side) try to watch data using DataSpy i can do it(CanSeeFromABBLocal.jpg
I tried matrikon OPC too. And have this error ( ErrorMAtrikon.jpg). Matrikon launched on Honeywell side. But even with this error i can see data (CanSeeItemsFromHone.jpg).
The question is - How critical matrikon error? and why i cant see data by DataSpy. Meybe ABB have some settings with permissons on access data ?
I wanted to point you to a post made a few days ago, when I realized it was your question. I think you have to options:
1 Call ABB to get support with you problem
2 Use an OPC tunneler. E.g. Matrikon OPC tunneler has been used in the past. Then you don't have problems with dcom settings.
Look more carefully at the slide(s)!
1. Page 6 contains four (4) different accounts:
- opcconnect in client domain
- opcconnect locally in server
- opctransfer in server domain
- opctransfer locally in client
2. Asynchronous callbacks from the AfwDsOPCSurrogate.1 ("surrogate") server to client will be made from the DCOM identity set on the surrogate (on slide 6 it is "opctransfer").
a) When client is started, it uses the domain account (opcconnect) in the client. This account must be mirrored locally to the server node with the same password as in client's domain. DCOM access, launch and activation permissions must be set on the surrogate in the server node.
-The surrogate server will be possible to launch now (but no access is permitted to 800xA, yet, unless the Guest account has been activated, or left active after an upgrade from a previous version when it was active from factory default).
b) The server domain's opctransfer account is set as launching identity for the surrogate. The opctransfer account must be added to the 800xA system, with lowest possible access rights, preferably read only. The surrogate will logon to the 800xA system using this account.
- Data retrieval is now possible for synchronous calls, e.g. ReadSynchronous(), WriteSynchronous() etc.
c) To allow asynchronous calls such as ReadAsync(), WriteAsync(), Advise(), etc you must add a local opctransfer account in the client node using the same password as in the server's domain. DCOM remote access permission must be set on the OPC client program in the client node.
- It is now possible for the surrogate server to post asynchronous replies back to the client, e.g. sustain a cyclic subscription following AddGroup(), AddItem() and Advise() calls.
Some of the DCOM settings may be skipped if default access rights are modified, e.g. given to the Everyone user. This is considered less secure than configuring a dedicated user as on slide 6.