Skip to content
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

[QUESTION] Power Panic when printing from Prusa Connect? #4445

Open
Rebel154 opened this issue Jan 31, 2025 · 2 comments
Open

[QUESTION] Power Panic when printing from Prusa Connect? #4445

Rebel154 opened this issue Jan 31, 2025 · 2 comments
Labels
question Further information is requested

Comments

@Rebel154
Copy link

Rebel154 commented Jan 31, 2025

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

@Rebel154 Rebel154 added the question Further information is requested label Jan 31, 2025
@me25542
Copy link

me25542 commented Jan 31, 2025

In my experience Power Panic does work when printing via prusa connect, though lately I have notice a slight (~1mm) layer shift on resume.

@CloudStrife1983
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants