Dimension displays incorrect value from measured feature

[habasit america]

I'm using a series of assignments to calculate difference percentage of the min and max of a series of measurements. See below

PITCH ANA.PNG

Hovering over my calculation (1-PITCHMIN/PITCHMAX)*100) produces the correct value. In this case 0.018

Then I'm using a generic feature and dimension in order to have this value display on the report

PITCH ANA 2.PNG
PITCH ANA 4.PNG


I'm running into a couple problems.

1. When I execute the program the measured value does not match the calculated value
2. It automatically overrides the nominal value of 0 with the measured value

PITCH ANA 1.PNG

I cannot figure out what I'm doing wrong here. Anyone have any suggestions?

[JEFMAN]

I often ASSIGN/ZERO=0, then use ZERO instead of 0...
Are you sure that the alignment is the same between the generic and the dimension ?

[habasit america]

The alignment? Could you expound please? How could it not be if I don't implement another alignment between the generic and the dimension?

Are you saying use ZERO as the nominal value rather than 0?

[JEFMAN]

Yes I use ZERO in theo values (here, in the generic, you could also use them in measured values.
If there's no alignment between generic and dimension, the problem is not there.
You could try to insert an operator comment with PITCHPERCENTDIFF, just checking if the value is 0.018 or 0.025...

[habasit america]

I mean I'll try using ZERO to help eliminate any "confusion" in the code.
Yes, I could and have used an operator comment that displays on the report and that works fine but want to incorporate the value into a cohesive look with the rest of the dimensions displayed on the report.

[habasit america]

After running some trials, I'm seeing that after executing the program several times in succession that the dimensional value being measured and displayed on the report is somehow the actual PITCHPERCENTDIFF value from the previous execution. I don't know how it's generating that as the dimension comes well after the feature in the code just like every other feature and dimension.

any thoughts?

[JEFMAN]

ASSIGN/PITCHPERCENTDIFF=0 at the start of the program, maybe also ASSIGN/PITCHARRAY=0

[Kp61dude!]

Where what is this?

ASSIGN/V7=[COLOR=#FF0000]BELTPITCHMEAS1.MEAS[/COLOR]

If you're assigning a constant to it fine though me persoanally I wouldn't use .MEAS just because it's confusing (reserved for other stuff example at end of post). EX:

ASSIGN/BELTPITCHMEAS.MEAS=3

then below should work fine.

ASSIGN/V7=[COLOR=#FF0000]BELTPITCHMEAS1.MEAS[/COLOR]

else

If you're pulling from a dimension named BELTPITCHMEAS1 then it's probably missing an extension. If it's a distance then I would expect to see BELTPITCHMEAS1.M.MEAS or if it's a position BELTPITCHMEAS1.X.MEAS or .Y.MEAS, .Z.MEAS. etc... EX:

DIM BELTPITCH1= 2D DISTANCE FROM CIRCLE CIR1 TO CIRCLE CIR3 PAR TO   YAXIS,NO_RADIUS  UNITS=IN,$
GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
AX    NOMINAL       +TOL       -TOL       MEAS        DEV     OUTTOL
M       3.0000     0.0010     0.0010     3.0000     0.0000     0.0000 ----#----
            ASSIGN/V7=BELTPITCH1.M.MEAS

[habasit america]

JEFMAN assigning those variables to 0 at the beginning of the program didn't help.

[dph51]

2. It automatically overrides the nominal value of 0 with the measured value

In your generic feature, set the nominal to 0, don’t use your variable as the nominal value.

[JEFMAN]

As Kp61dude! said, can you describe what are BELTPITCH1,2,3... ?
Are there dimensions, features, variables...?

[anthony.alfaro]

try changing your generic feature alignment from dependent to independent.

[habasit america]

Doing this seems to make it ignore the calculation result and output a point location.

[Matthew D. Hoedeman]

Isn't there something in Pcdmis about clearing previous incidence, so that it doesn't hang onto previous measurements?

[SingularitY]

For generic features, I +0 to any nominal in the feature to make sure it doesn't change. I may be late in the conversation, but is there a reason why the variable is inserted in both the measured and nominal sections of the generic feature? Is there a reason why the plane vector is set to Z+ when you are measuring the X axis of the feature?

[habasit america]

Thanks for some of the suggestions everyone. I'll be taking another look today and I'll report back here what I find out.
Kp61dude! and JEFMAN BELTPITCH1......6 are dimensions.
dph51 I tried changing my nominal to zero. That didn't work.

[JEFMAN]

So using Kp61dude! example should solve the problem... !