Thank you.

It is possible that .NET garbage collector may have something to do with this - or possibly not, but we should rule it out first. Please

I am sorry that I have to "task" you again, but there is hardly any other way, unless we get to reproduce the issue on our computer. Basically, I'd like you to run the Performance Monitor tool (included with Windows). I am not sure whether/how you are accustomed to work with it - it's not hard, and there are plenty of materials on the Web to explain.

If you could please use PERFMON to observe the process (in this case, it will be the Excel process), and its GC-related characteristics, and figure out whether there isn't a correlation between .NET GC collections, and the periods of the high CPU usage. The related counters are mainly under ".NET CLR Memory": # Gen n Collections, % Time in GC, # Bytes in all Heaps, #GC Handles etc. Other .NET counters in other groups may be interesting as well, and the CPU consumption.

Seeing the chart of "Gen ... Collections" counter (a screenshot, or send me a data capture file form PERFMON) would allow me to determine whether the .NET garbage collector might be responsible for the pauses.

If you need instructions that are more "step by step", I can work on that too.

Best regards

Hello,
how big is the Connectivity Explorer video? I may have to increase the maximum allowed size, if it is big.

Was the "irresponsivenes" of Connectivity Explorer at the same moment as that of Excel, or were they generally at different times?
When you write "Impossible to be used", is it meant to say that also the user interface of Connectivity Explorer was irresponsive (e.g. you could work with its controls)?

Thank you

Hello,
thank you for the additional information.

Obviously, there is no absolute guarantee of the refresh rate, on Windows. But the somewhat long "pauses" seen on the video are suspicious, I agree, so we will investigate them.

I am sorry but I have to bother you with additional tests, so that we can decide well. I would like you to do the following: For some of the variables you are monitoring, also add the StatusCode and ErrorMessage to your Excel sheets. Please see the attached picture. basically, instead of drag-and-dropping a cell from Value column to your Excel sheet, you would drag-and-drop also the cells under the StatusCode and ErrorMessage columns (the picture I used is from OPC "Classic", where instead of StatusCode there is Quality - but you get the idea).



Then, test that these actually work - e.g. by disconnecting the communication - some actual error text should appear in your Excel sheet.
And then, test again your "normal scenario", and observe whether during the "pauses", the StatusCode remains Good and the ErrorMessage remains blank, or whether some interesting change appears there during the "pauses".

In an additional test, can you please run the Connectivity Explorer *together* with your Excel sheet, and check whether 1) there are any "pauses" in Connectivity Explorer as well, and if so, 2) if they happen in a "synchronized way" with your Excel sheet.

Best regards

Hello,
thanks for answers.

For further troubleshooting, it is really important that you also subscribe to the error message. We must know whether there is an error during these 5 seconds or so, and if so, what precisely the error is.

Best regards