Extract coordinate value from True Positions via PCM

[[Ri...]]

Can we extract the coordinate values as reported in a true position to a result element?

If yes, will this require a PCM license or just basic PCM?

[[na...]]

Please sign in to view this quote.

 

Try to adapt what Phillip answered -> https://qualityforum.zeiss.com/topic/12522-bore-pattern-best-fit-additional-info/?do=findComment&comment=62730

[[Ch...]]

some relevant info here :

These are more PCM methods..

https://qualityforum.zeiss.com/topic/6602-using-best-fit-true-position/#comment-26378

and here (in 2025 the axis info may no longer show with legacy PCM) ... https://qualityforum.zeiss.com/topic/23353-result-element-new-gdt-position/#comment-131647

 

What version are you using? I'll see if it can be done without PCM...

 

This works in 2024 in Result Element : 

getActual("TP1").actual.x

getActual("TP1").actual.y

 

 

Edited Thursday at 03:30 PM

[[Ri...]]

v2016, v2017 and v2022.

Emphasis on v2022.

Thank you.

[[Ri...]]

Please sign in to view this quote.

"getActual("#34.1").actual.x" doesn't work in v2022.

#34.1 is a true position in Z and X axis.

Edited Thursday at 04:36 PM

[[Ri...]]

deleted

Edited Thursday at 04:43 PM

[[Ch...]]

 

I just tried it in 2022 (7.4.00) with PCM License disabled, works for me. As a sanity check, try making a copy of the position characteristic and name it something different such as TPOS or TPOS1 and try again, shouldn't matter here, but have to make sure.

 

Also do you get an error, or a null value, or other message ??

 

Thanks,

CR

Edited Thursday at 06:05 PM

[[Ri...]]

This is odd.

Why does the PCM work today that didn't work yesterday?

I did not have to change anything, and all of a sudden, it works.

I can't rely on software that works, sometimes...🤬