This is a great start, but is there any way to add a terminal so we can enter the changes to G-Code in the window rather than opening a code editor and saving?
So Iâve entered M600 properly. The printer stopped and allowed me to switch the filament which I did but how will it resume? It just stays in place once switching?
This was 2 colour changes manually added to the gcode, which is a little more obvious in profile (the ball at the top was printed separately and glued on):
Thanks to the Team for the new command, very useful.
I did modify a script for Ultimaker CURA.
Unzip the script file and save it in the folder âC:\Users\USER\AppData\Roaming\cura\4.9\scriptsâ (change the path to reflect the name of your âUSERâ on your computer).
Start or Restart CURA.
To use the script in CURA, go to âExtensionsâ then âPost Processingâ then âAdd a scriptâ. Select the script âFilament Change SnapMaker 2â in the list.
You can now enter the layer number at which the change(s) will occur (at the beginning of the layer).
You can enter multiple layers changes with a coma (,). For example you can set â5,10,15,30â to have 4 filament changes.
This is just a cleaning of unnecessary parameters in the original Ultimaker script, but I will add the possibility to change temperature in the next release, to print Multimaterials as it was my first use case and done it manualy.
Edit : Rewrite it all now that i have the possibility to attach files.
Interested in using the M600 but having not used VS Code before how do you get the Layer list column on the left and the G-Code in the column on the right, I just get the G-Code when I open it.
The layer numbering in Luban does not correspond with the layers in the G-Code. For starters, Luban starts with layer 1, G-Code starts with 0. If thereâs a raft, G-Code starts in negative numbers when Luban starts at 1. Even with a model with no adhesion assistance, Luban shows 5 or 6 layers less than are in the code. Can you explain the numbering system please.
Has anyone tried to do this recently? I had this working a few days ago, then it suddenly stopped working. The printer goes right past the M600 code without doing anything. Iâm not sure if itâs something Iâm doing, or the latest firmware. Anyone happen to know?
3x Sprit Tokens 62p.gcode (1.1 MB)
Would it be too much to ask you or someone to take a look at this bit of Gcode? I have tried like 10 times now and canât figure out what Iâm doing wrong. I thought I was onto something there for a bit - Notepad++ was inserting \n instead of \r\n for each new line - but Iâve made them match what is output by the Luban slicer and I still canât get it to pause.
Looks the same as your file. Are you sure your controller/heads are on the latest firmware? You might try a USB upgrade with the 3dp head attached (download the latest FW to USB, boot with the 3dp head attached, and select the file to upgrade) just to make sure. There was a release a while back that needed to upgrade the head firmware as well, and I canât remember if it prompted you to do anything if you changed heads. It also wouldnât work over wifi-had to be a local USB upgrade.
Possibly another thing to try-does your filament runout sensor work? Try cutting the filament off while printing and see if it detects the runout. Itâs distinctly possible that if the sensor is broken/not detected that the runout command wonât work.
I cannot seem to get the M600 command to work either. I have the latest firmware version of V1.13.2 and tried re-loading it via USB. I have confirmed that the filament runout sensor is working properly as well.
Iâve tried inserting the command into a few different Gcode files and also directly through the Luban command console. All other commands work as expected except M600 that it seems to completely ignore.
Any suggestions on what else to try? Maybe going to an older firmware version?
