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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NinjaBadger
    replied
    We don't calibrate on any given frequency. We run a probe check every Monday. Any probes which have drifted get re-calibrated.

    (we have 2 x6 probe racks all full - calibration of the whole lot is between half a day and a day).

    Leave a comment:


  • louisd
    commented on 's reply
    produce evidence of extending the calibration interval. present it, get patted on the back for doing less work.

  • Darrollh
    commented on 's reply
    I wish we would do that. We calibrate everyday, every shift. I think its a waste of time.

  • louisd
    replied
    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.
    Last edited by louisd; 02-26-2019, 04:19 PM.

    Leave a comment:


  • JEFMAN
    replied
    #5 here with assignments, maybe that could help...
    https://www.pcdmisforum.com/forum/pc...n-basic-script

    Leave a comment:


  • acgarcia
    commented on 's reply
    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.

  • JamesMuz5689
    commented on 's reply
    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.

  • acgarcia
    replied
    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.

    Leave a comment:


  • JamesMuz5689
    commented on 's reply
    I will download 2018 R2 and investigate offline. Thanks.

  • AndersI
    commented on 's reply
    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.

  • JamesMuz5689
    commented on 's reply
    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.

  • JamesMuz5689
    replied
    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

    Leave a comment:


  • AndersI
    replied
    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/

    CheckCalibrationLimits.PNG

    Leave a comment:


  • NinjaBadger
    replied
    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.

    Leave a comment:


  • 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

Related Topics

Collapse

Working...
X