Full LCD corruption and printer returns error 0 after long prints
Ever since I upgraded to the latest firmware the printer will get into a funky state after long prints. The LCD screen gets all jumbled and I get back error 0 when I try and connect via octopi. Hitting the reset key brings everything back online and it prints fine up up until this happens. (so far has not interrupted a print but my prints have only been a few hours each). Did not do this before the firmware update.
Any ideas on what is going on and how I would fix it?
Thanks in advance.
Do a firmware reset and clear storage.
You will have to calibrate again.
Ok did the reset and calibrating now. Will see how it goes
Did a factory reset (all data) then did the prompted calibration setup.
Once that was complete I let the printer sit at the home screen while I ran out to get lunch.
Came back 2 hour later and same corrupted screen is back.
Just reset the printer and unplugged the USB cable so now just the printer and SD card installed (no internal Pi Zero)
Will let this sit and try and check it every 15 minutes to see when things go south.
Ok ran 2.5+ hours with no issues. Hooked the USB cable back up to the OctoPi as I need to print something.
2 thinks I need to try yet.
1.) Pi connected from reset but no print start / heater on
2.) No Pi but run the heater (z cal or similar) then let sit.
Wondering if there is either a command overflow or a timer somewhere that is causing this weirdness.
When to start the print and after I hooked up the OctoPi and reset things to clear the lowtemp error (My shop is cold and will trigger this error if left to sit) it went into funky screen mode a few seconds later.
Anyone heard of any issue with the latest build of OctoPi and Prusa MK3s?
Will try and do the experiments above once this print completes
Reset was the only arrow in my quiver.
Better chat with Support. The EShop link above, sign in, and the Chat button is in lower right.
Will do once I rule out my Pi as the cause.
Thanks for the help!
Today's update. Powered on the printer and just left it with the Pi connected (no print started just a fresh power on in low temp error condition.) and when I got back from lunch the screen was corrupted. So looks like OctoPi is needed to get the printer into this funky state.
Right now I am trying fresh power on then a preheat cycle with the Pi disconnected to see if this will also cause the error.
If this latest run does not cause an error then going to go with some sort of interaction problem between OctoPi and the printer when it is in a error state. Would like to test in a non error state as well but shop will not be warm again until spring. (Too expensive to heat over ~60F during the winter and its a pain to pull the printer out of it's enclosure to take someplace warm.)
Will update once I have results from today's experiment.
How are you powering your Pi?
Your problems sound like they might be related to low power on the Einsy board...
Have a Pi3 A+ plugged into it's own 3A USB power supply. Should be plenty for that board.
From the USB A connector on the Pi strait run down to the USB B socket on the printer. (using the USB cable that came with it)
Ok ran most of the day with no errors with the Pi unplugged. So definitely looks like that is part of the formula to get this crash. Don't see anything on the octopi forums currently about it and the latest firmware having issues. So must be something unique about my setup. Guessing its the fact that the low temp alarm goes off when just sitting due to the temp in my shop.
Annoying but something I can work around. (power cycle and start a preheat as soon as it inits.)
I'm having the same problem. I'm running a PI 3b+ connected with dedicated 3A usb psu and running octopi. I haven't managed to figure out when this happens but found that a simple reset fixes it.
My office drops to about 5°C at night unless I'm printing. I have only witnessed it happen once but have come back to a corrupted printer screen a few times now. Luckily it has been when the printer was idle or just starting a print.
Another problem that may or may not be related is the filament sensor. Mine keeps switching itself off. I've got the mmu2s and it's really annoying when you check in on the printer and find it air-printing 10mm above the bed! I can't seem to get the filament sensor to stay on between reboots...
Forgot to say that my printer and pi are both within an insulated enclosure (psu is not in the enclosure).