Skip to content

Battery Pack Management

nflyernz edited this page Oct 19, 2026 · 3 revisions

Battery Pack Management

Purpose: Give each physical battery a user-chosen Pack ID, associate an entire ArduPlane DataFlash BIN with that pack, and explicitly record supported AUTO-takeoff battery observations for later comparison. APT cannot identify the physical battery from the BIN alone; the operator supplies that identity.

← Wiki Home

What you need

  • A DataFlash .bin or .BIN log from the aircraft.
  • Knowledge of which physical battery was used for the entire BIN recording.
  • A short, unique Pack ID that you will recognize later.
  • The APT desktop GUI running. See the README installation instructions if needed.

A Pack ID applies to the entire BIN, including every detected flight in that recording. It cannot be assigned separately to individual flights.

Open Battery Pack Management

  1. Click Choose BIN… beside Source BIN: at the top of the APT window.
  2. Select the relevant ArduPlane BIN. Its path appears in Source BIN:.
  3. Open Battery Pack Management from Overview or select its tab.
  4. Check the Selected BIN panel. Source: identifies the selected filename and Association: shows whether its content is already tracked by a Pack ID.

Simply selecting a BIN or opening this tab performs a read-only lookup. It does not change an association or record history.

Battery Pack Management showing a selected BIN association and pack controls

The selected BIN panel shows its tracked Pack ID and the available management controls. The local path and filename are redacted for privacy.

Create and assign a Pack ID

Use this when the physical battery has not been registered before.

  1. Under Create and assign Pack ID, enter the new identity in New Pack ID.
  2. Click Create and assign.
  3. Review the Create Battery Pack confirmation. It identifies the source BIN, current association and proposed Pack ID, and states that the entire source BIN will be associated.
  4. Choose Yes only after confirming the physical battery. Choose Cancel to make no change.
  5. Read the operation result in the lower status area and confirm that Association: now shows Tracked — <Pack ID>.

Duplicate or invalid Pack IDs are rejected. Creating the identity and assigning the selected BIN are one confirmed operation.

Assign an existing Pack ID

Use this when the battery already appears in the saved Pack ID list.

  1. Under Assign existing Pack ID, select the physical battery from the list.
  2. Click Assign selected BIN.
  3. Review the Assign Battery Pack confirmation, including the current association and proposed Pack ID.
  4. Choose Yes to apply the association to the entire BIN, or Cancel to leave saved data unchanged.
  5. Check the refreshed Association: value and operation message.

APT identifies a BIN association by its SHA-256 content fingerprint rather than its filename. An identical copy of the same BIN therefore resolves to the same saved association even if the copy has another filename.

Rename a Pack ID

Renaming changes the identity globally; it is not limited to the currently selected BIN.

  1. Under Rename existing Pack ID, choose the current ID in Existing:.
  2. Enter the replacement in Replacement:.
  3. Read the displayed Effect:: every saved BIN association using the old ID will be updated.
  4. Click Rename globally.
  5. Review the Rename Battery Pack confirmation and choose Yes or Cancel.
  6. After success, confirm that the replacement ID is selected and appears in the Pack ID lists.

An empty, duplicate, invalid or unchanged replacement is not applied. Renaming does not open or modify the original BIN files.

Record AUTO takeoff history

Assign the selected BIN to the correct Pack ID before recording history.

  1. Confirm that Association: shows the intended tracked Pack ID.
  2. Under Record AUTO takeoff history, read the Effect: explanation.
  3. Click Record history.
  4. Review the Record Battery History confirmation. It identifies the source BIN and tracked Pack ID and asks whether to record all supported AUTO-takeoff observations from that BIN.
  5. Choose Yes to process the log, or Cancel to perform no write.
  6. Read the completion message. It states how many new observations were recorded.

The operation reads supported TAKEOFF and battery evidence from the whole BIN. Assigning or renaming a Pack ID does not record history automatically.

Recording the same unchanged BIN again is idempotent: APT does not add duplicates for observations it already retained under the same supported analysis semantics. A repeat can therefore report zero new observations.

Recorded observations become available under the currently owning Pack ID in Pack Performance. Use Refresh there after changing identities, associations or history.

Understand saved identity and history

  • A Pack ID is the operator's name for one physical battery.
  • A log fingerprint is the BIN's content identity used for association.
  • An assignment links that fingerprint to a Pack ID.
  • History recording saves supported AUTO-takeoff observations separately from the BIN.
  • Renaming preserves associations under the new Pack ID.
  • Reassigning a BIN changes which current Pack Performance report owns its saved observations.

These records are stored locally in APT's Data directory. Back up that directory if the identities and history matter to you.

Limitations

APT cannot determine which physical battery was installed from flight-log evidence. A wrong operator assignment will place observations in the wrong pack report. Confirm the battery before accepting any change.

Pack IDs apply to whole BIN sessions, so this workflow is not suitable when different physical batteries were used within one continuous BIN recording. History contains supported logged observations, not a physical inspection or independent battery-health measurement.

Related information

Clone this wiki locally