search

OllisGit / OctoPrint-FilamentManager

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

G Code Filament Selection #71

Open demitrix opened 3 years ago

demitrix commented 3 years ago

PrusaSlicer allows for custom start G-code per filament. Using this filament manager could automatically select the correct spool. This would be useful for print jobs started from outside OctoPrint when changing filaments.

ldiegos commented 3 years ago

Hi, I like this idea.

You could add some program lines to search some like: ;FILAMENT_MANAGER: {filament_settings_id[0]}

In my case, this line generate something like: ;FILAMENT_MANAGER: Warhorse-Black-PETG@Asun3Pro

Where @Asun3Pro is the name of the printer. This is the way i identify which filament belongs to each printer, but could be replaced with some other pattern that your could ignore and only take into account of "Warhorse-Black-PETG"

Thank you so much in advance.

OllisGit commented 2 years ago

This feature is already tracked in the SpoolManager-Backlog (https://github.com/OllisGit/OctoPrint-SpoolManager/projects/1) ... unfortunately for you, this is tracked in the column "mid-term". So it will take a while to complete.

wernight commented 2 years ago

Adding here my use case: Improve my change filament macro (using Klipper but that shouldn't be relevant) so that when I run it, it tells the Spool Manager to set that no filament has been selected.

Another cool thing would be to use the camera (frequently connected to OctoPrint) so scan the QR code and set the new spool (if any). This could easily also be linked to an RFID reader calling the that QR code URL.

OllisGit commented 2 years ago

fyi: @wernight "scanning" spools is also already tracked: https://github.com/OllisGit/OctoPrint-SpoolManager/projects/1#card-27695769

badnetmask commented 5 months ago

So, I came here because I found issue#110, which is what I wanted to track. Looking at the GCODE generated by Prusa Slicer, I have the following lines.

;COLOR_CHANGE,T0,#E8AA2A
M600

So it seems like Prusa already injects the color I have selected in the UI, even though it doesn't necessarily matches the color code of the filament. Maybe that helps?

Also: I tried looking at the project list under the "mid-term" column and could not find this request. So where is it being tracked?