Force OPC DA Connect using DA 1.0 with OPC NET API|Classic OPC: DA, A&E, HDA, XML-DA, etc.|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
Force OPC DA Connect using DA 1.0 with OPC NET API
Avatar
Rick Shaw
New Member
Members
Forum Posts: 1
Member Since:
05/07/2014
sp_UserOfflineSmall Offline
1
09/03/2022 - 04:59
sp_Permalink sp_Print

Is there a way to force the async callback for group updates to always set up an IOPCAsyncIO callback rather than an IOPCAsyncIO2 callback. I have a use case where I need updated value and timestamps even if the values have not changed.

When calling connect using the Opc.Da.Server object the ConnectionData contains a flag to AlwaysUseDA20. I assume if true this avoids the use of OPC DA 3.0 calls.

I realize if a server implements OPC DA 3.0, I can use a keep alive to get a callback when data has not changed. This would be similar to using IOPCAsyncIO, in that the client would get regular callbacks when data is not changing.

Avatar
Randy Armstrong
Admin
Forum Posts: 1564
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
09/03/2022 - 11:03
sp_Permalink sp_Print

IOPCAsyncIO is a DA 1.0 only interface (i.e. it is not supported by the NET API or many servers).

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 54
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1435
Posts: 4855