Another occurrence after a few months-long hiatus from printing. A print finished <5 minutes ago. I remove the print from the platform, then noticed the UI was at the "Ultimaker S3" logo screen, as displaying during bootup. It suspect that I turned it on, queued the print, and never even looked at the printer until after the print was done.
- 3 months later...
still happening on multiple S5s firmware 8.1.2
Same here, for the Ultimaker S3: now and then a black screen for which only a power cycle reset remedies it. This morning I was expecting to see a full 5-day print finished, to arrive at a paused (PVA flow error) build with a black screen. I was relieved to be able to resume the print from Cura monitor interface, but I'm convinced this merits attention from the firmware devs. Attached the zipped logs I could extract from http://{printer_ip}/info/log.html
6 hours ago, reinvantveer said:Same here, for the Ultimaker S3: now and then a black screen for which only a power cycle reset remedies it. This morning I was expecting to see a full 5-day print finished, to arrive at a paused (PVA flow error) build with a black screen. I was relieved to be able to resume the print from Cura monitor interface, but I'm convinced this merits attention from the firmware devs. Attached the zipped logs I could extract from http://{printer_ip}/info/log.html
This appears to be a very incomplete log file.. and some reason in .html format? - this isn't an expected format.
I would recommend contacting UltiMaker Support directly
Here: https://support.makerbot.com/s/contactsupport
Additionally, be sure to export the complete log files as they will just ask you to do so again.
Guide here: https://support.makerbot.com/s/article/1667337561393
2 hours ago, Dustin said:This appears to be a very incomplete log file.. and some reason in .html format? - this isn't an expected format.
I would recommend contacting UltiMaker Support directly
Here: https://support.makerbot.com/s/contactsupport
Additionally, be sure to export the complete log files as they will just ask you to do so again.
Guide here: https://support.makerbot.com/s/article/1667337561393
Hi Dustin, thanks for looking into this. I see, those instructions tell you to dump to USB from the screen UI... which wasn't working at the time. This is what I could download from the API. I've attached a complete dump now that the printer display is working again.
logs-ultimakersystem-dc73a76132ca454d8f7788e22c92cd5c-8.2.0-20230605175834.zip
The good news is that those logs hold many days worth of log information so it's okay to reboot before dumping the logs.
- 1
- 4 months later...
I have the same problem on a S3 printer with the latest firmware 8.2.1
Interesting update, after switching from wifi to ethernet networking I have not had this happen again.
- 2 months later...
Have the same issue on my S5, latest today. Screen black and unresponsive, but I am able to start a new print from cloud. Firmware version V.8.3.0.0
Edited by bodoactionFirmware version.
- 2 months later...
Happened again after an overnight build, firmware version: 8.3.1.0. The printer is on and the web UI reports the print as finished. I assume it thinks it is at the "confirm removal" screen.
Have you considered a button on the remote UI to reinitialize the screen? So when this happens, we could press that button and report if the screen comes back.
UPDATE: After I power cycled it, it indeed displayed the "Confirm Removal" screen but the lights were *on* which is odd since I have them set to off.
Edited by MobyDisk
Recommended Posts
CarloK 202
@MobyDisk My gut feeling is that you experience different errors. The problem where the screen goes unresponsive after a long period of inactivity has been reported by other people as well and is a bug that we are investigating.
Then, the problem with the printer freezing when moving the printer is different. Here, in the log files I see no new entries after the freeze and a very rapid printer reboot. I'd suspect an external power plug is loose or had a bad connection and interrupted the power supply when the printer was moved.
Posting new logs has no extra value at the moment. Thanks for your efforts. It's now up to my colleagues to find the bug.
Link to post
Share on other sites