MK3s prompting for filament change after purge line
Hello Guys,
My new issue is pretty clear -hopefully- in the title.
My Prusa stops and asks for filament change right after finishing the purge line. Once I have proceeded with unload / reload, all goes back to normal, printing the file to the end.
At first, I added color changes myself by mistake (2) but deleted them but still.
I don't think it would come from any sensor issue (cables are in place, no change recently and issue only happening once at start.
Did I miss something in Slic3r ?
Thanks in advance for giving your thought on that one.
Cheers/Mike
RE: MK3s prompting for filament change after purge line
Turn off you filament sensor and see if it goes away. It is in your settings menu.
--------------------
Chuck H
3D Printer Review Blog
RE: MK3s prompting for filament change after purge line
@soapmaker
Save your project and zip it, the easiest way to get help.
https://forum.prusa3d.com/wp-content/uploads/2021/05/How-to-save-and-upload-a-project-1.pdf
Prusa i3 MK3S+ FW 3.11.0 (kit dec -20), PrusaSlicer 2.6.1+win64, Fusion 360, Windows 10
RE: MK3s prompting for filament change after purge line
You can look in your GCODE for a M600 code that triggers filament change. If it's in there, it's from somewhere in your slicer settings. As @ringarn67 said, you can upload the 3mf so we can check.
If not, I agree with @cwbullet, it could be filament sensor related but that wouldn't quite explain why it only happens after the purge line.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: MK3s prompting for filament change after purge line
Hello Guys,
Please see attached, I have open with Text and could spot indeed a M600 instructions even though I can find how it ended up there from Slic3r settings. Any help mostly welcome to avoid the issue from now on.
Best/Mike
RE: MK3s prompting for filament change after purge line
I looked through the gcode and there's nothing in your startup gcode that will insert the M600. The M600 appears as commented color change gcode which means it's been manually inserted into the print. Unfortunately, we need to see your 3MF project file to help with anything more as the gcode file only shows the results, not what causes it to be inserted.
Slice your print, then spend some time in preview mode examining the vertical bar at the right and see if there is a color change inserted. It will look something like this:
If you still need help, save your current 3MF project file in PrusaSlicer, zip it up, and attach it to a reply here so we can see your part & settings and give better recommendations. Without the actual project file, some settings are not visible, so it's very important that you actually provide the 3MF project file (saved PrusaSlicer project file).
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: MK3s prompting for filament change after purge line
@soapmaker
The GCODE file alone doesn't tell the whole story, can you save the project as a 3mf file, zip, and upload it as per https://forum.prusa3d.com/wp-content/uploads/2021/05/How-to-save-and-upload-a-project-1.pdf.
Just from looking through the GCODE file I suspect you still have a color change in the project.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: MK3s prompting for filament change after purge line
Okay, Bob just beat me to it as I was typing. This is the most likely explanation.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: MK3s prompting for filament change after purge line
@bobstro @fuchsr
Sorry I only inserted the gcode, now I (mostly) get the how and why’s 3mf are also important and how code get generated.
knowing it would come from Slic3r thanks to your posts, I have looked into it.
apparently I have firstly generated color changes by mistake which I have then cancelled before generating the gcode. Thing is the left color did not match the one I have set long ago as default filament color.
I guess this is why Slicer did generated a M600 command, logically !
Thanks because this has grown a bit further my slicer skills 😉
stay safe / happy printing !!