- Posts: 20
- Thank you received: 0
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
I could not find the AutoCom server in Matrikon downloads. Please either help me finding the download, provide me with the server, or (last resort) just send me its CLSIS and ProgIds.
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.
There is no sufficiently "fine grained" setting: Currently, if the server exposes an interface, we suppose that it works.
One way to get around it would be if IOPCSyncIO2::ReadMaxAge worked correctly. In such case, you can set the AllowAsynchronousMethod in EasyDAClientMode to 'false' (this, in turn, is in the Mode of property in the InstanceParameters of EasyDAClient).
But we put in special handling for servers that are known to have problems. Which Matrikon Server (and version) are you using please? (and, which QuickOPC version)?
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.