Great, thank you very much for the quick action on this. The new version works great in my test environment. Will update once more after the testing in the production environment, but see no reason for it not work.

Thank you!

So this project has come back up (only been a short year ) and we were able to do some testing with both AsyncIO3::ReadMaxAge as well as the SyncIO2::ReadMaxAge, and it looks like the server side issue here is not so much with OPC 3.0 calls, just ReadMaxAge calls in general. I appears to treat all ReadMaxAge calls as being from cache - even if the max age has been set as 0.

Would it be possible to have the toolkit use the AsyncIO2::Read calls with this server, even if it is changed in a recent version, rather than 5.23.

I have OPCAnalyzer traces available from my testing if you'd be interested in reviewing them.

Forgive me for the delayed response. The server is the Matrikon OPC AutoCom Server v1.2.0.2.

We are using QuickOPC 5.23.2143.1 because of a need to target .NET Framework 3.5.

It appears that when doing an EasyDAClient.Read or ReadMutliple that an AsyncIO3::ReadMaxAge call is issued.

Is there a way to force this to be a AsyncIO2::Read call instead?

The use case here is that we are working with a Matrikon Server that does not correctly handle the ReadMaxAge call, but does appear to be responding to a AsyncIO2 Read as expected.