English
Login

Unload manually

#04506 (MMU)

Relevant for

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

What happened?

Implausible SuperFINDA sensor reading. This error occurs when the SuperFINDA sensor detects filament inside the Selector, but the MMU has no record of any filament being loaded. As a result, it cannot determine which filament position is loaded and cannot perform the unload automatically.

This often happens due to a malfunctioning or improperly calibrated SuperFINDA sensor.

Another potential cause could be if the filament was inserted into the selector manually, bypassing the menu/buttons, or restarting the printer during a load/unload operation before it was completed.

 

How to fix it?

  • Verify there is no filament in Selector and SuperFINDA sensor isn’t detecting a filament.
  • If filament is loaded, unload it manually or clear any obstructions triggering the SuperFINDA sensor.
  • Re-calibrate the SuperFINDA sensor.
    Also see the FINDA toubleshooting article.
  • Use only the menu on the printer to load or unload a filament during regular use. 
 

3 comments

Log in  to post a comment
TSve
I had this error and it turned out that the little screw locking the adjustment for the superfinda probe in place had become loose for unknown reason, so the probe had slowly fallen lower and lower until giving a false reading. I raised the probe until the red light came on and tightened the lock screw. Now the error is gone and printing works like normal.
W5ZEN
To calibrate the FINDA on the MMU3Find it at: https://help.prusa3d.com/guide/5-selector-assembly_357317 >>>>5. Selector Assembly     >>>> Step 10 Selector assembly: SuperFINDA probe   This fixed my issue when that error came up on my screen.
simisimis
I couldn't get rid of this error on my MMU3 freshly upgraded printer, eventually I checked the D shape hole where you can see FINDA and it was a tad too far. Once I aligned it, the error disappeared
Derik Whittaker
Thank you for this not.  I had this issue and this solution resolved it. 
Meo Tseto
Same her, except it was too close. Now it is working.
ovid
Same problem here on e new Mk4s MMU3 upgrade, this solution worked, thanks