Notifications
Clear all

Is there a way to "tune" the idler?  

  RSS
WizardStan
(@wizardstan)
Eminent Member
Is there a way to "tune" the idler?

I updated my firmware at the start of January and ever since I've had problems loading and unloading filament.  It mostly works, but frequently slips, and then I need to give it a little nudge to get it going again. Fine enough for single colour prints (sometimes I come back and it's flashing at me that it was unable to unload) but for actual multicolour prints with regular swaps this is a no go.

After much experimentation I've discovered that after turning my printer on and waiting for the idler to home, if I just reach in and give it a push so it rotates one click I no longer have any problem with it, filament loads and unloads quick and easy, and it remains so until I power off and on again, at which point I just need to push it that one click again.

Is there a way to tune the position of the idler?  Or am I cursed?  It's strange, this is consistent and repeatable for me, but I don't see anyone else complaining.

Posted : 02/02/2025 5:08 pm
Muttzy
(@muttzy)
Active Member
RE: Is there a way to "tune" the idler?

I have complained extensively in forum posts.  My recommendation is to go back to firmware 3.12.2 (1.0.6).

Posted : 03/02/2025 3:39 am
WizardStan
(@wizardstan)
Eminent Member
Topic starter answered:
RE: Is there a way to "tune" the idler?

Unfortunately I have other, significantly worse problems with 3.12.2.  I'm going to try a frankenfirmware this weekend, see how it likes running 3.14 on the printer with 1.0.6 on the MMU2.  Failing that, guess I take initiative and try to fix the bug myself.

Posted : 07/02/2025 6:13 pm
WizardStan
(@wizardstan)
Eminent Member
Topic starter answered:
RE: Is there a way to "tune" the idler?

After a lot of investigation and experimentation I figured out it was failing because the current supplied to the idler motor had been significantly reduced.  When the idler would rotate to select a filament it would frequently skip or slip which is what was actually causing my problem.  I created a pull request which restores the currents to their pre-MMU3 values, but I get the feeling this may need more work if the new values are meant for the MMU3 which has more efficient motors.

But hey, if you are having a problem like I was you can pull my fixed branch and build it yourself (or I can put the hex file I built and am using somewhere)

Posted : 14/02/2025 12:13 am
Share: