This tool needs a larger screen (tablet, laptop or desktop). Phones are not supported.
SBG Log Analyser
No log loaded
Hover, focus or tap a field to see what it is.
Open a session folder (or drop one here)
sbgECom chunks session.000, .001… plus optional session_XXXX.json. Decoded locally; nothing is uploaded.
click a field → left axis · right-click → right axis · ? guide
Settings
Mapsatellite tiles
No valid GNSS/INS positions in this log
needs a GPS1_POS computed fix or EKF_NAV in nav-position mode
FFT
Events
t = —
SBG Log Analyser guide
No section of the guide matches this search.
Cheat-sheet
Click a field
plot it as a trace on the left Y axis (click again to remove)
Right-click a field
plot it on the right Y axis (or move it there)
Enter / Shift+Enter on a field
the same from the keyboard (left / right axis)
Drag on the plot
zoom to that box
Scroll wheel
zoom in/out
Double-click the plot
reset the zoom to the full recording
Hover the plot
values of every trace in the chips, time in the strip under the plot; map and FFT follow
ƒ next to the filter
new expression (e.g. AIR_DATA.altitude - GPS1_POS.altitude_msl)
F2 / Delete on an expression
edit / delete it
L / R in a chip
move that trace to the other axis
✕ in a chip
remove that trace
Drag a divider
resize the message list or a panel (double-click or Home: reset)
[ or the rail
collapse / expand the message list
Click an events row
zoom to ±10 s around it
CSV · shift-click · ▾
export the visible window (long · wide · choose)
Esc / ✕ / click outside
close this guide
Loading data
Open folder (header or the empty page), or drag a folder onto the page. Input is folder-only; a session folder (e.g. …/sbg/000067270_session_0014) loads at once.
Picking a bigger folder is safe: the page first looks only at file names and sizes, at most 8 folders deep, 20,000 files and folders or 3 s, skipping hidden and system folders (node_modules, Library, *.app …). Folders named sbg, …session…, by date (2026-08-03) or logs are looked at first. A status pill shows the count and has Cancel. A file whose name is not clearly an SBG chunk is checked by reading only its first 64 KB, and only when no session.NNN chunk was found.
When the scan stops on its budget, the page says so and never calls the folder "not an SBG log folder": Keep scanning continues where it stopped (in the message, or in the session list). A folder scanned to the end without SBG chunk files stops with a message before any log is read.
Several sessions open a list to choose from: sorted by date, hour and folder name (a session without an hour sorts by folder name within its day), grouped by day (a tick selects a whole day), with a filter box when the list is long. Each row shows the session folder, then what is left of its path (dimmed), the chunks and the size; a running total is checked against the 700 MB per-session and 1.2 GB per-load limits. When everything would not fit nothing is ticked, and a line says why. With logs loaded already, choose Replace (default) or Add to them (the loaded sessions are read again with the new ones; a session loaded already is not doubled).
Chrome and Edge open folders with the File System Access API, so the page reads entries one by one. Chrome then asks "Let site view files?": allow it (read only; the page cannot change anything). If you close the picker or decline, a short note says no folder was opened. If the browser refuses the picker (embedded frame, policy, the click is too old), a message offers the classic chooser. Other browsers use the classic folder upload: they may ask "Upload N files to this site?" first. That wording is misleading: nothing leaves your computer, the files are only read by this page.
sbgECom chunks name.000, name.001, … with the same folder and stem form one session, joined in numeric order.
Rollover chunks, duplicates and sidecarsQUANTA rollover chunks with a date prefix (session.000, 20260803_07h_session.001, …) normally join their session.NNN siblings. If that would create duplicate chunk numbers, or the folder holds several session_XXXX.json, chunks are chained instead: a chunk continues the chain that ends with the previous number at the same or the previous date-hour, only when that match is one-to-one; anything ambiguous becomes its own session, and a load note lists the files of every session and what was kept apart. A repeated chunk number keeps the first file by name (noted). Any other binary is its own session. session_XXXX.json supplies device and settings only for a recording without embedded SESSION_INFO, and only when it can be paired unambiguously (by session name, or as the single remaining sidecar for the single session that needs one); otherwise none is applied (noted).
Files without a valid sbgECom frame in their first 64 KB (PDFs, videos, scripts…) are skipped. A session above 700 MB, or a load above 1.2 GB in total, is refused with a message naming the folder.
While loading, a status pill in the header shows the step and a thin bar under the header shows the progress (only sbgECom sessions are counted). Problems open a message box; "nothing loaded" keeps the previous logs on screen and says so.
A new load replaces the previous logs (unless you chose Add to them); plotted traces stay where the new logs have the same field or expression, the others are dropped (a note gives the count). After a load, the settings panel shows the session summary and warnings; the events panel lists them under "Load notes", together with the full settings differences between sessions.
Message list
One group per message under its sbgECom name (EKF_NAV, AIR_DATA, GPS1_HDT) with its median rate; hover the header for a plain-English description and the sample count. Click or press Enter to expand. The button next to the filter collapses all groups.
Each field row: the decoder's field name (vel_n, true_airspeed, yaw_deg) and a unit badge (m/s², °C, µs, %…); hover, focus or tap it and the line at the bottom of the list shows MESSAGE.field [unit]: description (also read by screen readers). Outlined badges are types: flag = 0/1, enum = coded state, bitmask = packed flags (see Flags). Chips, axis titles, CSV, expressions and presets use the same MESSAGE.field names.
The filter matches names and descriptions (e.g. airspeed finds true_airspeed, pressure altitude finds AIR_DATA.altitude), including the flags inside bitmask nodes, and highlights matching names; a row found through its description shows that text, dimmed, under the name.
Expressions (top group, or the ƒ button next to the filter) holds your own plottable formulas (see Expressions). Raw / untimed lists messages that cannot be plotted, with counts.
All angles and rates are shown in degrees (…_deg, …_dps in deg/s, converted in this page); the radian originals are hidden behind Show raw radian fields at the bottom of the list. Chips, axes and CSV columns carry the unit.
Plotted fields get an L/R badge in the trace colour.
The list collapses to a rail with a chevron at its top (or [); the choice is remembered. On a narrow window it collapses automatically: a dot on the chevron and a note in the strip under the plot say so.
Plotting
Left-click = left axis, right-click = right axis, the same click again removes the trace. Colours are assigned automatically (a darker palette in the light theme); the axis titles list the traces and units.
Chips (above the plot), one per trace: colour, name, axis (L/R, click to swap), value under the cursor (enums add their label), min, max, mean of the visible window (full resolution) and unit. Numbers use the same decimals within a trace, chosen from its visible range; hover one for full precision. Enums, flags and bitmasks have no mean; bitmasks show hex. When the mouse leaves the plot the last values stay, dimmed. The button in the chip header hides min/max/mean.
Time strip under the plot: cursor time with its zone, the device sensor time and, with several sessions, the session (with its line style); ≈ marks extrapolated UTC.
Zoom with drag or the wheel; the toolbar at the top right of the plot has zoom in/out, box zoom, pan, autoscale (reset) and save as PNG. Zoomed in, the y axes follow the visible data. Flag and enum axes use whole-number ticks.
More than 6000 visible points are drawn with min/max decimation (extremes kept). Chips, map and CSV always use full-resolution data. Lines break between sessions/segments, where the clock goes backwards, at missing values and where a heading/yaw wraps at ±180°. Flags and enums are drawn as steps.
With several sessions, each session gets its own line style (solid, dashed, dotted…) and a grey dotted line marks each session start, even with annotations off.
Drag the dividers to resize the message list and the panels (double-click: reset); widths are remembered. The plot keeps at least 480 px: panels at their default width give way first (down to 240 px), then the list collapses automatically, then panels you sized shrink to 240 px, and finally all panels down to 180 px. Opening a panel that would still leave the plot under 480 px closes the oldest other open panel (a notice names it).
Clear plot removes all traces. The page starts in the dark theme; the moon/sun button switches it (remembered).
Time axis
UTC, IST (+05:30), Local time (browser zone, DST per sample; the axis title shows the data's offset): ticks show the time of day, the axis title the ISO date.
GPS week: GPS time of week (s); week and leap seconds are in the axis title (leap seconds from UTC_TIME, else 18 s assumed).
From boot: device seconds since power-up; sessions from different boots can overlap and are told apart by line style.
Elapsed: sessions and clock segments end to end with 5 s gaps.
UTC, IST, Local time and GPS week need a valid UTC anchor in every session and segment; otherwise they are greyed out, the axis uses elapsed and the time strip says why.
Samples more than 2 s outside the valid UTC anchors of their segment get extrapolated UTC: ≈ in the time strip, utc_extrapolated = 1 in CSV. Time never comes from file names or the host clock; a backwards boot-counter jump over 1 s starts a new segment.
Changing the basis keeps the zoom window when its edges fall inside recorded data.
Presets
Pick from Presets…. Fields missing from the loaded logs are skipped; if none exist you get a message.
Attitude
EKF roll/pitch (L), yaw (R)
Heading sources
EKF yaw vs dual-antenna GNSS heading, with their 1σ
Velocity NED
EKF vs GNSS N/E/D velocity
Altitude
EKF, GNSS and air-data altitude (L), EKF vertical velocity (R)
GNSS quality
satellites used and fix type (L), GNSS position 1σ (R)
Solution status
EKF solution mode, validity flags, GNSS1 position/velocity used
Position 1σ
EKF vs GNSS position uncertainty
IMU accel / IMU gyro
IMU_SHORT acceleration (IMU_DATA fallback) / angular rate in deg/s
Vibration
vibration-monitor RMS per axis, Z band-1 peak frequency
Interference
GNSS interference/spoofing/OSNMA status, mean SNR
Clock
UTC clock state and status, CPU usage
Aiding received vs used
GNSS1 position/velocity received (STATUS) vs fused (EKF)
Expression presets (ƒ, second group of the menu) add the expressions they need under From presets in the Expressions group and plot them. If one of their names is already used by a different expression (yours, or a preset expression you edited), you choose: keep both (the preset's copy gets _preset, and so does every preset expression that uses it, so the preset never mixes in your definition), keep yours, or replace yours. Applying the preset again reuses those copies without asking. Remove unused in From presets deletes copies that are no longer plotted. A trace that cannot be computed is named in the status line.
Baro vs GNSS altitude
baro altitude minus its median offset to GNSS, GNSS altitude (L), baro − GNSS while GNSS has a computed fix (R)
Horizontal speed
INS and GNSS horizontal speed
Magnetic heading
tilt-compensated magnetic and true heading, EKF yaw (L), validity and |m| (R)
Dual-antenna heading
HDT heading minus the installation offset, EKF yaw (L), HDT − yaw, HDT − magnetic (R)
Drift (position aiding off)
rebased drift N/E/D/horizontal (L), pos_aiding_off and ref_ok (R)
INS vs GNSS error (raw)
INS − GNSS position error (L), GNSS1 pos/vel and Velocity 1 used bits (R)
Save preset stores the plotted traces under a name in this browser (it asks before replacing a name). Saved presets appear under "Saved"; Manage saved presets… at the end of the list deletes them.
Annotations
Off by default to keep plots uncluttered; tick Annotations in the header (remembered). Until you have used it once, the time strip reminds you after your first plot.
Solution-mode bands (background; the longest visible bands are labelled first): 0 UNINITIALIZED, 1 VERTICAL_GYRO, 2 AHRS, 3 NAV_VELOCITY, 4 NAV_POSITION. From EKF_NAV, or EKF_EULER as fallback.
Red / amber dotted lines: DIAG errors / warnings, grouped within 1 s; hover a label for the full text.
Purple dotted lines: aiding-policy DIAG lines, e.g. rejection mode: GNSS1 position-velocity: never (a commanded denial, not RF jamming); …: auto allows them again. Filter initialisation and motion profile lines are marked too.
Red strips at the top and bottom (with a faint tint between): intervals with no position aiding fused (EKF_NAV.pos_aiding_off = 1) after the segment's first fused position, lasting ≥ 2 s; ≥ 5 s are labelled with their duration.
Session starts are labelled with the session name and "settings changed (N)" when the settings differ from the previous session; hover the label for the changes (all of them are in the events panel). Amber dashed line: new clock segment (reset candidate).
Labels that would overlap are hidden; zoom in to see more. Lines and bands always stay.
Panels
Toggle them with the buttons at the top right; each has a ✕ to close it.
Settings: device and settings source in the header, a session summary (sessions, frames, segments, UTC, start) and a Warnings list, then the latest session's settings by section. The filter searches keys and values; long values are shortened (hover for the full value).
Map (satellite tiles): GNSS fix (GPS1_POS, computed) and INS (EKF_NAV in nav-position mode). These two map colours are fixed and independent of the trace colours. The part inside the plot's time window is bright, the rest dim, with green/red dots at the window start/end.
Cursor, fitting and empty logsHovering the plot puts a marker on the GNSS fix and on the INS position nearest the cursor time (each within ±0.5 s), joined by a thin grey line; the INS marker's tooltip gives that INS−GNSS distance. The map refits to the visible part on every zoom until you pan or zoom it yourself; auto-fit resumes when the window moves by more than 10 %, or with the button. A log without positions shows "No valid GNSS/INS positions in this log" instead of a map.
FFT: the vibration-monitor spectrum nearest the cursor (else the latest) for axis X/Y/Z, in m/s² against Hz, with the peak marked. ACF multiplies by the amplitude correction factor; Log switches the magnitude axis.
Events: DIAG messages with time, level and code (click a row to zoom ±10 s). The level chips in the header filter them (INFO starts hidden above 200 messages). Then flag changes, clock reset candidates, decode errors and load notes.
Flags and bitmasks
Status words pack many on/off flags (and a few coded states) into one number. Under each such field the message list shows a node, e.g. status · 12 flags · 1 enum; expand it to plot each flag as its own 0/1 field and each coded state with its labels. Each flag shows its sbgECom bit name (e.g. airspeed_used); hover it for the description. Coded states that already have their own row in the message (e.g. solution_mode) are not repeated in the node.
Covered (sbgECom 5.8 headers): device status (health, ports, Ethernet, aiding received), IMU and magnetometer self-tests, UTC clock, GNSS position/velocity/heading status, GNSS interference/spoofing/OSNMA, INS solution status, air data, event inputs, vibration monitor, aiding echoes, odometer, DVL and ship motion.
Flags the decoder already provides (e.g. gps1_pos_used) are reused; others are computed when first plotted (raw name status:…).
A bitmask chip shows the value in hex. Hover it (or tap it) for every flag at the cursor time by bit name (● set, ○ clear), coded states with labels, and set bits without a definition; hover a flag for its description. Esc closes the list.
The events panel lists flag changes of the device health, aiding-received and communication bitmasks and of GNSS interference/spoofing/OSNMA (MESSAGE.field: +bit_name set, −bit_name cleared; hover a row for the descriptions; first 500).
Expressions
New expression: the ƒ button next to the filter, ƒ+ in the Expressions header, or New expression… (works before a log is loaded too). Give a name (letters, digits and _, starting with a letter; checked while you type, with a cleaned-up suggestion), the expression, a unit, the axis and, if needed, the message to evaluate on.
While you type: suggestions for fields (degree fields first; radian fields only with Show raw radian fields), $expressions and functions (with their signature); words also match descriptions (satellites, baro, north), after the name matches, and each suggestion shows a short description. ↑/↓ choose, Tab or Enter insert, Esc closes the list. The line under the box shows a syntax error with a caret (grey while you are still typing), a $reference cycle, a note when units are mixed (e.g. [deg] - [rad]), or for each log how many samples and finite values the draft gives, evaluated with your draft in place of the saved version. The unit is filled in when the fields agree; it is only a label, nothing is converted.
Saving: Add and plot plots a new expression when it has values; one that evaluates in no log needs Save without plotting, and one without finite values (e.g. x / 0) is saved but not plotted. Save on an edit never changes what is plotted. The row is scrolled into view and highlighted. Esc keeps your unsent draft: it comes back the next time you open the dialog (Discard the restored draft resets it). Cancel abandons it.
Syntax: fields MSG.field (any field of the list, e.g. AIR_DATA.altitude, EKF_EULER.yaw_deg, flags such as STATUS.aiding_status:gps1_pos_recv; names are matched without case), other expressions $name, numbers, + - * / ^ (typographic − × ÷ are accepted too), == != < <= > >= (1/0), && || !, c ? a : b (after a flag field name write A.b ? x : y with spaces), constants pi and nan.
Recipes: offset AIR_DATA.altitude - GPS1_POS.altitude_msl; offset removed with a median (computed per log) AIR_DATA.altitude - median(AIR_DATA.altitude - GPS1_POS.altitude_msl); km/h hypot(GPS1_VEL.vel_n, GPS1_VEL.vel_e) * 3.6; heading difference wrap180(GPS1_HDT.heading - EKF_EULER.yaw_deg); gate on a GNSS fix where(GPS1_POS.solution_type >= 2, AIR_DATA.altitude - GPS1_POS.altitude_msl) (GNSS fields before the first fix hold placeholder values).
Functions: abs sqrt exp log log10 floor ceil round pow min max hypot; sin cos tan asin acos atan atan2 (radians), sind cosd atan2d deg rad wrap180 wrap360; statistics over each log median mean first; along the series diff, deriv (per second), where(cond, x) (NaN when cond is false), rebase(x, cond[, maxlag]) (x minus its value at the start of each cond interval, the first finite sample within maxlag s, default 1 s), since(cond); geodesy dnorth(latA, latB), deast(lonA, lonB, latRef) in metres; tilt_heading(mx, my, mz, ax, ay, az); settings("aiding.gnss1.leverArmPrimary.0") (the log's latest settings value); hdt_offset(); ifmissing(MSG.field, value) for a field some logs do not have.
Time alignment: an expression is evaluated on the timestamps of its first referenced message (or the one chosen under Evaluate on). Other messages are interpolated linearly inside the same clock segment (wrap-aware for angles), take the nearest sample for flag/enum/bitmask/count fields, and are NaN where their samples are more than 2× their median period apart, so a dropout is never bridged. Nor is a status change: where the two samples around a timestamp differ in their own message's status, solution_status or solution_type (a fix gained or lost, a mode change), the nearest sample is taken instead of interpolating, so where(GPS1_POS.solution_type >= 2, GPS1_POS.altitude_msl) never mixes a no-fix and a fix value.
In the list: your expressions sorted by name, then the ones added by presets under From presets (Remove unused deletes those not plotted and not used by another expression). Click = left axis, right-click or Shift+Enter = right axis, pencil or F2 = edit, bin or Delete = delete. A row that does not evaluate shows the reason under it; clicking it (or Enter) opens the editor.
Expressions behave like fields: chips, L/R, decimals, annotations, CSV (message EXPR, field = name; the header lists the formula, every $expression it uses and the values settings() / hdt_offset() resolved to). Saved presets store expressions by name.
Sharing: Export expressions writes all or a selection to a JSON file ({"format": "sbg-analyser-expressions", "version": 1, "expressions": [{name, expr, unit, axis, evalOn}]}); expressions used through $name are ticked automatically. Import expressions reads such a file: format and version, at most 1 MB and 500 expressions, valid names (with the rule quoted when one is not) and every expression must parse; it is only parsed, never run, until you plot it; invalid entries are listed and left out. Identical entries are skipped without asking. For a different expression with an existing name you choose (collision 1 of N): keep both (the default; the import gets the _2/_3 suffix shown, and $references in the same file follow it), overwrite or skip, optionally for all. The summary says when imported expressions use fields that are not in the loaded logs.
Drift and heading presets
The former derived fields are expression presets, so every step is visible and editable. ref_ok: the GNSS1 fix qualifies as reference (computed, type 2–10, valid lat/lon, receiver integrity not ERROR/CRITICAL, spoofing not confirmed, OSNMA not spoofed). ins_north/east/down_err = INS minus GNSS (down: + = INS below), INS interpolated to the fix time, only in EKF mode 3/4. pos_aiding_off = gps1/gps2/pos1 position-used bits all clear (they persist ≈3 s, so the edge lags the real last fusion). drift_* = rebase(err, $pos_aiding_off): the error vector at the first qualified fix within 1 s of the off edge is subtracted; drift_horizontal is its norm. vel_err_* = EKF minus GPS1_VEL velocity.
Checked against the former built-in derivation on four sessions (drift identical to 1e-7 m) and against sbgtool.py aiding: ≤ 0.13 m on three GNSS-denial trials. A display aid, not a certified drift verdict; normal aided flights can show short aiding-off intervals that are not a denial.
Max drift is not the drift at restore. The chip's max is the largest drift anywhere in the window. When GNSS stays rejected after the restore command (the EKF keeps refusing the fixes), drift keeps growing past the restore, so the max can be far larger than the drift at the last qualified fix before the restore (session 0061: max 649.8 m, 164.9 m at restore). Read the restore value with the cursor at that fix.
mag_heading = tilt_heading(MAG…): tilt-compensated magnetic heading (level/quasi-static assumption; mounting and iron effects not removed); mag_true_heading adds the EKF_EULER declination; mag_heading_valid: |m| within ±15 % of the session median, tilt < 60°, |a| within ±30 % of g. hdt_vehicle_heading = HDT heading − hdt_offset() (lever-arm baseline angle, else the median of heading − EKF yaw; shown in the settings summary).
CSV export
Exports every trace (both axes) inside the visible time window from full-resolution data; no interpolation or resampling.
Long (the CSV button): one row per source sample, ordered by time, with session, segment, sensor_s, elapsed_s, utc_iso, utc_extrapolated, x_display, message, field, value, label, unit, axis.
Wide (shift-click, or ▾ → Wide CSV): one column per trace (plus .label for enums); rows are the union of exact sample times, blank where a trace has no sample.
The file starts with # lines: tool URL, sessions and firmware, time basis, window, format, rows and traces. Numbers are full precision; units stay the raw ASCII names (m/s2, degC) for tools.
Filename: <sessions>_<basis>_<start>_<end>_<long|wide>.csv. Above 2,000,000 samples you are asked to confirm.
Keyboard and accessibility
Tab reaches every control. In the message list, ↑/↓ move between rows, → / ← expand / collapse a group, Enter plots a field on the left axis, Shift+Enter on the right.
Dividers: Tab to one, then ← / → resize by 16 px, Home resets.
Dialogs and this guide keep the focus inside until closed (Esc). The page honours the system "reduce motion" setting.
Privacy and offline use
Files are decoded in this browser and never uploaded. Remembered only in this browser (localStorage): time basis, theme, saved presets, panel and list widths, list collapsed, show raw radian fields, expressions, annotations on/off (and whether they were ever ticked), chip compact mode. The phone-notice dismissal is kept for the tab (sessionStorage).
Plotly, Leaflet and the satellite tiles load from the internet; decoding itself needs no network.
Troubleshooting
Date options greyed out: at least one session or segment has no accurate UTC_TIME (e.g. no GNSS time yet). The axis uses elapsed seconds; use From boot or Elapsed.
Where are the warnings? In the settings panel summary and under "Load notes" in the events panel.
"missing chunk .00N": a numbered chunk is absent from the folder; copy the full session folder.
"Phones are not supported": shown below 600 px in either direction, or on a touch screen under 900 px in both. Continue anyway dismisses it for this tab.
Page looks outdated after an update: hard-reload (Cmd+Shift+R on macOS, Ctrl+Shift+R elsewhere).
Empty map: no GPS1_POS computed fix and no EKF_NAV in nav-position mode, or no internet for Leaflet/tiles.
Nothing plotted after a preset: none of its fields exist in these logs (the drift presets need EKF_NAV and GPS1_POS); the message lists why.
An expression row shows a warning: a referenced field or expression is missing in a loaded log, or the syntax changed; hover the row, or click it to edit.
Flat or empty drift curves: drift_* only exists inside no-position-aiding intervals with a qualified fix in EKF mode 3/4; check ref_ok and the red strips.