hexagon logo

Alignment from FCF Datum Shift



I think what vpt (and me) were hoping for was a way to create an alignment that uses the Xact fit shift. There are all sorts of applications for this. Using the available options in best-fit alignment is not the same, because they do not attempt to fit within a tolerance zone.

A few years old but I haven't found anything using search.

SPH1       =GENERIC/SPHERE,DEPENDENT,CARTESIAN,OUT,$
            NOM/XYZ,<0,0,0>,$
            MEAS/XYZ,<0,0,0>,$
            NOM/IJK,<0,0,1>,$
            MEAS/IJK,<0,0,1>,$
            DIAMETER/1,1.1
DIM LOC1= LOCATION OF SPHERE SPH1
AX    NOMINAL       +TOL       -TOL       MEAS        DEV     OUTTOL
D       1.0000     0.2500    -0.2500     1.1000     0.1000     0.0000 ------#--
END OF DIMENSION LOC1
            DATDEF/FEATURE=SPH1,A
            DISPLAYPRECISION/6
FCFLOC1 =POSITION : CIR152_1,CIR152_2,CIR152_3,...
            FEATCTRLFRAME/SHOWNOMS=NO,SHOWPARAMS=NO,SHOWEXPANDED=NO
              SIZE TOLERANCES/33,DIAMETER,0.375,0.005,-0.005
              PRIMARY DIMENSION/POSITION,DIAMETER,0.01,MMC,A,MMC,,
              NOTE/FCFLOC1
            FEATURES/CIR152_1,CIR152_2,CIR152_3,CIR152_4,CIR152_5,
                                CIR152_6,CIR152_7,CIR152_8,CIR152_9,CIR152_10,
                                CIR152_11,CIR152_12,CIR152_13,CIR152_14,
                                CIR152_15,CIR152_16,CIR152_17,CIR152_18,
                                CIR152_19,CIR152_20,CIR152_21,CIR152_22,
                                CIR152_23,CIR152_24,CIR152_25,CIR152_26,
                                CIR152_27,CIR152_28,CIR152_29,CIR152_30,
                                CIR152_31,CIR152_32,CIR152_33,,
            ASSIGN/V1=GETTEXT("DRF_SHIFTX",1,{FCFLOC1})
            ASSIGN/V2=GETTEXT("DRF_SHIFTY",1,{FCFLOC1})
            ASSIGN/V3=GETTEXT("DRF_SHIFTZ",1,{FCFLOC1})
            ASSIGN/V4=GETTEXT("DRF_ROTATIONX",1,{FCFLOC1})*-1
            ASSIGN/V5=GETTEXT("DRF_ROTATIONY",1,{FCFLOC1})*-1
            ASSIGN/V6=GETTEXT("DRF_ROTATIONZ",1,{FCFLOC1})*-1
            FORMAT/TEXT, , ,HEADINGS, , ;NOM,MEAS, , , , , 
DIM BEFORE= LOCATION OF CIRCLE CIR152_1
AX     NOMINAL        MEAS
X     10.153721   10.154507
Y    -27.402826  -27.405035
Z     -8.032519   -8.025360
END OF DIMENSION BEFORE
ALIGN1     =ALIGNMENT/START,RECALL:PREVIOUS,LIST=YES
              ALIGNMENT/ROTATE_OFFSET,V4,ABOUT,XPLUS
              ALIGNMENT/ROTATE_OFFSET,V5,ABOUT,YPLUS
              ALIGNMENT/ROTATE_OFFSET,V6,ABOUT,ZPLUS
              ALIGNMENT/TRANS_OFFSET,XAXIS,V1
              ALIGNMENT/TRANS_OFFSET,YAXIS,V2
              ALIGNMENT/TRANS_OFFSET,ZAXIS,V3
            ALIGNMENT/END
DIM AFTER= LOCATION OF CIRCLE CIR152_1
AX     NOMINAL        MEAS
X     10.151373   10.152161
Y    -27.394485  -27.396694
Z     -8.041472   -8.034312
D      0.376500    0.377383
END OF DIMENSION AFTER
            COMMENT/REPT,
            "Xshift:  "+V1
            "Yshift:  "+V2
            "Zshift:  "+V3
            "Rotation X:  "+V4*-1
            "Rotation Y:  "+V5*-1
            "Rotation Z:  "+V6*-1

The FCF output with datum shift is:


Using a sphere as the only datum seems to allow all 6 degrees to float. There is some small round-off error due to the numbers being used limited to the current DISPLAYPRECISION (not much).

Now what? Trying to actually use this has me baffled. I'd like to simulate the FCF output having the transformed measured coordinates evaluated against the model nominal values. The BEFORE dim has the nominals I want but the AFTER dim has the measured I want (like the FCF output). Inserting & Recalling alignments, Updating Dependent Commands (answering both yes and no) leaves me feeling like I've found my way into a rabbit hole. Maybe Profile dims behave differently?

I'm aware that some settings may influence the results: Update Dependent Commands (warning), UpdateBelowChangedAlignmentDuringExecution (registry), Ignore CAD to part (F5 settings), Allow Fine Tuning of Alignment (F5 settings). I'd really like to get this working inline without resorting to any type of external automation if possible. Can someone throw me a bone here? There's gotta be a way to get some mileage out of this.
Parents
  • GETTEXT("SUMMARY_MEAS",1,{FCF_DIM}) retrieves the value for the first axis of the first feature. The value itself depends on what axis has been enabled for the features. At the bottom of the Advanced tab for the FCF dialog is a section for determining what actually gets reported (X, Y, Z, PR, PA, DF, etc). Whatever is enabled here is what will be available in the SUMMARY_MEAS. For example, if you have Y, PR, DF selected for output then only the Y & PR fields will be available in SUMMARY_MEAS (diameter is another enum). Only locational values are in SUMMARY_MEAS.

    So, if you had 2 composite position holes with Y,PR,DF enabled the SUMMARY_MEAS fields would be:

    Segment:__Upr_Segment_|_Lwr_Segment
    Feature:___C1__|__C2__|__C1__|__C2
    Index:____1__2_|_3__4_|_5__6_|_7__8
    Axis:_____Y_PR_|_Y_PR_|_Y_PR_|_Y__PR


    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",1,{FCF_DIM}) 'C1 "Y" value for upper segment
    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",5,{FCF_DIM}) 'C1 "Y" value for lower segment


    If you had X,Y & Z enabled for locational output this would be your situation:

    Segment:__|_Upr_Segment__|___Lwr_Segment___|
    Feature:__|__C1__|___C2__|___C1__|____C2___|
    Index:____|1_2_3_|_4_5_6_|_7_8_9_|_10_11_12|
    Axis:_____|X_Y_Z_|_X_Y_Z_|_X_Y_Z_|__X__Y__Z|


    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",1,{FCF_DIM}) 'C1 "X" value for upper segment
    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",8,{FCF_DIM}) 'C1 "Y" value for lower segment

    The methods you list for obtaining the Datum Shift values seem correct. The jury is still out on what the Datum Shift values actually represent in a given context. But if you are only using the values for trending I wouldn't think that would matter.
Reply
  • GETTEXT("SUMMARY_MEAS",1,{FCF_DIM}) retrieves the value for the first axis of the first feature. The value itself depends on what axis has been enabled for the features. At the bottom of the Advanced tab for the FCF dialog is a section for determining what actually gets reported (X, Y, Z, PR, PA, DF, etc). Whatever is enabled here is what will be available in the SUMMARY_MEAS. For example, if you have Y, PR, DF selected for output then only the Y & PR fields will be available in SUMMARY_MEAS (diameter is another enum). Only locational values are in SUMMARY_MEAS.

    So, if you had 2 composite position holes with Y,PR,DF enabled the SUMMARY_MEAS fields would be:

    Segment:__Upr_Segment_|_Lwr_Segment
    Feature:___C1__|__C2__|__C1__|__C2
    Index:____1__2_|_3__4_|_5__6_|_7__8
    Axis:_____Y_PR_|_Y_PR_|_Y_PR_|_Y__PR


    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",1,{FCF_DIM}) 'C1 "Y" value for upper segment
    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",5,{FCF_DIM}) 'C1 "Y" value for lower segment


    If you had X,Y & Z enabled for locational output this would be your situation:

    Segment:__|_Upr_Segment__|___Lwr_Segment___|
    Feature:__|__C1__|___C2__|___C1__|____C2___|
    Index:____|1_2_3_|_4_5_6_|_7_8_9_|_10_11_12|
    Axis:_____|X_Y_Z_|_X_Y_Z_|_X_Y_Z_|__X__Y__Z|


    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",1,{FCF_DIM}) 'C1 "X" value for upper segment
    ASSIGN/V1=GETTEXT("SUMMARY_MEAS",8,{FCF_DIM}) 'C1 "Y" value for lower segment

    The methods you list for obtaining the Datum Shift values seem correct. The jury is still out on what the Datum Shift values actually represent in a given context. But if you are only using the values for trending I wouldn't think that would matter.
Children
No Data