Print job duration with M117

dportero

I am running version 2.03RC3 (can't update for a few reasons). I was wondering if there was a way to print the job duration using M117? I really miss the ability octoprint has to go back and see how long a job actually took and this seems like the only partial solution. I would love it if it could add it to the metadata of a job.

Thanks!

Phaedrux

If the slicer knows and has that accessible as a placeholder token, you can set gcode on layer change or whatever your slicer calls it for whenever you want it to report it.

Something like

M117 [print_duration]

Without knowing your slicer it's hard to say more.

As for adding that to saved information about the gcode file, nothing like that exists right now except I think if you run a simulation, it will save the simulated time to the file. Though the slicer itself will often add it's own estimate.

dc42

@dportero said in Print job duration with M117:

I am running version 2.03RC3 (can't update for a few reasons). I was wondering if there was a way to print the job duration using M117? I really miss the ability octoprint has to go back and see how long a job actually took and this seems like the only partial solution. I would love it if it could add it to the metadata of a job.

Thanks!

That's easily done in RRF3, but not in RRF2. However, you could use M117 commands in the slicer start and end GCode to print messages when the print starts and ends; then if you monitor the print using DWC the console output will show those messages along with time stamps, from which you can calculate the duration.

dportero

@dc42

If I am not always at the computer it sleeps and DWC reconnects so all messages are lost. Is there a way to save them somewhere?

Phaedrux

You may be able to capture it with the logging function

https://docs.duet3d.com/en/User_manual/Troubleshooting/Logging