MK2S queuing unwanted commands after M601 + M1 + M602
I'm trying to include a g-code pause to allow me to insert a washer into a cavity. Here's what I insert at the appropriate spot in the file:
G0 X50 Y200 ; Move to corner to allow part access.
M601 ; Pause.
M300 ; Beep.
M1 ; Pause for human. If using Octoprint, hit resume rather than knob.
M602 ; Restart where we left off.
G4 P5000 ; Some folks think a few seconds of dwell is useful...?
Here's what the transaction log looks like. Note that the printer is queuing up a bunch of commands I didn't send:
2018-01-27 15:52:36,725 - Send: N5155 M601*16
2018-01-27 15:52:36,749 - Recv: ok
2018-01-27 15:52:36,752 - Send: N5156 M300*23
2018-01-27 15:52:36,757 - Recv: ok
2018-01-27 15:52:36,759 - Changing monitoring state from 'Printing' to 'Paused'
2018-01-27 15:52:36,767 - Send: M400
2018-01-27 15:52:36,770 - Send: M114
2018-01-27 15:52:37,762 - Recv: ok
2018-01-27 15:52:37,978 - Recv: ok
2018-01-27 15:52:37,985 - Recv: X:50.00 Y:200.00 Z:2.60 E:77.02 Count X: 50.77 Y:201.16 Z:2.96
2018-01-27 15:52:38,000 - Recv: ok
2018-01-27 15:53:23,692 - Send: M105
2018-01-27 15:53:23,705 - Recv: ok T:215.0 /215.0 B:61.0 /60.0 T0:215.0 /215.0 @:63 B@:0
2018-01-27 15:53:27,399 - Changing monitoring state from 'Paused' to 'Printing'
2018-01-27 15:53:27,431 - Send: N5157 M602*17
2018-01-27 15:53:27,441 - Recv: ok
2018-01-27 15:53:27,446 - Send: N5158 G4 P5000*97
2018-01-27 15:53:27,519 - Recv: echo:enqueing "M104 S 0"
2018-01-27 15:53:27,523 - Recv: echo:enqueing "G90"
2018-01-27 15:53:27,527 - Recv: echo:enqueing "G1 X000.00 Y000.00"
2018-01-27 15:53:27,662 - Recv: echo:enqueing "M109 S 0"
2018-01-27 15:53:28,851 - Recv: echo:enqueing "M106 S0"
2018-01-27 15:53:28,860 - Recv: echo:enqueing "G1 Z000.00"
2018-01-27 15:53:28,864 - Recv: echo:enqueing "G1 E4"
2018-01-27 15:53:29,485 - Recv: echo:busy: processing
2018-01-27 15:53:30,000 - Recv: echo:enqueing "M220 S110"
2018-01-27 15:53:31,616 - Recv: echo:busy: processing
2018-01-27 15:53:32,453 - Recv: ok
2018-01-27 15:53:32,463 - Send: N5159 G1 X124.568 Y109.226 F7200.000*110
2018-01-27 15:53:33,483 - Recv: T:215.0 E:0 W:?
2018-01-27 15:53:34,486 - Recv: T:215.0 E:0 W:?
2018-01-27 15:53:35,485 - Recv: T:214.9 E:0 W:?
2018-01-27 15:53:36,490 - Recv: T:214.2 E:0 W:?
2018-01-27 15:53:37,488 - Recv: T:213.5 E:0 W:?
Is there a better way to pause? Is this a firmware bug? I'm running FW 3.1.0 and Octoprint 1.3.6.
Re: MK2S queuing unwanted commands after M601 + M1 + M602
If you check this page: https://github.com/prusa3d/Prusa-Firmware/wiki/Supported-G-codes (Prusa supported g-codes), M601 and M602 both say they are to be used to pause and resume SD card prints.
M601
Long pause
Suitable for pausing sd card print....
M602
Resume SD card print from long pause....
Perhaps not compatible when printing via USB.
-Kevin
Re: MK2S queuing unwanted commands after M601 + M1 + M602
Indeed - I read that but wasn't sure what to make of it.
Re: MK2S queuing unwanted commands after M601 + M1 + M602
So, what's the best workaround? Just run the code off the SD card?
Re: MK2S queuing unwanted commands after M601 + M1 + M602
I haven't experimented with this myself, but I'd try printing from the SD card.
-Kevin
Re: MK2S queuing unwanted commands after M601 + M1 + M602
So, what's the best workaround? Just run the code off the SD card?
Perhaps that: https://shop.prusa3d.com/forum/original-prusa-i3-mk3-f30/how-to-pause-and-resume-mk3-t14773.html#p70257