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

AndersI over 6 years ago

Which version of PC-DMIS? In 2018 R2 you just set up the limits (F9 on the LOADPROBE command, button Setup...) and in the program add the command CHECKCALIBRATIONLIMITS/
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
AndersI over 6 years ago in reply to AndersI

The whole point of the CHECKCALIBRATIONLIMITS/ command is that it generates an error, which you can catch with ONERROR/ and jump to the end of the program (or call a calibration program). No way for the operator to circumvent that if you run in Operator or Protected Mode.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

AndersI over 6 years ago in reply to AndersI

The whole point of the CHECKCALIBRATIONLIMITS/ command is that it generates an error, which you can catch with ONERROR/ and jump to the end of the program (or call a calibration program). No way for the operator to circumvent that if you run in Operator or Protected Mode.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data