how come one of my datums is showing out of tolerance in my report.....

[jozey]

when it is not out of tolerance?

[jozey]

I'm using pcdmis 2013 and trying to report in xact

[jozey]

heres a screen grab

[jozey]

sorry for the spam....

i think this is an error with xact measure.... when I report using legacy everything is "green" and in tolerance

[Darrollh]

Exact is funky. I prefer to use legacy and just make sure I’m in the correct alignment and use best fit when needed.

[Cumofo]

That's been my long standing technique too.I've had to explain xactmeasure's habit of flipping axis vectors and nominals that don't reflect the basics too much. I like legacy. I have much better repeatability from the best fit algorithms when I can control the primary axis of rotation. I really like using a 2-D least square best fit,

[Cumofo]

That dose n't happen very much if you use CAD=PART. But I do get it sometimes when using a lot of best fits with re-pierce checked. It seems that the theoreticals can be "disconnected" from the Part and CAD coordinates when best fitting.

[Darrollh]

I have never ever ever (did I say never) use CAD = Part.

[Schlag]

Same here !

[SingularitY]

The Datum that shows out of tolerance does so because it has a zero tolerance. It will always show out of tolerance.

[RandomJerk]

38 meter shift in Z?

Did you measure the datum after you leveled to the primary datum?

[sealevel]

CIR_P375-C
CIR_PORT-C
etc
names like you're using can (not always) give PC-DMIS/Xact a bit of heartburn.
Be safe and only use under_scores in your naming scheme.
Also check the vectors.......
2¢

[Rob Jensen]

1) The MMB value for datum C is .750, you keyed in .5125 for the datum C MMB value, why? Delete the keyed in MMB for C and PC-DMIS will calculate the MMB. 2) You are referencing a circle as a primary datum, this requires sample hits.