Naming: log_NNN.csv (sequential numbering). When a VN-300 EFIS provides a UTC timestamp, the file is renamed to YYYY-MM-DD_NNN.csv at close so the date travels with the file. Dynon, Garmin, and no-EFIS logs keep log_NNN.csv.
Size: A 1-hour flight produces approximately 50–100 MB of data
Each log_NNN.csv is written alongside a log_NNN.meta plain-text sidecar. The firmware refreshes the sidecar every 30 seconds while the log is open and rewrites it once at close, so a flight that ends with a power yank still leaves a usable sidecar (worst case: the last 30 s of metadata is missing). The first 30 seconds of any flight are an exception — a power yank in that window leaves no sidecar at all, and the /logs page renders em-dashes for that flight rather than a misleading zero-valued line. One key=value per line:
time_of_day_start is captured from any EFIS that publishes a clock (Dynon SkyView, VN-300, Garmin G3X, MGL). utc_start is VN-300-only. The /logs page reads the sidecar to populate the start-time, duration, max IAS, and max pressure altitude columns. The max_alt_ft value comes from the Palt column — every altitude OnSpeed records is pressure altitude (ISA 1013.25 hPa reference); there is no Kollsman/QNH correction.
For VectorNav VN-300, the columns use vn prefix instead (e.g., vnPitch, vnRoll, vnGnssLat, etc.) — see CSV Log Columns Reference for the complete list.
Appended at the very end of every row, after CoeffP. Older firmware
(format version 1) omits these columns entirely.
Column
Units
Description
flapsRawADC
counts
Raw flap-lever pot ADC reading. Replay tools interpolate the L/Dmax pip across detent transitions using this value and the configured <FLAPPOTPOSITIONS> boundaries.