How about putting timestamps in the console logfile so the user can see how long each piece of his job took? Just grab milliseconds since start and pre-pend each console entry with it.
@AutoDoc When you say “each piece” of a job, what are you referring to? gSender already shows the run time for each file, so I am assuming you are referring to some other period of the run.
Sorry for the slow reply. If you timestamped each line (piece) in the log, the user could see how long each individual command took which might help him to refine his g-code.
Interesting thought. I was just wondering about this. For example, in Lightburn, I have it write out a CSV of every file I’ve run. It gives datetime/device/filename. That too would be good if there was a start/finish time or just overall elapsed time for a file just to help keep track of a job. Many times I’ve been sitting there running a job wanting to keep track of how long it took and then when it ends, the times are cleared.
1 Like