ANSYS Fluent supports the following capabilities when used in a System Coupling analysis:
Force and displacement data transfers on wall boundaries (including walls in sliding mesh zones), porous jump boundaries, and porous zone interfaces:
Input of incremental displacements data from System Coupling allow moving and deforming mesh specification on boundary wall regions (including walls in sliding mesh zones), porous jump boundaries, and porous zone interfaces (via a zero-thickness porous jump boundary). Note the additional System Coupling option in the Dynamic Mesh Zones dialog box; see Specifying the Motion of Dynamic Zones for more information.
Output of force data on boundary wall regions (including walls in sliding mesh zones), porous jump boundaries, and porous zone interfaces (via a zero-thickness porous jump boundary). Fluent is able to serve the total force variable (viscous and normal) on all wall boundaries (with or without enabling the System Coupling option in the Dynamic Mesh Zones dialog box). See Variables Available for System Coupling for details about the forces transferred from the wall and porous jump boundaries.
Thermal data transfers on wall boundaries:
Input of temperature data and heat flow data from System Coupling on all wall boundaries. Note the additional via System Coupling option in the Thermal tab of the Boundary Conditions dialog box.
Output of temperature data, heat flow data, and heat transfer coefficient data to System Coupling on all wall boundaries (with or without enabling the System Coupling option in the Dynamic Mesh Zones dialog box).
Data transfers from wall boundaries that are in Fluent sliding mesh zone or rigid body zone.
The use of triangular and quadrilateral faced interface cell types.
Full dynamic mesh support everywhere except on coupling interface.
Full support for local and distributed parallel solver execution.
Convergence data for all equations (for example, continuity, momentum, and energy convergence data) is shared with the system coupling service at run time. Monitor data is shared if the monitor point has an iteration frequency set. If the monitor point has a time step frequency set, monitor data will not be shared with System Coupling.
This data from Fluent can be charted in conjunction with other data in the system coupling chart at all available intervals. Intermediate data points are not artificially created in the system coupling chart.
Monitor data can also be plotted in Fluent Solution Monitoring.
Note the following limitations when using Fluent in a System Coupling analysis:
Using System Coupling with the Remote Solver Manager (RSM) in Fluent is not supported. If attempted, you will receive the following message:
Solution updates for Fluent systems participating in System Couplings must run in the foreground. This change has been automatically applied.
When using a wall and wall-shadow pair in Fluent as System Coupling interfaces, you'll need to create a duplicate surface in Mechanical. These will be paired with two sets of shell elements in Mechanical. For more information, see Coupling with Wall/Wall-Shadow Pairs or Thin Surfaces in the ANSYS Mechanical User's Guide.
System Coupling requires participants to use 3D meshes, with data transfer regions consisting of element faces within the 3D mesh. Data Transfer regions cannot exist in 2D meshes (where the data transfer region would be a line/curve).
System Coupling does not support data transfer regions on polyhedral meshes, and the coupling interface’s mesh cannot have hanging nodes (which result from hanging node adaption and may occur in some CutCell meshes).
The mesh topology on a System Coupling boundary in Fluent must remain fixed for the duration of the analysis. This means that dynamic remeshing cannot be used on the System Coupling boundary, but interior nodes away from the System Coupling boundary can still be remeshed during the solution.
To transfer forces on wall and wall-shadow pair, you need two surfaces in Mechanical to match the two surfaces in Fluent. In this case, you cannot use a single set of shell elements in Mechanical. An example of a wall and wall-shadow pair is two different fluids on either side of a zero-thickness internal wall in Fluent.
The non-iterative time-advancement (NITA) scheme in Fluent cannot be used in a System Coupling analysis.
When executing design points for System Coupling cases where Fluent is a participant, Program Controlled should not be used for Fluent Initialization Method.
Shell conduction is not available when the Fluent region is set up to receive thermal data via System Coupling.
Note: In order to have changes made in Fluent systems propagated to downstream System Coupling systems, save your project, synchronize with Workbench, or close Fluent. This will ensure that the information passed to System Coupling matches settings in Fluent. If this is not done, the analysis may be allowed to run but the following Workbench state error will be issued at the end of the run:
Update of the Solution component in System Coupling failed: Update of the Solution component in System Coupling did not mark container as updated (final state is OutOfDate).