[Feature] Filament cost entity

[coltography]

Describe the feature

I was wondering since a few entities like print weight, print length, etc are now being pulled from the 3mf file, if the filament cost could also be used in an entity?

Right now I have a very crude python script that runs on automation to pull the gcode and extract the estimated cost from each print, then updates an input number. But I'm totally lost on how to implement such a thing in this add-on.

It's a unique sort of data point to be able to pull because you can track your filament cost over time.

For example at the very end of the gcode file sliced with orca slicer we get:

; filament used [mm] = 2212.59
; filament used [cm3] = 5.32
; filament used [g] = 6.76
; filament cost = 0.11

What device is this for?

P1S

Other Information

No response

[AdrianGarside]

It would be much better if Orca puts it into the cheaper files like slicer_config.json or plate_n.json. Hmm, there is something in project_settings.config although I'm looking at a local 3mf not one sent to the printer so maybe that's not in the printer's 3mf file.

[coltography]

I pulled the 3mf file off the printer and in project_settings.config I do see the filament_cost but that's for that entire roll (which is set in orca slicer for each filament profile)

For example this roll I paid $16.80 for:

  ],
    "filament_cost": [
        "16.8"

This could then be calculated against the print_weight to get an exact cost of that print? If that's even possible.

[AdrianGarside]

Yes, that's my plan. If we can properly associate that with the correct filament if an ams remap has occurred then we can do the conversion easily enough,.

[coltography]

I always forget how the AMS adds another layer of complexity I don't even think about. For my flow I just have the 1 external spool to consider.
I'll be forever grateful if this gets added some day!

[AdrianGarside]

There’s a separate spool card now. It may still only be in the beta releases.

[coltography]

Understood, I'll be happy to test. Unfortunately even attempting to figure out how to contribute to this is way over my head, so I'm willing to help test at the very least.