Showing results for 
Search instead for 
Do you mean 
Reply

File Open templates for CAD exchange formats using NX10 Custom

Hello All, 

 

We have many users that use the File>Open method when dealing with CAD exchange formats(.igs,.stp.dwg,etc..) instead of importing into a File>New template. I know I can copy a custom template to the OOTB location and change the name, but I would like to know how I can point to the custom templates for this function instead modifying everyone install. 

 

Can you set an enviromant variable? Or something else?

 

Thanks in advance for any input,

Ron

10.0.3.5

Windows 7

3 REPLIES

Re: File Open templates for CAD exchange formats using NX10 Custom

The DEF file contains variables for the BASE files, some DEF files don't list them, but they are supported by all translators.

Best would be to copy the translator folders to the NX_Custom folder structure and point the translator environment variables in ugii_env.dat to these folders.

If you do that, you should block the usage of the external translators, since they don't use the settings from ugii_env.dat.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community

Re: File Open templates for CAD exchange formats using NX10 Custom

[ Edited ]

It would be nice if Siemens put all the translator files in one location, in the install directories.

 

This should work for a STEP assembly, that is imported into a TC managed session, in that the components created, would use the company seed file, correct?

 

FYI, I think I have all the variables here:

####  TRANSLATORS  ####
#
#  Directory containing the AP203 STEP executables.
STEP203UG_DIR=${NX_CUSTOM_LIB}\Translators\step203ug\
#
#  Directory containing the AP214 STEP executables.
STEP214UG_DIR=${NX_CUSTOM_LIB}\Translators\step214ug\
#
#  Directory containing the AP242 STEP executables.
STEP242_DIR=${NX_CUSTOM_LIB}\Translators\step242\
#
#  Directory containing the DXFDWG executables.
DXFDWG_DIR=${NX_CUSTOM_LIB}\Translators\dxfdwg\
#
#  Directory containing the IGES executables.
IGES_DIR=${NX_CUSTOM_LIB}\Translators\iges\
#
#  Directory containing the UGTO2D executables.
UGTO2D_DIR=${NX_CUSTOM_LIB}\Translators\ugto2d\
#
#  If the following flag is set, surfaces that are sent from ICAD
#  to Unigraphics will not broken up into multiple faces
#UGII_ICADIF_SURF_CLEANUP=true
#
# Directory that contains the DLL's that run the Parasolid CATIA translator
UGII_CATIA_DIR=${NX_CUSTOM_LIB}\Translators\ugcatia\
#
# Directory that contains the DLL's that run the NX_CATIAV5 translator
UGII_CATIAV5_DIR=${NX_CUSTOM_LIB}\Translators\catiav5\
#
# Directory that contains the DLL's that run the Parasolid PROE translator
UGII_NXPROE_DIR=${NX_CUSTOM_LIB}\Translators\nxproe\
#
# Directory that contains the DLLs that run the ACIS translator.
UGII_NXACIS_DIR=${NX_CUSTOM_LIB}\Translators\nxacis\
#
# Schema directory used by SolidWorks loading code
UGII_SW_SCHEMA=${UGII_BASE_DIR}\ugii
#
# Library used by SolidWorks loading code
UGII_SW_LIBRARY=CrossCadWareX64.dll
#
####  END OF TRANSLATOR INFO  #####

 

-Dave
NX 11 | Teamcenter 11 | Windows 8.1

Re: File Open templates for CAD exchange formats using NX10 Custom

[ Edited ]

Some of the DEF files of the translators contain the following variables:

BASE_PART_MM
BASE_PART_IN

These are pointing to the seed files used for translation and can be added to all the DEF files of all translators, that I have used so far.

The problem is that translators can be launch in multiple ways and each is doing this differently.

  • File => Open
  • File => Import
  • external translator
  • command line

From within NX the ugii_env.dat file entries are used.

The external translators use the settings from their starting folder.

The command line uses what ever you submit as an argument.

One folder containing all translators would just make a mess out of everything, so not a solution in my opinion.

If everything would use ugii_env.dat, then there would at least be a single point for the initial configuration.

You could then select the DEF file of your choice from the settings dialog of the external translators or add it as an argument for the command line execution, but you would always start with a defined set of settings.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community