Hi,
I am communicating with OPC DA server using OpcLabs.QuickOpc 5.63.246 (.net6.0). In my application I perform subscription to the item A at startup, and in some cases I need to read the value of item A using EasyDAClient.ReadMultipleItems(DAReadItemArguments[] argumentsArray). Data source is ByValueAge and ValueAge is 1 sec.
Both for subscription and for reading I use State and operate with that when I get the response from OPC DA server. In most cases I perform read operation after the value changes, so it happens after I get subscription notification (< ValueAge). The problem is, in this situation State contains wrong object. Instead of State I specified in the DAReadItemArguments before reading using EasyDAClient.ReadMultipleItems(DAReadItemArguments[] argumentsArray), I receive object of type OpcLabs.EasyOpc.DataAccess.Implementation.DelegatingEasyDAClient+DelegationRecord, which is impossible to operate with.
Specifying ValueAge = 0 sec fixes the issue, but this is not expected behavior and seems to be bug.
Best regards,
Kristian
I am communicating with OPC DA server using OpcLabs.QuickOpc 5.63.246 (.net6.0). In my application I perform subscription to the item A at startup, and in some cases I need to read the value of item A using EasyDAClient.ReadMultipleItems(DAReadItemArguments[] argumentsArray). Data source is ByValueAge and ValueAge is 1 sec.
Both for subscription and for reading I use State and operate with that when I get the response from OPC DA server. In most cases I perform read operation after the value changes, so it happens after I get subscription notification (< ValueAge). The problem is, in this situation State contains wrong object. Instead of State I specified in the DAReadItemArguments before reading using EasyDAClient.ReadMultipleItems(DAReadItemArguments[] argumentsArray), I receive object of type OpcLabs.EasyOpc.DataAccess.Implementation.DelegatingEasyDAClient+DelegationRecord, which is impossible to operate with.
Specifying ValueAge = 0 sec fixes the issue, but this is not expected behavior and seems to be bug.
Best regards,
Kristian