Hi,

The Visual Micro Pro system is available to you already to try. When you attempt to build the first time each day you are asked if you want to start a trial, you can click Start Trial and use the pro debugger. It's the same as buying.

However the visual micro debugger will only help if you have used a lot of serial.print commands in your code without using the F switch. In that case all the strings in your serial prints will be consuming the arduino memory and that is where the debugger will help. You will be able to remove your serial prints and use the debugger messages instead. The debugger does not add the messages to the arduino code, it keeps them on the pc and shows the correct message when breakpoint #1 or #2 etc. is hit.

If you have used a lot of serial prints then you can remove them and probably free some memory. The debugger does have small overhead per breakpoint so it might or might not be a useful solution.

Visual Micro, In Atmel studio, will allow you to build Arduino but debug with hardware/atmel debugging. So another option is to buy a hardware debugger such as JTAG but again I can tell you that debugging an Uno or Mega is not easy. It requires you to change some fuses on the board, can damage the board if done wrong and can in some cases 
disable SPI. Hardware debugging is not easy for the type of board you have so this is why Visual Micro released the Serial debugger.

You are caught between a rock and a hard place. If you have a lot of serial.print statements then the Visual Micro Pro debugger might well be an option but will only prove to be useful after you test it and subsequently remove your serial print statements. If you do that don't forget to click YES to save the Solution when you close your project. Atmel and Visual Studio save breakpoint info into the solution so if you don't save you will lose your breakpoint config. One past user saved 5k by removing his Serial.prints.

Sorry can't be of more help.

You can add {vars} to debug messages which also become watch expressions

You can switch on vMicro>debugger digital/analog/free memory graphs. These are refreshed each time the loop is hit
or
You can use special vars in breakpoint messages such as {@DigitalReport} which also shows the graphs but refreshes when the breakpoint is reached.

You can plot your own charts

http://www.visualmicro.com/page/User-Guide.aspx?doc=Working-With-Breakpoints.htm...

http://www.visualmicro.com/page/User-Guide.aspx?doc=Working-With-Breakpoints-Whe...

http://www.visualmicro.com/page/User-Guide.aspx?doc=Multiplot.html

Hi,

That's old out of date documentation.

You should not change any code structure for debug. Use as published by the author or whatever you are using.

Visual Micro does now support debug of libraries.

You just need to add the existing libraries as shared projects to your visual studio solution

You can see a shared project working if you use the checkbox on the visual micro "add library to code" menu. Then add a library.

http://www.visualmicro.com/post/2017/01/16/Arduino-Cross-Platform-Library-Develo...

Hi,

Please change the tool bar option from Debug to Release. Then build and upload.

After that visual micro will take the same amount of memory as the Arduino IDE

Below shows in my connect window???:

VMDP�_|||35|_VMDPR
VMDPR_|252:31:||1

No visualizations are occurring like were seen on previous smaller Arduino Automaton process testing.