Bracken Systems

Application

Postflight

Beta

Log analysis for modeling improvement and tuning. Postflight reads the binary log after the sortie, in the browser, and turns it into the corrections that go back into the aircraft and into the next plan: what the control loops actually did, where the model and the airframe disagreed, and where the links really held.

Access is by arrangement. Signing in asks for your email and sends a one-time code; if no code arrives within a minute, you are not on the list yet. Email info@brackensystems.com and say what you fly.

The whole loop in a minute

Plan the sortie in Preflight, fly it, and feed the flight back through here, which calibrates the aircraft the next plan is made with.

Silent, captioned. A made-up mission over the Boulder foothills and a simulated flight, so nothing in it is a client's data or a real operation.

Planned against actual

The flight is tied to the Preflight run that planned it, so the plan and the log sit on one map and one table.

Satellite map with the planned route in blue and the flown track in red, the radio failsafe RTL marked, and the point where video was lost.
The planned route and the flown track, the point where the radio failsafe fired, and where video was lost, marked with one tap on the track.
Table of planned against actual: maximum range, flight time, when the RTL triggered and why, and the control link quality at the video-loss point.
Range, time, the RTL and its reason, and the control link's quality at the moment video was lost, planned beside actual.

What the log says

Read and analyzed in the browser tab. The log itself is never uploaded; only the numbers are, and only when you choose to submit them.

Result tiles: firmware version, flight modes with their durations, measured hover current with a button to push it into the saved aircraft, cruise speed with a speed trace, rate tracking and vibration.
Hover current and cruise speed measured from the flight, with a button that pushes each straight into the saved aircraft in Preflight; rate tracking and vibration against ArduPilot's own guidance.
Control link quality over the flight as a trace, beside the receiver's own radio status records.
Control link quality over the flight, and the receiver's own radio status records with the raw bytes kept beside the decode.

Back into the plan

One button fits the aircraft's video and control field loss from its own flights, and Preflight plans with those figures from then on.

The Recalibrate button for a saved aircraft and the result: the control field loss fitted from one radio failsafe, with the point where packet loss starts.
The fit names its method: from a radio failsafe that actually fired, or extrapolated from link quality against the model's margin when none did.