prusa3d / Prusa-Firmware-Buddy

Firmware for the Original Prusa MINI, Original Prusa MK4 and the Original Prusa XL 3D printers by Prusa Research.
Other
1.16k stars 226 forks source link

[BUG] 409 - Can't start print now #2301

Closed chrishilbert closed 4 months ago

chrishilbert commented 2 years ago

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 - [MINI]

Printer firmware version - 4.4.0 Beta 2

Original or Custom firmware - [Original]

Optional upgrades - [Filament Runout Sensor]

USB drive or USB/Octoprint USB

Describe the bug Files uploaded from PrusaSlicer often throw 409 can't start print now error in the slicer and the web GUI if kicked off manually.

image

How to reproduce Upload print to printer with "start job" selected. Get 409 error both in PS and web GUI.

DRracer commented 2 years ago

@chrishilbert is your MINI really showing the home screen? We only allow starting print while specific screens are being shown on the LCD. Error 409 means your MINI was not "idle" on the home screen.

darraghbr commented 2 years ago

I'm afraid I can confirm this issue, I cannot start a print from the so called "print-finished" screen. I get the same error, further to my issue #2298 which was closed somewhat prematurely.

I hope we can all agree that this is a "print-finished" screen?

PXL_20220728_053051226

I get the below when I try to start a print.

image

DRracer commented 2 years ago

@darraghbr yes, this is a "Print finished" screen. Could you please try starting a print remotely while the MINI is showing the Home screen?

darraghbr commented 2 years ago

@DRracer That does indeed work as expected.

DRracer commented 2 years ago

ok, so only the print finished screen seems to be "broken"

darraghbr commented 2 years ago

Any idea if the "print-cancelled" screen is different mechanically from the "print-finished" screen? If they are different it would be nice to be able to print from the "print-cancelled" screen as I mentioned in my other issue in case you accidentally start to print the wrong file.

chrishilbert commented 2 years ago

I think I have to hit HOME on the mini before I an start the next job.

chrishilbert commented 2 years ago

Update: I have double checked the mini and every time this happens it's either that I didn't hit the home button at completion of last print, or something happens after I hit send from Prusa Slicer. In the second example, the mini was idle/on the Home Screen and upon clicking send/print from PS the mini has the model up and wants me to click print. However it throws the 409 error anyways. Like it loaded the screen up to click print and then saw I wasn't on the Home Screen and sent a 409. Think it's something to do with timing is my guess.

chrishilbert commented 2 years ago

Anyone figure out a workaround for this one? This is the most annoying bug I have. I send the print from Prusa Slicer to an idle machine at Home Screen, and have to go to the machine and click "print" on the model up/ready-to-go.

joshnoe94 commented 12 months ago

Any progress on this? Admittedly it's not a showstopper, but it is fairly annoying. Would it be feasible to automatically return to the home screen a few minutes after a print completes?

I don't have any experience with this codebase, so I'm not sure how complicated this would be to fix. If it's something fairly simple, point me in the right direction and I'll take a look.

github-actions[bot] commented 5 months ago

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.

github-actions[bot] commented 4 months ago

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.

sebastianludwig commented 4 months ago

@Prusa-Support can you re-open this issue? It might not have had recent discussions but that's more due to the fact that everything has been said, not that it's not an issue anymore. Thanks 👍

danopernis commented 4 months ago

Before reopening, @sebastianludwig can you please confirm if the issue is still present on newest firmware 6.0.2?