TELEMETRY_CAPTURE: Option B requires no device interaction

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Robert McMahon 2026-02-07 12:37:42 -08:00
parent 07b3283518
commit cf7748960f
1 changed files with 4 additions and 6 deletions

View File

@ -17,7 +17,7 @@ monitor start [-c <channel>]
This puts the device in WiFi monitor mode and **automatically** writes MCS telemetry to `fiwi-telemetry` on the SD card every 10 seconds. No extra configuration needed.
> **Note:** Monitor mode disconnects WiFi. The device will not be on the network while capturing. Use **serial** to capture telemetry in this case. To capture over **WiFi**, run `monitor stop` first so the device rejoins the network, then download the telemetry file.
> **Note:** Monitor mode disconnects WiFi. The device will not be on the network while capturing. Use **serial** (Option A) to capture while in monitor mode. Use **WiFi** (Option B) when the device is back on the network—e.g. after reboot, or after running `monitor stop` if you have serial access.
Check telemetry status:
@ -50,13 +50,11 @@ Serial transfer is limited to 512 KB per file.
---
### Option B: WiFi + beacon discovery (device on network)
### Option B: WiFi + beacon discovery (no device interaction)
Use when the device is in STA mode and connected to the same LAN as the laptop. The device advertises itself via UDP broadcast on port 5555.
Use when the device is on the network (STA mode) and connected to the same LAN as the laptop. **No serial or device interaction required**—the device advertises itself via UDP broadcast on port 5555. Telemetry must already be on the SD card (from a previous monitor session, e.g. device ran monitor mode in the field, or rebooted back to STA).
**1. On the device:** Run `monitor stop` so it reconnects to WiFi. Telemetry is already on the SD card from when monitor mode was running.
**2. On the laptop:**
**On the laptop:**
```bash
# Listen only (see devices, no download)