Beruflich Dokumente
Kultur Dokumente
5 Release
Release 14.5
Outline
Coupling Overview
This lecture starts by describing how the FSI coupling process works. The main features and capabilities are then discussed along with the current limitations.
Workflow Overview
This section provides a high level view of the FSI workflow for a simple 2-way FSI analysis
Release 14.5
Coupling Overview
Simulations involving multiple physics requires solution of multiple fields Fields are coupled: solution data from one field is required by one (or more) other field Fluid Dynamics Solid Mechanics
Structural Mass Momentum Turbulence Thermal Heat Transfer
3 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Coupling Overview
CFX solves Mass and Momentum in a single matrix (fully coupled) Other fields (Turbulence, Heat Transfer, ) are solved in a segregated manner Iterations are required to convergence sequentially (segregated) solved fields
Release 14.5
Coupling Overview
MAPDL solver usually solves Structural OR Thermal fields Multifield (MFS) solver can couple fields in a segregated manner in MAPDL Fluid Dynamics Solid Mechanics
Structural Mass Momentum Turbulence
MFS
Thermal
Heat Transfer
5 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Coupling Overview
The MAPDL solver can also couple fields using a fully coupled approach
Heat Transfer
6 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Release 14.5
MFX
OR
Thermal
MFX
Heat Transfer
Release 14.5
MFX
Turbulence
Heat Transfer
9 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Iterative Coupling
Iterations are required to converge the quantities transferred between the MAPDL and CFX solvers Just like iterations are required to converge segregated fields
within the CFD or FEA solvers
Turbulence
Heat Transfer
10 2011 ANSYS, Inc. July 26, 2013
Release 14.5
End Field Loop End Coupling / Stagger Loop End Time Loop
11
Release 14.5
Iterative Coupling
Time Loop Coupling Loop Field Loop
Field loop iterations stop when the field reaches its convergence target (or Max Iterations/Time Step in Fluent)
The CFX field loop does not need to be converged every Coupling Iteration, only by the end of the last Coupling Iteration
Coupling loop iterations stop when the forces / displacements reach their convergence targets or max number of Coupling Iterations
End Field Loop End Coupling Loop End Time Loop Ensure the individual field solvers AND the forces / displacements are converged before starting the next time step
E.g.: CFX set to 10 iterations/time step, System Coupling set to 5 Coupling Iterations and 100 time steps are solved. CFX could perform a total of 10*5*100 = 5,000 iterations in total if convergence is poor
Release 14.5
12
13 2011 ANSYS, Inc.
Release 14.5
14
Release 14.5
Workbench based setup and execution Windows 32/64-bit, Linux 64-bit Command line execution outside of Workbench Can use separate machines and mix Windows, Linux Can use MAPDL to create the structural model Solver data transfer across standard sockets (TCP/IP) Third Party Coupling Scheme Not Required Efficient, no intermediate files Takes place in memory (RAM)
July 26, 2013
15
Release 14.5
Many Mechanical features based on newer contact elements (CONTA17*) are not supported Work-arounds discussed later
16
Release 14.5
Cases requiring transient rotor-stator can be solved with MFX/CFX but cases requiring FSI regions in sliding mesh zones cannot be solved with SC/Fluent
2011 ANSYS, Inc. July 26, 2013
17
Release 14.5
Outline
Coupling Overview
This lecture starts by describing how the FSI coupling process works. The main features and capabilities are then discussed along with the current limitations.
Workflow Overview
This section provides a high level view of the FSI workflow for a simple 2-way FSI analysis
18
Release 14.5
Workbench Workflow
Standard WB workflow for 2-way FSI Drop a CFX system onto the Setup cell of a Transient Structural system
19
Geometry is shared by default Fluid and structural meshes are created separately CFX Solution cell controls the FSI simulation Structural Solution not used for FSI, but can be used to check the structural model
July 26, 2013
Release 14.5
20
Release 14.5
Workflow Overview
Mesh fluid region
21
Release 14.5
Workflow Overview
Run in the CFX Solver Manager
22
Release 14.5
Export the fluid mesh, then run CFX outside of WB, providing the fluid mesh and the Mechanical Input File. Alternatively, connect to a CFX system then pull the .cfx file outside of WB
23 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Outline
Coupling Overview
This lecture starts by describing how the FSI coupling process works. The main features and capabilities are then discussed along with the current limitations.
Workflow Overview
This section provides a high level view of the FSI workflow for a simple 2-way FSI analysis
24
Release 14.5
Geometry Considerations
Helpful to use a single CAD file containing both the fluid and solid regions Ensures that FSI interface region lines up Fluid geometry/mesh may need to include fillets if present in the
solid Small mismatch OK ~ half the local element edge length
Can import separate CAD files into DesignModeler and move / transform as necessary Consider if the fluid bodies should be split to control mesh
motion or if subdomains are needed
25
Release 14.5
Geometry Considerations
To use shell elements in Mechanical, make a Surface body in DM Given a fluid body, use Create > Thin/Surface with zero thickness When you select a face, the side with the positive surface normal is highlighted in green Force passed to Mechanical is a vector, so the surface normal
direction doesnt matter, but...
26
Release 14.5
Geometry Considerations
Shell element assume the nodes are at the mid-plane of the true geometry Forces from a Fluid Solid Interface will be
applied at the mid-plane by default Negligible error for thin geometries
Outward pointing normal
Correct interpretation of the physics is given by using Offset Type Offsets the shell element nodes to the top
or bottom of the thickness In the pipe example shown, assuming internal flow with outward pointing normals, use Offset Type = Bottom
Locates the nodes at the true Fluid Solid Interface
27 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Meshing
When meshing the fluid, suppress the solid region in Meshing And visa-versa Interface mesh does not need to match Force still locally and globally conservative Similar mesh length scales will maintain the
load transfer resolution
Solid
Fluid
Solid
Difference in element normal Fluid directions across interface can produce twisting on coarse meshes with surface curvature Force vector is transferred to the solid, Create a matching mesh if necessary... but does not act normal to the solid
elements results in a twisting force
28 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Meshing
Matching interface mesh mesh the fluid and solid parts together, using a single Part The structural Model cell contains the fluid & structural bodies in one Part Mesh both fluid and solid regions in the Mechanical Model, then use File
> Export to write out a Fluent mesh (.msh) Suppress the fluid region, continue with the Mechanical Model definition Import the Fluent mesh into CFX-Pre in a CFX Component System
29
Release 14.5
Meshing
It is also possible to create fluid and solid meshes outside Workbench (e.g. ICEM) Import the fluid mesh into CFX-Pre manually Import the solid mesh into Finite Element Modeler, then connect
to a Mechanical system:
Fluid and solid meshes can be created together if necessary so that nodes match at the interface Meshing the fluid volume then extracting the surface mesh to
use as a Mechanical shell mesh is also possible
30 2011 ANSYS, Inc. July 26, 2013
Release 14.5
Summary
The MFX solver allows fields solved in different solvers to be coupled together
For 2-way FSI analyses iterations are typically used between the solvers within each time step so that the forces/displacements can converge at that time step
The workflow involves identifying boundary regions in Mechanical and CFX that will send/receive data. All coupling settings are defined in CFX-Pre in Workbench. The fluid and structural geometries should physically match at the FSI interface An offset may be required when using shell elements Poor mesh resolution on curved surfaces can lead to errors in the force transfer. Use of a matching mesh avoids this.
31
Release 14.5