-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] USB drive or file error #4368
Comments
Hello, this should be fixed in 6.2.0 |
I already tested **6.2.0-alpha1 ** and for last couple of months testing 6.2.0_Alpha2. |
@FSXLiveriesdotcom I see, please describe your problem a bit more then. So:
|
Yes. Let me give you a big picture maybe. The error started to occur in 6.1.4 or maybe one version before, to be honest I do not remember anymore. I do not use Connect at all. |
@FSXLiveriesdotcom thanks, so on 6.2.0-alpha2, this only happened to you once so far, right? And pressing the button didn't help, you had to reinsert the drive? |
Printer model
Prusa XL
Firmware version
6.1.3
Upgrades and modifications
No response
Printing from...
Prusa connect
Describe the bug
Occasionally our Prusa XL printers get the USB file drive error.
Once a printer is in this state, you have to press the knob and then you can press reprint to start the print that was intended to be printed.
To get the printer out of the error state, the error can only be acknowledged on the printer, not remotely.
It would be best if the error does not appear in the first place, but if it does it would be good if the error can be acknowledged remotely. Because now I can't print if I am away and the printers are giving the error.
We are using the USB sticks that came with the printer, there are only 8 BGCODE files on the USB stick.
How to reproduce
Occasionally our Prusa XL printers get the USB file drive error.
Once a printer is in this state, you have to press the knob and then you can press reprint to start the print that was intended to be printed.
To get the printer out of the error state, the error can only be acknowledged on the printer, not remotely.
Expected behavior
No response
Files
No response
The text was updated successfully, but these errors were encountered: