MultiNav Pro+ BLE - frequency hopping behavior at extreme range, worth disabling?

Melinda Weaver•July 25, 2026

Been running a point-to-point link test with two MultiNav Pro+ BLE modules over a pretty flat open field setup, trying to push toward the advertised 50km range spec. Link is decent but I'm noticing what looks like periodic dropouts that coincide with channel hops - at least that's my suspicion based on the timing. Makes me wonder if the adaptive frequency hopping is working against me at this range because some channels in the 2.4GHz band are just cleaner than others in my environment, and the hopping might be landing on noisier channels and tanking SNR momentarily before it adapts back out.

💬 2 replies👍 0 likes👁 0 views

Replies

Dana Whitney•July 25, 2026

Yeah that tracks - AFH is great in dense RF environments but at extreme range you're already fighting path loss so getting bounced onto a noisier channel mid-link can absolutely kill you. If your environment is relatively stable interference-wise, locking to a fixed channel (or a narrow manual hopping table) is worth testing just to isolate whether the hops are actually your culprit. Check what the firmware exposes for channel map config, I know some builds let you whitelist specific channels but I don't remember if that made it into the Pro+ release or if it's still on the roadmap.

Adam•July 25, 2026

@Melinda Weaver the channel map config question is a good one — the STM32WB07 actually does expose channel classification controls at the HCI level, so it's not purely locked behind the AFH algorithm. Whether the current Pro+ firmware surfaces that cleanly as a user-facing parameter is worth checking in the repo directly: https://github.com/RFOXiA/MultiNav-Pro-Long-Range-BLE-Module-Firmware-STM32WB07

If the whitelist isn't exposed yet, you can still get a lot of diagnostic mileage by logging RSSI per-channel during the dropouts — if you consistently see the SNR floor on specific channel indices, that confirms your hopping hypothesis and gives you the exact channels to blacklist when the feature does land. At 50km you're already at the margin where even a 3-4dB hit from landing on a busy channel can break the link, so this is absolutely worth isolating before assuming it's a hardware ceiling.