Fan Boundary Condition in ANSYS Fluent: Ceiling Fan CFD
Fan Boundary Condition in ANSYS Fluent: Ceiling Fan CFD
Model a ceiling fan in a room without meshing a single blade — using Fluent's fan boundary condition and its pressure-jump model. Full workflow from geometry to airflow results.
How do you simulate a ceiling fan pushing air around a room in CFD — without the nightmare of meshing and rotating the blades? The answer is one of Fluent's most useful and underrated tools: the fan boundary condition. It replaces the whole fan with a thin surface that simply adds a pressure rise to the flow, capturing the fan's effect at a tiny fraction of the cost. This tutorial walks through a complete ceiling fan simulation in ANSYS Fluent — geometry, named selections, mesh, adding the fan boundary condition, and reading the airflow — with screenshots from the full video.
What This Tutorial Covers
What Is the Fan Boundary Condition?
The fan boundary condition is a "lumped" model: instead of the real, rotating fan, you place an infinitely thin surface where the fan sits and tell Fluent to treat it as a fan. Across that surface, Fluent applies a pressure jump that drives the flow — exactly the net effect a real fan has on the air. No blades, no rotation, no expensive moving mesh.
The Pressure-Jump Model
The heart of the fan BC is the pressure jump (Δp) — the static-pressure rise the fan adds:
You can enter it two ways:
- Constant Δp — simplest; a fixed pressure rise.
- Polynomial Δp(v) — more realistic; the fan's performance curve (pressure vs flow velocity), so the fan responds to the flow like a real one.
This is the single most important input of the fan model: it sets how hard the fan pushes, and therefore the velocities you get in the room.
Step 1: Build the Room Geometry
1Sketch and extrude the room + fan disk
In ANSYS DesignModeler, sketch the room floor plan (here ~15 ft × 12 ft) and extrude it into a 3D room. Then sketch a thin circular surface on the ceiling to represent the fan disk — this is the surface that will become the fan boundary condition.
Step 2: Create Named Selections
2Name every important face
Before meshing, create named selections so Fluent recognises each boundary by name. In this ceiling-fan room model the named selections are: fan (the ceiling disk), fresh_air_in, air_out, ac_in and ac_out (the air-conditioner openings).
Step 3: Mesh the Room
3Generate and check the mesh
Mesh the room volume with a patch-conforming tetrahedral method, refining near the fan and the openings. Always check mesh quality before exporting to Fluent — a good mesh is the foundation of a stable solution. Confirm resolution independence with a grid-independence test.
Step 4: Set Up the Solver in Fluent
4Solver, turbulence & time
In Fluent, choose a pressure-based solver, turn on the energy equation if you're modelling AC temperatures, and select a turbulence model (here realizable k-ε with standard wall functions). Pick steady for the average field or transient for the time history. Set inlet turbulence with the turbulence intensity & length scale calculator.
Step 5: Add the Fan Boundary Condition
This is the key step. In the Boundary Conditions panel you'll see all your named zones — ac_in, ac_out, air_out, fan, fresh_air_in, etc.
5Set the fan zone type to "fan" and enter the pressure jump
Select the fan zone and change its Type to fan. Fluent now treats that thin surface as a fan. Click Edit and enter the pressure jump — a constant value, or a polynomial function of velocity for the fan's performance curve. That's the whole fan boundary condition.
fan (fan, id=3) in the Fluent tree.
Step 6: Set the Other Boundaries
Assign realistic conditions to the room's openings:
| Named selection | Typical Fluent type |
|---|---|
fan | fan (pressure jump) |
ac_in / fresh_air_in | velocity-inlet |
ac_out / air_out | pressure-outlet |
| walls | wall (no-slip) |
Match these to the real ventilation of the room. The inlet velocities can be sized from an HVAC CFM calculation.
Step 7: Initialise & Run
6Initialise, iterate, watch residuals
Initialise the solution, set the iterations (steady) or time steps (transient), and run. Monitor the residuals — continuity, velocities, energy, epsilon — until they fall and level off, and watch a physical quantity (like average room velocity) settle. Judge convergence by residuals, not a fixed count.
Step 8: Read the Airflow Results
7Velocity contours & the fan jet
In the results (Fluent or CFD-Post), plot velocity contours and vectors on planes through the room. You'll see the downward air jet the fan creates and how it circulates around the space — the whole point of the simulation. Here the fan produces velocities up to ~3.5 m/s directly below it.
Common Mistakes
- Meshing the real blades. Unnecessary for room airflow — the fan BC is the efficient, correct choice.
- Wrong pressure-jump sign/value. Too small and the fan does nothing; check the direction of the jump matches the intended flow.
- Fan surface not thin/interior. The fan must be a thin internal face, not a solid or an external wall.
- Skipping named selections. With many openings, unnamed faces make Fluent setup confusing and error-prone.
- Poor mesh near the fan. Refine around the fan and openings, and check y+ for the wall treatment.
- Judging convergence by iteration count. Watch residuals and a physical monitor instead.
Frequently Asked Questions
What is the fan boundary condition in ANSYS Fluent?
A lumped model that represents a fan as an infinitely thin surface adding a pressure rise (pressure jump) to the flow through it — no blades or rotation needed.
What is the pressure jump in the fan model?
The static-pressure rise the fan adds. Enter it as a constant, or as a polynomial function of velocity (the fan's performance curve). It's the key input of the fan BC.
When should I use a fan BC instead of a moving mesh?
When you care about the fan's effect on the surrounding flow (room ventilation, cooling) rather than blade-level detail. Moving/sliding mesh is only for resolving the rotating blades.
Why use named selections before meshing?
They label the fan, inlets and outlets so Fluent recognises each boundary by name — keeping a multi-opening setup organised and error-free.
Can I simulate a ceiling fan without modelling the blades?
Yes — that's exactly what the fan BC is for. A thin disk with a pressure jump captures the downward jet and room circulation cheaply.
Should the ceiling fan simulation be steady or transient?
Steady is faster and gives the average field (often enough for comfort); transient captures the time history at higher cost. Start steady, go transient if needed.
Conclusion
The fan boundary condition is the smart way to put a fan in a CFD model: a thin surface, a pressure jump, and Fluent does the rest — no blades, no moving mesh. In this ceiling-fan room simulation you built the geometry, named the faces, meshed, set the fan zone to fan with a pressure jump, ran the solver, and visualised the downward airflow jet. It's the standard, efficient approach for HVAC, ventilation and cooling studies — and now you can apply it to any fan-driven flow.
For more ANSYS Fluent, CFD and simulation tutorials plus free engineering calculators, explore Free CFD Tutorial. If this tutorial helped you, please share it and subscribe to the CFD Expert channel for the full video. our partner comapny work in cfd simualtions and data analytics









Excellent explanation of fan boundary conditions and their application in CFD. This approach makes fan-driven airflow simulations much more efficient without the complexity of modeling rotating blades.
ReplyDeleteAt HyperCurve, we use advanced CFD simulations to help optimize HVAC, ventilation, thermal comfort, and airflow performance for real-world engineering projects.
Learn more: https://hypercurve.in/