English
Login

Idler cannot home

#04125 (MMU)

Relevant for

MMU2S
MMU3
18 comments
Article is also available in following languages
English
Čeština
Polski
Deutsch
Français
Español
Italiano
日本語

What happened?

Before it can align with any of the filament positions, the Idler inside the MMU unit needs to be “homed” to determine its position. First, the Idler moves to one end of the travel (endstop). Then, it moves to the other endstop, while measuring the angle between the end stops. The idler homes after the unit starts up has been reset or after another error occurred.

In case it can’t find the first homing endstop or the distance between the two endstops differs from the expected value, the printer will show an error.

Distance between the Idler endstops: 225 degrees 
Allowed deviation: 10 degrees

Endstops are detected using the StallGuard function. Note that the Stallguard readings are ignored while the Idler moves over the filaments to mitigate false readings.

How to fix it?

The issue is usually mechanical. If you get this error, check the following items:

  • Verify there is no debris around the Idler and that it can move freely.
  • Release the idler tension screws slightly. If it is too tight, it will disable the Idler from moving freely.
  •  
  • Verify is the Idler Coupler is attached properly. Check both grub screws on the Idler Coupler are tightened and that one of the screws is facing the flat part of the motor shaft. Make sure the Idler doesn’t push against the Idler body so that it can rotate freely.
  • Especially the first time you are running the MMU, check that the motors are connected in the correct order.
  • Verify all the bearings can move freely and that the center shaft at the end is inserted into the Idler properly.
  • In case you are using the older MMU2S unit, check the MMU idler unable to move freely article.
  • In some specific cases, the unit might not be able to find the first homing endstop. This can occur, for example, when using a non-standard motor for the Idler axis. Adjusting the stall guard thresholds might help.

    Adjusting the Idler Stallguard threshold:

    When using an unsupported, third-party hardware or a rare differently-sized version of the Idler motor from the MMU1 to MMU2 upgrade kits or the early batch of MMU2, later upgraded to MMU2S and finally to MMU3, you might need to tweak the sensitivity threshold of the StallGuard feature (Idler_sg_thrs_R). The current MK3S+ printer firmware allows you to Tune the threshold to a value between 4 and 7, directly from the error screen. If none of the values in this range help, you may need to set it to a value outside this range.

    Some of these specific units might need to set the Idler sensitivity to a higher number such as 10. 
    You can do so by running a specific G-code command: M708 A0x19 X10. (where X10 denotes threshold value 10.) After that you can reset the MMU with: M709 command. Note that the commands are case-sensitive.

    The command can be either run in a G-code file, or sent to the printer via USB connection, using a serial terminal app such as PuTTY.

    For more info about the aforementioned commands, see the Registers MMU (MMU3) and the Prusa firmware-specific G-code commands articles.

 

7 comments

Log in  to post a comment
JackMorelli
Hi All, I'm having the same issue on my Mk3.5s MMU3, i can't see any options on the printer to adjust the stall guard settings?
Sergio FV
INFO MK4-MMU3.
I tried to adjust the Stallguard Idler threshold with PuTTY and Arduino IDE, but the G-codes didn't work, I could only solve it by putting the codes in PRONTERFACE
CazTheCar
This sucks. I have used the MMU3 upgrade kit and I cannot get past the Idler Cannot Home error. I have triple checked everything and am very sure this is not a mechanical error. The idler can 100% move freely.
I was on 3.13.2 then when I reached the MMU3 firmware flash stage I noticed that 3.13.2 has been withdrawn and am forced to go back to 3.13.1. 
This essentially means I cannot access the Tune Menu option and am essentially stuck with a brick.
@PrusaSupport is there ANY way for me to fix this without having to wait for 3.13.2 or better?
Added Tune menu for IDLER|SELECTOR CANNOT HOME
MMU2S users have reported that, despite careful hardware inspection, some units struggle to home the Idler reliably. Although MMU Firmware 3.0.0 has already offered an option to adjust the Idler's homing sensitivity by modifying the StallGuard threshold, some users have encountered difficulties changing this value.
Therefore, in case the MMU reports any of the “Idler and/or Selector cannot home” errors, there is a new option displayed on the screen called "Tune" which allows to set the threshold value in a user-friendly way. Please note that the allowed range of values has been limited to prevent users from accidentally setting extreme values. 
Jan Kratochvíl

Hello. Please contact our support team directly (best option via live chat). Thank you.

Codeplayer
My Idler happily does the whole movement, back and forth and then does it 2x more. After that it shows the error and possibility to tune. Tuning does not help. I am using Fw 3.13.2-7080 on MK2.5s+ and brand new MMU2s upgraded to MMU3 and flashed with Fw3.0.1 before first use. It's weird because I see that the idler can home just fine. Very disappointed. I was already thinking about eating all these gummy bears while doing the first print.
Codeplayer
Ok, anyone else with 12V system, you need to set the sensitivity to 10 or somewhere there. The fw 3.13.2-7080 and some others might not let you choose anything else but 4, 5, 6 or 7. So you need to inject a G-code. You can do this with pronterface through USB or if you have Octoprint or similar then through the terminal. The code is:
M708 A0x19 X10
X10 is sensitivity 10.
After that you can reset MMU3 with:
M709
This is the way.
 
GeekToyBox
This was exactly what I was missing! Thanks!
David B.

Thanks for sharing the info. A note has been added into the MMU3 Compatibility article. Feel free to add comments there, in case you have anything else to share.

Fabian
You need to check your quality control... such a Firmware should never ever have been released to the customers like this.
Jakub Dolezal

Hi Fabian, are you reffering to any specific case? I would need to know more details.