Coupling 1D and 3D CFD: Myth or Reality: (Fluids & Co, Canada)
Coupling 1D and 3D CFD: Myth or Reality: (Fluids & Co, Canada)
Vincent A. Soumoy
(Fluids & Co, Canada);
Abstract
For years Computational Fluid Dynamics (CFD) has been widely used across
many branches of engineering including the Aerospace, Automotive, Biomedical
Chemical, Marine, Oil, Gas, Petrochemical and Power Generation industries.
One dimensional (1D) CFD allows engineers to understand how flow rates and
pressures may change within a network flow system of interconnected
components. In contrast, three dimensional (3D) CFD allows design engineer to
understand how detailed flows interact with all manner of complex geometry. Of
course, 1D calculations are much faster, only a few minutes, when 3D CFD may
take hours or days.
We are now nearly 10 years later, tools and editors have changed, or merged.
The CFD Working Group (namely David Kelsall and the author) were involved in
the 2010 seminar. All the speakers have been contacted and agree to show that 1D-
3D is now a reality.
We had to consider two kinds of industrial need: the 1D user who is looking for a
local detail or the 3D user who would like the more real as possible boundary
conditions.
3D analysis is being used where the nature of the flow and the understanding
required makes 3D analysis the appropriate tool; 1D simulation is applied to
examine the fluid flow conditions of the remaining system, which can be captured
by a 1D calculation with in-built sub-models for specific components as required.
Boundary conditions and results are then passed around the complete system,
allowing for a more complete and faster analysis. A link is in charge to handle
communication of variables (and results) between the models. Most of the
software vendors have to enable users to bi-directionally link their 3D CFD
models (often via a simple to use and intuitive user interface) to a 1D fluid flow
system network. This 1D network then analyses for pressures, flows and
temperatures across the whole system, reporting boundary conditions (Steady Sate
or Transient) directly back into the CFD model.
The 1D system can also allow thermal interactions or mechanical positions from
other systems and incorporate those effects when determining the component CFD
boundary conditions.
To ensure proper functioning of the coupling, the interface must not be located in a
region in which flow separation or recirculation is expected and must be a planar
face orthogonal to the expected main flow direction.
This process will also allow you to investigate the influence of a complex three-
dimensional component on 1D fluid flow and system performance, to provide
detailed information about 3D flow fields in the domain of interest; considering
the influence of all relevant sub-systems modelled one-dimensionally and to obtain
an immediate response of the sub-systems on design changes.
We will review the first attempts of the 1D & 3D software vendors to reach these
capabilities, the situation about 10 years ago, at the initial NAFEMS seminar on
this subject, and the actual offers. We will also mention some external ways used
for the same target.
In 2001, Flowmaster (the most common 1D fluid code at this time) and STAR-CD
(from CD-adapco) distributed a direct link (called STARLink) initially for the
German automotive industry. It was followed by a FluentLink for Fluent (from
ANSYS).
AVL developed their own interface between the 3D code FIRE and the 1D codes
BOOST (from AVL), GT Power and WAVE. In the automotive engines
application, the use of coupled 1D/3D simulation was highly motivated by the
investigation of the impact of design modifications on the engine performances,
namely for the EGR (Valve used to control pollutants in exhaust systems) supply
location or the lambda probe positioning.
He reminded us that the Fluentlink was developed between Flowmaster and Fluent
for vehicle thermal management and started the series. He mentioned that Fluent
was linked with GT Power, Wave and Flowmaster. CFX is linked with GT Power
and Amesim. In some cases, the link required custom code.
As a second step, the link between Fluent and GT Power or Wave was described.
CFD components were defined in the 1D code and boundary macros were
automatically created to hook to the CFD boundaries and to exchange variables
like mass flow rate, pressure, temperature, and species mass fractions.
The next part of the presentation concerned co-simulation between CFX and
Amesim. Examples with ball valve, cryogenic pipe and tracer transport with 3D
effects in TT junction were described.
To finish an intake manifold (EGR) was described between CFX and GT Power.
Using the best of both worlds was the main idea of this model. The system model
is fast to set up and very quick to analyse. Moreover, the 1D air distribution
system modelling will allow analysing large aircraft air distribution, to evaluate
duct re-routing scenarios, to study the mixing of fresh and re-circulated air and to
conduct “what-if” scenarios on duct sizing.
The results obtained were challenging and stimulating and showed that changes in
1D model would directly affect 3D model.
This first approach on industrial case presumed that realistic simulations were
possible and gave scope for further development and optimization, but David
Kelsall remembered that validation is important.
Sreenadh Jonnavithula from CD-adapco was presenting the new link between
STAR-CCM+ and Olga, GT-Power and Wave.
The way CD-adapco has developed those new links corresponded to the ideal
solution for users. They did not need intermediate tools between 1D and 3D codes
and did not have to worry about the coupling itself.
The goal was to provide a consistent interface for coupling multiple 1D codes,
assuming that 1D problem is set up by an expert user of 1D code.
Examples shown coupling STAR-CCM+ with Olga, GT-Power and wave suggest
a lot of new application in future for example with lagrangian particle tracking.
Around 2010, MpCCI (Mesh-based parallel Code Coupling Interface) has been
developed and distributed by Fraunhofer-Institute for Algorithms and Scientific
Computing (Fraunhofer SCAI) to support Abaqus, ANSYS, Fine/HEXA,
Fine/TURBO, Flowmaster, Fluent, Flux, ICEPAK, MSC.Marc, Permas, STAR-
CD and RadTherm amongst others.
This new interface could facilitate interactions between different software tools as
it remains partially vendor independent but was probably less convenient than the
former direct links. Indeed, the initial links here were created for specific 1D and
3D codes, so they are fully dedicated. The graphical user interface was user-
friendly and often directly included in the 1D user interface. The only problem was
that each 1D or 3D software was live; the version was regularly changing, and the
link was generally dependent on both 1D and 3D code version.
Using MpCCI avoided the main part of this dependence but as it was a general
tool, the user interface was less easy to use than the direct ones.
Pascal Bayrasy showed at Gaydon how realistic simulations be. He first presented
the various advantage of this vendor independent tool, allowing multi-software
and multi-systems models. Some typical examples for fluid structure interaction
on a turbo charger fan, for radiation coupling with RadTherm and for full vehicle
thermal management were presented.
Today, with the same kind of method that the one used by MpCCI, some tools
allow to manage all the logical steps of your engineering process with a single
automated workflow.
Complex engineering problems often include the use of a myriad of in-house and
third-party CAD, CAE and general use software, including 1D and 3D CFD,
resulting in a disconnected, difficult to manage process.
Integration and process automation tools, like modeFrontier, for example, will
streamline and automate the engineering process within an integrated workflow of
various software to increase the overall efficiency, save time and reduce
operational costs.
Complex engineering problems include the necessity to take into account multiple
disciplines, consider high number of interrelated variables, and run multiple third-
party simulation software.
The technology offers a variety of direct integration nodes to couple with the most
popular engineering solvers.
Direct nodes seamlessly connect with the simulation models, extract relevant
parameters and allow the selection of the process input and output in few clicks,
through a simple guided process. Constraints and objectives just have to be added
to run the process and exploit the benefits of process automation.
Mainly most of the 1D and 3D CFD software vendors are involved ANSYS
(Fluent, CFX), AVL(Ast), GAMMA (GT-Suite), SIEMENS (STAR-CCM+,
FloEFD, FloMaster, Amesim), EXA (Powerflow)…
Today, two 1D leaders are offering 1D-3D co-simulation: FloMaster (the former
Flowmaster) and Flownex.
For the first time in the industry, Mentor Graphics was providing a tightly coupled
general-purpose 1D-3D CFD simulation software combination. With this
combination, engineers can characterize the more complex elements of the system
with full 3D and easily insert those models into the 1D system level model for
simulation.
And because FloMaster offers a fast and reliable solution to 1D flow problems,
designers can expect unrivalled savings in both time and process compression.
This 1D-3D combination provides the best of both worlds, thus reducing time to
get essential component information to system engineers and improving system-
level accuracy with highly complex geometries, thus reducing the design cycle
time.
To combine the best of both worlds, Mentor offers three new capabilities that will
be presented in a dedicated paper (Croegaert and al).
And last tool, OneSim is a tightly coupled co-simulation workflow that enables a
3D FloEFD model to be considered as part of a FloMaster system simulation. First,
one or more FloEFD boundary conditions are linked to nodes within a FloMaster
network. Then a simulation instigated from within FloMaster will solve both the
FloEFD model and the FloMaster network concurrently, until steady state or
transient convergence is achieved. Flow rates, pressures and fluid temperatures will
be communicated through the linked boundary conditions nodes throughout the
solution process. An implicit coupling technology is used to enable solutions to be
achieved more readily compared to more classic co-simulation approaches that can
be prone to instabilities, often requiring middleware to govern the solver
communication and can be notoriously tricky to set-up.
On the other side, Flownex made the choice to collaborate with ANSYS and
decided to integrate their 1D system tool to the workbench environment.
Flownex is linked to both ANSYS CFD and FEA codes for more localized results
where required.
Flownex can also be coupled with the FEA code ANSYS Mechanical: thermal and
pressure stress analyses can be performed starting from the temperature and
pressure calculated by Flownex. Co-simulations between 1D network and FEA 3D
code can be used to model conjugate heat transfer with 3D geometries: this
approach keep the accuracy of temperature distribution in the solid domain and
reduce the computational effort on the fluid side.
Figure 8: 1D and 3D flows are solved together, and information is exchanged at the
boundaries. The entire simulation is controlled by Flownex interface
One application of the coupling with ANSYS Fluent can be illustrated in the
simulation of the HVAC system in a server room. In this case Flownex is used to
simulate the fan, heat exchanger and ducting to the server room while ANSYS
Fluent is used to simulate the heating of the air by the electronics and the air flow
in the room.
The interface points are chosen at the vents that supply air to the room, where the
temperature and flow results from Flownex are transferred to Fluent and the
backpressure results from ANSYS Fluent are returned back to Flownex. In this
simulation, control elements are added to automatically adjust the fan speed and
the vent openings in order to study the transient scenario of the system.
Figure 9: Flownex and ANSYS Fluent link: HVAC system in a server room
Flownex SE also adds value to structural simulations and can be used to transfer
1D flow results to a FEA simulation package such as ANSYS Mechanical.
It shows a model of a boiler where the flows are calculated using Flownex and the
thermal stresses are calculated using ANSYS Mechanical. Using this analysis
technique, start-up conditions can be simulated in a transient environment and
boiler design can be modified to ensure the stresses are all within allowable limits
before construction begins.
Figure 11: Zoom view of some of the custom compound components illustrating the network
that was modelled in Flownex
Flownex can also calculate pressure forces on elbows and pipes: these can be used
as an input to mechanical design for the calculation of pressure stress analyses and
frequency analyses based on pressure signal (using Fast Fourier Transform).
Figure 12: Flownex and ANSYS Mechanical link: Thermal stresses of a boiler.
7. Conclusion
Coupling 3D and 1D codes, the overall computational effort is reduced while the
3D fundamental modelling aspects are maintained at the same time.
Following this approach, several 1D tools are now linked with 3D tools in a
unique simulation environment.
Now the coupling is completely automatic and be can used for sensitivity analyses
to improve the system design.
Simulations can be optimised for both accuracy and minimization of run time,
providing engineers with a robust set of simulation tools that meet industrial
demands.
8. References
Bayrasy, Pascal (2010). Generic Coupling of 1D System Codes with 3D CFD tools
by MpCCI: NAFEMS Seminar “Coupling 1D and 3D CFD: The Challenges and
Rewards of Co-Simulation” Gaydon (UK).