Collision during auto calibration process

Everyone used to be new. Have you done your training?

Unfortunately, I have zero formal training. The people who had trainings have left the company so I all I have is troubleshooting experience with them.

It is very hard to learn by yourself without any training. It costs lot of money to get training and it is part of their business...



Here is from HELP, hope it could help.

Before you calibrate a new probe, you must first calibrate your master probe.

Thank you for the pictures. I have gotten to this point and have built it correctly. My company is in the process of sending us to training but waiting on a confirmed date.

I would look and see if the calibration program is recalling any offsets, or using parameter sets for the probes.

Posting the program code is always good too, frequently that solves many problems here.

I started the same way as you. I've been doing that for 1.5 yrs, it definitely gets easier.

As someone suggested below, can you share your autocalibration set/program?

I had what sounds like the same problem happen here recently. When the autocal for that probe finishes, is it going to do a probe change right after? I ended up having to add a move point up to clear the sphere right after the auto cal finishes, but before the probe change command.

Code. It always crashes during tip 2 when it is going for a touch.

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.