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

[ENHANCEMENT] Allow operator discretion for clearing MMU3 errors. #4795

Open
1 of 4 tasks
ssackett opened this issue Oct 19, 2024 · 2 comments
Open
1 of 4 tasks

[ENHANCEMENT] Allow operator discretion for clearing MMU3 errors. #4795

ssackett opened this issue Oct 19, 2024 · 2 comments

Comments

@ssackett
Copy link

Printer model

  • MK3S/+
  • MK3
  • MK2.5S
  • MK2.5

Describe the enhancement

Sometimes the MMU3 enters an error condition because the sensors have not sequenced properly. Often the operator can tell there is nothing wrong but there is no way to clear the error except for repeating the process to sequence the sensors properly. Such a condition happens if a filament runs out and the operator manually loads a new filament but pushes it in far enough to trip the sensor in the MMU3 head. In this case the MMU3 will recalibrate and cut the filament rather than loading it to the extruder.

Expected functionality

Allow the operator to tell the MMU3 that the filament is properly loaded so that it doesn't end up going into an error condition when the sensors don't trip in the expected sequence.

Copy link

Thank you for your contribution to our project. This issue has not received any updates for 60 days and may be considered "stale." If this issue is still important to you, please add an update within the next 7 days to keep it open. Administrators can manually reopen the issue if necessary.

Copy link

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 26, 2024
@3d-gussner 3d-gussner reopened this Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants