hexagon logo
Register Sign in
  • Replies 23 replies
  • Subscribers 225 subscribers
  • Views 341 views
  • Users 0 members are here
Options
Related

Auto calibrate question

Dark_Prince
I am building a program for our operators that specifically calibrates our probes. We use 3 different probes, using a probe changer rack. I am implementing the use of password protection due to the frequent "fat-finger" occurences. I need a way to let operators calibrate as easy as possible. The company i work for requires the operators to calibrate at the beginning of every shift and we run the machines 24/7 with 4 shifts of operators. I have the calibration program built. I just can't find an answer for the meaning of this:

AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_DCC,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=YES

the last statement is "OVERWRITE_RESULTSFILE=YES. I assume I want to say YES. However, even when I had NO selected i could see the results files updated when i ran the program. Does anyone know what choosing yes or no does in this situation?
Parents
  • Thanks for the input. I really like acgarcia's naming convention for the pdf results. So if I have operators running autocalibrate, there will not be a warning message when the Stddev exceeds the limit? I like the idea using "if goto" statements to automatically recalibrate when std dev is too large, but not sure how to appropriately use it with multiple tips in a rack. Could I put an "if go to" statement directly after each auto calibrate statement, just before the next loadprobe statement?
  • in reply to Dark_Prince
    If your STDDEV exceeds the limit when auto-calibrating, an error will not appear. But the message will be present at bottom of calibration report text file.
    yup, you can even put IF_GOTO's within IF_GOTO statements, lol.
Reply Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement