Unexpected behaviour - 3.5.0b1
-
I was pondering doing PID auto-tuning from a macro and how to cancel the tuning mid way.
According to the docs, sending M0 would do so (which it does in 3.4.5)
I tried to use the new M291 functions in 3.5.0b1 to allow for the macro to continue after "Cancel" had been pressed.
Here is my macroM303 T0 P1 S240 F1 Q1 while heat.heaters[1].state = "tuning" if state.messageBox = null M291 R"Tuning" P"Tuning in progress" S4 K{"OK","Cancel"} if {input = 1} M0 M99 M291 R"Finished tuning" P"OK to save results, cancel to discard" S3 M500
However when I press "Cancel" I get an error
Error: M0: Pause the print before attempting to cancel itDespite no print being in progress.
If I add M25 before the M0 then I get
Error: Cannot pause print, because no file is being printed!
Error: Pause the print before attempting to cancel itIf I add abort prior to M0, it suppresses the errors, but tuning is not cancelled.
-
@OwenD thanks, I'll list this as a known issue. I'll probably replace the use of M0 to cancel tuning by M303 H-1 or something like that.
-
@OwenD I had forgotten that M0 cancels tuning. Does M0 sent manually work to cancel tuning in 3.5b1?
-
@dc42
No, M0 doesn't cancel tuning in 3.5.0 even from console -
@dc42
Also M0 didn't give any errors about cancelling the print first in 3.4.5 -
@OwenD thanks, I'll list this as a known issue. I'll probably replace the use of M0 to cancel tuning by M303 H-1 or something like that.
-
@OwenD
PS - where do the docs say that M0 cancels heater tuning?Found it! -
@dc42 said in Unexpected behaviour - 3.5.0b1:
@OwenD thanks, I'll list this as a known issue. I'll probably replace the use of M0 to cancel tuning by M303 H-1 or something like that.
That would make more sense in my mind as it avoids stop.g being run.
I'll mark this as solved for now. -
-
-