@Jason Lambert good question, and honestly one of the more interesting RF edge cases with this module.
The 50km figure is drone-to-drone with both units airborne, so you're already in a best-case propagation scenario where the link budget is working hard for you — but you're right that at those distances the retransmit cost on a bad hop is non-trivial. The STM32WB07 at the core of the MultiNav Pro+ does support channel map configuration, so you're not stuck with the full 37-channel sweep if your RF environment is known and clean. The firmware repo is public on GitHub (github.com/RFOXiA/MultiNav-Pro-Long-Range-BLE-Module-Firmware-STM32WB07) and that's probably your fastest path to seeing exactly how the channel management is exposed at the firmware level right now.
For a wide open asset tracking site where you have some control over the RF environment, locking to a subset of clean channels and tightening the connection interval is likely going to give you more predictable link behavior than relying on AFH to adapt dynamically at that range. That said, the specifics of what's configurable out of the box versus what needs custom firmware work is worth a direct conversation with Moamen — the AI Firmware Builder in the Dev Hub is also worth trying if you want to prototype a config quickly before going deep on the STM32WB07 datasheet.
What's the asset density on your site? That changes the calculus a bit on whether you're optimizing for single long-range links or something closer to a mesh topology.
