We need a verbose mode for general troubleshooting
-
I think it would be nice if there was a verbose mode available in console which could be enabled via an Mnnn gcode. This verbose mode would cause the duet to echo EVERY gcode before it is executed. This would be immensely helpful for troubleshooting unwanted behaviours.
-
@randyl00123 said in We need a verbose mode for general troubleshooting:
EVERY gcode before it is executed
Just to play devil's advocate here, but since all gcode that gets executed is already provided by the user, what benefit is there to have it stream past in the console? It's either executing a configuration file, a macro, or a sliced gcode file.
-
@phaedrux because I sometimes have gcodes run in other sub macros which have been called. For example, in my homeall.g, I call a file I've called Find_Z_Range.g. When things go ary, such as when the bed starts rising for no reason I can find, it's nice to know what command lead to it. I know from C++ coding, I would often insert line numbers or comments to help with troubleshooting. Just a way to have all macros and gcodes sent to console while running when in verbose mode. It should be able to be turned off when NOT troubleshooting.
-
@randyl00123 Have you tried using the gcode option in M111? You may need to use a USB connection to see the output.
-
@randyl00123 What about using conditional Gcode with some global variable (turing on and off "verbose mode") and do conditional M117-display message in macro files?
-
@cecil If you can attach a USB cable to your Duet, you can send
M111 P3 S1to see when G-codes are executed. It can be turned off again by sendingM111 S0.Duet software engineer
-
@randyl00123 Use echo in the macro, it'll show up in the DWC console.
-
@chrishamm said in We need a verbose mode for general troubleshooting:
M111 P3 S1
Do I NEED to use a USB, or will the web interface not transmit the verbose? I've used M117, but wasn't aware of M111, which I'm trying at the moment. Thanks for the tip!
-
@randyl00123 Pretty sure you need a usb console to see the m111 output.
-
@gloomyandy One thing I have always found confusing about the gcode explanations is the inconsistancy of definitions. For example, in M111, Pnn is the module number. What is a "module", how did it recieve a number, and what does that "number"refer to?
-
@randyl00123 I found the same confusions when trying to figure out what an 'axis' vs motor number vs drive axis, etc. I'm not new to programming, but I find it quite confusing trying to interpret what is being said. Personally, I'm finding that examples of code from other people to be more helpful when actually writing the code. The Gcode pages are ok once you actually understand what a gcode does, and it's particular switches.
Granted, I've decided to build one of the most complicated kinematics out there. I have a background that includes programming batch files back in DOS days, Qbasic, Pascal, C and C++ in College, so if I'm having a hard time understanding the nuances of the gcode explanation language, I can't even imagine the confusion of a nube.
-
@randyl00123 In fairness M111 is really a pretty low level sort of tool and probably unlikely to be used by many folks. Like many gcodes if you just enter the code (M111 in this case), you get some information. With M111 it will display all of the available modules (and their associated numbers) and the debug level set for each.
-
@gloomyandy One other "wish list" item: a way to comment out blocks of code, rather than semi colon every single line...ie C++ uses // \ or /// / to comment out a larger block of code.
-
@randyl00123 said in We need a verbose mode for general troubleshooting:
@gloomyandy One thing I have always found confusing about the gcode explanations is the inconsistancy of definitions. For example, in M111, Pnn is the module number. What is a "module", how did it recieve a number, and what does that "number"refer to?
Send M111 and it will list all the module numbers.
