You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After 3.7.1 version mmu2 filament loading into the nozzle has very low percentage of success. After load the filament into the nozzle and get a positive IR sensor detection the filament is retracted, mmu2 try to load again the filament with the same result geetting a message that mmu2 required attention. Usually , after intervention in the mmu2 but not doing any change , the mmu2 try to load the filament into the nozzle with success.
The only way I found to solve this in uploading version 3.6.0 again and I am able to print again without issues.
The text was updated successfully, but these errors were encountered:
However, the given values should be ok with an unmodded printe/hotend and if the filament was removed via unload beforehand. If nothing is stuck in the e3ds filament path, this cannot be the issue.
Instead, look at your idler and the IR-sensor calibration. The idler has to rotate quite freely and without any wobble (I inserted a brass tube for the screw-joint to remove wobble). The filament sensor maybe setup so tight that it detects a "no filament" just by bondtech-gear wobble.
This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.
After 3.7.1 version mmu2 filament loading into the nozzle has very low percentage of success. After load the filament into the nozzle and get a positive IR sensor detection the filament is retracted, mmu2 try to load again the filament with the same result geetting a message that mmu2 required attention. Usually , after intervention in the mmu2 but not doing any change , the mmu2 try to load the filament into the nozzle with success.
The only way I found to solve this in uploading version 3.6.0 again and I am able to print again without issues.
The text was updated successfully, but these errors were encountered: