hexagon logo

0.5mm tip + TP20

Hello all,

When using a single 0.5x20 ruby tip I have noticed all my Tigo's with TP20 modules give around 5μm of std while calibration. It has always been like this, validated, verified etc. The results between Tigos with X1C and TP20 when using a 0.5mm tip is day and night.  The X1C seems to be a whapping 4 times more repeatable and in my company TP20 is always considered to be the less precise option to make programs with. Is it supposed to be like this? (Keep in mind that due to making rather small parts, almost all programs have a 0.5 tip probing something with a TP callout or Datum).

Finally, 0.5 tips seem to work better with Low force modules but the issue applies to standard modules as well.


Parents Reply
  • It's not just the force of the module that will affect accuracy but also the touch speed being used.  Ø0.5 tips have a very thin stem that is quite flexible, probing at low touch speeds (~1 mm/second) with a low force module should help.  Also, remember that you should always calibrate your probes at the same touch speed that you use in your routine when measuring.

    Also remember there is an inherent tri-lobing error with touch trigger probes due to the trigger mechanism that you will not be able to eliminate, regardless of which force module or touch speed you use.  Those errors are usually in the sub-micron range but are one of the reasons why you can achieve more accurate results with an analogue system (like the LSP-X1-S / HPS-X1S).  

Children