Uncommanded Filliment Change
I downloaded a simple model and loaded the .STL file into the newest version of Slic3r. Only one color on the model. The modele was sliced and I exported the g-code onto an SD card. While printing the model, with white colored filliment on the MK3, the build would stop every 3-5 minutes, and demand a filliment change. This became very annoying after 3-4 hours because the MK3 beeps until you do the filliment change.
1/. Why did the g-code demand a filliment change when there is only one color in the model?
2/. Can I edit the g-code to remove the command? If so, what do I search for?
3/. Did Slic3r inherit the command from the .STL file?
4/. Is there a way in Slic3r to ensure only one color is in the g-code?
Any help or insight is appreciated. Thanks.
Re: Uncommanded Filliment Change
Turn off the filament sensor.
Search the forums for the recent posts regarding unwanted filament changes.
Re: Uncommanded Filliment Change
@lynol.a
Is this happening with an MK3 or an MK3S?
I have been looking around the forum for different things and have noticed
mention of this issue (in different forms) several times.
Is this a filament sensor issue with the newer MK3S?
I like the idea of a sensor to detect this situation but normally I am on top
of things while printing and if Im close to running out I typically switch spools
before a print.
Re: Uncommanded Filliment Change
MK3, mostly. There are several MK3 filament sensor issues. One is color sensitivity: white is one of the problem colors for the laser based motion sensor. Another is a what I am guessing to be a race condition in the firmware where the filament sensor trips, causes a pause for filament change, and clears interrupts that other processes have set, leading to print resumption at an incorrect location.
The MK3S sensor is immune to color and less prone to false readings, but there are still a few reports of "odd things" happening with it.