hexagon logo

Move points changing with new alignments.

New programmer here. After I had already made a program and tested it, I had to go back and create another alignment for a few dimensions. Which of course changed all of my move points after that. I would have thought that recalling my original alignment after getting those dimensions would have restored my move points to their original coordinates, but it did not. I'm fresh out of class and this is only my 3rd program if you can't tell. Any help would be appreciated.
  • Welcome. If you add a new alignment or change an existing alignment it should ask you "Update features below to new alignment?" If you click "YES" it will do just that, in your case it looks like you need to answer "NO" to the question.
  • Move points don't adjust like they are supposed to when you mess with alignments in programs that have measured data. I have dealt with this plenty of times. After adjusting alignments, my features are correct but MOVE/POINT and MOVE/INCREMENT moves get messed up. The only way I have found to get this to work as expected is to run the program offline so that EVERYTHING is reset back to nominal BEFORE adjusting any alignments. If I do this before adjusting my alignment, then the path is not affected and will be adjusted as expected. HTH
  • Can variables be used in move points?

    I almost exclusively use move-clearplane because of this. It's quicker to fix the few clearplane definitions than the dozen or so moves I'd have to program to dance around a part.
  • Thanks all for the advice. I've been trying to figure out clearance planes, but they just don't seem to work for me. Obviously I'm not doing something right, but I just don't see their usefulness in the kind of parts I check.
  • When I have to go back in and add an alignment in the middle of an already existing one, the first thing I do is a recall of the alignment you are already / currently in. Then move up one line from the recall and construct your new alignment, and then add your new probing after the new alignment, but before the recall. That way, everything afterwards does not get changed, regardless of whether answering yes or no to the update below question.
  • Hello,
    I would have to do the same as and @ ​ and it would fix the issues. Another thing I found is that has worked for me is. In a best-fit alignment, I would have to uncheck the iterate and repierce CAD.


    Attached Files