Klipper: Unknown command:"M108"

[Hywelmartin]

So I started a print and after it got to initial temps set. it halted

I got this from the "terminal"

Send: M84
Recv: ok
Send: M104 T0 S0
Recv: Not SD printing.
Send: M108Recv: ok
Send: M140 S0Recv: ok
Send: M106 S0Recv: ok
Recv: okChanging monitoring state from "Cancelling" to "Operational"
Recv: // Unknown command:"M108"

I have checked the gcode for M108, and there isn't any so this must be octoprint.. Is there lack of respond from Klipper so that a timer shut of the printer or something?? M108 is : Cancel Heating in (Marlin)...

klippy.log

edit:

Found this in the log

Move out of range: -0.718 -1.137 285.703 [41763.784]
Move out of range: -0.718 -1.137 285.703 [41763.784]
Exiting SD card print (position 510)

strange.. It is supposed to do this

        M117 SET_DELTA_HEIGHT
    G28
    G0 F4000 X0 YO Z10
    PROBE

[jakep82]

It is Octoprint. I believe you can disable the M108 in the Behavior tab.

[Hywelmartin]

So now is that sorted... the 108 issue... but why did it happen in the first place??

[KevinOConnor]

An M108 command doesn't cause an error in Klipper - the message sent back to OctoPrint is just a warning - OctoPrint displays it and does nothing else.

It looks a move in the g-code file you were printing (via virtual_sdcard) was out of bounds - do you have the gcode file you were printing at the time?

-Kevin

[Hywelmartin]

I wasn't even past the startup gcode... and I printed the gcode after a restart..
ABS.rpi2-bottom_8020_netfabb.0.3.20181218-133355klipper0.6.gcode.txt

yesterday I got the same but that was on the famous ...... so the end code made it to go to high..(semi calculated) I add that as well
PLA.gnomademax3flatfingersml3(1).0.2.20181217-173245klipper0.6.gcode.zip

By the way I found an error in the "SET_DELTA_HEIGHT" gcode

G0 F4000 X0 YO Z10
instead of
G0 F4000 X0 Y0 Z10

Could it be it, but I have been running with that a while...

[KevinOConnor]

It looks like the g-code was in relative coordinate mode (G91) instead of the normal absolute mode (G90) at the time of the M112. If it was also in relative mode at the time of the print start then your G28, G0 ... Z10 sequence in SET_DELTA_HEIGHT would have commanded the printer up instead of down and Klipper correctly reported an error on the move (out of range move to Z=285.703). G-code is horrible to work with - you might want to add G90 commands to your macros and start scripts.

-Kevin

[Hywelmartin]

Thanks. I will do..

And have a merry x-mas