Don't break the calibration chain!
I am posting this in hopes to have it made into a sticky since I see this issue arise a lot in the Vision section. This document perfectly explains the calibration process for calibrating offset with a Vision primary system with TTP.
Does this autocalibrate routine fully automate the process or does the vision-to-ring step still require three manual hits to locate the ring? I have tried this same routine and it always requires the locating hits if I choose Yes to has moved, even if I choose DCC in the Parameter Set. It would be ideal to get the full process automated. If the artifacts are places roughly in the same place each time it doesn't seem all that necessary to find it with manual hits don't you think?
I have a question on this. May I know what the last block of this code does? This is required for me to use in my calib routine. Thanks for your help in advance!!.
LOADPROBE/POINT3 OPTIV TIP/TIP1, SHANKIJK=0, 0, 1, ANGLE=0 AUTOCALIBRATE/PROBE, PARAMETER_SET=Sphere_Cal3, QUALTOOL_MOVED=NO, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO BEGIN AUTOCALIBRATE RESULTS FOR PROBE POINT3 OPTIV USING SET Sphere_Cal3 Probe file=POINT3 OPTIV Date=9/26/2016 Time=11:06:16 AM TIP1 THEO X -55.5000 Y 0.0000 Z 84.0000 D 0.3000 TIP1 MEAS X -55.5142 Y -0.0966 Z 84.2605 D 0.2879 StdDev 0.0008 END AUTOCALIBRATE RESULTS FOR PROBE POINT3 OPTIV USING SET Sphere_Cal3
I have a question on this. May I know what the last block of this code does? This is required for me to use in my calib routine. Thanks for your help in advance!!.
LOADPROBE/POINT3 OPTIV TIP/TIP1, SHANKIJK=0, 0, 1, ANGLE=0 AUTOCALIBRATE/PROBE, PARAMETER_SET=Sphere_Cal3, QUALTOOL_MOVED=NO, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO BEGIN AUTOCALIBRATE RESULTS FOR PROBE POINT3 OPTIV USING SET Sphere_Cal3 Probe file=POINT3 OPTIV Date=9/26/2016 Time=11:06:16 AM TIP1 THEO X -55.5000 Y 0.0000 Z 84.0000 D 0.3000 TIP1 MEAS X -55.5142 Y -0.0966 Z 84.2605 D 0.2879 StdDev 0.0008 END AUTOCALIBRATE RESULTS FOR PROBE POINT3 OPTIV USING SET Sphere_Cal3
What you asking? That is the probe calibration results to the sphere.
I have a question on this.
May I know what the last block of this code does?
This is required for me to use in my calib routine.
Thanks for your help in advance!!.
LOADPROBE/POINT3 OPTIV
TIP/TIP1, SHANKIJK=0, 0, 1, ANGLE=0
AUTOCALIBRATE/PROBE, PARAMETER_SET=Sphere_Cal3, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO
BEGIN AUTOCALIBRATE RESULTS FOR PROBE POINT3 OPTIV USING SET Sphere_Cal3 Probe file=POINT3 OPTIV Date=9/26/2016 Time=11:06:16 AM TIP1 THEO X -55.5000 Y 0.0000 Z 84.0000 D 0.3000 TIP1 MEAS X -55.5142 Y -0.0966 Z 84.2605 D 0.2879 StdDev 0.0008 END AUTOCALIBRATE RESULTS FOR PROBE POINT3 OPTIV USING SET Sphere_Cal3
This is simply the results of your probe calibration. Theo is the theoretical position of your probetip center and the measured is...well, the measured values of your probe tip center. if you want to disable it, i think you can change "SHOW_SUMMARY=NO"
A confirmed bug by Hexagon in 2019 R2 (JIRA 180393), pertains to vision-to-tactile auto calibration. Program, as written, works in 2019 R1 and older releases, but does not work in 2019 R2.
From the awesome vision people in the UK:
"I am able to reproduce the issue you are seeing... once the vision probe completes the calibration the machine just stops moving.. the execution timer continues but nothing else happens. I will see if I can identify anything obvious but this looks like a bug introduced in 2019 R2."
"I actually made a second discovery today with this issue. After the machine stops (once the vision probe cal is complete ) I went ahead and stopped execution.
Pc-dmis appeared normal.. so I executed the routine again expecting it to perform the vision probe cal again, instead the machine moved over to the rack and picked up the tactile probe, it moved to the machine centre and then just stopped with the execution dialog counting…. Again cancel and execute.. this time it dropped the probe off, before picking it up again and pausing the machine."
I will double check that is issue is still valid in R2 SP2, but I have a feeling it will be.
