docs: distinguish measured TX wall time from true channel occupancy
This commit is contained in:
@@ -61,3 +61,29 @@ a production repeater.
|
||||
to any SX126x-based design. Budget for it, or implement early-stop RX.
|
||||
- Repeat-delay accuracy of a few microseconds shows the ESP32-S3 side has
|
||||
ample timing margin; timing precision will not be the constraint.
|
||||
|
||||
## Airtime measurement vs true channel occupancy
|
||||
|
||||
`tx_airtime_us` and the duty-cycle ledger both use wall time from `SetTx`
|
||||
to the moment `TxDone` is observed. That interval includes SPI round-trips
|
||||
and up to ~1 ms of polling granularity, so it over-states true channel
|
||||
occupancy:
|
||||
|
||||
```
|
||||
computed airtime, 102-byte payload : (102 * 80 us) + 640 us = 8.8 ms
|
||||
measured SetTx -> TxDone observed : 13.4 ms median
|
||||
```
|
||||
|
||||
Consequences, both deliberate:
|
||||
|
||||
- The reported duty cycle is conservative (over-counted by roughly 50 %),
|
||||
so the 0.1 % guard suppresses slightly earlier than strictly required.
|
||||
For a compliance guard, erring high is the safe direction.
|
||||
- Independent confirmation that the real occupancy matches the computed
|
||||
airtime comes from the SDR side, not the firmware: observed burst
|
||||
durations in raw IQ differ from the computed airtime by 0.2-1.5 ms
|
||||
(median 1.2 ms), i.e. the transmission itself is ~9-10 ms for a 100-byte
|
||||
frame as expected.
|
||||
|
||||
A production implementation should budget on computed airtime and use the
|
||||
measured value only for latency diagnostics.
|
||||
|
||||
Reference in New Issue
Block a user