跳转到内容
YBO 技术文档

20260925-0942-air-hub-model-split-industrial-platform Split Air Hub into a 2.4 GHz model and a sub-GHz model on an industrial Linux platform

  • status: completed
  • createdAt: 2026-09-25 09:42
  • approvedAt: 2026-09-25 09:46
  • relatedTask: 20260925-0942-air-hub-model-split-industrial-platform

Context

章节标题：“Context”

Owner decisions 2026-09-25: split into two products (2.4 GHz with firmware-selected BLE / Zigbee / Thread; sub-GHz with LoRa and 433 MHz); change the main-controller spec to industrial grade; 433 MHz must receive third-party OOK remotes; LoRa is standard LoRaWAN.

Current state:

  • P05-air-hub.md R0.4: single model; platform row "Linux (ARMv7, reference SSD202D) + 2×ESP32-C6", CAN via C6 TWAI (B1); environment row records the SSD202D gap against the family −25…+70 °C rule; §7 treats radios as a three-radio combined assessment; open items AIR-O-03 (SSD202D freeze) and AIR-O-09 (sub-GHz positioning).
  • P05-air-hub-design.md R0.2: §2.1 options A/B/C, §2.2 B1, §2.3 sub-GHz co-processor candidates, §2.5 SSD202D + RK3506J alternative, §3 diagram with two C6, §5–§7 three image chains.
  • P05-air-hub-guide.md: D0 gate names SSD202D and B1; V-09 "three images"; quotation lists sub-GHz/LoRa as options.
  • Brief and package index: single model, SSD202D + 2×C6.
  • Governance: product-plan.md rows at lines ~188/191/283 (platform, extensions, regional sub-GHz), open-questions.md items 3 and 7, compliance-matrix.md Switch row ("no Wi-Fi, LoRa"). Line spec P05-switch.md §2 table and model names. P12-tag.md line 19/39 treat the sub-GHz receiver as "Air Hub R3", a single-channel SX1262 gateway to be designed separately.
  • Evaluation facts used: RK3506J (−40…+85 °C, 2×CAN-FD, external DDR3L); FET3506J-C module; 2.4 GHz candidates; sub-GHz: LoRaWAN needs a concentrator — LCSC SX1302 $4.09 @100, SX1303 $6.01 @100, SX1250 $1.63 @1k (two per Corecell design); OOK needs a separate chip (CMT2300A $0.87, SX1276 $3.06, CC1101 $0.97). LoRaWAN bands (EU868 / US915, aligned with Tag) differ from 433 MHz, so the sub-GHz product carries two RF chains and two antennas.

Proposal

章节标题：“Proposal”

Structure: keep one package switch/air-hub/ with one spec and two models (as Air 2 / Air 4 share one spec). Model names: Air Hub (2.4 GHz, the existing Air / Key hub) and Air Hub LR (sub-GHz: LoRaWAN gateway + 433 MHz OOK). Common requirements stay shared; radio-specific rows are split per model.

  1. Spec P05-air-hub.md R0.5
    • §1: two models on one industrial Linux base board; Air only pairs with Air Hub; Air Hub LR does not serve Air (BLE) and is the regional receiver for Tag, LoRaWAN devices and 433 OOK remotes; both keep CAN, Key support (GW-06), P09 hosting.
    • §2: model table; platform row → industrial Linux SoC with native CAN, component grade −40…+85 °C (reference RK3506J), one radio function per model; environment row drops the SSD202D gap; wireless row per model; power row unchanged as target, measured per model.
    • §3: GW-01…06 unchanged, scoped to Air Hub where they concern Air; new GW-07 (Air Hub firmware-image switching: BLE / Zigbee / Thread, verified image per function, Air control only in BLE image), GW-08 (Air Hub LR LoRaWAN gateway: 8-channel concentrator, regional plan EU868 / US915, packet forwarder or Basic Station, LNS location per AIR-O-12), GW-09 (433.92 MHz OOK: receive fixed-code / learning-code remotes; OOK sources carry no authentication and are limited like wireless_key or stricter, never bound to critical circuits; transmit is AIR-O-13).
    • §7: per-model radio assessment (2.4 GHz single radio; LR: EN 300 220 at 433 and 868, FCC 15.247 at 915, 433 in the US under 15.231 only).
    • §8: AIR-O-03 reworded (RK3506J freeze, module vs chip-down, DDR3L supply, lifecycle); AIR-O-09 reworded (Air-side sub-GHz only; Air Hub side settled by Air Hub LR); new AIR-O-11 (2.4 GHz radio freeze: EFR32MG21 / CC2674P10 / nRF54L15), AIR-O-12 (LoRaWAN LNS local vs external, regions), AIR-O-13 (433 OOK transmit and US 315 MHz).
  2. Design R0.3: §2.1 adds option D (industrial Linux + one radio per model) as direction, A/B/C kept as history with B marked superseded; §2.2 CAN from SoC, B1 superseded; §2.3 rewritten for Air Hub LR (SX1302/SX1303 + 2×SX1250 or module; OOK chip); §2.5 per-model devices (RK3506J / FET3506J-C, T113-i alternative; Air Hub radio EFR32MG21, alternatives CC2674P10 and nRF54L15; LR concentrator + CMT2300A or SX1276); §3 diagram and roles; §5–§7 two image chains (Linux + radio) instead of three.
  3. Guide: D0 gates, V-09 wording, new V-11 (Air Hub image switching) and V-12 (LR LoRaWAN and OOK), quotation per model.
  4. Brief and package index: two models.
  5. Evaluation page §1 boundary: note the decisions were adopted on 2026-09-25.
  6. Governance: product-plan platform / extension / regional rows; open-questions items 3 and 7; compliance-matrix Switch row plus Air Hub LR row. Line spec P05-switch.md §2 table and model names. P12-tag.md "Air Hub R3" references → Air Hub LR (LoRaWAN concentrator), with the Tag single-channel assumption left to Tag's own open item.
  7. Changelog, task, plan.

Risks

章节标题：“Risks”
  • Model name "Air Hub LR" is a proposal; renaming later touches every file above.
  • Tag's radio design assumed a single-channel proprietary link; a LoRaWAN concentrator can still receive proprietary LoRa packets on its channels, but Tag's access mode is not re-designed here.
  • 433 OOK remotes are unauthenticated; the restriction rule must reach X02 (source classes) in a later task.

Scope

章节标题：“Scope”

In: files in Proposal 1–7. Out: Air package, X01 / X02 foundation files, P09 / P03 / P12 design content beyond cross-reference wording, research pages.

Alternatives

章节标题：“Alternatives”
  • Separate package and product ID for the sub-GHz product (heavier: new package, product-plan and product-index entries, redirects).
  • Keep sub-GHz as an option slot on one board instead of a second model.