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

Wrong filament after MMU power fault (3.8.0-RC2, 1.0.6) #2159

Closed
vintagepc opened this issue Aug 31, 2019 · 4 comments
Closed

Wrong filament after MMU power fault (3.8.0-RC2, 1.0.6) #2159

vintagepc opened this issue Aug 31, 2019 · 4 comments

Comments

@vintagepc
Copy link
Contributor

vintagepc commented Aug 31, 2019

Started getting MMU power faults (all 5 MMU LEDs blinking red and green). Instructions say to reset the MMU to correct. However, the MMU will re-home and park on filament 1, not the correct filament the T command had requested. It can be worked around if you're quick and can hit "change filament", but not ideal.

(Note this happens only if the selector/FINDA is clear, of course if filament is sensed, it will not move the selector)

@MB3Y
Copy link

MB3Y commented Feb 9, 2020

This problem #2159 seems related to my finding documented in #2476 .
May I ask if this problem is considered to be taken up any time soon? Original submission dates 6months back meanwhile and before I submitted I was checking for SW updates... bad luck however

@JCaba
Copy link

JCaba commented Mar 12, 2020

I just had this same problem today: I resolved as follows (maybe ulimately related to "spooljoin" during reset?

March 12 2020:
Was using MMU positions/filaments stations 1 and 3:
MMU indicated line 3 (soluble) was jammed, when in fact line 1 (PLA) was jammed in the print-head. After extracting line 1 (by faking the machine into thinking line 1 was clear (by removing front PTFE tube and clearing the MMU, then pause MK3, remove side fan, increase head temp to 250, then extracting filament from print-head).
Then after resume, the MMU wanted to load line 5 – which wasn’t being used and was actually empty. (I faked it – by temporarily inserting filament so it was ‘loaded’) , then it wanted to load line 2 (faked it again). Printer started to use line 2.
Paused, went to settings, turned off the ‘spooljoin’ function, reset MMU, Then the MMU/Mk3 resumed using the normal/selected filaments (line 1 and line 3).

@github-actions
Copy link

github-actions bot commented Oct 2, 2023

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
Copy link

This issue has been closed due to lack of recent activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2023
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

4 participants