ArduPlaneTools v1.0.0 — Flight Log Analysis GUI Released

I’ve just released the first public version of ArduPlaneTools (APT), an open-source application for analysing ArduPlane DataFlash logs and, where applicable, EdgeTX transmitter telemetry.

APT started as a collection of tools to investigate takeoff and landing behaviour on my Ranger 2000. It’s gradually developed into a standalone application with ten analysis modules and a PySide6 desktop GUI.

Current analysis modules:

  • Battery Analysis, Battery Pack Management and Pack Performance

  • TAKEOFF execution and performance

  • Landing approaches, preflare, flare and termination

  • AUTOTUNE sessions and gain changes

  • FBWA slow-flight and probable stall/departure events

  • Flight Event Timeline

  • Radio Link and failsafe analysis

  • Range-Walk Comparison, including RF statistics and plots

An important design goal has been to distinguish what is actually recorded in the log from what can reasonably be inferred. Missing or ambiguous evidence is reported rather than filled in with assumptions.

About the reports: They’re still a bit wordy in places, but APT is an engineering tool at heart. For now, I’ve favoured presenting the supporting evidence and qualifications rather than simplifying reports at the expense of useful detail. There’s certainly room to improve the presentation as more people use it.

APT is focused on ArduPlane 4.7.x. It has been developed and extensively tested on macOS, with automated Python tests running on Ubuntu. Windows installation instructions are included, but Windows compatibility hasn’t yet been independently validated.

Release:

Illustrated user guide:

APT is released under the MIT licence. The current release requires Python; standalone macOS and Windows installers are planned.

I’d particularly welcome a few users trying APT with their own flight logs. My development and validation have naturally involved a limited range of aircraft, configurations and flight conditions, so testing against other people’s logs would be valuable.

I’m interested in:

  • Incorrect or questionable analysis results.

  • Different aircraft, firmware and logging configurations.

  • Reports that are unclear or unnecessarily verbose.

  • Windows users willing to try the installation and report whether the GUI and analyses work correctly.

  • General usability feedback and suggestions.

It’s reached the point where feedback from actual users will be more useful than continuing to polish it in isolation.

Thanks to anyone willing to give it a try!

How does it compare to this?

I use UAV Log Viewer a lot, and still do. The challenge I was having was that after three or four plots, things became cluttered. I was constantly switching between saved layouts, adding and removing plots to piece together what was happening.

APT approaches the problem differently. It identifies particular phases and events in the flight, such as takeoff, preflare, flare or a failsafe, and produces a structured report with the relevant measurements and supporting evidence. It saves me having to hunt through multiple plots to establish what happened and when.

It also has some tools for tracking battery pack performance across flights, something I’ve always maintained separately in spreadsheets. I also added in some radio link tests as I was setting up a new plane recently.

So I see the two as complementary. UAV Log Viewer is great for exploring the telemetry visually; APT is more about extracting and interpreting the relevant evidence automatically. I still go back to UAV Log Viewer when I want to investigate something in more detail.

ArduPlaneTools update — desktop builds now available

A quick update for anyone following this thread.

I’ve now released ArduPlaneTools v1.1.0-beta.1, with downloadable desktop applications for:

  • macOS — Apple Silicon (ARM64), supplied as a DMG.

  • Windows — 64-bit, supplied as a portable ZIP.

Hope this makes it easier to use. MacOS has been tested locally on Sequoia, Windows tested synthetically. Any feedback welcomed.

@BOIBoy

Thanks for clarifying.

Makes more sense now.

Have a look through the user guide for some examples of reports from my logs, might make it clearer.

Cheers