Notifications
Clear all

No crash recovery?  

  RSS
P. Larsen
(@p-larsen)
Trusted Member
No crash recovery?

So I've now experienced a "power off" accidentally two days in a row (hint, don't use remotely controlled power switches on your printer - you'll regret it!). In both cases, the printer did NOT resume the print after power-on. Crash detection is turned on - but the gcode is never reloaded on power-on. The printer resumes heat of bed and extruder, and it returns to the position where it was when power was lost - but that's it. It doesn't start printing. Having lost 3-4 hour prints this way, I'm really getting annoyed.

What's the procedure supposed to be? I've watched videos where Joseph Prusa simply restores power and the print resumes. That's not happening. Firmware is 3.1.1.

Posted : 07/04/2018 8:54 pm
JoanTabb
(@joantabb)
Veteran Member Moderator
Re: No crash recovery?

Hi Peter,
3.1.1 is not a current software, I doubt that Prusa will look at the issue

why not upgrade to the latest and greatest and see if it's already been fixed.... (early in a test piece to save hours of material and energy

good luck, 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

Posted : 07/04/2018 11:30 pm
P. Larsen
(@p-larsen)
Trusted Member
Topic starter answered:
Re: No crash recovery?

Thanks Joan,
An upgrade is definitely planned, but there's no need to guess if a feature has been fixed or not - I can read the release notes (and code) and nothing I can find indicates this has even been touched:

https://github.com/prusa3d/Prusa-Firmware/compare/v3.1.3...MK3
https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.1.2-RC1 [1]
https://github.com/prusa3d/Prusa-Firmware/compare/v3.1.2...MK3

[1] while this fixes important recovery issues, it doesn't talk about recovery not resuming - it's fixing recovery starting from the wrong location.

Basic philosophy - I'll focus on one problem at a time. Upgrades come with a ton of other challenges and risks and may cause a lot of other things not to work (for instance 3.1.2 requires full self-test/recalibration). As a different thread I just created also shows, upgrading when you're not running Windows isn't documented but I now have avrdude ready to attempt an upgrade when that becomes necessary.

Posted : 07/04/2018 11:58 pm
Share: