Could someone else please try the program below.
I find that the elapsed time counter only progresses during the rotary move (which is about 2 seconds on my machine). After that it stalls for the rest of the program.
I'm using V3.042.040
Program works fine other than that. It's a simple program to take the drudgery out of cutting a gear.

G1F1
G1Y0
M1 (RELEASE ROTARY LOCK)
G91
G1A1.5F1
G90
M1 (LOCK ROTARY LOCK)
G1Y-.02F1
G1X0
G1X2F10
G1Y-.04F1
G1X0
G1X2F10
G1Y-.06F1
G1X0
G1X2F10
G1Y-.08F1
G1X0
G1X2F10
G1Y-.083F1
G1X0
G1X2F10
G1Y0F1
M30


Thanks
Sage

The time counter stops counting when the last of a gcode file is loaded into the buffer (I think), not when the last command is executed.
John Champlain

Hmmm.
If that's true then I guess that would make the counter pretty useless.

Not sure if that's true. I write a lot of short programs and I've never noticed the time stops. But then I may not have paid much attention. I'll have to search down a few and try them.

(did so in next post)

Sage

Yes.
It appears you may be correct.
A simple program like.
G1 X 1000 F1
runs but no timer action.

This is not good.
Begs the question then what part of a LONG program is actually being timed.

I've had issues with this timer in the past in that it keeps running during M1's which I hate because it does not reflect the actual time the cutter is doing something - or more that it includes the time I choose to do nothing before pressing the start button again. But I was out voted because I guess some people like to consider time as money and want to know how much time the program takes in all.
But this isn't good. If one has a large buffer then if a  very time consuming portion of the program is at the end then it is not even timed.

I would consider this something that needs to be re-vamped in Mach 4 - NO???

Sage

So Brian:

Is this something that will be corrected in Mach 4??

Sage