Documentation
Onboarding
Getting Started
Power & Battery
Hardware & Components
Build & Assembly
Radio & RF Design
Frequencies & Regulations
Firmware & Software
USB & Connectivity
GPS & Navigation
Morse & Communication
Modes & Operation
Field Operations & Rescue
Building Effectively
Build Variants
Project & Reference
Docs Firmware & Software Config Backup

Config Backup

Edit on GitHub

Backing up and restoring the beacon's configuration: the serial dump, the file format, and the restore procedure.

Config Backup

Your configuration is the product of an evening’s careful work: callsign, channels, power, GPS settings. A factory reset or a firmware migration wipes it in a second. Backups are the answer.

The backup

The serial debug build provides the dump:

CODE
config dump

which prints every setting as key-value lines. Save the output to a file. That file IS the backup: human-readable, diffable, restorable.

The format

CODE
frequency=433100000
power_dbm=17
sleep_interval_s=10
repeat_count=1
wpm=12
gps_enabled=1
identity=IK2XYZ
...

Each line is key=value, matching the keys in Firmware NVS Keys.

The restore

  1. Factory reset (see Factory Reset and Recovery) for a clean base.
  2. Connect serial, enter the debug console.
  3. Feed the file: config set <key> <value> per line, or paste the whole file where the console accepts batch input.
  4. config dump again and diff against the backup to confirm.

The habit

  • Back up after every configuration session.
  • Keep the backup with the emergency card (see Emergency Kit).
  • Version the backup file in the repo if the config is a “known good” mission profile.