CFX FSI 14.5 2011 L1 Overview of FSI in Workbench 37

Lecture 1
Overview of FSI in Workbench

14. 5 Release
Solving FSI Applications Using

ANSYS Mechanical and ANSYS CFX
1 2011 ANSYS, Inc. July 26, 2013 Release 14.5
Outline
Introduction to the Workbench Environment
Here well provide an introduction to the basic operations in
Workbench and the Project Schematic, including connecting systems in
Workbench.
Modeling Approaches for FSI

This section discusses the different types of FSI problems and
approaches to solving them.
FSI Workflows in Workbench

Here well present an overview of the different types of FSI workflows
you may want to use in Workbench, including co-simulation and
various approaches for static data transfers.

ANSYS Workbench
ANSYS Workbench is a project-management tool. It can be considered as
the top-level interface linking all our software tools.
Workbench handles the passing of data between ANSYS Geometry / Mesh /

Solver / Postprocessing tools.
This greatly helps project management. You do not need worry about the
individual files on disk (geometry, mesh etc). Graphically, you can see at-a-
glance how a project has been built.
Because Workbench can manage

the individual applications AND
pass data between them, it is easy
to automatically perform design
studies (parametric analyses) for
design optimisation.
2012 ANSYS, Inc. July 26, 2013 3 Release 14.5

Workbench Overview
The options visible in the Analysis Systems are ready-
Toolbox show all the made stencils that include all
products (systems) you the individual systems
have licenses for. (applications) needed for
common analyses (for example
TIP: If this list appears Geometry + Mesh + Solver +
empty, you have a Post-Processor)
problem with your
licensing!
Component Systems are the
individual building-blocks for
each stage of the analysis
Design Exploration
provides tools for
optimising designs and
understanding the
parametric response.

Basic Workflow
Dragging an Analysis System onto
the Project Schematic lays out a
workflow, comprising all the steps
needed for a typical analysis.
Workflow is from top to bottom.

As each stage is complete, the icon
at the right-hand side changes

Alternative Workflow
However, an analysis could equally well be prepared by selecting

the individual Component Systems that are needed for this
analysis, and then linking them together with connectors.
TIP: There are two ways to create the connectors between the
systems:
1) Use the mouse to draw a line (eg A2 to B2, B3 to C2 etc)
2) Or, simply drop the new system on the cell of the upstream one,
and the link will be generated automatically.

Cell States
As each stage in the model-build is completed, the state
of the cell changes.
Icon Meaning
Up to Date
Refresh required. Upstream data has changed
Status after creating
Geometry in A2, not yet Update required. Local data has changed
opened mesh in A3 Unfulfilled. Upstream data does not exist
Attention Required
Solving
Update Failed
Update Interrupted
Changes pending (was up-to-date, but upstream
Status after model has data has changed)
converged, waiting for
post-processing
Sharing Data between Different Solvers
Workbench can be used to transfer data between solvers. In this 1-way FSI (fluid-
structure-interaction) example, we transfer the loads from a Fluent CFD simulation
over to a Mechanical system to perform a stress analysis
The square connector shows The round connector shows

that the geometry created that the CFD results are
in cell A2 (CFD model) is being transferred as a Setup
being shared with cell B3 (input) condition to be used
(FEA model). for FEA stress analysis.
File Location on Disk
Should you need to identify the individual files on your disk for each stage of the
project, these can be found by enabling View > Files. The resulting table will cross-
reference the directory and filename with the project cells.
Filename Directory

Use of Archive / Restore
The workbench project comprises many files and directories. If you need to
either archive the project, or bundle it to send to us for a Technical Support
query, use the Archive tool. This generates a single zipfile of the entire project.
When archiving, you can

choose whether to include
the computed result files or
not (omitting these may
make it small enough to send
by email)

Working with Parameters / Refresh and Update
To make changes, you can manually open up a component cell (e.g. geometry)
Or: most Workbench applications will let you specify key quantities as a parameter. A
new object Parameter Set appears on the Project schematic.
You then need to update your model. From Workbench you can choose to then update
the entire project, or just a single cell.
Refresh: Reads upstream data, but will not do any lengthy operation like solving or meshing.
Update: Performs both a Refresh, AND generates the new output
2] Update Project will then work through
each component in turn (geometry > mesh
> solver ) to compute the new design point.
3] However you may want to update an

individual component (eg to preview the
new geometry before proceeding).
Right-click on an individual cell.
1] Clicking here will let you modify the

parameters centrally, without having to
open the individual application.
License Preferences
Workbench license control is handled through the user interface
shown below, activated from the Workbench project page (Tools >
License Preferences . . . ).

License Preferences
With the available licenses displayed, the activation and use
order can be specified using the up/down arrows.
0 = off, 1 = on
License order represents the preference order for license use
The license control allows Workbench users

to specify whether a single license is used
when multiple applications are open, or if all
open applications access their own license.

License Preferences
In the example shown, you could have 3 Mechanical models open
simultaneously. Using the license control you may choose to open 3 licenses or
use only 1 that is shared. In the shared scenario, only the active Mechanical
session uses the license (the remaining will be read only).

Summary
ANSYS Workbench is a convenient way of managing your simulation projects.
Workbench is used to launch the individual software components, and used to

transfer data between them.
It is easy to see at-a-glace how a model has been built, and determine which files
were used for a particular simulation (pairing geometry files to solver runs)
Workbench also makes it straightforward to perform parametric analyses (without

the user needing to manually launch each application in turn), and makes it easy to
simulate multi-physics scenarios like fluid-structure interaction.

Outline
Workbench.



Fluid Structure Interaction (FSI)
What is Fluid Structure Interaction?
Occurs when a fluid flow interacts with a solid structure / bodies
Flow may exert pressure and / or thermal loads
These may cause structural deformations significant enough to change
the fluid flow itself (2-way interaction)
Or the deformations may be neglected on the fluid side (1-way)
Solid may deform or move due to external forces, driving the
fluid flow, or exert thermal loads on the fluid
Again, 1-way and 2-way interactions are possible
Why is FSI important?

Crucial in understanding many engineering problems
Material selection, fatigue, effect on fluid flow and structural
parameters etc.
For better designs!

Modeling Approaches
FSI can be categorised by the degree of physical

coupling between the fluid and solid solution fields
How sensitive is one field to a change in the other field?
Fields that are strongly coupled physically require strong

numerical coupling
Generally more difficult to solve
Solution fields that are relatively independent can be

solved with weaker coupling or even uncoupled (1-way)

Modeling Approaches
Physical
Coupling
Biomedical,
Strong
membranes, highly
Very
deformable solids,
Vortex induced vibrations,

Strong
Blade deformations, rigid bodies,

Weak
CHT, small deformations (excluding turbulence induced),
Numerical
1-way 2-way Coupling
(uncoupled)
Explicit Implicit
Iterative
Fully Coupled
Modeling Approaches
Physical
Coupling Fully Coupled
Fluid and Solid equations solved in aBiomedical,
single monolithic
Strong
matrix membranes, highly

Very
deformable solids,
Like Mass and Momentum in CFX, or coupled field elements in
the Mechanical solver Flutter, water hammer,
Fields remain very tightly coupled
Strong
But very difficult

Bladeto solve a monolithic
deformations, fluid-structure
rigid bodies,
matrix
Not available with Mechanical CFX coupling
Weak
Numerical
(uncoupled)
Explicit Implicit
Iterative
Fully Coupled
Modeling Approaches
Physical
Coupling 2-way Iteratively Implicit
Fluid and Solid equations solved separately
Biomedical,
Strong
membranes, highly
Very
Just like Turbulence is not fully coupled to Momentum

deformable solids, in CFD
Usually separate solvers too
Iterate within each time Flutter,
step to water hammer,
obtain an implicit
Strong
solution (stagger loops)

Used in Mechanical CFX rigid bodies,
Blade deformations,
Weak
Numerical
(uncoupled)
Explicit Implicit
Iterative
Fully Coupled
Modeling Approaches
Physical 2-way Explicit
Coupling
Same as previous except no iterations between the fluid
and solid fields within a time step Biomedical,
Strong
membranes, highly
Very
Solid solution is based on fluid field fromsolids,

deformable the previous

time step
Flutter,
Or visa-versa depending who water
solves hammer,
first
Strong
Can be done in Mechanical CFX by using a single

Blade deformations, rigid bodies,
coupling iteration
Usually not recommended
CHT,
Generally requires much smaller
turbulencetime steps
Weak
small deformations (excluding induced),
Numerical
(uncoupled)
Explicit Implicit
Iterative
Fully Coupled
Modeling Approaches
Physical
Coupling 1-way
A converged solution is obtained forBiomedical,
one field, then used
as a boundary condition or external load for the second
Strong
membranes, highly
Very
field deformable solids,
Suitable for weak physical coupling

Flutter, water hammer,
E.g. Determining maximum structural stresses from CFD
Strong
results, but strains are not significant enough to affect CFD

results Blade deformations, rigid bodies,
Easily done in Mechanical CFX

Automated data transfer
Weak
Numerical
(uncoupled)
Explicit Implicit
Iterative
Fully Coupled
Implicit vs Explicit
Implicit and Explicit approaches in the context of the FSI

coupling is not to be confused with an implicit solver
or an explicit solver
The term implicit/explicit solver refers to whether an
implicit/explicit formulation is used for the transient terms in
the equations
In the context of FSI couplings:
Explicit means the fluid and solid fields are solved separately but
there are no coupling iterations within a time step
Implicit means the dependencies between the fluid and solid
fields are converged within a time step
By using Coupling Iterations = Iteratively Implicit
By using a single fluid-solid matrix = Fully coupled (and naturally
implicit)
Implicit vs Explicit
When considering an explicit approach we should be

confident that the coupling is weak and/or the time
scales small enough that we will get the right answer on
the first coupling iteration
When using an implicit approach we assume we are not
going to get the right answer on the first coupling
iteration (as a result of the flow physics or time scales)
We therefore rely on iteratively updating the problem until the
FSI interface quantities converge
Implicit solutions can be more robust and use larger time steps
ANSYS uses the iteratively implicit approach

Outline
Workbench.



FSI Options in Workbench
Multiple workflows are available in Workbench. Can split into:

Static Data Transfers
CFX/Mechanical runs to completion, then results are used to generate
loads/boundary conditions for Mechanical/CFX
Always a 1-way transfer
Co-simulation
CFX and MAPDL solvers run simultaneously exchanging data
Could be 1-way or 2-way
To decide the best workflow for your case, ask the following:
Is the data transfer 1-way or 2-way?
Is the case transient or steady-state?
Do I need to pass force/displacement or thermal data?
Which WB workflow fits my project workflow best?
Co-simulation
Supports surface Force and/or Displacement coupling
Supports surface Temperature / Heat Flow coupling
Requires command objects in Mechanical
1-way or 2-way
Steady-state or Transient
Typically setup in a single Workbench project
Can setup individually and run outside Workbench or from the command line

CFD - CHT
Multiple workflows
Direct Project Schematic Connections (CFD-
Post interpolation)
External Data Connection to Mechanical
Manually export loads/profiles from CFD-
Post
Thermal
Loads
Always a 1-way transfer
But can perform a series of 1-way transfers
to get a steady-state 2-way result
Thermal
Stress

Direct Project Schematic Connection
Supports surface Force, Temperature and HTC from CFD to Mechanical

Thermal systems
Supports volumetric Temperature from CFD to Mechanical Structural
systems
Steady state only (Transient via Application Customization Toolkit)
Does not support Displacement transfer from Mechanical to CFD
Automated and persistent workflow in a single WB project

External Data Connection to Mechanical
Connects to Mechanical systems only
Supports volumetric/surface
Temperature, Pressure (force vector),
HTC, Heat Flux, volumetric Heat
Pressure in CFD Generation, Shell Thickness and
Displacementb
Source files for External Data can be
exported from CFD-Post or any other
package (or text editor/spreadsheet)
Steady or Transient
Easy to use via the Workbench
schematic
Must re-export and re-read files in
External Data after making a change
Deformation in Mechanical
Manual Export from CFD-Post
Use CFD-Post to map data onto a
Mechanical mesh, then export a
load file
The direct Project Schematic connection
does this automatically
May want to do this manually if you are
using MAPDL
Supports the same data transfer as the
direct schematic connection
Can also export Displacements from
Mechanical results for use in CFX
Workflow is not automated or persistent

Rigid Bodies
Simpler FSI approaches are possible when simplifying
assumptions can be made
If the solid moves but does not deform (rigid body), then a 6-Degree of
Freedom rigid body solver can be used
Rotation about 3 axes, translation along 3 axes = 6-DOF
A 6-DOF rigid body solver is available in CFX
This gives a 2-way explicit or implicit solution
Depending on whether the solid body position is
updated once or multiple times per timestep
More efficient than using a full FEA solver
No structural solution field
Examples: Boats in waves, falling objects

Rigid Bodies
Boundary motion imposed via the 6-
DOF solver results in mesh deformation
Large displacements may result in poor
mesh quality or the mesh may collapse
Automatic re-meshing is one possibility,

the Immersed Solid approach is another
Used when mesh deformation is not practical
Fluid mesh remains stationary
Solid motion can be specified or calculated by
the 6-DOF solver
Limited boundary layer resolution; single
phase, incompressible only

Deforming Solids
When the solid motion is known (or
easily calculated) it can simply be
imposed on the wall boundaries using
Moving Mesh capabilities
E.g. Pistons, Actuators, 1-DOF motion
Boundary motion can be described by CEL
expressions or User FORTRAN

Other ANSYS FSI Solutions
Rocket Propelled Grenade on
ANSYS AUTODYN Carbon Firer Reinforced Wing
Explicit 2-way approach

Uses very small time steps
Suitable for predicting small time scale
phenomenon
Blast wave propagation and its impact on
surrounding structures
Impacts
Drop tests
Mechanical FLUENT FSI

1-way structural and thermal FSI
2-way structural FSI using System
Coupling in Workbench Steady State 2-way
Aeroelastic Deformation

Summary
The aim of this lecture was to provide an overview of the
Workbench environment, including how to add and connect
systems in the Project Schematic
You should understand how a basic workflow proceeds from
start to finish.
You should be aware of the different methods for performing
FSI simulations in Workbench
Co-simulation is used for all 2-way simulations but can also be
used for 1-way FSI, particularly if transient data transfer is
required
Various methods are available for static data transfers. The
best approach will depend on your preferred workflow and
the data you wish to transfer. More details for each method
will be presented during this training course.

CFX FSI 14.5 2011 L1 Overview of FSI in Workbench 37

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CFX FSI 14.5 2011 L1 Overview of FSI in Workbench 37

Transféré par

Droits d'auteur :

Formats disponibles

Lecture 1

Overview of FSI in Workbench

Solving FSI Applications Using

Modeling Approaches for FSI

FSI Workflows in Workbench

2 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Workbench handles the passing of data between ANSYS Geometry / Mesh /

Because Workbench can manage

2012 ANSYS, Inc. July 26, 2013 3 Release 14.5

2012 ANSYS, Inc. July 26, 2013 4 Release 14.5

Workflow is from top to bottom.

2012 ANSYS, Inc. July 26, 2013 5 Release 14.5

However, an analysis could equally well be prepared by selecting

2012 ANSYS, Inc. July 26, 2013 6 Release 14.5

The square connector shows The round connector shows

2012 ANSYS, Inc. July 26, 2013 9 Release 14.5

When archiving, you can

2012 ANSYS, Inc. July 26, 2013 10 Release 14.5

3] However you may want to update an

1] Clicking here will let you modify the

12 2011 ANSYS, Inc. July 26, 2013 Release 14.5

The license control allows Workbench users

13 2011 ANSYS, Inc. July 26, 2013 Release 14.5

14 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Workbench is used to launch the individual software components, and used to

Workbench also makes it straightforward to perform parametric analyses (without

15 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Modeling Approaches for FSI

FSI Workflows in Workbench

16 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Why is FSI important?

17 2011 ANSYS, Inc. July 26, 2013 Release 14.5

FSI can be categorised by the degree of physical

Fields that are strongly coupled physically require strong

Solution fields that are relatively independent can be

18 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Vortex induced vibrations,

Blade deformations, rigid bodies,

CHT, small deformations (excluding turbulence induced),

matrix membranes, highly

But very difficult

CHT, small deformations (excluding turbulence induced),

Just like Turbulence is not fully coupled to Momentum

solution (stagger loops)

CHT, small deformations (excluding turbulence induced),

Solid solution is based on fluid field fromsolids,

Can be done in Mechanical CFX by using a single

small deformations (excluding induced),

field deformable solids,

Suitable for weak physical coupling

results, but strains are not significant enough to affect CFD

Easily done in Mechanical CFX

CHT, small deformations (excluding turbulence induced),

Implicit and Explicit approaches in the context of the FSI

When considering an explicit approach we should be

25 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Modeling Approaches for FSI

FSI Workflows in Workbench

26 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Multiple workflows are available in Workbench. Can split into:

28 2011 ANSYS, Inc. July 26, 2013 Release 14.5

29 2011 ANSYS, Inc. July 26, 2013 Release 14.5

Supports surface Force, Temperature and HTC from CFD to Mechanical

30 2011 ANSYS, Inc. July 26, 2013 Release 14.5