Some time ago I mentioned that I didn't like the way the run timer kept on running even if the process was stopped on an M1 (optional stop) wating for me to tend to the machine. Well, I was shot down by others saying that they thought waiting for the operator was part of the run time and they wanted to know the full time it took for the process (or something like that). I guess if you're charging by the hour for the whole job that's a good reason to keep it running. I guess everyone has their opinion so I just let it go.
I use the timer more to anticipate how long the a piece of the process is going to take by looking at something like how long a passs around a part is taking and then I can multiply by how many passes and figure out when to come back to check progress or change a tool etc...
Well, today I wrote a program with a subroutine and noticed that the timer started over every loop of the routine making the timer pretty useless for anything.
I guess I'm wondering if this simple feature of the program could be improved, perhaps with some operator options in setup or something.
Sage