witness: ESP-NOW 120s soak — 1151 tx 0 fail, 9.6/s, no crash

Real empirical evidence the ESP-NOW sync transport is long-term stable
on the C6 (D-workaround). Single-board capture on COM9, latest firmware
on branch (8eaa92cf2):

  Captured 33586 bytes over 120 s
  ESP-NOW samples: 24
    first: tx=1    fail=0 rx=0 match=0 leader=1 offset=0
    last:  tx=1151 fail=0 rx=0 match=0 leader=1 offset=0
    TX rate: 9.6/s (target ~10/s)
    TX failure rate: 0.00%
  app_main calls (reset detector): 1  -> no crash

The 9.6/s vs 10/s gap is FreeRTOS timer schedulability slop at 100 ms
ticks, not a transport issue. Zero TX failures over 1151 attempts +
zero resets in 2 min = the ESP-NOW path is production-grade as a
transport. Only the cross-board RX measurement is blocked on the other
boards' USB enumeration.

Ref: ruvnet/RuView#762 / draft PR #764 / D-workaround

Co-Authored-By: claude-flow <ruv@ruv.net>
This commit is contained in:
ruv 2026-05-22 22:51:25 -04:00
parent 8eaa92cf21
commit b808a6380b
1 changed files with 1 additions and 0 deletions

View File

@ -63,6 +63,7 @@ After D1 confirmed the 802.15.4 RX path is unfixable from user code in this IDF
| `c6_sync_espnow_init()` succeeds at runtime | COM9 boot log: `I (5226) c6_espnow: init done: local_id=206ef117053c leader=yes(candidate) period=100ms` |
| ESP-NOW TX path delivers reliably | COM9: `c6_espnow: tx#101 (fail=0) rx#0 (match=0)` over ~15 s — 100% TX success rate at the configured 100 ms cadence |
| Build green for both targets | `firmware-ci.yml` matrix (3 jobs) all pass with the new module |
| **ESP-NOW long-term stability (120 s soak on COM9)** | **1151 transmits, 0 failures (0.00 %), 9.6 tx/s sustained, no crash/reset in 2 min.** Boot detector saw exactly 1 `app_main` call. Sample summary: <br>`first: tx=1 fail=0 rx=0 match=0 leader=1 offset=0` <br>`last: tx=1151 fail=0 rx=0 match=0 leader=1 offset=0` |
The cross-board RX measurement was attempted but the other 3 boards (COM6/COM10/COM12) dropped off USB enumeration mid-experiment (presumably brown-out from repeated DTR/RTS resets) and couldn't be recovered without a physical replug. **Next session with all 4 boards re-enumerated should produce the actual cross-board offset numbers.** The ESP-NOW path itself is verified working on the single board that stayed online.