CORE One bed thermal runaway
Today on v6.40.0 firmware I got very unpleasant crash. The printer restarted and red screen appeared with a bed thermal runaway error. As I saw on a graph the bed temperature went don't from 115C to 108C for no reason when printed with PC CF. Room conditions were the same. Also I was unable to exit the screen and then was unable to recover my print after a restart. That was very disappointing, taking into account the price of PC CF filament.
RE: CORE One bed thermal runaway
yes, the whole "Runaway!" topic screams "Amateur!" in all-caps.
"Runaway" usually refers to a self-accelerating process that cannot be brought back under control. In Prusa language it translates loosely as "ummm looks like our control loop error is larger than we've been hoping for. Let's just crash the print.".
RE: CORE One bed thermal runaway
yes, the whole "Runaway!" topic screams "Amateur!" in all-caps.
"Runaway" usually refers to a self-accelerating process that cannot be brought back under control. In Prusa language it translates loosely as "ummm looks like our control loop error is larger than we've been hoping for. Let's just crash the print.".
It's always nice do get some not requested skills assessment here. But the topic is more dedicated to a latest firmware update:
1) Want to know how often people facing with bed thermal runaways. I didn't have that on Core One before so I am wondering if this is this related to the latest version of the firmware.
2) Wanted to raise concerns about not user friendly approach of crashing prints when a thermal runaway happens. May be there is a room for improvement here.
RE: CORE One bed thermal runaway
It's always nice do get some unrequested skills assessment here.
I am pretty sure the "amateur" rating was directed at the Prusa developers, not at you. As you have experienced, the way they handle this control loop deviation seems ill-conceived, and they use a technically incorrect term to describe the issue.
Beyond that, the lack of responses here might indicate that it is an uncommon fault. FWIW, I have never experienced it in my Core One during the 8 months I have used it. I updated to 6.4.0 shortly after RC1 became available, and to the official release version when that came out. I think a hardware issue in your printer (bad temperature sensor or wiring maybe?) is the more likely cause, and the fact that it showed up after you updated the firmware might be just a coincidence.
RE:
Hi,
>> I am pretty sure the "amateur" rating was directed at the Prusa developers,
And not even that - more about the whole mindset and history e.g. RepRap. The "amateur" comment wasn't meant to be disrespectful against anybody including Prusa developers and open source contributors ("amateur" or not) - that's just where this printer is coming from. And it's a main reason why some people - me included - buy it.
Still, that colorful, over-excited message is something they might want to review at some point 🙂