Pro · UAV AI In development

AI Log Analyzer

Drop a flight log. Ask it questions. "Why did it crash?" "What was wrong with the tune?" "What should I change before the next flight?"

The idea

Flight logs already contain the answer — attitude, vibration, voltage sag, EKF innovations, mode changes, failsafes — but reading a dataflash log is a skill that takes years, and most crashes get diagnosed by forum thread. The Log Analyzer pairs real log parsing (ArduPilot dataflash and ULog) with AI-assisted diagnosis grounded in the actual telemetry: it cites the log messages and timestamps behind every claim, suggests plausible causes ranked by evidence, and proposes concrete parameter or hardware fixes.

What asking it looks like

Ask it: "Quad dropped out of the sky about 40 seconds in — why?" — and it answers with cited telemetry: VIBE.VibeZ climbing 12 → 58 m/s² with accelerometer clipping from t≈31s, RCOU.C3 pinned at maximum while the other three outputs drop (the classic thrust-loss compensation signature), XKF4.SV velocity variance growing after t≈39s. Diagnosis: physical damage or imbalance on motor 3's propeller — thrust loss, then saturation, then attitude loss. Then the concrete part: inspect prop 3, enable the harmonic notch filter, re-fly, and compare the two logs' VIBE traces with the free Param Diff.

Where it stands, honestly

This is the earlier-stage of the two Pro products: the design exists, the product does not yet. It builds on real prior work — the free ArduPilot Param Diff tool and its full parameter-metadata dataset (~5,700 parameters per vehicle from ArduPilot's official definitions) are the foundation the diagnosis layer stands on. Waitlist feedback directly shapes what gets built first: which vehicles, which failure modes, which log formats.

Join the waitlist

One email when it opens — founding waitlist members get launch pricing and a say in the first supported failure modes.

Flying today? The free ArduPilot Param Diff already catches configuration drift between flights.