You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does the Power-Panic feature work when printing via Prusa Connect? I suffered a brief (15-20 secs max) power cut midway through a couple of prints on my two Mk4S printers (one with MMU3), and neither printer restarted after the power came back on.
I'm aware it never worked when printing via OctoPrint, but I thought it would (should?) work via Connect, as the print file is downloaded to the printer's USB stick.
I was using PrusaSlicer 2.9.0 to send the .bgcode files to the printer via the 'send and print' option (1st in the list). The firmware on both printers was 6.1.3+7898. Printers are now on 6.2.0
The text was updated successfully, but these errors were encountered:
In my experience Power Panic does work when printing via prusa connect, though lately I have notice a slight (~1mm) layer shift on resume.
@me25542 Yes, PowerPanic works with Prusa Connect prints. Thats because the printer always prints from USB. Prusa Connect only copy the printfile to the USB drive.
The layer shift is due to the fact that the printer no longer has the exact same zero point on X/Y after re-homing. Either it was wrong at the beginning or after the next home.
Question
Does the Power-Panic feature work when printing via Prusa Connect? I suffered a brief (15-20 secs max) power cut midway through a couple of prints on my two Mk4S printers (one with MMU3), and neither printer restarted after the power came back on.
I'm aware it never worked when printing via OctoPrint, but I thought it would (should?) work via Connect, as the print file is downloaded to the printer's USB stick.
I was using PrusaSlicer 2.9.0 to send the .bgcode files to the printer via the 'send and print' option (1st in the list). The firmware on both printers was 6.1.3+7898. Printers are now on 6.2.0
The text was updated successfully, but these errors were encountered: