This chapter describes the ANSYS Multi-field solver - multiple code coupling (MFX), available for a large class of coupled analysis problems. The MFX solver is one of two versions of the ANSYS Multi-field solver. See The ANSYS Multi-field™ Solver - MFS Single-Code Coupling for a description of the other version, the MFS solver). The MFX solver is used for simulations with physics fields distributed between more than one code running on one or more machines. Thus, this solver can accommodate more physically complex and larger models than the MFS version.
In the MFX solver, a "field solver" is each running instance of the different codes. These field solvers are coupled using stagger iterations. During each iteration, every field solver collects loads from the other field solvers and proceeds to solve its own physics fields. Iterations continue until all physical field solutions and loads converge. The coupling between field solvers running on potentially different machines is accomplished using a client/server based communication protocol over standard internet sockets. No third party software is required, allowing for maximum flexibility and extensibility.
The MFX solver is primarily intended for fluid - structure interaction (FSI) analyses (including conjugate heat transfer). Typical applications include:
Biomedical applications (i.e., drug delivery pumps, intravenous catheters, elastic artery modeling for stent design)
Aerospace applications (i.e., airfoil flutter, turbine engines)
Automotive applications (i.e., under hood cooling, HVAC heating/cooling, heat exchangers)
Fluid handling applications (i.e., valves, fuel injection components, pressure regulators)
Civil engineering applications (i.e., wind and fluid loading of structures)
Electronics cooling
If you are not familiar with the ANSYS Multi-field solver, read the ANSYS Multi-field solver discussion before using MFX. You must also be familiar with CFX.
MFX analyses require setting up the field solver controls. You can perform these setup tasks using ANSYS or using ANSYS CFX in standalone mode or ANSYS CFX Workbench mode. See the CFX Release 18.2 Introduction for information on launching ANSYS CFX in the different modes.
This chapter describes how to do a fluid-structure interaction analysis using the MFX solver.
To use the MFX solver, your analysis must meet the following requirements:
The analysis must be three-dimensional.
The ANSYS model must be single-field and the elements involved in load transfer must be 3-D with either structural or thermal DOFs.
Only surface loads are transferred. Valid surface loads are displacement, temperature, force and force density, heat flow, and heat flux.
Only two field solvers, one ANSYS and one CFX, can be coupled. A given analysis can have only one coupling between two field solvers, but it can have multiple load transfers.
The ANSYS field cannot be distributed, but the CFX field can use CFX's parallel processing capabilities. A CFX field being solved using parallel processing is still considered a single field solver.
The analysis must be a batch run.
CONTA171 through CONTA177 elements with the multipoint constraint (MPC) feature (KEYOPT(2) = 2) are invalid for the MFX solver.
The following terms are used throughout this chapter:
A field solver refers to a specific instance of an ANSYS or CFX solver execution that is defined by the respective input file(s) referenced when starting the solver. The field solver names that are referenced in several MFX commands must be consistent with the names that will be used when starting the coupled simulation.
The client code actively requests information from the server code.
The server code works passively, providing information to the client code, and will never send information that has not been requested.
The master performs the coupling setup (e.g., reads all MFX commands, collects the interface meshes from the slave code, does the mapping) and sends instructions (time and stagger loop controls) to the slave executable. In MFX, the ANSYS code is always the master. During the simulation process, the master will act as both a client and a server.
The slave code receives the coupling control information from the master code and sends the interface meshes to master. It receives instructions (time and stagger loop controls) during simulation. In MFX, the CFX code is always the slave. During the simulation process, the slave will act as both a client and a server.
Field solvers can be grouped together for simultaneous execution during each stagger iteration. When grouped this way, all field solvers collect their respective loads from the other field solvers, and then all proceed to solve their physics fields simultaneously.
Field solvers that are not grouped together for simultaneous execution are executed sequentially during each stagger iteration. In this case, each field solver collects its respective loads from the other field solvers and proceeds to solve its physics fields.
The following MFX topics are available: