hexagon logo
Register Sign in
  • Replies 34 replies
  • Subscribers 222 subscribers
  • Views 392 views
  • Users 0 members are here
Options
Related

GeoTol Axis Data Extraction

bfire85
Is there a way to pull the data from the axis measurements in Geometric Tolerances? I cannot seem to find the correct method to get that data. Is it possible?

  • The GD&T features should be reworked so they follow the same layout as the "regular" features when it comes to accessing their values:

    FCFLOC1.ITEM .X
    FCFLOC1.ITEM.Y
    FCFLOC1.ITEM.Z
    FCFLOC1.ITEM.TX
    FCFLOC1.ITEM.TY
    FCFLOC1.ITEM.TZ
    etc...

    To have some consistency throughout PC-DMIS. This would greatly enhance the user automation possibilities.
  • Hi

    I can only offer you the good old string formatting if you don't like the detour via the csv file. 

    
ASSIGN/COUNT=0

L1 =LABEL/

ASSIGN/COUNT=COUNT+1
ASSIGN/VANGLE=90+DOUBLE(LEFT(GETTEXTEX("REPORT_LABEL_MEAS", COUNT, "SEG=1", "FCFLOC1"),13))

ANGLE =GENERIC/NONE,DEPENDENT,CARTESIAN,OUT,$
NOM/XYZ,<0+0,0+0,0+0>,$
MEAS/XYZ,<0+0,0+0,0+0>,$
NOM/IJK,<0+0,0+0,1+0>,$
MEAS/IJK,<0+0,0+0,1+0>,$
RADIUS/0+0,0+0,$
ANGLE/90+0,VANGLE,$
DISTANCE/0+0,0+0

IF_GOTO/COUNT<4,GOTO = L1
  • Hi

    I can only offer you the good old string formatting if you don't like the detour via the csv file. 

    
ASSIGN/COUNT=0

L1 =LABEL/

ASSIGN/COUNT=COUNT+1
ASSIGN/VANGLE=90+DOUBLE(LEFT(GETTEXTEX("REPORT_LABEL_MEAS", COUNT, "SEG=1", "FCFLOC1"),13))

ANGLE =GENERIC/NONE,DEPENDENT,CARTESIAN,OUT,$
NOM/XYZ,<0+0,0+0,0+0>,$
MEAS/XYZ,<0+0,0+0,0+0>,$
NOM/IJK,<0+0,0+0,1+0>,$
MEAS/IJK,<0+0,0+0,1+0>,$
RADIUS/0+0,0+0,$
ANGLE/90+0,VANGLE,$
DISTANCE/0+0,0+0

IF_GOTO/COUNT<4,GOTO = L1


    I'll have to try that out. I wasn't sure how to work in the CHR(13) in this instance.
  • in reply to bfire85
    ah sorry that has to be the 1133 instead of "REPORT_LABEL_MEAS", my bad

    this "REPORT_LABEL_..." always gives exactly 13 characters and then a Chr(13) character too end the line.
    thats why Left(...,13) -> you can convert the rest into a number which removes the spaces
  • Hi

    I can only offer you the good old string formatting if you don't like the detour via the csv file. 

    
ASSIGN/COUNT=0

L1 =LABEL/

ASSIGN/COUNT=COUNT+1
ASSIGN/VANGLE=90+DOUBLE(LEFT(GETTEXTEX("REPORT_LABEL_MEAS", COUNT, "SEG=1", "FCFLOC1"),13))

ANGLE =GENERIC/NONE,DEPENDENT,CARTESIAN,OUT,$
NOM/XYZ,<0+0,0+0,0+0>,$
MEAS/XYZ,<0+0,0+0,0+0>,$
NOM/IJK,<0+0,0+0,1+0>,$
MEAS/IJK,<0+0,0+0,1+0>,$
RADIUS/0+0,0+0,$
ANGLE/90+0,VANGLE,$
DISTANCE/0+0,0+0

IF_GOTO/COUNT<4,GOTO = L1


    For some reason, I cannot edit my previous post...

    However, when I do this, it returns a "0" rather than the angle or deviation on the angle. At this point, I will stick with my route unless I am missing something.
  • hello,

    do you have time to find out why it doesn't work for you?

    Of course, this assign code does not work if you have clicked on several axes, only "PA" and "DF" may be clicked because "PA" has to be in the first line.

  • hello,

    do you have time to find out why it doesn't work for you?

    Of course, this assign code does not work if you have clicked on several axes, only "PA" and "DF" may be clicked because "PA" has to be in the first line.

    {"data-align":"none","data-size":"large","data-attachmentid":517270}

    Now it works! Not sure what in the world was going on with that yesterday.

    Thanks for the help!
  • Ok what I discovered in Xactmeasure Probably the same for Geo, but when I created a position for 2 or more holes under Assignment this what you can extract, First pic, When you do single callouts, This is what you can extract, 2nd Pic

  • Ok what I discovered in Xactmeasure Probably the same for Geo, but when I created a position for 2 or more holes under Assignment this what you can extract, First pic, When you do single callouts, This is what you can extract, 2nd Pic

    {"data-align":"none","data-size":"large","data-attachmentid":517292} {"data-align":"none","data-size":"large","data-attachmentid":517293}

    Geo Tol does not allow you to extract the axis locations like Xact did. The work around from Henniger and SABarber is the only way, at the moment.


    This should be created as a sticky at the top of the forum because I am sure I am not the only one who wants to extract the axis location.


  • I found a way to pull in a second axis out of the string set ASSIGN/V1=GETTEXTEX(1133, 1, "SEG=1", "FCFLOC1") 

    ASSIGN/V5=DOUBLE(MID(GETTEXTEX(1133,1,"SEG=1","FCFLOC1"),13))


    Can you test and validate on your end?
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement