ANSYS Inc. Known Issues and Limitations

Known Issues and Limitations
ANSYS, Inc. Release 19.2

Southpointe August 2018
2600 ANSYS Drive ANSYS, Inc. and
Canonsburg, PA 15317 ANSYS Europe,
Ltd. are UL
ansysinfo@ansys.com registered ISO
http://www.ansys.com 9001: 2015
(T) 724-746-3304 companies.
(F) 724-514-9494
Copyright and Trademark Information
© 2018 ANSYS, Inc. Unauthorized use, distribution or duplication is prohibited.
ANSYS, ANSYS Workbench, AUTODYN, CFX, FLUENT 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 located 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. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.
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.
ANSYS, Inc. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.
U.S. Government Rights
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, contact ANSYS, Inc.
Published in the U.S.A.

Table of Contents
Introduction ................................................................................................................................................. v
1. Advisories ............................................................................................................................................... 1
2. Installation .............................................................................................................................................. 3
3. Licensing ................................................................................................................................................. 5
4. Documentation ....................................................................................................................................... 7
5. ANSYS Structural Products ..................................................................................................................... 9
5.1. Mechanical ....................................................................................................................................... 9
5.2. Mechanical APDL .............................................................................................................................. 9
5.3. Autodyn ......................................................................................................................................... 10
5.4. Aqwa .............................................................................................................................................. 10
5.5. ANSYS Composite PrepPost (ACP) ................................................................................................... 10
6. ANSYS Fluids Products .......................................................................................................................... 11
6.1. Fluent ............................................................................................................................................. 11
6.1.1. General .................................................................................................................................. 11
6.1.2. Meshing Mode ....................................................................................................................... 11
6.1.3. Solution Mode ....................................................................................................................... 12
6.2. CFX ................................................................................................................................................ 14
6.3. TurboGrid ....................................................................................................................................... 14
6.4. BladeModeler ................................................................................................................................. 14
6.5. CFD-Post ........................................................................................................................................ 14
6.6. Polyflow ......................................................................................................................................... 14
6.7. Forte .............................................................................................................................................. 14
6.8. Chemkin-Pro .................................................................................................................................. 14
6.9. FENSAP-ICE .................................................................................................................................... 15
7. ANSYS Electronics Products .................................................................................................................. 17
7.1. Icepak ............................................................................................................................................ 17
8. ANSYS Geometry & Mesh Prep Products .............................................................................................. 19
8.1. CAD Connections & Integration ....................................................................................................... 19
8.2. DesignModeler ............................................................................................................................... 19
8.3. Meshing ......................................................................................................................................... 19
8.4. IC Engine ........................................................................................................................................ 19
8.5. ICEM CFD ........................................................................................................................................ 19
9. ANSYS Simulation Products .................................................................................................................. 21
9.1. Workbench ..................................................................................................................................... 21
9.2. System Coupling ............................................................................................................................. 21
9.3. ANSYS ACT ..................................................................................................................................... 21
9.4. Remote Solve Manager (RSM) ......................................................................................................... 21
9.5. DesignXplorer ................................................................................................................................ 21
10. ANSYS Discovery ................................................................................................................................. 23
10.1. ANSYS Discovery SpaceClaim ........................................................................................................ 23
10.2. ANSYS Discovery Live .................................................................................................................... 23
10.3. ANSYS Discovery AIM .................................................................................................................... 23
Release 19.2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
iv of ANSYS, Inc. and its subsidiaries and affiliates.
Introduction
The following information is relevant to ANSYS, Inc. Release 19.2. The entries describe known non-op-
erational behavior, an error, or limitation at the time of this release. Work-arounds for these items, if
available, are included in the respective descriptions. Inclusion in this document does not imply the issues
and limitations are applicable to future releases.
The parenthetical numbers associated with each entry are reference numbers corresponding to an in-
ternal error tracking system. The numbers are included to help to facilitate ANSYS, Inc. technical support
and help to ensure that the issue described in the entry is resolved.
Service packs may become available for some of the entries.
Additional known issues and limitations may be found in the product Help and/or release notes, both
accessible in the ANSYS Help.
For the most recent version of the current release's Known Issues and Limitations document, see the
ANSYS, Inc. Release Notes section of the ANSYS Help internet documentation website or download it
here.
of ANSYS, Inc. and its subsidiaries and affiliates. v
vi of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Advisories
Specific to ANSYS Workbench, Japanese multi-byte characters in new folder paths are not supported.
Creation of a new folder and use of the characters results in a runtime error that stops the run process.
(160971)
of ANSYS, Inc. and its subsidiaries and affiliates. 1
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Installation
No known issues, limitations, or documentation inaccuracies.
Chapter 3: Licensing
Chapter 4: Documentation
CAD Integration
In the Limitations sub-section of the Creo Parametric Associative Geometry Interface section, the following
entry should be included:
Smart Update of Mixed Unit Assemblies: There are some situations where assembly compon-
ents will fail to be smart updated due to the component(s) having different unit system than
the root assembly. Work-around: Normalize model units within Creo; see the Length Unit section
of the Creo Parametric Associative Geometry Interface help for detailed instructions. (177639)
Chapter 5: ANSYS Structural Products
5.1. Mechanical
When performing topology optimization, design validation workflows are not supported on Linux
platforms, since they require SpaceClaim Direct Modeler, which is not available on those platforms.
(176058)
The Samcef CAE Interface requires the temperature field for those material properties which indicate
that temperature is supported f(T). Refer to the Supported Properties in the Engineering Data User's
Guide for Samcef. If the temperature field is missing the Samcef input file will not be written. The tem-
perature field can removed from the property for a material in Engineering Data or a material read from
a material database may not have it defined. If these materials are to be used for Samcef setup you
must add the temperature field and define a value for the temperature. (176878)
If you resume a solved database prior to this release 19.2 that has the material-based Constant
Damping Coefficient defined in the Engineering Data workspace and the analysis is Mode Superposition-
based Harmonic Response Analysis/Transient Structural Analysis, then the new property Eqv. Damping
Ratio From Modal (Analysis Settings > Damping Controls) becomes visible and is set to Yes.
This setting makes the Expansion property (Analysis Settings > Output Controls) to automatically
become set to Modal Solution provided the Expand Results From property was set to Program Con-
trolled. The Expansion property should not be modified for solved database because you could have
an expanded solution from the Modal or respective Harmonic Response/Transient Structural solution.
However, the expansion from the Modal solution is needed to account for the material-based Constant
Damping Coefficient effect in your MSUP Harmonic and MSUP Transient solutions. Therefore, it is re-
commended that you resolve the affected harmonic or transient analysis if it was not expanded from
the Modal solution. This is important because when you re-solve the analysis, you may see different
results for the respective analyses. (177261)
The Campbell Diagram may present incorrect results in a Modal analysis that includes substructures
where you have made selections in the Expansion Settings worksheet. Work-around: To properly
evaluate Campbell Diagram results, you need to:
1. Specify your Campbell Diagram result objects before performing the solution, and
2. Remove any Expansion Settings worksheet selections.
Once you have performed the solution, you can add results and use the Expansion Settings worksheet
as desired. (177526)
5.2. Mechanical APDL

If new elements are added in a modal analysis restart session, when the enforced motion calculation
key is used in the MODCONT command (EnforcedKey=ON) and VALUE is issued in D command to define
the support points where imposed motion will be applied and to define the enforced base identification
ANSYS Structural Products
number, the program may crash unexpectedly. The following are typical Traceback messages where
these crashes may occur:
• enforceSlaveFullFileSeq
• enforceSlaveFULL
• modeupdLoad
• svkan2
• solvcl
• ANSYS
Work-around:
• Perform the analysis without modal restart.
• Do not define new elements in a modal restart session.
(176012)
5.3. Autodyn
5.4. Aqwa
5.5. ANSYS Composite PrepPost (ACP)

Chapter 6: ANSYS Fluids Products
6.1. Fluent
The following sections list new or recently discovered limitations known to exist in version 19.2.
6.1.1. General
Starting Fluent
• When first starting Fluent from Windows using the Use Remote Linux Nodes option in the Fluent Launcher,
Fluent may not be able to locate and execute the ssh command and the following warning will be printed:
'ssh' is not recognized as an internal or external command, operable

program or batch file.
Work-around: To avoid this start-up issue, in the Fluent Launcher, select the Remote tab, select
Other under Remote Spawn Command, and provide the full path to the ssh executable.
In addition, you should add the location of ssh executable to the beginning of the PATH environment
variable.
(176971)
For a list of ongoing Fluent limitations listed in previous ANSYS, Inc. Release Notes, refer to Known
Limitations in ANSYS Fluent 19.2 in the Fluent Getting Started Guide.
6.1.2. Meshing Mode

Graphics
• For any session that displays graphics in the graphics window (including when running a batch job
with the -gu command line option) and/or saves picture files, the rendering / saving speed will be
significantly slower if you do not follow all of the following best practices:
– Run Cortex on a suitable machine with an appropriate graphics card and the latest drivers (for details,
see the ANSYS website). Note that you can assign Cortex to a particular machine using the -gui_ma-
chine=<hostname> command line option.
– Ensure that Cortex / the host process is run on a separate machine than that used for compute node 0.
For example, do not include the machine assigned using the -gui_machine option as the first machine
in the hosts file / machine list (specified using the -cnf=x command line option).
– Do not set the graphics driver to null, x11 (for Linux), or msw (for Windows).
– When saving picture files, enable the Fast hardcopy option in the Preferences dialog box (under
Graphics).
ANSYS Fluids Products
(177399)
Surfaces
• Fluent may unexpectedly close when you create multiple surfaces of the same type (point or line) and you
then try to immediately delete the most recent surface.
To avoid loss of data, work-arounds include:
1. Delete any surfaces, except the most recently created surface
2. Save the case file and delete surfaces in any order
3. After creating the surfaces, perform some other operation (such as displaying the mesh, etc.) fol-
lowed by deleting the most recent surface. This will give you the chance to still save the case file
and have no data loss, however, Fluent will still experience a segmentation violation.
(177618)
6.1.3. Solution Mode

Discrete Phase Model
• For transient Lagrangian multiphase analysis with unsteady particle tracking, atomizer or cone injections
will release particles from the same position rather than from random positions if Particle Time Step Size
is smaller than Time Step Size. To use particle random starting points, issue the following scheme commands
in the ANSYS Fluent console:
(rpsetvar 'dpm/random/seed-timestep-corrected? #t)
(dpm-parameters-changed)
Note that this change will also affect particle trajectories if stochastic tracking, particle breakup, or
other mechanisms that involve random numbers are used. (176638)
Remote Display
• (Exceed onDemand and VNC Viewer) The Num Lock number keys and arrows may not function in the
graphical user interface or console. Work-around: Define the XKB_DEFAULT_RULES environment variable
set equal to base, which resolves the arrow keys' functionality. Number entries must still be completed
using the number keys at the top of the standard keyboard. (172528)
Data Import
• (Windows only) The file filter available in the Select File dialog box may not work as expected, requiring
you to manually select the desired file(s) without filtering aid. (174291)
Remote Visualization Client
• In certain circumstances, typing or pasting a series of interdependent Python commands into the
Remote Client console could result in an unexpected closure of both the Fluent server and the Remote
Visualization Client applications. To avoid this potential issue, read Python commands into the Remote
Client using the File/Read Script File... menu option. (176614)
Fluent
• For a client session with multiple connected servers, only one server can receive commands through
the Send Command to Server dialog box—that server is whichever one you send a command to
first using this dialog box. Work-around: You can use the Python console to control the other con-
nected servers. (177632)
• (Overset meshing cases) Displaying graphics objects on certain surfaces (such as internals or symmet-
ries) in the Remote Client may cause the client and/or server to experience an unrecoverable error.
(177493)
• On some Linux machines you may see a warning message containing SO_REUSEPORT printed in
the console when starting the server. This message can be ignored—it will not have any effect on
the simulation or on the Remote Visualization Client. (176526)
Graphical User Interface
• The Lighting option in the Viewing ribbon tab remains grayed-out even after the Headlight option is dis-
abled. Work-around: You can modify the Lights On option through the Display Options dialog box.
(173998)
ACT in ANSYS Fluent
• ACT with ANSYS Fluent is disabled on Linux systems for Release 19.2. To use ACT with ANSYS Fluent, use
Release 19.2 on Windows or Release 19.1 on Linux. (177173)
Graphics
• Deleting a Point or Line surface can cause a crash when multiple surfaces of same type (point or line) are
created and user tries to delete immediately the latest one created. There are several workarounds:
– Delete any point or line except latest one created
– Save case file and delete surfaces in any order
– After creating surfaces, do some other operations (e.g. mesh display etc.) - now deleting latest surface
gives user chance to save case file (seg violation, but no loss of data)
(177618)
• For any session that displays graphics in the graphics window (including when running a batch job
with the -gu command line option) and/or saves picture files, the rendering / saving speed will be
significantly slower if you do not follow all of the following best practices:
– Run Cortex on a suitable machine with an appropriate graphics card and the latest drivers (for details,
see the ANSYS website). Note that you can assign Cortex to a particular machine using the -gui_ma-
chine=<hostname> command line option.
– Ensure that Cortex / the host process is run on a separate machine than that used for compute node 0.
For example, do not include the machine assigned using the -gui_machine option as the first machine
in the hosts file / machine list (specified using the -cnf=x command line option).
– Do not set the graphics driver to null, x11 (for Linux), or msw (for Windows).
– When saving picture files, enable the Fast hardcopy option in the Preferences dialog box (under
Graphics).
ANSYS Fluids Products
(177399)
Cell Registers
• Cell register display is only adding to the graphics window, not clearing and re-displaying. Work-around:
Start with a new graphics window, then display the register. (177088)
• A cell register will not display with the mesh (even if Draw Mesh is enabled for that register), unless you first
display a mesh in the graphics window before displaying the cell register. (177088)
For a list of ongoing Fluent limitations listed in previous ANSYS, Inc. Release Notes, refer to Known
Limitations in ANSYS Fluent 19.2 in the Fluent Getting Started Guide.
6.2. CFX
This applies to CFX multi-configuration cases run in ANSYS Workbench. When the CFX-Solver Manager
is used to monitor a run in progress, the monitoring does not start automatically and nothing is shown
until the run has completed. When the run has completed, the displayed Run History might not show
the individual configurations. Work-around: In CFX-Solver Manager, manually start monitoring by se-
lecting "File" > "Monitor Run in Progress" and selecting the run directory from within the project directory.
If individual configurations are missing from the Run History after the run has completed, force the
completed run data to be re-read by closing the CFX-Solver Manager and then re-opening it using the
"Display Monitors" command. (176357)
CFX-Solver Manager is likely to crash when continuing an Operating Point run in which all operating
point jobs are to be re-run. Work-around: Whenever all operating point jobs are to be re-run, do not
continue an existing run; instead, start a new run. (177559)
6.3. TurboGrid
6.4. BladeModeler
6.5. CFD-Post
6.6. Polyflow
6.7. Forte
6.8. Chemkin-Pro
FENSAP-ICE
6.9. FENSAP-ICE
• Wall boundaries that cut through the prism layer in unstructured grids are not supported for multishot
icing simulations with automatic remeshing using OptiGrid. (170443)
• The post-processing tools need to be manually launched to load the *.orig solution file when viewing
a droplet solution file while using the custom_meshing_FLUENT script. For example grid.ice.000002 is
matched with droplet.drop.000002.orig. (177584)
• When a screen boundary of type 6000 contains duplicate nodes that are topologically disconnected,
FENSAP will not stop or provide warning messages and the flow and droplet calculations will diverge.
These disconnected nodes are usually created when two separate grid files are merged into one but
the two domains are not reconnected at the interface. (171432)
• DROP3D can produce numerical oscillations in ICC and LWC when very fine structured grids are used
with particles that are larger than 40 microns in diameter. Increasing the crosswind dissipation level to
1e-4 helps to reduce the magnitude of these oscillations. (175731)
Chapter 7: ANSYS Electronics Products
For more entries specific to the Electronics Products, see the Known Issues and Limitations section of
the Readme.txt document distributed with the Electronics products.
7.1. Icepak
Chapter 8: ANSYS Geometry & Mesh Prep Products
8.1. CAD Connections & Integration
See the Documentation section of this document for items specific to CAD Integration.
8.2. DesignModeler
8.3. Meshing
Mesh copy will not generate conformal mesh when used on parts or bodies on which share-topology
was performed. It is recommended not to use mesh copy on parts or bodies which are involved in
share-topology with other parts or bodies, and a warning message will be issued in such situations.
(176447)
8.4. IC Engine
8.5. ICEM CFD

Chapter 9: ANSYS Simulation Products
9.1. Workbench
When running or updating a Workbench project on a Linux machine that generates many files, such
as a large number of Design Points running concurrently, the solver can fail with the following exception:
System.IO.IOException: Too many open files

Work-around: To prevent this failure, increase the maximum number of files able to be opened at one
time by running the ulimit command ulimit -n [limit] where limit is either a numerical value
(for example, 1000000) or, “unlimited”. (131559)
When duplicating multiple systems, a dialog is is displayed with the following message:
Should upstream connections from the rest of the project be kept

for created systems?
If you are duplicating systems linked to an upstream system by both shared and data transfer connections,
selecting either dialog option has the same effect. The shared connections are not duplicated and
connected to the new systems, but the data transfer connections are. Work-around: If you selected
Yes, you must manually create the shared connections from the upstream system to the duplicated
systems. If you selected No, delete the data transfer connections to prevent errors. (177587)
9.2. System Coupling

When running Fluent with System Coupling, if you attempt to create the System Coupling dynamic
mesh zone on an existing polyhedral mesh, you'll receive an error. To avoid this error, it's recommended
that you first set up the dynamic mesh zone and then convert to a polyhedral mesh. (177375)
9.3. ANSYS ACT

See the ANSYS ACT 19.2 Known Issues and Limitations document on the ACT Resources page on the
ANSYS Customer Portal.
9.4. Remote Solve Manager (RSM)

9.5. DesignXplorer
ROM Production
To produce a new ROM for Fluent, you can import a CAS file that already has an enabled ROM into the
Setup cell of the Fluent system. However, because the setup of the ROM in this CAS file cannot be de-
tected until Fluent is started, the status of the Design of Experiments (RB) cell of the ROM Builder
system indicates that an edit is required. Work-around: To be able to run the DOE, you simply have to
start Fluent, close it, and then refresh the Design of Experiments (RB) cell. (176587)
Chapter 10: ANSYS Discovery
10.1. ANSYS Discovery SpaceClaim
10.2. ANSYS Discovery Live

10.3. ANSYS Discovery AIM

It has been observed in a few occasions that the Solution Monitor leads to a freeze of the Solve of a
coextrusion setup in AIM. Work-around: Remove any chart before launching the Solve. (151306)
If two or more contacts overlap at a shared face, edge, or vertex of a multi-body part (shared topology)
in a structural analysis, contact reaction results can be incorrect if evaluated on multiple contacts. Work-
around: Evaluate contact reaction results on one contact at a time in such a situation. (177544)

ANSYS Inc. Known Issues and Limitations

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ANSYS Inc. Known Issues and Limitations

Hochgeladen von

Copyright:

Verfügbare Formate

Known Issues and Limitations

ANSYS, Inc. Release 19.2

© 2018 ANSYS, Inc. Unauthorized use, distribution or duplication is prohibited.

U.S. Government Rights

Published in the U.S.A.

Service packs may become available for some of the entries.

2. Remove any Expansion Settings worksheet selections.

5.2. Mechanical APDL

• Perform the analysis without modal restart.

• Do not define new elements in a modal restart session.

5.5. ANSYS Composite PrepPost (ACP)

'ssh' is not recognized as an internal or external command, operable

6.1.2. Meshing Mode

To avoid loss of data, work-arounds include:

1. Delete any surfaces, except the most recently created surface

2. Save the case file and delete surfaces in any order

6.1.3. Solution Mode

(rpsetvar 'dpm/random/seed-timestep-corrected? #t)

Remote Visualization Client

Graphical User Interface

ACT in ANSYS Fluent

– Delete any point or line except latest one created

– Save case file and delete surfaces in any order

8.5. ICEM CFD

System.IO.IOException: Too many open files

Should upstream connections from the rest of the project be kept

9.2. System Coupling

9.3. ANSYS ACT

9.4. Remote Solve Manager (RSM)

10.2. ANSYS Discovery Live

10.3. ANSYS Discovery AIM

Das könnte Ihnen auch gefallen