Thank you. I agree that 20 seconds is very long.
In order to work with OPC Analyzer, please download and install the <a href="/LinkClick.aspx?fileticket=N4D8rpfbWkM%3d&tabid=195">OPC Analyzer Tool (<a href="/LinkClick.aspx?fileticket=grX1_Kt-DUM%3d&tabid=195">readme file). After installing, enter any necessary information in the "Category Filter" and "Remote Machine Name" fields, and press the "Refresh" button. Then, select your target OPC server from the "Server" drop-down, and make sure the trace is started (if "TRACE STOPPED" is displayed, press the "start trace" button).
You then need to modify your application (or change the settings in the demo app) to connect to the OPC Analyzer instead of your real target OPC server; the OPC Analyzer acts as an intermediate logger. The ProgID of the OPC Analyzer is "OpcTestLab.OpcAnalyzer.1". You can then run your application, and you should see the trace being collected in the OPC analyzer. Afer you are finished, select File -> Save Trace in the Opc Analyzer, save the .TRA file, and send it to us - ideally, attach it to your reply in this forum.
For this particular problem, a log file from your application (or comparable information) with times of method calls/method returns will also be needed.
Note: The OPC Analyzer tool is available to OPC corporate members only (such as OPC Labs are), thus the download is only permitted to your user account (you must be logged into our site), and you can only use it for the purpose of troubleshooting this particular problem.