I am trying to do an alignment where it’s plane , circle , circle but my x and y dimensions are not calling out properly by following the alignment the customer requested. Unless I’m misunderstanding I also don’t think the x y and x should be at an angle and that that is also why my callouts for dimensioning aren’t correct .
adjust the nominals of your manual circles to the X and Y on the print. Easier to visualize if you make one zero-zero and then have basics to the second hole, lets say 2" on X and 1" on Y.
CIR1
(0,0,0) (0,0,1)
CIR2
(2,1,0) (0,0,1)
Level PLN1 ZPlus
Trans PLN1 Z
Trans CIR1 X
Trans CIR1 Y
Best Fit, Rotation Only, Least Squares, Rotation about Z plus, CIR1 and CIR2
Trans PLN1 Z
Trans CIR1 X
Trans CIR1 Y
Why translate twice? Because sometimes PcDmis is stupid.
This morning I didn't translate first, and it rotated 80° off or something silly.
In the past, I haven't translated after and the Z has dropped an inch and a half.
Just translate twice and never have a worry.
This way, if the holes are right, you aren't having error added by the angle you calculated for rotation.
Let the software best fit the two holes so the error is balanced.
In my opinion, anyway.
If there is something wrong in the code itself, highlight and copy, then past it here and put the Code and /Code tags around it so it looks like code (code and /code go inside [ ] brackets, code in front /code at end).
adjust the nominals of your manual circles to the X and Y on the print. Easier to visualize if you make one zero-zero and then have basics to the second hole, lets say 2" on X and 1" on Y.
CIR1
(0,0,0) (0,0,1)
CIR2
(2,1,0) (0,0,1)
Level PLN1 ZPlus
Trans PLN1 Z
Trans CIR1 X
Trans CIR1 Y
Best Fit, Rotation Only, Least Squares, Rotation about Z plus, CIR1 and CIR2
Trans PLN1 Z
Trans CIR1 X
Trans CIR1 Y
Why translate twice? Because sometimes PcDmis is stupid.
This morning I didn't translate first, and it rotated 80° off or something silly.
In the past, I haven't translated after and the Z has dropped an inch and a half.
Just translate twice and never have a worry.
This way, if the holes are right, you aren't having error added by the angle you calculated for rotation.
Let the software best fit the two holes so the error is balanced.
In my opinion, anyway.
If there is something wrong in the code itself, highlight and copy, then past it here and put the Code and /Code tags around it so it looks like code (code and /code go inside [ ] brackets, code in front /code at end).
