lorenolepi
Aerospace
- Jan 22, 2009
- 118
So I have been using NX for about 8 years as a design/drafter and have been amazed by its capabilities. Recently I have been learning the CAM side of NX and I got to say it seems like the ugly step sister of the other applications. Its lack of parametric goodness such as expressions and being able to reference things really gets to me. Example tools and holders... its a crime that if a tool/holder is modeled in NX that it can not be inserted as a tool. You need to re-define the tool through a tool wizard step by step and can only use the 3D model as a graphical reference that has no checks or boundaries against the tool created in the wizard. How hard would it be to have a 3D tool drive the tool library, even if you had to give explicit expression names/values? Same situation with the free-form tools, the way they need to be defined is beyond any logical explanation, why not have a way to be able to cross-section the model and have it auto constrain the definition that CAM side needs?
Another thing that really grinds my gears is how the milling side really seems to be lacking with simple threaded hole features. Its an HOLE not rocket science! The feature based machining is a joke unless you have time to learn a new programming language and your parts are exactly the same every single time (not working for a job shop). With holes already being features in the model tree, why not transfer the information in... I really need to input the size of the hole twice? (Every time you input information, is another time an error can occur not to mention the time that is wasted)
The third thing is and this is far beyond my knowledge but why TCL programming language for shop docs/post? I realize its a cool open source code and all but I havn't been able to find a real class on it. The NX post class isn't going to cover everything you need to have amazing shop doc's. If VB is good enough for NX-open then why not this? How many programming languages does NX expect us to learn to be a good/efficient engineer?
Another thing that really grinds my gears is how the milling side really seems to be lacking with simple threaded hole features. Its an HOLE not rocket science! The feature based machining is a joke unless you have time to learn a new programming language and your parts are exactly the same every single time (not working for a job shop). With holes already being features in the model tree, why not transfer the information in... I really need to input the size of the hole twice? (Every time you input information, is another time an error can occur not to mention the time that is wasted)
The third thing is and this is far beyond my knowledge but why TCL programming language for shop docs/post? I realize its a cool open source code and all but I havn't been able to find a real class on it. The NX post class isn't going to cover everything you need to have amazing shop doc's. If VB is good enough for NX-open then why not this? How many programming languages does NX expect us to learn to be a good/efficient engineer?