hexagon logo

Collision during auto calibration process

Hello all, I am fairly new to CMM and do not have much knowledge, so I am learning through experience and this forum. I am having trouble setting up a new probe. I am able to "qualify" or add all active tips and successfully run the measure process. However, once I run the auto calibration program it crashes into the sphere. Our autocalibration program is copied from one of our other CMMs except I changed the sphere size to match. I could be missing something here and I'm hoping one of you can help out. I can provide the program, pics, and videos or whatever is needed to better visualize.
Parents
  • In reading your code, I noticed this is the same definition for every probe you have listed:
    AUTOCALIBRATE/PROBE, PARAMETER_SET=PROBE2_T2, QUALTOOL_MOVED=YES_DCC,

    When you state the qual tool has moved for each probe, you are basically telling the machine to "reset" the location of the qualification sphere, relative to the current iteration of the machine's volumetric "Home" location which it finds every time you shut down the machine and turn it back on ("Press OK to Home machine" command will vary every time you turn machine on).

    So what this does, is it prevents each probe from "correlating" to each other. If you use Probe2 and Probe5 in a routine, whatever deviation from perfect that those probes have between each other (slightly bent, module projecting the tip off-perfect axis, etc) will show up in your measured data.

    This QUALTOOL_MOVED=Yes_Manual, Yes_DCC is intended to be set to a "YES" output only when you are defining the "one probe to rule them all" The Master Probe. Typically folks set this probe as the one in which you are dictated to use to calibrate your probe racks (2x20mm, or a 5x20mm for LSPX probe systems).

    Now, changing this, and establishing a "Master Probe" might not fix what you are encountering, but it will absolutely be necessary in order to get accurate data when using more than one probe in a measurement routine. You can read more about Master Probes if you log into the hexagon support page ( Home (hexagonmi.com)​) and look in the knowledgebase for a file titled "Relating Multiple Probes"

    What i believe will fix your issue, if you are certain the probe builds are correct... would be to checkbox the "Reset Tips to theoretical" within each probe's settings. You can also increase the prehit/retract distance to absorb any variation you might have in your build.
Reply
  • In reading your code, I noticed this is the same definition for every probe you have listed:
    AUTOCALIBRATE/PROBE, PARAMETER_SET=PROBE2_T2, QUALTOOL_MOVED=YES_DCC,

    When you state the qual tool has moved for each probe, you are basically telling the machine to "reset" the location of the qualification sphere, relative to the current iteration of the machine's volumetric "Home" location which it finds every time you shut down the machine and turn it back on ("Press OK to Home machine" command will vary every time you turn machine on).

    So what this does, is it prevents each probe from "correlating" to each other. If you use Probe2 and Probe5 in a routine, whatever deviation from perfect that those probes have between each other (slightly bent, module projecting the tip off-perfect axis, etc) will show up in your measured data.

    This QUALTOOL_MOVED=Yes_Manual, Yes_DCC is intended to be set to a "YES" output only when you are defining the "one probe to rule them all" The Master Probe. Typically folks set this probe as the one in which you are dictated to use to calibrate your probe racks (2x20mm, or a 5x20mm for LSPX probe systems).

    Now, changing this, and establishing a "Master Probe" might not fix what you are encountering, but it will absolutely be necessary in order to get accurate data when using more than one probe in a measurement routine. You can read more about Master Probes if you log into the hexagon support page ( Home (hexagonmi.com)​) and look in the knowledgebase for a file titled "Relating Multiple Probes"

    What i believe will fix your issue, if you are certain the probe builds are correct... would be to checkbox the "Reset Tips to theoretical" within each probe's settings. You can also increase the prehit/retract distance to absorb any variation you might have in your build.
Children
No Data