Auto calibrate question

mb0258, “The man who asks a question is a fool for a minute, the man who does not ask is a fool for life.” --Confucius

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.

Also our operators do not have full access to PcDmis so the pdf report on the network folder is the record that the probe calibration even happened.

So I am running the basic program I originally posted. I am looking into using if_goto statement for if a high standard deviation occurs, then the program will execute the calibration again. I tested it out by sticking some tape on our qual sphere and running the program. The problem I have now is that when the probe is at the final angle of whichever probe build is currently being calibrated, and the program goes to recalibrate that tip, I do not have enough clearance. Our last angle is either A-90B180 or A-110B180. The probe rotates to A0B0, but when it goes to the top of the sphere the point it moves to isn't high enough over the qual sphere and I get a "probe deflection" error message.

I have 2 options I can see:
(A) I adjust the calibration settings some how. I can see when I open the probe utilities window and click "setup" I am given a bunch of options for different distances along the shank vector, etc.

(B) I take the LABEL command

AUTOCALIBRATEMASTER=LABEL/
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_DCC,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
and put a move point in the command so the probe will move above the sphere before calibrating

definitely run with B. I'd use move/increment=0,0,8 (if in imperial units not mm).
That should suffice for most tips under 50mm long using a ph10mq with tp20 or tp200 module.

You could define the order of the tip angles calibrated within in your parameter set to avoid this, but that's a lot of work compared to a simple move/increment.

STARTUP =ALIGNMENT/START,RECALL:USE_PART_SETUP,LIST=YES
ALIGNMENT/END
MODE/MANUAL
MOVESPEED/ 300
FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
OPTIONPROBE/MAXFORCE=0.096,LOWFORCE=0.019,UPPERFORCE=0.072,TRIGGERFORCE=0.033,
PROBEACCURACY=0.1,POSACCURACY=0.1,#RETURNDATA=10,
RETURNSPEED=0.4,SCANPNTDENSITY=10,
SCANACCELERATION=10,SCANOFFSETFORCE=0.06,
PROBINGMODE=DFL,MANFINEPROBING=NO
MODE/DCC
AUTOCALIBRATEMASTER=LABEL/
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_DCC,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
AUTOCAL =LABEL/
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
LOADPROBE/8 MM TIP
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_DCC,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
ASSIGN/STD1=PROBEDATA("standarddeviation","T1a0b0")
IF_GOTO/STD1>=0.01,GOTO = AUTOCALIBRATEMASTER
ASSIGN/STD2=PROBEDATA("standarddeviation","T1a-90b0")
IF_GOTO/STD2>=0.01,GOTO = AUTOCALIBRATEMASTER
ASSIGN/STD3=PROBEDATA("standarddeviation","T1a-90b180")
IF_GOTO/STD3>=0.01,GOTO = AUTOCALIBRATEMASTER
LOADPROBE/1 MM TIP
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
ASSIGN/STD4=PROBEDATA("standarddeviation","T1a0b0")
IF_GOTO/STD4>=0.01,GOTO = AUTOCAL
ASSIGN/STD5=PROBEDATA("standarddeviation","T1a-45b180")
IF_GOTO/STD5>=0.01,GOTO = AUTOCAL
LOADPROBE/STOCK TIP
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
ASSIGN/STD6=PROBEDATA("standarddeviation","T1a0b0")
IF_GOTO/STD6>=0.01,GOTO = AUTOCAL
ASSIGN/STD7=PROBEDATA("standarddeviation","T1a-110b0")
IF_GOTO/STD7>=0.01,GOTO = AUTOCAL
ASSIGN/STD8=PROBEDATA("standarddeviation",
MOVE/POINT,NORMAL,<310.738,1322.216,-112.826>

That code isn't 100 percent done yet, but I can not get the label command to work with a move increment. I will post what I tried, but was unsuccessful with. We do have a 150 mm tip extension, so I am going to probably need a move increment in Z of at least 50

I added a screenshot of the Code in my original post. PCDMIS seems to skip right over my IF_GOTO/STD>=0.01, GOTO=MOVE. I don't know how to add multiple things into the Label or I would just do that.

louisd acgarcia Thank You for explanation. i do same way, one master probe, qual tool yes_dcc, other probes qual tool not. but all the calibration doing mysefl manualy. I would like to also switch to autocalibration routine by operator.

I typically make my labeling convention avoid exact-matching terms that PCDMIS uses. MOVE is a pcdmis command. toss an _1 at the end and it becomes unique/non affiliated to any active code. I also try to avoid spaces at all costs (like the "8 MM Probe" should be 8_MM_PROBE).

Any time you have a loadprobe command, you should define the active angle immediately afterwards, without anything in between them.

Regarding the image:
- When you have two if_goto statements with identical criteria, only the first goto will effectively ever happen, so nix the if_goto/std1>=0.01, goto = autocalibratemaster.
- I would insert the MOVE_1 label just after MODE DCC, then move/increment, then loadprobe, then tip/t1a0b0, then you can create a "CALIBRATE ACTIVE TIP WITH FEAT_ID=" to calibrate just your master tip.
-Then insert your auto-recalibration assignment check and if_goto loop just for that master probe at T1A0B0, (capitalize the T, A, and B in the assignment)
-Insert autocalibrate all angles for the master probe tip at this point, repeat auto-recalibration assignment check if-goto loop for each of the applicable tips.
this should fix the skipped move increment.