Hello,

I'm fairly new to VisualMicro, and have this message all the time no matter what I do in the Output window, and even for a trivial program of 15 lines. Some even more trivial programs do not have this issue, however, but I can't make out what does trigger this or what not.

It starts at the very beginning of the void loop(): the loop just contains an if, and within it a switch with just a few lines for each press of the button.

Some details:
- ATMega 2560 correctly working at 115200 bps on COM4 - no other interface involved.
- It is just lighting a few LEDs based on the push of a button
- there are a few trace/breakpoints
- The bounce2 library is loaded, but I commented out every line referring to it
- the port monitor is open, set to 115200, but says otherwise nothing special
- the VM Debugger dropdown is set to 115200 as well
- the is no serial.print or serial.whatever() anywhere
- the program compiles and works fine, bar for that message

There was one thread about this in 2020, but it doesn't really explain what the cause of this issue is.
The message also says 'Use WhenHit>=millis to limit the data rate'... Do I have to insert that in every sketch? And where then?

Read the docs and Googled to no avail...
Than you ! 

Hello,

I double checked; settings set as requested.

The zip file now contains

• the txt file that contains the output window/Micro Build and /Debug Trace - both are in the same text file.
• the whole solution folder without any modification, except for not including the .vs folder   

In the source of the sketch, the first small part, all commented out, is an initial version and that works without the error message. The actual uncommented part is a mini sketch that allows to progressively turn on 1-2-3-4-5 LEDs on the repeated push of a button.

Thank you,

OK, thank you for clarifying ! This is then really easy to fix! 

For those hitting this thread, I then noted the following:

• There must be at least one active breakpoint in the void loop(), or no breakpoint defined at all;
• The first active breakpoint must not be a comment;
• There can be disabled breakpoint before the active one;
• I might be wrong, but if you have (active) breakpoints, they better get hit quickly or VisualMicro gets impatient and shows the message. So an active breakpoint somewhere in an if or case that only rarely gets hit will not do the trick and you'll have the message all over the place - that's a bit of an annoyance because it's usually what one does;
• But then, you can set a tracepoint and check Continue code execution - this also suppresses the error message. For a tracepoint to work, at leastsomething must be filled in the Show a message box.
• And you cannot turn off the debugger as long as there are debug points - active or not - in the sketch as you have to be in a Release configuration for that.

That's a bit what I could find.