Skip to content

Instantly share code, notes, and snippets.

@ruvnet
Last active July 19, 2026 04:31
Show Gist options
  • Select an option

  • Save ruvnet/5ca5a27f2e607dcfcf0e3655fdec2d62 to your computer and use it in GitHub Desktop.

Select an option

Save ruvnet/5ca5a27f2e607dcfcf0e3655fdec2d62 to your computer and use it in GitHub Desktop.
RuView update: Realtek, MediaTek, Qualcomm, and vendor sensing program (2026-07-18)

RuView hardware sensing update ? 2026-07-18 (Toronto)

Today RuView and Cognitum.one moved two vendor integrations from research into reproducible, simulator-first Rust betas. Both integrations label synthetic data explicitly and stop short of claiming physical-hardware validation before the boards and vendor SDKs arrive.

Realtek RTL8720F radar beta

  • Merged RuView PR #1356.
  • Published v0.9.0-realtek-beta.1.
  • Added a deterministic RTL8720F radar simulator, parser/validation boundary, sensing-server integration, tests, documentation, and ADRs.
  • Opened the upstream Ameba RTOS announcement and collaboration thread: Ameba-AIoT/ameba-rtos#1338.
  • Physical RTL8720F validation remains scheduled for when the hardware and vendor SDK arrive.

MediaTek Filogic CSI beta

  • Merged RuView PR #1358.
  • Published v0.9.1-mediatek-beta.1.
  • Added deterministic profiles for MT7981+MT7976, MT7986+MT7975, and MT7988+MT7996.
  • Defined the versioned MTC1 application envelope for complex I/Q, MIMO dimensions, RSSI, bandwidth, PPDU metadata, provenance, sequence/timestamp, and CRC32.
  • Added strict Rust validation, UDP ingestion, latest-frame REST output, bounded WebSocket summaries, replay generation, and explicit mediatek:simulated provenance.
  • Published Windows binaries, three deterministic replay captures, and SHA-256 manifests.
  • Opened the upstream mt76 announcement/RFC: openwrt/mt76#1106, cross-referencing the existing MT7916 HE160 investigation in mt76#1087.

Validation completed

  • Hardware crate: 183 tests passed; one timing-sensitive test remains intentionally ignored.
  • Sensing server: 177 tests passed.
  • Targeted MediaTek codec/summary tests: 9 passed.
  • Clippy completed for hardware and sensing-server targets with only pre-existing warnings.
  • Optimized Windows release builds completed.
  • Live UDP simulator-to-server checks passed for all three profiles.
  • Replay determinism was confirmed; the MT7986 fixture SHA-256 is 3f93b0d71afec8c9e78da85fc6667ac3fa87b10e1ea92727951d0a60afb3f223.
  • Invalid oversized 4x4x1024 frames were rejected as designed.
  • All required GitHub checks passed before merge.

Next hardware gate

Once boards and SDKs arrive, we will replace simulator-only confidence with captured-vs-simulated fixtures, verify vendor metadata and scaling, exercise loss/rate behavior on the physical transport, and document firmware/SDK provenance. For MediaTek, the upstream question is especially important: public firmware support for CSI export varies, so RuView?s adapter will follow a confirmed mt76/firmware boundary rather than assume private interfaces.

Qualcomm Atheros CSI beta

  • Merged RuView PR #1359.
  • Published v0.9.2-qualcomm-beta.1.
  • Added the bounded Rust QCS1 codec, deterministic QCA9300/QCN9074/QCN9274 simulator profiles, UDP/REST/WebSocket integration, replay fixtures, and SHA-256 manifests.
  • QCA9300 is the first physical baseline; QCN9074/QCN9274 remain explicitly simulator-only until a public firmware export path is confirmed.
  • Published the PicoScenes interoperability RFC: wifisensing/PicoScenes-Issue-Tracker#77.

Repeatable vendor integration program

ADR-270 now classifies RF Solutions, Origin AI, Plume, Linksys, Electric Imp, Mist/Juniper, Luma, Google Nest, NETGEAR, and Wifigarden by actual capability: complex CSI, derived sensing, RF telemetry, network-only, or unsupported. Every provider must pass the same research, contract, simulator, Rust validation, physical-hardware, provenance, and publication gates. A simulator can validate software behavior but never proves CSI availability or RF accuracy.

RuView ADR-270 vendor provider beta — 2026-07-19

RuView and Cognitum.one published the Rust-centric ADR-270 vendor RF provider beta after a concurrent implementation and validation pass.

  • Merged RuView PR #1360.
  • Published v0.9.3-vendor-providers-beta.1.
  • Added capability-safe outcomes for Origin AI, Plume/OpenSync, Mist/Juniper, NETGEAR Insight, Electric Imp, RF Solutions, Luma/OpenWrt, Google Nest, Linksys, and Wifigarden.
  • Added deterministic JSONL/UDP simulation for the eight providers with defined event contracts. Linksys fails closed as unsupported and Wifigarden fails closed as contract-required.
  • Added strict bounded Rust decoders/request plans, REST ingestion and latest state, canonical synthetic UDP transport, and WebSocket summaries.
  • Published Windows server/simulator binaries, eight deterministic 100-frame replay fixtures, and SHA-256 manifests.
  • Opened the public RuView announcement at ruvnet/RuView#1361.
  • Opened the Mist interoperability announcement/RFC at mistsys/mist_openapi#69. Plume/OpenSync has public issues disabled, so no issue was posted there.

Validation

  • Hardware crate: 192 passed; one intentional timing test ignored.
  • Sensing-server library: 485 passed.
  • Sensing-server binary: 179 passed.
  • Integration suites: 5, 8, 4, 16, and 18 passed.
  • Provider matrix: 30 targeted tests passed.
  • Post-merge SAST, dependency, secret, license, policy, infrastructure, and container security scans passed.
  • Default and CIR feature-gated workspace benches compiled successfully.
  • Live optimized simulator-to-server validation accepted all eight supported providers; Linksys returned 501 and Wifigarden returned 403 as designed.

This beta validates RuView software contracts and simulation. It does not claim vendor credentials, commercial SDK rights, complex CSI for telemetry-only providers, or physical hardware validation. Every provider remains hardware_validated: false until live evidence is captured and published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment