hexagon logo
Register Sign in
  • Replies 14 replies
  • Subscribers 223 subscribers
  • Views 350 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
  • 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
Reply
  • 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
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement