Been running the MultiNav Pro+ BLE module in a field telemetry setup and I'm trying to figure out if tweaking the connection interval actually makes a meaningful difference at the longer end of the range. Right now I'm sitting at the default interval and things are mostly stable, but I'm seeing occasional missed packets that I suspect might be timing-related rather than pure signal quality. Wondering if stretching the connection interval out buys me anything in terms of link reliability when I'm pushing closer to that 50km spec, or if it's just trading throughput for nothing.</TITLE>
My gut says a longer interval gives the radio more time to "settle" between events at extreme range, especially if there's any propagation delay factor creeping in, but I genuinely don't know if that's how it works in practice or if I'm just making that up. The 2Mbps PHY is great when it's clean but I'm also not sure if there's a point where dropping to the slower PHY would actually stabilize things even at the cost of speed. Anyone switched PHY modes mid-deployment to recover a flaky link?
Also curious if the power/program kit's supercap system has any influence here - I've seen UART glitches on my dev bench that I'm pretty sure are power brownout artifacts, not the BLE link itself. Would love to know if others separated those two failure modes cleanly or if it took a while to figure out which was causing drops. I'm logging RSSI alongside my packet counters but honestly not sure if that's enough to tell the story.
