Академический Документы
Профессиональный Документы
Культура Документы
Guide
© 2015 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited.
ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS, AIM
and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarks
or trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademark
used by ANSYS, Inc. under license. CFX is a trademark of Sony Corporation in Japan. All other brand, product,
service and feature names or trademarks are the property of their respective owners.
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-
ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products
and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement
that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting
laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products
and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions
of that software license agreement.
For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).
Third-Party Software
See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, please contact ANSYS, Inc.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
iv of ANSYS, Inc. and its subsidiaries and affiliates.
List of Figures
2.1. ANSYS Connection for ACIS Dialog .......................................................................................................... 5
2.2. ANSYS Connection for CATIA Dialog ........................................................................................................ 7
2.3. ANSYS Connection for CATIA Version 5 Dialog ......................................................................................... 8
2.4. ANSYS Connection for Creo Parametric (formerly Pro/ENGINEER) Dialog .................................................. 9
2.5. ANSYS Connection for NX Dialog ........................................................................................................... 11
2.6. ANSYS Connection for Parasolid Dialog ................................................................................................. 13
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
vi of ANSYS, Inc. and its subsidiaries and affiliates.
List of Tables
1.1. CAD Package and Recommended Connection Functionality .................................................................... 1
3.1. ANSYS Default Configuration Settings ................................................................................................... 19
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. vii
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
viii of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Introduction to the Connection Functionality
The connection functionality provides you with a means to import CAD geometries into ANSYS. The
connection functionality can import geometries for the CAD/CAE file formats listed below. You must
have the appropriate Geometry Interface license to use the connection functionality.
• CATIA V5–6R2014
• CATIA V4.2 (separate geometry interface licenses must be used for CATIA V5 and CATIA V4)
• Parasolid 26.0
• Creo Parametric WIldfire 5.0, Creo Parametric 2.0 and Creo Parametric 3.0
• ACIS 25
Note
The connection functionality generally supports prior releases of CAD files (such as ACIS
18.0); however, due to changes in the CATIA product, support is not available between CATIA
5.x and prior CATIA releases.
Table 1.1 provides a list of CAD packages, their file type, and the recommended connection functionality
to use when importing files.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
Introduction to the Connection Functionality
• Before starting any connection task, ANSYS 16.2 must be installed and configured on the target system.
• As applicable, Creo Parametric (formerly Pro/ENGINEER) must be installed on your machine for proper con-
nection operation.
• For ACIS, Parasolid, and CATIA, the connection functionality does not require any additional CAD product
licenses.
Note
You cannot enter multiple files with an individual command; you must use a separate com-
mand line for each file. For example:
/INPUT part1.anf
/INPUT part2.anf
/INPUT part3.anf
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Getting Started: Import a CAD File
ANSYS displays the following message after you import the second file (and any subsequent files):
You have already entered the input file utility (AUX15)
The number of files that you can add to create a single database depends on the memory configuration
of your machine.
ANSYS automatically increments the entity numbers of the objects (keypoints, lines, areas, and volumes)
in the subsequent .anf files by the highest object in the previous .anf files. This prevents object
numbers from being duplicated in the final database.
For example, you could have numbered lines and areas in part1.anf and part2.anf like this:
When you put both into a new ANSYS database, the object numbers are automatically updated like
this:
Lines Areas
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 1, 2, 3, 4, 5, 6
This combination scheme can produce some object number gaps in the new database.
• At least one connection. If you have any questions about a connection's availability on your system,
talk to your system administrator or refer to the appropriate installation guide.
2. Start ANSYS.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
Introduction to the Connection Functionality
Import procedures specific to a CAD package are covered in the Importing Parts and Models section of
this document.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Importing Parts and Models
This section further defines the steps to import parts or assemblies with connection functionality. Select
the appropriate CAD product heading to examine the import procedure for:
2.1. ACIS
2.2. CATIA V4
2.3. CATIA V5
2.4. Creo Parametric (formerly Pro/ENGINEER)
2.5. UG/NX
2.6. Parasolid
2.1. ACIS
The connection products support the import of multiple .anf files for the creation of a single ANSYS
database. You can import ACIS-based .sat or .sab files that make up an assembly, save them as
.anf files, and then compile them into one database. See Importing Multiple Files (Create ANSYS
Database) (p. 2) for more information on working with multiple .anf files.
You can import ACIS files using the GUI or by using the ~SATIN command.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
Importing Parts and Models
2. Select the desired file. In addition to the file name, location and type options, modify the following values
as necessary.
• Allow Defeaturing - Select this button to store the model in the solid database format so that it can be
defeatured after import. The default is to store the model in neutral database format, which restricts
defeaturing after import.
– All - Import all entities; use this when the file contains multiple entity types.
3. Click OK.
Note
If your imported model contains multiple volumes, Boolean operators are available to further
process your geometry (see Sculpting Your Model with Boolean Operations in the Modeling
and Meshing Guide for more information).
Command Syntax
~SATIN,Name,Extension,Path,Entity,FMT,NOCL,NOAN
Troubleshooting
For general troubleshooting information, please see Troubleshooting Connection Issues, or examine
Problems Specific to the Connection for ACIS for specific issues.
2.2. CATIA V4
The connection for CATIA supports models created with CATIA Version 4.x or lower. If you are using
CATIA Version 5, see CATIA V5.
Before you start ANSYS, the file (.model, .exp, .session, or .dlv) you wish to import must exist
on your machine or on a known network location.
You can use the ANSYS GUI or the ~CATIAIN command to initiate the import.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
6 of ANSYS, Inc. and its subsidiaries and affiliates.
CATIA V5
2. Choose the appropriate file. If necessary, select the Import blanked bodies check box to allow suppressed
CATIA data to be imported.
3. Click OK.
Once the geometry is imported, follow standard ANSYS analysis procedures; the Basic Analysis Guide
has many examples. If your imported model contains multiple volumes, Boolean operators are available
to further process your geometry (refer to Sculpting Your Model with Boolean Operations in the Modeling
and Meshing Guide for more information).
Note
Only surface and volume models are imported. Wireframe models are not supported and
will be filtered out.
Command Syntax:
~CATIAIN,Name,Extension,Path,- -,- -,BLANK,- -
2.3. CATIA V5
The connection for CATIA Version 5 can import model part or assembly files created with CATIA
V5–6R2013. Supported geometry files have the .CATPart or .CATProduct file extension.
Before starting ANSYS, the file (.CATPart or .CATProduct) you wish to import must exist on your
machine or on a known network location. You can use the ANSYS GUI or the ~CAT5IN command to
import the file.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
Importing Parts and Models
2. Click the Browse button and navigate to the appropriate directory location of the part.
• Select Allow model defeaturing option to store the model in the solid database format so that it can
be defeatured following import. If this option is not checked, the model is stored in a neutral database
format, that restricts defeaturing following import. This is the default setting.
• Select the Geometry type drop-down menu to filter the type of geometry contained in the CATIA version
5 file. Selections include:
– All - Import all entities; use this option when the file contains multiple entity types.
Note
Only surface and volume models are imported. Wireframe models are not supported and
will be filtered out.
If your imported model contains multiple volumes, Boolean operators are available to further
process your geometry (see Sculpting Your Model with Boolean Operations in the Modeling
and Meshing Guide for more information).
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
8 of ANSYS, Inc. and its subsidiaries and affiliates.
Creo Parametric (formerly Pro/ENGINEER)
Command Syntax:
~CAT5IN,Name,Extension,Path,Entity,FMT,NOCL,NOAN
Note
If you specify defeaturing (FMT = 1), this command should be the last line of any script or
file input.
You can use the ANSYS GUI or the ~PROEIN command to import the file.
Note
When importing Creo Parametric parts and assemblies, the connection for Creo Parametric
will always import the version with the highest number (.asm.N) extension, if a number is
the final extension.
Figure 2.4: ANSYS Connection for Creo Parametric (formerly Pro/ENGINEER) Dialog
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 9
Importing Parts and Models
2. Select the desired Creo Parametric file. As necessary, modify the values of the following dialog box options:
• Start Command - Specify the command that launches Creo Parametric on your system. This field defaults
to the value specified during the installation process or using the CAD Configuration Manager. If no
command was specified, the default is proe1 (or Parametric1). The Creo Parametric command name
is set by the PROE_START_CMD162 environment variable.
• Allow Defeaturing - This option is no longer available. The model will always be stored in a neutral
database format which restricts defeaturing after import.
3. Click OK.
Remember that the geometry is always imported to ANSYS using the default ANSYS coordinate system
(CSYS,0), Global Cartesian.
Command Syntax:
~PROEIN,Name,Extension,Path,Proecomm
Troubleshooting
For general troubleshooting information, please see Appendix B, Troubleshooting Connection Issues,
or Problems Specific to the Connection for Creo Parametric for specific issues.
2.5. UG/NX
These procedures assume that you are running NX 8.5, 9.0, or 10.0 and ANSYS 16.2. In addition, the
part file you want to import must be created using NX.
When initiating a part file import, you can select the layers and entities to import, and can specify
whether the part file is to be defeatured after import. You can use the ANSYS GUI or the ~UGIN com-
mand.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
10 of ANSYS, Inc. and its subsidiaries and affiliates.
UG/NX
2. Select the desired UG/NX file. In addition to the file name, file location and file type options, you can
modify the following values as necessary.
• Use selected layers only - Import specific layers of the NX part by checking the Use selected
layers only button and by entering the layer numbers to be imported in the field beside it. You
can specify one layer (for example, 5) or a range of layers (for example, 7-20). The default is to
import all layers (1-256).
• Allow Defeaturing - Select this button to store the model in the solid database format so that
it can be defeatured after import. The default is to store the model in neutral database format,
which restricts defeaturing after import.
– All - Import all entities; use this when the file contains multiple entity types.
3. Press OK.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 11
Importing Parts and Models
Command Syntax
~UGIN,Name,Extension,Path,Entity,LAYER,FMT
Troubleshooting
For general troubleshooting information, please see Troubleshooting Connection Issues, or examine
Problems Specific to the Connection for NX for specific issues.
• partname.tbl
• partname.attr
The partname.tbl file is the NX-to-ANSYS correspondence table file, which relates NX item names
to ANSYS IDs and types.
.
.
.
! Part : square_cube
! Units : Inches
! Selected Layers : 1-256
! Geometry Type : Solids Only
!
! Translator Working Tolerance: 5.0000000E-004
! Part system Tolerance (ref): 1.0000000E-003
!
!Object Name ANSYS Type ANSYS ID
NS_SIDE_FACE AREA 4
NS_PEG_FACE AREA 15
The NX attribute name appears in the first column, the ANSYS entity type appears in the second, and
the ANSYS ID appears in the third.
The partname.attr file is the NX-to-ANSYS attribute file, which lists the object attributes that are
applied in NX and that are for use in ANSYS. These attributes may be used to add mesh control inform-
ation, load and boundary condition information, or material or element property information.
.
.
.
!
! Part : square_cube
! Units : Inches
! Selected Layers : 1-256
! Geometry Type : Solids Only
!
! Translator Working Tolerance: 5.0000000E-004
! Part system Tolerance (ref): 1.0000000E-003
!
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
12 of ANSYS, Inc. and its subsidiaries and affiliates.
Parasolid
Note
Both of the following variables must be set to import a part. Check to see what variables
have been set for your platform, and if necessary, set these variables as indicated below.
UGII_BASE_DIR
Sets the location of the NX files; set by the NX installation. A typical value for this variable is C:\Program
Files\Siemens\NX 8.5.
UGII_ROOT_DIR
Sets the location of the NX executable; set by the NX installation. A typical value for this variable is
C:\Program Files\Siemens\NX 8.5\UGII\.
2.6. Parasolid
2.6.1. Importing a Parasolid File
Before you start ANSYS, the Parasolid file (.x_t or .xmt_txt) you wish to import must exist on your
machine or on a known network location. You can use the ANSYS GUI or the ~PARAIN command to
import the file.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 13
Importing Parts and Models
2. Select the desired Parasolid file. In addition to the file name, file location and file type options, modify the
following values as necessary.
• Allow Defeaturing - Check this box to store the model in the solid database format so it can be defeatured
after import. If this is not checked, the model is stored in neutral database format, which restricts defea-
turing after import (default).
• Allow Scaling - Check this box to permit scaling of the model (if warranted by the model size).
– All Entities - Import all entities; use this option when the file contains multiple entity types.
Note
If your imported model contains multiple volumes, Boolean operators are available to further
process your geometry (see Sculpting Your Model with Boolean Operations in the Modeling
and Meshing Guide for more information).
Command(s) Syntax:
~PARAIN,Name,Extension,Path,Entity,FMT,Scale
Troubleshooting
For general troubleshooting information, please see Troubleshooting Connection Issues, or examine
Problems Specific to the Connection for Parasolid for specific issues. In addition, please refer to the
Parasolid Specific Attributes section for additional information about specific considerations associated
with importing Parasolid files.
However, models must be saved in the text Parasolid format. The saved model files must have either
the *.x_t or *.xmt_txt extension.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
14 of ANSYS, Inc. and its subsidiaries and affiliates.
Parasolid
Scaling
When a Parasolid model is created, the measurement unit information is always represented by meters
regardless of the units used to create the model. However, when the CAD package writes out the file,
the measurement unit information is not included. The absolute numbers in the Parasolid file can differ
from those represented in the ANSYS model.
When ANSYS reads a Parasolid file, the dimensions can be so small that ANSYS must apply a scale factor
to improve the success of the transfer. ANSYS uses a scale factor of 10 or 100, depending on the original
model size. ANSYS displays the scale factor used in the output window.
Assemblies
You can directly import Parasolid assemblies into ANSYS using the connection for Parasolid. After you
import an assembly, you will have as many volumes in ANSYS as you had parts in the assembly. You
must then do the following to build a contiguous model:
2. Glue dissimilar meshes together by generating constraint equations at the interfaces using the CEINTF
command. You should only use this method for models with small deflection.
3. Define bonded contact elements such as CONTA171 to glue dissimilar meshes together.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 15
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
16 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 3: Starting ANSYS from Creo Parametric
The connection functionality allows you to launch ANSYS from within the Creo Parametric (formerly
Pro/ENGINEER) package on Windows.
All Creo Parametric users must have copies of the WBPlugInPE.dat file and the config.anscon.162
files. The config.anscon.162 file is placed in the ANSYS 16.2 installation directory. The WBPlugIn-
PE.dat file is also placed in the ANSYS installation directory, usually located in <drive>\Program
Files\ANSYS Inc\v160\aisol\CADIntegration\ProE\ProEPages\config. This file defines the name of the
executable, the path to the executable, the path to the message file, and the current revision of Creo
Parametric.
For more information about the files used, see the ANSYS, Inc. Windows Installation Guide.
1. Choose File> Open from the Creo Parametric Menu Manager. The File Open dialog box appears.
2. Select the part you wish to open from the appropriate folder.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 17
Starting ANSYS from Creo Parametric
4. Select ANSYSGeom from the ANSYS 16.2 menu (part of the Tools menu in Creo Parametric). The Creo
Parametric part is converted into an ANSYS model database. If you encounter difficulties or the model does
not display, please refer to the Troubleshooting an Imported File section listed below.
Note
5. Analyze the part with ANSYS. If you have any questions about running an ANSYS analysis, see the Basic
Analysis Guide.
• Note for Windows Users: An additional window may open when the connection to ANSYS is launched.
The window title bar contains the full path to the connection executable; the executable is named
ac4pro.exe (ac4pro_wf5.exe for Wildfire 5.0). After the message Releasing Connection
license... appears in the window, close the window. These messages are caused by Creo Parametric and
have no impact on your process.
• If the ANSYS options do not appear, theWBPlugInPE.dat file may not be properly installed. Based upon
your platform, please refer to Windows System Configuration for Connection Functionality for Creo Paramet-
ric (p. 17) for additional information about installingtheWBPlugInPE.dat file.
• Note for Creo Parametric 2.0 or 3.0 Users: Launching ANSYSGeom or ANSConConfig require that the
CAD's path be added to the system PATH. For the default Creo Parametric installation the additional string
to be inserted into the variable would be C:\Program Files\PTC\Creo 2.0\Parametric\bin or C:\Program
Files\PTC\Creo 3.0\<ShipCode>\Parametric\bin, where <ShipCode> is F000, M010, or some higher M###.
Previous versions of Wildfire and Creo Elements/Pro performed this action as part of the installation process,
and this action is not required.
• When spawning a Mechanical APDL session from Creo Parametric, the CAD will be unresponsive until the
user closes the Mechanical APDL session.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
18 of ANSYS, Inc. and its subsidiaries and affiliates.
Launching from Creo Parametric
ANSYS_NEUTRAL_FORMAT Yes**
ANSYS_PRODUCT_NAME ANE3FL
** These variables are not supported by Creo Parametric and are ignored.
The table shown below summaries the default settings for the config.anscon.162 file. For additional
information, please refer to Appendix A (p. 21).
Additional References
For additional information, please refer to the following:
3. If you do not own ANSYS Mechanical, set this value to the default product for your machine. See the ANSYS,
Inc. Licensing Guide for the complete list of ANSYS product names.
4. This setting is included only to maintain compatibility with the config.anscon.162 file for the connec-
tion for NX. It is no longer supported.
The connection for Creo Parametric on Windows searches for config.anscon.162 in the
\ac4\data\<platform> subdirectory.
When you save a new version of the config.anscon.162 file, the new version is always saved to
your working directory.
Add Creo's path to the PATH variable to be able to edit config.anscon (for example, <Creoloadpoint>/bin).
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 19
Starting ANSYS from Creo Parametric
ANSYS does not load when you select the ANSYSGeom button.
This generally happens if you forgot to set the ANSYS162_DIR environment variable as mentioned earlier
in the Launching from Creo Parametric section. Reset this variable and try again.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
20 of ANSYS, Inc. and its subsidiaries and affiliates.
Appendix A. Setting ANSYS Configuration Parameters
This appendix discusses the configuration of ANSYS using the config.anscon.162 configuration
file. This configuration file is used to configure ANSYS when it is launched from Creo Parametric. Default
paths include:
Windows Systems
The config.anscon.162 file may be modified by the system administrator to set information for
all connection users on a system. However, you can modify this file for your projects.
The following list defines the configuration settings that you can set in the config.anscon.162 file,
and the typically default settings.
ANSYS_CMD
Sets the full path name of the ANSYS software to be run. The Windows default is drive:\Program
Files\ANSYS Inc\V162\ANSYS\bin\ansys162
ANSYS_GRAPHIC_DEVICE
Sets the graphics driver to be used by ANSYS. The possible values for this keyword are win32 (default),
win32c, and 3D.
ANSYS_MEMORY_SIZE
Sets the amount of ANSYS workspace, in megabytes, required to run ANSYS. The value you use is
limited by how much swap space or virtual memory is available on your workstation. The default
value is 2 GB for 64-bit machines.
ANSYS_PRODUCT_NAME
Sets the product name for ANSYS. See the Product Variable Table in the ANSYS, Inc. Licensing Guide
for the complete list of ANSYS product names. The default is system dependent, but typically ANSYS
(or ANSYS Multiphysics).
ANSYS_NEUTRAL_FORMAT
Sets the database format in which the ANSYS model will be saved. The possible values are Yes (save
as neutral format) or No (save as solid format). The default value is Yes (save as neutral). This option
is no longer available. The model will always be saved in a neutral database format.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 21
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
22 of ANSYS, Inc. and its subsidiaries and affiliates.
Appendix B. Troubleshooting ANSYS Connection Issues
This appendix examines some common error messages that you may encounter. It also discusses gen-
eral connection troubleshooting as well as licensing issues that may arise.
The following sections describe some of the primary problems you may encounter when importing
parts into ANSYS. The General Troubleshooting section outlines problems common to any connection.
Later sections discuss general problems with part import. For information on problems specific to a
particular type of connection, please refer to the appropriate section of the user documentation.
B.1. General Troubleshooting
B.2. License Troubleshooting
B.3. Shared Library Problems
B.4. Configuration Errors for Creo Parametric and NX Users
B.5.Troubleshooting Part Import
Be certain the programs have execute permissions, that there is adequate swap space to run ANSYS
and the CAD package simultaneously, and that the connection is configured. In addition, if you do not
possess the proper licensing, the system may not run.
If you receive one of these error messages shown below, check the ANSYS text window for additional
error or warning messages and make sure that the connection is configured properly. Most failures are
due to the connection not being configured.
When a connection is running, an overly-long command string can be passed to the CAD package,
which can sometimes cause problems. If this message occurs, copy the file to the current working dir-
ectory and try to import it again.
Error Messages:
filename.anf not found
filename.aaa not found
Make sure that you have a current license to run the appropriate connection. Check the license file
in the licensing directory <drive>:Program Files\ANSYS Inc\Shared Files\licensing
(Windows). See the ANSYS, Inc. Licensing Guide for a complete list of product names and their asso-
ciated feature name.
These messages indicate that either the connection is not properly installed or it has not been li-
censed for the current system. In addition, if you try to run the connection for Creo Parametric or
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 23
Troubleshooting ANSYS Connection Issues
NX you must also have a valid licenses for those products. Contact your system administrator if you
have any questions about which products are licensed for your system.
This message indicates that ANSYS and the connection were installed on a shared drive (named by
using the Universal Naming Convention) rather than on a local drive (named by using a drive letter).
Replace the drive letter in the configuration file with the UNC name of the drive. Refer to the ANSYS,
Inc. Windows Installation Guide for more information.
Indicates part transfer failure in NX and Creo Parametric if ANSYS_MEMORY_SIZE is set to a value
greater than the available memory available on the machine. Use the ANSYS Configuration editor
to reduce the amount of RAM set for the ANSYS_MEMORY_SIZE variable and relaunch ANSYS.
• If you receive errors, examine the filename.log file created by ANSYS. It is located in the current working
directory and may contain clues to the source of the error.
• If a part name fails to be read into ANSYS. Be sure that the part name begins with an alphanumeric (required).
If your part name begins with a special character, you must rename it before importing. For example, a NX
user can rename the part name _123hinge.prt to be 123hinge.prt, or x123hinge.prt.
• Models that have undergone multiple conversions from other CAD packages may cause difficulties when
transferring into ANSYS.
• If your CAD package has a "defeature" option, use the utility before importing the part to ANSYS. This allows
you to avoid analyzing a model with small features that are irrelevant in an ANSYS study. Parts that have
sharp vertices or areas that have lines that touch may experience problems in tessellation and meshing.
• If the model fails to mesh, you can repair, simplify, or reimport the model.
– Choose Main Menu> Preprocessor> Modeling> Check Geom> Show Degeneracy for a list of possible
problem areas in your model. To use this commands, the part must be imported with the Allow Defea-
turing option selected.
– Repair portions of the model by choosing Main Menu> Preprocessor> Modeling> Update Geom to
update nodes. To use this command, the part must be imported with the Allow Defeaturing option se-
lected.
– Be sure to use elements that are designed to model irregular meshes. These elements are particularly
well-suited for using with imported parts:
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
24 of ANSYS, Inc. and its subsidiaries and affiliates.
Troubleshooting Part Import
Please note that it is necessary to first run the CAD Configuration Manager to configure the connection
for Creo Parametric. See the ANSYS, Inc. Installation Guide for your platform for more information.
ANSYS expects Creo Parametric to be run in the same directory from which it is started (the ANSYS
working directory). The trouble can occur if you have a startup file (such as parametric.bat,
proe1.bat, etc.) that modifies the working directory of Creo Parametric (typically from a change
directory, cd, command).
Be sure Creo Parametric can run on the machine on which you just installed the connection for
Creo Parametric.
Verify that the WBPlugInPE.dat file is pointing to the correct executable: ac4pro or ac4pro_wf5.
See the Creo Parametric Configuration for more information.
ANSYS does not launch from within Creo Parametric, and one of the following (or similar) messages
appears:
The requested license feature is not available. Contact your ANSYS support contact.
OR
The required licmsgs.dat file, which contains licensing-related messages, was not found or could
not be opened. The following path was determined using <path error occurred>. This is a
fatal licensing error. (Path: )
This problem occurs if the ANSYS162_DIR (or ANSYS_DIR) or ANSYSLIC_DIR is not set. See the
discussion on post-installation procedures in the ANSYS, Inc. Installation Guide for your platform for
more information on setting these environment variables.
Connection for Creo Parametric Cannot Import Models Using Network UNC Paths
There is a known limitation with the connection for Creo Parametric where the connection will fail
to import models specified using UNC paths. As a workaround, either copy the file to the local drive,
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 25
Troubleshooting ANSYS Connection Issues
or map the location to a network drive and import from there. This does not apply when launching
MAPDL from Creo Parametric.
Before you import a part into ANSYS, you should use the Examine Geometry function in NX to identify
any abnormalities in the part. Any problems with the part need to be corrected in NX first.
Parts created using an older version of NX (especially those created prior to version 11.0) may need to
be upgraded to a supported version of NX.
If a part fails to import into ANSYS, examine jobname.ug_log and jobname.ans_log. Both files
are located in the current working directory. The jobname.ug_log file contains warnings and errors
generated during the conversion that relate to problems in the part itself. The jobname.ans_log
file contains warnings and errors that relate to building the model in ANSYS.
When you import a part and only certain aspects of it are displayed (for example, the keypoints), look
at the part in NX using the Examine Geometry tool. This tool helps to locate corruption in the part.
Allow Defeaturing option is known to cause problem for some NX geometries during import. The
defeaturing method is currently not supported. Please avoid using the option if you encounter a
problem with it.
A compatibility issue in Linux prevents the Mechanical APDL (MAPDL) NX connection to import
geometry using NX 8.0, NX 8.5 and NX 9.0 into MAPDL. However, the Workbench NX reader works
correctly in Linux and can be used to do so. First, create a geometry cell in ANSYS Workbench, right
click on the geometry cell and select the part from the file browser. Edit the geometry cell to import
the geometry in ANSYS DesignModeler. Second, drag and drop an MAPDL system in Workbench
on top of the geometry cell. Edit the MAPDL system by double clicking on it. It should now import
the geometry in MAPDL.
A Parasolid file containing the geometry, exported from NX, could also be imported into MAPDL.
If a part fails to convert into ANSYS, examine filename.para_log and filename.ans_log. Both
files are located in the working directory. The filename.para_log file contains warnings and errors
generated during the conversion that relate to problems in the file itself. The filename.ans_log
file contains warnings and errors that relate to building the model in ANSYS.
Note
The filename.ans_log file is only generated when the part is saved in neutral database
format.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
26 of ANSYS, Inc. and its subsidiaries and affiliates.
Troubleshooting Part Import
Failed to process.
May indicate a corrupt Parasolid file. This can be caused by sending a Parasolid file via e-mail, or
by trying to import a binary file. The safest way to transfer a Parasolid file is to use FTP and transfer
the file using binary mode; be certain to save the file in ASCII format (not binary). On UNIX operating
systems, the dos2unix command can be used to convert the file to UNIX format.
Failed to process.
Schema keys are missing. Check the installation. Schema keys should be found in
<drive>:\Program Files\ANSYS Inc\V162\ANSYS\ac4\schema (Windows). On Windows
machines, the P_SCHEMA environment variable must be set to <drive>:\Program
Files\ANSYS Inc\V162\ANSYS\ac4\schema.
***Warning: ANSYS environment variables: ANSYS162_DIR and/or ANSYS162_SYSDIR are not set.
***ERROR: connection for Parasolid directory structure is not set. Unable to find the Connection
executable.
Either the ANSYS162_DIR or the ANSYS162_SYSDIR variable needs to be set. See the ANSYS, Inc.
Installation Guide for your platform for information about these configuration variables.
If a part fails to convert into ANSYS, examine filename.sat_log and filename.ans_log. Both
files are located in the working directory. The filename.sat_log file contains warnings and errors
generated during the conversion that relate to problems in the file itself. The filename.ans_log
file contains warnings and errors that relate to building the model in ANSYS.
If a model is sensitive to tolerance, shapes may not be created properly, which can lead to poorly
transferred areas. If you find this problem with a model, reimport it using the following steps:
where filename.aaa is the name of the file you are working with
The following problems may occur on Windows systems: A sys error may be displayed if the executable
is in the wrong directory or if the required shared libraries are missing. Check for proper installation
(see the ANSYS, Inc. Windows Installation Guide) and reinstall the software.
***Warning: ANSYS environment variables: ANSYS162_DIR and/or ANSYS162_SYSDIR are not set.
***ERROR: connection for SAT directory structure is not set. Unable to find the Connection execut-
able.
Either the ANSYS162_DIR or the ANSYS162_SYSDIR variable needs to be set. See the ANSYS, Inc.
Installation Guide for your platform for information about these configuration variables.
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 27
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
28 of ANSYS, Inc. and its subsidiaries and affiliates.
E
Index entities
Parasolid, 13
Symbols environment variables
.sat files, 5 ANSCON_CONFIG_DIR, 13
UGII_BASE_DIR, 13
A UGII_OPTION, 13, 26
ACIS geometry file, 5 UGII_VENDOR_DIR, 13
ACIS-based CAD files
importing, 5 F
ANSCon Config option, 17 files
ANSCON_CONFIG_DIR, 13 combining .anf , 2
ANSYS config.anscon.162, 19
configuration settings, 18 .dlv, 6
launching from Creo Parametric, 17 .model, 6
quitting, 17 protk.dat, 17
ANSYS connection, 1 .prt, 9-10
ANSYS Geom option, 17 .CATPart, 7
.asm files, 9 .sat, 5
C G
CAD connection functionality Geometry Interface
supported systems for, 2 see ANSYS connection, 1
CAD packages, 1
CAD parts, 1 H
CATIA, 6 hardware requirements, 2
CATIA version 5, 7
Creo Parametric, 9 I
importing, 3 import commands
Parasolid, 13 ~CAT5IN, 7
~CAT5IN command, 7 ~CATIAIN, 6
CATIA ~PARAIN, 13
importing parts created in, 6 ~PROEIN, 9
~CATIAIN command, 6 ~SATIN, 5
combining .anf files, 2 ~UGIN, 10
config.anscon.162 file, 19 importing, 1
Configuration Editor, 17 .sat files, 5
configuration files ACIS-based CAD files, 5
troubleshooting, 24 CAD parts, 3
configuration settings CATIA parts, 6
ignored, 18 CATIA version 5 parts, 7
modifying from Creo Parametric, 18 Creo Parametric parts, 9
connection NX parts, 10
troubleshooting, 23 Parasolid assemblies, 14
converting a CAD part, 17 Parasolid parts, 13
Creo Parametric importing parts
importing models from, 9 Creo Parametric, 9
launching ANSYS from, 17 Parasolid, 13
modifying ANSYS settings from, 18 /INPUT command, 2
setting command name for, 25 installation prerequisites, 2
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 29
Index
L T
launch troubleshooting, 23 troubleshooting, 23
license troubleshooting, 23 configuration files, 24
licenses, 23
M NX file import, 26
measurement units in Parasolid files, 14 Parasolid file import, 26
multiple .anf files, 2 part import, 24
SAT file import, 27
N
NX U
files created during file import, 12 UGII_BASE_DIR, 13
importing files from, 10 UGII_OPTION, 13, 26
troubleshooting file import, 26 UGII_VENDOR_DIR, 13
~UGIN, 10
P
P_SCHEMA environment variable, 26
~PARAIN command, 13
Parasolid
importing parts, 13
troubleshooting file import, 26
Parasolid files
importing, 13
scaling models, 14
parts
ACIS, 5
CATIA, 6
CATIA Version 5, 7
importing, 3
importing Parasolid, 13
NX, 10
plotting volumes of, 17
troubleshooting import, 24
path environment variable, 25
plotting volumes in ANSYS, 17
prerequisites for installation, 2
~PROEIN command, 9
protk.dat file, 17
.prt files, 9
NX, 10
S
SAT files
troubleshooting import, 27
~SATIN command, 5
scaling models
in Parasolid imports, 14
shared libraries
troubleshooting, 24
system requirements, 2
systems, 2
Release 16.2 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
30 of ANSYS, Inc. and its subsidiaries and affiliates.