Thank you.

The OPC Analyzer is here: www.opclabs.com/resources/product-information/knowledge-base/category/49-restricted

And the instructions are here: www.opclabs.com/files/knowledgebase/QuickOPC/QuickOPC-1-How%20to%20use%20OPC%20Analyzer.pdf

Best regards

It can be either caused by QuickOPC, or by the OPC server. I do not see a reason why it should be caused QuickOPC, but we need facts to establish the true cause.

Would you be willing to use a tool (OPC Analyzer) that will log the communication between your OPC client and the OPC Server? Note that your app needs to be changed temporarily to connect to OPC Analyzer instead (the OPC Analyzer acts as both a server and a client, forwards the commnunication and stores the log). The resulting log contains timing on the level function calls between the server and client, and from it, it should be possible to tell whether the delay is on the client side or server side.

Just to be absolutely sure, aren't you timing something else together with the Write? Can you post here a piece of code that does the timing please?

Are there also "one-shot" Reads in your application, or just Subscribe-s and Write-s?

Thank you