PC-DMIS 2021.2 - Possible bug with variable of position evaluation

My apologies I mislead you slightly, the returned measured value from QA1637.Z.MEAS is actually the first point of the plane. If you turn on the textual analysis you can see the data
​

You can see the (1) 43.810238 represents the value obtained from ASSIGN/V_QA1637=QA1637.Z.MEAS

The issue as you have identified is that this not the worst point, point number (3) is the worst value and this is what you wish to extract. This will change for each part obviously.

I did reach out to the developers and the syntax QA1637.Z.MEAS is the old way to use expressions. It may work with single features and single segments but not multi feature/multi segment. For example if you report position of 4 holes the dimension_name.X.meas would only return the first hole in the pattern.

With the geometric tolerance command because it supports multiple segments and features you use the QA1637.SEGMENT[1].FEATURE[1].MEAS. This does return the measured value of the true position. The expression builder lets you create QA1637.SEGMENT[1].FEATURE[1].MEAS but not QA1637.Z.MEAS unless you type it into the program. Where we are lacking is the ability to pull more data than the measured, deviation, nominal etc

For the measured value of the individual axis in your example we could not identify a way in which to obtain this other than as I indicated in my previous mail.

Your suggestion in the ideas centre is a good one and I will discuss this with Neil when he is back from holiday. Thank you

My apologies I mislead you slightly, the returned measured value from QA1637.Z.MEAS is actually the first point of the plane. If you turn on the textual analysis you can see the data
​

You can see the (1) 43.810238 represents the value obtained from ASSIGN/V_QA1637=QA1637.Z.MEAS

The issue as you have identified is that this not the worst point, point number (3) is the worst value and this is what you wish to extract. This will change for each part obviously.

I did reach out to the developers and the syntax QA1637.Z.MEAS is the old way to use expressions. It may work with single features and single segments but not multi feature/multi segment. For example if you report position of 4 holes the dimension_name.X.meas would only return the first hole in the pattern.

With the geometric tolerance command because it supports multiple segments and features you use the QA1637.SEGMENT[1].FEATURE[1].MEAS. This does return the measured value of the true position. The expression builder lets you create QA1637.SEGMENT[1].FEATURE[1].MEAS but not QA1637.Z.MEAS unless you type it into the program. Where we are lacking is the ability to pull more data than the measured, deviation, nominal etc

For the measured value of the individual axis in your example we could not identify a way in which to obtain this other than as I indicated in my previous mail.

Your suggestion in the ideas centre is a good one and I will discuss this with Neil when he is back from holiday. Thank you