Ansys Known Issues and Limitations
description
Transcript of Ansys Known Issues and Limitations
ANSYS, Inc. Known Issues and
Limitations
Release 14.0ANSYS, Inc.
November 2011Southpointe
275 Technology Drive 000286
Canonsburg, PA 15317 ANSYS, Inc. is
certified to ISO
9001:[email protected]
http://www.ansys.com
(T) 724-746-3304
(F) 724-514-9494
Copyright and Trademark Information
© 2011 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 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 subsidi-
aries 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 CONFIDENTIAL 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, com-
pliance 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. is certified to ISO 9001:2008.
U.S. Government Rights
For U.S. Government users, except as specifically granted by the ANSYS, Inc. software li-
cense 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.
Published in the U.S.A.
Table of Contents
Introduction .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
1. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2. Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Advisories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. ANSYS Workbench Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7. Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Engineering Data Workspace .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.2. Parameters Workspace .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Common Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. CAD Connections & Integration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2. ANSYS DesignModeler ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.3. ANSYS DesignXplorer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.4. FE Modeler ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
9. Meshing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.1. ANSYS Meshing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.2. ANSYS ICEM CFD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10. Mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.1. ANSYS Mechanical ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.2. ANSYS Mechanical APDL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
11. Remote Solve Manager (RSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
12. Fluid Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.1. ANSYS CFD-Post ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.2. ANSYS CFD-Viewer .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.3. ANSYS CFX-Pre .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.4. ANSYS CFX-Solver Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.5. ANSYS CFX-Solver ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.6. ANSYS Fluent .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.7. ANSYS Workbench IC Engine Component System ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.8. ANSYS Icepak .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
12.9. ANSYS POLYFLOW ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
13. Explicit Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.1. ANSYS Explicit ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.2. ANSYS AUTODYN ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.3. ANSYS LS-DYNA ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
14. Turbo Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.1. ANSYS BladeModeler ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.2. ANSYS TurboGrid .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
iiiRelease 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
14.3. ANSYS Vista TF .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
15. Offshore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
15.1. ANSYS ASAS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
15.2. ANSYS AQWA ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
16. Simulation Process and Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
16.1. ANSYS EKM Desktop .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.iv
ANSYS, Inc. Known Issues and Limitations
Introduction
The following items are specific to the ANSYS, Inc. release 14.0. The entries de-
scribe known non-operational behavior, an error, or limitation at the time of this
release (Release to Manufacturing date 2011–11–17). Work-arounds for these
items, if available, are provided in the respective descriptions. Inclusion in this
document does not imply the issues and limitations are applicable to future re-
leases.
The parenthetical numbers associated with each entry are reference numbers
corresponding to an internal error tracking system. The numbers are included
here to facilitate ANSYS, Inc. technical support and help ensure that the issue
described in the entry is resolved.
Product documentation changes relative to some entries are detailed in the
ANSYS, Inc. Documentation Errata located in the Documentation section of the
ANSYS Customer Portal.
Service packs may become available for some of the entries. See the ANSYS
Customer Portal for information about the errata, ANSYS service packs and any
additional items not included in this document. First-time users of the customer
portal must register via the ANSYS Web site (www.ANSYS.com) to create a
password.
vRelease 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.vi
Chapter 1: Installation
Specific to the 64-bit Linux platform, ANSYS Mechanical must be installed to
import Meshing/CFX-Mesh files (.cmdb, .dsdb) into ANSYS CFX-Pre and ANSYS
CFD-Post. (25415)
CFX Distributed Parallel in ANSYS CFX 13 uses HP-MPI while CFX Distributed
Parallel in ANSYS CFX 14.0 uses PCMPI. These different installations of MPI can
have a conflict when installed on the same Windows machine. To avoid such a
conflict, be sure to follow the installation instructions that appear during Platform
MPI installation. (25077, 25565)
If you install the CATIA v5 CAD product without installing another product that
includes ANSYS Workbench, the CAD Configuration Manager does not run
automatically and the necessary configuration is not completed. In this situation,
you must run the CAD Configuration Manager after the installation is complete
to finish the CATIA v5 configuration. (26856)
1Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.2
Chapter 2: Licensing
Use of the FlexNet LM_PROJECT environment variable does not function as ex-
pected with ANSYS, Inc. licensing. Beginning with release 14.0, LM_PROJECT is
ignored by default. To use the value of LM_PROJECT from the first user for all
subsequent connections, use the command option -uselmproject or the an-
syslmd.ini keyword ANSYSLI_USE_LMPROJECT (as occurred in release 13.0). If
you set the above command option or keyword and the first user does not have
LM_PROJECT set, it will remain unset by all subsequent users going through the
Licensing Interconnect. (21649)
3Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.4
Chapter 3: Platform Support
To continue use of an installed version of ANSYS release 13 with ANSYS Mechan-
ical running HPC with HP-MPI, please run the following command to ensure
compatibility: %AWP_ROOT140%\commonfiles\MPI\Platform\8.1.2\Win-dows\HPMPICOMPAT\hpmpicompat.bat The command will display a dialog
box with a title of "ANSYS 13.0 SP1 Help". (20536)
5Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.6
Chapter 4: Documentation
Corrections specific to the product documentation (ANSYS Help) are detailed in
the ANSYS, Inc. Documentation Errata located in the Documentation section of
the ANSYS Customer Portal. First-time users of the customer portal must register
via the ANSYS Web site (www.ANSYS.com) to create a password.
The PDF option, accessible via the Help menu, is limited to the opening of one
PDF file. To open a second PDF file, the first one must be closed. (26729)
7Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.8
Chapter 5: Advisories
In addition to this document (ANSYS, Inc. Known Issues and Limitations), release
14.0 product-specific known issues and limitations can be found in the product
help and release notes. The ANSYS, Inc. Release Notes document is located in the
Documentation section of the ANSYS Customer Portal. First-time users of the
customer portal must register via the ANSYS Web site (www.ANSYS.com) to
create a password.
9Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.10
Chapter 6: ANSYS Workbench Environment
In order to update design points of a project with BladeEditor parameters through
RSM, you must set the Geometry license preference to ANSYS BladeModeler, as
described in product documentation at TurboSystem> 4. BladeEditor > 4.1.
Configuring the ANSYS BladeModeler License, on both the local host and on the
remote compute server. (16825)
EKM Commands and Queries have changed for release 14.0. Pre-14.0 EKM Com-
mand and Query users must update their wbjn or python-based scripts to
maintain compatibility. Please refer to the release 14.0 Workbench Scripting Guide
for more details on the new EKM entries. (25446)
ANSYS Workbench is a multi-threaded application which makes use of more of
the system simultaneously. One way in which it does this is by off-loading ren-
dering operations to auxiliary threads. To make this work correctly on Linux, all
Xlib calls are treated atomically (without corrupting internal X state), and the
way this achieved is by using X's build-in synchronization mechanism. Certain
RH5 releases introduced problems which resulted in various ANSYS Workbench
exceptions when X11 synchronization is used. The problem is described in a Red
Hat errata under "RHBA-2010:0127-1". The associated patch resolves the ANSYS
Workbench exceptions in many cases. As a workaround, we have disabled X11
synchronization in ANSYS Workbench and have disabled some minor features
that require synchronization. For example, run-time updates of charts in the
System Coupling user interface have been disabled on all Linux platforms. Chart
updates and operations after run execution are unaffected. All functionality may
be re-enable by passing "-enableX11threads" to runwb2 on all supported SUSE
and RH distributions, with the exception of RH5. Using this option on RH5 systems
is not recommended. (25461, 26739)
Resetting an ANSYS Fluent Solution component that has been configured to
submit to Remote Solve Manager may result in incorrect component properties
being displayed. To work around this problem, select another component, and
then select the Fluent Solution component to refresh the Properties view. Note
that, if this occurs, certain controls like Execution Mode may not respect the
11Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
setting of the "Use Setup Launcher Settings" control by allowing changes that
are not valid. (25764)
ANSYS, Inc. release 14 significantly enhances the ANSYS Workbench Remote
Solve Manager (RSM) functionality. It is possible to use
1. RSM for component update with various applications (Mechanical, MAPDL,
CFX, ANSYS Fluent and Polyflow) and/or
2. RSM submission of the ANSYS Workbench Update All Design Points.
A large number of options are available by combining the two approaches and
the different applications. The general recommendations are:
• Use RSM component submission (without RSM submission of Update All
Design Points) for jobs that require parallel execution of the solver. Please
note that this approach may temporarily require using N+1 licenses for the
submission of N jobs.
• Use RSM submission of Update All Design Points (without choosing RSM
submission at the component level) for jobs that do not require parallel
execution of the solver. RSM submission of Update All Design Points allows
for remote execution of the whole ANSYS Workbench project and for parallel
execution of a user-specified number of design points.
Combinations other than the one listed above can be problematic, depending
upon the specific applications in use, the choice of parallel settings, and the re-
mote submission options (cluster, native RSM). Those who need to use a non-
recommended configuration or approach are advised to contact ANSYS support
in order to be alerted to specific limitations and issues. (26170, 26865, 26905)
Web-based ANSYS Workbench content may not be accessible from certain Linux-
based machine configurations. Affected areas include:
• Report Generation
• EKM (via menus)
• Tutorials (via menus)
• "Getting Started" links
• Message links
SOLUTION A: If Linux KDE users observe the error "System.ComponentMod-
el.Win32Exception: Cannot find the specified file " while accessing web-based
workbench content, kfmclient must be added to the user account's path:
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.12
Chapter 6: ANSYS Workbench Environment
1. Locate kfmclient on your machine (typically under /opt/kdeX/bin, where
X is the KDE major version number)
2. Edit the .cshrc file located at your home directory (~) by adding the kfmcli-
ent location to the path:
set path = ( ~/bin/$ARCH \ ~/bin \ /usr/local/bin \ /usr/openwin/bin \ /usr/ucb \ /usr/bsd \ /bin \ /usr/bin \ /usr/sbin \ /etc \ /usr/etc \ /usr/local/etc \ /usr/bin/X11 \ /usr/local/bin/X11 \ /usr/lang \ /opt/kdeX/bin )
SOLUTION B: If Linux KDE users observe the error "Unknown Proxy Host" while
interacting with Workbench EKM Menus:
1. Confirm that the proxy address is valid.
2. Confirm that the system's default web browser is not Konqueror (Firefox
is recommended).
a. Navigate to "Personal Settings > KDE Components > Component
Chooser > Web Browser".
b. Under "Open http and https URLs" select "in the following browser".
c. If Konqueror is the current selection or the option is empty, select "..."
and specify an alternate web browser from the "Browse > Web
Browser" location.
d. Press OK.
3. Apply changes.
(26374, 26384)
ANSYS Workbench projects that contain missing files are not found via an Ad-
vanced Search from the Open Project from Repository dialog. (26423)
Workbench Project Archive (WBPZ) files cannot be opened from the search results
pane of the "Open from repository" dialog. Double-clicking a WBPZ file or select-
13Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
ing a WBPZ file and clicking the "Open" button will result in an error. Work-
around: Note the repository path of the WBPZ file in the search results that you
wish to open, close the search results pane, and navigate to the WBPZ file's path
in the repository browsing panel and double-click the WBPZ file. (26454)
When monitoring a solution using CFX-Solver Manager under ANSYS Workbench,
the Stop button does not successfully interrupt the CFX Solver when the run has
been started from the Define Run panel. Work-around: Interrupt the run from
the ANSYS Workbench progress bar. Alternatively, you can close CFX-Solver
Manager and reopen it by selecting Display Monitors from the CFX Solution cell's
context menu, which will also make the Stop button functional. (26554)
When the MAPDL solver runs a distributed solve on a Windows HPC cluster via
RSM, the software may report that the solve failed, even though it ran on the
cluster. This can occur when the solve is submitted to the cluster either by
Mechanical or by the Workbench MAPDL add-in. In both cases the .out file for
the solve is incorrectly deleted, causing the client to report that the solve failed.
In addition, the distributed solver processes will incorrectly write their output
files to the shared cluster directory on the head node of the cluster, instead of
to a local directory on each cluster node. This can lead to poor performance.
This defect can be corrected by modifying a script file. Please contact support
for details. (26694)
In ANSYS Workbench, when a new repository connection to a shared server is
created for the first time on a Windows 32–bit machine, the screen may go blank
after you enter the EKM server address in the Create a New EKM Repository
Connection wizard. When you Cancel the wizard, ANSYS Workbench may report
an exception. Work-around: Close the Open Project from Repository wizard or
Save Project to Repository dialog (depending on where you initiated the create
a new repository action from) and create the new connection again. (27066)
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.14
Chapter 6: ANSYS Workbench Environment
Chapter 7: Workspaces
7.1. Engineering Data Workspace
Prony models require that the number of entries be the same when entering
data for multiple temperatures. The MAPDL solver will use the entry count of
the first temperature point as the number of entries, so data at other temperatures
could be ignored or incorrectly used. (26576)
7.2. Parameters Workspace
No known issues or limitations.
15Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.16
Chapter 8: Common Tools
8.1. CAD Connections & Integration
A known issue exists when the ANSYS plug-in is loaded and a SolidWorks user
attempts to execute a Face Delete feature in SolidWorks. A crash will occur in
the SolidWorks product. If the SolidWorks session is started without loading the
ANSYS plug-in(s) the feature creation will proceed as normal. The ANSYS plug-
in may then be loaded and all features that follow should work as expected; in-
cluding subsequent Face Delete features. We are working with SolidWorks for a
resolution. (8966)
NX may crash when a large number of named selection are created on a part.
An example had in excess of 900 named selections and crashed NX when an
additional collection of named selections was created. Work-around: Save the
model frequently during creation of named selections. (24585)
Admin install may result in a failure of the GAMBIT Reader for non-Admin users
(more typically for Linux). Work-around: Specify a temporary directory location
with non-Admin privileges (e.g., Linux: setenv TMPDIR /tmp or Windows:
TEMP=C:\temp). (24621)
Interactive sessions of the CAD Configuration Manager will fail to start in the
Linux environment when running as a non-administrative user when a file named
CADConfigurationMgr.log exists in /tmp. Work-around: Delete /tmp/CADCon-
figurationMgr.log before launching the configuration utility, then it will work as
expected. (24696)
Specific to ANSYS Workbench, there is a known limitation with Name Selections
created in the Creo Parametric Associative Plug-In. Named Selection defined with
a name consisting of non English characters will not be translated into ANSYS
Workbench with the correct name. Work-around: Limit the name to characters
supported in the English language. (25737)
17Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
8.2. ANSYS DesignModeler
Attribute data applied to bodies of multi body parts with the Share Topology
type set to Automatic will not be transferred to downstream applications. Apply
the data to faces, edges or vertices of such bodies in order to transfer attributes
to downstream applications. (25423)
While importing models from CAD systems where the unit is specified as Microns
into a DesignModeler session which also uses Micron as the unit, the model size
is scaled incorrectly. Use a Body Operation feature to scale the model to the
correct size before continuing. (25613)
For the standard cross section types, physical properties for moments of inertia
and torsional constants reported in ANSYS DesignModeler may not be correct.
(26912)
8.3. ANSYS DesignXplorer
No known issues or limitations.
8.4. FE Modeler
No known issues or limitations.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.18
Chapter 8: Common Tools
Chapter 9: Meshing
9.1. ANSYS Meshing
In some cases when there is a vast difference between the specified global
growth rate and local growth rate, the local growth rate may not be respected.
(1744)
On Windows systems, an error message may appear in the Command prompt
window when your Windows system language is set to French and your ANSYS
Workbench language is set to US English. In such cases closing the Command
prompt window causes the Meshing application to crash. Work-around: Set
your Windows system regional and language options to US English. (3000)
In some cases the Mesh worksheet may attempt to mesh an inactive step even
if the Named Selection that the step references is invalid due to geometry sup-
pression. (18671)
The Sharp Angle Tool is not supported between baffles (0–thickness walls) in
acute angle. The feature capturing will be poor. (22044)
Virtual bodies are not supported when Physics Preference is set to Mechanical,
although the interface will permit you to insert them. Pertinent documentation
changes are detailed in the ANSYS, Inc. Documentation Errata located in the
Documentation section of the ANSYS Customer Portal. You must register and
create a password to access the ANSYS Customer Portal via the ANSYS Web site
(www.ANSYS.com). (24579)
In some cases meshing with inflation may result in poor mesh quality and/or
inconsistent expansion rates, particularly on the surface mesh. Work-around:
Set Smoothing to High and set Use Post Smoothing to No. (25443)
Assembly meshing for Mechanical models is not supported. Assembly meshing
currently only supports linear elements, and does not respect Shared topology
options for multibody parts nor non-conformal meshes between parts that are
within close proximity. As a result this meshing approach is not yet suitable for
Mechanical models and should not be used as such. You should not use any
19Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
beta 14.0 database in which assembly meshing is enabled unless Physics Prefer-
ence is set to CFD and Solver Preference is set to Fluent. If these preferences are
not set properly in a beta 14.0 database, you must manually change them before
using the database. Pertinent documentation changes are detailed in the ANSYS,
Inc. Documentation Errata located in the Documentation section of the ANSYS
Customer Portal. You must register and create a password to access the ANSYS
Customer Portal via the ANSYS Web site (www.ANSYS.com). (26231)
In cases where you connect a CFX component system to a model, open the
model in the Meshing application, and change the Solver Preference to Fluent
to activate assembly meshing, a Fluent .msh file is passed to CFX-Pre. Although
the software allows this workflow, it is not officially supported. Similarly, you
should not read or import any beta 14.0 database generated using assembly
meshing directly into CFX when running outside of ANSYS Workbench. The
database must first be converted to a Fluent .msh file. This method is also not
supported. (26264)
You cannot add an image (Standard Toolbar > Image) when the Mesh object is
selected in the Tree Outline. If you try to do so, the Image icon is inserted into
the Tree Outline. However, whenever Image is selected in the Tree Outline, the
Mesh worksheet appears instead of an image. (26821)
9.2. ANSYS ICEM CFD
The ANSYS ICEM CFD Parasolid reader (File > Import Geometry > ParaSolid or
File > Export Geometry > To Parasolid) does not work on RedHat 6 systems.
Work-around: Use the Workbench Readers option to import the Parasolid file
instead. (24822)
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.20
Chapter 9: Meshing
Chapter 10: Mechanics
10.1. ANSYS Mechanical
Explicit analyses with a Pre-Stress Initial Condition fail to solve on Linux. (18645)
Specific to the Windows XP operating system, the display of meshes containing
connectivity-coded information (i.e. the “By Connection” and “Black” options in
the Edge Coloring section of the Graphics Options Toolbar) may take longer than
on similar Windows 7 operating systems. (18930)
When using the creep models a reference length is provided to indicate the
length unit for the data input, but is missing the other required base units for
time, temperature, and force. It is required to enter the data in units which cor-
respond to the same base units that would be used by the associated unit system
in Mechanical corresponding to the reference length, and all data with temper-
ature units must be an absolute value (Kelvin or Rankine corresponding to SI or
British unit systems). (21632)
If Contact Side is set to Both in the Contact Tool and if an unaveraged result is
chosen, then results are fetched from only one of regions (instead of both re-
gions). (22805)
A Response PSD (power spectral density) analysis currently may not solve or
evaluate if the Location Method is Remote Points. Work-around: To avoid this
problem, insert an additional Response PSD probe whose Location Method is
Geometry Selection (1 Vertex). This tandem of probes should then solve or
evaluate normally. (26007)
Reaction results (force reaction and moment reaction) for any requested non-
zero phase angle will be incorrect for complex modal and harmonic analysis. To
extract the rxn forces corresponding to any phase angle or the phase angle in
which the contour results has been post-processed, you need to enter the neg-
ative value of the phase angle in the details view settings of the reaction results.
(26296)
21Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
The Analyze option in the right-mouse options menu of the Validation object
does not function on Linux platforms. Work-around: The Import option in the
right-mouse options menu of the Imported Load or Imported Thickness object
will evoke a calculation of all its child validation objects. (26753)
Typically after plotting a "Frequency Response" result, the RMB option of "Create
Contour Result from Result" is used to create the result at a frequency and phase
angle of maximum amplitude. Erroneously in release 14.0 , the generated contour
result "Phase Angle" details view was set to the same value of the phase angle
used in the "Frequency Response" result and the result generated is not correct.
It will not match with the maximum amplitude retrieved from the "Frequency
Response" result. The workaround is to change the sign of the "Phase Angle"
details view of the generated contour result. For example, if the "Phase Angle"
in detail view is -135 degree, then change it to 135 degree. (27092)
A Named Selection scoped to a Face in an explicit dynamics analysis will cause
a crash in a linked ANSYS AUTODYN system, specifically occurring when ANSYS
AUTODYN has to read modified upstream data. Named Selections scoped to
faces should be removed from the model. (26876)
10.2. ANSYS Mechanical APDL
No known issues or limitations.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.22
Chapter 10: Mechanics
Chapter 11: Remote Solve Manager (RSM)
Within the ANSYS Workbench environment, the RSM (Remote Solve Manager)
option is not supported for Electromagnetics-Fluid Dynamics coupling. (21221)
In the online help for the Remote Solve Manager, within Section 2.2.4.3. Computers
with Multiple Network Interface Cards (NIC), note the corrections below. (27024)
• The configuration files listed in Step 1 are Ans.Rsm.JMHost.exe.configand Ans.Rsm.SHHost.exe.config , not Ans.Rsm.JM-Host140.exe.config and Ans.Rsm.SHHost140.exe.config , as
documented.
• In Step 2, the second line of example code should show port="9140"instead of port="9012" .
23Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.24
Chapter 12: Fluid Dynamics
12.1. ANSYS CFD-Post
After saving the CFD-Post state in Workbench, any subsequent modifications
made to the instance definitions upstream from the Results cell will not be re-
flected in CFD-Post when reediting the Results cell. The instance definitions are
saved locally in the CFD-Post state file, and will overwrite those specified by the
results file. To ensure that the instance definitions from the results file are used,
right click on the Results cell and click 'Reset'. (2647)
If Angular Velocity is defined via an expression in CFX-Pre, the Angular Velocity
and omega expressions in CFD-Post will now show the original expression, rather
than a value. Ensure that your scripts do not rely on the results of Angular Velocity
and omega expressions being a floating-point value. (18847)
Expressions based on callbacks that refer to another expression (e.g. expression
1 = areaAve(expression 2)@Inlet) will not update their value when the second
expression changes (in this case, expression 2). Work-around: Create a variable
for the second expression and use it in the callback. (25707)
Variable 1 = expression 2 expression 1 = areaAve(Variable 1)@Inlet
In mult-domain turbo cases, streamlines may not always cross from one domain
to next. This can happen when there is no overlap between the two domains,
or when the domain interface is not modeled as an interface, but rather as out-
let/inlet pair (for example, as in ANSYS Fluent). If you want to view streamlines
in both domains in such cases, you can start the streamlines from both "inlets",
or from the inlet and the outlet, setting the Direction to be Forward and Back-
ward. (26336)
12.2. ANSYS CFD-Viewer
No known issues or limitations.
25Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
12.3. ANSYS CFX-Pre
No known issues or limitations.
12.4. ANSYS CFX-Solver Manager
No known issues or limitations.
12.5. ANSYS CFX-Solver
When running Eulerian multiphase flows with the Turbulence Dispersion Force
activated, it is recommended that you also use the Coupled Volume Fraction
(CVF) algorithm to solve the equations. Note that this is not the default option,
and needs to be explicitly selected in CFX-PRE. If you run this physical situation
with the default Segregated Volume Fraction (SVF) option, then convergence
can be poor, or the solution may converge to a slightly different result than
when running with the CVF algorithm. Work-around: Follow it by a calculation
where you switch to the CVF algorithm, restarting from the SVF results. (7367)
In some cases where the signal becomes very weak in geometries that involve
long narrow passages, an instability could occur when using the Fourier Trans-
formation model. (9931)
The steady state case used to initialize a Fourier Transformation method run
crashes in parallel with two partitions. This is probably due to the inherent stiff-
ness of the k-epsilon turbulence model in combination with the coarseness of
the mesh at some walls. To avoid this problem, it is recommended to run this
case in serial. (24418)
When using advanced multiphase physics models, such as turbulent dispersion
or solids pressure forces, convergence difficulties at GGI interfaces may be
greater than in other applications and solution errors may be greater than usual
close to the GGI interface. If possible, avoid using GGI interfaces in such applica-
tions. Using the expert parameter settings 'vfr gradient force option = 0' and/or
'virtual mass force option = 0' in addition to 'mpf ggi force flow balance = t'
might help in these situations. (25693)
12.6. ANSYS Fluent
Force mapping should not be used in ANSYS Fluent release 14.0. Please contact
ANSYS support for details and possible work-arounds. (2171)
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.26
Chapter 12: Fluid Dynamics
Specific to the Windows 7 operating system, ANSYS Fluent may fail when the
graphics window is minimized. (5642)
On Linux platforms, if ANSYS Fluent is open, an ANSYS Fluent system may not
detect an upstream mesh update until after you click Calculate in ANSYS Fluent.
(6291, 22020)
The current modeling treatment for the interaction of porous media and radiation
in ANSYS Fluent is strictly valid only for values of local fluid porosity nearly or
equal to 1.0. (7870)
Compressible (ideal and real) gas models when used in conjunction with gravit-
ational body force (buoyancy) need to employ a specified operating density
value of zero. (10302)
Stopping and starting ANSYS Fluent several times may result in the base name
used for transient calculation to increase exceptionally. (17532)
Note that unsaved settings in the Porous Zone tab of the Fluid dialog box will
be lost when Non-Equilibrium is selected from the Thermal Model list in the Heat
Transfer Settings group box. Therefore, it is recommended that you do the fol-
lowing before you enable the non-equilibrium thermal model: click OK in the
Fluid dialog box (in order to save your settings in the Porous Zone tab); then
you can reopen the Fluid dialog box proceed to define the heat transfer settings.
Note that unsaved settings in the Porous Zone tab of the Fluid dialog box will
be lost when Non-Equilibrium is selected from the Thermal Model list in the Heat
Transfer Settings group box. Therefore, it is recommended that you do the fol-
lowing before you enable the non-equilibrium thermal model: click OK in the
Fluid dialog box (in order to save your settings in the Porous Zone tab); then
you can reopen the Fluid dialog box proceed to define the heat transfer settings.
(19915)
Relevant to deformation constraints, ANSYS Fluent may fail or yield erroneous
results if the boundary settings are changed after performing an initial deforma-
tion. Work-around: Make constraint settings of the deformation region and
constraints on the initial mesh before morphing to ensure ANSYS Fluent success.
(25064)
G equation combustion models may fail on an adapted mesh during flow initial-
ization. (25522)
Serial processing is not supported for ANSYS Fluent jobs under WorkBench for
Design Point Updates if the Solution Process Update Option property is set to
27Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
ANSYS Fluent
run via the RSM under Windows HPC load manager. Work-arounds: Use the
parallel launcher settings for both the Setup and the Solution cell (i.e., use a
parallel setting of -t1 instead of running in serial). Alternatively, you can leave
the Solution cell set to run in serial via RSM to HPC, but set its Solution Process
Update Option property to Run in Foreground. (25649)
Standalone Fluent cannot be started in serial on Windows HPC load manager, if
the Use Job Scheduler property is turned on. Work-around: Use parallel setting
of -t1 instead of running serial (25649)
Specific to the Windows platform, when the injection positions are changed in
the Injections panel of ANSYS Fluent, the “Settings have changed” dialog fails
to appear. Consequently, upon closing ANSYS Fluent the x-position values are
not saved in the settings file. (25906)
A 2D axisymmetric case with the swirl option may show zero swirl after iteration
till convergence. This issue occurs with the pressure far field inlet boundary
condition. (26131)
The compatibility check for sliding mesh with relative velocity formulation is
missing in TUI. Work-around: Set the absolute formulation after executing the
TUI command "solve set numerics no yes no no no 1". (26382)
When creating a Fluid Flow (Fluent) system on the ANSYS Workbench Project
Schematic, the Setup Cell has a property of Double Precision, whereas the Solution
Cell has the Property of Single Precision, which cannot be changed. As a con-
sequence, when trying to inspect the Solution in ANSYS Fluent, once the project
is up-to-date, it will always be opened in Single Precision. Work-around: Unselect
the “Use Setup Launcher Settings” option for the Solution cell and manually
change the defaults for the Solution cell. (26677)
The Pseudo Transient Solution method should not be used with the density-
based solver when solid zones are present in the domain. (26995, 26982)
Fluent's G-equation model is not compatible with adapted meshes.
It is not recommended to execute Parameter set of RSM while running the ANSYS
Fluent application in Foreground mode.
The coupling between Ansoft and Fluent in ANSYS Workbench is not supported
on Windows Vista (32– and 64–bit), Red Hat 6, and SUSE Linux Enterprise Server
11.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.28
Chapter 12: Fluid Dynamics
Automatically compiling UDFs is not supported with mixed Windows/Linux sys-
tems (e.g., using the Use Remote Linux Nodes option from the Windows Fluent
Launcher).
12.7. ANSYS Workbench IC Engine Component System
If the Geometry, Setup, or Results cell is Reset, some of the IC Engine specific
properties are lost and have to set once again manually. Work-around:
• For the Geometry cell (Design Modeler)
1. Enable Attributes in the Properties window of the Geometry cell.
2. Append "ICEngine" to the Attribute Key string in the Properties window.
• For the Setup cell (Fluent) enable Double Precision from the Options list in
the Fluent Launcher window.
• For the Results cell (CFD-Post)
1. Set the State Initialization File location to
%AWP_ROOT140%\Addins\ICEngine\Customization\WB .cse
2. Enable Generate Report.
(21459)
In the case of engines without cylinder decomposition, after insertion of interior
layer, monitors are not updated with the newly created cell zones. Work-around:
Manually add the monitors after the interior layer insertion. (26112)
CFD-Post may exit abnormally when changing time step in some IC Engine cases.
Work-around: Perform the following steps.
1. Launch the Fluent (start > Programs > ANSYS 14.0 > Fluid Dynamics >
FLUENT 14.0)
2. Type the following command in the Fluent console: > (getenv "HOME")You will get the following output, which is the HOME path on your system:
C:/Users/user_name/AppData/Local/Temp
3. Create a file in this HOME path with the name .FLUENT (You can use
Notepad for creating this file.)
4. Copy the following lines to the .FLUENT file.
;; save the function %is-default-interior? to is-default-interior?(define is-default-interior? %is-default-interior?)
29Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
ANSYS Workbench IC Engine Component System
(define %is-default-interior? ;; replace the function %is-default-interior? to return #t for ;; interior threads automatically created during mesh-interface ;; creation. These interiors are actually nodeless zones and not ;; needed for postprocesing. ;; For all other boundaries just return the value returned by ;; original %is-default-interior? function (lambda (thread-id) (if (%is-non-conformal-mesh-interface-interior-thread? thread-id) #t ;; return true (is-default-interior? thread-id))))
(define (%is-non-conformal-mesh-interface-interior-thread? thread-id) (let ((mesh-interfaces (rpgetvar 'sliding-interfaces))) (if (pair? mesh-interfaces) ;; loop only if mesh-interfaces are defined (let* loop ((interfaces mesh-interfaces)) (let ((interiors (assq 'interior-id (car interfaces)))) (if (memv thread-id interiors) #t ;; if thread-id is found return true (if (pair? (cdr interfaces)) (loop (cdr interfaces)))))))))
5. Save the Fluent file.
6. Close ANSYS Fluent.
7. Launch ANSYS Fluent once again.
8. You should see the following lines in the console during the launch:
Loading "C:/Users/user_name/AppData/Local/Temp/.FLU-ENT" Done.
(26266)
12.8. ANSYS Icepak
Only unique names for ANSYS Icepak objects are supported when importing
geometry from ANSYS DesignModeler to avoid duplicate or skipped objects.
(19708)
The Resize Block option used to automatically resize blocks while importing
ECAD data is not supported for polygonal blocks. (23270)
Grilles, fans, heat exchangers, thin conducting plates and networks are not per-
mitted to intersect/touch zero slack assemblies. (26837)
12.9. ANSYS POLYFLOW
No known issues or limitations.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.30
Chapter 12: Fluid Dynamics
Chapter 13: Explicit Dynamics
13.1. ANSYS Explicit
No known issues or limitations.
13.2. ANSYS AUTODYN
AUTODYN models that contain either the MO Granular or the slowburn material
model will result in a premature end of a parallel analysis. In serial analyses these
material models can be used, but in parallel analysis the use of the MO Granual
or slowburn material model should be avoided. (25986)
Using the Examine option in the ANSYS AUTODYN standalone GUI on NBS, tet-
rahedral elements may result in an ANSYS AUTODYN failure. (26057)
When running a 2D axial symmetry simulation containing rigid bodies, user might
experience an early end of calculation due to an energy error. The accounting
of the WORK done is incorrect for those 2D axial symmetry simulations. Work-
around: Continue the simulation is to ignore the check on energy. (26339)
13.3. ANSYS LS-DYNA
No known issues or limitations.
31Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.32
Chapter 14: Turbo Systems
14.1. ANSYS BladeModeler
For the Quasi-Orthogonal Area Graph, in some special cases involving sharp
bends in the hub or shroud, the Quasi-Orthogonal Area with the blades can give
incorrect results. This is the case regardless of the flow angle correction. The area
curves without the blades are not affected by this defect. (2334)
14.2. ANSYS TurboGrid
When running ANSYS TurboGrid in ANSYS Workbench, it is recommended to
not unparameterize an expression that has been parameterized. Choosing to
Deselect as Workbench Parameter on an expression that was previously selected
as a Workbench parameter will cause errors to be reported in ANSYS Workbench.
While the expression in ANSYS TurboGrid will no longer be connected with a
Workbench parameter, the parameter will still exist in Workbench. In the case
of an Output Parameter, its value will no longer be updated even though it may
be marked as up-to-date. (26534)
14.3. ANSYS Vista TF
Vista TF does not support simultaneous update of design points via the Remote
Solve Manager. If updating design points for Vista TF via RSM, the Design Point
Update Process Job Submission property must be set to One Job for All Design
Points in order for the update to succeed. (25938)
33Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.34
Chapter 15: Offshore
15.1. ANSYS ASAS
No known issues or limitations.
15.2. ANSYS AQWA
No known issues or limitations.
35Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.36
Chapter 16: Simulation Process and Data
Management
16.1. ANSYS EKM Desktop
If an error occurs when a Command Journal Script is executed, it is shown as an
unhandled exception instead of a user-friendly error message. Clicking "Continue"
when such an exception occurs will allow you to dismiss the exception and go
back to the object from where the script was executed. (16328)
Clicking the validation expression multiple times successively while editing a
validation expression of a node in Workflow editor, may result in the Edit Expres-
sion Dialog being hidden behind the Studio window. Work-arounds: Use Alt+Tab
to return to Edit Expression Dialog; or click on Studio in Windows taskbar twice
to make Edit Expression Dialog appear again. (26047)
File transfers from EKM Desktop to a cache server that take longer than the
server's configured HTTP session time-out will cause subsequent transfers to fail.
(26229 )
Selecting the links displayed in the Simulation Details report results in the error
message "Object that you are referencing no longer exists." (26491)
37Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 14.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,Inc. and its subsidiaries and affiliates.38