Skip to content

Data Storage and Backups

nflyernz edited this page Oct 19, 2026 · 1 revision

Data Storage and Backups

Most APT analyses read the selected source file and display a report without saving analytical data. Battery Pack and Range-Walk workflows are the exceptions described here.

← Wiki Home

Where APT stores persistent data

APT stores its current persistent records in the Data directory inside the ArduPlaneTools application folder:

Path Contents
Data/battery_packs.json Physical Pack IDs and BIN-content-fingerprint associations, including explicit Not tracked decisions.
Data/battery_pack_history.json Versioned supported AUTO-takeoff battery observations recorded on request.
Data/range_walk_history.json Saved Walk 1 baselines, associated later walks, landmark mappings, radio-configuration metadata, RF settings, source identity and checksums.
Data/range_walk_csv/ Checksum-named managed copies of the EdgeTX CSV evidence owned by saved Range-Walk records.

These paths are relative to the APT source/application directory, not a system-wide preferences folder. They are created when the corresponding workflow first writes data. APT does not currently provide automatic cloud storage, migration or backup.

Battery Pack IDs and log associations

Battery Pack Management assigns a user-created Pack ID to the SHA-256 content fingerprint of an entire BIN. The association does not modify the BIN and is not tied only to its filename. Identical copies of the same BIN resolve to the same saved decision.

Renaming a Pack ID updates the saved associations that use it. Marking a BIN Not tracked records that decision without assigning a physical pack.

battery_packs.json does not contain the original BIN. If the BIN is deleted, the Pack ID and fingerprint decision may remain, but APT cannot reopen or reanalyse the missing log.

Battery history

Record AUTO takeoff history explicitly extracts supported battery and AUTO-takeoff observations from the selected, assigned BIN and stores them in battery_pack_history.json. Repeating the operation does not duplicate an observation already recorded for the same event and supported analysis semantics.

The history retains source identity and filename, firmware and time provenance where available, event bounds, battery instance, supported electrical values and configuration warnings. Pack Performance presents observations according to the BIN's current Pack ID association, so reassigning or renaming a pack changes which report owns existing history without rewriting the source BIN.

The history file is evidence extracted from a BIN; it is not a copy of that BIN. Keep the original flight logs separately.

Range-Walk history and CSV evidence

When a baseline or additional walk is saved, APT records its metadata in range_walk_history.json and preserves a checksum-named copy of the source EdgeTX CSV under Data/range_walk_csv/.

The metadata includes stable record IDs, parent-baseline association, labels, original CSV filename, SHA-256 identity, five candidate/landmark mappings, radio-configuration descriptions and optional RF settings. The managed CSV is required to reconstruct section statistics and plots in History & Comparison.

APT validates the managed filename, path and checksum before using saved evidence. A missing, modified or inconsistent managed CSV makes that saved comparison unavailable rather than causing APT to invent results.

The original CSV should still be retained with field notes. The managed copy protects the evidence used by APT, but it is not a substitute for preserving the complete test record outside the application folder.

What to back up

Close APT before copying its data, then back up the complete Data directory. Keeping the directory together preserves the relationship among JSON metadata and managed Range-Walk CSV files.

Also back up separately:

  • Original ArduPlane BIN files.
  • Original EdgeTX CSV recordings and associated field notes.
  • Any reports, plots or screenshots you need to retain.

Store backups on a different disk or a trusted backup service. Flight logs and saved records can contain filenames, dates, aircraft details and GPS-derived information; protect backup access appropriately.

Replacing or reinstalling APT

Before replacing the application folder or extracting a new source archive:

  1. Close APT.
  2. Copy the entire existing Data directory to a safe backup location.
  3. Install or extract the replacement copy of APT.
  4. Before recording new data, restore the backed-up Data directory to the root of that replacement application folder.
  5. Start APT and verify Pack IDs, Pack Performance history and Range-Walk history.

Do not assume that deleting or replacing the application folder preserves Data. APT does not currently merge independent stores or automatically migrate data between installations. Keep an untouched backup until the restored records have been checked.

If application versions use incompatible saved-data schemas, APT reports the unsupported data rather than silently converting it. Seek project guidance before editing JSON files manually.

What APT does not preserve

  • Battery persistence does not copy original BIN files.
  • Running ordinary Battery, TAKEOFF, Landing, AUTOTUNE, Stall, Events or Radio Link analysis does not create a durable copy of the selected BIN.
  • Optional Radio Link EdgeTX evidence is not added to Range-Walk storage merely by selecting it.
  • APT does not automatically back up, synchronize or migrate the Data directory.

Related information

Clone this wiki locally