# M600 manually injected pause for color change failures **URL:** \ **Category:** Snapmaker 2.0 (3-in-1)\ **Created:** [November 16, 2020, 9:49pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594 "2020-11-16T21:49:29Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![GloomhavenGamer](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@GloomhavenGamer](https://forum.snapmaker.com/u/GloomhavenGamer)\ **Post date:** [November 16, 2020, 9:49pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/1 "2020-11-16T21:49:30Z")
On Craftbot I’ve used the M600 command to manually inject pauses between layers for changing filament color. I tried the same thing on my Snapmaker 2.0 and found that when it gets to the pause it moves odd the bed and it ejects the filament just like I want. Unfortunately the buttons for loading filament don’t come up on screen and there is no “resume” button. It has a “pause” button on screen. If I push the pause at that point it just freezes and can’t recover. Any suggestions on how to do a hot swap of the filament on Snapmaker? ---
**Author:** ![brent113](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/brent113/32/11114_2.png) [@brent113](https://forum.snapmaker.com/u/brent113)\ **Post date:** [November 16, 2020, 10:07pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/2 "2020-11-16T22:07:24Z")
Yea, the resume features are not implemented unfortunately. That’s something I’m hoping to change in the firmware soon enough, but in the meantime I think your only option is to slice with S3D and use the multi-process wizard to generate separate files for each color. Possibly Cura has similar features. Anyone else have any ideas? ---
**Author:** ![ITmaze](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/itmaze/32/6225_2.png) [@ITmaze](https://forum.snapmaker.com/u/ITmaze)\ **Post date:** [November 16, 2020, 10:52pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/3 "2020-11-16T22:52:25Z")
I’ve just created an issue on my Firmware version for this, just so we can track what’s needed - and even hopefully apply patches to the SM firmware when it gets released 😉 [https://github.com/ITmaze/snapmaker-firmware/issues/2](https://github.com/ITmaze/snapmaker-firmware/issues/2) Feel free to add other issues to keep track. ---
**Author:** ![GloomhavenGamer](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@GloomhavenGamer](https://forum.snapmaker.com/u/GloomhavenGamer)\ **Post date:** [November 17, 2020, 1:40am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/4 "2020-11-17T01:40:20Z")
Thanks to both of you! I appreciate the responsiveness. I look forward to the change, I’ve got several multi tone projects I’m going to hold off on till this one is done. I’ll follow and wait for the patch. ---
**Author:** ![ITmaze](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/itmaze/32/6225_2.png) [@ITmaze](https://forum.snapmaker.com/u/ITmaze)\ **Post date:** [November 20, 2020, 11:41pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/5 "2020-11-20T23:41:58Z")
@brent113, did you see this reply: [https://github.com/Snapmaker/Snapmaker2-Controller/issues/6#issuecomment-730812691](https://github.com/Snapmaker/Snapmaker2-Controller/issues/6#issuecomment-730812691) ---
**Author:** ![brent113](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/brent113/32/11114_2.png) [@brent113](https://forum.snapmaker.com/u/brent113)\ **Post date:** [November 21, 2020, 12:48am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/6 "2020-11-21T00:48:27Z")
I did, I almost replied too. It’s a real problem. The serial buffer fills up, and then no new gcode commands, like a resume command, would be received. The issue originates in the original HAL implementation for the ST chips, and the ST USB interface apparently cannot have interrupts that would allow that to work. This GD chip implementation is different in that the USB to UART is external to the chip. If there’s an interrupt that can be handled from the UART then an ISR can be written to check if the command is for the EMERGENCY\_PARSER special functions. Or Something. I haven’t looked into it much. ---
**Author:** ![ITmaze](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/itmaze/32/6225_2.png) [@ITmaze](https://forum.snapmaker.com/u/ITmaze)\ **Post date:** [November 21, 2020, 4:01am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/7 "2020-11-21T04:01:42Z")
I’m not sure if I follow what you’re saying, but having a squiz through the source, it seems that M600 is linked to ADVANCED\_PAUSE\_FEATURE, as is, FILAMENT\_RUNOUT\_SENSOR. Bearing in mind that I don’t yet have my A350, there is discussion here[1] under 9.1.1 that the SM has a Filament Runout Recovery. [1] [https://support.snapmaker.com/hc/en-us/articles/360041733553-Snapmaker-2-0-3D-Printing-V1-0-0](https://support.snapmaker.com/hc/en-us/articles/360041733553-Snapmaker-2-0-3D-Printing-V1-0-0) Which makes me think that even if there was a serial buffer issue, there must be something in the filament runout process that’s dealing with that. Still digging … ---
**Author:** ![brent113](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/brent113/32/11114_2.png) [@brent113](https://forum.snapmaker.com/u/brent113)\ **Post date:** [November 21, 2020, 4:03am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/8 "2020-11-21T04:03:59Z")
The filament runout doesn’t use serial… that comes over CAN. Basically this bugfix PR needs to be modified for the GD using not USB and merged into HAL > ---
**Author:** ![GloomhavenGamer](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@GloomhavenGamer](https://forum.snapmaker.com/u/GloomhavenGamer)\ **Post date:** [February 26, 2021, 5:28pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/9 "2021-02-26T17:28:30Z")
I just checked and saw that the bug report was closed back in November. I saw there is a new version of the firmware, but it doesn’t mention fixing this issue, and I didn’t see anything in the bug report notes. Has this been fixed then? ---
**Author:** ![Caleb](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@Caleb](https://forum.snapmaker.com/u/Caleb)\ **Post date:** [March 22, 2021, 4:11am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/10 "2021-03-22T04:11:24Z")
> [@ITmaze](#): > > just created an issue on my Firmware version for this, just so we can track what’s needed - and No it hasn’t, i tried this same thing and had the same issue, the only i got it to work was to print to the m600 then change the filament then cancel the print modify the gcode file with notepad++ as if I was doing a restore a failed print and upload the new gcode file with everything before the m600 deleted then make sure that before the first print line i move the nozzel to the correct z with g1 to the correct z height. ---
**Author:** ![ctaddey](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ctaddey](https://forum.snapmaker.com/u/ctaddey)\ **Post date:** [March 22, 2021, 1:05pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/11 "2021-03-22T13:05:08Z")
You can cut the filament and feed the new color without even triggering the runoun sensor. It’s not layer-precise but it works… /Edit Sry, I meant to reply to the OP. ---
**Author:** ![buzzplop](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@buzzplop](https://forum.snapmaker.com/u/buzzplop)\ **Post date:** [April 17, 2021, 11:09pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/12 "2021-04-17T23:09:09Z")
It looks like this feature has made it into the next release ---
**Author:** ![Caleb](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@Caleb](https://forum.snapmaker.com/u/Caleb)\ **Post date:** [April 25, 2021, 7:32pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/13 "2021-04-25T19:32:45Z")
> [@buzzplop](#): > > his feature has made it into the next rele Sweet I will keep my eye out for that. Thanks ---
**Author:** ![Edwin](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/edwin/32/13481_2.png) [@Edwin](https://forum.snapmaker.com/u/Edwin)\ **Post date:** [April 27, 2021, 6:30am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/14 "2021-04-27T06:30:41Z")
Yep, `M600` will be enabled in next version of firmware. > > > M600: > Parameters：None EDWIN ---
**Author:** ![cbardon](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/cbardon/32/6204_2.png) [@cbardon](https://forum.snapmaker.com/u/cbardon)\ **Post date:** [April 27, 2021, 1:06pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/15 "2021-04-27T13:06:29Z")
Neat-so I’m guessing you’d either have to manually insert this, or use the “pause at layer” cura plugin? ---
**Author:** ![buzzplop](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@buzzplop](https://forum.snapmaker.com/u/buzzplop)\ **Post date:** [April 27, 2021, 3:54pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/16 "2021-04-27T15:54:23Z")
This feature is working now. SuperSlicer and PrusaSlicer insert the M600, and the machine pretends to run out of filament to let you load some other filament. It’s a shame the touch screen does not understand that its just seen an M600 so it appears like a filament runout event, but, at least it works. Its up to the slicer to adjust nozzle temp, so initially its best to use a material that you would print at the same temp. SuperSlicer lets you insert custom GCode, so you _could_ modify the nozzle temp straight after the M600. Or, of course, you could adjust the nozzle temp on the touch screen. I would advise to watch print speeds though, the machine stops quite abruptly which _may_ throw the Y modules of alignment ---
**Author:** ![dbvanhorn](https://avatars.discourse-cdn.com/v4/letter/d/58956e/32.png) [@dbvanhorn](https://forum.snapmaker.com/u/dbvanhorn)\ **Post date:** [April 27, 2021, 7:21pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/17 "2021-04-27T19:21:06Z")
Would this be related to why I’ve never had a print where resuming (after manual pause on the touchscreen) actually worked? It sort of works, but it seems that a number of print commands are skipped, and the resumed print does not stick to the part from before the pause. ---
**Author:** ![buzzplop](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@buzzplop](https://forum.snapmaker.com/u/buzzplop)\ **Post date:** [April 27, 2021, 7:39pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/18 "2021-04-27T19:39:33Z")
Hmm, don’t know about that, the times I have used pause / resume it has worked ---
**Author:** ![buzzplop](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@buzzplop](https://forum.snapmaker.com/u/buzzplop)\ **Post date:** [April 27, 2021, 9:26pm UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/19 "2021-04-27T21:26:59Z")
I was wrong, I thought the touchscreen maintained the previous filament temp after a change. It does not, it seems to maintain the temp set when loading the new filament, which by default is 200. This is annoying. Means either custom GCode to set the nozzle temp after the M600, or an extra interaction with the touchscreen to set the correct temperature again. ---
**Author:** ![Edwin](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/edwin/32/13481_2.png) [@Edwin](https://forum.snapmaker.com/u/Edwin)\ **Post date:** [April 28, 2021, 6:34am UTC](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594/20 "2021-04-28T06:34:03Z")
Thank you for your reminder. I tried to use `M600` to change the filament and then resume. The current temperature in Snapmaker Luban console is still 205℃ while the one on the touchscreen is 200℃. #### Snapmaker Luban console ![image](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/2X/9/9e3cfc7c655f5b2908f719f663cdbb9427768871.png) #### Touchscreen ![image](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/2X/b/b6fc48782f5729b87a88ce7e084e646768333c62.jpeg) I have reported this issue to our software developer. This issue is likely to relate to the touchscreen. Best regards Edwin [Next page](https://forum.snapmaker.com/t/m600-manually-injected-pause-for-color-change-failures/11594.md?page=2)