hexagon logo

tp20 madness!

i had a program giving bad data (.005 oot) for a length characteristic on a production floor cmm.  this was verified in the gage lab with an open setup.

i ran the program on the gage lab cmm and got good data (matched the open setup).

i swapped out the tp20 and tip on the production floor cmm, reran the same program and part, and got good data (matched the open setup and gage lab cmm).

i then ran the same program with the same part on the gage lab machine with the "bad" tp20 and tip and got good data.

its a 3x30 tip in 0,0 orientation.  no other orientations seem to be offering contrary data.

thoughts?

Parents
  • I would recalibrate your tip/tips then check a ring gauge and a 123 block to see if either machine is showing any significant differences. Typically, when I get something that far out it's due to the part moving during the routine or some debris on the tip/surface causing the bad data. I had a similar issue in the past that was due to a damaged calibration artifact that someone dropped, and the sphere was loose.

Reply
  • I would recalibrate your tip/tips then check a ring gauge and a 123 block to see if either machine is showing any significant differences. Typically, when I get something that far out it's due to the part moving during the routine or some debris on the tip/surface causing the bad data. I had a similar issue in the past that was due to a damaged calibration artifact that someone dropped, and the sphere was loose.

Children
No Data