PCM problem

[[Cl...]]

I have a parametric program for a family of 5 sizes. Visually the scan doesn't match where it should be on the model.

I've double checked everything (I think). It's got to be something simple. Any ideas? PCM_1 shows in wireframe the scan

inside the outer wall. Should be on the wall. PCM_2 is the solid view and PCM_3 is the para file showing the X variable.

I must be overlooking something simple. Any ideas? BTW, I'm running this is simulation.

Edited January 15

[[No...]]

1. Does the model displayed match the part size measured?

2. Is dispersion turned on (since nominals and actuals differ)?

3. Have you set a display scale (overheight) factor for deviations?

Edited January 15

[[Cl...]]

For questions 2 & 3 where are these settings located?

[[Cl...]]

[[No...]]

Dispersion is under Extras/Settings/Measurement/Simulation. If it's on you should also see a yellow warning sign in the CNC start window.

What I meant by 3. is magnification (I was struggling with the correct translation 😉). You can access it by right-clicking in the CAD view when a feature window is open, or in the CAD evaluation dialog. Dispersion together with high magnification can result in seemingly shifted actuals.

Edited January 15

[[Cl...]]

Magnification is set at 1

[[No...]]

Then it's not that.

[[Kl...]]

If the screen dump shows your input, the dispersion is always in "+" direction.

To create it +/- according to nominal direction, modify it to -0.0001 / 0.0001.

[[No...]]

Oops, I missed that 😲

[[Ri...]]

The times I have seen this, its usually one or the other for nominals values.

If using a circle on a plane, check the Strategy for nominal values (My example works in the Z axis).

If using a polyline in a plane, you also have to check nominal values. Regardless of the axis or angle of a plane, the polyline nominal for Z should be Zeros.

This is why I preach about nominals and vectors being perfect.

[[Cl...]]

Thanks Richard. I'll check that.

[[Je...]]

Besides the more likely causes that were already posted above, one oops that has caused this for me was using an improperly qualified probe (was set to reference sphere 1 when 2 was actually probed), or a different probe was attached then what was defined.  Or, a bent probe shaft.