Filament Runout
I had an issue today where the print ran out of filament, I fed through new filament of the same type and brand, and started the print back up. I didn't notice it right away but at some point it changed the temp to 170 and never changed it to running temp.
RE: Filament Runout
Went for it a second time. The printer stopped, purged a bunch of material through the nozzle and onto the part, then continued printing as if it had material at all. All it had was the bit left in the hot end. Sigh.
RE: Filament Runout
Had another runout last night. This was a print that came from Octoprint. I'm not sure what the printer actually did, but I am sure that when I woke up, the printer was cooled down completely and on the main screen. Currently with octoprint, anything that happens outside of normal, the printer UI just plays dumb and shows nothing. I don't want to chalk this up to an octoprint issue though because of all the previous runouts I mentioned earlier in testing.
RE: Filament Runout
Is this the same print? If so, it may be worth uploading the file so it can be looked at. Almost sounds like something is wrong in the g-code and I am new to this.
RE: Filament Runout
No.
Is this the same print? If so, it may be worth uploading the file so it can be looked at. Almost sounds like something is wrong in the g-code and I am new to this.
RE: Filament Runout
Since you are using Octoprint, I wonder if is an issue with it. Might be worth running a small test with a short piece of filament and see what happens. Run the same gcode off the the SD card to find out where the change comes from. I don't use Octoprint yet.
RE: Filament Runout
The MK4 firmware doesn't support host communication (octoprint) at the moment. It runs similar firmware to the prusa mini and to activate the host communication on the mini you pass gcode "M876 P1". That same gcode isn't supported with the MK4 so there's no way to enter host communication. This means that filament run outs, M73 progress, M117 commands (and probably more that I haven't tested yet) don't get communicated. I'm interested to see if crashes are detected or if the printer simply continues printing.
RE: Filament Runout
Yeah I've tested all that as well. As far as crashes are concerned, I haven't had one yet.
The MK4 firmware doesn't support host communication (octoprint) at the moment. It runs similar firmware to the prusa mini and to activate the host communication on the mini you pass gcode "M876 P1". That same gcode isn't supported with the MK4 so there's no way to enter host communication. This means that filament run outs, M73 progress, M117 commands (and probably more that I haven't tested yet) don't get communicated. I'm interested to see if crashes are detected or if the printer simply continues printing.