malnvenshorn / OctoPrint-FilamentManager

OctoPrint plugin to manage your filament inventory
GNU Affero General Public License v3.0
131 stars 60 forks source link

Add support for multiple tools (Prusa MMU/MMU2) #157

Closed trv-in-3d closed 5 years ago

trv-in-3d commented 5 years ago

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

trv-in-3d commented 5 years ago

Just starting using the PRUSA Multi Material Unit. It allows printing from up to 5 filaments through a single extruder. It would be great if Filament Manager would allow be link multiple spools in the database to the gcode tool (T0,T1,T2,T3, etc). This way a multi-color print using tool 2 and tool 4 would correctly decrement the associated two spools.

This would probably need to be a new "mode" for Filament manager. Single Filament Mode (as currently written) that requires a single spool to be selected, or Multi Filament Mode, where you have to specific the number of slots, link a spool to each slot, and probably define the GCODE that would be used to activate that spool. In this example, the GCODE would be the Tx commands - but making this a parameter may enable Filament Manager to work with a variety of other multiple-filament solutions.

malnvenshorn commented 5 years ago

This plugin supports multiple extruders you just have to configure OctoPrint accordingly. Or do I miss something?

Found a related ticket, see #84

trv-in-3d commented 5 years ago

The multi material unit from prusa works as an auto loader/unloader. Octoprint is correctly configured for the multiple filaments, via a single extruder. In this setting Filament Manager only offers (correctly) an "extruder 0" option to assign a spool against.

I am asking for a feature to assign spools against gcode "tools", not "extruders".

Gcodes T0, T1, T2 ... will result in different spools being consumed and I cant find a current way that filament manager will track that.

Or am I still missing something?

Thank you for this add-in. I fully appreciate it's current capabilities and find it very useful.

Sent from my phone. Please pardon the brevity and likely typos.


From: Sven Lohrmann notifications@github.com Sent: Sunday, March 24, 2019 5:26:14 PM To: malnvenshorn/OctoPrint-FilamentManager Cc: trv-in-3d; Author Subject: Re: [malnvenshorn/OctoPrint-FilamentManager] Add support for multiple tools (Prusa MMU/MMU2) (#157)

This plugin supports multiple extruders you just have to configure OctoPrint accordingly. Or do I miss something?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmalnvenshorn%2FOctoPrint-FilamentManager%2Fissues%2F157%23issuecomment-476001760&data=02%7C01%7C%7C2ee1ed24719e492b061008d6b09f5885%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636890595758180776&sdata=CG1p8Hx9GYfK7YhpQdZOIwYGpxOwlPJHRkuuKojK2wI%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAuoHLhv-kOFMKzWCYB1_O9-zslGCUV_fks5vZ-12gaJpZM4cFunZ&data=02%7C01%7C%7C2ee1ed24719e492b061008d6b09f5885%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636890595758190787&sdata=rNrGxJ8dn5BMYt235GKt%2B4fuHn3SN3Sc4qa8cQM4pFg%3D&reserved=0.

malnvenshorn commented 5 years ago

Octoprint is correctly configured for the multiple filaments, via a single extruder.

If you can assign only one spool you haven't configured it correctly. If I set the extruder number to two and enable the shared nozzle flag I can assign spools to two different tools in the sidebar. This is what you have to do as described in the related ticket.