For an open source system I think it’s mainly just a matter of when. Granted there are currently complaints with the licensing for the system, so that might hurt/kill traction.
Support in Klipper sounds amazing. There could be open repositories of printing parameters. Not 100% sure how Klipper would pass the info to the slicer but that seems solvable.
I’ve not user Klipper in a long while, but would it not suffice if Klipper knew 'Spool has 100m Filament left, print says it takes 110m, throw an error/require user confirmation to continue '?
ikirin@feddit.org 3 weeks ago
Definitely! Mostly looking forward to see how/if other printers (especially Klipper) will support it
Zikeji@programming.dev 3 weeks ago
For an open source system I think it’s mainly just a matter of when. Granted there are currently complaints with the licensing for the system, so that might hurt/kill traction.
Kuro@feddit.org 3 weeks ago
I mean it’s fairly new and the maintainer seems to be open for a license change.
inzen@lemmy.world 3 weeks ago
Support in Klipper sounds amazing. There could be open repositories of printing parameters. Not 100% sure how Klipper would pass the info to the slicer but that seems solvable.
ikirin@feddit.org 2 weeks ago
I’ve not user Klipper in a long while, but would it not suffice if Klipper knew 'Spool has 100m Filament left, print says it takes 110m, throw an error/require user confirmation to continue '?