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

NinjaBadger over 6 years ago

Right - before you do this have a think...

Do you use multiple tip angles in a program? Do you intend to check each one?
How long are your programs? There's a good chance you run a program and then it quits at the last probe or tip change.

How do you qualify? All in one go, or different probe at different times?

There's probably a better way to do this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
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
JamesMuz5689 over 6 years ago

Yes approximately 8 angles makes up the calibration routine.
No a single check on any of the angles (TIMES) will be sufficient, as the calibration cycle only takes 10 mins or so (so in the grand scheme of things, the minutes/seconds difference on the tip angles wouldn't make that much difference, when talking across a 12 hour period)
Part programs run times range from 5 to 15 mins
All tips used are calibrated together at the beginning of every 12 hour shift (all tips are calibrated for all variants of parts)

The whole idea is to prevent shifts missing tips calibrations, yet still measuring parts. We use the Inspect interface currently which ignores the tip out of cal prompt message

Having a error label forcing the program to stop (end of program label etc.) if that 12 hour period is exceeded is what I'm aiming to achieve.

Hope this makes sense

Thanks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
JamesMuz5689 over 6 years ago in reply to AndersI

V2016 at the moment. We use the Inspect interface at the moment which seems to bypass this alert.
Also this alert can be easily dismissed by the operators, allowing them to proceed measuring parts, which out of date tip cals.
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
JamesMuz5689 over 6 years ago in reply to AndersI

I will download 2018 R2 and investigate offline. Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
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
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
JEFMAN over 6 years ago

#5 here with assignments, maybe that could help...
https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-code-samples/29132-difference-between-2-dates-times-in-basic-script
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel