Hi,
we're using version 5.54.1151.1 / 2018.3 of EasyOpcClassic to acquire a thousand values from an OPCDA server using mostly subscriptions.
Everything works properly for some days, but then for no apparent reason, ItemChanged events stop coming...
When we detect this scenario, we try to recover by calling UnsubscribeAllItems on the EasyOPCDA instance, and then we dispose it, hoping to cleanup.
Then we create a new EasyOPCDA instance, and try to subscribe again all the signals.
However, the call to clientOPCDA.SubscribeMultipleItems(short_item_list) sometimes blocks indefinitely, locking our thread.
The only way we found to restore data acquisition is to completely restart the app/service.
Is there any parameter that we can use to tweak EasyOPCDA behavior to overcome this problem?
Is it the correct way to force the creation of a new connection to the OPCDA server?
we're using version 5.54.1151.1 / 2018.3 of EasyOpcClassic to acquire a thousand values from an OPCDA server using mostly subscriptions.
Everything works properly for some days, but then for no apparent reason, ItemChanged events stop coming...
When we detect this scenario, we try to recover by calling UnsubscribeAllItems on the EasyOPCDA instance, and then we dispose it, hoping to cleanup.
Then we create a new EasyOPCDA instance, and try to subscribe again all the signals.
However, the call to clientOPCDA.SubscribeMultipleItems(short_item_list) sometimes blocks indefinitely, locking our thread.
The only way we found to restore data acquisition is to completely restart the app/service.
Is there any parameter that we can use to tweak EasyOPCDA behavior to overcome this problem?
Is it the correct way to force the creation of a new connection to the OPCDA server?