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

M600 in non-MMU mode now asks for confirmation before unloading #2142

Open
wants to merge 1 commit into
base: MK3
Choose a base branch
from

Conversation

ekr1
Copy link

@ekr1 ekr1 commented Aug 27, 2019

M600 now asks (yes/no) before unloading the filament.

All functionality of the command stays exactly the same - previously the user had to push the button. Now he can still just push the button and activate the default "yes". Then everything works as usual.

If the user instead selects "no", then no filament change is performed, and the print resumes immediately.

If MMU is installed, then nothing changes at all (the user was not prompted before, and is not prompted now).

While the yes/no question is up, the special logic for beeping, and for turning off the heater after a specific timeout, still work.

This gives the user a chance to opt-out of the filament change and be a bit more "dynamic" about this (for example, schedule the change ahead in a long print, and only do it if the old filament spool looks like it's not going to last).

A major secondary use of this change is that together with the filament-change feature of PrusaSlicer (which generates a M600 in user-selected layers) it is a very convenient and safe pause function: if the user does not actually want to change filament, but just to pause the print and move the nozzle head away at that layer for whatever reason (I do this frequently with creative manual support structures that I drop into a print physically; or for dropping in magnets and so on), he can now do this without the enforced filament unload/reload. The other choices (i.e., the "Pause" gcode) are much less powerful, and also would need manual manipulation of the gcode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant