Comparing the PROBEDATA("TIME") vs SYSTEMTIME for Calibration time limits

Looking for some help in regards to the coding for the above.

I want to enforce a 12 hour time limit on calibrations, i.e if the SYSTEMTIME elapses 12 hours from the PROBEDATA time, a label in the program forces it to the bottom of the program, preventing any further measurements.

I can return the active PROBEDATA("TIME") and current SYSTEMTIME string values no problem

Its just the comparing of the 2 raw elements, where I'm struggling.

Any help or ideas would be appreciated.

Thanks in advance

Parents

acgarcia over 6 years ago

Do you have an autocal program? I have my guys run the autocal program before each shift (2 twice a day). It also prints a report at the end.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

acgarcia over 6 years ago

Do you have an autocal program? I have my guys run the autocal program before each shift (2 twice a day). It also prints a report at the end.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

JamesMuz5689 over 6 years ago in reply to acgarcia

Yes we have an auto cal program, which is run before each shift also (x2 per day).
It also out put a .pdf with STDDEV/OUTTOLS etc.....

A more robust procedure is required though, to eliminate any human error of missing the calibration for a shift.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
acgarcia over 6 years ago in reply to acgarcia

There is another thread that asked about this recently, i don't think they found a solution. They were looking for something that would not allow operators to run a program unless the probes were recalibrated "unlocking" access to programs so to speak.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel