A static-fire trace shows what your test stand measured during the burn. Attach it to the motor to compare it with the simulation, or use the measured curve for flight simulations.
Import a trace#
The import lives in the motor editor's Overview section, under Static Fire. Import Thrust Data accepts RASP files (.eng / .rasp) and raw CSV from a data logger:
- RASP files are read directly — the thrust points, designation, manufacturer and propellant weight all come from the file.
- CSV goes through a short mapping step: pick which columns hold time and thrust and set their units (seconds or milliseconds; newtons, pounds-force or kilograms-force), with the first rows of the file previewed alongside.
The last step shows the derived metrics before anything is saved — peak and average thrust, total impulse, burn time, sample count and impulse class. Confirm, and the trace is attached to the design.
Compare with the simulation#
The measured and simulated thrust curves appear together in the performance panel. The static-fire result also has its own performance card showing the designation, impulse class, peak and average thrust, total impulse and burn time calculated from the measurement.
Use static fire as the source#
The Use Static Fire Result switch — in the Overview section, and offered during import as Use as Motor Performance — decides which curve the motor uses. Switched on, the motor's designation, impulse class, total impulse, peak and average thrust and burn time all come from the measurement, and any rocket flight simulated with this motor burns the measured curve instead of the modeled one. The performance panel marks whichever source is live with an Active badge, and you can switch back to the simulated values at any time.
To start over, the Overview section shows the loaded data with a Clear button — clearing removes the trace and returns the motor to its simulated performance.