-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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
Filament change....Did it work? #5173
Comments
My thinking is the LCD Screen should stay in a filament change control type screen until the filament change is completed. That would make more sense to me. |
That would be great as long as it went to that screen as soon as the filament change menu were selected. As it is now, nothing happens. |
That's a good point. Obviously we need to wait for the current move to complete, so it's not possible to go to filament change immediately, but a message " |
It so happens that the first screen for filament change says:
…so the above patch jumps straight to that screen, which will not time-out to the status screen. |
Could it be shorter, like "Waiting for filament change"?
|
@Barrocas It is what it is, and has already been translated into all the supported languages. You can always customize it in your personal copy. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
With filament change enabled, there is a menu option available in the Tune menu while printing to change the filament. It works, but nothing happens when you click the menu item. Thinking that nothing happened I selected the option again and didn't know until i turned on the serial that it was Enqueueing the M600 command. I think it would be great if upon selecting the change filament command the menu returned to the status screen and a message indicating that filament change has been Enqueued shown on the screen. I imagine this is an easy fix...Thoughts?
The text was updated successfully, but these errors were encountered: