Brian,
After a bit of toying around, it seems to me that the internal clock variables are correct. By that I mean they are the same variables being used by MacMan. I checked all the variables, then I cycled the power on the machine, re-checked, and everything zeros out. This is the same way MacMan operates. So if you could get the operator to only use M00 and M01, you could simply write an M code macro and substitue that in your programs for M00 and M01. In your macro, record the time right before you read the M01 and add that variable each time to keep a running count of the cycle time and the stoppage time. The only issue is the Single Block button. There isn't a way to record this that I know of. Add this to what you have, and I think it will take care of everything you need. If only I could find out where all of the other information was stored, you wouldn't need to have the operator run anything else. On the zero set data, we actually write all of our data through a calculation program based on the probing we do, you should be able to write that stuff out no sweat. I have never used the write option, but couldn't you set the file name based on the part number? We have a folder on the network for our E control, so it could actually maintain a large amount of history before you needed to worry about it.
Bala,
As you read above, these variables all are in reference to the last power on of the machine. I think you will need something special to actually be able to see what time it is.
You CAN do anything, if you REALLY want to, but how many people really want to?
Kyle