Design sequence

Build the motor from chemistry through simulated firing.

3 linked stages

Project Ember / Engineering analysis

Hybrid motor
analysis workspace

Analyse an ABS and nitrous oxide hybrid motor through one traceable workflow: characterise combustion, define the grain, then resolve the complete firing.

3 linked stages ABS solid fuel N2O oxidiser
Record storage 0 run records
Current workspace
Workspace register Session analysis records
0Chemistry runs
0Grain designs
0Burn simulations

Analysis sequence

Build your motor in sequence

Each saved result becomes an input to the next stage automatically.

Design workspace

Procedure notes

Why the stages are separated

Do the slow chemistry once, iterate on geometry, then tune the live burn.

01
Characterise the flame

Equilibrium chemistry

Calculate flame temperature and exhaust composition across mixture ratios and chamber pressures, then save a reusable lookup table.

The chemical search is genuinely slow. Computing it once keeps the thousands of calls inside a burn simulation fast.
02
Shape the fuel

Grain geometry

Model a circular, star, wagon-wheel, or uploaded port and calculate how its flow area, burn surface, and fuel volume evolve.

Port shape controls the thrust profile: a circular bore usually rises through the burn, while a star can produce a flatter response.
03
Simulate the firing

Transient burn

Resolve tank cooling, injector flow, fuel regression, chamber conditions, nozzle flow, thrust, and impulse moment by moment.

The run produces thrust, chamber pressure and temperature histories, total impulse, and downloadable burn data.

How the tools hand over

Each tool records its output in the current workspace. A simulation uses the exact chemistry and geometry records you select; it never silently falls back to the newest.

A combustion table and a saved grain geometry are both required to run a simulation. The grain file supplies its own length, outer diameter, port shape, and quench margin.

Why the work is split into three stages

Chemistry depends only on the propellants, geometry only on the grain, and the transient simulation is the part you re-run while tuning nozzle sizes and operating conditions. Separating those jobs keeps iteration fast and every input traceable.

Current run storage

0 chemistry run(s), 0 grain geometry file(s), and 0 burn simulation(s) are available in the current history.

Session runs

Save this session?

Save 0 runs to your account?