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
Context
Besides managing spools and available filament, the biggest challenge in my workflows is managing process parameters. With multiple printers, you can use the same spool of filament, but likely not the same process parameters, such as:
Pressure Advance
Flow
Hot-end Temperature
Z-Offset
These values typically differ from printer to printer and might even vary between a 0.4 nozzle and a 0.6 nozzle.
Describe the solution you'd like
Add a capability to create "Printer Objects" that can hold and manage the above process parameters and can be associated with a spool.
Describe alternatives you've considered
Currently, I work around this by adding "Extra Fields" in the convention parameter_nozzleDiameter_printername, e.g., pa_04_voron.
Outlook
Once a proper slicer integration is available (e.g., Orca is WIP), all relevant parameters can be fetched from Spoolman.
The text was updated successfully, but these errors were encountered:
Context
Besides managing spools and available filament, the biggest challenge in my workflows is managing process parameters. With multiple printers, you can use the same spool of filament, but likely not the same process parameters, such as:
These values typically differ from printer to printer and might even vary between a 0.4 nozzle and a 0.6 nozzle.
Describe the solution you'd like
Add a capability to create "Printer Objects" that can hold and manage the above process parameters and can be associated with a spool.
Describe alternatives you've considered
Currently, I work around this by adding "Extra Fields" in the convention
parameter_nozzleDiameter_printername
, e.g.,pa_04_voron
.Outlook
Once a proper slicer integration is available (e.g., Orca is WIP), all relevant parameters can be fetched from Spoolman.
The text was updated successfully, but these errors were encountered: