SoftFever / OrcaSlicer

G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)
https://discord.gg/P4VE9UY9gJ
GNU Affero General Public License v3.0
5.89k stars 670 forks source link

Print Log with Tagging (also filament tracking) #5766

Open g3gg0 opened 1 week ago

g3gg0 commented 1 week ago

Is there an existing issue for this feature request?

Is your feature request related to a problem?

I am now and then printing stuff for friends, for my work, for the house or for kids. Especially when printing a few parts for friends or I simply want to check where my filament has gone, the slicer could have helped me with (relatively) low effort.

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

The slicer's "print plate" button is a good place to also add some log entry, be it some CSV, or even a small DB, HTML or even XML (with XSLT for visual appearance) with history of what has been printed.

Lets check this great and concise statistics screen: grafik

When I now could simply have a dropdown / list field where I could enter "Johns MPCNC" or "Toys" and it would write these values into a file, that would be great.

Maybe this is also good to be combined with #4840 which also aims towards "being aware" of the costs and print time.

Dont get me wrong - It's a slicer, not SAP. But it's about properly exporting the metadata of a print as OrcaSlicer even knows the serial number of the (currently) inserted filament spool.

Thanks for your great work!

Describe alternatives you've considered

  1. i could copy a screenshot of every print job
  2. or write the numbers manually

still i would be missing the spool S/N and probably the thumbnail of the print

Additional context

No response

kylek29 commented 1 week ago

Certain values are exposed in the G-Code placeholders, you could use a post-processing script call to extract those and push them to a database. It wouldn't show in the UI, but you'd at least get your stats out in a more automated way.

I know there's codes for:

But I don't think they expose any of the slicing statistics in the breakdown nor the per-object breakdowns.