Calibrate Tips vs ScanRDV. Combined?

I have been wondering the same thing. I run the calibration program at the end of the shift and when I come in in the morning all tips are done. Takes about 5-6 hours so running it during work hours is generally not an option. Hopefully replying to this will get noticed and insight given. Is running both autocalibrations redundant?

STARTUP    =ALIGNMENT/START,RECALL:USE_PART_SETUP,LIST=YES
            ALIGNMENT/END
            MODE/DCC
            FORMAT/TEXT,OPTIONS,ID,HEADINGS,SYMBOLS, ;NOM,MEAS,TOL,DEV,OUTTOL, , 
            MOVESPEED/ 231
            ACCELERATION/MAXACCELX=100, MAXACCELY=100, MAXACCELZ=100
            LOADPROBE/PRIMARY_5X20
            TIP/T1A0B-90, SHANKIJK=0, 0, 1, ANGLE=-90
            COMMENT/OPER,NO,FULL SCREEN=YES,AUTO-CONTINUE=NO,OVC=NO,
             
            PLACE THE QUALTOOL AND DCC BEGINS AT OK
             
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_DCC, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ScanRDV, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            LOADPROBE/75X20X5
            TIP/T1A0B-90, SHANKIJK=0, 0, 1, ANGLE=-90
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ScanRDV, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            LOADPROBE/100X20X1_5
            TIP/T1A0B-90, SHANKIJK=0, 0, 1, ANGLE=-90
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ScanRDV, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            LOADPROBE/200X20X3
            TIP/T1A0B-90, SHANKIJK=0, 0, 1, ANGLE=-90
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ScanRDV, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            LOADPROBE/150X20X5
            TIP/T1A0B-90, SHANKIJK=0, 0, 1, ANGLE=-90
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ScanRDV, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            TIP/T1A0B-90, SHANKIJK=0, 0, 1, ANGLE=-90
            LOADPROBE/250X8
            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
            MOVE/INCREMENT,<0,0,300>
            AUTOCALIBRATE/PROBE, PARAMETER_SET=ScanRDV, QUALTOOL_MOVED=NO, 
                          CHECK COLLISION=NO, SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=NO
            MOVE/INCREMENT,<0,0,300>
            LOADPROBE/200X20X3
            TIP/T1A90B180, SHANKIJK=0, -1, 0, ANGLE=180

Hello Mike, when you are calibrating all of the TIP angles do you get a popup after loading a new probe to "Press OK when ready to move Wrist to T1A0B0? If not are you or somebody else aware of a way to configure this as a setting? It seems if you already get this pop up you can just select "Don't ask me again".

No, program runs all the way from start to finish without any popup.

I'm not an expert on this so take this advice with a grain of salt. Are you selecting "DCC+DCC"?  If so, then I think it will do what you describe and take hits points as well, but will only report the ScanRDV deviation.  Try selecting "DCC", then it will just do the ScanRDV without the hit points.  When I calibrate, I only use "DCC+DCC" for the Primary Tip and "DCC" for everything else.  I do a regular calibration first, then a ScanRDV, both using the "DCC" option.

Also, do you know if your CMM is a chrome model?  If it is, then uncheck "TRAX Calibration" and you shouldn't have to do a ScanRDV.  It will scan the sphere during normal calibration.  If you don't have a chrome model, then don't uncheck it.  

Again, I'm not 100% sure if I'm correct here.  So if someone else gives you different advice, then ignore mine.

Ill give that a shot, We have 3 different models at my work. One of them is the Chrome, its scanning is completely different than the other models. It will scan up and over, around, and some loops. The other models will do a single side scan.

I think the TRAX calibration is for machines that DON'T support VFT (Vibration Free Transmission).  The chrome does support it, so TRAX calibration needs to be UNCHECKED for the Chrome model and it will scan the sphere like you just described during normal calibration.  For machines that do not support VFT, like the green and blue models for example, TRAX calibration needs to remain checked and a ScanRDV done in addition to the regular calibration.  Using "DCC" rather than "DCC+DCC" should stop it from taking hit points again during ScanRDV.  

Again, I'm not 100% sure I'm correct with all that.

Actually I have the same confusion about it. When I run the "ScanRDV" calibration, it first hits the sphere as the same way as the "Tips" calibration does, and then does the scanning. But the summary only shows the scanning dev, so I suppose this two calibrations are both needed.

Yeah I started doing what ESchertz suggested. Doing a regular calibration using DCC+DCC, then doing ScanRDV using only DCC. Its much faster then the DCC+DCC, and results have been pretty normal.

Ive been doing as you suggested and so far my results seem to work as they should.