Multi-receiver ground station: N radios / N channels / one timebase — nothing measured beyond 2 TX → 1 RX
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- c
- 領域
- networking, testing-qa
調査の方向性
Start with docs/scheduled-mac.md, the linked film-set preview-link document, and the bench notes for the existing two-transmitter measurements; inspect the RX-loop and rx.ring metrics, UeRxAttribution, energy/busy sensors, and the testrig PTP nodes. Measure the requested adapter and Ethernet-node matrices, adjacent-channel effects, attribution at higher N, and co-channel delivery, then document each result’s limits and recommend a ground-station shape.
索引モデルが issue の本文から書いたものです。
説明
Every receive-side measurement in this project is one radio on one channel, and the largest multi-transmitter experiment on record is two transmitters into one receiver (per-UE RX attribution, docs/scheduled-mac.md). A ground station that has to hear many transmitters on many channels at once has no story: no test, no doc, no tool, no measured number.
Motivation
The film-set preview-link case (docs/film-set-preview-link.md, #254 comment): 2–25 cameras uplinking 1080p60 into one video village. The arithmetic makes it a 10–25-channel plan with one receiving radio per channel — a receiving USB adapter has the same ~50–60 Mbps airtime ceiling as a transmitting one, and 25 CSMA transmitters on a shared channel defer rather than add. So the receiving end is N radios, not one, and the open questions are all about N.
Questions this issue exists to answer (measure, don't assume)
- N adapters on one host. How many devourer RX loops can one x86/ARM host run before the USB tree or the RX rings become the ceiling? Per-adapter frame rate and pool stalls (
rx.ring) vs N, on a hub topology that actually powers N adapters (the VBUS-sag traps in the bench notes apply). Where is the knee: 4, 8, 16? - N nodes over Ethernet instead. The alternative shape is one small RX+decode box per monitor, each on its camera's channel, with the recorder pulling streams over the tent LAN. This needs nothing new in the radio core but does need a timebase story: N independent TSF domains vs one PTP-disciplined timebase (the
testrigPTP nodes are the scaffold, M4 in #254 is the milestone). - Adjacent-channel self-interference at the ground station. 10–25 radios receiving 20 MHz channels a few MHz apart, antennas within a metre of each other — does adjacent-channel leakage from the neighbouring receiver's channel cost sensitivity? This is measurable today with two adapters and the energy/busy sensors.
- Per-transmitter attribution at N.
UeRxAttributionholds 64 by default and was tested at 2. Does per-TA windowing stay honest at 10–25 transmitters with the same cadence ratios measured at 2? - What a chip does when 25 transmitters share a channel anyway (the worst case the channel planner has to prevent): frame-count and delivery vs N co-channel transmitters, so the planner's "one or two per channel" rule is a measured constraint rather than a guess.
Shape of the deliverable
A measured matrix (N adapters on one host; N nodes over Ethernet), a doc section pairing each number with what it does not prove, and a recommendation between the two ground-station shapes. No library change is expected up front; anything found that userspace cannot do gets its own issue.
Not in scope
Range (no kilometre measurement exists anywhere; needs a field day with a vendor-driver control), the HDMI/SDI encoder side (ecosystem gap, not devourer), OFDMA/UL-MU (#236).
Relates to #254 (M4/M5 are this problem in different clothes), #381 (ARM cell node), #382 (per-chain sectors at the ground station).
- 主要言語
- C
- スター
- 56
- フォーク
- 29
- 平均マージ
- 3時間 43分
- マージ済み PR(30日)
- 75
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
OpenIPC/devourer のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)対応中かも @josephnef が今日担当しました。 オープンenhancement
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 12/100
OpenIPC/devourer#579 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 12/100
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 8/100
メンテナーはふだん 1 日以内に返信
OpenIPC/devourer の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
Needs-Triage
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
メンテナーはふだん 2 日以内に返信
-
issue: bug report
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 2 日以内に返信
-
cross-platform fix-now
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
feature:index kind:crash status:confirmed triaged
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
clice-io/clice#1123 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信