Probe "crash" during calibration

[pcdmisstudent]

Hey all
So we got an autocal program for our 6 stylis (we have a rack).
One of the probes (single tip Ø4 L40) sometimes "crashes" during calibration.

"sometimes" = about 50% of our calibration runs it "crashes".

"crashes" = it measures A0B0, A90B0 etc fine, but when it comes to an angle A0B45 it goes to its prehit distance of the sphere (2.5mm) then it stops with error "probe deflect" and also we get emergency warning.
I tried reseting the tips to nominal, which worked for about 2 times, then it "crashed" again.
Should i maybe check the box "reset to nom. before calibration" ?
But i rather not use this method as we will lose our tracability right?

anyone has any ideas what might be causing this problem?

[JEFMAN]

A0B45 ? Is it a star probe ?
I had a similar problem with a A45B0, I think it was a problem on the tesastar-m.
I fixed it by using A-45B180.
If it's really A0B45 with a star probe, maybe you can try B-45 ?

[pcdmisstudent]

Its a "normal" straight single styli, and its the 2nd tip in our rack (after master probe).

[JEFMAN]

Why do you use B45 with A0, in this case ?

[pcdmisstudent]

Im sorry, thats not the actual angle, i ment a45b0. And thats just a guess, i havent acctually checked which exact angle it is

[JEFMAN]

SO if it's A45B0, You can replace by A-45B180...

[NinjaBadger]

Hey all
So we got an autocal program for our 6 stylis (we have a rack).
One of the probes (single tip Ø4 L40) sometimes "crashes" during calibration.

"sometimes" = about 50% of our calibration runs it "crashes".

"crashes" = it measures A0B0, A90B0 etc fine, but when it comes to an angle A0B45 it goes to its prehit distance of the sphere (2.5mm) then it stops with error "probe deflect" and also we get emergency warning.
I tried reseting the tips to nominal, which worked for about 2 times, then it "crashed" again.
Should i maybe check the box "reset to nom. before calibration" ?
But i rather not use this method as we will lose our tracability right?

anyone has any ideas what might be causing this problem?

I don't see how it affects traceability. There's no history of calibration results stored in the .prb file itself.

Just make sure it's set to append results in the probe setup.

[neil.challinor]

Hey all
So we got an autocal program for our 6 stylis (we have a rack).
One of the probes (single tip Ø4 L40) sometimes "crashes" during calibration.

"sometimes" = about 50% of our calibration runs it "crashes".

"crashes" = it measures A0B0, A90B0 etc fine, but when it comes to an angle A0B45 it goes to its prehit distance of the sphere (2.5mm) then it stops with error "probe deflect" and also we get emergency warning.
I tried reseting the tips to nominal, which worked for about 2 times, then it "crashed" again.
Should i maybe check the box "reset to nom. before calibration" ?
But i rather not use this method as we will lose our tracability right?

anyone has any ideas what might be causing this problem?

When you say "crashes" it sounds like you just mean that the program stops and present you with the error message "probe deflect"? Have you actually witnessed the probe collide with something (cal sphere?) or does it just error out in fresh air? We need a little more information - a lot of factors could be causing the issue you are having. For example, your machine type, probe type, and settings (move speed, acceleration, clearance values within the probe utilities setup etc.)

[pcdmisstudent]

It stops mid-air (at the prehit distance from the cal.sphere, which is about 2.5mm and i get the error message "probe deflect" and joystick shuts off.
It never acctually crashes. (But pc-dmis seems to think it does).
The weird thing is that A0B0, a90b90 etc calibrates fine, its just this one angle.

Im using a DEA classic cmm with pc-dmis 2011. tesastar-sm head with tp200 probe. Movement speed is 200mm/s, rest of the settings are set to deafult.

[neil.challinor]

Have you tried slowing the movespeed down? Maybe drop it to 100 as a test to see if the problem goes away. Also, check the acceleration values. Sometimes - especially on older machines - the combination of high movespeeds, high acceleration and long / heavy styli cause the probe to trigger whilst the machine is in motion.

[ClayT]

something...

Our Tessa-m will occasionally 'air trip' @ A90B180.
Wrist indexes to A90B180 and soon as it locks in, the red light starts flashing.
The CMM will continue until the ruby hits something and/or overtravels far enough to shut it down.

Sometimes the blinking red light goes solid during transit and the program continues uninterrupted.

There's only one program where it happens consistently.
All the other programs that have A90B180 in it run without incident.

I think it also happens during tip qualification, but I can't prove it.
(I'm not going to watch qual for 30 minutes.)
CMM will stop with either nothing found in range of the probe* or run up against the qual sphere and stopped.
I back it away from the sphere, hit continue, and qual resumes.

(*This is the same error when the CMM tries to hit something while the red light is blinking.)