M600 entry at the beginning of the print

[bronsn]

OrcaSlicer Version

1.8.0

OS version

Windows 11

Additional system information

No response

Printer

Ender 7 / K1

How to reproduce

Setup a print File, add a second or third Filament, add at a specific layer height the Filament Change and slice the Objekt.
If i check the sliced gcode, there are 3 M600 Entry´s in the Code, 2 are correct but every time the Slicer add the M600 at the beginning of the Code so the printer stop with M600 after the Start Code

I have to manaally delete the M600 Entry in the Gcode.

Actual results

M600 at the beginning of the print

Expected results

M600 only th this point i added it in the slicer

Project file & Debug log uploads

?

Checklist of files to include

• Log file
• Project file

[ajbergelin]

I have this exact same problem as well.

[staal54a]

I am also seeing this issue

[Eldenroot]

Confirmed

[saxxonian]

same here, all M600s work well, except that one appears at the beginning of the actual print sequence.

[samiresa]

Ender 3V2 can confirm it is happening for me as well, removing the fist m600 via notepad modification.

[dral3x]

Same issue. I'm using the latest version of Orca Slicer on a Sovol SV06.

[SwineFlew931]

I have been manually deleting the first M600. Sometimes i forget (it's that problem of being human). But this is so annoying that I am looking at learning Python just to hopefully write a post processing script to remove it. It seems a check box for an option to include/exclude that first change would solve the issue and give people with AMS/MMU units as well as manual change folks the power to configure it as they need.

[dral3x]

I think it's related to the "Manual Filament Change" option, introduced in #2379.

If your printer (like my Sovol SV06) support just one filament, you have to turn ON that option in your printer profile.
After that, the M600 is not added anymore at the beginning of each print with multiple colors, but only on the layers in which you set the color switch.

[borisb74]

I think it's related to the "Manual Filament Change" option, introduced in #2379.

If your printer (like my Sovol SV06) support just one filament, you have to turn ON that option in your printer profile. After that, the M600 is not added anymore at the beginning of each print with multiple colors, but only on the layers in which you set the color switch.

Can confirm. After enabling the option for "Manual Filament Change" under Machine -> Multimaterial, the initial M600 is not in anymore. OrcaSlicer is version 1.8.1.

[SwineFlew931]

I think it's related to the "Manual Filament Change" option, introduced in #2379.
If your printer (like my Sovol SV06) support just one filament, you have to turn ON that option in your printer profile. After that, the M600 is not added anymore at the beginning of each print with multiple colors, but only on the layers in which you set the color switch.

Can confirm. After enabling the option for "Manual Filament Change" under Machine -> Multimaterial, the initial M600 is not in anymore. OrcaSlicer is version 1.8.1.

It was there the whole time face->palm.

Thank you @dral3x for pointing that out.

[DBT85]

@dral3x thank you so much for that. I've only just started doing multi colours on my Ender 3 but having to strip the extra M600 after prime line out was a pain. Hopefully anyone else suffering the same issue will find this answer too!

[manferlo81]

Thank you @dral3x, @DBT85, @borisb74 , @SwineFlew931. I have the "Manual Filament Change" on but it still happening to me. I will attach a test project I put together really quick for a different issue but as it turns out it has an M600 at the beginning.

M600 String Issue.zip

[chuckkay]

Update: next time i will sift through the comments more....
#Can confirm. After enabling the option for "Manual Filament Change" under Machine -> Multimaterial, the initial M600 is not in anymore. OrcaSlicer is version 1.8.1.

..........
confirmed this is a problem... even especially when i am only doing a single filament print
for me problem goes away if:
1 - i remove M600 from "Change Filament G-Code" in settings
or
2 - I remove all filaments except the one im using from slicer window (between bed type and process)

both are not optimal solutions, as i will want to do color swaps on some jobs, and don't want to have to mess with adding gcode or remembering option 2, ALSO the Print Pauses in the very beginning, I guess to make sure you have the right color loaded first.. but with out some sort of message that says load Blue... sort of silly, considering most people will load the filament before hitting print..

Anyway DEFFINETLY A BUG, because im only printing with one color, yet the M600 is sent at the beginning of the print.... Just because the slicer has some other filaments loaded in the filament viewing window ((between bed type and process)

do you know how long it too for me to figure out that this was the problem and this was the solution

[Eldenroot]

Prusa slicer maybe fixed this in the 2.7.2 version?

I am not sure. Anyway this is not good for nonAMS users.

@SoftFever please could you reply if it is somehow fixable?

[samiresa]

This is how I fixed my issue, I think it is a bug, but this is a work around.

[vgdh]

It's not a bug.
If you're changing the filament automatically, it's essential to include 'M600' at the beginning of your G-code.
Without this command, your printer will continue using the last filament loaded.
Therefore, when manually changing the filament is chosen, the slicer won't include 'M600' at the start since it's your responsibility to ensure the correct filament is loaded into the machine.

[github-actions]

Orca bot: this issue is stale because it has been open for 90 days with no activity.

[github-actions]

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.