Expand description
Rocketronics’ AltiMAX altimeters: a flight as the AltiMAX PC software exports it to Excel, a
bare .xls worksheet (xls) whose sheet reads as this table.
The maker’s manuals say only that a flight “can be exported to Excel as altitude values” (AltiMAX G4 Manual, Rocketronics, 2021, p. 52); none describes the columns. One header row names them, and the one export among the sample logs has these eleven:
TIME,PRESS FILTER [hpa],HEIGHT FILTER [m],PRESS RAW [hpa],HEIGHT RAW [m],ACCEL [m/s2],
SPEED [m/s],EVENT,EVENT,VOLT. CHANNEL,VOLTAGE [V]Channels. Each column is read into the record’s SI unit (Quantity::unit) on the
TIME clock:
| Column | Quantity | Read as |
|---|---|---|
TIME | the clock | seconds, though it names no unit: held below |
PRESS FILTER [hpa], PRESS RAW [hpa] | pressure | the unit its values show, held below |
HEIGHT FILTER [m], HEIGHT RAW [m] | altitude above the pad | m: the altimeter sets its sensors “to “0”“ when armed (AltiMAX G3 User Manual, p. 10) |
ACCEL [m/s2] | acceleration | m/s², as written: below |
SPEED [m/s] | speed | m/s, as written: below |
EVENT, numbers | a number, as written | 0 on a row with no event |
EVENT, text | the flight’s events | below |
VOLT. CHANNEL | a number, as written | which voltage the row’s VOLTAGE [V] is |
VOLTAGE [V] | one voltage channel for each VOLT. CHANNEL number, on its own rows | V |
A column the reader doesn’t know is kept as written, as Quantity::Unrecognized, with a
note. A header of more than MAX_COLUMNS names is refused.
The primary track is HEIGHT RAW [m], the height from the barometer’s own reading; the
filtered height is a channel, as an Eggtimer’s filtered altitude is.
The accelerometer’s columns, as the sample shows them. No manual describes them. ACCEL
is measured along an axis pointing down the rocket: in the sample it reads −0.94 g before
liftoff, where an axis pointing up would read +1 g at rest. SPEED is ACCEL summed over the
clock, gravity left in: over the sample’s boost, the median of its change against ACCEL’s is
1 to within 0.2 %. So SPEED isn’t the rocket’s speed, and the record’s vertical speed is
left empty; both columns are kept, signs and all, as channels.
Units the file doesn’t state, or states wrongly, held to physics. TIME names no unit. The
altimeter stores 200 samples a second until apogee and fewer after it (AltiMAX G4 Manual,
p. 8 and p. 10), so the clock is read in seconds when its shortest step is 5 ms, within
10 %; otherwise the file is refused. The pressure columns say [hpa], but the sample’s hold
pascals: six-digit values whose heights follow them in pascals, not in hectopascals. Each
pressure column is read in the unit that puts its first value, on the pad, between 500 and
1,100 hPa: hPa as stated, or Pa, with a note. The two ranges don’t overlap, so only one can;
a value in neither is refused.
Events. The two EVENT columns are a code and its name. A row whose code isn’t 0 is an
event, named as the text column writes it, such as BARO-LIFTOFF or APOGEE PRESSURE. The
names follow the manual’s list of events
(AltiMAX G3 User Manual, p. 15), in the software’s own spelling; the codes aren’t documented,
so they are kept as written.
Voltages. VOLT. CHANNEL is a channel number, one a row, and VOLTAGE [V] is that
channel’s voltage: the reader gives each number its own voltage channel, VOLTAGE [V] (channel 1) and so on, five in the sample. The software lists five voltages, the battery’s, the igniter’s and three pyro
channels’ (AltiMAX G4 Manual, p. 42), but not which number is which, so none is named.
Cells. A row holds as many cells as the header; an empty value is a gap, NaN, counted in
a note. The clock must increase from row to row, and a row without a time is refused.
use hpr_flightdata::altimax;
// An invented export: three rows, the second an event.
let text = "TIME,PRESS FILTER [hpa],HEIGHT FILTER [m],PRESS RAW [hpa],HEIGHT RAW [m],\
ACCEL [m/s2],SPEED [m/s],EVENT,EVENT,VOLT. CHANNEL,VOLTAGE [V]\n\
0.005,98000,0,98000,0,-9.8,0,0,PAD,1,7.4\n\
0.01,97990,0.8,97989,0.9,40,1,3,BARO-LIFTOFF,2,7.3\n\
0.015,97975,2.1,97974,2.2,60,2,0,PAD,3,0.1\n";
let log = altimax::read(text)?;
assert_eq!(log.altitude_m, [0.0, 0.9, 2.2]);
assert_eq!(log.events[0].name, "BARO-LIFTOFF");
assert_eq!(log.events[0].time_s, 0.01);Constants§
- MAX_
COLUMNS - The most columns a header may name: the export the reader was built on names eleven. A header of more names is refused before they are compared, as the AltOS telemetry CSV, Fluctus and AeroSpaceNU readers refuse one past their own limits, so that a hostile header can’t cost time growing as the square of its width (#1250).
Functions§
- read
- Reads an AltiMAX export’s table.
- recognizes
- Whether
textis an AltiMAX export: its first line that isn’t blank opens with the five columnsTIME,PRESS FILTER [hpa],HEIGHT FILTER [m],PRESS RAW [hpa],HEIGHT RAW [m], in any case.