RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ BLE at 50km - what kind of line-of-sight conditions are needed?

Joseph RodriguezJune 23, 2026
Hey everyone, been digging into the MultiNav Pro+ BLE module for a project I'm putting together - basically a long-range telemetry link between a ground station and a UAV. The 50km range spec is obviously what caught my attention but I'm trying to wrap my head around what real-world conditions that number assumes. Like is that measured over flat open water, elevated hilltop-to-hilltop, or is there actual test data with modest terrain/vegetation in the path? I know BLE long range mode (coded PHY, S=8) inherently trades throughput for sensitivity but even then 50km is a bold number and I want to understand the antenna setup on both ends before I commit to a design.
💬 3 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

AdamJune 23, 2026
@Joseph Rodriguez good questions, and you're clearly coming at this from the right angle technically.
 
The 50km figure is the drone-to-drone number — both modules airborne, which eliminates ground reflections and multipath almost entirely. That's where you get the clean link budget that supports that kind of distance. For your use case with a ground station on one end, you're in the 15-20km man-to-drone territory, which is still well beyond anything else at this price point but worth setting expectations correctly before you design your link margin around the headline number.
 
On antenna setup — the module uses an external antenna configuration, and that's a big part of how it achieves the sensitivity numbers it does. For a UAV telemetry build I'd think about antenna placement on the airframe carefully (keeping it clear of carbon fiber and ESCs) and on the ground station side a directional antenna with a tracker would obviously push your practical range further if you need it.
 
As for terrain and vegetation — honestly any significant obstruction at these ranges will bite you, not because the module is weak but because physics doesn't negotiate. Water and elevated terrain are naturally favorable. If you've got rolling hills or tree cover in the path you're going to see degradation, and I'd plan for that in your link budget rather than assume clean LOS. If you want to share more about your specific deployment scenario I can probably give you a more grounded take on whether the spec fits your use case.
Mary ThomasJune 23, 2026
From what I've seen in the RFOXiA docs and some internal testing notes, that 50km figure is pretty much best-case elevated LOS - think hilltop to hilltop with a clear Fresnel zone, not flat terrain with any real obstruction. In practice with even light vegetation or moderate terrain undulation you're looking at a significant haircut on that number, so I'd plan your link budget conservatively and maybe prototype with a few test points at different elevations before committing to the architecture.
Richard LopezJune 23, 2026
Yeah Mary's spot on - that 50km is really a "perfect world" number and in my testing even a gentle ridgeline or treeline in the Fresnel zone can cut usable range by 30-40% easy. For a UAV link I'd honestly target your architecture around 20-25km as a realistic working budget and treat anything beyond that as a bonus if conditions cooperate. Have you looked at what altitude you'll be flying at? Even modest AGL can recover a lot of that margin.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →