0% found this document useful (0 votes)

201 views129 pages

NX Open Getting Started Guide

Uploaded by

Mohan Kumar

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

201 views129 pages

NX Open Getting Started Guide

Uploaded by

Mohan Kumar

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 129

NX 2007 Release

Notes
NX 2007 Series
Unpublished work. © 2021 Siemens

This material contains trade secrets or otherwise confidential information owned by Siemens Industry Software, Inc., its
subsidiaries or its affiliates (collectively, "Siemens"), or its licensors. Access to and use of this information is strictly limited as set
forth in Customer's applicable agreement with Siemens. This material may not be copied, distributed, or otherwise disclosed
outside of Customer's facilities without the express written permission of Siemens, and may not be used in any way not
expressly authorized by Siemens.

This document is for information and instruction purposes only. Siemens reserves the right to make changes in specifications
and other information contained in this publication without prior notice, and the reader should, in all cases, consult Siemens to
determine whether any changes have been made. Representations about products, features or functionality in this document
constitute technical information, not a warranty or guarantee, and shall not give rise to any liability of Siemens whatsoever.
Siemens disclaims all warranties including, without limitation, the implied warranties of merchantability and fitness for a
particular purpose. In particular, Siemens does not warrant that the operation of the products will be uninterrupted or error
free.
The terms and conditions governing the sale and licensing of Siemens products are set forth in written agreements between
Siemens and its customers. Siemens' End User License Agreement and Universal Contract Agreement may be viewed at: https://
www.sw.siemens.com/en-US/sw-terms/
TRADEMARKS: The trademarks, logos, and service marks ("Marks") used herein are the property of Siemens or other parties. No
one is permitted to use these Marks without the prior written consent of Siemens or the owner of the Marks, as applicable. The
use herein of third party Marks is not an attempt to indicate Siemens as a source of a product, but is intended to indicate a
product from, or associated with, a particular third party. A list of Siemens' trademarks may be viewed at:
www.plm.automation.siemens.com/global/en/legal/trademarks.html. The registered trademark Linux® is used pursuant to a
sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide basis.

About Siemens Digital Industries Software

Siemens Digital Industries Software is a leading global provider of product life cycle management (PLM) software and services
with 7 million licensed seats and 71,000 customers worldwide. Headquartered in Plano, Texas, Siemens Digital Industries
Software works collaboratively with companies to deliver open solutions that help them turn more ideas into successful
products. For more information on Siemens Digital Industries Software products and services, visit www.siemens.com/plm.

Support Center: support.sw.siemens.com

Send Feedback on Documentation: support.sw.siemens.com/doc_feedback_form

Contents

Welcome to NX 1-1

NX System Information
Customer support ───────────────────────────────────── 2-1
Platforms ─────────────────────────────────────────── 2-1
NX central runtime directory ───────────────────────────────── 2-1
System requirements guidelines ─────────────────────────────── 2-3
Operating system requirements ─────────────────────────────── 2-6
Supported hardware and graphics ───────────────────────────── 2-12
NX Open programs on Linux ───────────────────────────────── 2-13
Initializing the JVM ─────────────────────────────────────── 2-14
NX variables in the ugii_env.dat file ──────────────────────────── 2-16
Browser requirements ────────────────────────────────── 2-18
Browser requirements ───────────────────────────────────── 2-18
Licensing Caveats ──────────────────────────────────── 2-19
General licensing caveats ─────────────────────────────────── 2-19
Licensing caveats for Windows ─────────────────────────────── 2-20
Licensing caveats for Linux ────────────────────────────────── 2-21
Product compatibility - supported release combinations ──────────── 2-22
NX compatibility with Spreadsheet ───────────────────────── 2-25
NX applications unsupported on specific platforms ─────────────── 2-26
Support for touch enabled devices ────────────────────────── 2-27
Legacy commands and commands to be retired ───────────────── 2-28
Retired commands in NX ─────────────────────────────────── 2-29

NX Caveats and Product Notes

Teamcenter Integration for NX ───────────────────────────── 3-1
Product Notes ────────────────────────────────────────── 3-1
Caveats ────────────────────────────────────────────── 3-2
Fundamentals ─────────────────────────────────────── 3-2
Product Notes ────────────────────────────────────────── 3-2
Caveats ────────────────────────────────────────────── 3-4
Customer Defaults ───────────────────────────────────── 3-5
Customer defaults ──────────────────────────────────────── 3-5
Design (CAD) ──────────────────────────────────────── 3-6
Assemblies ──────────────────────────────────────────── 3-6
NX Analysis ──────────────────────────────────────────── 3-6
Coating ────────────────────────────────────────────── 3-6
Digital Mockup (DMU) ───────────────────────────────────── 3-7
Animation Designer ────────────────────────────────────── 3-10
Layout ────────────────────────────────────────────── 3-11
Product and Manufacturing Information (PMI) ────────────────────── 3-11

NX 2007 Release Notes, NX 2007 Series 3

© 2021 Siemens
Model Based Definition ──────────────────────────────────── 3-11
Routing ───────────────────────────────────────────── 3-12
Routed System Designer ─────────────────────────────────── 3-12
Ship Structure ───────────────────────────────────────── 3-20
Sheet Metal ─────────────────────────────────────────── 3-21
Flexible Printed Circuit Design ──────────────────────────────── 3-22
Structure Designer ─────────────────────────────────────── 3-23
Human Modeling ─────────────────────────────────────── 3-23
Vehicle Design and Validation ──────────────────────────────── 3-23
PCB Exchange ────────────────────────────────────────── 3-24
Manufacturing (CAM) ────────────────────────────────── 3-24
Manufacturing Product Notes ──────────────────────────────── 3-24
Manufacturing caveats ──────────────────────────────────── 3-31
Additive Manufacturing ──────────────────────────────────── 3-38
Additive Manufacturing Process Simulation ──────────────────────── 3-41
CMM Inspection Programming ─────────────────────────────── 3-41
Manufacturing Planning ──────────────────────────────── 3-57
Line Designer ────────────────────────────────────────── 3-57
Fixture Planner ───────────────────────────────────────── 3-61
Assembly Line Planner ──────────────────────────────────── 3-63
Knowledge Fusion and DesignLogic functions ────────────────── 3-65
Product Notes ────────────────────────────────────────── 3-65
Validation ───────────────────────────────────────── 3-67
Model Based Systems Engineering ───────────────────────────── 3-67
Tooling Design ────────────────────────────────────── 3-67
Mold Wizard ─────────────────────────────────────────── 3-67
Progressive Die Wizard ──────────────────────────────────── 3-67
Press Die Checker ─────────────────────────────────────── 3-68
Data translation ────────────────────────────────────── 3-68
Product Notes ────────────────────────────────────────── 3-68
Caveats ───────────────────────────────────────────── 3-71
Mechatronics Concept Designer ─────────────────────────── 3-81
Product Notes ────────────────────────────────────────── 3-81
Automation Designer ────────────────────────────────── 3-82
Product Notes ────────────────────────────────────────── 3-82
Caveats ───────────────────────────────────────────── 3-84
Programming Tools ─────────────────────────────────── 3-86
NX Open ───────────────────────────────────────────── 3-86
Release upgrades ─────────────────────────────────────── 3-87
Product Notes ────────────────────────────────────────── 3-90

4 NX 2007 Release Notes, NX 2007 Series

Dear Customer:

We are excited to introduce the latest release of NX, which builds upon the continuous release process
with significant new and enhanced functionality in all areas of the product, as well as several new
design tools, to help you work more productively and efficiently to build your 3D digital twin.

Design
To help you leverage the latest design techniques and optimize your product designs, we have
invested in all aspects of modeling, including core functionality in Modeling and Drafting, such as
selection, feature modeling, synchronous technology, and assembly modeling.

This release brings some exciting new tools, including NX Topology Optimizer, which brings the
simulation and design worlds closer together, allowing you to develop optimized designs based on
key criteria. In addition, the new Design Space Explorer brings powerful multitarget parameter
optimization by leveraging our Simcenter HEEDS solutions.

Finally, we have extended our capabilities in the area of Sheet Metal design and manufacture with a
new NX 2D nesting solution.
Manufacturing
The latest part manufacturing capabilities in NX, including CNC programming and additive
manufacturing, enable new levels of production efficiency, both during planning and on the shop
floor.

• NX CAM
Through AI-powered NC programming capability, NX CAM can now predict and suggest the next
programming step based on the current machining application and user’s workflow patterns,
helping you accelerate and standardize the programming process.
New and enhanced machining methods deliver unique advantages. A new Z-level Undercut
operation requires minimum input to program hard-to-reach, undercut part regions, achieving
programming five times faster by eliminating manual input. In just a few clicks, you can now
create high-quality, collision-free toolpaths using T-cutter, spherical, or barrel tools. A new Flow
Milling operation replaces the Flow Cut operation for rest machining, enabling precise toolpaths
to remove the uncut material. The legacy Flow Cut operations can be automatically migrated to
the new Flow Milling operations, enabling you to immediately leverage the benefits of this new
advanced operation. The Guiding Curves finishing operation now supports bull nose tools, which
are ideal for finishing steep areas, resulting in better surface finish.
The enhanced Operation Navigator provides more flexibility and ease of use. You can now
configure the operation navigator for multichannel machining. For each channel, you can filter
the view individually, making the programming of multifunction machines much more intuitive.
Smart Machine Kit Solution (SMKS) is a modern approach for NX CAM users to accurately
validate and generate production-ready NC programs. SMKSs, also known as the digital twins of
CNC machine tools, are available on Post Hub. Each SMKS includes the accurate model of the

NX 2007 Release Notes, NX 2007 Series 1-1

machine with kinematics, the postprocessor, and G-code-driven simulation. You can now
purchase an SMKS license for different types of machining operations, such as 2-axis Turning and
3-axis Milling, enabling you to install the available kits from Post Hub. As an additional benefit,
you can also try any SMKS on a single operation without a license. With the new SMKS approach,
NX CAM users gain additional flexibility to easily program a wide range of CNC machine tools.

• Additive Manufacturing
This release of NX continues the trend of applying automation to additive manufacturing. New
capabilities for automating the population of the build tray equate to gains in efficiency when
printing parts at industrial scales. Being able to copy parts and the associated supports within the
build tray, and the ability to nest parts across multiple build trays, both streamline the build setup
process. Furthermore, integrated orientation optimization runs dozens of simulations
simultaneously in the cloud to find the optimal build orientation for reducing distortion, and this
release includes the ability to offload print jobs to the new AM Print Server. Each of these
capabilities increases the efficiency of your additive manufacturing operation and, together, they
represent a consistent evolution towards a more streamlined end-to-end additive manufacturing
process.

We are confident that the new capabilities in this release will allow you to work more productively than
ever before, and to achieve your product requirements while staying at the forefront of industry trends.
For more information about this release, check Discovery Center in NX or see the What's New Guide
included with the NX help.

–Your NX team

1-2 NX 2007 Release Notes, NX 2007 Series

© 2021 Siemens
2. NX System Information
Customer support
Customers covered by valid maintenance agreements are eligible to receive customer support. If you are
a customer of one of our partners or resellers, please contact them first to determine your first line
support provider.

Our Customer Support team has the following mission: To increase our customer’s productive use of our
software by providing responsive and specialized support. You can find your local Customer Support
contact information and additional support information on Support Center.

Platforms

NX central runtime directory

Central runtime directory concept

To help you find executables and libraries, and distinguish them from configuration files more easily, a
central runtime directory that contains DLLs (or so's, or dylib's), executables, and JAR files is now used.
The central runtime directory will be updated as NX supports more and different applications.

Scripts that are used to wrap executables have not been moved and they are still in their original kit
locations with the configuration files.

NXBIN directory

The central runtime directory, NXBIN, is created on all platforms at the UGII_BASE_DIR\nxbin location
during the NX installation. Depending on what was selected to be installed, libraries and executables
from different kits are consolidated into the central runtime directory during the install process.

The new NX runtime directory does not contain all binaries and executables. Only the most frequently
used files from the following directories have been moved:

• UGII

• UGMANAGER

• STEP203UG

• STEP214UG

• PVTRANS

NX 2007 Release Notes, NX 2007 Series 2-1

• MACH

Other files will also be moved over time. However, some applications, such as NX Nastran, will not be
moved.

While NXBIN does not contain all of the executables and DLL's, it does contain a large quantity and is a
prime location to search for an executable or library.

UGII_ROOT_DIR obsoleted

UGII_ROOT_DIR has historically been used to find the following in the UGII directory:

• Libraries and executables

• Configuration files

With the creation of the central runtime directory, there are two different locations for these files (nxbin
and ugii), so the concept of UGII_ROOT_DIR is obsoleted. Use the UGII_BASE_DIR variable instead when
you write custom application code and scripts.

While the NX install no longer sets UGII_ROOT_DIR, the definition on the system will remain to support
earlier releases. If your code or scripts rely on UGII_ROOT_DIR, modify them to ensure they still work in
this release.

Teamcenter code and scripts

To provide backward compatibility with released versions of Teamcenter, all executables called directly
by Teamcenter code or scripts are wrapped.

The wrapper executables just correct the settings of the UGII_BASE_DIR, PATH, and LD_LIBRARY_PATH
variables that are set by the Teamcenter scripts and code, and then start up the real executable from the
NXBIN directory. This enables support for the new runtime concept, while allowing NX to run with
existing versions of Teamcenter.

These new wrapper executables must remain in the ugii and ugmanager directories since that is where
Teamcenter code expects to find them. Two processes are shown for executables invoked from the ugii
and ugmanager directories.

Executables are still in the UGII, UGMANAGER, STEP203UG, STEP214UG, and PVTRANS kits.

Teamcenter code migration to the new central runtime directory structure is scheduled in a future
Teamcenter release.

2-2 NX 2007 Release Notes, NX 2007 Series

System requirements guidelines

Defining the minimum system requirements is difficult because key requirements, most notably
memory, can vary dramatically from user to user. The following are general guidelines that you should
consider before purchasing a system.

Processor performance

Although raw processor speed has a major impact on system performance, other factors also contribute
to overall performance; for example, the type of disk drive (SSD, SCSI, ATA, or Serial ATA), disk speed,
memory speed, graphics adapter, and bus speeds. The general rule is that "the faster the processor, the
better the performance is," but this only applies when comparing like architectures. For example, it is
difficult to arrive at performance expectations for an Intel processor when compared to an AMD
processor just by looking at their respective processor speeds. There is also a general trend today to de-
emphasize processor speeds and move to multi-core processors, which actually can have lower
processor speeds.

NX takes advantage of modern processors, and if a processor does not have the required functionality,
you will see the following error message and NX will not run on the installed CPU:

This processor is too old and not supported anymore

SMP

Symmetric Multiprocessing (SMP) is supported in NX mostly via Parasolid, although a small number of
NX capabilities have some threading. In general, it is not possible to quote a figure for the general
performance improvement achieved by using SMP, since this improvement depends on the nature of the
operations you are performing. You need to evaluate your actual performance gains using your own
models. Functional areas that are SMP enabled in Parasolid include:

• Validity checking

• Boolean operations

• Wireframe

• Rendering

• Hidden line rendering

• Closest approach

• Faceting

• Mass properties

NX 2007 Release Notes, NX 2007 Series 2-3

SMP is enabled by default with the variable UGII_SMP_ENABLE, which is located in the ugii_env_ug.dat
file.

Multi-Core

Multi-core processors are similar to SMP because there are two or more actual processor cores but they
are delivered in single processor packages. Siemens Digital Industries Software has found that multi-
core performance characteristics are similar to SMP. The one advantage of multi-core processors over
SMP is that this technology has proliferated much faster than SMP and is now common in workstations,
servers, and laptops.

Multi-core technology is complex and, depending on the configuration, can actually have a negative
impact on performance. This is due to the potential conflict of multiple cores sharing system resources,
such as cache, memory, and bus bandwidth, as well the need for the system to manage and control an
increasing number of cores. Increasing the number of cores does not always translate into better
performance. Although additional cores can improve NX performance, processor speed is still a vital
measurement of NX performance.

Many systems enable you to turn off cores via the bios, which can enable you to compare performance
with a different number of cores that are active. Some users may find that turning off some cores will
actually improve performance. One micro-architecture (Intel) even does this automatically, shutting
down unused cores and increasing the clock speed of the others.

The hardware vendors continue to improve their processor micro-architectures to better address the
limitations of older multi-core technologies. New subsystems better integrate memory and other
peripherals directly to the processors, resulting in major performance improvements. Buses are being
eliminated, cores are better managed, and channel speeds continue to improve.

In summary:

• Turn SMP on only if you have an SMP system. Having it on in a single-processor system incurs a slight
overhead.

• Turn SMP on if you have a multi-core system.

• Never assume that by simply adding more cores you will see better performance. Always test first.

Memory

The minimum recommended amount of memory to run native NX is 8GB. If you are running NX with
Teamcenter (Teamcenter Integration for NX), the minimum recommended is 12 GB. However, because
NX is capable of handling large assemblies and very complex parts, many of our customers use
workstations with 32GB of RAM, and some even use 64GB, 96GB, or more.

For the optimum user experience and application performance, we recommend that you install as much
RAM as can be installed in the client workstation that is running NX.

2-4 NX 2007 Release Notes, NX 2007 Series

As a guideline, so that you get the best possible performance when using NX, ensure that the amount of
physical memory (RAM) in your workstations is always larger than the amount of memory consumed by
NX, plus all the other applications that are running at the same time on the same machine. This can be
done by using a tool such as Windows Task Manager or Resource Monitor.

The minimum memory requirements varies and depends on various factors including:

• Complexity of the geometry within individual parts

• Size of the assemblies that are loaded

• Less memory is required if the assemblies contain multiple instances of the same components.

• More memory is required when large assemblies contain lots of unique components with complex
geometry.

• Use of Teamcenter in addition to NX

• Some additional memory is required when using Teamcenter 4-tier.

• A even greater amount of memory is required when using Teamcenter 2-tier.

• Fully loading exact assemblies versus using lightweight assemblies and partial loading

• Generating CAM toolpaths for very complex geometry, such as an automotive engine block or
gearbox

• Updating large assembly drawings

Graphics adapters

All the NX certified systems contain graphics adapters that meet all Siemens Digital Industries Software
requirements and are fully supported by our hardware partners. The graphics adapters supported are
carefully selected by working with our OEM partners as well as our graphics vendor partners. We do not
recommend low-end, consumer, or game cards, since these graphics devices are developed for the
DirectX market and are not well supported under OpenGL. Because a majority of platform/hardware
problems are graphics related, it is critical that all the graphics adapters that NX supports are designed
for OpenGL and have the highest level of support from our hardware vendors. We highly recommend
that you only use supported graphics adapters and Siemens Digital Industries Software certified drivers.

For the latest information on certified graphics cards and driver versions, see Supported hardware and
graphics.

NX 2007 Release Notes, NX 2007 Series 2-5

Multiple monitors

Siemens Digital Industries Software supports multi-monitors but with limitations. These limitations were
necessary due to the large number of possible configurations. Other combinations may work, but these
conditions are tested and supported by Siemens Digital Industries Software. These guidelines could be
extended or relaxed in the future.

The following is a summary of findings for the support of multiple monitors.

• NX 6.0.1 or higher - no older releases are supported.

• Two monitors only.

• LCD monitors only

• Run with native resolution and aspect ratio.

• Laptops are tested without docking stations or port replicators (direct connection only).

• Horizontal Scan mode (not Vertical) and only with identical monitors.

• Dual View (Nvidia) or Extended View (ATI) modes, but the user must have the display window entirely
in either the primary or secondary monitor.

You do not have to comply with the configurations mentioned above, but Siemens must be able to
duplicate the problem on the configurations in our labs before being able to investigate your issues.

Operating system requirements

This section documents operating system and service pack requirements.

Minimum Operating Systems

The following operating systems are the minimum recommended for NX. Newer versions and service
packs are available as they are released.

O.S. Version
Microsoft Windows (64-bit) Microsoft Windows 10 Pro and Enterprise editions
Linux (64-bit) SuSE Linux Enterprise Server/Desktop 15
Red Hat Enterprise Linux Server/Desktop 7.6

2-6 NX 2007 Release Notes, NX 2007 Series

Linux

Starting in NX 1847, NX is no longer supported on the Linux operating system for interactive NX (NX
running with UI), which includes graphics integration. It is only supported for running solvers and NX
Open batch programs with no user interface calls.

Batch NX programs run on Linux are dependent on the availability of Motif in the installation.

Contact Customer Support (GTAC) for the new NX Linux product.

If you are using the SCL compiler on Red Hat Enterprise Linux, you need to do some additional setup.
See Programming Tools Product Notes for more information.

Mac OS X

Starting in NX 1847, the Mac OS X operating system is no longer supported.

Windows 10

Windows 10 is the minimum supported release for NX 2007. The supported versions of Windows 10 are
the Pro and Enterprise editions utilizing Semi-Annual Channel (SAC) updates.

Windows 10 is also available for NX 10.0.3 and later versions up to NX 2007. Any caveats or special
instructions are provided in the SFB announcing support.

Windows 7 and 8.1

Windows 7 has reached the end of life and mainstream support has ended. Windows 8.1 is still
supported by Microsoft, but was rarely deployed. These two versions of Windows are no longer
supported by NX 2007. Siemens Digital Industries Software has not performed testing on these versions
and cannot resolve any issues related to NX 2007 running on these operating systems. If NX 2007 is
deployed on these versions of Windows, any issues will have to be replicated on Windows 10 before
filing an incident report with Customer Support (GTAC).

System error when running NX

If you receive the following system error when launching NX, the problem is generally that the
operating system is not up-to-date for the required and optional updates. This error can occur with
Windows 7 and Windows 8.1.

The program can't start because api-ms-win-crt-heap-l1-1-0.dll is

missing from your computer.

The error occurs when there are missing Visual C++ libraries due to a dependency on the Universal CRT
libraries in Visual C++ 2015. To fix the problem, install the Visual C++ 2015 update 3 redistributable

NX 2007 Release Notes, NX 2007 Series 2-7

from Microsoft. The 64-bit redistributable (vc_redist.x64.exe) is available in the INSTALL folder of the NX
runtime environment after installation, or you can download the redistributable from Microsoft.

If you still have a problem, contact Customer Support (GTAC).

Linux Distributions

NX is developed using Linux standards and accepted Linux development conventions. Quality assurance
testing is performed on the two versions of Linux listed in the table above. Siemens PLM Software
cannot guarantee operation, performance, compatibility, or support on any other distributions.

The following is a list of information about the development environment (for reference only):

Kernel kernel 3.10.0-957.eI7.x86_64

Glibc glibc-devel-2.17-260.e17.x86_64
Motif motif-devel-2.3.4-14.e17_5.x86_64
C, C++ Compiler gcc 7.3.1
Java Development version 1.8.0_45

Considerations and caveats

Linux Requirements

NX supports SuSE Linux and Red Hat Linux, both 64-bit only. The minimum supported version of SuSE
Enterprise (Desktop/Server) is 15 and Red Hat Enterprise (Desktop/Server) is 7.6. Newer versions will be
supported via certification.

See Supported hardware and graphics for details about supported hardware configurations as well as
for the latest graphics drivers.

Java Runtime Environment

The Java Runtime Environment (JRE) is not shipped with NX, but NX does require JRE 8 or later version
for certain NX applications and products.

Note:
If you are running a Siemens product other than NX, you may need to run a different version of
Java according to the requirements for that product.

To download and install the JRE, visit the Oracle JRE site at http://java.com/en/download/index.jsp, or
the AdoptOpenJDK JRE site at https://adoptopenjdk.net/releases.html?
variant=openjdk8&jvmVariant=hotspot.

Java is used for the following NX applications and products:

2-8 NX 2007 Release Notes, NX 2007 Series

• NX Relations Browser

• Manufacturing – Process Studio Author

• Command line version of the following translators:

• CATIA V4

• CATIA V5

• Dxfdwg

• IGES

• NX Pro E

• Step AP203

• Step AP214

• Knowledge Fusion ICE

• Quality Dashboard

• Validation Rule Editor

• Simcenter 3D Batch Mesher

• Simcenter 3D Response Analysis Function Tools

• Simcenter 3D Report Writer

• Customer written NX Open Java programs

Java requirements for NX Open

NX Open for Java is designed to be used with Java version 1.8.0_45 or higher.

Transition to new supported Java

Due to industry trends and the adoption of AdoptOpenJDK Java instead of Oracle Java throughout the
user community, AdoptOpenJDK is planned to be the certified and supported Java in a future release of
NX.

NX 2007 Release Notes, NX 2007 Series 2-9

Post Processing of Abaqus ODB format results

In the NX release, NX uses Abaqus version 6.12 libraries to process ODB results files. For NX to use these
libraries, you must first install Visual C++ 2008 X64 Runtime – v9.0.30729.4967.

Note:
If you have Abaqus version 6.12 installed on your system, the required Visual C++ runtime should
already be installed.

You can download this runtime from the Simulia customer support website: http://www.3ds.com/
products-services/simulia/support/

For more information on the system requirements for ODB version 6.12 files, see: http://www.3ds.com/
support/certified-hardware/simulia-system-information/abaqus-612/system-requirements-for-
abaqus-612-products

Running Samcef in parallel

On Windows, when you run parallel computations with the built-in Samcef solver, Python 2.7 is
required. In NX 2007, that version of Python is not present. Install Python 2.7 on your disk and ensure
that the Python directory is named Python27 (default name) and is included on your PATH variable.

You can download the software from the Python website: https://www.python.org/downloads/

Note:
The Python requirement does not apply if you have Samcef installed separately from NX.

Configuration files

Starting in NX 12, the NX configuration files on Windows are written to C:\users\<name>\AppData

\Local\Siemens.

Installing the .NET Framework

The NXOpen for .NET API is a Windows-specific project that leverages the Microsoft .NET Framework
component. Before you can execute a custom .NET application, you must install .NET Framework 4.7.2.
In addition, to replay a .NET journal, the .NET Framework 4.7.2 must be installed.

To download .NET Framework 4.7.2, use the links on this page: Microsoft .NET Framework 4.7
(Web Installer).

2-10 NX 2007 Release Notes, NX 2007 Series

Visual Studio runtime redistributable

To run NX 2007, the MS Visual Studio 2019 runtime redistributable is required. In addition, the MS
Visual Studio 2013 runtime redistributable is required to properly setup some system dll files for some
of the older executables.

You can download the Visual Studio 2019 redistributable here.

You can download the Visual Studio 2013 redistributable here.

Note:
If you have MS Visual Studio 2019 and 2013 installed, you don't need to download and install the
redistributable.

NX 2007 Release Notes, NX 2007 Series 2-11

Supported hardware and graphics

The list of currently supported hardware and graphics cards can be found on Hardware and Software
Certifications. Click Graphics Card Certification Matrix to open a spreadsheet that has tabs for
supported systems and graphics.

2-12 NX 2007 Release Notes, NX 2007 Series

NX Open programs on Linux

If you try to link an external NX Open C++ program using the ufmenu and uflink scripts with NX 2007
on SLES 15, Linux may fail with an error message such as:

/usr/x86_64-suse-linux/bin/ld: cannot find -lelf

For NX to properly build an NX Open program, you must have the correct RPM kits installed.

For NX 2007 and SUSE 15, the following packages are required:

elfutils-0.158-6.1.x86_64.rpm
libelf1-0.158-6.1.x86_64.rpm
libelf-devel-0.158-6.1.x86_64.rpm

For NX 1953 and RedHat 7.6, the following packages are required:

elfutils-libelf-0.172-2.el7.x86_64.rpm
elfutils-libelf-devel-0.172-2.el7.x86_64.rpm
elfutils-devel-0.172-2.el7.x86_64.rpm
elfutils-libelf-0.172-2.el7.x86_64.rpm
elfutils-libs-0.172-2.el7.x86_64.rpm

Note:
For SUSE, the devel packages are available from the optional SLE 15 SDK DVD/ISO.

NX 2007 Release Notes, NX 2007 Series 2-13

Initializing the JVM

In some cases, NX is not able to create the Java Virtual Machine (JVM) properly on Windows. The root
cause in these scenarios is insufficient memory to start the JVM. In most cases of insufficient memory
Java is able to report back an error code indicating this problem. However, in some cases Java reports a
generic error message that NX then displays. The typical error message is:

Can’t initialize the Java Virtual Machine (JVM)

When running a Java application, such as the Wave Browser or Interactive Class Editor, NX may give an
unexpected error due to this problem.

If NX detects that there is not enough memory available for the JVM, an error message is given and
information is provided in the syslog. The following is an example of the syslog information:

The JVM could not be created due to not enough memory.

The Java heap size must be contiguous and the largest contiguous block
available is outputted below.
Windows largest block free
=================================
Maximum block 267Mb
=================================
Please note, this number is to be used as suggestion for setting the
heap size. It
is unlikely that you will be able to utilize the full amount.
If you need a heap size larger than what is possible you can try to use
the /3GB
switch or its equivalent, if available for the Operating System you are
on.
Otherwise your other option is to use Remoting. Please consult the NX
Open
Programmer's Guide for more information on this topic.

Reset the size of the Java heap

To remedy this problem, you can reset the size of the Java heap that NX uses. Choose
File→Execute→Override Java Parameters to open the dialog box and set UGII_JVM_OPTIONS to the
size of the Java heap. You can experiment with the size of heap that you need, but if the JVM is already
started then you cannot change the UGII_JVM_OPTIONS setting.

It is recommended that you use both the –Xmx and –Xms options together. Both of these are needed as
Java may determine default values for the heap size that are not possible with the machine’s current
memory load. For example:

UGII_JVM_OPTIONS=–Xmx50M –Xms50M

2-14 NX 2007 Release Notes, NX 2007 Series

When trying to determine the size of the heap, keep in mind that if the heap size is too small, a Java
program you are trying to run may not run. This could be due to the amount of memory available on the
machine, or due to multiple Java processes running. This can be the case with the Wave Browser where
there is a client and server process.

Once you find a value that works, you can modify the UGII_JVM_OPTIONS value in the ugii_env.dat file
so you don’t have to reset it in the NX Open Java Parameters dialog box each time you start an NX
session.

NX 2007 Release Notes, NX 2007 Series 2-15

NX variables in the ugii_env.dat file

Standard and modified environment variables

The ugii_env_ug.dat file contains the standard environment variables for NX. You can override these
variables with the ugii_env.dat file. This file is essentially empty when delivered. You can define new
values for the environment variables in this file and they take precedence over the values defined in the
ugii_env_ug.dat file.

The ugii_env.dat file should be used to modify any standard NX environment variables or add new ones.

Both the ugii_env_ug.dat and ugii_env.dat files are located at <UGII_BASE_DIR>\ugii.

Note:
You can make all, some, or none of the changes to the variables in the ugii_env_ug.dat file.
However, it is recommended that you use the ugii_env.dat file to define all of the values in use at
your site.

Using the ugii_env.dat file

The following apply when using the ugii_env.dat file:

• Define the variables before the #include statement.

• The first variable defined is used. If you have the variable defined twice in the file, only the first one is
used.

Note:
This also applies to the ugii_env_ug.dat file.

• You cannot have spaces in the variable names.

Designate a single ugii_env.dat file for all users

You can place the ugii_env.dat file in a central location for all users to access.

For each user, set the environment variable UGII_ENV_FILE to the location of the file. For example:

UGII_ENV_FILE=G:\common\version_env_vars.corp_standards

2-16 NX 2007 Release Notes, NX 2007 Series

Note:
The file can have any name but must be a fully qualified path.

Statements you can use in the ugii_env.dat file

The statements that you can use in the ugii_env.dat file are shown below with examples:

• #if/#else/#endif
Used to check for specific conditions and then to define variables based on those conditions.
Conditions that can be checked are:

• FILE - Check for the existence of a file

#if FILE ${UGII_BASE_DIR}\UGII\html_files\start_${UGII_LANG}.html

UGII_CAST_HOME=${UGII_BASE_DIR}\UGII\html_files\start_$
{UGII_LANG}.html
#else
UGII_CAST_HOME=${UGII_BASE_DIR}\UGII\html_files\start_english.html
#endif

• platform - Check for a specific platform. Possible values:

x64wnt

lnx64

macosx

#if lnx64
UGII_CAM_THREAD_MILL=${UGII_CAM_THREAD_MILL_DIR}thrm.so
#endif

• $variable = “value” - Check for a specific value for a previously defined environment variable

#if $UGII_LANG = "simpl_chinese"

UGII_COUNTRY=prc
UGII_COUNTRY_TEMPLATES=$UGII_BASE_DIR\localization\$UGII_COUNTRY
\simpl_chinese
#endif

• $variable != “value” - Check for a previously defined environment variable that does not have the
specified value.

#if ${UGII_PACKAGE_DIRECTORY} != ""

#if FILE $UGII_PACKAGE_DIRECTORY\ugii_package_env.dat

NX 2007 Release Notes, NX 2007 Series 2-17

#include $UGII_PACKAGE_DIRECTORY\ugii_package_env.dat
#endif
#endif

• #include
Used to include a specified environment file at the current location

#include $UGII_PACKAGE_DIRECTORY\ugii_package_env.dat

Browser requirements

The NX suite of documentation (Help, What's new Guide, and Release Notes) is provided in an HTML
format that is displayed in your local Web browser.

There are three ways to access the NX documentation:

• Access directly on the internet from Support Center (requires login).

• Install the Secure Documentation Proxy, which allows access to documentation on Support Center
without logging in or creating a Webkey account. This eliminates the need and overhead of installing
documentation locally while still providing secure access.

• Install the Siemens Digital Industries Software Documentation Server, which sets up a web server on
each workstation or on your company intranet. For requirements, see Siemens Help Server for
Windows.

The latest versions of web browsers are recommended to comply with the latest browser security
updates.

Windows browser support

• Google Chrome

• Microsoft Edge

• Mozilla Firefox

• Internet Explorer

Downloading browsers

These browsers are free and can be downloaded from the following Web sites:

2-18 NX 2007 Release Notes, NX 2007 Series

Chrome — http://www.google.com/chrome

Internet Explorer and Edge — http://www.microsoft.com

Firefox — http://www.mozilla.org

Licensing Caveats

General licensing caveats

License files and license server

The following are applicable to license files and the license server:

• Merging of license files is not supported.

Example:
You can not merge a pre-TC 2007 MP3 or pre-NX 5 license file, which uses the uglmd license
daemon, with a TC 2007 MP3, NX 5, or NX 6 license file, which uses the ugslmd daemon.

NX requires and tests for the latest version of the ugslmd vendor daemon. This vendor daemon is
supplied with NX and must be installed and initiated prior to starting NX. If an older daemon is
utilized, a generic NX License Error dialog box is displayed during start-up. In addition, the syslog will
contain an error message that the daemon version is older than the client.

NX Borrowing is version specific

NX license borrowing is version specific due to dependencies within the third party licensing software
used by Siemens PLM Software. To ensure that NX works on a borrowed license, you should always
utilize the borrow tool supplied with that NX version. For example, a license borrowed using the NX
1980 borrowing tool will work for NX 1980 but cannot be used to run NX 1953. In addition, you cannot
borrow licenses for two NX versions simultaneously on the same workstation.

NX 2007 Release Notes, NX 2007 Series 2-19

Licensing caveats for Windows

The following caveats are applicable to Windows platforms only.

License Option tool

The License Option tool should only be used to borrow NX licenses, even though it may display other
licenses. The License Option tool does not filter features in the license file that are of an earlier version
than NX, such as Teamcenter lifecycle visualization, so these licenses are displayed in the tool. If you try
to borrow a license for an application other than NX, you get an error when you launch the non-NX
application.

LMTOOLS fails to restart service

You may encounter a problem where the license service fails to start after using LMTOOLS to set
locations for the license file or server debug log file, or for both.

Cause: The license service is run as as user=LocalService, and LMTOOLS may have insufficient
modification rights to do the following:

• Read the license file.

• Create and append to the server debug log.

Solution: Do one of the following:

• Use the default locations that the Siemens License Server Installer uses:

• For the license file: C:\ProgramData\Siemens\License Server\<vendor>.lic

• For the server debug log: C:\ProgramData\Siemens\License Server\<vendor>.log

• Specify a directory location that user=LocalService can modify.

To determine whether a directory has LocalService permissions, go to the directory location in
Windows File Explorer, right-click the folder, choose Properties, and click the Security tab. Search
the Group or user names list for LOCAL SERVICE.

2-20 NX 2007 Release Notes, NX 2007 Series

Licensing caveats for Linux

Additional software to support licensing

SuSE and Red Hat require the following to be installed:

• LSB 4.0

NX 2007 Release Notes, NX 2007 Series 2-21

Product compatibility - supported release combinations

Teamcenter and NX

The following table lists the version combinations of Teamcenter, Active Workspace, and NX that are
supported.

Note:
• TC is Teamcenter

• AW is Active Workspace

• The Teamcenter release that is compatible with NX is identified in the table. If no patch is
specified in the table cell, then the base release is the minimum required.
If a patch is required, then the Teamcenter patch level specified in a table cell is the minimum
required for that Teamcenter release. Later patch levels in that release are also applicable,
unless otherwise specified. For example, TC 11.4.0_patch_5 is the minimum patch level in the
Teamcenter 11.4.0 release, and also includes patch_6, patch_7 and so on, that is, TC
11.4.0_patch_5 or later.

• The NX release identifies the minimum update in that series, where applicable. For example,
the NX 1953 series specifies the NX 1961 update as the minimum.

• To connect to any supported Teamcenter release that is configured for use with single sign on
(SSO), the NX 2007 series requires that the Teamcenter security services session agent from
Teamcenter 13.3 is installed.

NX 1847 NX 1872 NX 1899 NX 1926 NX 1953 NX 1980 NX 2007

NX 12.0.2 Series Series Series Series Series Series Series

Teamcent
er UA TC 10.1.7
10.1 AW 3.3.1
AW 3.4

TC TC TC
11.4.0_pa 11.4.0_pa 11.4.0_pa
tch_5 tch_5 tch_15
Teamcent AW 3.4 AW 4.0.4 AW 4.0.4
er UA AW 4.0.4 AW 4.1 AW 4.1
11.4 AW 4.1 AW 4.2 AW 4.2
AW 4.2

2-22 NX 2007 Release Notes, NX 2007 Series

AW 4.0.4 AW 4.0.4 TC TC TC TC
AW 4.1 AW 4.1 11.5.0_pa 11.5.0_pa 11.5.0_pa 11.5.0_pa
AW 4.2 AW 4.2 tch_10 tch_10 tch_10 tch_10
Teamcent AW 4.0.4 AW 4.0.4 AW 4.1 AW 4.1
er UA AW 4.1 AW 4.1 AW 4.2 AW 4.2
11.5 AW 4.2 AW 4.2 AW 4.3.3 AW 4.3.3
AW 4.3.3 AW 4.3.3

NX 12.0.2 NX 1851 TC TC TC TC TC
MP5 update 11.6.0_pa 11.6.0_pa 11.6.0_pa 11.6.0_pa 11.6.0_pa
TC TC tch_4 tch_4 tch_4 tch_4 tch_4
Teamcent 11.6.0_pa 11.6.0_pa AW 4.1 AW 4.1 AW 4.1 AW 4.1 AW 4.1
er UA tch_1 tch_1 AW 4.2 AW 4.2 AW 4.2 AW 4.2 AW 4.2
11.6 AW 4.1 AW 4.1 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3
AW 4.2 AW 4.2

NX 12.0.2 NX 1851 TC TC TC TC TC
MP5 update 12.1.0_pa 12.1.0_pa 12.1.0_pa 12.1.0_pa 12.1.0_pa
TC TC tch_4 tch_4 tch_4 tch_4 tch_4
Teamcent 12.1.0_pa 12.1.0_pa AW 4.1 AW 4.1 AW 4.1 AW 4.1 AW 4.1
er UA tch_1 tch_1 AW 4.2 AW 4.2 AW 4.2 AW 4.2 AW 4.2
12.1 AW 4.1 AW 4.1 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3
AW 4.2 AW 4.2 AW 5.0 AW 5.0 AW 5.0 AW 5.0

Teamcent NX 12.0.2 NX 1851 AW 4.2 AW 4.2 AW 4.2 AW 4.2 AW 4.2 AW 4.2

er UA MP5 update AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3
12.2 AW 4.2 AW 4.2 AW 5.0 AW 5.0 AW 5.0 AW 5.0 AW 5.0
AW 5.1 AW 5.1 AW 5.1 AW 5.1

TC TC TC TC TC TC
12.3.0_pa 12.3.0_pa 12.3.0_pa 12.3.0_pa 12.3.0_pa 12.3.0_pa
tch_1 tch_1 tch_1 tch_1 tch_1 tch_1
Teamcent AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3
er UA AW 5.0 AW 5.0 AW 5.0 AW 5.0 AW 5.0
12.3 AW 5.1 AW 5.1 AW 5.1 AW 5.1
AW 5.2 AW 5.2 AW 5.2

Teamcent
er UA AW 5.0 AW 5.0 AW 5.0 AW 5.0 AW 5.0
12.4 AW 5.1 AW 5.1 AW 5.1 AW 5.1
AW 5.2 AW 5.2 AW 5.2

NX 2007 Release Notes, NX 2007 Series 2-23

Teamcent
er UA AW 5.0
13.0 AW 5.1

Teamcent
er UA AW 5.1 AW 5.1 AW 5.1 AW 5.1
13.1 AW 5.2 AW 5.2 AW 5.2
AW 6.0 AW 6.0

Teamcent
er UA NX 1961 AW 5.2 AW 5.2
13.2 update AW 6.0 AW 6.0
AW 5.2

Teamcent
er UA AW 6.0 AW 6.0
13.3

Teamcent
er UA AW 6.0
14.0

Note:
For information on version compatibility for Teamcenter and Teamcenter lifecycle visualization,
see the Teamcenter documentation.

2-24 NX 2007 Release Notes, NX 2007 Series

NX compatibility with Spreadsheet

NX Platform► Windows
version Spreadsheet software version► MS Excel 365 MS Excel 2019 MS Excel MS Excel
▼ Desktop 2016 2013 and
Platform Operating Operating
▼ system▼ system previous
version▼ releases
For both 32–bit and 64-bit
NX Windows Windows 10 Pro and Certified and Certified and Certified Not
2007 10 64–bit Enterprise supported supported and supported
supported

Note:
• The 64-bit versions of Microsoft Excel are supported starting in NX 12.

• Microsoft Starter Edition is not supported by NX due to lack of support for Add-in's, Macro's,
Math and Equation Editing.

• If you launch a spreadsheet command such as Spreadsheet or Part Family on a system having
Excel 2003 or older version as the default spreadsheet application, NX displays an error
message and does not proceed with the launched command.

NX support for the currently supported versions of Microsoft Office will be discontinued as per the
following dates:

Microsoft Office version End of support

2007 October 11, 2017
2010 October 13, 2020
2013 November 20, 2021
2016 October 14, 2025

NX 2007 Release Notes, NX 2007 Series 2-25

NX applications unsupported on specific platforms

The applications listed are not supported on the specified platforms.

Application Functionality Platform not

supported on:
Tooling & Fixture Design NX EasyFill Analysis - Advanced Linux
NX Translators & Open Tools NX Open Python Author Linux
NX Translators & Open Tools Content Migration Manager for SolidWorks Linux
NX Translators & Open Tools CMM Drawing Repair Assistant Linux
Electro-Mechanical Design ELMA Linux
Electro-Mechanical Design NX Piping Fabrication Drawings & PMI Linux
Electro-Mechanical Design Mechatronics Concept Designer Linux
Mechanical Design NX Lattice Structures Design Linux
Mechanical Design NX Drafting Linux
Mechanical Design NX Additive Design with Convergent Linux
Mechancial Design NX Ship Structure PMI Creation Linux
Mechanical Design NX Ship Dimensions & Adv Annotation Linux
Mechanical Design Drawing Automation for NX (version 10 Linux
and later)
Mechanical Design Layout for NX Linux
Mechanical Design NX Aerospace Design Linux
Mechanical Design NX Lattice Structures Design Linux
Gateway Advanced Studio Rendering Style Mode Linux
Pre/Post Abaqus OBD result file reading Linux
Pre/Post Topology Optimization and Shape Linux Redhat
Optimization
Motion Motion Mechatronics co-simulation Linux

2-26 NX 2007 Release Notes, NX 2007 Series

Support for touch enabled devices

In NX 2007, you can interact and manipulate 3D models and control the overall user interface using
touch screen and stylus. The support for touch enabled hardware follows a slightly different support
model than what is provided through the NX certification program. We have tested NX on a number of
Windows based touch screen laptops, monitors, and tablets. However, support for these devices and
other comparable systems is limited as they are not true workstations and do not qualify for our full
certification program. Support for these devices is limited as follows:

• Graphics performance issues are not supported as most of these devices do not offer the level of
driver support available on workstations.

• Graphics quality and display issues are not supported unless they can be duplicated on a certified
workstation.

• Any issue determined to be caused by the graphics driver is not supported.

• Performance issues with NX are not supported on these systems unless reproducible on certified
workstations.

Caveats aside, we have tested and used for development a variety of touch based systems from HP, Dell,
Microsoft, and others and have found them acceptable for general usage of NX.

Additional Notes

• NX supports touch devices on the Windows operating system.

• Only stylus configurations support pre-highlighting. The most commonly used devices supporting
stylus are the Surface Pros.

NX 2007 Release Notes, NX 2007 Series 2-27

Legacy commands and commands to be retired

Commands that have (Legacy) or (to be retired) in their name are outdated, unsupported commands.
In many cases, newer commands that provide more robust and enhanced functionality, or support
improved workflows, exist.

Legacy commands remain in NX to sustain legacy workflows and products. Commands to be retired will
be removed in a future version of NX, typically within two to four NX versions.

By default, both legacy commands and commands to be retired are removed from the Menu, the Ribbon
bar, shortcut toolbars, and shortcut menus. However, they do appear in the Search box, and you
can add them to your Ribbon bar, Quick Access Toolbar, or Border bars using the Customize command.

Finding legacy commands and commands to be retired

In the Search box in the top right corner of the NX window, type legacy or to be retired to see a list
of the corresponding commands. Press Return to display the commands in the Search window.

2-28 NX 2007 Release Notes, NX 2007 Series

Retired commands in NX

The following table contains a list of retired commands since NX 12, and the recommended
replacement commands.

Retired command Replacement command Release retired

Instance Feature Pattern Feature NX 12
Export PNG Export Image NX 12.0.1
Export JPEG Export Image NX 12.0.1
Export GIF Export Image NX 12.0.1
Export TIFF Export Image NX 12.0.1
Export BMP Export Image NX 12.0.1
Materials/Textures Show Usage NX 12.0.1
Soft Blend (Closed) Face Blend NX 1847
Show/Remove Constraints (in Legacy Constraint Navigator (in NX NX 1847
Sketcher) Sketcher)
Display Dimension as PMI Display as PMI NX 1847
Delete Sketch Object (old) Delete Sketch Object NX 1847
Ray Traced Studio (old) Ray Traced Studio NX 1847
Ray Traced Studio Editor (old) Ray Traced Studio Editor NX 1847
Material Editor Studio Material Editor NX 1847
HQI Ray Traced Studio NX 1847
Artistic Image - NX 1847
Visualization Preferences (non-block Visualization Preferences NX 1847
based)
Visualization Performance Preferences Visualization Preferences NX 1847
Facet Settings Visualization Preferences NX 1847
Fillet Surface (closed) Face Blend NX 1872
Join Curve Composite Curve NX 1872
Stretch Curve - NX 1872
Tolerance Feature Associated Objects PMI commands NX 1872
Tolerance Feature Search PMI commands NX 1872
Tolerance Feature Update Report PMI commands NX 1872
Convert Non-associative Tolerances PMI commands NX 1872
Delete Tolerance Feature PMI commands NX 1872
Geometry Tolerancing PMI commands NX 1872

NX 2007 Release Notes, NX 2007 Series 2-29

Retired command Replacement command Release retired

Geometric Tolerancering Preferences PMI commands NX 1872
List All Tolerance Features PMI commands NX 1872
Master Model Tolerancing PMI commands NX 1872
Validate Tolerance Specification PMI commands NX 1872
Isoparametric Trim/Divide Snip Surface NX 1872
Move Defining Point X-form NX 1872
Move Pole X-form NX 1872
Navigate Fly-through NX 1899
Navigation Options Fly-through Options NX 1899
Edit Text Commands that let you directly edit NX 1899
the text of objects
Basic Lights Scene Preferences NX 1899
Edit Background Scene Preferences NX 1899
Scene Editor Scene Preferences NX 1899
Measure Distance Measure NX 1926
Simple Distance Measure NX 1926
Simple Diameter Measure NX 1926
Simple Radius Measure NX 1926
Measure Angle Measure NX 1926
Simple Angle Measure NX 1926
Measure Length Measure NX 1926
Simple Length Measure NX 1926
Measure Point Measure NX 1926
Minimum Radius Measure NX 1926
Measure Face Measure NX 1926
Measure Body Measure NX 1926
Measure Extreme Measure NX 1980

2-30 NX 2007 Release Notes, NX 2007 Series

Product Notes

Refile utility is now retired

Historically, the NX product release has included the refile utility, which was created many years ago for
very specific data conditions and was never intended to be run by all customers on all of their data. This
utility was never mandatory when performing NX upgrades.

NX product enhancements and improvements that are delivered and available in the current NX release
make NX upgrades much faster and easier, so the refile utility is now obsolete. As a result, the refile
utility is retired starting in NX 12.0.1. The documentation for the utility has already been removed in NX
12.

In place of the refile utility, standalone utilities will be introduced that incorporate non-version-up
related options and future NX batch processes.

NX 2007 Release Notes, NX 2007 Series 3-1

Caveats

Listing order for JT assemblies in Assembly Navigator

The listing order of items you have set in the Assembly Navigator is not maintained for JT assemblies if
you reopen the assembly. To get the set listing order for the JT assemblies, you need to save the top JT
assembly with the master dataset.

Assembly arrangements in Active Workspace

NX does not load the assembly arrangement from Active Workspace. The arrangement that was active
at the last save of the assembly into Teamcenter is loaded into NX.

Fundamentals

Product Notes

NX Virtual Reality display environment

The NX VR environment operates within the following display framework:

• The color of geometry comes from the NX component or object color (Edit Object Display→General
tab, Basic group→Color). Color does not come from the True Shading material, Studio material,
face, or facet color.

• Only solid-body, facet-body, and sheet geometry is displayed in the VR environment.

• The VR environment does not support translucency in the display.

• Geometry tessellation quality follows NX graphics window tessellation quality.

The following NVIDIA VR system is supported for NX Virtual Reality:

• Virtual Reality Systems, Components, Drivers | NVIDIA Quadro – https://www.nvidia.com/en-us/

design-visualization/solutions/vr-ready-systems/

Unit Manager settings

When you run the ug_convert_part tool to convert an NX 12 part from mm to inch, the settings in the
Unit Manager dialog box do not display the converted units. This is as intended.

The Units Manager dialog box displays the units that you have selected as the default units for data
entry and object information output. Those units are independent of the underlying part units (metric or
inch).

3-2 NX 2007 Release Notes, NX 2007 Series

Cursor speed and shake gesture

Pressing MB1 and shaking the mouse from side to side is a new gesture called UGUI_MOUSE_SHAKE.
This new gesture is reported to GIT clients whenever a user shakes the mouse.

An API is implemented to provide the value of the pointer speed at a given mouse movement gesture.
This data is only valid if the current gesture is UGUI_PRE_POSITION or UGUI_DRAG_POSITION.

Navigate tool is retired

The Navigate tool is retired. You can explore your design in 3D space using Fly-through.

NX 2007 Release Notes, NX 2007 Series 3-3

Caveats

Decal Sticker dialog box

When you use the Decal Sticker dialog box:

• Dragging the decal origin on the on-scene dynamic handles will move it to an arbitrary position.

• Dragging and dropping sample decals from system studio library, may not always appear in correct
location.

For a decal with Reflectivity set to From Visual Material, when you edit this decal, in the Decal Sticker
dialog box, Reflectivity shows Matte.

Extended reality files

For export to extended reality files, NX does not support:

• Studio Materials that are applied to the assembly level.

• Scene Lights, Advanced Lights, and Image-based lighting from high end rendering modes.

• Animation Designer animated solutions.

• PMI Objects.

Speech Recognition

You can use all languages to execute voice commands in NX except Traditional Chinese.

Note:
When you execute commands using speech recognition, you can move forward through a dialog
box by saying next. This is supported only for the group-based dialog boxes, such as Extrude and
Blend.
This navigation in the dialog boxes is not supported for other commands, such as, Open and
Curve.

NX Virtual Reality

• Windows update version 1809 creates multiple issues with NX VR and Windows Mixed Reality,
including drops in frame rate. We recommend that you update Windows to version 1803 or 1903 and
later.

• NX Virtual Reality does not support HP Reverb G2 Windows Mixed Reality headset.

3-4 NX 2007 Release Notes, NX 2007 Series

• Oculus Rift S virtual controllers appear upside down due to a design change in the Rift S as compared
to the original Rift.

Bookmarks

If you create a bookmark file with Ray Traced Studio mode enabled, when the bookmark is applied Ray
Traced Studio mode is not in effect.

If you create a bookmark file when displaying a View Section with clipping disabled, when the bookmark
is applied the section may be incorrectly clipped.

If you try to apply a bookmark file when

1. the bookmark file is not for the current displayed part and

2. the number of views in the layout at the time when the bookmark file was created is not the same
as the number of views in the current displayed part

then the number of views in the layout may be wrong after the bookmark file is applied. Applying the
same bookmark file a second time corrects the number of views.

3MF files with lattice bodies

3MF currently doesn't support ball specifications. If you import or export a 3MF file that has lattices with
balls or specified ball diameters, the balls are lost during the import or export operation.

Customer Defaults

Customer defaults

Customer defaults allow you to customize the operation of NX. The initial settings and parameters of
many functions and dialog boxes are controlled by customer defaults. You can view them in NX by
choosing File→Utilities→Customer Defaults.

For a description of the new or modified customer defaults, see the Customer Defaults What's
Changed Report. You must have a valid Siemens Digital Industries Software sign in account to access
this report.

For additional information on customer defaults, see Customizing the NX installation→Customer

Defaults in the NX online help. For a listing and description of all customer defaults, see the Customer
Defaults help.

NX 2007 Release Notes, NX 2007 Series 3-5

Design (CAD)

Assemblies

Product notes

Multi-user design notifications

In Teamcenter Integration for NX, you can follow parts using multi-user design notifications. This
means, you receive notifications when another user saves the parts that you follow or checks them in or
out.

You must install the eventing service when you configure Teamcenter Integration for NX. In Teamcenter
13.3 or later versions, the eventing service is supported on both Windows and Linux. In Teamcenter
13.1 and 13.2, the eventing service is supported only on a Linux host.

NX Analysis

Product Notes

Mass Management customer defaults

Three new customer defaults affect assembly mass properties roll-up calculations:

• Reference Only Components Participate in Roll-up—Determines whether or not reference only

components will be included in assembly mass property roll-up calculations.

• Non-Geometric Components Participate in Roll-up—Determines whether or not the mass and

inertial properties of non-geometric components will be included in assembly mass properties roll-up
calculations. When the Non-Geometric Components Participate in Roll-up customer default is
cleared, non-geometric components will display no mass in the Assembly Navigator, and their
properties will not be considered or included in assembly mass properties roll-up calculations.

• Quantity Attribute Participates in Roll-up—Determines whether or not the Quantity component

attribute will affect assembly mass properties roll-up calculations. When the Quantity Attribute
Participates in Roll-up customer default is selected, component mass in the Assembly Navigator
will be multiplied by the Quantity attribute, and the total mass will be displayed and used in assembly
mass properties roll-up calculations. All additional components added using this method will be
considered to be at the same location and orientation as their original components.

Coating

Caveats

A coating may not work if you apply it on an assembly.

3-6 NX 2007 Release Notes, NX 2007 Series

Coating parameters

• Coatings that are applied on linked faces are not included in calculations of mass properties.

Coating region

You cannot create a coating region by selecting faces from different solid bodies.

Integrated Material Management (IMM) database

When you assign a physical material for the coating from the IMM database, NX does not save that
material as a non-geometric component (NGC). As a result, no NGC is saved in Teamcenter or added to
any bill of materials.

Digital Mockup (DMU)

Caveats

Capturing an assembly snapshot in NX with visible and non-visible components

When you capture a snapshot of an assembly where only a component is visible and the subassembly is
not visible, the subassembly and its parent become visible in the snapshot, as shown below in the
Assembly Navigator.

When you capture a snapshot of an assembly where the subassembly is visible, but none of the
components are visible, everything inside the subassembly becomes visible in the snapshot, as shown
below in the Assembly Navigator.

Note:
In both of these cases, no error message is displayed.

NX 2007 Release Notes, NX 2007 Series 3-7

Capturing an assembly snapshot in Teamcenter Visualization with assembly-level

geometry

In Teamcenter Visualization, when you capture a snapshot of assembly-level geometry, as shown below
in Teamcenter Visualization (identified as -geom in the node description), you cannot view the snapshot
in NX

Note:
An error message is displayed in NX

In Teamcenter Visualization, when you capture a snapshot of only a component in an assembly with the
assembly-level geometry hidden, as shown below in Teamcenter Visualization (identified as -geom in
the node description), the entire assembly is visible in the snapshot in NX.

Note:
No error message is displayed in NX.

Multi-document design session is not supported in NX

You can only open a design session that contains a single document in NX. You can create a session that
contains more than one document in Teamcenter Visualization, but you cannot open it in NX.

Design sessions with more than one inserted model are not supported in NX

In Teamcenter Visualization, you can create a design session that has more than one inserted model.
These sessions cannot be opened in NX.

Limited support for markup properties in design sessions

There is limited support in NX for the markup properties in design sessions:

• Circle, Ellipse, Rectangle, Freehand, and Text 3D markup elements are supported.

• Border of text and Leader line style markup elements are partially supported.

3-8 NX 2007 Release Notes, NX 2007 Series

• Solid fill is supported. Other fill styles, such as Cross, Vertical, Horizontal, and so on, are not
supported. Transparency settings for text markup is not supported.

• Symbols in Text is not supported.

• Attached text markup is not supported.

• Center (shown below) and right text alignment, and underline and strike through text effects, are not
supported.

• Render style and section of work views that are captured in NX are not added when saving them to a
session file. Teamcenter Visualization does not support them.

• The Teamcenter Visualization CenterDashDash and Invisible line styles are not supported in NX.

Note:
No error message is displayed in NX for unsupported markup properties.

NX 2007 Release Notes, NX 2007 Series 3-9

JT data in design sessions

The JT data for the parts in a design session must be up-to-date.

The state of the session loaded in NX may not match the saved state in Teamcenter
Visualization

The properties that are displayed when the session is saved in Teamcenter Visualization are
automatically loaded when the session is opened in Teamcenter Visualization. But these properties are
not initially displayed when the session is loaded in NX.

For example, you create a markup of a model in Teamcenter Visualization, create a snapshot, and save
the session with the markup. If you open the session in Teamcenter Visualization, the markup is there.
When you open the session in NX, the session will not initially show the markup that was visible in
Teamcenter Visualization during the save. When you apply the snapshot in NX, the markup becomes
visible in the session.

Animation Designer

Product Notes

Work in Progress dialog box

The following commands display a Work in Progress dialog box after you click Apply or OK, to allow
you to cancel an operation that is taking too long to complete:

• Rigid Group

• Contact

• Envelope

• Monitor

• Inverse Kinematics

• Joint Jogger

• Animation commands

• Move Rigid Group

• Record Movie

3-10 NX 2007 Release Notes, NX 2007 Series

Layout

Product Notes

Create from 3D

When you use the Create from 3D command, you can now select lightweight components without
first setting the Load Smart Lightweight Data customer default. Assembly performance improvements
made that default obsolete in NX 12.0. Now smart lightweight data is loaded whenever NX needs it to
complete an action.

Limitation to using convergent bodies that have mixed geometry

The Create from 3D command is not supported for the convergent bodies that have mixed
geometry.

Product and Manufacturing Information (PMI)

Product Notes

Component annotation enhancements

The following commands are enhanced:

• The Note and Table commands can now select components as associated objects.

• The Label command can now select points and components as associated objects.

Model Based Definition

Product notes

New out of the box rules

MBD has added the following out-of-the-box rules:

• Add Appended Text and Remove Appended Text

• Convert to Basic

• Create Fillet

• Modify Tolerance

NX 2007 Release Notes, NX 2007 Series 3-11

• Attribute Components

• Create on Touching Components

• Name Components

• Create Hole Table

• Create Part Table

Node enhancement

The Locating Dimension node is enhanced with a Annotation Plane input port to support
measurement direction.

Routing

Caveats

• You cannot place a port on a convergent face.

• You cannot place overstock on the convergent face of a fitting.

Routed System Designer

Product Notes

Placing hangers in cableway networks

To meet Capital Cable Router's requirement that all cableway hangers be placed on a path RCP, set the
Subdivide Segment for Fixture Port Placement preference or customer default. Then when you place
the hanger on the path, the path is automatically subdivided at the part's fixture port.

Routing template parts

• You can use an NX template to create a new Routed System Designer part. When you use the
template, NX initiates the part in the selected application.

• NX template parts and their associated PAX files are located at %UGII_BASE_DIR%\routing\templates\.
ugs_route_templates.pax
For configuring Routed System Designer templates for inch and millimeter units in Native NX.
nxdm_ugs_route_templates.pax

3-12 NX 2007 Release Notes, NX 2007 Series

This PAX file was introduced in 2007 specifically for configuring Routed System Designer
templates for inch and millimeter units in Teamcenter Integration for NX.

Direction-sensitive port extension behavior

The following scenarios show the previous behavior of port extensions and their resolutions.

• Scenario 1
The path originates at a clamp’s fixture port (1) and terminates at fixture port (2). Both fixture ports
are qualified with front and back extensions.
Previously, the result shows the forward extension segment (3) of the originating port and the back
extension segment (4), along with a front extension segment (5) of the terminating port. In this case,
front extension (5) is unneeded and undesirable.

For NX 1961 and later, the path starting (1) and terminating (2) at the same fixture ports omits the
front extension at fixture port (2).

NX 2007 Release Notes, NX 2007 Series 3-13

• Scenario 2
The path originates at a clamp’s fixture port (1) and terminates at fixture port (2).
Previously, the result shows the forward extension of fixture port (1) is still selected, and the path
segments fold back on themselves.

3-14 NX 2007 Release Notes, NX 2007 Series

This behavior is also apparent if you select a path point that is parallel to the fixture port (1) but in the
opposite direction of its forward extension. The path still uses the fixture port’s forward extension and
consequently, folds back on itself.

For NX 1961 and later, fixture ports are more direction-sensitive, and apply the forward or back
extension only as needed to create the shortest, most direct route from the path origin to the next
path point.

NX 2007 Release Notes, NX 2007 Series 3-15

Treating path segments as extension segments when placing fixture ports

When a fixture port is placed on one or more path segments, each path segment is considered an
extension segment if it meets all three criteria:

1. The path segment is physically connected to the fixture port.

2. The path segment is parallel to the fixture port.

3. The fixture port is qualified with forward and back extension values.

An extension segment is defined as a general extension and is not subdivided at the fixture port.

• Scenario 1
A part with a fixture port is placed on a path segment.

3-16 NX 2007 Release Notes, NX 2007 Series

The path segment is treated like an extension segment.

In this case, the segment is defined as a general extension and is not subdivided at the fixture port.

• Scenario 2
A part with a fixture port is placed at the RCP of two collinear path segments.

NX 2007 Release Notes, NX 2007 Series 3-17

Each path segment is treated like an extension segment, corresponding with the forward and back
extension of the fixture port.

• Scenario 3
One of the path segments is not parallel with the fixture port, so it is not treated as an extension
segment.

Maintaining adjoining extension lengths when moving fixture parts

In this scenario, if you select the fixture part to move using the Move Routing Objects command, NX
also selects its adjoining two extension segments, so that a total of three routing objects are selected for
moving in the dialog box.

NX also selects the Maintain Length option so that the extension lengths do not change when the
fixture part is moved, and the two extension segments will remain collinear with the fixture port.

3-18 NX 2007 Release Notes, NX 2007 Series

Caveats

General caveats

• You cannot place a port on a convergent face.

• You cannot place overstock on the convergent face of a fitting.

• Do not apply assembly constraints to routing paths or insulation.

• Do not mix inch stock or insulation with metric parts, and vice versa.

• You cannot place a part with the Place Part command by referencing objects outside of the work
part.

• Port displays may not be consistent when the Routed System Designer part is not the displayed part.

• Avoid relocating a part from one run to another.

• Do not create more than one run from a single piece of equipment.

• Runs do not show their discipline and specification in the Run Navigator columns outside of the
application in the no-part state. The discipline or specification must be loaded in Routed System
Designer.

• Connection compatibility is not yet supported in Routing specifications.

• Avoid using the Bulk Replacement command to replace parts where multiple port engagement
values are involved.

• In pre-production releases of 2007 with Teamcenter Integration for NX, the Routing Mechanical
System application is accessible from both the Routing Mechanical and Mechanical Routed System
Designer templates. However, you should avoid using the Routing Mechanical template to enter
into the Routing Mechanical System application.

Previews of extension segments

The following example involves a preview of an extension segment. In this case, both the fitting port on
the flange and the fixture port have forward extensions defined. If you route a path from the clamp (1)
to the valve (2):

NX 2007 Release Notes, NX 2007 Series 3-19

The extension segment at the valve flange does not appear in the preview. However, when you
complete the process, the extension properly displays in the path.

Ship Structure

Caveats

Sketch

The new Sketch solver is the default in NX 2007, but it is not recommended for ship design workflows.
We recommend you disable the Sketch_NewSolverAndUI early access feature.

3-20 NX 2007 Release Notes, NX 2007 Series

Sheet Metal

Caveats

Patterning of a gusset on non-cylindrical bends

When a gusset is on a non-cylindrical bend, you cannot create a pattern of the gusset.

Note:
This is applicable only for gussets created using Automatic Profile.

To create a pattern of a gusset that exists on a non-cylindrical bend:

1. Extract the curve of the mold edge of the non-cylindrical bend.

For example, use Offset Curve in Face to extract the curve.

2. Use the extracted curve for defining the plane location and create a gusset.

3. Pattern the gusset using the extracted curve as a path.

Tip:
To do this, use Along in the Layout list.

Bridge Bend

You cannot create a bridge bend if the two sheet metal bodies intersect in the following way:

• A body from which you select an end edge intersects with the non-planar web face of the parent body
of start edge.

1 Start edge
2 End edge

NX 2007 Release Notes, NX 2007 Series 3-21

Convert to sheet metal

If you create a fold transition between the planar web faces of chained bends and convert the body to a
sheet metal part, the conversion may be partially successful.

Creating multiple flanges

While creating multiple flanges, if adjacent flange edges are not in the same set, you cannot apply an
internal miter.

Unite in Sheet Metal

If you unite bodies that consist of Sheet Metal and advanced Sheet Metal features, the united body may
not support subsequent Sheet Metal operations.

Nesting

You cannot nest parts in NX 2007.

Material and Bend tables

The tool selection options are not available for the following commands and options.

• Hem Flange

• Lofted Flange

• Convert to Sheet Metal

• Bridge Bend→Type group→Z or U Transition

Bridge Bend→Type group→Fold Transition→Bend Properties group→Define By list→Length
option

• Advanced Flange→Type group→To Reference

Flexible Printed Circuit Design

Caveats

Unite in Flexible Printed Circuit Design

If you unite multi-thickness bodies, the united body may not conform to the selected layer scheme.

3-22 NX 2007 Release Notes, NX 2007 Series

Structure Designer

Caveats

Corners between curve members

Corner results between curve members is not guaranteed.

This will be enhanced in a future release.

Human Modeling

Product Notes

Posture prediction enhancement

Human Modeling now supports the following two posture prediction features:

• Non-forward facing vehicle occupants

• Automatic hand and feet posturing for vehicle passengers

Documentation Notes

Hands-on learning aids in the online help

The online help now includes a limited number of hands-on procedures with part files to download,
which let you work through detailed instructions on your own. These hands-on procedures are a good
learning tool to try out new functionality and complex workflows. The procedure topics are titled
Hands-on: <Procedure name>.

Vehicle Design and Validation

Caveats

• Any Eyellipse feature created in versions prior to NX 2007 will not work in the Direct Vision
command. You must create a new Eyellipse feature in NX 2007.

NX 2007 Release Notes, NX 2007 Series 3-23

• The monocular Direct Vision feature cannot be created for the user-defined eyellipse. You can create
user-defined direct vision for those points.

PCB Exchange

Caveats

Flat Solid workflow

The import and export of ECAD models in their bend state only works when the board is a solid body. If
the board is an assembly component this workflow does not work.

PCB Exchange automation

It is recommended to use NX Open instead of the standalone executable for PCB Exchange automation.

Manufacturing (CAM)

Manufacturing Product Notes

The Manufacturing product notes describe product changes that are not included in the What’s New in
NX documentation.

Tool path and template changes

Tool path changes

A general reminder: There are ongoing changes in the processors to fix problems, add enhancements,
and improve reliability. In many cases, you may see some differences between the new path and the old
path when you generate an operation from a previous release. If you rely on automatic methods, these
changes should be acceptable. The end result of the new path should be comparable to, or better than,
the previous path.

To prevent accidental changes to tool paths in part files from a previous release, use the Lock Tool Paths
During Version Upgrade customer default. This option automatically locks all operations with an edit
status of Complete or Repost.

Ongoing dialog box changes

As a result of customer feedback for the explorer tree format dialog boxes, there are ongoing changes to
parameter locations. To find a specific parameter, enter the parameter name in the box. As you
type, NX displays a list of matching entries that you can select from.

3-24 NX 2007 Release Notes, NX 2007 Series

CAM configuration changes

• No changes

Operation templates

The new generic_motion.prt template part contains the Generic Motion , Generic Feature

Operation , Generic Motion Device , and Mill User Defined operations.

Additional changes to operation templates:

• All operation templates, except generic_motion, now include Documentation to add work
instructions.

• Hole Milling and Thread Milling are removed from the mill_planar template.

• Multi Axis Deburring now includes three separate operation subtypes.

mill_contour mill_multi_axis mill_rotary

3 Axis Deburring Multi Axis Deburring 4 Axis Deburring

Geometry templates

Each Create Geometry template includes an MCS and a Workpiece , and then the other

geometry subtypes used by the operations in the templates. The MILL_GEOM geometry subtype is
removed.

Method templates

Duplicate method subtypes are removed from the Create Method templates. For example, the
hole_machining template had multiple drilling methods with different names that used the same
parameter values.

Tool templates

Each Create Tool template now includes all tools for the technology you are working in, such as Drilling,
Milling, or Turning, regardless of the operations in the template.

NX 2007 Release Notes, NX 2007 Series 3-25

Customized templates

If you create your own template files, you must back up the files before you upgrade to the current
release. Copy the template files from the templates folder (%UGII_CAM_BASE_DIR%\mach
\templates\) to a separate location to prevent the installation from overriding your defined
templates.

After the upgrade installation is done, copy your template files to the %UGII_CAM_BASE_DIR%\mach
\templates location.

Merging customized templates

You can merge your customized templates with the templates included in this release in the following
ways:

• Start with the new default templates and apply your customizations. This is highly recommended to
ensure you receive all the PR fixes.

• Re-file your customized templates in the new release, review the changes listed for the release, and
implement the applicable ones in your templates. This method is not recommended, because you will
not receive the PR fixes.

General changes

Manufacturing license information

Machine Tool changes

The standard machine tools supplied with NX have revised postprocessors and kinematics models.
Review all existing Manufacturing setups which use a standard machine tool from a release prior to NX
8. If necessary, retrieve the machine tool again.

New Operation Navigator

There is a new Operation Navigator that includes the following:

• New configuration and filtering capabilities.

Right-click a column heading and choose Column Configuration, Find, or Filter.

• Keyboard accelerator support.

• Multiple program order views with individual filtering.

The new Operation Navigator is on by default. To use the old navigator, you must select the Use
Classic Navigator check box in customer defaults.

3-26 NX 2007 Release Notes, NX 2007 Series

Tip:
To find a customer default, choose File tab→Utilities→Customer Defaults, and click Find
Default .

Turning

Facing heads

The Enables facing heads early access feature replaces the UGII_CAM_ENABLE_FACINGHEADS
environment variable.

You must set the Enables facing heads feature to On in the Early Access Features dialog box
(File→Utilities→Early Access Feature).

Tools

More button tools are now available in the library.

Integrated Simulation and Verification (ISV)

ISV using CSE simulated controllers with Python parser

• The CSE Python parser is supported for Windows only.

This means that the standard examples supplied with NX will not run on non-Windows operating
systems. As a workaround: Inside the MachineConfigurator, in the Global Settings dialog box, change
the Implementation setting for the MCF from Python to Library.

Note:
The Machine Configurator is supported for Windows only.

• For existing simulations using Python parser with encrypted files from older versions, for example NX
9 or NX 10, we recommend that you use the un-encrypted *.py files from the latest release.

Feature-based Machining (FBM)

Create Feature Process

If your organization has an emergency requirement for the previous version of the Create Feature
Process command, do the following:

• Set the Enables the Classic Create Feature Process feature to On in the Early Access Features
dialog box (File→Utilities→Early Access Feature).

NX 2007 Release Notes, NX 2007 Series 3-27

• Notify Customer Support of your requirement, so that it is forwarded to development.

The Enables the Classic Create Feature Process early access feature toggle will be removed in NX
2206.

Manufacturing critical maintenance and retirement notices

Planned retirement of legacy Create Feature Process

The Enables the Classic Create Feature Process early access feature toggle will be removed in NX
2206.

Planned retirement of Post Builder application

In a future release, the Post Builder application will be under critical maintenance. There will be no
updates and no issues will be corrected. At that time, you can still run postprocessors built in Post
Builder, but we strongly recommend that you switch to the Post Configurator platform.

Verify

Currently, the Verify command is hidden by default.

You can use the Show Verify (Legacy) option in Customer Defaults to control the visibility as needed.

There are newer display and animation commands on the Ribbon bar to validate tool paths.

Planned retirement of Tool Path Based Simulation support for setups without a machine

Beginning in NX 2206, the Tool Path Based Simulation command will not animate the tool path if the
CAM setup does not contain a machine.

Use the display and animation commands on the Ribbon bar when the CAM setup does not contain a
machine.

Template part files

The following template part files were deleted in NX 1980:

• Die Mold (Essentials)

3-28 NX 2007 Release Notes, NX 2007 Series

• Turning (Essentials)

• Machinery (Essentials)

• Multi-Axis (Essentials)

• Mill Turn (Essentials)

Retirement of 2D Dynamic module

In the Tool Path Visualization (Legacy) dialog box, the 2D Dynamic tab is removed.

Retirement of NX Manufacturing Tutorials from all platforms

The Manufacturing Tutorials were retired in NX 1980.

The new Manufacturing Day One replaces the existing tutorials. To view the Manufacturing Day One
content:

1. Launch NX.

Note:
The Manufacturing Day One tab is available on the Discovery Center when you launch the
complete NX suite or the NX Manufacturing application.

2. Click the Manufacturing Day One tab on the Discovery Center.

Retirement of Solid Edge CAM Pro Manufacturing Tutorials from all platforms

The Manufacturing Tutorials were retired in Solid Edge.

The Manufacturing Day One content replaces the tutorials.

Manufacturing Wizard Builder

The Manufacturing Wizard Builder is on critical maintenance. It is a plug-in for the Process Studio Author
(PSTUDIO) application, which is no longer being developed. The 32 bit version is included in the NX
installation, and there is no plan to discontinue this.

The location in the Windows start menu has changed. Choose Start→All Programs→Siemens NX→NX
Manufacturing - Process Studio Author.

There are no plans to discontinue CAM Wizards, which are xml files based on our block based UI
architecture.

NX 2007 Release Notes, NX 2007 Series 3-29

Point To Point planned retirement from all platforms

Point To Point is in critical maintenance. The Drill template has been hidden by default, but is still
available.

3-30 NX 2007 Release Notes, NX 2007 Series

Manufacturing documentation notes

Hands-on learning aids in the online help

Note:
Make sure you are not in the Welcome role when you work through a hands-on procedure.

Manufacturing caveats

General caveats

Machining Feature Navigator

The Machining Feature Navigator is sometimes empty for parts loaded in the Manufacturing
Compare Tool Navigator. As a workaround, right-click a column header in the Machining Feature
Navigator, and choose Apply Filter. This problem will be fixed in a future release.

Reflect Component

NX CAM does not support the Reflect Component assembly command. If you use any geometry from a
reflected component for your operation, the results may be unpredictable.

NX CAM plans to support the Reflect Component command in a future release.

NX process

When you exit NX, it may close the UI without stopping the process. There is no data on how
widespread this problem is.

Tilt Tool Axis

Problem Workaround

Shortest 2D distance to curve Use the 3D shortest

distance option.
For longer tool paths, the shortest distance calculation can become
unsynchronized.

NX 2007 Release Notes, NX 2007 Series 3-31

Problem Workaround

The tilted tool path may have non cutting moves with lifts in regions None
where they are not needed, and the moves can cause gouges.

IPW

• A Generic Motion (GMC) operation does not change the machine mode state of the IPW. Adding a
Machine Control subop with a Set Modes event at the beginning of the GMC operation does not
change the machine mode state of the IPW. The previous machine mode, either milling or turning,
remains active.
If the preceding operation does not have the required machine mode, you must add an operation
with the required machine mode before the Generic Motion operation. For example, if the Generic
Motion operation is for turning, add a turning operation. The new operation must generate tool path,
but does not need to cut material.

Note:
This is not a limitation in ISV when you use the CSE driver. The machine state is defined by the
workpiece spindle setting, which is either turning or milling.

Milling caveats

Fixed Axis Guiding Curves operation - bull nose tools

A Fixed Axis Guiding Curves operation could have spikes in the tool path when all of the following
conditions apply:

• The tool is a bull nose.

• The drive curve is not defined on the boundary of a cut area.

• The cut area includes transitions between steep and non-steep areas.

The spikes are caused by inconsistent contact points as the bull nose tool transitions between the
bottom tooltip and the lower corner of the tool.

As a workaround, do one of the following:

1. Reselect the drive curve to define it from the cut area boundary.

2. Define the tool axis so that the bull nose tool can touch the cut area consistently.

3. Choose another bull nose tool that has a different lower radius.

3-32 NX 2007 Release Notes, NX 2007 Series

Rotary Floor milling

Problem Workaround

The Min. Lead Angle does not influence the tool path. None

Multi Axis Roughing

Problem Workaround

The Custom Feed and Speed parameter To control the engage feed rate during the helical
values specified for the Helical and Plunge or plunge move, do the following:
engage types are not output in the G code.
The engage motions use the specified Cut 1. Select the Feeds & Speeds node.
feed rate.
2. In the Feed Rates group, under More, define
an Engage feed rate.

Multi-Axis Additive Manufacturing

Freeform Additive Buildup Gradient

The Freeform Additive Buildup Gradient operation is only applicable to the laser additive
deposition of metal powder.

Turning caveats

Multi-channel Turning

The Rough Turn Multi-Channel operation has the following limitations:

• When you use the following settings, the retract movement of the primary operation can cause
reduced spindle speed of the secondary operation.

Main node→Multi-Channel Turning group

Mode = Merged

Feeds and Speeds node→Spindle Speed group

Output Mode = SMM

• In the Tool Settings, Axis & CutCom node→Tool Orientation group:

NX 2007 Release Notes, NX 2007 Series 3-33

• You must set the Tracking Point option to Automatic. Do not use the default setting of Rotate
With Holder.

• When you set the Reorient Tool Holder option to Fixed, the fixed value is passed to the secondary
operation. This can lead to an unwanted tool path for the secondary operation.

Hole machining caveats

Tapping operations

Drilling and Tapping are distinct operation subtypes. Although tapping cycles are available in
the Drilling operation dialog box, we recommend that you do not use a Drilling operation combined
with a tapping cycle. The tapping cycles will be removed from the Drilling operation in a future release.

In a Tapping operation, you can set feature geometry parameters, such as pitch, that output the
required mom variables for tapping. If you use one of the tapping cycles in a Drilling operation:

• The operation will not contain the necessary feature geometry parameters and in-process feature
volumes for tapping.

• You will have the legacy Point to Point output where the pitch is driven by feed rate.

Back Counter Sinking operation

The Gouge Checking option reports false gouges.

ISV caveats

Multi tool collision warnings

Multiple function tools (multi tools) can be used in both spinning mode for operations such as milling or
drilling, and non-spinning mode for operations such as turning.

If the cutting portions of individual cutters on a multi tool overlap, the inactive cutter can cause
misleading collision messages.

Non-spinning display:

3-34 NX 2007 Release Notes, NX 2007 Series

Spinning display:

Simulation

• In certain cases the reported minimum distance of a clearance violation is not the closest distance.

• Selecting a location on the tool path is now supported in ISV for both CSE-based simulation and tool
path simulation. Selecting tool path segments involving cycles, such as drilling cycles, may not work
in some cases.
There are also some cases in which the selected positions of rapid motions are not displayed correctly.

• When the simulation runs in the history buffer, and the spindle speed Output Mode for an operation
is set to SFM or SMM to maintain constant surface speed, the simulation behavior can be unreliable.

• When you use the Machine Code Based Simulation option for synchronized operations, Show Tool
Path is supported, but Path Segment Selection is not supported.

NX 2007 Release Notes, NX 2007 Series 3-35

• When you use the External Program Simulation option, and you replace a machine, the
software removes the selected external main program from the Program Manager dialog box. You
then lose all changes in the edited main NC code program.
As a workaround, save your main program before replacing the machine.

Virtual NC Kernel (VNCK)

• When it reaches a breakpoint, the simulation may fail to stop or may not stop at the exact position
specified.

• VNCK version 4.5.5 is officially supported by Windows 10.

• Although the VNCK versions 4.4 and 4.7.4 are not officially released for Windows 10, they usually run
without any problems when you use HMI Operate. If the VNCK does not boot after installing, please
ensure that Windows Data Execution Prevention is not active for vncksl.exe and vplc3172dp.exe.

1. Press the Windows key.

2. In the search box, type advanced system, and press Enter.

3. In the System Properties dialog box, click the Advanced tab.

4. Under Performance, click Settings.

5. Click the Data Execution Prevention tab.

If the Turn on DEP for all programs and services except those I select option is selected, you must
exclude the vncksl.exe and vplc3172dp.exe files.

To exclude the vncksl.exe and vplc3172dp.exe files:

1. Click Add.

2. Select the vncksl.exe and vplc3172dp.exe executable files.

The default location for both files is the VNCK installation folder.

3. Click OK.

Note:
You must exclude the vncksl.exe and vplc3172dp.exe files for all installed VNCKs.

3-36 NX 2007 Release Notes, NX 2007 Series

VNCK - NCK Power On Reset

In the Human Machine Interface (HMI), if you execute an NCK Power On Reset (warm restart) while the
simulation is stopped for any reason, the VNCK state and the simulation state in NX are not the same.

If you try to continue the simulation, or execute an NCReset, NCStop, or NCStart command, NX
displays the following Machine Tool Simulation message and aborts the action.

VNCK executed an externally triggered 'NCK Power On Reset (warm

restart)' while being in 'SIM Stop' mode. This is an unsupported use
case which created an inconsistent state. Shutdown and reboot VNCK to
heal this.

If this happens you must shut down and reboot the VNCK.

HMI Advanced

• HMI Advanced is not supported, because it is not supported on Windows 10.

Positional ISV — Show Machine Axis Positions dialog box

When the setup has a multi-function machine and you use the dynamic manipulator to change the tool
axis for a fixed-axis operation, NX does not update the Show Machine Axis Positions dialog box. To
avoid confusion, use the Show Machine Axis Positions customer default to suppress the dialog box.

1. Choose File tab→Utilities→Customer Defaults.

2. In the Customer Defaults dialog box, choose Manufacturing→User Interface.

3. Click the Dialog Boxes tab, and in the Visibility group, clear the Show Machine Axis Positions
Dialog check box.

Post Configurator

Combine Rapid Rotations

Combine Rapid Rotations supports only four-axis table machines. The results could be incorrect if this
function is set to Yes for a five-axis machine.

Heidenhain TNC PLANE rotation on non-orthogonal 5axis machine

The Real Machine Axis option for tilting plane kinematics does not work with non-orthogonal 5-axis
machines for Heidenhain TNC PLANE rotation. The SPA , SPB, SPC angles in the PLANE command
output could be wrong.

NX 2007 Release Notes, NX 2007 Series 3-37

DEF File Editor

The editor removes comments from the main definition file, including any existing comments.

TCPM prepositioning plane

When this option is activated, the plane output for the prepositioning is wrong in the following case:

• There is only one MCS in the Geometry View of the Operation Navigator, and

• The MCS is defined as Local, and

• Special Output is set to None.

Postprocessing tool paths

Postprocessing a synchronized group

To directly postprocess a synchronized group without entering the Synchronization Manager, you must
use the default postprocessor registered with the machine. NX does not generate synchronized NC
codes if you browse for a postprocessor.

Additive Manufacturing

Product Notes

New version of Build Processor Interface

You must install the updated Build Processor Interface (BPI) 5.2.1.0 version when you upgrade to NX
2007. This installs the latest updated 3.1.4.0 version of the Build Processor System.

You will get this message until you install the (BPI) 5.2.1.0 version: Incorrect version of the Materialise
Build Processor Interface.

Before you install the BPI 5.2.1.0 version, stop any Build Processor Manager process that may be
running, uninstall the old BPI version, and then install (BPI) 5.2.1.0 from this location:
%UGII_CAM_BASE_DIR%\mach\auxiliary\mfgam\BuildProcessorInterface.exe

Note:
You may need to resolve printers in the Build Processor Manager application, after you upgrade.

3-38 NX 2007 Release Notes, NX 2007 Series

Templates

If you created your own template files in an earlier version of NX, you must do this before you upgrade
to the next NX version: copy the template files from the templates folder (%UGII_CAM_BASE_DIR%
\mach\templates\) to a separate location to prevent the installation from overriding your defined
templates.

After the upgrade installation is done, copy your template files to the %UGII_CAM_BASE_DIR%\mach
\templates location.

am.xml data

If you have custom support profiles in your current NX version and you want to upgrade to a newer NX
version, you must ensure that you migrate your am.xml data to the upgraded version so that your
custom profiles are available in the upgraded NX version. For detailed instructions, see Migrating the
am.xml file.

Shortcut key for switching to Additive Manufacturing

You can press Ctrl+Alt+Z to switch from another NX application to the NX Additive Manufacturing
application.

Documentation Notes

Print driver for Renishaw

Quant AM API is installed automatically with NX. You do not need to install it separately, as directed in
the Configure Renishaw 3D printer printer topic in the Additive Manufacturing Help.

Hands-on learning aids in the online help

Caveats

2D Edit

• 2D Edit does not work when the Draw Lowest Line support attribute is set to True.

• When you translate a part with a support structure to which 2D Edit is applied, in the Z direction, then
the 2D Edit sketch is removed.

NX 2007 Release Notes, NX 2007 Series 3-39

• When you rotate a part with a support structure to which 2D Edit is applied, in the X or Y directions,
then the 2D Edit sketch is removed.

• If you edit certain support attributes of a support structure after you apply 2D Edit changes to it,
regeneration of that support will not work as expected. Any changes you make to existing support
attributes such as perforations, lower teeth and so on, may be lost on applying 2D Edit.

Print marks

• Support structure calculation on print marks is not currently working.

• Geometric bodies of print marks on all the non-nested parts get removed when you use the Add
Overflow Build Tray command to add another build tray for the non-nested parts. Generate the
geometric bodies for all print marks on the parts added to another build tray.

• When you use a 3D printer that does not support print marks with negative thickness value and you
try to generate geometric bodies for such print marks, NX displays a warning.
If you generate geometric bodies for print marks with negative thickness value and you switch from a
3D printer that supports such print marks to a 3D printer that does not support them, NX does not
display a warning and these print marks are excluded from the output file.

Support structures anchored to a lower part or user-defined support structures

Note:
Support structures are anchored to a lower part or to user-defined support structures only if you
have set the Prevent creating supports intersecting other parts in the build tray feature toggle
to On in the Early Access Feaures dialog box.

• If you use the Pattern Supports command for support structures that are extended to a lower part or
user-defined support structures and pattern them to a part that does not have any lower part or user-
defined support structures, the patterned support structures are extended only to the length of the
original support structure instead of the build tray. Use the Regenerate Supports command to
properly update the support structures.

• If you use the Create Supports command to add line and point support structures using the
automatic support generation process, then the generated line and point support structures do not
get extended only to the lower part or user-defined support structure. Instead the support structures
pass through them to the build tray. Use the Regenerate Supports command to anchor the line or
point support structures to the lower part or user-defined support structures in the build tray.

• If you use the Move Part command to move along the Z-axis of 3D printer an upper part that has an
existing support structures anchored to a lower part or an user-defined support structure, the support
structures are displayed as out-of-date in the Additive Manufacturing Navigator. Use the
Regenerate Supports command to properly update the anchored support structures.

3-40 NX 2007 Release Notes, NX 2007 Series

• If you use the Move Part command to move along the X or Y axis of 3D printer an upper part that has
an existing support structures anchored to a lower part or an user-defined support structure, the
support structures are not automatically updated or displayed as out-of-date in the Additive
Manufacturing Navigator. Delete the support structures and create them again to generate the
support structures according to the updated orientation of the part.

User-defined supports

When you move a part that has user-defined supports, the part is moved, but the user-defined supports
do not move unless your user-defined supports reference part geometry, for example, edges or faces of
the part.

Heat Sink support attribute

The Heat Sink attribute is currently not visible for gusset support structures.

Additive Manufacturing Process Simulation

Caveats

• The software does not yet support automatically generating compensated/deformed geometry from
computed deformations, for models created with convergent geometry.

• The application will run on a localized version of NX, but the deformation results (in case of solver
slicing) must be selected manually, except for the English, German or French versions.

CMM Inspection Programming

CMM Inspection - New Features

Construct a circle from lines

NX 1973, NX 2007

You can now construct a circle of a specified diameter that is tangent to two lines.

NX 2007 Release Notes, NX 2007 Series 3-41

A constructed circle of fixed diameter is typically used during alignment to simulate the gauge pin of a
fixture.

Example:

1. Choose Home tab→Insert group→Constructed Feature .

2. In the Constructed Feature dialog box, set the following parameters:

Constructed Feature group

Feature Type = Circle

Construction Form = Tangent To

Select Design Feature = Create New

Design Feature Name = new_circle

Circle Diameter group

Diameter = 0.55

3. Select the first line.

3-42 NX 2007 Release Notes, NX 2007 Series

4. Select the second line.

5. View the computed solution.

6. Select the desired solution.

NX 2007 Release Notes, NX 2007 Series 3-43

7. Enter an operation name.

8. Click OK to save the constructed feature.

Alignment operation improvements

NX 1980

CMM now supports two new alignment types:

• Locate PCS by Fitting Nominal to Actual

• RPS (Reference Point System)

Locate PCS by Fitting Nominal to Actual To create a locate alignment, do the following:

1. Select the check box for each motion that is

allowed.

2. Select each feature to align.

The features to align must be point reducible features.

The exact capabilities of the operation are determined by
your CMM controller.

3-44 NX 2007 Release Notes, NX 2007 Series

RPS To create an RPS alignment, do the following:

1. Select the features to align.

2. For each feature, set the direction values to Yes or

No to specify which direction of motion the feature
controls.

The features used for an RPS alignment are usually point

features. The RPS alignment is typically used when
aligning to a free-form surface such as the surface of a
turbine blade. The exact capabilities of the operation are
determined by your CMM controller.

NX 2007 Release Notes, NX 2007 Series 3-45

Copy and Transform

NX 1980

You can now move or copy inspection operations using a transformation. NX CMM supports the
following transformation types:

• Translate

• Rotate About a Point

• Rotate About a Line

• Mirror Through a Plane

To transform one or more operations, do the following:

1. In the Inspection Navigator, select the operations.

2. Right-click and choose Object→Transform.

3-46 NX 2007 Release Notes, NX 2007 Series

From the Inspection Transformations dialog box, you can do the following:

• Specify the transformation to apply.

• Choose whether you want to move the operations or make copies.

• Specify the tolerances for matching the transformed operations to the part model.

For additional information about transformation options, see Transformations dialog box in the
Manufacturing General document.

Enhancement to 5-axis Scan Curve

NX 1953

You can now drag the probe for a 5-axis Scan Curve sub-operation in the graphics window to change
the probe angles. This enhancement makes it much easier to create 5-axis scan paths on complex
surfaces.

NX 2007 Release Notes, NX 2007 Series 3-47

Scan lines on a plane

NX 1953

Use the new Scan Line sub-operation type to easily create scan lines on a planar face. Previous releases
required using the Modeling application to manually create the lines for these type of paths.

The Scan Line parameters are similar to the U and V parameters for the Point Set sub-operation type.

Scan arcs on a curve

NX 1953

3-48 NX 2007 Release Notes, NX 2007 Series

Use the new Scan Arc sub-operation type to easily create scan arcs on cylinders and cones. Previous
releases required using the Modeling application to manually create the arcs for these type of paths.

The Scan Arc parameters are similar to the parameters for the Point Set sub-operation type.

Scan the boundary of a plane

NX 1926

You can now easily create a scan path that follows the boundary of a planar face. Previous releases
required using the Modeling application to manually create the boundary curves for these type of paths.

NX 2007 Release Notes, NX 2007 Series 3-49

To create the scan path, do the following:

1. Choose Home tab→Insert group→Inspection Path.

2. In the Inspection Path dialog box, click Select Feature .

3. Select the feature to inspect.

4. Click Add Sub-Operation .

5. In the Create Sub-Operation dialog box, from the Move Type list, select Scan Curve.

6. In the Geometry group, from the Curve Selection list, select Boundary.

7. Specify the scan curve parameters, and click OK.

8. Click OK to save the inspection path.

Display Nearby Paths

NX 1926

NX can now display other paths in the CMM program as you create and edit an inspection path. In the
following example, the path being editing is displayed in blue. The paths before and after the active tool
path are displayed in gray.

3-50 NX 2007 Release Notes, NX 2007 Series

To change the path display, right-click an object in the Inspection Navigator, and choose Path Display,
then one of the display options.

• Show Selected Paths Only

• Show Nearest Paths

• Show All Paths

Resequence Paths

NX 1926

The Resequence Paths command now has sequencing options.

NX 2007 Release Notes, NX 2007 Series 3-51

• Head Angle Changes considers head angle changes when resequencing inspection paths.

• Tool Change considers tool changes when resequencing inspection paths.

• Distance to Path gives the same results as previous versions of NX.

Circular Arc Transition Moves

NX 1899

When programming inspection paths for round parts, you can specify the Transition Motion as Circular.
This will produce transition moves between inspection points that follow the curvature of the part.

Curve Scanning Improvements

NX 12.0.2 MP12, NX 1899

3-52 NX 2007 Release Notes, NX 2007 Series

A curve that is defined in NX using multiple segments can now be inspected as a continuous scan with
control over the scan speed and point density for each individual segment. In the Curve Scan sub-
operation dialog box, a list of control points is presented. The list is pre-populated with control points at
the beginning and end of each curve segment. You can edit scan speed and point density at each
control point.

3-axis curve scan 5-axis curve scan

These settings are implemented in the DMIS 3.0, DMIS 5.2, and MODUS (Equator) postprocessors using
DMIS statements in the following format:

P(CURVE_SCAN_1)=PATH/CURVE,<point data for curve1>

P(CURVE_SCAN_2)=PATH/CURVE,<point data for curve2>
P(CURVE_SCAN_3)=PATH/CURVE,<point data for curve3>
PAMEAS/DISTANCE,<dist1>,SCNVEL,<speed1>,P(CURVE_SCAN_1),$
DISTANCE,<dist2>,SCNVEL,<speed2>,P(CURVE_SCAN_2),$
DISTANCE,<dist3>,SCNVEL,<speed3>,P(CURVE_SCAN_3)

Data Elimination and Data Filtering

NX 12.0.2 MP10, NX 1880, NX 1899

Data elimination means the removal of measured data points, sometimes called outliers, that are
outside a range of standard deviations from the mean deviation. Data filtering means a high pass, low
pass, or band pass filter is applied to the measured data in order to isolate form deviation from surface

NX 2007 Release Notes, NX 2007 Series 3-53

texture. You can enable these and set the parameters using new groups in the feature dialog boxes and
the method dialog box.

Example Meaning
Data elimination and filtering are turned off.

Data elimination based on a standard deviation

multiple.

Low pass data filter

High pass data filter

These settings are supported by the DMIS 5.2 postprocessor using a statement in the following format:

GEOALG/CIRCLE,LSTSQR,STDDEV_LIMIT,2.,FILTER,CIRCULAR,HIGH,15.,GAUSS

Head Touch on Outer Circles and Cylinders

NX 12.0.2 MP10, NX 1880, NX 1899

Simulation of inspection paths using the PH20 in Head Touch mode has been improved for the following
feature types:

• CIRCLE/OUTER

3-54 NX 2007 Release Notes, NX 2007 Series

• CYLNDR/OUTER

• GCURVE on the surface of a CYLNDR/OUTER

Verify Program

NX 12.0.2 MP10, NX 1880, NX 1899

You can now verify inspection programs before sending them to the shop floor for execution. Many
common errors are detected and reported in the NX information window.

• Feature not measured or constructed

• Datum not defined before a tolerance that references it

• Size tolerance missing when using MMC or LMC modifiers

Arc Scan using Rotary Table

NX 12.0.2 MP8, NX 1880, NX 1899

You can now perform arc scans by bringing the probe into contact with the part, then rotating the part
with the rotary table while holding the probe at a stationary XYZ. You can specify this on the Scan Arc
dialog box using the new Rotary Table choice for Scan Mode.

This is supported by the DMIS 5.2 postprocessor using a statement in the following format:

PAMEAS/P(CIRCLE1_PATH_Scan_Arc),ROTARY,RT(ROTARY1)

Support for Valisys programs

NX 12.0.2 MP8, NX 1880, NX 1899

Inspection programs written using Valisys (eM-ProbeCAD) may now be imported into NX CMM with
good success. Fewer than 10% of operations will need to be edited by hand. Support for the following
statement types was added in NX 12.0.2 MP8:

• DATSET statement

• MACRO and CALL statements

• CONST/POINT,…,BF

• Convert 3 character datum letters VP1,VS1,VT1 to valid datum letters

NX 2007 Release Notes, NX 2007 Series 3-55

• Option to ignore BND1,BND2,BND3,BND4,F(VBND and BOUND/

• Option to ignore Comments

• OUTPUT that isn’t a T() or F() format

• Valisys GEOALG formats

• GSURF/GCURVE Features

• Width Tolerance

• OUTPUT/R()

• TEXT/OPER

• ROTAB/

• SAVE/FA

CMM release notes

PAX file change

The .pax files are now located in the UGII_BASE_DIR\cmm_inspection\templates folder.

VALISYS critical maintenance and retirement notice

The VALISYS application is unsupported as of July 21, 2016. Use the NX CMM Inspection Programming
application instead of VALISYS Programming and use CMM Inspection Execution instead of NX-Inspect.

Linking to PMI information

All geometry referenced by PMI must be in the current reference set, and if it is not, then NX:

• Issues warning messages in the information window.

• May still create features, but will not create paths because there is no access to the feature geometry.

Caveats

Renaming or deleting the SENSORS group

In the Inspection Navigator, do not delete or rename the SENSORS group as this may cause machine
simulations within the Inspection Path dialog box to fail.

3-56 NX 2007 Release Notes, NX 2007 Series

Machine simulation

When you create an inspection path or simulate a program, you may see the following INI Programs
message:

In order to handle INI files in the Program Manager, define the channels
in the Machine Tool Builder.

You can ignore this message for NX CMM Inspection applications. It has no effect on the machine
simulation.

Manufacturing Planning

Line Designer

Product Notes

Template files

To work in Line Designer managed mode, you must import the standard part files delivered with Line
Designer into the Teamcenter database, so you can access these files in the New Item dialog box. If you
do not perform this step, the New Item dialog box displays only blank templates.

A setup script for installing Line Designer templates in Teamcenter is included with NX:
%UGII_BASE_DIR%\MANUFACTURING_PLANNING\templates\tcin_linedesigner_template_setup.bat

For information about how to use the script, see Installing File New templates in the NX help at the
following location:

Home→
Teamcenter Integration for NX→
System Setup/Administration→
Server Setup/Administration→
Installing/creating/modifying templates→
Installing File New templates

Platform support

Line Designer is currently supported only on the Windows platform.

Data Upgrade

Due to changes in the connector design in NX 11 and NX 12, equipment that uses connectors created in
the previous versions should be upgraded to NX 12.0.2 MP5 or later format.

NX 2007 Release Notes, NX 2007 Series 3-57

For more information, see Using library components with connectors from NX 12.0.2 MP5 or earlier in
the Line Designer caveats.

Manufacturing Planning Additions

Manufacturing Planning Additions includes Teamcenter extensions to support the following:

FactoryCAD Migrating libraries from FactoryCAD to Line Designer also requires a Teamcenter
Library extension to support new required dataset types. This extension is included in the
Migration Manufacturing Planning Additions package to Teamcenter installation
(TC13.x_MfgPlanningAdditions_3.1_wntx64.zip).

Find the MfgPlanningAdditions x.x package on Customer Support. Log on using your webkey
credentials.

If you need to request credentials, see the WebKey management page on the Support page.

In Support Center, find the ManufacturingPlanningAdditions package in the following section:

Support Center→
Teamcenter→
Downloads→
Additional Downloads→
Manufacturing Planning Additions

For example, from the Manufacturing Planning Additions list, choose Windows and search for
TC13.x_MfgPlanningAdditions_3.1_wntx64.zip.

Find instructions for applying the Manufacturing Planning Additions in the package .zip file
(Teamcenter_Manufacturing_Planning_Additions 3.1.pdf).

Factory resource samples

Installation of the sample factory resources, conveyors, and robots from the manufacturing resource
sample library to Teamcenter is highly recommended.

Factory Resources

Factory Conveyors

Factory Robots

Factory Weld Guns

Instructions for installing the samples are located in the following section of the Teamcenter HTML
documentation:

3-58 NX 2007 Release Notes, NX 2007 Series

Home→
Installing Teamcenter→
Teamcenter server Installation on Windows→
Adding Features→
Installing and configuring the Manufacturing Resource Library

Manufacturing Resource Library version compatibility

Line Designer supports the use of factory resources with compatible versions of Teamcenter and
Manufacturing Resource Library (MRL). You should find the latest version of MRL in the latest
Teamcenter release.

Note:
You should always upgrade the Manufacturing Resource Library components from the previous
release to the new release.

Saving the connection information in Teamcenter

By default, NX saves the connector connection information in Teamcenter, using the environment
variable:

LD_DO_NOT_SAVE_CONNECTION_TC = 0

To save the connector connection information locally and not in Teamcenter, set the environment
variable:

LD_DO_NOT_SAVE_CONNECTION_TC = 1

Note:
You must always set the variable for all users, to save the connector connection information locally
and not in Teamcenter.

Documentation Notes

Note the following about the Line Designer documentation:

• Line Designer can work with BVR data structures, and the documentation describes BVR procedures
wherever required.
In the release notes, you can find Line Designer in the Manufacturing Planning section.

• Line Designer is now available to work in native NX. Please refer to the Line Designer Help
documentation for more details.

NX 2007 Release Notes, NX 2007 Series 3-59

Note:
End Items support is currently not available in Line Designer in native NX.

• You can find the Line Designer customer defaults in the Configuring Line Designer section, in Line
Designer system administration. Please refer to the Line Designer Admin documentation for more
details.

Caveats

Configured components in the Plant Navigator

Configured out components from the plant structure appear as loaded components with no graphics in
the Plant Navigator.

Using library components with connectors from NX 12.0.2 MP5 or earlier

While placing or disconnecting components in a layout, or while dragging components to another

layout, you may experience incorrect behavior if those components have connectors created in NX 11 or
earlier.

Recommend Before using the library objects in NX 12.0.2 MP5 or later Line Designer layouts, you
ation should upgrade any part files of the library objects that include connectors created
before NX 12.0.2 MP5. To do this:

• Open the library objects in NX.

• Open the Edit Connector dialog box for each connector.

• Click OK.

• Save the library objects in the later version.

Creating occurrence poses

When you create occurrence poses for the components, NX shows no modifications for the parent
component in the tree structure, in the Plant Navigator. Also, if the state of the component for which
you create occurrence poses is Released, you may observe an issue that you can still create and save the
occurrence pose.

Deleting the connected components in a layout

When you work in managed NX, and you load a plant layout and then delete any component that is
connected to another component, NX deletes all the connections in the layout.

3-60 NX 2007 Release Notes, NX 2007 Series

This issue is fixed in Teamcenter 11.6.0.10, Teamcenter 12.2.0.5, and Teamcenter 12.3 and later.

Modifying the kinematic components

In a kinematic assembly, when you jog the component joints, NX displays the component as modified.

The issue is fixed in a later release.

Paste duplicate of the components

To use the Paste Duplicate of the components in NX in Teamcenter 12.3 and later, set the environment
variable:

ME_defer_save_in_clone = false

Fixture Planner

Product Notes

Template files

The Open dialog box displays only installed templates. You must import the standard template part files
delivered with Fixture Planner into the Teamcenter database, so you can access these files in the Open
dialog box. Other templates are not configured to work with Fixture Planner.

A setup script for installing Fixture Planner templates in Teamcenter is included with NX:
%UGII_BASE_DIR%\MANUFACTURING_PLANNING\templates\tcin_fixtureplanner_template_setup.bat

For information about how to use the script, see Installing File New templates in the NX help at the
following location:

Home→
Teamcenter Integration for NX→
System Setup/Administration→
Server Setup/Administration→
Installing/creating/modifying templates→
Installing File New templates

Platform support

Fixture Planner is currently supported only on the Windows platform.

Manufacturing Planning Additions installation

Using Fixture Planner with Teamcenter also requires you to install the Manufacturing Planning Additions
package to the Teamcenter server installation (for example, Manufacturing Planning Additions 3.1).

NX 2007 Release Notes, NX 2007 Series 3-61

Find the MfgPlanningAdditions 3.1 package on Customer Support. Log on using your webkey
credentials.

If you need to request credentials, see the WebKey management page on the Support page.

In Support Center, find the Manufacturing Planning Additions package in the following section:

Support Center→
Teamcenter→
Downloads→
Additional Downloads→
Select a version

For example, from the Select a version list, choose Manufacturing Planning Additions 3.1, then select
Manufacturing Planning Additions 3.1. From the Filter by OS/Language list, choose Windows

Find instructions for applying the Manufacturing Planning Additions in the package .zip file
(Teamcenter_Manufacturing_Planning_Additions 3.1.pdf)

Documentation Notes

Note the following about the Fixture Planner documentation:

• In the release notes, you can find Fixture Planner in the Manufacturing Planning section.

• Fixture Planner is now available to work in native NX with limited capabilities. Please refer to the
documentation for more details.

Caveats

Loading the study with assembly load options

In Fixture Planner, while loading a study using assembly load options, you may observe the different
behavior for the minimal load and the partial load option.

Minimally Load
NX currently supports the partially load and the fully load options, and does not support the
minimal loading of the study and its components in a Minimally Load - Lightweight display
option.

Creating occurrence poses

When you create occurrence poses for the components, NX shows no modifications for the parent
component in the tree structure, in the Planning Navigator. Also, if the state of the component for
which you create occurrence poses is Released, you may observe an issue, that you can still create and
save the occurrence pose.

3-62 NX 2007 Release Notes, NX 2007 Series

Assembly Line Planner

Product Notes

Template files

To work in Assembly Line Planner managed mode, you must import the standard part files delivered
with Assembly Line Planner into the Teamcenter database, so you can access these files in the New Item
dialog box. If you do not perform this step, the New Item dialog box displays only blank templates.

A setup script for installing Assembly Line Planner templates in Teamcenter is included with NX:
%UGII_BASE_DIR%\MANUFACTURING_PLANNING\templates\tcin_linedesigner_template_setup.bat

For information about how to use the script, see Installing File New templates in the NX help at the
following location:

Home→
Teamcenter Integration for NX→
System Setup/Administration→
Server Setup/Administration→
Installing/creating/modifying templates→
Installing File New templates

Platform support

Assembly Line Planner is currently supported only on the Windows platform.

Manufacturing Resource Library version compatibility

Assembly Line Planner supports the use of factory resources with compatible versions of Teamcenter
and Manufacturing Resource Library (MRL). You should find the latest version of MRL in the latest
Teamcenter release.

Note:
You should always upgrade the Manufacturing Resource Library components from the previous
release to the new release.

Manufacturing Planning Additions installation

Using Assembly Line Planner with Teamcenter also requires you to install the Manufacturing Planning
Additions package to the Teamcenter server installation (for example, Manufacturing Planning Additions
3.1).

Find the MfgPlanningAdditions 3.1 package on Customer Support. Log on using your webkey
credentials.

NX 2007 Release Notes, NX 2007 Series 3-63

If you need to request credentials, see the WebKey management page on the Support page.

In Support Center, find the Manufacturing Planning Additions package in the following section:

Support Center→
Teamcenter→
Downloads→
Additional Downloads→
Select a version

For example, from the Select a version list, choose Manufacturing Planning Additions 3.1, then select
Manufacturing Planning Additions 3.1. From the Filter by OS/Language list, choose Windows, and
search for TCx.x_MfgPlanningAdditions_3.1_wntx64.zip

Find instructions for applying the Manufacturing Planning Additions in the package .zip file
(Teamcenter_Manufacturing_Planning_Additions 3.1.pdf)

Documentation Notes

Note the following about the Assembly Line Planner documentation:

• In the release notes, you can find Assembly Line Planner in the Manufacturing Planning section.

Caveats

Loading a line with assembly load options

In Assembly Line Planner, while loading a line using assembly load options, you may observe the
different behavior for the minimal load and the partial load option.

Note:
NX currently supports the partially load and the fully load options, and does not support the
minimal loading of a line and its components. Use only the Partial load - Lightweight display
option to load a line.

Structure of a workarea object

Assembly Line Planner uses the recommended BiW data model. The workarea objects (MEWorkarea)
must not have a process twin structure.

Supporting product configurators

Assembly Line Planner may not support some advanced product configurator use cases, when you
create the variant conditions on operations. This does not impact loading of the data in NX.

3-64 NX 2007 Release Notes, NX 2007 Series

Knowledge Fusion and DesignLogic functions

Product Notes

Impact of angle base units on custom Knowledge Fusion and DesignLogic functions:

Customers who use NX interactively should see no impact from this change. Customers automating NX
programmatically should read this section carefully.

The internal base units for angles are now radians instead of degrees. Internally, calculations involving
angles will be converted to radians while the calculation is performed. This change enables certain new
calculations involving angular units.This affects not just the angle measurements but every
measurement that includes angular dimensions as shown in the following table.

Measure Base units before radian-based Base units in radian-based

Angle degrees radians
Angular Velocity degrees/sec radians/sec
Angular Acceleration degrees/sec^2 radians/sec^2
Angular Jerk degrees/sec^3 radians/sec^3
Per Angle 1/degree 1/rad
Angular Momentum per Angle mN-mm-sec/degree mN-mm-sec/rad
Moment per Angle mN-mm/degree mN-mm/rad
Voltage per Angular Velocity microV-sec/degrees microV-sec/radians
Length per Angle mm/deg mm/rad
Per Angle Squared 1/degree^2 1/rad^2
Mass Moment of Inertia Per Angle kg-mm^2/deg kg-mm^2/rad

Custom DesignLogic and Knowledge Fusion functions with parameters involving angular
dimensionalities may need to be scrutinized for accuracy.

• Functions that have been authored using pure KF language may not be impacted. Any special coding
done by you to handle units/unit conversions in your functions should work the same as they did in
NX 1872.

• Functions that make calls to UG Open/Ufunc accepting and returning dimensionalities with angles
may be impacted. Even those that don’t may be impacted.

For example, the functions floor() and ceiling() had to be changed because they sometimes may receive
a value that has an angle dimension, in which case UF_KF_ask_number() would return a radian value.

NX 2007 Release Notes, NX 2007 Series 3-65

You might have special custom coding to apply unit conversion from degrees to radians in such cases
which may no longer be necessary. We also recommend looking into the APIs
UF_KF_ask_number_with_measure & UF_KF_make_number_with_measure that provide numbers in
degrees while preserving the dimensionality. Using these APIs instead of UF_KF_ask_number &
UF_KF_make_number may help achieving the original intent of the KF/DL functions. For example:

//========================================
DllExport extern void supplimentary_Angle(UF_KF_value_p_t *data, int
num, UF_KF_value_p_t *rv)

//Initialize UF session
UF_initialize();
double angle=0;
char *dim = "";

// Extract a degree-based value and its dimensionality from an input

argument
UF_KF_ask_number_with_measure(data[0], &angle, &dim);

//Calculate supplementary
double comp = 180 - angle;

// Prepare a return value with a given dimensionality.

UF_KF_make_number_with_measure(comp, dim, rv);

UF_terminate();

3-66 NX 2007 Release Notes, NX 2007 Series

Validation

Model Based Systems Engineering

Caveats

Creating verification requests from NX

NX does not support Creating verification requests from NX in the Active Workspace 5.2 and above. Use
the earlier versions of the Active Workspace to test this workflow.

Tooling Design

Mold Wizard

Mold Wizard and Progressive Die Wizard Caveats

BOM shortcut options

In the Bill of Material dialog box, when you right-click a column heading, you can choose from the
following additional shortcut options:

Shortcut item Description

Sort Numbers and Text Seperately Sorts the BOM list for the selected column by grouping
items together that contain numbers, and items together
that contain text.
Use Alphabetic Method Sorts the BOM list for the selected column alphabetically.
Use Alphanumeric Method Sorts the BOM list for the selected column
alphanumerically.

Progressive Die Wizard

Mold Wizard and Progressive Die Wizard Caveats

BOM shortcut options

In the Bill of Material dialog box, when you right-click a column heading, you can choose from the
following additional shortcut options:

NX 2007 Release Notes, NX 2007 Series 3-67

Shortcut item Description

Press Die Checker

Product Notes

Platform support

Press Die Checker is currently supported only on the Windows platform.

Caveats

Minimal load support

The minimal load is not completely supported in Press Die Checker.

Accuracy in collision checking

To achieve the most accurate collision check, the step increment size during the simulation should be
around 1. Increasing step size speeds up the simulation movement, but accuracy might be compromised
and some collisions may not be detected.

Data translation

Product Notes

Updates for the default tessUG.config JT configuration file

• To ensure that you are using an up-to-date configuration file, we highly recommend using the
tessUG.config configuration file included with NX and customizing it per your current settings.

• Make sure you delete all the references to the activateCsysPMI option in the JT configuration file.
If activateCsysPMI = true is set anywhere in the configuration file, the translator stops the
translation process.

• The doSectionViews configuration option which is used to process non-lightweight PMI section
views (also known as heavyweight section views) is removed from the default tessUG.config file

3-68 NX 2007 Release Notes, NX 2007 Series

shipped with NX11. This option is now renamed as LegacyHeavyweightSectionViews. If your

existing NX part or assembly contains section views created using PMI tab→Section View command
in Pre-NX11 versions and you want to translate these section views to a JT file, you need to add
LegacyHeavyweightSectionViews option in your tessUG.config configuration file and set it
to true.

CATIA V5 translator product notes

You can now import CATIA V5-6R2020 SP3 files to NX:

The translator now retains the wireframe color, font, width, and style attributes. For more information,
see Import and export entity mapping.

ACIS translator product notes

You can now read and write ACIS version up to 2021.

DXF/DWG translator product notes

You can now read and write AutoCAD DXF/DWG version up to 2022.

NX to JT translator product notes

When you set JtFileFormat = “10” in the tessUG.config file, the NX JT translator now exports to version
JT 10.6 files. The JT 10.6 version additionally supports:

• Convergent bodies that have mixed geometry.

• Wireframe line styles applied on curves, such as:

Long Dashed Dotted

Long Dashed Double Dotted

Long Dashed Triplicate Dotted

Long Dashed Double Short Dashed

Teamcenter Visualization 13.1 or later is required to view the additional capabilities of the JT 10.6
version.

For more information about exporting to previous JT file versions, such as 10.5, 10.2, 9.5, and so on,
see the JtFileFormat configuration option in JT configuration file—Setup section in the NX help.

NX 2007 Release Notes, NX 2007 Series 3-69

NX ProE translator product notess

You can now import Creo 7.0 files to NX.

IFC translator product notes

• The Import IFC File dialog box is redesigned as an import wizard. You can use the import wizard for
quick interrogation of the IFC file and for fine-grained control over IFC to NX translations.

• Additional tessellation controls are available for export of NX data to IFC. You can now specify that the
NX light-weight representation should be used when exporting IFC files. Additionally, when
specifying custom tolerance values, you now have the choice to specify either an absolute tolerance
or a relative tolerance. Using the NX light-weight representation reduces the IFC file size without
compromising the necessary detail of small holes or features.

• Improvements have been made to the generation of Globally Unique Identifiers (GUIDs) during export
of IFC files.

3-70 NX 2007 Release Notes, NX 2007 Series

Caveats

Support for imported PMIs

The following NX translators do not support the export of Imported PMI objects:

• 2D Exchange

• DXF/DWG

• STEP AP203 and STEP AP214

Exporting convergent bodies

• The NX ACIS and CATIA V4 translators do not allow selection of convergent bodies.

• The NX STEP AP203, STEP AP214, and IGES translators do not support exporting of the convergent
bodies. These translators add a message “Convergent/Facet bodies are not processed” to the log file.

Support for Teamcenter settings

The following translators do not support other Teamcenter settings other than variant rule, revision
rules, and effectivity:

• STEP AP203, AP214, and AP242

• IGES

• DXF/DWG

• 2D Exchange

Limited support for new line styles

The following NX translators do not support the new OOTB and shipbuilding line styles, and write them
as Solid line style:

• CATIA V5

• IGES

• NX to JT

• STEP AP203, AP214, and AP242

NX 2007 Release Notes, NX 2007 Series 3-71

Internationalization caveat

File import or export by the following translators may not work if you set the NX temporary directory
UGII_TMP_DIR to a folder containing non-locale characters.

• DXF/DWG

• IGES

• STEP

• 2D Exchange (export only)

NX to JT translator caveats

NX to JT translator caveat for the Windows operating system

If you are translating pre-NX11 parts with material, texture, and light applied on it and you want to
get the texture or light information into the JT file, We recommend you to invoke NX in Author2
(non-IRAY+) rendering mode and then translate the parts to a JT file. This recommendation is
applicable for JT creation from interactive NX session as well as command line application ugtopv.
Contact GTAC to get more information on how to invoke NX in Author2 (non-IRAY+) rendering
mode.

Note:
If you invoke NX in Author2 (non-IRAY+) rendering mode then these options will be available
in the JT Configuration and the Export JT dialog boxes.

NX to JT - IRAY texture and material caveats

In some situations, you may find differences between the quality of the texture displayed in NX and
that displayed in JT, when you view it in the Teamcenter Visualization.
For NX parts that contains symbolic thread features:
• If you apply different colors to multiple curves of a symbolic thread feature in an NX part, they
will appear in the same color in the JT file.

• If you associate a PMI object to a single curve of a symbolic thread feature in an NX part, it gets
associated to all the curves in the JT file. If you select any thread feature PMI in the JT file in
Teamcenter Visualization, all the curves are highlighted.
Exporting line style and line width applied on symbolic thread curves caveat
Different line styles and line widths applied on the curves of symbolic thread features are not
exported to JT files. When viewed in Teamcenter Visualization, such curves are displayed with the
Dashed line style and the Thin line width.

3-72 NX 2007 Release Notes, NX 2007 Series

DXF/DWG translator caveats

DXF/DWG — Dimension export caveats

These caveats are applicable when you export a file using the 3D option in the AutoCAD DXF/DWG
Export Wizard dialog box.

• Dimensions associated with external references are exported as non-associative dimensions to

the DXF/DWG file.

• NX Radius dimensions associated with ellipse or spline object are translated as AutoCAD block
reference.

• The dimension associated between NX sheet object and View port object may be translated as
overridden text of AutoCAD dimension.

• Narrow dimensions are exported as non-associative dimensions to the DXF/DWG file.

• Chamfer and Thickness dimensions are exported as block reference to the DXF/DWG file.

• Angular dimensions created with vector option are exported as block reference to the DXF/DWG
file.

• Dimension with fits tolerance having fit tolerance style other than Fit Symbol is exported as block
reference in AutoCAD.

• Dimension text location may not match with NX for the dimensions created with oriented text.

• Dimension line breaks and foreshortening symbols are not supported when dimension is
exported as group or block.

• If a dimension text is on the extended dimension line, the exported dimension has to be updated
to view any foreshortening symbols on it.
DXF/DWG — MText import caveats
You cannot import:

• MText paragraph tabs to NX.

• Euro symbol (created using %%128 in MText) to NX.

DXF/DWG — Architecture data import caveats
• You can not import:

• View dependent data

• Texture data

NX 2007 Release Notes, NX 2007 Series 3-73

• Corner windows

• Wall cleanups

• Body modifiers on staircase

• Associativity defined between the architecture objects is not maintained in NX. For example, door
on wall will not move along if wall is moved.
DXF/DWG — Solids import caveats
You cannot import:

• Material, color, and transparency applied on solids in the DXF/DWG file.

• Solids data at location outside the NX supported bounding box.

DXF/DWG translator- Image translation Caveats
• When you import DXF/DWG model data to NX drawing view, the translator does not support
image translation.

• When you import DXF/DWG file that contains image rotated by angle which is not in a multiple of
90, the image is imported with zero degree rotation.

Note:
In NX, the images are rotated in steps of 90 degrees only.

• When you import DXF/DWG file with images having other than .jpeg, .tiff, and .png formats to
NX, the translator does not support importing of such images.

• Images are not imported if exported as CGM.

• Image translation is not supported if the DXF/DWG file is imported to workpart.

DXF/DWG translator- 3D Workflow caveats
When you export View Breaks using 3D workflow, the translator does not support an export of the
following:

• NX Object clipping and view break symbols.

• Geometry clipped inside a view boundary.

• A section line arrow in Break view.

Dimension export using 3D workflow

3-74 NX 2007 Release Notes, NX 2007 Series

• When a dimension is exported as a block reference, the foreshortening symbol is not supported.

• 3D workflow does not support the inclusion of before/after appended text in the export of the
inspection dimension. It always includes all the appended text in the frame.

• The translator does not support a tolerance separator in the output DXF/DWG file.

Text export using 3D workflow

• When you export text as lines using 3D workflow, the translator ignores the text symbol aspect
ratio.
DXF/DWG translator- Associative dims to polyline and block caveats
You cannot import dimension as real associative in following scenarios:

• Blocks are imported as custom symbols or as a part and if dimensions are associated with block
reference in the DXF/DWG file.

• Dimensions are associated to 2D and 3D polyline.

• Dimensions that have following Object snap points:

• Tangent

• Perpendicular

• Nearest

• Apparent Intersection

• Parallel

• Intersection

• Dimensions are associated to arc segment of the polyline.

DXF/DWG translator- Support for drafting objects caveats
You can not export:

• Drawings created in the Layout application using the 2D option.

• Custom symbols used in a PMI table.

• Section views.
DXF/DWG Support for Hole table

NX 2007 Release Notes, NX 2007 Series 3-75

If the multiple sections of the hole table are created on different drawing sheets, the continuation
text will be lost.
DXF/DWG support for importing model and layout data
• You cannot import DXF/DWG model data and layout data to a drawing view while importing to a
work part.

• When you import DXF/DWG files with model data to drawings with Import Curves as Sketch
Curves , it results in increased translation time.

2D Exchange caveats

• Object attributes with title longer than 50 characters or string value longer than 132 characters are
not exported to 2D parts.

2D Exchange – Dimension export caveats

These caveats are applicable for both, when you export a file using the NX Part file option in the 2D
Exchange Options dialog box or when you export a file using the 2D option in the AutoCAD
DXF/DWG Export Wizard dialog box.

Following dimensions are exported with the Override Dimension Text:

• Feature Parameter Dimensions

• True Length Dimensions

• Dimensions in scaled view and output set to Modeling (applies only when you export a file using
the NX Part file option in the 2D Exchange Options dialog box)

• Dimensions associated to:

• Drafting Intersection point

• Offset center point

• Section line (in scaled view)

• The dimensions where associated object type changes in the flattened part. For example, circle
projected as line.

Following Data will be exported as grouped geometry in the 2D part file and as a block in the DXF or
DWG file.

• Linear and Radial callouts

• Retained dimensions

3-76 NX 2007 Release Notes, NX 2007 Series

• Component level dimensions and PMI dimensions

• Inherited ordinate PMI dimensions

• Dual dimension in scaled views and output set to Modeling.

• Dimension with hole and shaft tolerance in scaled views and output set to Modeling.

• Dimensions associated with:

• Blanked objects

• 3D and Symmetric centerlines

• Faces

• Two object intersection (applies to ordinate dimension only)

• Target Points

• Dimension created in plane other than view plane.

• PMI Partial Bolt Circle centerline.

2D Exchange translator- Image translation caveats
• 2D Exchange Translator does not translate image, if image is not projected on 2D. This happens
when image is in XY plane and trimetric view is exported.

• 2D Exchange Translator supports translation of images only if input is being exported to Part File
and not to IGES).
2D Exchange translator- Dimension export caveats
• When Dimension and a Leader are associated with the symmetrical centerline, the translator
exports them as a grouped geometry.

• When a radial dimension is associated with a break view geometry, the translator exports it as a
group geometry.

• When a perpendicular and angular dimension is associated with a break view section line,
translator exports them as a group geometry.
2D Exchange translator - Foreshortening Symbol export caveats
A translator does not support export of foreshortening symbol when dimension is exported as a
group in a 2D part.
2D Exchange translator – Leader caveats

NX 2007 Release Notes, NX 2007 Series 3-77

A leader with an extension line is converted as a grouped geometry when it is associated with a
spline in a 2D part.
2D Exchange translator – Weld symbol caveats
When you export a weld symbol containing arcs, the translator exports it as a grouped geometry.
2D Exchange translator – Support for drafting objects caveats
You can not export:

• Drawings created in the Layout application

• Custom symbols used in a PMI table.

• Section view while exporting Model views.

2D Exchange Support for Hole table
If the multiple sections of the hole table are created on different drawing sheets, the continuation
text will be lost.

DXF/DWG and 2D Exchange - PSM body support project caveats

• If you export convergent bodies as polyline mesh, it exports only edges.

• Colors are not honored when you import 3D faces as convergent bodies or JT facets.

• Colors applied to face of convergent body is not honored on export.

• You cannot export model views with convergent bodies with 2D Exchange (or using 2D option on
DXF/DWG export dialog box).

STEP translator caveats

• Line fonts for PMI objects are not supported for import or export.

• PMI objects in section views are not imported from or exported to STEP 203/214.

• Translating hidden components and objects:

• When you export NX components as nested external references to STEP AP203 or AP214, the
hidden components will not be marked as invisible.

• When you export NX components as basic or nested external references to STEP 242, the hidden
components will not be marked as invisible.

• The translator does not export hidden objects at the assembly level, even if the
PROCESS_HIDDEN_OBJECTS is set to Yes.

3-78 NX 2007 Release Notes, NX 2007 Series

• When you export NX data to a STEP AP242 file, the translator excludes hidden points and curves,
even if the PROCESS_HIDDEN_OBJECTS is set to Yes.

• Kinematics defined between different bodies within single part cannot be exported to STEP AP242.

• When you import kinematics information from AP242 XML files, the translator names the joints as
Rigid Group. To use such joints in simulation, you must rename them per your requirements.

• When you export or save NX data to an STPX file, the STEP translator does not export nested external
references.

• When you export NX data containing PMI lightweight section views to a STEP AP242 file, the
following are not supported:

• Selective object sectioning

• Section plane display properties

• Section view crosshatches

• When you export NX data to a STEP AP242 file, the translator uses B-spline Tolerance value of 1e-5
meters and ignores the B-spline Tolerance value specified in the Advanced tab of STEP Export dialog
box.

• When you export NX data to a STEP AP203, AP214, or AP242 file, the translator does not export NX
layer categories.

• When you export data to a STEP AP242 file, the translator does not export:

• Layer mapping and layer mask.

• Color overrides for faces, wireframes, points, and coordinate systems.

• Components and body colors, when you export components as external references.

• Color overrides at the assembly level, when you export selected objects.

• Color overrides at the assembly level, when you export NX files to XML (*.stpx, *.stpxz).

• The STEP AP203 and AP214 translators do not export and import assembly color overrides.

• Due to STEP schema limitations, chamfer dimensions from NX are exported as presentation data.

• When you import tessellated PMI from STEP AP242 files, vertices that create the PMI display are not
optimized and this can result in an increase in the NX file size.

NX 2007 Release Notes, NX 2007 Series 3-79

CATIA V5 translator caveats

• The translator exports NX files to CATIAV5 R14 files.

• If an attempt to export a newly created part in Teamcenter Integration for NX mode fails, close and
open that part file and re-run the translation.

• You cannot import CATIA V5 R7 and earlier version of files.

• Color is supported on a per face basis.

Color is not supported when you export an NX convergent body or face to a CATIAV5 point cloud
mesh.

• You can only import CATIA V5 “Lines and Curves” into NX using default Linetype and Thickness
values.

• You cannot export NX parts with file name containing international characters.

• The CATIAV5 translator does not keep a log of failed export of password protected data during
translation.

• During import, the translator will look for component files at and below any directories specified
through Assembly Search Directories.

• The translator looks for the default settings file in the following sequence:

1. Settings file specified using the d= option if you launch the translator from command line
prompt.

2. Settings file specified using the NX_CATIAV5_DEF environment variable.

3. Settings file specified using customer defaults.

4. Searches for the settings file in the directory specified by the environment variable
UGII_CATIAV5_DIR. If this is not defined on your system, you can set it to %UGII_BASE_DIR%
\catiav5 on Windows or $UGII_BASE_DIR/catiav5 on Linux.

ACIS translator caveat

Heal Bodies has been enabled by default in ACIS Import to remove invalidities in the imported data.

IGES translator caveat

• When you import trimming surfaces to NX, the trimming curves that are outside the surface limits are
not snapped to the surface boundary if:

3-80 NX 2007 Release Notes, NX 2007 Series

• Any portion of the trimming curves is outside the surface limits.

• Any curve is outside the surface limits by more than the distance specified by the general Distance
Tolerance Modeling preference.

• NX Drafting symbols are not exported.

Exporting unsaved imported IFC file

In NX 1926, your NX session may crash if you import an IFC file and export it without saving. You must
save your NX work prior to exporting the imported file using Save As or Export IFC command.

ACIS translator caveats

When you import ACIS files, few solid bodies from ACIS file may get imported as collection of sheet
bodies, and sheet bodies with multiple faces may get split into multiple sheet bodies. This will also result
in increased translation time.

Exporting unsaved imported IFC file

In NX 1926, your NX session may crash if you import an IFC file and export it without saving. You must
save your NX work prior to exporting the imported file using Save As or Export IFC command.

Caveat for all translators

The password protected parts or assembly components are not exported to other file formats.

Mechatronics Concept Designer

Product Notes

PLCOpen XML export for STEP 7

Mechatronics Concept Designer can export the sequence of operation in the standardized XML format
PLCOpen XML. PLCOpen XML can be imported into STEP 7 5.5 SP 2 Hotfix 4 and above. If you need to
update your current STEP 7 installation you can find information about the latest service packs and
hotfixes at the following:

English: https://support.industry.siemens.com/cs/products?
dtp=Download&mfn=ps&pnid=14342&lc=en-WW

NX 2007 Release Notes, NX 2007 Series 3-81

Automation Designer

Product Notes

To work with Automation Designer, you must set it up as a four-tier, client-server application with
Teamcenter as the server.

Software requirements for Automation Designer in NX 2007

Support
ed
Product version Notes
Teamcen • 12.2 We recommend that you use Teamcenter 13.3 or later to use the complete
ter functionality of Automation Designer.
• 12.3
Note:
• 12.4 If you are upgrading Teamcenter, see Teamcenter Upgrade in the
Teamcenter documentation.
• 13.1

• 13.2

• 13.3
EPLAN • 2.8 You must have an EPLAN runtime license EADN:Application 0193.
Automation Designer supports only .zw9 files.
• 2.9

• 2.9
SP1
TIA Portal • 15.0.0 You must have a valid TIA Portal license.

• 15.1.0 • STEP7 Professional Combo V15, V15.1, V16, V17

• 16.0.0 • (Optional) STEP7 Safety Advanced Combo V15, V15.1, V16, V17

• 17.0.0 Note:
If you want to export safety software blocks to TIA Portal, you need a valid
license for this component. Safety exchange is supported from V15.1 and
higher.

• (Optional) Drive Support: SINAMICS Startdrive V15, V15.1, V16, V17

• (Optional) SINUMERIK Toolbox V16, V17

3-82 NX 2007 Release Notes, NX 2007 Series

Support
ed
Product version Notes

Note:
Automation Designer does not exchange data with TIA Portal V14.SP1. But
you can export program blocks of TIA Portal V14.SP1 to a higher TIA Portal
version.

ECLASS 8 or later You must have a valid eCl@ss license.

ADVANC
The terms of use of the eCl@ss standard state: This content contains eCl@ss. The
ED
use of the eCl@ss standard requires a license. Please register and order in the
Download Portal.
Automati 9.0 You must add Automation Designer content to Teamcenter. If Automation
on Designer content already exists, you must upgrade it.
Designer
To upgrade Automation Designer content to support NX 2007, you must:
content

1. Upgrade the existing library in Teamcenter before you run NX 2007.

2. Run the Automation Designer application in NX 2007, and then upgrade your
other existing data.

Automation Designer supports the versions of Windows that NX supports.

NX 2007 Release Notes, NX 2007 Series 3-83

Caveats

Templates

• If you use value sets in unmanaged mode, the template definition from the library must be available
to be able to change or apply value sets.
(AD-41669)

Collaboration

• When multiple users create subsets for the same mechanical data in the same project, some
mechanical objects can be greyed out in the Collaboration Navigator and they are invisible in the 3D
model. Only one user should create a subset and publish the collaboration context. Then other users
can use the Load external objects command to avoid creating subsets by themselves.
(AD-8881)

• Automation Designer does not save object mappings when working with versions of Teamcenter 12.
This is fixed with NX2011 and NX1980.3400.
(AD-45676)

Data exchange

• You need DBA rights in order to import a project on the target site. After the import, you can change
the owning group of the imported data to the Automation Designer group to enable modifications by
other users in this group.

• If you share a project by PLMXML that includes mechanical collaboration data, the import is successful
only if there is at least one object mapping in the project.
(AD-42589, AD-27236)

• In versions of Teamcenter prior to 13.2 the Teamcenter user name must not exceed the length of 14
characters. Otherwise transfer of ownership is not successful.

Snapshot

• The functionality to inspect a snapshot is limited and experimental. Inspection functionality is only
available, when the AD_ENABLE_INSPECT_SNAPSHOT=1 environment variable is set.

• Restoring a snapshot can fail with error Object is reference by relation when using Teamcenter
versions prior to TC13.1, TC12.4.0.3, and TC13.0.0.3. Snapshot restore is not available if Automation
Designer is based on Teamcenter 12.2 or TC12.3 series.
(AD-35936)
To use snapshots that are created of older versions of Teamcenter or Automation Designer, you must
upgrade the data.
Please follow this procedure:

3-84 NX 2007 Release Notes, NX 2007 Series

1. Ensure that no other users are working on the project currently.

2. Save your current state beyond restoring an older one by taking a snapshot before restoring.

3. Restore the snapshot and upgrade its data.

4. Take a snapshot of the upgraded state to preserve the upgraded data.

5. Delete the snapshot of the older version.

(AD-24321)

• A snapshot can only be inspected while the same project is not open, and content can be copied. Do
not copy templates usages from the snapshot. Copying template usages from the snapshot into the
current project breaks all templates usages of this template in versions of Teamcenter prior to TC13.3.

Automation

• The sdx-file import of CreateMyConfig 6.0 release version has some known issues that block the
transfer of the engineering result from Automation Designer to CMC:

• The products S120M, CU310-2PN and CU310-2DP after export from Automation Designer are not
imported successfully in CreateMyConfig.
(AD-8763, AD-8779, AD-22967)

• The encoder number value as defined in Automation Designer is not respected by CMC. You use the
encoder number for establishing the mechanical connection between Motor and Encoder.
(AD-8764)

Electrical Design

• If you set cell settings Wrap, wrapping the text will not adjust the cell height. This results in
overlapping texts and reduces readability. It is recommended to avoid using Wrap in reports.
(AD-41949)

• If you

1. Add pages to the project´s documents by

2. including the pages into a template and

3. inserting the template to the project while

4. the page in the template contains non-translatable annotations

any additional free text that you later add to the page is not included to the export for translation

NX 2007 Release Notes, NX 2007 Series 3-85

(AD-44515)

• If you import symbols from DWG/DXF and the line color defined in the symbol image is the same as
the background color of the pages, the symbol is not visible on the page once inserted. Automation
Designer warns you about this. You can edit the symbol and change the line color.
(AD-44685)

• If you update any report in managed mode before you update the Table of Content report, you need
to save the project before updating the Table of Content report. Not saved updated reports will not be
part of Table of Content.
(AD-8770)

• If you include pictures in symbols, those pictures are scaled to a smaller size in PDF, paper printout
and in exported DXF or DWG files. This will be fixed with NX2011.
(AD-43725)

• If an existing product selection for terminal is changed, the identification numbers of the terminal are
incremented instead of kept. As a workaround you can manually fix terminal numbers.
(AD-45561)

• If you import symbol geometry from DXF or DWG files, they can show twisted lines instead of a circle
when the symbol is placed on a page. This will be fixed with the next major NXAD version.
As a workaround: edit the symbol and replace the twisted lines with a sketched circle.
(AD-44084)

Programming Tools

NX Open

NX Open differences between releases

The NX Open differences between releases and deprecated items replacements are now published in
Support Center.

In the NXOpen APIs What's Changed Reports webpage, you can select the Changes That May
Require Code Changes tab to view the changes that have occurred for the release and any that might
require changes to your existing code. The What's New tab provides new items for the release.

You can compare your release to another one to see the amount of change that has occurred between
the two releases. In the Comparing NX <your release> and: listing, select the release you want for
comparison, and click Compare. You can get comparisons for up to two years of releases.

3-86 NX 2007 Release Notes, NX 2007 Series

Release upgrades

A primary goal of NX Open is to maintain your automation investments. This is done by adopting
policies which minimize the amount of required code changes by you to migrate your applications to
new releases of NX. The following contains a description of these policies and how they impact your
ability to support the users of your applications, and the steps you should take to successfully move your
application to new releases of NX.

NX Open API change policy

NX maintains the following three primary policies to protect your investments:

• API stability
Stability ensures that the API that has been released will continue to work. This means that the API is
still present in future releases and the behavior of the API doesn't change. API changes should be
designed to minimize any changes to your source code. For example, if the capabilities of a method
are expanded which requires new parameters, then NX may maintain and optionally deprecate the
original method and add a new method that includes the new capabilities. By doing this, existing
applications do not require code changes unless they want to take advantage of the new capabilities.

• Binary compatibility
Compatibility means that applications that are built against a specified release continue to work with
subsequent releases. This requires not only that API stability is maintained but also is binary
compatible. For example, re-ordering the values of enum members so that API stability is maintained.
In this case, the values have changed so existing automation programs will be using the wrong
values. In other cases, deleting a method or modifying the inheritance hierarchy of a class will likely
cause run-time errors for existing programs.
The other aspect of binary compatibility is the compiler. When the compiler NX uses changes, this
may break binary compatibility of automation programs. While some language bindings are more
tolerant of being backwards compatible, such as Java, others are not as tolerant, such as C++.
NX libraries will be forward compatible for all releases in a release family. If you compile and link your
application with the libraries shipped with a functional release of NX, such as NX 1847, then your
application should continue to run with all future monthly releases in that release family (NX 1847).
This compatibility means you do not need to recompile, relink, and reship your applications to
customers running various monthly releases of NX. Note that NX is not backwards compatible, which
means you can't compile and link an application in NX 1847 and expect it to work in NX 12.
NX will only change the compiler used (breaking binary compatibility) in a functional release and will
not change it more than once a year. During the functional release, the compiler may change and APIs
may be retired per the deprecation policy for deletion.

• Deprecation policy
If an API change requires you to make source code changes, you are given notice one year in advance,
if possible. For example, if a method is going to be replaced by a new method, the original method is
marked as deprecated in NX 1847, which is the release family. The original method is maintained
through the current release family and through the next release family also, after which the API may
be retired and removed.
The what's changed reports in Support Center and, if possible, compile time warnings are used to
warn you of changes made in the current release and changes coming in the next release. The

NX 2007 Release Notes, NX 2007 Series 3-87

deprecated items topic in Support Center provides a list of the deprecated methods and their
replacement methods.
For more information about API information in Support Center, see NX Open Differences between
releases.

Note:
NX development makes every effort to follow the above policies. However, there may be instances
when the policies must be violated due to the type of changes required. When this type of change
is made, it is published on the Changes That May Require Code Changes tab in Support Center.
This includes information on the change that happened and suggests changes that could be made
to the code.
NX maintains and publishes stability metrics that show that for at least the last 10 years the
stability of the NX Open APIs is above 96% for any given release, while the average is above 99%.

Exploring changes to the NX Open API between releases

NX Open changes are published in Support Center. In the NXOpen APIs section for your release, you
can view API changes in the NXOpen APIs What's Changed Reports.

By default, this webpage contains the reports of the current release and the last functional release. In
addition, you can select a release to compare with your release to get a comparison between the two
releases. You can get comparisons for up to two years of releases.

Each page presented provides a point-to-point comparison of the APIs. The What's New tab on the page
presents the new API items added between the two selected releases. The Changes That May Require
Code Changes tab provides information that shows the changes that violate API stability and (or) binary
compatibility, in accordance with the rules specified in the above policies.

For example, removing API items violates our API stability and binary compatibility policy unless the
compiler changes. For each entry, we provide remediation suggestions, if needed, and possibly the
reason for the change. An example of a change for which the only remedy is to recompile, is if a class
has a new base class inserted into it's hierarchy. In this case, you don't need to change your code, but
you do have to recompile your automation code that uses the API. This is contrasted by changes to a
method signature to add an additional parameter. In this case, there will be a description of what the
new parameter's purpose is and how to use it.

Also, the Changes That May Require Code Changes tab lists all of the deprecated APIs, their
replacement APIs, and the earliest that each API could be retired. APIs that are retired are listed on the
tab, along with when the API was removed and their replacement.

Open C API changes are listed in the NX release notes, in the New Open C routines, Obsoleted Open C
routines, and Deleted Open C routines topics.

Function declarations that are newly retired (obsolete/deprecated) are moved to the uf_retiring.h file,
which contains a complete list of Open C functions that could be deleted in the next NX release.

3-88 NX 2007 Release Notes, NX 2007 Series

Release upgrade process for a functional release

For each functional release of NX, you should perform the following steps to migrate your application to
the release:

1. Review the Changes That May Require Code Changes tab for the release you are going from and
upgrading to. This helps you to understand what changes are being made in the release and what
changes are planned for the next release.

2. For any methods or properties that have been deleted and for those which you have not already
replaced in your code, implement the replacement code.

3. Recompile your entire source base using the current compile time files and settings for the given
release.

4. For any methods or properties that produce deprecation warnings, decide if you are going to
replace this code now or in the next release. Implement the replacement code for any deprecated
methods you want to replace now and recompile.

5. Link your application with the appropriate NX Open libraries.

6. Perform a full suite of application testing in a stable NX environment.

7. Distribute your applications to your user base.

Release upgrade process for a monthly release

For each monthly release of NX, you should perform the following steps to migrate your application to
the release:

1. Review any changes for the monthly release in Support Center.

2. Any API changes that may require rework or a recompile of your code will only be made if
absolutely necessary. In this case, you will have to rework or recompile the affected applications,
then test and redistribute. These changes are provided in Support Center.

NX 2007 Release Notes, NX 2007 Series 3-89

Product Notes

Certified compilers and environments to use for NX Open programs

The following table specifies the compiler (or installation for Python) to use for the applicable platform.
These certified compilers are the ones used in testing for a particular release. These are the only ones
certified for use with NX Open:

Windows Linux

C/C++ Visual Studio 2019 Professional gcc 7.3.1

16.0.5
Build 19.20.27508.1

.NET .NET 4.7.2 Framework N/A

Java (64–bit) JDK 1.8.0_45 JDK 1.8.0_45

Python (64–bit) Python 3.8.12 Python 3.8.12

Use of a non-certified compiler

• C++
For Windows, any version of a Visual Studio compiler should work within the release family as long as
the version is equal to or higher than the certified version.
For Linux and gcc versions, any version of gcc should work as long as the version is equal to or higher
than the certified version and in the same release family.
To find the current C++ linker version installed on your system, run link /?. For additional information,
see Signing Process.

• .Net
The .Net framework provided by Microsoft attempts to maximize backward compatibility. The version
used should be equal to or greater than the certified version. Additional information is provided by
Microsoft at Version Compatibility in the .NET Framework.

• Java
Java has historically allowed programs compiled with earlier compiler versions to work with later JRE
versions. This means that users can choose to compile at the certified compiler level and run with a
later JRE version, or choose to compile at a compiler level greater than or equal to the certified
compiler.

• Python
The Python version that NX delivers is built at the certified version for the release. In addition, Python
is binary compatible in a major release family, so for example, if we build and certify against X.Y.4,
our NX Open Python binaries will be binary compatible for all releases in the X.Y series (X.Y.5, X.Y.6,
and so on). But they will not be binary compatible with a different major release family, for example,
the X.Z series (X.Z.3, X.Z.4, and so on).

3-90 NX 2007 Release Notes, NX 2007 Series

Using a non-certified compiler or environment is not without risks, which is assumed by the user. If an
issue arises using a non-certified compiler or environment, Siemens Digital Industries Software can
investigate with the following caveats:

• We need to be able to reproduce the issue easily so we can investigate the problem.

• If the compiler or environment regresses, it is expected that the user will investigate the issue in their
environment to rule out improper usage on their part. For example, it is expected that users will rule
out scenarios where the latest version of the compiler or environment fixes a bug that now catches
something invalid that wasn't caught before in a previous version.

• There exists the possibility that the solution to the issue encountered cannot be realized in the release
reported, but will be deferred to a later release.

Using the SCL compiler on Red Hat Enterprise Linux

To use the SCL compiler gcc 7.3.1 on Red Hat 7.6 or later, add a repository and install the compiler
package:

1. Register the system (required for Red Hat Linux). If you don't register, the following commands will
fail.

2. Install a package with a repository for your system. Run the following to enable the RHSCL
repository:

sudo yum-config-manager –enable rhel-server-rhscl-7-rpms

3. Run the following to install the collection:

sudo yum install devtoolset-7

4. The compiler is installed. However, the default compiler recognized is still the one found by paths
and environment variables. To use your compiler, either invoke a shell or set environment variables.

• Invoke a shell using the SCL compiler:

scl enable devtoolset-7 bash (or ksh)

• Set environment variables:

• INFOPATH /opt/rh/devtoolset-7/root/usr/share/info:$INFOPATH

NX 2007 Release Notes, NX 2007 Series 3-91

• LD_LIBRARY_PATH /opt/rh/devtoolset-7/root/usr/lib64:/opt/rh/devtoolset-7
/root/usr/lib:/opt/rh/devtoolset-7
/root/usr/lib64/dyninst:/opt/rh/devtoolset-7/root/usr/lib/dyninst:/opt/rh/devtoolset-7
/root/usr/lib64:/opt/rh/devtoolset-7/root/usr/lib:$LD_LIBRARY_PATH

• MANPATH /opt/rh/devtoolset-7/root/usr/share/man:$MANPATH

• PATH /opt/rh/devtoolset-7/root/usr/bin:$PATH

Note:
When invoking a shell to use the compiler, it's possible you could have problems when
running Perl scripts. In that case, setting environment variables is the preferred method.

Running Java and .NET programs

To run programs created in NX Open that require Java or .NET, the following is required:

Windows Linux

.NET .NET 4.7.2 Framework N/A

Java (64–bit) JRE 1.8.0_45 or later JRE 1.8.0_45 or later

Note:
• Some standard NX applications, such as translators, require installation of the JRE. For
additional information, see Considerations and caveats.

• If you are running a Siemens product other than NX, you may need to run a different version of
Java according to the requirements for that product.

Internet browsers

If you do not see the latest documentation for the following programming tools, it may be a cache issue.
Try clearing your cache, or using a different browser.

• Open C Reference Guide

• NX Open C++ Reference Guide

• Open for Java

• NX Open Python

• Open for .NET

3-92 NX 2007 Release Notes, NX 2007 Series

In the Open C Reference Guide, if links to the example .c files do not work in IE, the .c file may not have
an associated program to open it. Follow the instructions for your operating system to associate the .c
file to a program, such as Notepad.

Managed C++

Starting in NX 1872, support is dropped for managed extensions for C++ (referred to as managed C++).
In addition, C++/CLI extensions, which superseded managed C++, are also not supported.

Signing applications

An executable for an application created with NX Open must be signed before it can be executed by
anybody who does not have a NX Open Author license. This typically includes the primary users of the
executable, such as the mechanical designers at your site. The signing process is performed with the NX
Open signing utility before the application is distributed to the user base. Starting in NX 2007 for Java jar
files, you can sign the executable using the NX Open signing utility and also have the executable
digitally signed using jarsigner.

Previously, you could not do both as the NX Open signing process was not compatible with digital
signing. Adding digital signing provides an additional level of security and protection especially if the
application is going to other sites.

NX 2007 Release Notes, NX 2007 Series 3-93

NX 2412 Release Notes
No ratings yet
NX 2412 Release Notes
156 pages
NX 2406 Series Release Notes 2406.1700
No ratings yet
NX 2406 Series Release Notes 2406.1700
149 pages
NX 2312 Release Notes
No ratings yet
NX 2312 Release Notes
146 pages
NX 12.0.2 Release Notes: Siemens Siemens Siemens
No ratings yet
NX 12.0.2 Release Notes: Siemens Siemens Siemens
146 pages
NX 12.0.1 Release Notes
No ratings yet
NX 12.0.1 Release Notes
142 pages
Release Notes
No ratings yet
Release Notes
130 pages
NX 2506 Release Notes
No ratings yet
NX 2506 Release Notes
176 pages
Release Notes
No ratings yet
Release Notes
118 pages
NX 2412 Series Release Notes 2412.3000
No ratings yet
NX 2412 Series Release Notes 2412.3000
7 pages
Release Notes
No ratings yet
Release Notes
116 pages
Release Notes
No ratings yet
Release Notes
112 pages
Release Notes
No ratings yet
Release Notes
118 pages
NX10 Release - Notes
No ratings yet
NX10 Release - Notes
114 pages
NX 1926 Series Release Notes 1926
100% (1)
NX 1926 Series Release Notes 1926
106 pages
Edt GD
No ratings yet
Edt GD
346 pages
Nx-10.0.3 Release Notes
No ratings yet
Nx-10.0.3 Release Notes
124 pages
Siemens NX RN 10.03
No ratings yet
Siemens NX RN 10.03
124 pages
Tshell User
No ratings yet
Tshell User
1,008 pages
NX 2406 Series Release Notes 2406.6000
No ratings yet
NX 2406 Series Release Notes 2406.6000
8 pages
Tshell Ijtag User
No ratings yet
Tshell Ijtag User
196 pages
Tshell Mbist User
No ratings yet
Tshell Mbist User
844 pages
NX
No ratings yet
NX
25 pages
SiemensNX-1872 wntx64 Jun2019.README
No ratings yet
SiemensNX-1872 wntx64 Jun2019.README
2 pages
NX 2406 Series Release Notes 2406.8100
No ratings yet
NX 2406 Series Release Notes 2406.8100
8 pages
WinCC-109810917 Unified Beginners Guide en
No ratings yet
WinCC-109810917 Unified Beginners Guide en
50 pages
Cont Int Jenkins DOC V11 en
No ratings yet
Cont Int Jenkins DOC V11 en
23 pages
Classification
No ratings yet
Classification
90 pages
Polarion Widget SDK
No ratings yet
Polarion Widget SDK
21 pages
2008 NX Open Status
No ratings yet
2008 NX Open Status
24 pages
2008 NX Open Status
No ratings yet
2008 NX Open Status
24 pages
Wincc Migrationguide DOC V30
No ratings yet
Wincc Migrationguide DOC V30
31 pages
Nokia Siemens Networks Netact Oss5.4 CD Set 2: Document List
0% (1)
Nokia Siemens Networks Netact Oss5.4 CD Set 2: Document List
16 pages
NX
No ratings yet
NX
28 pages
NX Install WNT
No ratings yet
NX Install WNT
37 pages
Using The Kinematics Toolbox With Sample PLC Programs For Simulation With The NX MCD Player PDF
No ratings yet
Using The Kinematics Toolbox With Sample PLC Programs For Simulation With The NX MCD Player PDF
30 pages
DCC LoadSharing V3 0 en
No ratings yet
DCC LoadSharing V3 0 en
54 pages
LStream DOC v1 6 en
No ratings yet
LStream DOC v1 6 en
24 pages
Unified TipsScripting V30 en
100% (1)
Unified TipsScripting V30 en
80 pages
Standardization Guideline DOC V10 en
No ratings yet
Standardization Guideline DOC V10 en
36 pages
InfoPLC Net 77430539 Wincc Migrationguide DOC V21 en
No ratings yet
InfoPLC Net 77430539 Wincc Migrationguide DOC V21 en
24 pages
PCS7 ServiceBridge DOC en
No ratings yet
PCS7 ServiceBridge DOC en
66 pages
LongTermDataArchives en v20-2
No ratings yet
LongTermDataArchives en v20-2
38 pages
SINAMICS S120 Web Server - User-Defined Sample Pages
No ratings yet
SINAMICS S120 Web Server - User-Defined Sample Pages
33 pages
Install STEP7 WinCC V16 enUS PDF
No ratings yet
Install STEP7 WinCC V16 enUS PDF
84 pages
Install STEP7 WinCC V18 enUS
No ratings yet
Install STEP7 WinCC V18 enUS
124 pages
Wincc Upgrade v6.2 v7.5 en
100% (1)
Wincc Upgrade v6.2 v7.5 en
32 pages
Udp BaseComm V1 en
No ratings yet
Udp BaseComm V1 en
67 pages
Anaheim OMEGAMON SHARE 11792
No ratings yet
Anaheim OMEGAMON SHARE 11792
30 pages
Configuration and Extensibility
No ratings yet
Configuration and Extensibility
456 pages
License en-US
No ratings yet
License en-US
7 pages
SINAMICS S120 Web Server - Creating User-Defined Web Pages
No ratings yet
SINAMICS S120 Web Server - Creating User-Defined Web Pages
87 pages
Checklist SCALANCE IBS V20 en
No ratings yet
Checklist SCALANCE IBS V20 en
32 pages
WinCC Unified VisualStudioCode en
No ratings yet
WinCC Unified VisualStudioCode en
17 pages
SoftwareEngineer NodeJS-Abhinav Gupta
No ratings yet
SoftwareEngineer NodeJS-Abhinav Gupta
2 pages
Null Object Reference Error in Moon Reader
No ratings yet
Null Object Reference Error in Moon Reader
2 pages
Android Developer Profile - IIT Delhi Alum
No ratings yet
Android Developer Profile - IIT Delhi Alum
1 page
A Mobile Greenhouse Environment Monitoring System Based On The Internet of Things
No ratings yet
A Mobile Greenhouse Environment Monitoring System Based On The Internet of Things
60 pages
Chapter - 1 Getting Started With Python
No ratings yet
Chapter - 1 Getting Started With Python
10 pages
Chapter 3 BASIC ELEMENTS OF JAVA
No ratings yet
Chapter 3 BASIC ELEMENTS OF JAVA
21 pages
Java J2ee Objective Type
No ratings yet
Java J2ee Objective Type
3 pages
System Flow Diagram
No ratings yet
System Flow Diagram
25 pages
Java Concepts 5th Edition Cay S. Horstmann - PDF Download (2025)
No ratings yet
Java Concepts 5th Edition Cay S. Horstmann - PDF Download (2025)
55 pages
TCP Multiclient Chat Guide
No ratings yet
TCP Multiclient Chat Guide
22 pages
Karthik Resume
No ratings yet
Karthik Resume
3 pages
Mca 1 Unit Notes JAVA
100% (1)
Mca 1 Unit Notes JAVA
6 pages
TCS Prime Interview Experience
No ratings yet
TCS Prime Interview Experience
15 pages
OOPs Through Java Unit-04 Notes
No ratings yet
OOPs Through Java Unit-04 Notes
9 pages
How To Install JDK 15 and Notepad (On Windows) and Get Started With Java Programming
No ratings yet
How To Install JDK 15 and Notepad (On Windows) and Get Started With Java Programming
24 pages
Java Questions and Joke Answers
No ratings yet
Java Questions and Joke Answers
2 pages
Java Development
No ratings yet
Java Development
12 pages
Topic1 ClassesAndObjects
No ratings yet
Topic1 ClassesAndObjects
27 pages
Discourse Analysis Worksheet
No ratings yet
Discourse Analysis Worksheet
5 pages
Java Questions
No ratings yet
Java Questions
24 pages
Android App Programming Diploma Course
No ratings yet
Android App Programming Diploma Course
7 pages
Pycharm
No ratings yet
Pycharm
79 pages
Hardware Integration Log
No ratings yet
Hardware Integration Log
2,808 pages
SAP PI 7 Monitoring in Single Stack
100% (1)
SAP PI 7 Monitoring in Single Stack
9 pages
PassLeader 1Z0-808 Exam Dumps (1-20)
100% (1)
PassLeader 1Z0-808 Exam Dumps (1-20)
16 pages
Gradle User Guide
No ratings yet
Gradle User Guide
573 pages
Inventory Management Project
No ratings yet
Inventory Management Project
55 pages
MCA BookList - Compressed
No ratings yet
MCA BookList - Compressed
352 pages
Barik Question and Answer
No ratings yet
Barik Question and Answer
12 pages
NetWorker - Updating The NetWorker software-NetWorker 19.5
No ratings yet
NetWorker - Updating The NetWorker software-NetWorker 19.5
41 pages