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

[BUG] MMU Idler cannot home message leads to unrecoverable state #4558

Closed
PxT opened this issue Jan 4, 2024 · 5 comments · Fixed by #4681
Closed

[BUG] MMU Idler cannot home message leads to unrecoverable state #4558

PxT opened this issue Jan 4, 2024 · 5 comments · Fixed by #4681
Assignees
Labels
bug MMU MMU2s and MMU3

Comments

@PxT
Copy link

PxT commented Jan 4, 2024

Printer type - MK3S
Printer firmware version - 3.13.2

MMU upgrade - MMU2S
MMU upgrade firmware version - 3.13.2

SD card or USB/Octoprint
SD

Describe the bug
Upon receiving an “IDLER CANNOT HOME” error from the mmu there is an option to adjust the sensitivity. Going into this menu then back by selecting “Done” returns the printer to the main info screen with “OK” on the bottom line and the print does not resume. Both temperatures remain set but otherwise the printer does not appear to be actively doing anything. Pause / Stop print options do not appear in the menu and there’s no apparent way to resume or recover the print. I have experienced this more than once, with different gcodes. Not sure how to specifically reproduce as I haven’t tried to artificially trigger the idler error message.

@PxT PxT added the bug label Jan 4, 2024
@3d-gussner 3d-gussner added the MMU MMU2s and MMU3 label Jan 4, 2024
@gudnimg
Copy link
Collaborator

gudnimg commented Jan 5, 2024

Going into this menu then back by selecting “Done” returns the printer to the main info screen with “OK” on the bottom line and the print does not resume.

The idler error screen should have been rendered again to give you the “Retry” button. Can you confirm this didnt happen?

This can explain your scenario since the MMU will stay in an error state waiting for the “retry” command.

I have never seen this when the printer is idle. Maybe something strange happens when printing or the MMU is running a toolchange.

@PxT
Copy link
Author

PxT commented Jan 5, 2024

Confirmed, this didn't happen.

@gudnimg
Copy link
Collaborator

gudnimg commented Jan 6, 2024

@PxT I can confirm the issue and can reproduce it quite easily. The issue seems to happen when the Idler fails to engage/home during toolchange. The printer tries to tell the MMU to unload which the MMU rejects since it think it is doing a toolchange.

I will look more into this.

@gudnimg gudnimg self-assigned this Jan 6, 2024
gudnimg added a commit to gudnimg/Prusa-Firmware that referenced this issue Jan 6, 2024
Fixes prusa3d#4558

Change in memory:
Flash: +136 bytes
SRAM: +1 byte
@sithlord48
Copy link

sithlord48 commented May 1, 2024

+1 just had this happen. tool change got held up i mis clicked into tune yeah there is no way to get back .. lost about 1kg of filiment and 18ish hours worth of the mmu job i was printing.. :(

MMU 3.0.2
MK3S+ 3.13.3

@gudnimg
Copy link
Collaborator

gudnimg commented May 4, 2024

@sithlord48 @PxT I've submitted another PR which does at least mitigate the issue by making the Tune button not do anything if the MMU is in the middle of a toolchange or another command. This way this issue will at least stop ruining prints.

To make the Tune button work while printing is a whole other matter. But the important thing is it should not ruin prints!

gudnimg added a commit to gudnimg/Prusa-Firmware that referenced this issue Sep 1, 2024
Fixes prusa3d#4558

Change in memory:
Flash: +136 bytes
SRAM: +1 byte
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug MMU MMU2s and MMU3
Projects
None yet
4 participants