Bryan, I received your email thanks and have added the image to your post.
You are certainly talking about debug for .cpp in libraries. That is a neat system you guys are working with!
I have a few tips:
1) I notice you are trying to set a breakpoint on the call to initialise the wire i2c system. I know it is just an example for the picture because it isn't a useful breakpoint but have this information just in case.
If you want to see what i2c device ids are available when the arduino boots up then there is visual micro debug option called "Startup I2C Report". Enabling this option will give you a list of connected i2c device ids in the debug output windows.
If you are connecting and disconnecting i2c devices when the arduino is running then let me know because there is a {special variable} name you can add to breakpoints that will give an i2c report at any time during a debug session.
2)
All the classes in the reefAngel:Init should be accessible to breakpoints in the main .ino file.
I guess you can use something like this as a debug message from the .ino:-
Joystick x pos ={Joystick.x}
Does the main .ino file call something like ReefAngel.Init()? If so then you can add breakpoint conditions to that line (or anywhere after it) such as :-
The value of joystick x pos ={Joystick.x} and other stuff = {LCD.blah},{TempSensor.blahblah}
The breakpoint message about would result in 3 watched expressions
- Joystick.x
- LCD.blah
- TempSensor.blahblah
And one debugger message
Quote:The value of joystick x pos =456 and other stuff = 123,456
Or simply debug expressions without a message
{Joystick.x}{LCD.blah}{TempSensor.blahblah}
Hope this helps for now