The tools to use in NX

Since NX v10 (some 12 years ago) came out. There are many parts of functions of NX that are still around but are some what obsolete. Obsolete is not the right word, There is functionality that can accomplish the same thing and beyond. This article will give you an idea of what functions to use and which ones are around for legacy and are limited compared to what is now available.

Visual Editor
• (limited in functionality, attached to the individual part file)
• Use Knowledge Fusion and UI/Styler

Spreadsheets for data driver
• Very clumsy to use effectively with non expert users
• Attached to the individual part file
• Need to migrate spreadsheets between Windows and Unix environments or use Exceed on Windows
• Difficult to maintain old code
• Use Knowledge Fusion and UI/Styler

Sketcher
• Pre v13 sketch was very primitive compared to what is available now
• Sketcher (post v13) is a great tool if you need to maintain specific sizes, distances, logic
• If you have stayed away from sketcher to now, give it a shot, you can accomplish the same thing using basic curves, but why waste the time, and frustration

Translations
• Unless your moving between applications that don’t accept anything except these formats, there shouldn’t be a need to export these: parasolid, cgm, polygon file, vrml, tiff, gif, bmp, iges, Step203, step214, dxf/dwg, v4 Catia solids
• use Teamcenter Visualization (JT for 3D model representations)
• use PNG (image format, vector based color image)
• use JPEG (image format, standard high quality color image)
• use 2D Exchange (Autocad interopability)
• File -> Save As -> .model (for v4 Catia Solids) unless you want just a specific solid in a part then use the export
• Heal Geometry (for speciality uses)

Automation
• I would like to say don’t use Macro’s and instead use Journal files, but Journal does not completely support all operations, until then macros if needed
• UDF (user defined features) (It’s a functionality that has good and bad points, Stay away from it if you don’t know the limitations)
• Use Knowledge Fusion and UI/Styler to at least package the UDF in an application, or use KF completey if possible
• GRIP (don’t develop new applications based on this)
• Open C (don’t develop new applications based on this, instead use C++ and the Open C API)
• NX/Open is the future, work towards this (you will have the flexibilty of C++, Java, .Net, Knowlege Fusion)
• Knowledge Fusion is the future, but not for everything

What is the edge?
• Deformable parts
• Check Mate
• Smart Line

Interpart linking
• WAVE (the dust has settled and it is a very robust tool)
• Geometry Linker (similiar to WAVE expect used when it is an assembly) This replaces Promotions

Part Identifications
• Part Attributes (nothing has changed in a while with this, they are not exported in JT files either)
• Product Definition (Attached to the part, solid, faces, etc.. and can be exported in the JT files)
• Drafting (they are not dead yet, and are able to pull more information from the solid, if the information is there)
• Embeded GD&T (use this for 3D downstream users, as well and drafting to pull information from)

Editing
• Edit -> Feature -> Parameters is not needed, right click on the entity to edit
• Use the Part Navigator to double click
• hover over entity and drag the handles

View changing
• Previously the 3rd Mouse button click then shade, switch views, etc..
• Now hold down the 3rd Mouse Button and the contect icons show up
• Use gestures (advanced users) by knowing the location of the icons under the 3rd mouse button hold, but don’t wait for it to show up and move in that direction and release. The action is taken

This is just the beginning of the areas of NX to focus on. Many more areas of NX can be filled into each of the categories above, and more categories added. But instead we focused on NX Modeling, Drafting, and Assemblies. There is nothing worse then working on a project using a certain piece of technology and finding limitations and lack of functionality. The more everyone knows about the direction NX is going and focus efforts on using those features the better more reliable the products will be. To sum up, NX almost never removes functionality but usually adds or creates something better in place of the older technology. For example is the new “smart line” going to replace basic curves eventually? Will basic curves disappear? Probably not. So when the “smart line” is mature enough for your process, jump. Until then stick with your foundation of tools you use.

Focus on WAVE, Expressions, Sketcher, Master Model, Product Definition, JT, Embeded GD&T, Knowledge Fusion, Assemblies, Deformable parts, etc.. When you add functionality to your parts I would fully test the limitations of the technology. See what the long term maintainability is, how mature is the technology, is it still in flux and cause breakage later, how much documentation is there, examples, support group.