One problem I ran into is how to rezero during a tool change to account for the height of a new cutter. After I start the gCode, it seems I cannot jog the axes again until I power cycle the Maslow.
Even when the machine pauses for my tool change, I can’t move the Z axis up to get more clearance for the wrench, and can’t move it down once the new endmill is installed to touch off on the work piece to rezero. X and Y jogs are also unresponsive.
Wondering if I just don’t know the right series of buttons to press to jog in this scenario
This behavior that requires me to power cycle the maslow is also quite annoying for situations in which I want to run multiple gCodes. It seems like after the first file is run, not only can I not jog the machine, but I also can’t seem to get any more gCodes to upload to the machine.
I do think that while the machine is paused you can’t move it (that makes sense as a limitation of the FluidNC motion planner), but after a gcode file finishes running you the machine should go back to the same state that it was in before the file was started and be ready to run a new file.
You are seeing that after fully finishing running a file you aren’t able to start a new file?
Generally the easiest way to do jobs with multiple tools is to split each one into it’s own gcode file
One problem I ran into is how to rezero during a tool change to account for the height of a new cutter. After I start the gCode, it seems I cannot jog the axes again until I power cycle the Maslow.
Even when the machine pauses for my tool change, I can¢t move the Z axis up to get more clearance for the wrench, and can¢t move it down once the new endmill is installed to touch off on the work piece to rezero. X and Y jogs are also unresponsive.
Wondering if I just don¢t know the right series of buttons to press to jog in this scenario
can you post the logs? I suspect that it’s getting into alarm mode somehow.
ideally you should only release tension, and jog the Z axis, then apply tension