Auto Calibration

For "Auto Probe Calibration" . so i inserted below command. but while execution it calibrate angles, which are all used in this probe. i need to run only angles which are used in this program. how to set "Parameter Set' to calibrate angles used in this program?
i am using PC-DMIS 2019R2.

STARTUP =ALIGNMENT/START,RECALL:USE_PART_SETUP,LIST=YES
ALIGNMENT/END
MODE/MANUAL
PREHIT/0.1
RETRACT/0.1
MOVESPEED/ 100
SCANSPEED/100
FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
LOADPROBE/PROBE_4
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO

Parents

acgarcia over 4 years ago
acgarcia - I've been looking for this for awhile. We have out master calibration program and one other program with a calibration in the middle. What I would like to do is have the program stop and put out a comment stating that that the calibration has failed and asked if they would like to re-run it. I can't seem to figure out how to get the cal results into a variable. Any thoughts?

Thanks in advance.

Thoughts? Yes.

All I do is use a variable for each probe/angle to check the standard deviation of the tip. then I use logic to see if the results are larger than or equal 0.0005" to repeat which usually fixes things. Here is one of my star probes. See below.

AUTOCALIBRATE=LABEL/ AUTOCALIBRATE/PROBE, PARAMETER_SET=Star_Calibrate, QUALTOOL_MOVED=YES_DCC, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO BEGIN AUTOCALIBRATE RESULTS FOR PROBE VC0022 STAR USING SET Star_Calibrate Probe file=VC0022 STAR Date=10/3/2017 Time=6:02:09 PM Dixie Sphere CENT X 21.0250 Y 9.8345 Z -12.3495 D 0.7500 T1A0B0 THEO X 0.0000 Y 0.0000 Z 8.2262 D 0.1969 T1A0B0 MEAS X -0.0296 Y -0.0223 Z 8.1695 D 0.1948 StdDev 0.0002 T2A0B0 THEO X -0.9252 Y 0.0000 Z 7.1927 D 0.0787 T2A0B0 MEAS X -0.9491 Y -0.0197 Z 7.1290 D 0.0770 StdDev 0.0002 T3A0B0 THEO X 0.0000 Y -0.9252 Z 7.1927 D 0.0787 T3A0B0 MEAS X -0.0243 Y -0.9461 Z 7.1275 D 0.0765 StdDev 0.0003 T4A0B0 THEO X 0.9252 Y 0.0000 Z 7.1927 D 0.0787 T4A0B0 MEAS X 0.9035 Y -0.0166 Z 7.1416 D 0.0769 StdDev 0.0002 T5A0B0 THEO X 0.0000 Y 0.9252 Z 7.1927 D 0.0787 T5A0B0 MEAS X -0.0207 Y 0.9022 Z 7.1400 D 0.0769 StdDev 0.0002 END AUTOCALIBRATE RESULTS FOR PROBE VC0022 STAR USING SET Star_Calibrate LOADPROBE/VC0022 STAR ASSIGN/STD1=PROBEDATA("STANDARDDEVIATION","T1A0B0") IF_GOTO/STD1>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD2=PROBEDATA("STANDARDDEVIATION","T2A0B0") IF_GOTO/STD2>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD3=PROBEDATA("STANDARDDEVIATION","T3A0B0") IF_GOTO/STD3>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD4=PROBEDATA("STANDARDDEVIATION","T4A0B0") IF_GOTO/STD4>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD5=PROBEDATA("STANDARDDEVIATION","T5A0B0") IF_GOTO/STD5>=0.0005,GOTO = AUTOCALIBRATE

I also have a comment in the beginning of the program to have the operator take off the star probe and clean it with the gum stuff to clean the module and cmm head contacts.

So if everything works out well, it goes to a timed operator comment saying the cal was successful and then the probe moves to the back of the machine ready for parts.

Then you can put in a counter like CALCOUNT=CALCOUNT+1 so like if it automatically repeats more than once, (meaning you've calibrated twice and the results are still not good.), then human intervention is needed so then it will go to not timed operator comment say to seek help. Maybe a probe or 5way is loose or dirty or bent or something. I also have a backup star probe under the CMM so they can just replace it, calibrate the new star probe and continue running until I can asses the probe causing problems.

1 time I was called in because the machine would not calibrate and a ruby had fell off one of the probes.

Let me know if this helps.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

acgarcia over 4 years ago
acgarcia - I've been looking for this for awhile. We have out master calibration program and one other program with a calibration in the middle. What I would like to do is have the program stop and put out a comment stating that that the calibration has failed and asked if they would like to re-run it. I can't seem to figure out how to get the cal results into a variable. Any thoughts?

Thanks in advance.

Thoughts? Yes.

All I do is use a variable for each probe/angle to check the standard deviation of the tip. then I use logic to see if the results are larger than or equal 0.0005" to repeat which usually fixes things. Here is one of my star probes. See below.

AUTOCALIBRATE=LABEL/ AUTOCALIBRATE/PROBE, PARAMETER_SET=Star_Calibrate, QUALTOOL_MOVED=YES_DCC, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO BEGIN AUTOCALIBRATE RESULTS FOR PROBE VC0022 STAR USING SET Star_Calibrate Probe file=VC0022 STAR Date=10/3/2017 Time=6:02:09 PM Dixie Sphere CENT X 21.0250 Y 9.8345 Z -12.3495 D 0.7500 T1A0B0 THEO X 0.0000 Y 0.0000 Z 8.2262 D 0.1969 T1A0B0 MEAS X -0.0296 Y -0.0223 Z 8.1695 D 0.1948 StdDev 0.0002 T2A0B0 THEO X -0.9252 Y 0.0000 Z 7.1927 D 0.0787 T2A0B0 MEAS X -0.9491 Y -0.0197 Z 7.1290 D 0.0770 StdDev 0.0002 T3A0B0 THEO X 0.0000 Y -0.9252 Z 7.1927 D 0.0787 T3A0B0 MEAS X -0.0243 Y -0.9461 Z 7.1275 D 0.0765 StdDev 0.0003 T4A0B0 THEO X 0.9252 Y 0.0000 Z 7.1927 D 0.0787 T4A0B0 MEAS X 0.9035 Y -0.0166 Z 7.1416 D 0.0769 StdDev 0.0002 T5A0B0 THEO X 0.0000 Y 0.9252 Z 7.1927 D 0.0787 T5A0B0 MEAS X -0.0207 Y 0.9022 Z 7.1400 D 0.0769 StdDev 0.0002 END AUTOCALIBRATE RESULTS FOR PROBE VC0022 STAR USING SET Star_Calibrate LOADPROBE/VC0022 STAR ASSIGN/STD1=PROBEDATA("STANDARDDEVIATION","T1A0B0") IF_GOTO/STD1>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD2=PROBEDATA("STANDARDDEVIATION","T2A0B0") IF_GOTO/STD2>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD3=PROBEDATA("STANDARDDEVIATION","T3A0B0") IF_GOTO/STD3>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD4=PROBEDATA("STANDARDDEVIATION","T4A0B0") IF_GOTO/STD4>=0.0005,GOTO = AUTOCALIBRATE ASSIGN/STD5=PROBEDATA("STANDARDDEVIATION","T5A0B0") IF_GOTO/STD5>=0.0005,GOTO = AUTOCALIBRATE

I also have a comment in the beginning of the program to have the operator take off the star probe and clean it with the gum stuff to clean the module and cmm head contacts.

So if everything works out well, it goes to a timed operator comment saying the cal was successful and then the probe moves to the back of the machine ready for parts.

Then you can put in a counter like CALCOUNT=CALCOUNT+1 so like if it automatically repeats more than once, (meaning you've calibrated twice and the results are still not good.), then human intervention is needed so then it will go to not timed operator comment say to seek help. Maybe a probe or 5way is loose or dirty or bent or something. I also have a backup star probe under the CMM so they can just replace it, calibrate the new star probe and continue running until I can asses the probe causing problems.

1 time I was called in because the machine would not calibrate and a ruby had fell off one of the probes.

Let me know if this helps.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

acgarcia over 4 years ago in reply to acgarcia

This is the only probe on this machine so I use YES_DCC which makes tip 1 A0B0 the master tip. It will repeat automatically without operator input if it fails.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
acgarcia over 4 years ago in reply to acgarcia

So I also print a report to our network for record keeping. policy is that the operator must calibrate before each shift. once the calibration is done, the probe moves to the back which is an indicator that the calibration had good results. Otherwise they'd walk up to the CMM and see the operator comment saying the cal was unsuccessful and to seek help.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel