71
General Mach Discussion / Re: Elapsed Time counter bug?
« on: November 13, 2013, 07:35:23 PM »
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
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