Not at all @purple - there are 263 ARC software releases with fixes inspired from user experience. Your experience has inspired an update today, as well.

The process to identify an issue starts with reviewing the project. Without a project to review, there is no information for me to see what scenario is causing the experience. Once you provide a project that crashes or locks up, it will be easy for me to fix

In this thread, we have identified that the performance enhancements of the benchmark utility flood the communication channel at a high sample count. This has resulted in an ARC update.

Take your time with an Example Project that demonstrates the software lockup - when you come across it, let me know, i'm always here to help.

I have just put up a project to the cloud. It is called 20151219 pausing test. Just notice the changes with and without the Connection Diagnostics running. This is on a bare board.

awesome, thanks!

First, that project has the debug control added, which is incredibly resource hungry and debugs every command sent to and from the ez-b in the gui thread. The plugin should not be used for testing - as it's a connection plugin only, hence the title. The title and description of that plugin in no way leads itself to be used for performance testing. Please do not use the connection plugin when not being used to debug connection failures. Due to this incorrect use of the connection debug plugin, i will update the description so others do not confuse the name of the plugin with a reason to use it for any other purpose.

Here you go - here's the fix for your example project. I added educational notes in the project. Hopefully this will contribute to your programming learning experience

Your new file: PurpleFixed.EZB

Let me know if you have additional questions.

Updated the connection diagnostic plugin with a description that includes the warning about why not to use it. Even though it's name and description does imply what it is - let me know if there are other plugins which may cause confusion and be used incorrectly as well. Thanks!

Here's a video demonstrating to avoid confusion of how the Pause On and Pause Off work... Let me know if you have any questions!

@DJ You are the one that is confused.

What else can i do for you? Let me know and we'll get you up and running!

Go back and run my project. Take note of the update speed of the graphs. Then remove the Connection Diagnostic, now note the speed of the graphs again. Now put the Connection Diagnostics back in and look at the update speed of the graphs. I am using the Connection Diagnostics to show that with it added to the project the update speed increases by 5 times. This corrolates to the read 300 adcs. This also contradicts your flooding the communication link theory.