Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
In the case of a 5 axis reposition there are many case where I manually want to decide how to move the tool to prevent both collision and full retract.
If you put this in a manual move, we can sketch our own toolpath.
Tool orientation? You could link multiple manual moves.
This is how I worked before in ESPRIT. An addin let you create the moves one by one with orientation. This is then put in one folder. Thats all you need.
In NX, generic motion is also the basis for a ton of other rare use-case implementation stuff. Bar pull/tailstock/part transfer etc all rely heavily on either user defined events (similar to manual NC) or generic motion, or often some combo of the two stored as a template. It's useful for sure, and their implementation would be a good framework to strive for.