Closed handro123 closed 3 months ago
Thank you for reporting.
That's surely interesting, and I don't think I've ever heard about this specific message before.
Have you tried further firmware downgrading? Would the error persist on firmware 4.3.4 (or older)? Could you confirm that the error is "something new" (4.4.0 or newer firmware)?
Michele Moramarco Prusa Research
Downgraded to 4.3.4 and the issue was not seen.
Upgraded back to 4.4.1, had to go through the Setup Wizard again, and after that was successful I was able to reproduce the "Divide by 0" error again by disconnecting power to the Raspberry Pi running Octoprint.
Alright. Thank you for the additional feedback. Our developers will look into this.
Michele Moramarco Prusa Research
Just to confirm this. Same issue occured for me.
I ran into this blue screen today for the first time. I wasn't unplugging octoprint, but my pi is powered by poe and was running for a few days now as i was printing heavily. So while not normal power could have dipped.
Normally i only turn on/off to print. i rebooted prusa and pi and within a short time (10 min) i had the blue screen again. I shut down the pi to give it a rest and ran across open issue this looking for a solution. i am on firmware 4.4.1+4194 which is what came on my mini.
Just adding my hat to the ring of those it happened to since this issue is still marked as open.
Thanks for reporting.
So far an abrupt power shortage on the micro USB port seems to be the key to the reproducibility of the issues as further confirmed by other users in a more recent issue (https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/3278).
Michele Moramarco Prusa Research
This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.
This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.
Printer type - Original MINI (not +)
Printer firmware version - 4.4.1
Original or Custom firmware - Original
Optional upgrades - Filament Runout Sensor, SuperPINDA, E3d Revo Micro
USB drive or USB/Octoprint Have OctoPrint on Raspberry Pi 4 installed and Connected by not printing.
Describe the bug My OctoPrint was not responding so I went to reboot the Raspberry Pi while still Connected to the Printer. When I unplugged the power to the RPi it also reset the Printer and the printer showed a blue screen for "Divide By 0" error. First noticed the issue on 4.4.0 firmware, then upgraded to 4.4.1 and was still able to reproduce the issue.
How to reproduce
Expected behavior I don't think the Printer should reboot and show blue screen if the Raspberry Pi loses power.
G-code N/A
Crash dump file Can't attach .bin so it is inside Zip archive. dump.zip
Video Issue on 4.4.1: https://youtube.com/shorts/rwQBYCOJzuc Issue on 4.4.0: https://youtube.com/shorts/wOScBs0lfZU