STAR-CCM+ / ROTATING MACHINERY

STAR-CCM+ MRF vs Sliding Mesh: Which Rotating-Flow Approach Should You Use?

Rotating reference frames and sliding meshes answer different questions. The right choice depends on whether the relative rotor-stator interaction is part of the physics you need to resolve.

ENGINEERING PRINCIPLE

Use a rotating-frame approach when a steady approximation of rotation is sufficient. Use sliding mesh when relative motion, blade passing, wake interaction or time-resolved loads are part of the engineering question.

01

What a rotating reference frame gives you

A rotating-frame formulation represents rotation through the governing equations while the mesh remains stationary relative to its region. This is efficient for many steady operating-point calculations and is often a strong first model for fans, pumps and turbomachinery.

02

What sliding mesh adds

Sliding mesh physically changes the relative angular position of connected mesh regions over time. That allows transient rotor-stator interaction, blade passing, wake transport and periodic load fluctuations to be resolved, at the cost of transient time marching and interface-resolution requirements.

03

Choose from the required output

If the goal is mean pressure rise, torque or efficiency at a steady operating point, begin with the less expensive steady rotating-frame model when its assumptions are defensible. If phase-dependent pressure, acoustic forcing, cyclic loads or transient interaction matters, use sliding mesh.

04

Match angular and temporal resolution

A sliding-mesh result is only as good as its timestep and interface resolution. Select timestep from rotational speed and desired angular advance, then verify timestep sensitivity. Keep compatible mesh resolution across the moving interface and monitor conservation.

05

Use the two models as a hierarchy

A practical workflow is to converge a steady rotating-frame case first, use it for initialization and screening, then promote selected operating points to sliding mesh. Differences between the mean sliding-mesh result and the steady model quantify the importance of rotor-stator interaction.

Run the engineering check

Use the linked Abecator calculator or workflow to turn the setup decision into a quantitative check.

Open Rotating Machinery Calculator →
Independence notice:

STAR-CCM+ is a Siemens product name. Abecator is independent and this article is original engineering guidance; it does not reproduce Siemens documentation or third-party tutorial text.

AUTHORITY

MRF vs sliding mesh: resolve the blade-passing time scale when unsteadiness matters

This section turns the workflow into a quantitative engineering check and an original visual model that can be reused during setup review.

region Aregion Binterface transfer / conservation
MRF is a steady rotating-frame approximation; sliding mesh is justified when time-resolved interaction changes the decision.
ENGINEERING RELATION

f_BPF = N_b · RPM / 60

  • f_BPF = blade-passing frequency
  • N_b = blade count
  • RPM = rotational speed
Worked example:

A 12-blade rotor at 6000 rpm has f_BPF = 1200 Hz. If a transient model needs 30 samples per blade-passing period, Δt ≈ 1/(1200×30) = 27.8 μs. This is the scale MRF deliberately averages away.

Decision table

Mean performance is the objective

MRF can be an efficient baseline.

Compare mean pressure/torque/flow.
Rotor-stator interaction matters

Use sliding mesh/transient treatment.

Resolve blade-passing content and phase statistics.
Unsure whether unsteadiness matters

Run MRF first, then a targeted transient comparison.

Judge by the engineering output, not visual animation alone.

Primary / official references

Exact model names and menu locations can change by STAR-CCM+ release; use the official documentation for the installed version when reproducing software steps.

AI Assistance
Contact
TGTelegram