Did RRF stop writing print time to gcode files?
-
I am trying to gauge print time estimates with actual print time but I can't seem to get the actual print time for completed jobs anymore. I dimly remember that was written to the end of a gcode file in the past. Am I hallucinating, has this feature been removed? My usual code spelunking has proven inefficient this time.
-
@oliof actual print time has never been written to GCode files. Simulated print time is.
-
@dc42 ok, hallucination then (-:
-
@dc42 what's stopping actual being written at the end of a print? Could this make the wishlist?
-
Not sure what format is expected, but you can easily enough append the info to the file by putting something like this is stop.g
Edited for better readability
if (job.lastFileName != null) var numHours = floor({job.lastDuration}/3600) var numMins = floor(({job.lastDuration}-var.numHours*3600)/60) var numSecs = mod({job.lastDuration},60) var thisString = ";Print time = " ^ var.numHours ^ "hrs " ^ var.numMins ^ "min " ^ var.numSecs ^ "secs" echo >>{job.lastFileName} "" echo >>{job.lastFileName} ";Last printed:", state.time echo >>{job.lastFileName} var.thisString
note as written it will append the info if stop.g was run after a file was cancelled or aborted.
I have another post about that as it seems to be a bug. -
@jay_s_uk yes we could write last printed time to the end of the file, although if you adjust the printing speed during the print as I often do then the value is less useful than the simulated time.
-
@dc42 I personally don't. It would be appreciated if you could. Thanks