RE: Idler cannot home deadlock !
@stephane-hamel thank you very much for reporting this and putting so much effort in the issue. I followed your intructions and did the update with 3.13.2 for the MK3S+ and 3.3.0 for the MMU2. So the idler works now.
Now I am Stuck with the "FINDA DIDNT TRIGGER" error code. Although the filement is moveable it does not move. Any idea of what I could try next?
RE: Idler cannot home deadlock !
i got the same Finda didn't trigger error.. my MMU is basically useless now. so frustrating!!!!
i updated a MK3S single machine and it works fine, so the new firmware is screwy with the MK3S+ with MMU2
“One does not simply use a picture as signature on Prusa forumsâ€
RE: Idler cannot home deadlock !
I'm having the same issue with MK2.5S and MMU2S.
I upgraded to latest firmwares for both the printer and the MMU, and now I get the "tune" option, but still homing fails in all settings. I contacted support, after a lot of back and forth with flashing different firmwares combinations, sending them video, and following up with the developer team, they told me the MK2.5S is not longer supported so they don't have a fix and won't have one either.
Does anyone have an idea on what to try? Anyone managed to get that same combination (MK2.5S + MMU2S) working?
RE: Idler cannot home deadlock !
roll back the firmware to the last version you had that was working.
ignore any firmware upgrade messages you get from the gcode. you can remove the firmware check from the slicer if you want.
basically things at prusa are really messed up now. not only is firmware being released that is bugged but also slicer since 2.6 has been bugged.
the last time i had a major print project was spring of 2023 and i might have to revert back to what i was running back then in order to keep things going. in December 2023 i decided let me just upgrade everything since it was a long time and that was when it all went nuts.
the main upgrade reason was my XL arrived and i wanted everything running properly, well my XL is basically a brick since it has so many issues, and the firmware upgrade screwed up all my MK3 machines and the slicer has a bunch of new problems for 2.6.X and 2.7.X.
i might have to just revert to 2.6.0 as that was the first version with Trees support.
because of the firmware problems i actually went back to using my MK2S machines again, because they can't screw those machines up anymore.
“One does not simply use a picture as signature on Prusa forumsâ€
RE: Idler cannot home deadlock !
I'm having the same issue with MK2.5S and MMU2S.
I upgraded to latest firmwares for both the printer and the MMU, and now I get the "tune" option, but still homing fails in all settings. I contacted support, after a lot of back and forth with flashing different firmwares combinations, sending them video, and following up with the developer team, they told me the MK2.5S is not longer supported so they don't have a fix and won't have one either.
Does anyone have an idea on what to try? Anyone managed to get that same combination (MK2.5S + MMU2S) working?
I am half way there. To get the idler working, you have to tune the sensitivity to 10.
For this you can use the following g-code:
M708 A0x19 X10
X10 sets sensitivity to 10.
This is needed, because anything MK2 is 12V system, so the steppers need more sensitivity to sense that they reached the end.
I have yet to find out how to get the Finda triggering. For now I have the red Finda light working properly, but I cannot see Finda status changing in the Support ---> Sensors menu.
RE: Idler cannot home deadlock !
Thank you for the info! Could you explain how to send serial commands directly to the MMU2? Or should I send them to the printer? I'll try setting the sensitivitiy to 10 how you suggest.
RE: Idler cannot home deadlock !
I can also recommend setting the sensitivity to 10, that worked for me as well, as I have written in this thread. I also linked the bug report, which also had lots of discussions about how to issue these commands, but apparently the bug has been deleted. Not closed, but deleted! Don‘t know, how that can happen. There is a snapshot of the bug on archive.org, but it only includes a tiny fraction of the discussion, unfortunately: https://web.archive.org/web/20230728211129/https://github.com/prusa3d/Prusa-Firmware/issues/4285
To cite from that bug report discussion:
You need to connect a computer to the printer's USB connector and open the serial port with Baudrate 115200 and send the gcode command manually.
I usually find Arduino IDE to be easiest to use. But other software like https://www.pronterface.com/ or PuTTy or TeraTerm should also work.
I used putty and this command: M708 A0x19 X10
Now everything works perfectly for my MK2.5S+MMU2S
RE:
I'm just running into this for the first time after updating to the latest mmu firmware as well. This is with an MK2.5S. I have two questions
First, is the unit looking for physical stops? I ask because it never really fully goes stop to stop. I also tried removing the motor from the mmu and it did the same.
Second, could this issue be caused by an underlying power issue? Before having this error, I had the mmu mcu 04306 immediately after updating the firmware. That miraculously went away and this issue appeared.
RE: Idler cannot home deadlock !
Codeplayer, THANK YOU!!!
I managed to get it working. I used Octoprint serial monitor to issue the commands. It did a few funny things, at first the printer would issue back an "ok" but sensitivity stayed at 7. At one point it showed sensitivity 19!
In the end I managed to get it done like this:
1) Start the printer and let the homing fail.
2) When the prompt to change sensitivity shows up, it gives you 3 options: retry, tune or 2 down arrows for more info. Select that last option.
3) WHILE the text is open, issue the command by serial monitor. It´ll reply "waiting for user" as the printer is kinda paused while you are supposedly reading the text on screen.
4) Click on the printer until it goes back to the previous menu. It´ll home correctly as now the sensitivity is recorded.
Now everything works fine. I´ve tried loading and unloading filaments and it works like a charm. I haven´t tested a print yet.
Thanks again for the help!!!
RE: Idler cannot home deadlock !
Thank you! This fixed my issue.
Installing firmware version 3.13.2 for the MK3S+ and 3.3.0 for the MMU2 solved the problem. As expected, the idler failed to home after the upgrade, but it then offered to tune the sensitivity which I did change from 7 (default) to 5. And now it works just fine.
RE: Idler cannot home deadlock !
This was my fix.. changed the sensitivity from 4 to 5 and no more error.