Unplanned filament changes???
Running a 90-odd hour print (0.05x0.4 in PLA) and just after the 48h remaining mark the print stopped for a filament change as if a M600 was in the gcode. Roughly 40 minutes later (though I hadn't noticed for awhile) it did it again.
The filament isn't jamming, the printer isn't making any odd noises to suggest problems, and there are no M600 codes in the gcode (just double checked). In now occurs to me that I should have paid attention to the Z value to go look at that layer specifically...
I generated it from Slic3rPE with nothing special (Generic PLA, 0.05 height, 0.4 nozzle, 15% Gyroid infill, no supports). I have no custom scripts set up and did no post processing of the gcode.
When it pauses it acts exactly like a M600 would (press button to eject, press button to load, confirm load, restart print).
The filament is Amazon's yellow which turned out to be a bit on the translucent side, but it ran ~40 hours up to that point (plus another 2 hour print prior to this one with the same filament) with no issues. It's been running various 1-4 day prints with the same settings for a couple weeks now with a mix of Inland and Amazon PLAs without experiencing this issue.
Anyone have any idea what might be going or other codes that act similar to M600 that I can look for (to see how many more times this might happen)?
Re: Unplanned filament changes???
You don't mention which printer model you are using. If you are on a MK3 with the direct optical filament sensor it my be getting confused and thinking that it ran out of filament and is prompting you to start a new spool. Try turning off the filament sensor for that filament. (I've had to do that for some of my filaments before I applied the MK3S modification.)
(The indirect sensor mods on Thingiverse (et. al) and the MK3S modification all are to resolve this issue.)
See my (limited) designs on:
Printables - https://www.printables.com/@Sembazuru
Thingiverse - https://www.thingiverse.com/Sembazuru/designs
Re: Unplanned filament changes???
Just did it again after about another 40 minutes (this is shaping up to be a long 46 hours 🙁 )
Noted the Z position this time and checked the gcode, but don't see anything out of the ordinary:
$ grep -nr ';37.25' yellow\ 1_0.05mm_PLA_MK3.gcode
2425898:;37.25
2425906:;37.25
$ grep -nr ';37.3' yellow\ 1_0.05mm_PLA_MK3.gcode
2430191:;37.3
2430204:;37.3
2434580:;37.35
2434594:;37.35
$ sed -n '2425898,2430190p;2430191q' yellow\ 1_0.05mm_PLA_MK3.gcode > temp
$ cat temp | cut -d" " -f1 | sort -u | grep -v ";"
G1
G92
M204
M73
Here is the full list of gcodes in the file:
$ cat yellow\ 1_0.05mm_PLA_MK3.gcode | cut -d" " -f1 | sort -u | grep -v ";"
G1
G21
G28
G4
G80
G90
G92
M104
M106
M107
M109
M115
M140
M190
M201
M203
M204
M205
M221
M73
M83
M84
M900
Re: Unplanned filament changes???
You don't mention which printer model you are using. If you are on a MK3 with the direct optical filament sensor it my be getting confused and thinking that it ran out of filament and is prompting you to start a new spool. Try turning off the filament sensor for that filament. (I've had to do that for some of my filaments before I applied the MK3S modification.)
(The indirect sensor mods on Thingiverse (et. al) and the MK3S modification all are to resolve this issue.)
It is the MK3, sorry.
The filament sensor is one of the things I thought about, but why start this 40 hours into a print? It's also never given me trouble with any other light or translucent color before.
Argh... Just did it again, but now it says my Z is lower than where it was the last time it stopped (35.55 vs 37.25)?? Same gcodes as shown above though, so nothing interesting there. That was only about 15 minutes of print time 🙁
I just turned the sensor off, so we'll see if that helps.
Re: Unplanned filament changes???
So I turned the filament sensor off and it ran for 2 hours without any more change prompts.
Because I like to know things, I turned the sensor back on and it has since run for 1.5 hours without prompting for a change.
So I still don't know if it is the sensor or not. When/if it fails again though I'll leave the sensor off again until either it stops or the print finishes.
Re: Unplanned filament changes???
Well it ran through the night (about 16 hours at this point) with the sensor turned back on and it's still. Will see what the next 24 hours holds I guess...
Re: Unplanned filament changes???
So it did another 10 hours and then stopped late last night with 15 hours left. Turned the sensor off again and it just finished the print.
Annoying, but behind me now I guess.