Your Products have been synced, click here to refresh
I can give you at least one example where this can be handy. If you program a part without CAD, and then wanted to add a CAD model after the fact, you would need to use CAD = PART. I suspect there might be another reason or two, but this is the first that comes to mind. I agree not everyone needs it, and it is often mis-understood, but it can still be handy on occasion.
oh, and I do not consider this to make me far wiser than you, but as someone told me recently (so as not to call me old), I might have more experience.
Nope, not true, not even CLOSE to true. You do NOT ever "need" to translate a model, not for any reason at all.
AND OTHER RELATED GOOD INFO.
I have never translated a model, every model I've worked with (and we are 99.999995% CAD here) I've used AS IS.
Using the 3-D rotate view, you rotate the model until it matches how it sits on the table. Then SAVE THE VIEW. Then F5 and set the machine axis to match the cad axis. All done.
.
Nope, no shift, no change, tri-thingie still in the same place. ALL IT DOES is 'reassigns' the axis inside the controller to new 'values', X will be Y, Z will be X, Y will be Z, or however you set it up. IF you move the jogbox in X (before you make an alignment) and you have the machine X axis equal to the Y CAD axis, you will see the numbers in Y change instead of the numbers in X on the probe position readout.
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |