[Feature Request] G32 Ran Flag
-
It would be helpful if there was a flag in the object model that was flagged as true when G32 has been ran and completed and flagged false when M84 or M18 is ran (but not when the Z axis is homed).
This would allow G32 to be skipped if its already been completed.
Klipper already has a similar feature. -
@jay_s_uk G32 just runs bed.g, you're free to configure that yourself. If you just want to know if mesh compensation is active, check out
move.compensation.type
. -
@chrishamm I know G32 runs bed.g. I could create a global value that runs but theres no way of clearing that when running M18 or M84 independently.
This is for gantry levelling and not mesh compensation
Here is the link the klipper documentation https://www.klipper3d.org/Status_Reference.html#quad_gantry_level -
Thinking about this a little more. Maybe the answer would be to extend M84 to run something like motors_off.g if it exists. That would give a lot more flexibility, especially around stepper motor brakes etc. Any parameters passed through could also be used too.
-
You can write a code in daemon.g that would clear the global variable for you if your axes aren't homed (which would happen in you disable motors or idle hold anyway)
The only thing is that you might need to put the code in a while loop in daemon.g so the variable get cleared faster (daemon.g has some delay, that you can lower with a while loop)
Be aware, when you home an axis it gets "un"homed during a homing sequence, therefore you need to set up additional variables to prevent your G32 global variable get cleared when you home an axis that was already homed.