Repository navigation
Events
Purpose: Present a chronological timeline of supported recorded events inside every detected flight window in one ArduPlane DataFlash BIN.
- One ArduPlane DataFlash
.binor.BINlog. - At least one detected flight window for a flight timeline.
- Supported
MSG,MODEorLANDrecords if you expect timeline entries. - The APT desktop GUI. See the README installation instructions if needed.
- Click Choose BIN… beside Source BIN:.
- Select the aircraft BIN.
- Open Events from Overview or select the Events tab.
- Click Analyse.
- Review each detected flight timeline in the report panel.
- Click Docs for the in-app description and glossary.
The GUI processes every detected flight in order. The terminal workflow instead lets you select one flight when a BIN contains several.
Each flight remains a separate section. Its header shows:
- Flight number.
- Source-log filename.
- Detected flight-window start and end times.
- Number of supported events retained in that window.
Times are log-relative values derived from DataFlash TimeUS, not local clock times.
The current timeline merges three sources:
- MSG — firmware text recorded in the DataFlash log.
- MODE — each logged flight-mode record, displayed with its known mode name.
-
LAND_STAGE — changes in the landing-controller stage, including retained flare-height (
fh) and slope diagnostic values.
LAND telemetry is continuous, so APT emits an event only when the stage changes. It does not repeat every unchanged sample.
Events from the three sources are merged and sorted chronologically. When records share a timestamp, the extractor preserves a deterministic retained order. This makes the timeline useful for examining the sequence around mode changes, firmware messages and landing-stage transitions.
The single flight timeline merges firmware messages, mode records and changed landing stages by log-relative time while preserving each event's source detail.
- No flights found means the selected BIN contained no detected flight windows.
-
No events found means that flight window contained no supported
MSG,MODEor changedLANDstage records.
Neither message proves that nothing happened onboard. Logging configuration, message availability and the current extractor's supported sources determine what appears.
Events is a focused recorded-event timeline, not a reconstruction of every vehicle state or physical event. It currently does not include every DataFlash message type, unchanged controller samples or inferred unlogged events.
A firmware message or mode record reports logged state. It does not necessarily prove the aircraft's physical response. Missing events remain absent rather than being inferred.
- Back to the Wiki Home
- TAKEOFF — review owned TAKEOFF execution and performance evidence.
- Landing — review measurements around landing attempts.
- AUTOTUNE — review authoritative tuning-session evidence.
- APT project README
- Events in-app Help source
- Events glossary
Getting started
Battery & packs
Flight analysis
Radio & diagnostics
Reference
