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

DCC alignment not automatically following manual alignment

MomPickMeUpImScared
Hello all,

I'm new to PC DMIS and I'm having an issue where it seems like my manual alignment is not properly telling my DCC alignment where the features are.

I'll get a program up and running, and then I have to move the part to a different location on the table for one reason or another.

I run another manual alignment, go to run the program, and it doesn't work.

I was able to resolve the problem by re-setting my initial alignment and updating the dependent features, but my understanding is that I shouldn't have to do this every time and that it should do it automatically.

what am I missing here?
Parents
  • Adding to what has been said your manual alignment has PLN5 with THEO vector as 1,0,0 ( X plus ) but measures 0,1,0 ( Y plus ) it is then used to Level to X plus? There is also no rotation in the alignment.

    The DCC alignment has the datum E with THEO vector of 1,0,0 (x plus) but measures as 0,-1,0 ( Y minus), datum B has vectors 1,0,0 (X plus) but measures 0,-1,0 ( Y minus).

    Datum B ( Y minus) is used as Level X plus?

    Constructed line2 has a vector of 1,0,0 ( X plus) but is used as a Y plus rotation about X ?

    Your DCC alignment sequence is wrong should always be LEVEL, ROTATE,TRANSLATE, never LEVEL,TRANSLATE,ROTATE.


    that is screwy... on a side note how do you handle a part with no clocking features in pcdmis, section of straight pipe for example... I've been rotating to a constructed line to maintain the machine axis as rotation, this part was a simple bushing, ID, OD, and length. To be honest I'm not fuilly convinced it is needed, my understanding was machine axis is maintained anyway in its absence but others have me wondering so knowing it won't hurt I do this now.... 

    LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
THEO/<-0.5,0,0>,<1,0,0>
ACTL/<-0.5,0,0>,<1,0,0>
CONSTR/LINE,ALIGN,1,XPLUS
A1 =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
ALIGNMENT/LEVEL,ZPLUS,TOP_FACE
ALIGNMENT/ROTATE,XPLUS,TO,LIN1,ABOUT,ZPLUS
ALIGNMENT/TRANS,XAXIS,CIR1
ALIGNMENT/TRANS,YAXIS,CIR1
ALIGNMENT/TRANS,ZAXIS,TOP_FACE
ALIGNMENT/END
Reply
  • Adding to what has been said your manual alignment has PLN5 with THEO vector as 1,0,0 ( X plus ) but measures 0,1,0 ( Y plus ) it is then used to Level to X plus? There is also no rotation in the alignment.

    The DCC alignment has the datum E with THEO vector of 1,0,0 (x plus) but measures as 0,-1,0 ( Y minus), datum B has vectors 1,0,0 (X plus) but measures 0,-1,0 ( Y minus).

    Datum B ( Y minus) is used as Level X plus?

    Constructed line2 has a vector of 1,0,0 ( X plus) but is used as a Y plus rotation about X ?

    Your DCC alignment sequence is wrong should always be LEVEL, ROTATE,TRANSLATE, never LEVEL,TRANSLATE,ROTATE.


    that is screwy... on a side note how do you handle a part with no clocking features in pcdmis, section of straight pipe for example... I've been rotating to a constructed line to maintain the machine axis as rotation, this part was a simple bushing, ID, OD, and length. To be honest I'm not fuilly convinced it is needed, my understanding was machine axis is maintained anyway in its absence but others have me wondering so knowing it won't hurt I do this now.... 

    LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
THEO/<-0.5,0,0>,<1,0,0>
ACTL/<-0.5,0,0>,<1,0,0>
CONSTR/LINE,ALIGN,1,XPLUS
A1 =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
ALIGNMENT/LEVEL,ZPLUS,TOP_FACE
ALIGNMENT/ROTATE,XPLUS,TO,LIN1,ABOUT,ZPLUS
ALIGNMENT/TRANS,XAXIS,CIR1
ALIGNMENT/TRANS,YAXIS,CIR1
ALIGNMENT/TRANS,ZAXIS,TOP_FACE
ALIGNMENT/END
Children
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement