Reporting Profile

read a few posts and seems people use the max/min,

i create vector points and then construct a set and report profile in XactMeasure. I also include min/max. i know a lot of people use "T" values for each point. You could use point info or "T" values and add all of the information they requested. Not much you can do if the customer wants that information.

thank you Mikeg.

What I'd do:
1) Origin my program to the datum scheme that is called out in the feature control frame for my profile callout
2) Set up a linear open scan. Get it right where I want it, set all of my parameters and everything...but instead of clicking "create" you click the box that says "to points". This will take all of the hit points that would have made your scan and will create them in your program as auto vector points. Depending on how you set up your scan, you could have dozens if not hundreds or even thousands of points being created.
3) Construct a feature set out of those points and report the profile. Be mindful of how your customer wants this reported. They may require Y14.5M or another spec...if you're unclear how to handle these differences check back with us.
4) Report the T value of each of those points.

I think that's what his customer is looking for

there's no other way TO use profile.

the MEAS value is the difference between MAX and MIN. Leaving those out of the report is misleading, if not downright disastrous.


Example:

I'm scanning the surface of my mouse, attempting to see if it's within .010 to it's CAD model (we'll assume you have FINDNOM turned on, scan created correctly, and Profile Dim is +/- 0.010). MAX / MIN are not added to this report.

the first mouse I scan shows (NOM = 0; TOL = +/- 0.010; MEAS = 0.005; OTOL = 0.000). Sweet, looks like the mouse surface falls within profile.
the second mouse shows (NOM = 0; TOL = +/- 0.010; MEAS = 0.005; OTOL = 0.004). Wait, aren't I inside the tolerance band?
the third mouse shows (NOM = 0; TOL = +/- 0.010; MEAS = 0.015; OTOL = 0.012).
the fourth mouse shows (NOM = 0; TOL = +/- 0.010; MEAS = 0.012; OTOL = 0.000). What is happening here?

MEAS is the difference between MIN MAX. Had we included it, we'd have seen the following:

first mouse had a MIN of -.005, MAX of 0.000; well within the tolerance band
second mouse had a MIN of .009, MAX of 0.014; too much material
third mouse had a MIN of 0.007, MAX of 0.022
fourth mouse had a MIN of -0.008, MAX of 0.004; within the tolerance bad.

Adding MIN/MAX is essential to understanding what your part is doing, you can't really leave it off your report for those reasons. In fact, when showing profile I only use ( MAXMIN, TOL, DEV, OUTTOL) for those reasons. MEAS just confuses people when it comes to profile.

Report the set profile using textual analysis.

should give all points and highlight the max/min.

well after pointless attempts to convince them, they got what they wanted.

Colin, you might want to double check your numbers. The MEAS value is the difference between min and max when min and max are on opposite sides of 0, when both are positive or negative, then 0 is the min/max (as necessary). I'm fairly certain that PC-DMIS reports the first mouse as .005, the second as .014 (you wrote .0014, but meant .014), the third as .022 (you wrote .0022, but meant .022), and the fourth as .012. (Your example don't match either.

Your overarching point is the important part though. Per ASME Y14.5, the min and max values are what is important. A single value is not relevant.