After 8 months of use, my first and really serious incident occurred. I print details to be used for my greenhouse and each run takes between 5 and 6 hours so the printer has been working around the clock.
I had a new run, which after a while stopped and the printer sounded like a stuck pig. The display showed "Maxtemp error" and the nozzle was pressed in the bed firmly.
For some unknown reason, the nozzle had been lowered and more or less started embossing the filament in the bed. The filament that is stuck in the bed can not be removed without the surface coating on the bed.
I had previously completed a run with the same gcode without any problems so there should be no error in the code.
The bed is broken but because there is no hardware failure, I do not think Prusa gives me a new bed on the warranty.
But what might have happened? Could it be due to an external disorder?
I have a Raspberry 3 with Octopi connected to the USB port but printing from SD card. Octopi, I only have video surveillance of the printout and it has never caused any printing problems. Firmware was 3.4.0 but was upgraded after the crash to 3.4.1.
A Self Test run was performed without a problem, but I have been unable to print anything more because I have not yet removed the embossed filament.
It might be interesting to hear if someone else has encountered this?
- Crash-2.jpg (468.26 KiB) Viewed 103 times
- Crash-1.jpg (410.16 KiB) Viewed 103 times
Happy owner of a Prusa MK3