From f6c9d5a87f77f5ee0a77b3479c2b93fea963e032 Mon Sep 17 00:00:00 2001 From: mikecarper Date: Wed, 19 Aug 2026 11:54:19 -0700 Subject: [PATCH] Document legacy OTA airtime tuning --- docs/ota_easy.md | 6 ++++++ docs/ota_protocol.md | 6 ++++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/ota_easy.md b/docs/ota_easy.md index aaed6432..7318fe30 100644 --- a/docs/ota_easy.md +++ b/docs/ota_easy.md @@ -311,6 +311,12 @@ For a powered bench update where restart-resume is not needed, `ota config check removes periodic progress writes. It is a smaller optimization than selecting the correct hop count and it trades away persisted mid-download resume; restore the previous checkpoint cadence afterward. +Current repeater firmware automatically uses the full transmit budget during a bounded TempRadio window. +Older receivers do not: if `get af` reports a nonzero value on such a node, record it, use `set af 0` for the +maintenance window, and restore it afterward. This affects how promptly the legacy receiver can send its next +block/proof request; it does not increase LoRa transmit power. Use a full duty budget only where the selected +frequency and local rules permit it. + The update is ready when the status says `ready to install`. Discovery is background traffic, while an active OTA download is primary mesh traffic. At the temporary-radio settings in this guide, allow roughly **one hour** for a typical ESP32 full image over a quiet, direct link. That is a planning estimate, not an diff --git a/docs/ota_protocol.md b/docs/ota_protocol.md index 805d85f4..4e7564ab 100644 --- a/docs/ota_protocol.md +++ b/docs/ota_protocol.md @@ -556,8 +556,10 @@ This keeps each active transfer as one transmitter and one receiver while still repeaters between them and persistent archive nodes to improve future availability. TempRadio is treated as a private maintenance network. Active transfer packets use priority 0, bypass the -public-flood receive holdoff, retain the relay role's airtime-scaled transmit collision window, and do not -schedule generic flood retries. The bounded serving +public-flood receive holdoff, use the full transmit budget without overwriting the saved normal-radio airtime +factor, retain the relay role's airtime-scaled transmit collision window, and do not schedule generic flood +retries. Deployed firmware predating that TempRadio budget override can be accelerated manually with a saved +`get af` / temporary `set af 0` / restore sequence. The bounded serving queue admits at most two DATA/PROOF packets ahead of the radio while preserving at least four free packet-pool entries. CAD remains enabled to arbitrate the half-duplex channel, but its busy retry is scaled to one-quarter of a packet airtime and clamped to 5-50 ms instead of the ordinary 120-360 ms cadence. Discovery traffic keeps