"system error" on powerup; link is 404
Turned on CORE One+ this morning and was greeted with "system error."
It shows a QR code (which I cannot scan) and a URL: prusa.io/31538
That URL takes me to a page that says, "default backend - 404".
Cycling the power resolved the fault, but I'm curious to know what type of error this is. I've overcome several problems getting my new printer set up and running over the past two weeks, and I was finally ready to focus on figuring out some print quality issues. Maybe this fault is a spurious sensor reading that could be relevant.
Firmware is 6.5.3+12780.
RE: "system error" on powerup; link is 404
Any chance that it was an "Internal Error" rather than a "System Error"? That's the notorious "black screen of death" which is triggered by some issues Prusa does not yet have a proper handle on.
The stated address for the help page should work. Be sure to enter "prusa.io/31538", not "www.prusa.io/31538" or such. You should be forwarded to the following page, which is however not all that helpful: https://help.prusa3d.com/article/blue-screen-of-death-bsod-31538-core-one-35538-core-one-l-26538-mk4s-13538-mk4-27538-mk3-9s-17538-xl-21538-mk3-9-28538-mk3-5s-23538-mk3-5-12538-mini_689421
Instead of power cycling, you can just press the Reset button on the front panel. That should put you back in business.
RE: "system error" on powerup; link is 404
> Any chance that it was an "Internal Error" rather than a "System Error"?
It said "ERROR" at the top of the display, "INTERNAL ERROR" below that, and "system error" below that.
> Be sure to enter "prusa.io/31538", not "www.prusa.io/31538" or such.
Typing "prusa.io/31538" into the Chrome address bar gives "default backend - 404", so thanks for the expanded URL.
RE: "system error" on powerup; link is 404
One more note: While the help page mentions saving a crash dump file, users have found consistently that none is created -- probably because the error occurs before the firmware has set up the relevant infrastructure.
I don't think it's worth reaching out to Prusa support about this anyway. The error has crept into the firmware when the new boot loader 2.5 was introduced, in September of last year. Prusa have since released new firmware and a new boot loader, but all they managed to do is to replace the former blue screen of death by a black one with a bit more information. Prusa know about this error and don't seem to have a fix or a workaround (beyond "press Reset to play again") yet.