 Source:

 https://ww3.cad.de/foren/ubb/uploads/Majomouse/Solution_Center.txt



Solution Center
--------------------------------------------------------------------------------
Next Doc
--------------------------------------------------------------------------------

PRODUCT:      NX
SUBJECT: Automatically Correct Split Faces For Holes In NX Importing STEP file.

SUBMITTED BY: MARK WHITWELL             SUBMITTED DATE:   06/10/2011
IR #:         6357351                   DOCUMENT ID:      001-6357351
PLATFORM:     All                       OPERATING SYSTEM: All
OS VERSION:   All                       PRODUCT VERSION:  V3 and later

===============================================================================

HARDWARE/SOFTWARE CONFIGURATION
-------------------------------
All Certified Hardware Platforms.

SYMPTOM/PROBLEM
---------------
Automatically correct split faces such as holes when importing STEP files into
NX.

SOLUTION/WORKAROUND
-------------------
This function will join split faces and automatically make a single face.
It is available in NX3 and later releases of NX.

Edit step214ug.def or step203ug.def file or both files and add this line:

	DO_IMPORT_MERGING_REDUNDANT_TOPOLOGY = On

If the line is added to the end of the file, put a carriage return, by
pressing the Enter key directly after "On", at the end of the line otherwise
the step translator will not read this line.

NX does not need to be restarted, just import in the STEP file and the split
faces will automatically be joined together.

REFERENCES/NOTES
----------------

===============================================================================

COPYRIGHT (C) by Siemens Product Lifecycle Management Software Inc.
ALL RIGHTS RESERVED.  No distribution except provided under contract




--------------------------------------------------------------------------------

Next Doc
--------------------------------------------------------------------------------





Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------

PRODUCT:      NX
SUBJECT: Emplty components after importing STEP

SUBMITTED BY: WOODY KUHN                SUBMITTED DATE:   09/08/2007
IR #:         1614141                   DOCUMENT ID:      001-1614141
PLATFORM:     INTEL                     OPERATING SYSTEM: WINDOW
OS VERSION:   XP32_SP2                  PRODUCT VERSION:  V4.0.4

===============================================================================

HARDWARE/SOFTWARE CONFIGURATION
-------------------------------
NX STEP AP214 and STEP AP203
All Platforms

SYMPTOM/PROBLEM
---------------
Import a STEP assemby and the components are empty.  Are external references
supported in NX?

SOLUTION/WORKAROUND
-------------------
External references are supported in NX 5 and later.  In order to import
external references into NX, the following line has to be added to the
step203ug.def or step214ug.def file:

	OVERWRITE_EXISTING_PARTS = On

(If this line is added to the end of the .def file, a carriage return must be
added to the end of the line.)
REFERENCES/NOTES
----------------

===============================================================================
COPYRIGHT (C) by UGS, Inc.
ALL RIGHTS RESERVED.  No distribution except provided under contract




--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------



Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------


Subject: [PR-05788865] Validation results missing when importng Step from XlatorUI

Description of Problem:
PR Number: 5788865
Priority:  2

Problem Description:
====================

When importing a Step file from the XlatorUI that has mass properties validation, the validation results are not written to the log file. This works correctly if the Step file is imported within a NX session. It was found that the cause of the failure is having the below text in the .def file:

COMPARE_SOLID_IMPORT_MASSPROP_PERCENT_ACCURACY = .9
COMPARE_SOLID_IMPORT_MASSPROP_PERCENT_VOL_ACCEPT_CRITERIA = .1
COMPARE_SOLID_IMPORT_MASSPROP_PERCENT_AREA_ACCEPT_CRITERIA = .1
COMPARE_SOLID_IMPORT_MASSPROP_CG_DISTANCE_MM_ACCEPT_CRITERIA = .1


Please see coordinator note pad for PR file directory path

Step File: test_gvp-7-20-07-export-include-validation-info.stp
Default file: step203ug.def

To Reproduce:
- Start the Step203 translator via the XlatorUI and use the provided files
  No validation results in the log file.


- Start a session of NX and use File-> Import-> Step203 and import using the provided files. The log file will have the validation results

Problem is part specific:        No

Platform Information-
  Problem is platform specific: Unknown
  Problem occurs on the following platforms and versions:
WXP-SP2, NX 4.0.4.2, NX 5.0.1.4
Not tested on other platforms.




PR Number  : 5788865
Date Opened: 23-jul-2007
Status     : NE
Priority   : 2
Family     : NX
Application: TRANSLATOR
Function   : STEP_AP203
Category   : SOLID
Release    : V4.0.2
Platform   : INTEL
OS         : WINDOW
OS Version : XP32_SP2
Terminal   : OTHER
Platform specific: Undetermined

-- End of document --

--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------



Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------


Subject: [PR-01583652] Add 'Flatten Assembly' option to STEP import GUI.

Description of Problem:

Customer Observations --

Step 203 Assembly Import to TC through NX problem.
Customer wants to import a step assy to TC.
Procedure:
- start TC
- Start NX from TC
- create new part
- import step203
- select the step-assy from OS-location
- import result is one solid body


If you use native NX and select the external step203 translator, you would find a advanced setting called "flatten assembly" (see stepImport_external.bmp) which will create for each single part in the step-assy a single solidbody in the NX part.

But this setting is not available when you do the translation with an import in NX (see stepImport_nx_1.bmp and stepImport_nx_2.bmp).

If you use the IGES import you will find this setting (see igesImport.bmp).

We have found a workaround to edit the step203ug.def and change the setting for "ASSEMBLY_MAP = Off" to ON.
This workaround is not usable for the customer.

Customer would like to have this "flatten assembly" setting available in the step import dialog.


GTAC Observations --


The 'Flatten Assembly' option is available as an Advanced Setting in the xlatorui but not from the GUI. This is true in NX4.0.3 and NX5.0.

PR Matrix: 8b, Priority 3

PR Data --

See Coordinator Notepad


PR Number  : 1583652
Date Opened: 22-mar-2007
Status     : O
Priority   : 3
Family     : NX
Application: TRANSLATOR
Function   : USER_INTERFACE
Category   : SOFTWARE
Release    : V4.0.3
Platform   : INTEL
OS         : WINDOW
OS Version : XP32_SP2
Terminal   : OTHER
Platform specific: Undetermined

-- End of document --

--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------



Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------


Subject: [PR-05659237] Assembly map fails to clean up JT/CGM for merged components.

Description of Problem:


If the Customer Defaults are set to create JT files for saved NX parts, and the 'step203ug.def' file has "ASSEMBLY_MAP = On", the JT files which were created for the component parts are not deleted along with the component parts and a part of the import process.

This has an impact for Teamcenter Engineering users when importing the NX part by creating unnessary named references for the Item Revsion. This also impacts native NX users by leaving unneeded data on the file system.

Step to duplicate:


1. In the native NX4 session, go to 'File-> Utilities-> Customer Defaults-> Assemblies-> Site Standards-> Misc' and turn on 'Save JT Data'.

2. Re-start the NX session.

3. Create a new Inch part.


4. Import the supplied STEP file to the workpart using the supplied settings file (flattens the assy on STEP import).

5. Observe that the JT files created from the component parts remain behind while the component parts were deleted after the assembly was flattened.

The STEP translator should delete the JT files when deleting the component parts.


PR Data --

Internally generated data
See Coordinator Notepad


.
PR Number  : 5659237
Date Opened: 14-dec-2006
Status     : O
Priority   : 3
Family     : NX
Application: TRANSLATOR
Function   : STEP_AP203
Category   : ASSEMBLY
Release    : V4.0.3.3
Platform   : INTEL
OS         : WNT
OS Version : 4.0_SP4
Terminal   : OTHER
Platform specific: Undetermined

-- End of document --

--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------





Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------

PRODUCT:      NX
SUBJECT: STEP import is bringing in data from the wrong file

SUBMITTED BY: KEITH POWELL              SUBMITTED DATE:   07/13/2005
IR #:         5223737                   DOCUMENT ID:      001-5223737
PLATFORM:     INTEL                     OPERATING SYSTEM: WINDOW
OS VERSION:   XP32_SP2                  PRODUCT VERSION:  V3.0.2

===============================================================================

HARDWARE/SOFTWARE CONFIGURATION
-------------------------------
NX IGES and STEP
All Releases
Windows Platform

SYMPTOM/PROBLEM
---------------
Using 'File-> Open-> STEP' always imports a STEP file (the same file every
time) other than the file selected for import.


SOLUTION/WORKAROUND
-------------------
Check the settings file from the installation (%STEP203UG_DIR%\step203ug.def)
to see if the recurring file name appears as a value with the
'PROCESS_PARTS_LIST =' variable. There should be nothing following the equal
sign (=).

If the settings file from the installation is okay, search the system for
other occurrences of the step203ug.def file. If found, either rename or remove
these files from the system.

REFERENCES/NOTES
----------------
Extra occurrences of settings files are created in the course of a previous
STEP
imports where modified settings necessitate saving a settings file. In this
situation, an extra occurrence of a STEP import settings file in the user's
PATH
included the name of the STEP file which was repeatedly processed.

RECOMMENDED PRACTICE: Override the default File Name value using smart names
when saving settings files. A smart name would characterize the nature of the
modified settings or purpose (customer-specific, etc.). Aside from avoiding a
problem where an import produces unexpected results, smart names facilitates
reusing the settings in future imports.

===============================================================================
COPYRIGHT (C) by UGS, Inc.
ALL RIGHTS RESERVED.  No distribution except provided under contract




--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------





Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------


Subject: [PR-04710828] Unrecoverable error importing STEP

Description of Problem:
Test Data -- /parts/noexport/step/pr4710828/pr4710828.zip


Windows XP, SP1 plus Hot Fix for 3 GB option.
3 GB RAM, 4 GB Swap
NX 1.0.1.2 and V18.0.5.2


When using the XUI to import some large STEP files from Pro/E there is a "948 -- unrecoverable runtime error" encountered. The customer received a batch of several files. The smaller files in the set imported successfully, but the larger ones encounter the error.

   ***  Date & Time: 07-feb-2003 07:06:55  User id: powellk  ***



Tested in NX 1.0.2.1 on Windows and the conversion failed with a signal 11 in the syslog file. This followed a series of IP ifail in the FACE_REPAIR and EDGE_REPAIR routines.

   ***  Date & Time: 11-feb-2003 09:44:46  User id: powellk  ***

The following received from Development --

He could try adding the following to the step203ug.def file:

CALL_PK_FACE_MAKE_VALID_FACES =  off

This turns off self-intersection fixup which appears to be where things go haywire.

Based on my testing I was able to get a solid.


I'll have to spend more time on it to try and get the problems resolved in the self-intersection fixup code and the crash farther downstream. Being such a big file (long translation time) it's going to take me a while to make any more progress on this.

The data in this STEP file has a lot of self-intersection and tolerance issues. The self-intersections are a known possible problem with some ProE files which might be improved by the ProE user doing a "regen" on the ProE model and then fixing (remodeling) the problem/suspect areas identified by the "regen".

***** <<<<< This PR has been closed.  The resolution was: >>>>> *****

DO NOT ISSUE A CUSTOMER LETTER FOR THIS PR CLOSURE. Closed without a fix due to its age and our internal assessment of its priority.

PR Number  : 4710828
Date Opened: 11-feb-2003
Status     : NF
Priority   : 2
Family     : UNIGRAPHICS_NX
Application: TRANSLATOR
Function   : STEP_AP214
Category   : SOFTWARE
Release    : V1.0.3
Platform   : INTEL
OS         : WINDOW
OS Version : XP32_SP1
Terminal   : OTHER
Platform specific: Specific

-- End of document --

--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------




Solution Center
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


Subject: [PR-01374261] Documentation needed for igesexport.def,step203ug.def,step214ug.def

Description of Problem:


I need to batch export UG files from TCE in IGES and STEP format.


I need more information on all available parameters for igesexport.def,step203ug.def,step214ug.def (do exists additional parameters not included in the standard .def files?).

I need to know if it's possible to specify Ug/Manager Load Options through .def file (e.g: Latest Working, Any Status; Working, ...)

I also need informations on error handling.

I already searched in GTAC and GTAC newsletters but I didn't find any exhaustive explanation.


PR Number  : 1374261
Date Opened: 27-dec-2004
Status     : DO
Priority   : 2
Family     : UNIGRAPHICS_NX
Application: TRANSLATOR
Function   : IGES
Category   : DOCUMENTATION
Release    : V2.0.4
Platform   : all
OS         : N/A
OS Version : N/A
Terminal   : N/A
Platform specific: Specific

-- End of document --

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------



 Newsgroup:nx.translators
 Subject:Re: How to control which "Load_options.def" is used ?
 From:"Tomas Osterman"
 Date:9 Mar 2006 04:45:15 -0800
 Message-ID:news://4410235b$1@bbsnotes.ugs.com


Thanks guys,
I am sure it will fix my problem.
I have missed the existence of this variable


Little follow up question though,
- will adding the variable to the ugstep203.def affect both the "internal" as well
as the "external" translator ? ( will it work for both of them ?)

Regards,
 Tomas



"Keith Powell" <keith.powell@ugs.com> wrote:
>
>Steve Vickers is right on the money about using the UGII_LOAD_OPTIONS variable
>to
>"control" assembly loading behavior in the NX translators. You can define
>the variable
>at the system level, but keep in mind that this will also affect your NX sessions.
>
>Here's a little trick which you might find useful, you can also add the UGII_LOAD_OPTIONS
>keyword to the ugstep203.def settings file and achieve the same results. Here's
>an excerpt from the settings file used in a test I have just run:
>
>UGI_PROC_ASSEM = Use load_options.def options
>UGI_COMP_FAIL = Abort if Load Fails
>UGI_LOAD_COMP = Load Components
>UGI_LOAD_VER = Load Exact Version
>UGI_COMP_SUB = Do not Allow Substitution
>UGI_LOAD_OPTION = Load From Assem Dir
>UGI_SEARCH_DIRS =
>UGII_LOAD_OPTIONS = P:\powellk\parts\load_options.def
>
>
>Keith Powell
>GTAC Product Support


          <<>>



--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------



Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------




 Newsgroup:nx.translators
 Subject:Re: Base part Step import NX6
 From:sburger
 Date:Wed, 2 Jun 2010 02:50:19 -0700
 Message-ID:news://sburger.4bxb9n@noreply.bbsnotes.ugs.com


Hello

You can set in the customer defaults under Gateway/Translators/Step214
the step214ug.def setting file to a central def file
and in the def file ist the Path to the step214ugnullnx60_mm.prt
defined

The only problem is if you convert with the external translator which
reads only the def File From Lokal Base Dir....


--
sburger

Samuel Burger

Systemmanager CAD
Windows XP Pro x64 SP2 (x86 SP3)
NX6.0.5 MP.., TcEng 2005 SR1 MP8.3
xw6x00, Z-600
2-8 GB RAM, nVIDIA Quadro FX 34x0/1700
------------------------------------------------------------------------
sburger's Profile: http://bbsnotes.ugs.com/vbulletin/member.php?userid=225605
View this thread: http://bbsnotes.ugs.com/vbulletin/showthread.php?t=42472


          <<>>



--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------



Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------

PRODUCT:      NX
SUBJECT: Customer Needs to Maintain the B-Surfaces on Import

SUBMITTED BY: WOODY KUHN                SUBMITTED DATE:   10/29/2008
IR #:         1691600                   DOCUMENT ID:      001-1691600
PLATFORM:     INTEL                     OPERATING SYSTEM: WINDOW
OS VERSION:   XP32_SP3                  PRODUCT VERSION:  V4.0.4

===============================================================================

HARDWARE/SOFTWARE CONFIGURATION
-------------------------------

Family: NX
Application: TRANSLATOR
Function: STEP_AP214
Subfunction:

SYMPTOM/PROBLEM
---------------
Is there a way to import b-surfaces in a step file into b-surfaces in NX
instead of analytic surfaces?


SOLUTION/WORKAROUND
-------------------
To keep b-surfaces in the step file from being simplified into analytic
surfaces when imported into NX, add the following two lines to
%UGII_BASE_DIR%\step214ug\step214ug.def.

DO_IMPORT_BSPLINE_SIMPLIFICATION_BEFORE_OR_AFTER_FAULT_FIXUP = Off

BSURFACE_MAP = Off


REFERENCES/NOTES
----------------

===============================================================================
COPYRIGHT (C) by Siemens Product Lifecycle Management Software Inc.
ALL RIGHTS RESERVED.  No distribution except provided under contract




--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------




Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------

PRODUCT:      NX
SUBJECT: Emplty components after importing STEP

SUBMITTED BY: WOODY KUHN                SUBMITTED DATE:   09/08/2007
IR #:         1614141                   DOCUMENT ID:      001-1614141
PLATFORM:     INTEL                     OPERATING SYSTEM: WINDOW
OS VERSION:   XP32_SP2                  PRODUCT VERSION:  V4.0.4

===============================================================================

HARDWARE/SOFTWARE CONFIGURATION
-------------------------------
NX STEP AP214 and STEP AP203
All Platforms

SYMPTOM/PROBLEM
---------------
Import a STEP assemby and the components are empty.  Are external references
supported in NX?

SOLUTION/WORKAROUND
-------------------
External references are supported in NX 5 and later.  In order to import
external references into NX, the following line has to be added to the
step203ug.def or step214ug.def file:

	OVERWRITE_EXISTING_PARTS = On

(If this line is added to the end of the .def file, a carriage return must be
added to the end of the line.)
REFERENCES/NOTES
----------------

===============================================================================
COPYRIGHT (C) by UGS, Inc.
ALL RIGHTS RESERVED.  No distribution except provided under contract




--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------

 Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------


Subject: [PR-01590166] Imported model has still gaps

Description of Problem:

Imported the step file and it imports as a solid body.  When shaded, some of the faces are missing.



There appears to be a problem with the b-spline degeneracy fixup when importing this step file. Tured off the b-spline degeneracy fixup by adding the following line in the step214ug.def file and then the step file imported the solid without any faults and all the faces display when shaded.

The line to add to is:

	BSPLINE_IMPORT_DEGEN_FIXUP = Off


If this line is added to the end of the step214ug.def file, make sure that there is a carriage return at the end of the line.

This is a workaround but the customer would like a fix in a future release of NX 4.
PR Number  : 1590166
Date Opened: 04-may-2007
Status     : O
Priority   : 2
Family     : NX
Application: TRANSLATOR
Function   : STEP_AP214
Category   : SURFACE
Release    : V4.0.3
Platform   : INTEL
OS         : WINDOW
OS Version : XP32_SP1
Terminal   : OTHER
Platform specific: Undetermined

-- End of document --

--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------




Solution Center
--------------------------------------------------------------------------------
Previous Doc   Next Doc
--------------------------------------------------------------------------------

PRODUCT:      UG
SUBJECT: Bodies suspected to be corrupt after STEP import

SUBMITTED BY: KEITH POWELL              SUBMITTED DATE:   10/18/2001
IR #:         N/A                       DOCUMENT ID:      002-0002356
PLATFORM:     All                       OPERATING SYSTEM: All
OS VERSION:   All                       PRODUCT VERSION:  V18.0

===============================================================================

HARDWARE/SOFTWARE CONFIGURATION
-------------------------------
-

SYMPTOM/PROBLEM
---------------
The problem is that after the STEP214 import, go to Modeling->(Shade the part)
and the error occurs 'One or more bodies in this model are suspected to be
corrupt'

SOLUTION/WORKAROUND
-------------------
The problem where shading fails on the UG part generated from translating the
STEP file is fixed in v18.0.0.16.

The fix/workaround is to use either of 2 undocumented .def file options which
are new in v18.  Insert either of the following in the .def file being used for
the STEP214UG translator import translation:

    SMOOTH_BSURFS = Off
    DO_IMPORT_MERGING_REDUNDANT_TOPOLOGY = Off

The recommendation is to use DO_IMPORT_MERGING_REDUNDANT_TOPOLOGY = Off

These undocumented step214ug.def file options are not available in v17.

REFERENCES/NOTES
----------------

===============================================================================

COPYRIGHT (C) by UGS, Inc.
ALL RIGHTS RESERVED.  No distribution except provided under contract




--------------------------------------------------------------------------------

Previous Doc   Next Doc
--------------------------------------------------------------------------------

