Jaguar2 8822BU TX does not air at level for ~4 s after its first submitted frame
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- c, linux
- Ambito
- embedded-iot
Direzione di ricerca
Start with the mentioned tests/busy_window_probe.cpp and tests/busy_window_probe.sh, then run the reproduction with FLOOD_SETTLE_S=0 using a Jaguar3 sensor and RTL8822BU T3U on channel 165. Compare the first submitted frame with the sensor’s busy-window readings, and first A/B test the onset using the vendor rtl88x2bu driver. Done means identifying whether the initial ~4-second low-reading period is reproducible and whether it is specific to this port; the cause is not established in the issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What was seen
A Jaguar2 RTL8822BU (TP-Link Archer T3U, 2357:012d) driven by txdemo at max duty (DEVOURER_TX_RATE=MCS1 DEVOURER_TX_GAP_US=0, ch165) does not air at level for ~4 s after its first submitted frame. Found while re-validating #437 on this bench: the Jaguar3 sensor's first armed busy window read a valid 0% on a channel that was 64% busy a second later.
Sensor first, flooder second (RTL8812CU sensor, 120 × 50 ms ArmChannelBusy windows, tests/busy_window_probe.cpp):
| cycle | flooder's first bulk_send |
sensor first non-zero window | gap |
|---|---|---|---|
| 1 | window #37 | window #99 (11%, then 61-65%) | ~62 windows ≈ 4.0 s |
| 2 | window #38 | window #100 (56%, then 61-65%) | ~62 windows ≈ 4.0 s |
The complementary arm, flooder first: 5/5 sensor bring-ups launched 4 s after the flooder saw seven 50 ms windows at 0% before the load appeared; 5/5 with the flooder running >10 s were at 61-65% from the first window. 15 s of sensor idle before bring-up changes nothing. So it is the transmitter's onset, not the receiver's.
txdemo reports submitted frames from its first bulk_send, and the bulk-OUT calls return OK, so from the host's side the flooder is transmitting the whole time.
Why it matters
- Any harness that starts a Jaguar2 flooder and measures within ~5 s measures an idle channel and cannot tell.
tests/busy_window_probe.shnow waits for it (measured value + margin,FLOOD_SETTLE_S), and the sensing doc carries the caveat; other loaded-channel harnesses that use a Jaguar2 flooder should be checked. - On the link itself: the first ~4 s of a Jaguar2 TX session are, as far as a co-channel receiver is concerned, not at the level the rest of the session runs at. For a quick-connect FPV downlink that is the part of the session that matters most.
What is not known
- Whether it is power (weak), a wrong channel, or no radiation at all during the window — the sensor's CLM cannot tell those apart. An SDR read of the first 5 s would.
- What ends it at ~4 s. Candidates in the Jaguar2 bring-up: the thermal/pwr-track first tick, the DIG/EDCCA operating point settling, or something in the USB smart-switch sequence on this unit (the T3U boots USB2 and re-enumerates USB3).
- Whether the 8821CU and the CF-924AC (
0bda:b812, external antennas) do the same — only the T3U was the flooder here. - Whether the vendor
rtl88x2budriver shows the same onset. That A/B is the first thing to run before attributing it to the port.
Reproduce
Bench with a Jaguar3 sensor and the T3U on ch165, branch of #437:
sudo tests/busy_window_probe.sh # with FLOOD_SETTLE_S=0 the first arm reads 0%
Or the sensor-first form: start BusyWindowProbe --vid 0x0bda --pid 0xc812 --channel 165 --mode window --window-ms 50 --reps 120, then txdemo on the T3U ~3 s later, and count windows between its first bulk_send and the sensor's first non-zero reading.
🤖 Generated with Claude Code
- Lingua principale
- C
- Stelle
- 56
- Fork
- 29
- Merge medio
- 3h 43m
- PR unite (30g)
- 75
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di OpenIPC/devourer
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)Forse già presa @josephnef l’ha presa oggi. Apertaenhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
OpenIPC/devourer#579 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 8/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di OpenIPC/devourer
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Needs-Triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 2 giorni
-
issue: bug report
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 2 giorni
-
cross-platform fix-now
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
feature:index kind:crash status:confirmed triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
clice-io/clice#1123 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno