@DougJoseph thanks, that really helped me!
Iāll give it a tryā¦
PS for unload the filament Iāll just have to pull it out manually?
@DougJoseph thanks, that really helped me!
Iāll give it a tryā¦
PS for unload the filament Iāll just have to pull it out manually?
Thatās what dcarpenter65 was suggesting, yes.
Sure, no problem, while the printer is printing, you have the option to press either pause print or stop print on the touch screen. Use the pause button, once the printer stops and goes to the home position, open the latch on the front of the print module, pull the filament out of the top of the module, remove the spool and replace it with whichever color you want to continue printing with, insert it inside and close the latch, press continue on the screen and once the previous color filament is out of the nozzle, youāll start to see the new color! Enjoy!
Dave Goliath
[dave.goliath65@yahoo.com](mailto: dave.goliath65@yahoo.com)
I also use octopi + cura pause at height plugin method for filament color change at my snapmaker 2.0. However, sometimes, there is an unintended filament mass ejection from the first starting point of the layer to be changed. So, it fails to print a layer using letters that need to maintain some precision. As a convenience, I use prints the decoy object together and starts printing from there. According to the findings, if filament is replaced by filament run-out in snapmaker and resumed, extruding about 10mm and printing starts. If you have a solution to this problem or have experienced.
Interesting thread-is there any reason the pause/resume isnāt supported natively by the SM firmware?
If you try this as two separate jobs, is there a reason that I canāt just take the gcode and manually divide into multiple files? Similar to using the āpause at layerā, but instead of the unsupported pause command, make that end the job, then change the filament, then start a new job with the rest of the gcode?
I know that it is very difficult to output to another gcode file after completing one task.
I know that this is because slicer does not remember the absolute position and uses a lot of gcode that uses the relative position during output. I donāt know if Iām misunderstood
@soubim
Hi, you can make posts now. Sorry for the inconvenience.
Best regards
Up to now when I want to change Filament I simply hang around to watch the percentages where I think it needs to occur and I simply cut the filament before it gets into the extruder an inch or so back and then the automatic fulfillment run out feature kicks in and I simply wait for that to cycle to begin and Iām onto my new color.
I canāt wait till the firmware is upgraded to allow us to use the M600 GCode.
Itās available now in the latest firmware
I read through the forum looking for specific instructions so I figured Iād post them here. In case anyone is curious. I verified that the M600 command triggers the filament runout subroutine in the Snapmaker allowing you to unload and load filament into the machine without having to worry about modifying gcode manually. Simply load an addon with Cura. It avoids having to monitor your print, clip filament, etc. and it parks the head automatically in a safe place in case you walk away from your prints (not that any of us would do that). Hereās the easy way: Using Cura slicer (if you donāt have Cura, these instructions are useless to you as Snapmaker Luban doesnāt implement post-processors):
If Cura is new to you and you want to save directly to the Snapmaker youāll need the Snapmaker2Plugin from the Cura Marketplace.
If you have Luban, you can use any gcode editor to find the layer and insert the M600 command to achieve the same thing.
Click Please note that the head and the bed will remain at temperature.
No, I just end up cutting the filament, letting it run out, and then putting the new filament in.
Works well enough.