Nominal value

Post the code...

Without seeing the code, I'll take a shot in the dark that its a F5 setting like "Update nominals during execution" or something like that

Angle*...

Secondly, as stated above, need some code.
The circle could be FIXED_RAD for all I know

Update report during execution is on..

I fixed it yesterday by re measure several times, but the problem occurs when I do re-measurements. Then actual value are the same as nominal value.
however, im not getting any smarter..

Is the "Find nominals" enabled perhaps?

No, it`s not.

Loose anything not alpha-numeric in your feature and dimension names.

This is the exact type of randomness you can expect if you do this.


LETTERS_NUMBERS_AND_UNDESCORES_ONLY

Thank you for the feedback.

i didt quite understand your answer so i would be grateful if you could define it a bit deeper .

in advance thank you

Although PC-Dmis doesn't prevent you from naming features, alignments and dimensions using special characters (by special characters I mean anything other than letters number and underscores) it has been observed by many people to cause odd behavior.


Example: I was an Apps Engineer for Hexagon, and a customer was getting odd results on a ring gauge measurement, I reviewed the program and it was perfect, but reporting 0.016mm big on a calibrated ring gauge. We tried it on a different machine and same result, we switched ring gauges and got the same result. Always with a 0.016mm error.

wrote (copied) a program and got the correct value (or within 0.001mm).

The only difference was I left feature names as PC-Dmis had generated them (i.e. CIR1 instead of 22.265RING)

We renamed his circle without the decimal point in the name - reran it and it reported correctly.


The more symbols and charachters you use, the weirder things get (i.e. !"£$"£$^&$^*&*()*][:~@;'#<>,.??| would probably make Pc-Dmis implode!