You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I didn't see anything in the readme about this, but I'd like to be able to track usage across filament spools. I'm not seeing anything that indicates a spool gets updated when it runs out, or that the filament contributed from said spool is accounted for after the print has completed. I'm assuming if I change spools through my print server (I'm using Octoprint), that Spoolman takes that as being removed and replaced, thereby taking the entire build volume only from the last spool loaded.
Describe the solution you'd like
I'm not a developer, but I'm making an assumption that the filament runout signal that causes the printer (in this case, a Prusa XL) to pause and await replacement can also be read by Spoolman, but I don't know if it's reasonable to calculate the total build volume in that paused state to credit against the currently loaded spool.
Describe alternatives you've considered
I am currently manually zeroing out the first spool and adding it's weight back to the final spool.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I didn't see anything in the readme about this, but I'd like to be able to track usage across filament spools. I'm not seeing anything that indicates a spool gets updated when it runs out, or that the filament contributed from said spool is accounted for after the print has completed. I'm assuming if I change spools through my print server (I'm using Octoprint), that Spoolman takes that as being removed and replaced, thereby taking the entire build volume only from the last spool loaded.
Describe the solution you'd like
I'm not a developer, but I'm making an assumption that the filament runout signal that causes the printer (in this case, a Prusa XL) to pause and await replacement can also be read by Spoolman, but I don't know if it's reasonable to calculate the total build volume in that paused state to credit against the currently loaded spool.
Describe alternatives you've considered
I am currently manually zeroing out the first spool and adding it's weight back to the final spool.
Additional context
No response
The text was updated successfully, but these errors were encountered: