Your Products have been synced, click here to refresh
I'm not sure why people are advocating a width in this example. I'm not saying it's wrong but from the description it doesn't sound like in terms of function it behaves as a width.
I'm not even sure if it would be a valid datum.
I'm picturing two nominally coplaner planes but facing opposite directions from each other, the fact they're nominally coplaner but facing opposite directions suggests to me they're offset from each other?
PLN1 =FEAT/CONTACT/PLANE/DEFAULT,CARTESIAN,TRIANGLE,LEAST_SQR THEO/<25,0,0>,<0,0,1> ACTL/<25,0,0>,<0,0,1> TARG/<25,0,0>,<0,0,1> ANGLE VEC=<1,0,0>,RADIAL SHOW FEATURE PARAMETERS=NO SHOW CONTACT PARAMETERS=YES NUMHITS=5,NUMROWS=1 SPACER=6 AVOIDANCE MOVE=NO SHOW HITS=NO PLN2 =FEAT/CONTACT/PLANE/DEFAULT,CARTESIAN,TRIANGLE,LEAST_SQR THEO/<-25,0,0>,<0,0,-1> ACTL/<-25,0,0>,<0,0,-1> TARG/<-25,0,0>,<0,0,-1> ANGLE VEC=<1,0,0>,RADIAL SHOW FEATURE PARAMETERS=NO SHOW CONTACT PARAMETERS=YES NUMHITS=5,NUMROWS=1 SPACER=6 AVOIDANCE MOVE=NO SHOW HITS=NO PLN3 =FEAT/PLANE,CARTESIAN,TRIANGLE,NO THEO/<-25,0,0>,<0,0,1> ACTL/<-25,0,0>,<0,0,1> CONSTR/PLANE,REV,PLN2 PLN4 =FEAT/PLANE,CARTESIAN,TRIANGLE,NO,LEAST_SQR THEO/<0,0,0>,<0,0,1> ACTL/<0,0,0>,<0,0,1> CONSTR/PLANE,BF,PLN1.HIT[1..PLN1.NUMHITS,PLN3.HIT[1..PLN3.NUMHITS],, OUTLIER_REMOVAL/OFF,3 FILTER/OFF,WAVELENGTH=0
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |