hexagon logo

XactMeasure versus GeoTol accuracy- comparative study of results

Hello all,

Has anyone done a comparative study or has some experience with reported results between Xact and GeoTol?  How similar are the results?

I have a customer drawing which requires ANSI Y14.5M-1982 so the previous programmer did everything with Legacy and alignments using all of the applicable MMC given by the common (mis)understanding of additive bonus from datums.  Our customer has recently rejected some parts due to OOT position of one feature at MMB as internally they have decided to go to ASME Y14.5-2009 without contractual notification.  One of the CAs was to switch everything over to GeoTol and ASME Y14.5-2009/2018 even though not specified anywhere (pick your battles, I lost).  However, according to my Hexagon rep, there have been a couple of library changes and corrections in how PCDmis approaches geometric requirements up to and including a large correction due to a misinterpretation of the standard on their end.  They couldn't give me specifics though.

The information I have gotten is that they are measuring using 2018.2 with XactMeasure and I have 2023.2 SP11 running GeoTol.

Parents
  • I would need you to send me a copy of the program (.prg & .cad files) to confirm but I do not expect there to be large discrepancies between 2018 & 2023.2 - providing everything has been programmed correctly.  By that I mean, THEO values matching the CAD nominals for all features, a fully constrained alignment BEFORE measuring anything that gets reported later and no partially constrained alignments mid-program (this breaks the alignment chain and can lead to strange behaviour), datums referenced at MMB/LMB must have been previously dimensioned - see "Determining the Size of the Material Boundary" on the following help page: How PC-DMIS Solves and Uses Datums

  • Good Morning Neil,

    By that I mean, THEO values matching the CAD nominals for all features

    The CAD is reference only so for every feature I have to run a location first and adjust nominals to print, then run the GeoTol.

    a fully constrained alignment BEFORE measuring anything that gets reported late

    I may get their Engineers to correct this at least but most features are ABC with A plane defined by flatness, B is position MMC from A-C MMB, and C has no geometric definition.  To follow print as it currently stands, I've already lost and would like to find out if XactMeasure can do this as GeoTol is not happy.  I don't get a Datum does not constrain error like some FCFs from another customer that doesn't understand common datums (A | B-C | B), but I know it is treating datums as 0.  Further D and E datums have no constraints other than linear dimensions.  Their Engineers don't understand the necessities of PCDmis but I would have figured their Quality Lab would have chimed in by now.

Reply
  • Good Morning Neil,

    By that I mean, THEO values matching the CAD nominals for all features

    The CAD is reference only so for every feature I have to run a location first and adjust nominals to print, then run the GeoTol.

    a fully constrained alignment BEFORE measuring anything that gets reported late

    I may get their Engineers to correct this at least but most features are ABC with A plane defined by flatness, B is position MMC from A-C MMB, and C has no geometric definition.  To follow print as it currently stands, I've already lost and would like to find out if XactMeasure can do this as GeoTol is not happy.  I don't get a Datum does not constrain error like some FCFs from another customer that doesn't understand common datums (A | B-C | B), but I know it is treating datums as 0.  Further D and E datums have no constraints other than linear dimensions.  Their Engineers don't understand the necessities of PCDmis but I would have figured their Quality Lab would have chimed in by now.

Children