docs/bench: on-air TX throughput vs wfb-ng (svpcom) + SDR duty tool#109
Merged
Conversation
c3e5b4d to
6994dc0
Compare
6994dc0 to
82eb509
Compare
…R tools Per-chip on-air TX throughput measured by USRP channel-occupancy, with the 8812AU as the benchmarked reference; devourer matches wfb-ng on the svpcom driver at parity (docs/wfb-ng-tuning.md). Adds tests/sdr_duty.py (ceiling-free duty-cycle metric), tests/bench_onair.py, the DEVOURER_TX_PAYLOAD_BYTES knob, and a USB Vbus-sag hardware gotcha (5 GHz TX browns out through bus-powered hub chains — use a powered hub / root port; figures marked with a dagger are power-bound on the test bench, not chip limits). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
82eb509 to
fd0a8ed
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
An SDR-measured on-air TX throughput benchmark for the Jaguar family — per-chip, and devourer (userspace libusb) vs wfb-ng (the
svpcom/rtl8812audriver +wfb_tx) — plus a ceiling-free measurement tool and a writeup of the most efficient wfb-ng config.devourer vs wfb-ng (USRP B210 channel-occupancy, clean 5 GHz ch149, 1500 B)
Both deliver the same on-air injection throughput. After FEC (k/n=8/12): MCS1 ≈ 8 Mbps, MCS7 ≈ 35 Mbps — consistent with wfb-ng's ~7 Mbps default and OpenIPC's 52-total/36-video figures.
Per-chip on-air throughput (README hardware table)
HT MCS7 / 20 MHz, USRP-measured. 8812AU is the fully-benchmarked reference (56 / 52 / 52 Mbps at 2.4 GHz / UNII-1 / UNII-3). 8821AU does 54 / 32 / 28. 8814AU saturates 2.4 GHz (65) and reaches ~32 Mbps at 5 GHz on a powered port.
USB-power caveat: 5 GHz TX is current-hungry and browns out through deep bus-powered hub chains — frames submit fine but on-air power collapses, intermittently, while 2.4 GHz keeps working. Figures marked
†in the README are bench-power-bound, not chip limits. A new CLAUDE.md USB Vbus sag gotcha documents the symptom, theuhubctlrecovery, and the powered-hub fix (plus how to avoid mis-diagnosing it as a per-chip/EFUSE/gate bug).Other findings
Changes
tests/sdr_duty.py— USRP energy/duty-cycle on-air throughput (ceiling-free; a Wi-Fi monitor sniffer caps ~2900 fps and undercounts).tests/bench_onair.py— per-chip per-band on-air throughput sweep (drives the README table).txdemoDEVOURER_TX_PAYLOAD_BYTES— pad PSDU to N (3993 = wfb-ng max frame).inject_beacon.py--size+--max-rateAF_PACKET blaster.docs/wfb-ng-tuning.md— optimal wfb-ng config (svpcom driver, MCS/40 MHz/short-GI/LDPC/STBC, tx-pwr override, clean 5 GHz) + the comparison + methodology + reproduce steps.README.md— per-chip on-air TX throughput in the hardware-landscape table.CLAUDE.md— USB Vbus-sag hardware gotcha.🤖 Generated with Claude Code