fix(mesh): widen RNode KISS-detect read window from 800ms to 2.5s
Confirmed on real hardware: a genuine Heltec V4 RNode (firmware 1.86, verified via rnodeconf --info against the same port) prints extra boot/status chatter over the same serial line before answering KISS commands. Replaying the exact probe bytes and timing budget our Rust probe_rnode() uses showed DETECT_RESP arriving ~1.05s after the write — past the old 800ms deadline, so a real, correctly-flashed, correctly- responding RNode was being timed out and misclassified as "not an RNode". 2.5s leaves comfortable margin. Non-RNode devices (Meshcore/Meshtastic) already budget ~5s each, so this doesn't meaningfully slow down detection when the port turns out to be something else. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
458b9fbbb7
commit
791618f96f
@ -47,7 +47,14 @@ const KISS_CMD_PLATFORM: u8 = 0x48;
|
||||
const KISS_CMD_MCU: u8 = 0x49;
|
||||
|
||||
const PROBE_BAUD: u32 = 115200;
|
||||
const PROBE_READ_TIMEOUT: Duration = Duration::from_millis(800);
|
||||
// 800ms was too tight for real hardware: confirmed on a genuine Heltec V4
|
||||
// RNode (firmware 1.86, verified via `rnodeconf --info`) that prints extra
|
||||
// boot/status chatter on the same serial line before answering KISS
|
||||
// commands — DETECT_RESP measured arriving ~1.05s after the probe write in
|
||||
// that case. 2.5s leaves comfortable margin without meaningfully slowing
|
||||
// down detection of non-RNode devices (Meshcore/Meshtastic already budget
|
||||
// ~5s each).
|
||||
const PROBE_READ_TIMEOUT: Duration = Duration::from_millis(2500);
|
||||
|
||||
/// Prefix marking an LXMF `content` string as base64 of a raw binary
|
||||
/// typed-envelope payload rather than literal text. LXMF `content` travels
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user