Expand description
Silicdyne’s Fluctus flight computer’s logs, as its Fluctus Control Center (FCC) exports a
flight: a sep=; line, then a semicolon-separated table with each column’s unit in its name.
The Fluctus records its black box at each tick of its flight software, 50 times a second, from
a second before the launch it detects (Fluctus – Full Documentation, v1.7b, Silicdyne, 2025,
https://silicdyne.net/resources/docs/fluctus_fulldoc_v1_7b_EN.pdf, read 2026-10-13, p26); the
FCC’s BlackBox Viewer exports it to a .csv file “which can be opened in any spreadsheet
program, such as Excel” (p58). The first line is sep=;, the hint that tells a spreadsheet the
separator; the next names the columns, a unit in brackets after most; each row below is one
tick:
sep=;
time (ms);deltaTime (ms);status;baro-altitude (m);dedrck-v-speed (m/s);angle (deg);…;gpsSats
61500;20;3;0;0;3,5;0;0,0;9,8;0;0,0;21;8400;1;1;0;0;0;0;12,345678;-23,456789;150;1;8Recognition. Within the file’s first 16 lines, the first that isn’t blank is either sep=
and one separator character (;, ,, a tab or |), followed by the header on the next line
that isn’t blank, or the header itself, then separated by semicolons. The header’s first name
is time, and it names deltaTime and baro-altitude too: those are the Fluctus’s own names
(manual p27), and no other layout among the project’s sample logs has them. Names are compared
with their bracketed unit taken off and without regard to case. An Eggtimer’s or an RRC3’s
semicolon-separated file has neither name.
Numbers. The FCC’s export has a Decimal point delimiter setting, as spreadsheets in
different regions read a .csv file differently (p58): the sample logs write 12,5 for 12.5. When the separator isn’t a comma, a comma in a cell is read as the decimal mark, and a
point as well; a cell with both, or with two commas, isn’t a number (table::number). The
files bear this out: their latitudes are written 12,345678, six digits after the comma,
which as a thousands separator would put the logger millions of degrees from the equator, and
their clock, past 1,000 ms on every row, is written with no thousands separator, so 1,234 is
1.234, never 1,234. When sep=, names the comma, numbers take a point only.
Columns. A name is split into the name and the unit in the brackets at its end, as
baro-altitude (m). The name says what the column holds and the unit how to read it; the
units are those of the header, read without regard to case or spaces:
| Column | Read as | From |
|---|---|---|
time | the clock, the logger’s own: its zero isn’t stated, and the rows start about a second before the launch | the header (ms); manual p27 (“Frame time”) |
deltaTime | not a channel: checked against the clock’s step, and a note counts the rows where it differs | the header (ms); manual p27 (“Time since last tick”) |
status | Quantity::Number, and an event at each change, named as the manual names the code (below) | manual p23 |
baro-altitude | Quantity::AltitudeAboveGround: the primary track | the header (m); manual p27 (“Baro altitude from origin”) |
dedrck-v-speed | Quantity::Speed, up positive: the vertical speed by dead reckoning, the accelerometers’ and gyroscope’s integral | the header (m/s); manual p23, p27 |
angle | Quantity::Angle: the tilt from vertical on the rail and in the descent, from the launch axis in the climb | the header (deg); manual p24 |
roll-rate | Quantity::AngularRate | the header (deg/s); manual p27 |
vert-accel | Quantity::Acceleration, vertical | the header (m/s2); manual p27 |
accel | Quantity::Acceleration: the magnitude of the acceleration the accelerometers feel, 1 g at rest | the header (m/s2); manual p24 |
dedrck-alti | Quantity::InertialAltitude | the header (m); manual p27 |
baro-speed | Quantity::Speed, up positive: the primary track’s vertical speed | the header (m/s); manual p23 (“barometric altitude derivative”) |
amb-temp | Quantity::Temperature: the board’s sensor, which reads the bay | the header (deg c); manual p27 |
batt-voltage | Quantity::Voltage: the battery’s | the header (mV); manual p27 |
P1-state, P2-state, P3-state | Quantity::Number, and an event when an output fires (below) | manual p23 |
analog1, analog2 | Quantity::Voltage | the header (mV); manual p27 |
inFreefall | Quantity::Number, 1 or 0 | manual p27 (“Rocket in free fall (bool)”) |
gpsLat, gpsLng | Quantity::Latitude, Quantity::Longitude, when the values bear out degrees (below) | manual p38; a note |
gpsAltMSL | Quantity::GnssAltitude in meters, when the barometric altitude bears it out (below); otherwise kept as written | manual p27 (“GPS altitude (MSL)”); a note |
gpsState | Quantity::Number as written: the manual gives no codes; Silicdyne’s changelog says that from firmware 2.2 it holds the satellite count, the fix status before it moved elsewhere (https://silicdyne.net/changelog-fluctus/, update 2.2, read 2026-10-13) | |
gpsSats | Quantity::Number: the satellites the GPS uses | manual p27 |
The units the header may state: ms, s and us for a time; m and ft; m/s, ft/s
and km/h; m/s2 (or m/s², m/s^2) and ft/s2; deg (or °) and rad; deg/s and
rad/s; deg c and deg f (or °c, °f) and k; mV and V; Pa, hPa, mbar and
kPa. A column the reader knows whose unit is another, or is of the wrong kind, such as an
angle in m/s, is kept as written, Quantity::Unrecognized, with a note; so is one the
manual gives a unit and the header writes none for. A column the reader doesn’t know is read
by its unit where the unit can mean one quantity only, a speed, an acceleration, an angle, a
rate of turn, a temperature, a voltage or a pressure; a length, a time, no unit or one the
reader doesn’t know keeps it as written, with a note. The clock must be in a unit of time and
the barometric altitude in one of length: a file without either is refused.
The altitude’s zero. The manual gives baro-altitude “from origin” (p27) and doesn’t say
where that is; as of 2026-10-13, in all 6 Fluctus files among the project’s sample logs, it
reads 0 on the first rows, on the pad before launch, so the logger zeroes it on the pad. It is
written in whole meters there, though the manual gives the barometer a resolution of 0.1 m
(p18), so the format’s resolution is 1 m
(LogFormat::altitude_resolution_m).
The position in degrees. No unit is in the header for gpsLat and gpsLng; the manual’s
picture of the FCC’s Locate tab shows the position in decimal degrees to six places (p38), as
the file writes it. Each is read in degrees if it holds at least one reading and every reading
lies within ±90° for the latitude or ±180° for the longitude; otherwise it is kept as written,
with a note.
The GPS altitude in meters. No unit is in the header for gpsAltMSL, nor in the manual (p27),
and Silicdyne’s changelog says only that the firmware logs it from update 1.6. It is read in
meters only if the barometric altitude bears it out, at the GPS’s fresh fixes: the rows where
the GPS altitude differs from its last reading before, the first included. A reading that
repeats the last, as the receiver holds its last fix while it has none, and a gap are left out.
Through those fixes a straight line is drawn by least squares, the GPS altitude against the
barometric; in meters it rises 1 for each meter, in feet 3.28. The GPS altitude is read in
meters where all four hold:
- there are at least 10 fresh fixes, more than the two that fix a line exactly, so that the scatter about it is measured too;
- they span at least 120 m of the barometric altitude. The manual’s ±3 m for the GPS (p18) is its horizontal position; a GPS receiver’s vertical error is larger, the U.S. government’s standard for GPS giving 13 m against 8 m horizontal, 95% of the time, 1.6 times (GPS Standard Positioning Service Performance Standard, 5th ed., 2020, Table 3.8-3, p58). Allowing twice the horizontal, 6 m, two readings that far off in opposite directions at the span’s ends tilt the slope by 12 m over the span: over 120 m, the 10% margin below;
- they scatter about the line, RMS, by at most 10% of that span. A receiver that lags far behind the flight traces a loop rather than a line, and the slope of a loop doesn’t tell the unit: a feet GPS lagging by a 10 s filter can come out near 1 (a test pins one at 3 times the allowed scatter);
- the slope lies within 10% of 1, far from the 3.28 of feet.
Otherwise it is kept as written, Quantity::Unrecognized, with a note saying which failed.
A GPS that loses its fix in the climb and regains it low in the descent, the fixes spanning
little of the flight, is kept: its highest reading’s rise above the pad can match the apogee in
feet by chance, but the span or the slope gives it away. As of 2026-10-13, none of the 6 sample
files passes: in each, the GPS altitude lags the barometric one by hundreds of meters in the
descent, and every slope is below 0.75.
Events. Each change of status is an event named as the manual names the code it changes
to (p23): 0 IDLE, 1 ARMED, 2 COUNTDOWN ENGAGED, 3 WAITING FOR LAUNCH, 4 ASCENT (the
launch detected), 5 DESCENT (the apogee detected), 6 TOUCHDOWN; another code is named
status and its number. A pyro output’s state is 0 for no continuity, 1 for continuity and 10
for fired (p23): each change to 10 is an event, the column’s name and ENABLED, as P1-state ENABLED. A row whose cell is a gap changes nothing.
Placeholders. A cell of 2,147,483,647, the largest signed 32-bit number, or of −2,147,483,648, the smallest, isn’t a reading: as of 2026-10-13, in one of the 6 sample files, both of the dead-reckoning columns hold 2,147,483,647 from a few rows after the launch to the end, where their readings would run to many kilometers a second. Each such cell is a gap, counted in a note.
Rows. Every row must have as many cells as the header has names; a row of another width, a
clock cell that isn’t a number, or a time that doesn’t come after the row above’s is refused,
naming its line. Any other cell that is empty or isn’t a number, such as nan, is a gap,
counted per column in a note. A reading its unit’s conversion carries past the largest number
an f64 holds, as 1e308 in deg f or 1.7e308 in g, is refused, naming its line
(ADR-258 §3). Blank lines are skipped; lines may end in CR, LF or both, and a
byte-order mark is dropped. A note counts the steps of the clock longer than its commonest. A
header of more than MAX_COLUMNS names, or naming a column twice, is refused.
Constants§
- MAX_
COLUMNS - The most names a header may have: the Fluctus writes 24 (manual p27).
Functions§
- read
- Reads a log in this layout.
- recognizes
- Whether the text is in this reader’s layout, judged from its first lines, never the file’s name.