hexagon logo

DCC alignment not automatically following manual alignment

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
  • Every single program I write has the exact same sequence:

    1) Create a constructed line "for alignment" and force the IJK of that line in the direction I want
    2) Readpoint alignment in a hole or above a corner or something.
    3) Using readpoint alignment, find a plane and a circle.
    4) Create a new alignment recalling startup...Level using plane, rotate using constructed line, XYZ origin to your probed features. This is my "finding" alignment.
    5) Now that the part is found...Drive around and probe the datums
    6) Construct all of my datum alignments that I will need all in a row. Each alignment recalling startup and then being made.
    7) Recall the alignment I want, measure & report stuff, recall next alignment, measure & report stuff..continue as needed

    I NEVER use stuff from my "finding" alignments..they're "junk" features that serve no purpose other than to locate the part for me.
  • I do the same except I use manual start points instead of read points.
    Honestly, I love read points but if I changed the way our programs have been done for years, people would complain.
Reply Children
No Data