hexagon logo
Register Sign in
  • Replies 14 replies
  • Subscribers 223 subscribers
  • Views 359 views
  • Users 0 members are here
Options
Related

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

JamesMuz5689
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
  • We calibrate once monthly. We have in-process inspection requirements for all product being produced, every 6 hours, running production 24/7. If your routines are robust, there's no probe wear to be concerned with (plastic parts here), and there's no crashing going on, probe calibration can stay accurate for months. If your site policy is to arbitrarily calibrate every 12 hours, I would suggest doing a study to quantitate how far you can extend that frequency before your probe calibration would start to affect product acceptance, and NEED to be calibrated. I'm planning to conduct a study to justify bimonthly calibration soon.
  • in reply to louisd
    I wish we would do that. We calibrate everyday, every shift. I think its a waste of time.
Reply Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement