Static-fire acquisition and analysis

Live test data in. A report you can inspect out.

Redline reads rocket motor test data from an ESP32 or CSV, shows channels live, records checklist and alarm events, and calculates the burn afterward. Before reporting a motor class, it checks whether the data can support the result.

Open Redline Download offline HTML

Imported static-fire recordNeeds review

Total impulse31.5 kN·s

Burn time6.8 s

EvidenceReview

01 / Workflow

One place for test day and the analysis after it.

Acquire

Use Web Serial, the built-in simulated stand, or an existing CSV.

Monitor

Watch thrust, pressure, and temperature against limits you set.

Validate

Review timing, baseline, clipping, truncation, sign, and sample gaps.

Report

Export burn time, impulse, peak thrust, motor class, checks, and source details.

02 / Data checks

The number only matters if the file survives review.

Baseline and drift

Looks for nonzero load before ignition and a zero that moves across the record.

Timing and gaps

Checks monotonic time and large jumps in sample spacing.

Clipping and truncation

Flags flat sensor rails and files that end while thrust is still high.

Units and source

Records the selected force unit and a hash of the imported file.

03 / The bug

A vertical test stand exposed the wrong assumption.

A University of Maryland team shared a past static-fire CSV for testing. The first result was too high even though the parser and numerical integration were working.

The load cell was also carrying the motor's weight. That weight changed as propellant burned, so subtracting one constant was not enough. The project now treats baseline choice as part of the evidence behind the result rather than an invisible preprocessing step.