When you create data transfers in System Coupling, certain rules must be observed in order to correctly define the analysis.
Note: Participant data transfer regions must consist of triangular or quadrilateral faces. Polyhedral faces as well as faces with hanging nodes (cut-cells) are not supported in System Coupling.
Currently, the following three types of transfers are supported in System Coupling. Details of these three types of transfers are given in Table 2: Data Transfers available in System Coupling.
Force transfers
Motion transfers
Thermal transfers
Use the links in Supported System Coupling Participants to review the data transfers that are supported for the specific participant systems you are coupling though System Coupling.
Force and motion transfers are typical for fluid-structure interaction problems, where a load to the structure is transferred from a fluid solver, and the deformations to the fluid are transferred from the structural solver. There can only be one force transfer and one motion transfer for each data transfer region.
Thermal transfers can be transferred between ANSYS Fluent and ANSYS Mechanical directly through System Coupling, or through the coupling of the External Data system. Three thermal transfers are available, each transferring different thermal variables. The three thermal transfers are described in the table below.
For one-way thermal transfers, only one of the three options below for thermal transfers can be defined for a given pair of source and target regions.
For two-way thermal transfers, two data transfers are set up on the same data transfer region. In a two-way transfer:
the two variables, heat transfer coefficient and near wall temperature, cannot be transferred on the same data transfer region as heat flow, and
a participant’s data transfer region cannot provide and receive the same thermal variable(s); for example, Fluent cannot send and receive temperature data on the same data transfer region.
Table 2: Data Transfers available in System Coupling
|
Transfer Type |
Variable(s) Transferred |
Data Transfer Direction | |
|---|---|---|---|
|
Force transfer |
Force (VectorXYZ*) |
from a fluid solver to a structural solver | |
|
Motion transfer** |
Incremental displacement (VectorXYZ*) |
from a structural solver to a fluid solver | |
|
Thermal Data Transfers |
1. Temperature transfer |
Temperature (Scalar) |
|
|
2. Heat flow transfer |
Heat flow (also known as heat rate) (Scalar) |
| |
|
3. A pair of variables*** |
|
from a fluid solver to a structural solver | |
* Represents the force vector (
,
,
) and the incremental displacements vector
(
,
,
)
respectively.
**In a general coupled analysis, when the solver receiving the
motion (such as Fluent) solves before or simultaneously to the solver
sending the motion (such as Mechanical), then the incremental displacement
transferred during the first coupling iteration of each coupling step
is identically zero. This behavior can be changed by using GeneralAnalysis_IncrDisp_InitIterationValue_Zero in
the Expert Settings.
***You must correctly define both variables in the data transfer in order for this thermal transfer to be valid.
Note: For a given target region, there can only be one source region. However, a given source region can send data to multiple target regions. In other words, 1-to-M data transfers are supported, where M is an integer and is greater than or equal to 1. Note that M-to-1 data transfers are not supported.