Which G or M codes can be edited on the fly (while printing)?
-
Hi all,
Simple question really, which settings can and cannot be edited on the fly?
Particularly interested in settings you would normally put in 0:/sys/config.g
Can I change things that make sense for tuning during a print like M566 Jerk, M201 acceleration, or M203 max speed?
What about things that don't make sense to change during a print, like M569 drive mapping? I cannot think of a reason why on earth you would want to, but I tried to find a list of things that can and cannot be changed on the fly, and couldn't, so I figure the creation of an exhaustive list that can then go on the gcode wiki (https://duet3d.dozuki.com/Wiki/Gcode) would be great. Unless someone can already point me to a list?
Cheers all!
-
@jhalewood you can change most things on the fly, certainly speeds, current, accel, pressure advance etc.
Only ones that might cause trouble would be things like drive remapping, because then you'd need to rehome the axis. Though this could be done while a print is paused.
I think you might be able to redefine a tool though not sure what kind of carnage that might cause.
In general everything can be changed with gcode, at any point, just some might need to to take additional steps.
One caveat - if your slicer is doing acceleration control for different move types etc, it will be changing the settings as it prints so will override similar changes you make each time it does -
@jhalewood said in Which G or M codes can be edited on the fly (while printing)?:
Hi all,
Simple question really, which settings can and cannot be edited on the fly?
Particularly interested in settings you would normally put in 0:/sys/config.g
Can I change things that make sense for tuning during a print like M566 Jerk, M201 acceleration, or M203 max speed?
What about things that don't make sense to change during a print, like M569 drive mapping? I cannot think of a reason why on earth you would want to, but I tried to find a list of things that can and cannot be changed on the fly, and couldn't, so I figure the creation of an exhaustive list that can then go on the gcode wiki (https://duet3d.dozuki.com/Wiki/Gcode) would be great. Unless someone can already point me to a list?
Cheers all!
I can't off hand think of anything that you cannot change "on the fly" but there are order dependencies. For example, M584 must come before many other commands. When config.g is executed, M584 happens first, then the other commands. So if sent M584 "on the fly" it would override the first instance and you would effectively be putting it after those other commands and not before. It's probably safe to assume that anything can be changed "on the fly" but there may be consequences, so be careful.
-
Thanks both of you.
That's what I thought, but wanted to check.
If it's alright, I'll add a little comment to the wiki, since the above is not reflected in it.
