Claudio Prezzi

Seems that this feature was broken at some point and nobody realized it, which probably means that nobody is using it anyways ;) I'll put it on the "todo list".

I do already have "some" job metrics on server side: Job started at Fri Feb 24 2017 18:24:26 GMT+0100 (Mitteleuropäische Zeit) Job finished at Fri Feb 24 2017 18:30:27 GMT+0100...

@cojarbi Where do we have an estimated time (preview) for the job duration in LW3? I only see a distance esimation. - It's not so eays to estimate how long...

Job stats from LW3 are back: 

I have an idea for the duration estimation, at least while the job is running. I could count how many queue lines was processed over a period (like 5s) and...

Right, could jump around but people are used to it from Windows ;)

@cojarbi Yes, that could be a trigger, but what if there is no Z change? Most Laser cutters don't have a Z-stage. The gcode generator could place a command into...

I would't use Z-moves for that, as this would not work on milling. It should be very easy to add a comment line to the gcode when a new pass...

@jonbev At the moment, the job is "finished" when the last line has been accepted by the controller. At this time, the controller planner queue still has some commands to...

I see two things of interest. First the estimated duration in the CAM tab and second the job progress in JOG. Instead of showing the queue length aboove the DRO,...