survive disconnect during BLE MTU lookup
This commit is contained in:
Vendored
+5
@@ -63,6 +63,11 @@ removed before production firmware was built and flashed.
|
||||
final status records one disconnect and one deliberate frame replay, with
|
||||
zero notification failures or invalid ACKs. It validates that the 10.24-second
|
||||
queue covered the measured resubscription interval without permanent loss.
|
||||
Of its 2,575 contiguous sample intervals, 1,293 differ from exactly 10 ms.
|
||||
Absolute deviation has a 4 us median, 160 us p95, 170 us p99, and 780 us
|
||||
maximum; cumulative error is 152 us over 25.75 seconds. This records bounded
|
||||
BLE scheduling jitter without rate drift and requires timestamp-derived `dt`
|
||||
in future fusion work.
|
||||
|
||||
`tests/test_trikke_protocol.py` verifies the hashes, parses the captures in
|
||||
fragmented chunks, and asserts these signatures so the hardware evidence remains
|
||||
|
||||
Reference in New Issue
Block a user