Pulling data from XactMeasure

[LaserJay]

Does anyone know if there is a way to pull a MAX and MIN value from a true position in XactMeasure?

I want to be able to see
MIN = .0017
MAX= .0036

When I try ITEM95.TP.MAX it always = 0
Maybe there is another way to write it that PCDMIS will understand?



Capture.JPGCapture1.JPG

Thanks in advance for the help

[bfire85]

Use the GETTEXT function.

ASSIGN/V1=GETTEXT(688,1,{ITEM95})
ASSIGN/V2=GETTEXT(688,2,{ITEM95})
ASSIGN/V3=GETTEXT(688,3,{ITEM95})
ASSIGN/V4=GETTEXT(688,4,{ITEM95})
ASSIGN/V5=GETTEXT(688,5,{ITEM95})
ASSIGN/V6=GETTEXT(688,6,{ITEM95})
ASSIGN/VMAX=MAX(ARRAY(V1,V2,V3,V4,V5,V6))
ASSIGN/VMIN=MIN(ARRAY(V1,V2,V3,V4,V5,V6))
​​​​​​​

[LaserJay]

Hey @bfire85 where is the 688 from?

[bfire85]

Hey @bfire85 where is the 688 from?

If you do a PC-DMIS Help File search for "A List of Available Data Types", it gives you command numbers for everything you need to extract data from.

[LaserJay]

If you do a PC-DMIS Help File search for "A List of Available Data Types", it gives you command numbers for everything you need to extract data from.

Thank you bfire85 ! That works great!

[LaserJay]

Did something change on this when they updated to GEOTOL?
I cant get this to work

ASSIGN/V1=GETTEXT(688,1,{ITEM95})

[neil.challinor]

Yes, the GETTEXT assignment you show here specifically targets a Xactmeasure command. Since XactMeasure no longer exists the GETTEXT assignment will not return anything. You can still use GETTEXT and the new GETTEXTEX functions to pull data from geometric tolerance commands but you would need to edit any previous XactMeasure references. We provided much more expressions functionality in general to make it easier to pull data using the more common dot syntax (.meas, .dev, .outtol for example). This is a link to a prior thread where we discussed converting existing XactMeasure GETTEX expressions.

https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-code-samples/478298-convert-xactmeasure-gettext-to-expressions-for-geometric-tolerance-commands

[KIRBSTER269]

68 is interesting. Not sure how it could be applied in DMIS. But we were all aware of this because at 69, you got to get up and turn around.

Capture.JPG

[R2ah1ze1l]

I'd 'like' it, but it keeps erroring out. Now that is funny

[KIRBSTER269]

R2ah1ze1l wondering if anybody would have got that.

[LaserJay]

neil.challinor With the new function is there an easier way to do min and max of a tpos deviation? I dont really want to make an array of 105 of these functions.

ASSIGN/V1=DIM22_1.SEGMENT[1].FEATURE[1-105].MAX
ASSIGN/V1=DIM22_1.SEGMENT[1].FEATURE[1-105].MIN

something like this? (but that actually works lol )

[Probe_101]

'LaserJay, or anyone else that might know, I appear to have had success pulling the min/max from the GeoTol using "FeatureName.SEGMENT[1].FEATURE[1-99].MAX".

Does anyone know the correct syntax for pulling the diameter min/max from the GeoTol True Position?

[Henniger123]

with a Basic-script its posible, maybe this is a thing for you ?

i dont know if its posible with assign command

[MikeF]

If 688 is for Xactmeasure position how do you know that if 688 is LINE2_MEAS, So what want to know is there another chart that tells you what LINE2_MEAS is?

[neil.challinor]

https://docs.hexagonmi.com/pcdmis/2020.2/en/helpcenter/mergedProjects/automationobjects/webframe.html#PCDLRN~ENUM_FIELD_TYPES.html

[MikeF]

that still shows me LINE2_MEAS how do i know what LINE2_MEAS is position?