Expand description
rusty_esp_signal — The radio-application layer remade in Rust: Wi-Fi CSI radar (presence/motion), LoRa point-to-point over lora-phy, BLE provisioning and telemetry over trouble-host, Wi-Fi station/AP lifecycle and ESP-NOW framing — every frame mID-signed. Memory safe, no_std core.
This is the facade: it re-exports the no_std core and exposes the
chip backends under esp. Depend on this crate; reach into the
sub-crates only when you are building a backend.
Part of Janus (Remade With Rust). Plan: docs/plans/rusty_esp_signal.md.
Modules§
- ble
- The Janus GATT table as data: three services (provisioning, manifest, telemetry), their characteristics, and the 128-bit UUIDs they live under.
- esp
- Chip backends (
esp-halfor Track B,esp-idffor Track A). - esp_
core rusty_esp_core— the shared vocabulary of the Janus ESP family.- link
- The authenticated link every ESP-NOW and LoRa frame travels in.
- lora
- LoRa modem parameters, exact time-on-air, the regional duty-cycle budget and the unauthenticated discovery beacon.
- mid
rusty_esp_mid-core— MATA mID on the chip, the pure core.- prelude
- The names a sketch or firmware wants in scope.
- provision
- BLE provisioning: the provisioning service carries the setup session.
- radar
- Radar: presence, motion and breathing without a camera.
- setup
- The setup session’s cryptographic core (enc-ble M1): the protocol of
docs/setup-protocol.mdin the Janus umbrella, v1, suite 1. - wifi
- Wi-Fi station credentials that never print, the TLV they travel in over BLE provisioning, the station reconnect policy and RSSI statistics.
Constants§
- VERSION
- Crate version, for capability manifests and logs.