Auto calibrate question

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

Dark_Prince over 7 years ago

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Dark_Prince over 7 years ago

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

louisd over 7 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
acgarcia over 7 years ago in reply to Dark_Prince

After the cal program is complete, the probe moves to the back of the machine so operators can load parts. So operators clean the probe and cal sphere, click execute and walk away. The come back and if the probe is in the back of the machine, means all probes passed calibration and a report was generated with the results. Very rare that the probe is bad and it repeats after 2 calibrations.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
acgarcia over 7 years ago in reply to Dark_Prince

Yes you can put multiple if go to after each probe and tip. We used to have a probe rack but we narrowed it down to this single star probe so we don't use the rack anymore. I would definitely use a if go to right after the probe is done calibrated to make sure everything is good before changing probes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel