Skip to content
nflyernz edited this page Oct 19, 2026 · 5 revisions

ArduPlaneTools (APT) — User Guide

Welcome to the illustrated user guide for ArduPlaneTools (APT), a Python-based application for examining evidence recorded by ArduPlane flight logs and, in supported workflows, EdgeTX transmitter telemetry.

APT v1.0 focuses on ArduPlane 4.7.x. It reports what the available evidence supports, and explicitly identifies missing or ambiguous data.

New to APT? Start with the main project README for step-by-step download, Python installation and launch instructions for macOS and Windows. Windows operation is not yet validated to the same level as macOS.

Using this guide

Each module chapter will cover its required input, the steps to run it, annotated screenshots, the meaning of the principal report fields, and limitations. The application's Docs button also provides short, built-in help; some modules have a Test Procedure button.

Battery & packs

Flight analysis

  • TAKEOFF — Launch triggers, control stages and performance.
  • Landing — Approach, preflare, flare and landing/rollout evidence.
  • AUTOTUNE — Sessions, axes and saved gain evidence.
  • Stall — FBWA slow-flight and attitude-departure evidence.
  • Events — Chronological flight events.

Radio & diagnostics

Reference

Understanding the results

  • APT reads logs from your computer. BIN logs and reports may contain GPS locations and other sensitive information; review them before sharing.
  • A logged state, command or threshold is not always proof of the aircraft's physical response.
  • Unavailable measurements are not treated as zero or silently inferred.
  • The reports support investigation and tuning decisions; they do not certify airworthiness or replace safe flight-test practices.

Clone this wiki locally