Siemens NX Programming
Expand your possibilities! Siemens NX (formerly Unigraphics Siemens NX) offers your company a huge potential to reduce costs and increase productivity. How? We are pleased to show you.
Designing and developing products, tools, machinery and equipment today is not imaginable without the constructional CAD / CAM system Siemens NX of Siemens PLM Software.
For you, we develop software solutions for NX, which are specially adapted to your needs. We are constantly on standards – so you can easily continue to develop your Add-on for your NX system even within years from now.
With over [date_year] years of experience of Siemens NX Customized Solution programming for numerous international companies such as Bosch, Heidelberg KSB, Siemens or Nolte and a number of proprietary Siemens NX extensions, we guarantee a professional implementation in a short time.
Find out more about our references.
For you, we create highly effective programs that simplify and automate your processes, create interfaces between software and machines and let your employees do their jobs faster.
Read more about some recent Customized Solutions for our customers.
See for yourself the quality of our software solutions and Siemens NX extensions:
Siemens NX programs by neoapps offer a broad variety of options regarding adjustments, development of own programs and their integration. The following is a brief overview of the tools and their use, willingly and consciously in simple words.
NXOpen programming with NX
Today Siemens NX programs typically are programmed in the context of NXOpen interface. This interface is the so-called Common API of NX, where it is free to developers in which language they develops their programs.
In addition to C++ also VB.NET, C # and Java are supported by the NXOpen interface. The big advantage is that a common functional basis can be accessed with the Common API, regardless of which programming language is choosed.
For the development with NXOpen an authoring-license is required. However, unlike the programming with user functions, no more runtime license is required to run the self-developed programs. Rather that, the functions themselves are “knowing” in which module they were interactively kept.
For these modules there has to exist a licenses at runtime. Still, the program must be signed by the developer to execute the program.
The journaling, which is often considered as a (moral) successor of the macros, is creating journals that can be played back. They are registered in VB, C + +, C # or Java and can be integrated into existing NXOpen projects of the appropriate language and can be adapted.
The UIStyler can be used for the creation of the user interfaces and since NX6 the Block-Styler is available, too. Alternatively, all of the functionality of the GUI libraries associated with the appropriate languages (such as VB.NET and C #: WinForms; C++: MFC; Java: Swing) can be accessed.
Macro programming with NX
Recording macros is simple, fast and you can achieve results in a very short time. Here is a sequence of instructions during the interactive execution recorded and stored for later play back.
Unfortunately, macros are not fully version-compatible and they can only be used in a limited way to access the geometry but rather the functionality of NX.
The great advantage of the macro-programming is the rapid automation of simple workflow, which is implemented in a short time.
GRIP programming with NX
The GRIP API stands for “Interactive Graphics Programming” and constitutes a rudimentary programming language that is a mixture of BASIC and FORTRAN view.
Many interactive Siemens NX functions can be performed with it. In addition to basic functions such as file processing or user input can be realized.
Generally GRIP programs are version-compatible – but they don’t offer very much comfort in terms of performance and the user interface. The further development of this programming language is stopped.
It was used to program smaller automation tools in GRIP, because it was relatively easy even for a non-professional to create such programs.
GRIP programs require a corresponding runtime license.
User Function Programming with NX
The actual C / C + + API of Siemens NX was called “user functions”. It allowed full access to Siemens NX object structure and also permitted all the possibilities of the traditional software development.
Typically programming was done in C / C + +, so the functionality of existing class libraries, such as MFC from Microsoft, can be fully utilized.
Programs that access Siemens NX via user functions API, require a corresponding runtime license. Since NX5 these programs can alternatively be signed by the developer.
This means that no runtime license is needed anymore. For the creation of user interfaces the UI Styler is available. Alternatively, all the functionality of the Windows MFC can be accessed.
Knowledge Fusion programming with NX
With KF (Knowledge Fusion) the part file can be programmed directly and rules can be encoded so that they will be recalculated in the normal way of form element update.
However, this advantage can redound to a disadvantage, in certain situations. Developing with KF requires an authoring license; Running KF programs, or program code in components with KF rules demands a runtime license.
Have we piqued your interest?
If you have further questions about NX, we are happy to advise you free of charge and without obligation.
You need an individually adjusted, custom-tailored Siemens NX Extension?
If you need a Siemens NX extension that is tailored specifically to your needs, you’ve hit the spot here with neoapps. Contact us – together we can find a solution.
With over [date_year] years of experience in software development for NX, we provide you with individually adjusted, custom-tailored Siemens NX Extension.