Closed edgauthier closed 2 years ago
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue was closed, because it has been already marked for 10 days with no activity.
It would be nice if PrintJobHistory could save the output of M503 (captured at the start of a print perhaps) to know what the printer firmware was configured for prior to executing any GCODE for a print. This would help in comparing settings from previous prints if changes were made to firmware settings (and aren't captured in the slicer settings).
Thanks for considering!