DCOM OPC Communication with Domain and workgroup systems
Hi Stefan, I would like to ask you a question if you don't mind. I have an ASCS running in the workgroup & 3 customer DCS systems running in 3 different domains.
My question is is it possible to share DATA between my system (in a workgroup) and the customer non 800xA system running in the domain. I am only looking for data sharing using DCOM settings.
If it is possible, can you please let me help with the procedure if you have one which describes this process along with generic OPC process?
My question is is it possible to share DATA between my system (in a workgroup) and the customer non 800xA system running in the domain. I am only looking for data sharing using DCOM settings.
If it is possible, can you please let me help with the procedure if you have one which describes this process along with generic OPC process?
Asked 5 months ago
Answers
0
@stefan: will refer your comment on previous ques. Thanks
Answered 5 months ago
1
Basically, the answer is yes.
However, you must dissect and understand the requirements for asynchronous DCOM (where client connect server, add groups & items and finally calls advise after which the token is passed to the server who will continue by making opposite direction callbacks with data, so called "OnDataChanged" events).
Clients staying in the synchronous domain will not call advise and instead "feed" themselves by posting cyclic "Read" calls to the server where the data is passed with the read return.
Then have a look at the PDF I posted detailing the need for four (4) different accounts to be created in various places; make sure to understand the difference between being able to launch a server using account "A" after which it may redress itself into account "B" (this will e.g. be the case with the ABB 800xA OPC DA Surrogate which may be allowed to be launched by a "remote stranger" but who must redress [DCOM setting = Run as this user...] into an account "B" having permission to access the 800xA system which a remote account cannot have).
OPC surrogate running as This user set to a well known user of 800xA and having appropriate access permission in the system (Everyone = Read, Operate = Write, etc...)
Both client and server computer must know of A and B, hence there will be four (4) accounts 2xA + 2xB. Passwords must be equal for the "local" and "remote", A(l) = A(r), B(l) = B(r).
Then a number of DCOM settings must be made with DCOMCNFG.EXE.
Server side) allowing A remote launch and remote activation of the OPC server
Client side) B need remote access on the OPC client process.
However, you must dissect and understand the requirements for asynchronous DCOM (where client connect server, add groups & items and finally calls advise after which the token is passed to the server who will continue by making opposite direction callbacks with data, so called "OnDataChanged" events).
Clients staying in the synchronous domain will not call advise and instead "feed" themselves by posting cyclic "Read" calls to the server where the data is passed with the read return.
Then have a look at the PDF I posted detailing the need for four (4) different accounts to be created in various places; make sure to understand the difference between being able to launch a server using account "A" after which it may redress itself into account "B" (this will e.g. be the case with the ABB 800xA OPC DA Surrogate which may be allowed to be launched by a "remote stranger" but who must redress [DCOM setting = Run as this user...] into an account "B" having permission to access the 800xA system which a remote account cannot have).
OPC surrogate running as This user set to a well known user of 800xA and having appropriate access permission in the system (Everyone = Read, Operate = Write, etc...)
Both client and server computer must know of A and B, hence there will be four (4) accounts 2xA + 2xB. Passwords must be equal for the "local" and "remote", A(l) = A(r), B(l) = B(r).
Then a number of DCOM settings must be made with DCOMCNFG.EXE.
Server side) allowing A remote launch and remote activation of the OPC server
Client side) B need remote access on the OPC client process.
0
Hi
Kindly find attached DCOM settings manual for your reference.
Kindly find attached DCOM settings manual for your reference.
Answered 5 months ago
Add new comment