Softing DATA FEED OPC tunnel
Hello,
With Data Feed opc tunnel I want to send tag values from 800XA to IT infrastructure. For testing I added tags from Softing demo server and data quality is good ,I can see that value is changed. Data source connected TRUE and PROVIDED ITEMS is Dynamic.
But then i add tags from ABB opc DA quality is BAD comms failure, data source connected FALSE and PROVIDED ITEMS is STATIC.
Regards, Tomas
With Data Feed opc tunnel I want to send tag values from 800XA to IT infrastructure. For testing I added tags from Softing demo server and data quality is good ,I can see that value is changed. Data source connected TRUE and PROVIDED ITEMS is Dynamic.
But then i add tags from ABB opc DA quality is BAD comms failure, data source connected FALSE and PROVIDED ITEMS is STATIC.
Regards, Tomas
Asked 4 months ago
Answers
0
The ItemIDs with bad quality look very suspect to me... how did you get them?
Login to an arbitrary 800xA node as a proper user that has been added to the system.
Use the 800xA built-in OPC DA client test tool advdsopcclient.exe to connect to ABB.AfwOpcDaServer.1 and browse for some items and add them.
Notice the extremely useful Advise button which converts the ABB test client from synchronous (needing one-way DCOM settings when connected from a remote node) client to an asynchronous (needing bidirectional DCOM settings when connecting from a remote node) client. See attached document for an overview.
Before clicking Advise, a synchronous only client must "scan" for data by performing repeated Synchronous Read operations (preferably on active items using cached read). Once the client enters the asynchronous domain, active items will be automatically "pumped" to the client at very low overhead. The ABB test client make proper distinction between sync (scanned) and async (subscribed) data and output the timing of the OPC interactions so that the user will clearly notice the time it takes to perform them. Lack of proper DCOM settings will show up as Advise errors. Your regional ABB support center shall be able to provide you with a standalone version of the tool in case you need help with async DCOM across different workgroups or domains.
Likely you will now see proper ItemIDs and data (PLC must be downloaded, running and the OPC DA Connector service connected to the OPC server)
Any OPC DA client to 800xA must:
The generic System 800xA Item ID is:
OBJECTNAME:ASPECTNAME:PROPERTYNAME
Names can be given as full path, partial path or object name (all need to be unique to work, use the Find Tool to test its uniqueness).
The Plant Explorer will list "structure aspects" for all objects you browse to; from Details... on these aspects, the full path can easily be copied, e.g.
The aspect name and property names can be written off from the data carrying aspect when viewed in Plant Explorer.
Login to an arbitrary 800xA node as a proper user that has been added to the system.
Use the 800xA built-in OPC DA client test tool advdsopcclient.exe to connect to ABB.AfwOpcDaServer.1 and browse for some items and add them.
Notice the extremely useful Advise button which converts the ABB test client from synchronous (needing one-way DCOM settings when connected from a remote node) client to an asynchronous (needing bidirectional DCOM settings when connecting from a remote node) client. See attached document for an overview.
Before clicking Advise, a synchronous only client must "scan" for data by performing repeated Synchronous Read operations (preferably on active items using cached read). Once the client enters the asynchronous domain, active items will be automatically "pumped" to the client at very low overhead. The ABB test client make proper distinction between sync (scanned) and async (subscribed) data and output the timing of the OPC interactions so that the user will clearly notice the time it takes to perform them. Lack of proper DCOM settings will show up as Advise errors. Your regional ABB support center shall be able to provide you with a standalone version of the tool in case you need help with async DCOM across different workgroups or domains.
Likely you will now see proper ItemIDs and data (PLC must be downloaded, running and the OPC DA Connector service connected to the OPC server)
Any OPC DA client to 800xA must:
- Connect as a known user (LocalSystem does NOT work)
- Use proper itemIDs (or browse)
The generic System 800xA Item ID is:
OBJECTNAME:ASPECTNAME:PROPERTYNAME
Names can be given as full path, partial path or object name (all need to be unique to work, use the Find Tool to test its uniqueness).
The Plant Explorer will list "structure aspects" for all objects you browse to; from Details... on these aspects, the full path can easily be copied, e.g.
The aspect name and property names can be written off from the data carrying aspect when viewed in Plant Explorer.
0
Items are taken from ABB OPC and used by Softing OPC. Then I browse ABB opc item quality is good, bad only in Softing OPC.
I solved a port of problem by running this program as Service and under 800xaservice account. But I have to trigger to work those items.
I solved a port of problem by running this program as Service and under 800xaservice account. But I have to trigger to work those items.
Answered 4 months ago
Add new comment