Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsuccessful filament loading after IR sensor positive detection #1938

Closed
castayuelas opened this issue Jun 19, 2019 · 4 comments
Closed

Unsuccessful filament loading after IR sensor positive detection #1938

castayuelas opened this issue Jun 19, 2019 · 4 comments

Comments

@castayuelas
Copy link

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.

@Demolux
Copy link

Demolux commented Jun 19, 2019

You can change the retraction distance in mmu.cpp, see here:

#1935

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.

@Kylra
Copy link

Kylra commented Jul 8, 2019

Decreasing the retract distance in mmu.cpp solved this issue. 52 was too high.
It unloaded the filament.

static bool can_load()
current_position[E_AXIS] += 60.0;
current_position[E_AXIS] -= 46.0; // old 52.0

@github-actions
Copy link

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.

@github-actions
Copy link

This issue has been closed due to lack of recent activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants