We are at Luban V4.1.4. I am assuming it has not been implemented yet. Do you know when it will be scheduled or do we need to go outside of Snapmaker using other tools like Octoprint to do this?
M600 is already supported in the firmware. It triggers a filament runout event so you can swap in a new colour. I don’t know how it works in Luban, but it works in Prusaslicer just as it does for my prusa machines. M600 support was added in firmware 1.12.1.
I was working several things back in may 23, M600 Advance -Pause doesn’t work in the current version. I am using the Dual Extruder changing the filament for both sides it ONLY works for the LEFT extruder. gives you some flexibility but also limits you, since all filament changes need to on the left only.
That sounds like a good ticket Support Ticket Form
So they can fix it in firmware.
I’ve used M25 to pause the human machine interface with my dual-extruder module: https://snapmaker.github.io/Documentation/gcode/M025
M76 also works - I believe it is identical.
This worked for me. Use a text editor to edit the .gcode file. Go through and place M76 on it’s own line at the lines of gcode where you need a pause. If you used PrusaSlicer and set a color change at the layers you needed, then it’s simpler. Using the text editor, “Find” all of the M600 commands and place M76 on the next line, on it’s own, after every M600 command or just replace the M600 with M76. Either way, the print will pause and the toolhead will park. You must manually replace your filament then resume the print.
It was cool working the problem because it brought me back to my days of DOS 1.1 and programming in BASIC. (Beginners Allpurpose Symbolic Instruction Code) 1984 was a long time ago and George Orwell was running late.
I’m still trying to figure out how to use both of my extruders. PrusaSlicer is generating bad code when employing both extruders. It causes file parsing to fail.
You will find this useful:
https://wiki.snapmaker.com/en/Snapmaker_Luban/manual/2_supported_gcode_references
In Prusaslicer, you can just change the “Pause print g-code” in Printers > Custom G-Code. There should be no need to do any post processing.
I noticed this too, but only when printing from the screen.
If you use octoprint, it works fine.