Repository navigation
Home
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.
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 Analysis — Inspect consumption, voltage sag, load events and configured voltage margins in a BIN log.
- Battery Pack Management — Assign physical batteries to logs and record supported history.
- Pack Performance — Compare saved observations across sessions.
- 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 Link — RC failsafe and response evidence, with optional EdgeTX CSV.
- Range-Walk Comparison — Landmark-aligned RF comparisons of saved walks.
- Field Test Procedures — Safety-focused navigation for the established Radio Link, Range-Walk and Stall procedures.
- Terminology and Evidence — Common evidence language and distinctions used across APT reports.
- Data Storage and Backups — Persistent battery and Range-Walk data, source-file retention and backup guidance.
- Project README — Installation, launching APT, basic operation and current support scope.
- Report an issue — Report problems or documentation corrections.
- 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.
Getting started
Battery & packs
Flight analysis
Radio & diagnostics
Reference