2022.1 bug

This is the problem I'm having when adding the mod on the secondary datum the position goes out an extreme amount --- Top result is 2020r2 next is 2022.1 s/p 2 with the mod turned on then next is 2022.1 s/p 2 with the MOD off

Any ideas? is there a known bug in this release BTW is a program that's been running for some time.

Parents

Caemgen over 1 year ago

I used to get this a LOT in Xact Measure (even without datum boundary modifiers) when my datums were not square to each other, like -A- is a plane and -B- is a plane that is 70° off of -A- rather than 90°, or -C- is a compound angle hole for some reason. That reason usually being that engineers hate CMM programmers.

I think I saw it once in GeoTol but I just remade the frame and it fixed, so I didn't look into it closer to try and find a why.

Powerful tool, but programmatically (like PcDmis source code program, not a part program) a miserable b!tch to pull off clean in every single instance any engineer ever dreamed to torment us with.

When I couldn't get it in Xact to stick, I'd align to the Feature Control Frame and use legacy.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Caemgen over 1 year ago

I used to get this a LOT in Xact Measure (even without datum boundary modifiers) when my datums were not square to each other, like -A- is a plane and -B- is a plane that is 70° off of -A- rather than 90°, or -C- is a compound angle hole for some reason. That reason usually being that engineers hate CMM programmers.

I think I saw it once in GeoTol but I just remade the frame and it fixed, so I didn't look into it closer to try and find a why.

Powerful tool, but programmatically (like PcDmis source code program, not a part program) a miserable b!tch to pull off clean in every single instance any engineer ever dreamed to torment us with.

When I couldn't get it in Xact to stick, I'd align to the Feature Control Frame and use legacy.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data