Logs? Failed print
It happened overnight on a long print. I was using the USB port, not network, nor wifi. The screen showed a heater shutdown due to inactivity then "Filament successfully unloaded?' There were no filament changes in the print. There was plenty of filament on the reel. Near as I can tell, for some reason it tried to unload the filament and then the extruder cooled down and the filament was stuck due to a small nib on the filament. I could not remove it and had to take the extruder apart to get it out. I learned something, so all good on the extruder, but would like to understand what happened. If there is a log file on the USB I can review once the current print is finished. May wire up the network.
Unintended color change
Reviewing the gcode revealed that despite it being a single-color single-extruder print, there was an unintended color change right where it stopped.
RE: Logs? Failed print
The printer also doesn’t write logs, I don’t know where to dig
🌠qrmagazin.ru
RE:
This issue happens usually due to wrong signals from the side filament sensors. The printer thinks that the filament has run out and expects you to load new filament. Maybe take the side filament sensor apart, clean it carefully with airpressure and run the side filament sensor calibration again. If the issue is still comming up you should check with Prusa if you are still covered in waranty and replace the side filament sensor.
Had the same issues. Cleaning helpt for some time but by the end the side filament sensor was the main issue.
there was an unintended color change right where it stopped.
This is usually a miss-click on the slicer preview page, or perhaps a stutter when scrolling through - play with the scroll bar on the right to get used to spotting them.
Cheerio,