Closed Cloud-Tickler closed 2 months ago
Crash dump file removed. Still available. But since it contains the unencrypted password to the WIFI and Prusalink, it will no longer be public.
See https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/3528
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.
Please, before you create a new bug report, please make sure you searched in open and closed issues and couldn't find anything that matches.
Printer type - [XL 5T]
Printer firmware version - [5.1.0 alpha 2]
Original or Custom firmware - [Original]
USB drive or USB/Octoprint USB
Describe the bug Filament runout at about 85 % of the print. When I came to the printer the instructions weren't clear when you should pull out the rest of the filament. I was asked if the unloading was successful. I confirmed and waited for the next screen. Then I was asked to remove the filament from the sensor but the filament was stuck. Since there is no option available to do anything and you can't leave that screen, I tried to retract the filament via Prusa Connect. That didn't work. There is also no option in this situation to stop the print on the printer, so I stopped it via Prusa Connect. That lead to a watchdog reset. Happy days...
How to reproduce Please describe steps to reproduce the behavior.
Expected behavior A clear and concise description of what you should do when you ran out of filament to replace the spool.
G-code xTool_F1_Pencil_Jig_V01_eSunPLA_XL_060_0.6n_0.2mm_PLA_XL_2h43m.bgcode.zip
Please attach the G-code you had trouble with. This will make it easier for us to replicate the error.
Crash dump file
Crash dump file removed. Still available. But since it contains the unencrypted password to the WIFI, it will no longer be public.
Please attach the crash dump file. This will make it easier for us to investigate the bug.
Video
Please attach a video. It usually helps to solve the problem.