Avoiding accidental homing via screen input while mid-print
-
Hello,
I'm running a machine using a Duet wifi 1.4 board + Duet extension 5X with firmware version 3.2.
I've been looking for a way to prevent the user from being able to manually perform a homing sequence once the print has begun or at least create a warning requiring user confirmation ONLY if the printer is already doing something else.
At the moment I have tried to use meta commands to consult the state of the machine prior to entering the home routine but this has not been successful since when executing the homing itself the machine changes state to "busy".
I have also tried to query if the machine has already been referenced in a previous home to avoid doing the same again, but it happens that when executing the homing itself, the state of the same is reset.
I wanted to know if there is any way to achieve this since in our case the machines use a BLTouch as a Z probe and executing a Z homing during a print could result in damage to it.
Thanks in advance.
-
something like if move.axes[0].homed = true then exit else home the printer.
If you haven't already, you should poke around in the Object Browser plugin in 3.2.
-
Thanks for the response.
I have tried similar aproaches.
The thing is that using "if move.axes[0].homed = true" does not work properly if inserted inside de homex.g as it seems the machine actually resets the X homing value when that function is run and before entering into the code, and that results in move.axes[0].homed being equal to false every time or at least this is what I understood from the different tests I've made.
-
Hmm, yes that would be the case because once a homing file is called the axis i marked unhomed. The if check would have to happen outside of the homing file.
I could see this being solved by variables where you could store the homed status and then check it.
-
@Phaedrux
I have it in a macro for priming the nozzle.
So it should work in the slicer start g-code. -
Isn't there something in the JOBS section of the Object Model that could be tested in the homing macros?
Frederick
-
state.status=processing maybe? That's different than the busy for homing.
-
This post is deleted!
