Unexpected filament change
Today I was surprised when my MK3 stopped about 40 minutes into a print job, expecting me to change filament. I just pulled the PLA filament out, reinserted it, and the job started up again.
The thing is, I didn't (intentionally) include a planned filament change. Is there anywhere I can look (gcode? slicer settings?) to find what caused this?
The project was a design from Fusion 360 exported as stl, opened in PrusaSlicer 2.4.1 with settings for 0.10mm Detail, PLA, 15% infill.
It sounds like a glitch from your filament sensor.
First make sure the cables are all plugged in securely.
If the problem recurs, temporarily disable your filament sensor (LCD menu) - it should then be OK but you have no run-out detection so work through the sensor and its connections until you narrow down the issue.
Cheerio,
RE: Unexpected filament change
Thanks!
RE: Unexpected filament change
Or at least equally like, you might have inadvertently clicked on the right-hand slider in the slicer preview and inserted a color change. Has happened to the best of us.
RE: Unexpected filament change
Going back to this issue, my MK3 is again pausing to change filaments when I didn't (intentionally) insert any such command.
I just looked at the gcode with a text editor, and I only see one instance of "M600" (color change command). This is near the end of the file in a line that begins with a semicolon (";"), so I assume that that is commented-out.
Based on the above, does it sound as though my problem is *not* with a color-change command mistakenly inserted into gcode -- but rather a hardware glitch with the filament sensor?
RE: Unexpected filament change
Agreed. Sounds like the sensor.