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.

Sign up for GitHub

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

Jump to bottom

!!! Before you report !!! #36

Open

jukebox42 opened this issue Sep 27, 2023 · 0 comments

Owner

jukebox42 commented Sep 27, 2023 •

edited

Loading

Things to check:

Make sure you are running the latest version of Prusa MMU
Make sure your printer profile has "Number of extruders" set to 5 AND "Shared nozzle" is checked.
Make sure you are slicing your prints with PrusaSlicer and using a printer profile that supports either MMU or MMU Single.
Make sure your Octoprint version is greater than or equal to 1.8.0 (when they dropped python 2 support)

Needed to debug:

What model of Prusa printer are you using? MK3/MK3s/MK3.5/MK3.9/MK4/MK4s
What version of the Prusa MMU plugin are you running?
What versions is your printer running? (and what version is your MMU running?)
What behavior are you seeing?

Known bugs:

The nav menu can sometimes get stuck if the print finishes before you return to the tab (working on a fix)
The nav menu may report an incorrect state on occasion. Sometimes the MMU reports a state message in the wrong order.
Using custom start scripts, if you call M109 more than once the filament selection wont trigger properly. (MK3 only problem)

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment