[FEATURE REQUEST] Track total prints / Prevent reprint for serialised gcode

[murk-sy]

Printer model

All

Describe the feature

This feature request combines 2 different features that would rely on the same base functionality.

Track total prints

For a user making a larger amount of parts, re-starting an already finished file is more often than not the most convenient way to go about it. While scheduling jobs in connect is an option, I think that a fairly power-user type thing to do with advance planning needed. Honestly, for a lot of recurring parts, I generally just start the print from the physical interface. When printing a job with an odd number of mixed parts, it can get difficult to track how many have been printed, and sometimes, especially for really common parts, having some sort of a count would be helpful.

Prevent reprint for serialised gcode

I don't actually know how common printing parts with serial number embedded is, but it was brought up in the past at the very least.

• Crazy idea: print serial numbering with fs_emboss PrusaSlicer#7695
• Add object serial number/revision when sliced PrusaSlicer#4023

Expected functionality

Track total prints in gcode file

1. On print start, a variable "print_start_count" is increased / set to 1.
2. On print successfully completing, a variable "print_completed_count" is increased / set to 1.
3. On print end screen (and on gcode preview) total number of completed prints (and non-completed: stops, fails, etc) is displayed if 1 or more

Prevent reprint for serialised gcode

1. On print start, a variable "print_start_count" is increased / set to 1.
2. On print successfully completing, a variable "print_completed_count" is increased / set to 1.
3. On print end screen reprint is disabled
4. When opening the gcode file preview, text "Print completed" is displayed
5. When trying to start the print, a warning is thrown that the print job is serialised has already been completed

Notes

• Ideally, this information would be saved in a file that is not the gcode file itself, but quite often you will reprint a file with minor changes, which can result in exact same filename.
• Identifying gcodes by slice time down to the second and a randomly generated string/hash/something would likely be more reliable than using the filename and make collisions near impossible. An example would be 20241123125237-219654 which is still mostly human readable and not too long (if not very efficient)
• Connect was not a consideration, but by using the above option it should be possible (and relatively simple) to track jobs even if they are renamed on individual printers for whatever reason. This way, a long term and resource unintensive way of counting prints can be used.
• This would of course identify gcode and completely ignore whatever is actually inside of it. It could not be directly used to count total parts printed, but could be easily extrapolated by the user once the filenames are displayed.

[github-actions]

Thank you for your contribution to our project. This issue has not received any updates for 60 days and may be considered "stale." If this issue is still important to you, please add an update within the next 7 days to keep it open. Administrators can manually reopen the issue if necessary.

[murk-sy]

Bump