hexagon logo
Register Sign in
  • Replies 8 replies
  • Subscribers 14 subscribers
  • Views 117 views
  • Users 0 members are here
Options
Related

Calibrating Probe Offset HELP!

afotion
So I just about had a heart attack today.

I'm wanting to calibrate my 5x Nikon Lens with my TP200 by1x30mmTip.

So I opened up the probe utility box

-Went to my Fixed 5x Lens tip, Calibrated to the Ring Gauge,Calibrated probe Offset-All went well with calibration, I closed out and went to select my TP200Tip
-Selected the TP200 tip and Saved my prior Tip calibration data as it asks, went to measure my tip had ring Gauge selected and right after is asked if the Calibration Tool had moved I hit NO and as soon as that happened the probe went directly down towards the table not even going towards the ring and snapped my tip! AngryAngryAngry I tried several times even after shutting down completley with the same result. Am I missing something? This was how I was instructed to Calibrate my Optics to Probe Offsets from the other programmer I work with and they have no idea what is wrong. Any ideas anyone?
Parents
  • The question whether the fixture has moved will have two different results. Yes its moved will update the location of the calibration artifact whether the ring or sphere. No it hasn't moved will update the probe file from the last known location of the calibration artifact.

    On a vision system always measure the ring first with vision and always say YES its moved. The vision probe is the Master that everything else is offset back to. This will locate the ring in the measurement range. Your vision probe should always have a TIP location of 0,0,#. If X and Y are not 0 then someone answered NO at some point.

    Then choose a touch probe tip to be the secondary master. Measure TIP1 only on the Cal Sphere and answer YES. This will update the probe radius but will not update the probe location. Then calibrate the same tip on the ring gage and answer NO. This will update the probe location relative to the camera. If it is the first time you have ever measured the offset always use MAN+DCC. The manual hit is straight down about 5 mm from the inside diameter at 6 O'Clock. If you have done the offset before and know its close then you can run DCC.

    Then if using multiple probes or star probes, go back to the cal sphere with the same TIP1 and answer YES its moved, this now updates the location of sphere with the corrected offset of TIP1 to the vision probe. All other tips can now be calibrated back to the cal sphere and answered NO like a normal CMM.

    Hopefully this makes sense.
Reply
  • The question whether the fixture has moved will have two different results. Yes its moved will update the location of the calibration artifact whether the ring or sphere. No it hasn't moved will update the probe file from the last known location of the calibration artifact.

    On a vision system always measure the ring first with vision and always say YES its moved. The vision probe is the Master that everything else is offset back to. This will locate the ring in the measurement range. Your vision probe should always have a TIP location of 0,0,#. If X and Y are not 0 then someone answered NO at some point.

    Then choose a touch probe tip to be the secondary master. Measure TIP1 only on the Cal Sphere and answer YES. This will update the probe radius but will not update the probe location. Then calibrate the same tip on the ring gage and answer NO. This will update the probe location relative to the camera. If it is the first time you have ever measured the offset always use MAN+DCC. The manual hit is straight down about 5 mm from the inside diameter at 6 O'Clock. If you have done the offset before and know its close then you can run DCC.

    Then if using multiple probes or star probes, go back to the cal sphere with the same TIP1 and answer YES its moved, this now updates the location of sphere with the corrected offset of TIP1 to the vision probe. All other tips can now be calibrated back to the cal sphere and answered NO like a normal CMM.

    Hopefully this makes sense.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement