Hello.

One more thing: There is a "free-usage" State property ('object' type) passed in arguments to each operation (such as Read), and you get the same State in the results of that operation. I am not sure if that can help you, but it is good to know.

So if you somehow need the IndexRange that you passed to Read, you might pass it *also* to the State in the arguments, and then pick it up in the State in the result.

Not all overloads of ReadXXXX will show you the State parameter. What happens under the hood is that all such overloads ultimately construct a single "arguments" objects that is passed to Read, and that one *does* contain the State. So if you do not see the precise overload of the ReadXXXX that you need, rest assured that you can find a different one that will do the trick. I am ready to help you out if needed - that's why we are here.

Best regards
 

Ok. I got that I need to do refactoring of a more substantial part of my software.
Best regards.

Hello.

I do not quite understand the question. The Arguments in the EasyUADataChangeNotificationEventArgs, and everything below it, is just a copy of what has been passed to the component when the subscription was established. So, it is not a new information that was somehow returned by the server. It is *your* information that you have specified,.

If you are using Reads instead, you also specify the IndexRange when initiating the Read. How would it be possible that you pass in the IndexRange but do not know what you have passed in?

Please clarify.

Best regards
 

Hello, i have a problem with a machine tool that does not support very well item subscriptions. I have to convert actual read routines, to read data changes using polling instead of item subscriptions. In the actual implementation, in the DataChangeCallback event handler,  I use the property IndexRangeList from EasyUADataChangeNotificationEventArgs.Arguments. I need that information. How can be obtained without using data change events?
Thank you!