M112 called after upgrade to 3.12.2- coincidence?
Hello Prusa Community!
I've had years of painless printing on my updated Mk3 till yesterday. I updated the firmware to 3.12.2 and the first print failed with an M112 error. It was a large (8+ hours) print. I tried again thinking it was an anomaly but it failed again - M112.
I printed a Benchy test without issues.
I tried again with the large print but it too also failed - M112. See screenshot of my OctoPrint temperature screen. I don't see a temperature anomaly. I've never seen this issue with the printer till I updated firmware. Is this just a coincidence or could there be something wrong with the printer?
I noticed on the interweb that it could be a power problem to the bed. A possible intermittent break in one of the power conductors after years of back and forth. I'll take a look tomorrow but has anyone else noticed this after firmware update?
Thanks in advance for all the help.
Cheers,
Alan
Calgary, AB
Which firmware did you upgrade from?
Cheerio,
RE: M112 called after upgrade to 3.12.2- coincidence?
That is a good question, Diem. Sorry but I am not sure. I tend to keep the printed up to date but I could have been one or two revisions old. Certainly not older than that.
Thanks,
Alan
RE:
Yesterday, I updated my MK3S+ from 3.12.2 (to confirm) to 3.13.2 and same happened to me. Before the print, I was trying to do the thermal calibration but it failed, so I decided to deactivate the Thermal Protection with M310 S0 & M500.
After rebooting, I tried last night to do a 7 hours print and I found this morning that an M112 was raised and the print failed at 2:17 am with "HEATBED THERMAL RUNAWAY". First time that this happened to me...
I have an MK3S+ with E3D Revo and Octopi.
I will rollback the firmware to 3.12.2 and try to print again.
RE: M112 called after upgrade to 3.12.2- coincidence?
Wow, I just rollback and now the bed is not heating any more...
RE: M112 called after upgrade to 3.12.2- coincidence?
Finally, after talking with Prusa support and some continuity checks, I found that the GND cable from heatbed was broken, the printed lock for the cables cut a little bit the cable and with the time started to fail...
The firmware update is innocent this time