-
Notifications
You must be signed in to change notification settings - Fork 59
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
Color change support #278
Comments
Or, prompt for a new spool at the M600 gcode command. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
I don't think this should auto close. This seems like a valuable feature to include. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
Activity |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
Activity |
When I changed spool in the octoprint while changing filament, the plug-in only subtracted the used amount of filament from the last spool selected. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
When this can't solved with the MMU2 select Plugin (https://github.com/tkoecker/OctoPrint-Mmu2filamentselect), it would be interesting to support such changes with this plugin . (I haven't tested jet.) |
Is no one actively supporting this plugin anymore, this is an issue I have seen raised multiple times and all I see is the bot auto-mark for closure and never actually answers the question of why this doesn't work when its listed as a feature in the features list. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
It's a pity ... |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
reset, bot |
I fear ... #333 and hope we get a chance with our wish: OctoPrint/plugins.octoprint.org#1213 |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
This is like riding a dead horse ... that's really a pity. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
To be or not to be, that's the question... |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
Good things take time...but not so much. |
. |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
. |
FYI: new maintainer: https://github.com/dojohnso/OctoPrint-SpoolManager/ |
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days. |
This issue was closed, because it has been already marked for 10 days with no activity. |
When printing with multiple spools (color changes during printing), it is not possible to select correct filament.
When starting a print with color changes, I would expect the plugin to ask for all the spools to be used in sequence.
The text was updated successfully, but these errors were encountered: