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

Hello

I think I found a bug with the extraction (in a variable) of the z value in a position command.

I have a position of a plane to datum B (also a plane). The nominal distance is 43.64mm.
The measured TP value of the feature is 0.518015 and the measured z-value of the feature is 43.899007.

When extracting the z-value via a variable I get a totally different value of 43.810238. A difference of approx. 0.09mm

To verify the result of the position feature, I aligned to datum B and evaluated each z-value of the plane.
The worst z-value of the individual points is 43.899024... so nearly identical to the position evaluation.
So the error must be in the extracted value.

I don't have any special characters in the name of the features.
PC-DMIS version is 2021.2 SP8 (Build-Nr. 524).

neil.challinor Don Ruggieri

May I send the routine to one of you guys to investigate?

Parents

Aaron Baldauf over 1 year ago

In the meantime I also got another response from Hexagon by mail:

Apologies for the delay in responding I was on holiday last week. I have spoken to Neil and we are going to raise this as a bug. I will keep you posted on how this progresses.

In the short term if you want to find the highest or lowest point you can use the Construct Point option and there is an Extreme Point method which uses the raw hits to evaluate the max or min point either to the current alignment or a user defined alignment. So in your example after the alignment is created you can construct the extreme point and then report this using the legacy position.

And again my reply:

Thank you very much for looking into this again and treating this as a bug.

Regarding the highest and lowest point. I think there was a misunderstanding.

I only mentioned the extreme points to show that Hexagon used to provide little helper tools (in my example the HighPoint.exe) for stuff that was hard for the user to do.
As it's very complicated to get to the axis data at the moment, I thought a little helper tool would be great addition until PC-DMIS gets an easier native way.

To actually use the extreme point method is not a solution as not every datum system is reproducible using a classic alignment.
Again, this was only to show about what kind of tools I was referring.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Aaron Baldauf over 1 year ago

In the meantime I also got another response from Hexagon by mail:

Apologies for the delay in responding I was on holiday last week. I have spoken to Neil and we are going to raise this as a bug. I will keep you posted on how this progresses.

In the short term if you want to find the highest or lowest point you can use the Construct Point option and there is an Extreme Point method which uses the raw hits to evaluate the max or min point either to the current alignment or a user defined alignment. So in your example after the alignment is created you can construct the extreme point and then report this using the legacy position.

And again my reply:

Thank you very much for looking into this again and treating this as a bug.

Regarding the highest and lowest point. I think there was a misunderstanding.

I only mentioned the extreme points to show that Hexagon used to provide little helper tools (in my example the HighPoint.exe) for stuff that was hard for the user to do.
As it's very complicated to get to the axis data at the moment, I thought a little helper tool would be great addition until PC-DMIS gets an easier native way.

To actually use the extreme point method is not a solution as not every datum system is reproducible using a classic alignment.
Again, this was only to show about what kind of tools I was referring.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data