Thermal calibration fails 3.12.2
I've just upgraded the firmware to 3.12.2 from a pre-thermal model firmware and I can't get it to calibrate. It fails on the refining C est. stage.
My printer is totally stock with the exception of a hardened nozzle. I replaced the hotend with a genuine replacement from Prusa a few months ago (due to snapping a wire of the heater cartridge during a nozzle swap) and it has been printing flawlessly before and since.
I don't think there's anything at all wrong with my printer.
The only thing I can think of is that it's in a workshop that's not heated and is usually around 17°C but I can't bring it into the house.
Is my only option to downgrade the firmware or an I missing something?
RE: Thermal calibration fails 3.12.2
I've been underwhelmed with the whole thermal model. I'm all for improving safety but too many perfectly fine working printers seem to get disabled with a model that appears to be too zealous. The Mk3S - unlike the Mini - at least has a way to disable it. Please check the release notes for the gcode you need to send to disable it.
RE: Thermal calibration fails 3.12.2
Here's the instructions they're giving folks submitting bugs on GitHub.
You can disable the thermal model by sending G-code
M310 S0
followed by
M500
to make it permanent.
Aaron
RE: Thermal calibration fails 3.12.2
Thanks for the replies. I decided to downgrade to 3.11 and I'm back to happy printing.
I'll wait for the thermal model to mature a bit more before upgrading. I've been able to rely on firmware updates to be flawless up to now. I guess they're trying something with good intentions but rolling it out before it's ready.
RE: Thermal calibration fails 3.12.2
I upgraded to Revo at the same time as 3.12.2 because it "supposedly" solves Revo problems. Thermal calibration ran maybe 5 seconds before an error. Downgraded to 3.11 and all works fine. Revo definitely heats faster than stock.
You know, if they are going to release 3.12.2 as BETA, it should say BETA. This software is definitely not ready for prime time.
RE: Thermal calibration fails 3.12.2
I've got a Mosquito and I dropped back to 3.11. It's stable and it works.
There's another problem too, that I hope isn't unique to me, but it's that the M112 error now sounds a continuous alarm. As in, it doesn't go away until you acknowledge it. I only get these when my printer is idle and at room temp, so you can imagine how fun it is to be woken up early in the morning to hear this sound.
I just hope they can sort out this firmware to work in the future.
Aaron
RE: Thermal calibration fails 3.12.2
I just upgraded to 3.12.2 and I am unable to complete thermal calibration. Hotend is the Revo 6
RE: Thermal calibration fails 3.12.2
I suggest that you downgrade to 3.11 and wait for a revo proof version of the new firmware
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Thermal calibration fails 3.12.2
it's not just about being Revo proof. But wasn't the whole concept of Prusa an open source printer? This thermal model protection is locking people into specific hardware unless they disable it through gcode commands. this feature is an alpha at best. And if it's only going to work on specific hardware, rather than working like PID tuning, where it tunes to the hardware, then there should be a menu setting to disable it, not through gcode.
RE:
it's not just about being Revo proof. But wasn't the whole concept of Prusa an open source printer? This thermal model protection is locking people into specific hardware unless they disable it through gcode commands. this feature is an alpha at best. And if it's only going to work on specific hardware, rather than working like PID tuning, where it tunes to the hardware, then there should be a menu setting to disable it, not through gcode.
I agree. And even more, this is not some random hotend from some unknown company. This is an upgrade hotend made by the company that has been suppling hotends for "stock" PRUSA 3D printers for years. You would THINK, if PRUSA was going to modify the FW that would BREAK the REVO, they would have the courtesy to work with E3D to get it working BEFORE this firmware was even released. The fact that they didn't tells you a lot about where PRUSA is now.
And nobody has yet to tell me what this firmware achieves. Why was it SOOO important to release?
RE: Thermal calibration fails 3.12.2
And nobody has yet to tell me what this firmware achieves. Why was it SOOO important to release?
That's a very valid question.
RE: Thermal calibration fails 3.12.2
I have been using the Revo nozzles without any problems (multiple sizes) for several months without problems. As soon as I flashed 3.12.2, I had the same failed thermal calibration issue! Tried entering the G-codes suggested by @extra-fox. Those seemed to make the fan run at 100% all the time. So back to 3.11 and all is working just fine again. If you have a Revo nozzle, I DO NOT recommend upgrading to 3.12.2. Not sure about the other 3.12.x releases as I didn't install them. Now if I could just get rid of the annoying message on the LCD to upgrade to 3.12.2!
RE: Thermal calibration fails 3.12.2
look in the
Printer Settings Custom Gcode, Start Gcode
there should be a line, something like this
M115 U3.12.2 ; tell printer latest fw version
Delete this line
and save the profile as a new name
say
Original Prusa i3 MK3S & MK3S+ - No Firmware Nag
Then use that profile in the future. ~
Regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Thermal calibration fails 3.12.2
Thanks Joan. I did figure that part out.
But maybe the bigger question? Why did Prusa suddenly feel the need to release firmware for a 5 year-old printer that breaks a very popular third-party upgrade (Revo) coincedentily at the same time Prusa just happens to be releasing their own competitive upgrade in the form of a MK4 "upgrade" kit. Now you might say, Prusa wants the firmware to work with their upgrade, and that is fine. But if you DON'T have their MK4 upgrade, they should deactivate the part of their firmware that breaks Revo. Otherwise, to me, it looks very petty and self-serving.
RE: Thermal calibration fails 3.12.2
Prusa has a good record, I'm sure they will fix it. What you are saying is a bit of a conspiracy theory.
RE: Thermal calibration fails 3.12.2
I recently upgraded to 3.12.2 as well and have made more print failures than ever before. The last one completely fouled my extruder. No biggie, I will just install my Revo 6 that I have been sitting on for the last two weeks. So now I am not even at the custom G-Code stage yet. I can't even try and load filament into the Revo 6 because I immediately get an error about temperature anomalies. So I try to a PID calibration but it seems to do the same thing most others are saying. It jumps up to 35C and then shuts off the heater. This is where it stays. It is stuck on step 0 of 5.
Now what? Go back to 3.11 and do the PID calibration there? What's the consensus?
RE: Thermal calibration fails 3.12.2
that's twice now... thermal fails with my revo... getting rather sick of this crap
RE: Thermal calibration fails 3.12.2
I went back to firmware 3.11 and the revo works with it. Good enough for me! 🙂
RE: Thermal calibration fails 3.12.2
Yeah, coincidently Prusa now has their own quick-change hotend, so they "upgraded" their firmware so the competitor product no longer works. But don't fear they are "working" on fixing it.
RE: Thermal calibration fails 3.12.2
Yes, "they upgraded" their open source firmware and "forced you to install it", right. 🙂
The revo works just fine with firmware 3.11 that the upgrade instructions by e3d tell you to use right at the top.