RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ BLE - data throughput vs range tradeoff, real numbers?

Douglas YoungJuly 25, 2026
So the spec sheet lists 50KM range and 2Mbps speed, but I'm assuming those two numbers aren't happening at the same time, right? Like the 2Mbps is presumably at short range with 2M PHY, and once you push out to coded PHY for the long range stuff the throughput tanks. I'm building a remote telemetry node that needs to sit maybe 5-10km out and push sensor data back at a reasonable rate, and I'm trying to figure out what "reasonable" actually means in practice before I commit to the architecture.
💬 1 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

AdamJuly 25, 2026
@Douglas Young yeah you're reading that correctly — those two numbers are not simultaneous. The 2Mbps is 2M PHY mode, short range, and the 50km figure is drone-to-drone with coded PHY where both ends are elevated and you're eliminating ground reflections. At your 5-10km use case on the ground you're looking at the 5km ground-to-ground spec, which is already using the long-range PHY, so throughput will be meaningfully lower than 2Mbps.
 
For a telemetry node pushing sensor data though, coded PHY throughput is honestly fine in practice — you're not streaming video, you're pushing packets of environmental readings, GPS coordinates, maybe IMU data. That workload is well within what the link can handle at that range even with the coding overhead. The question is more about your packet rate and payload size than raw throughput.
 
What sensors are you planning to run on the node? If you're using the RFOXiA Sensors Module that's temperature, humidity, pressure, air quality, accel, gyro, mag — all seven — and the data rates for that kind of telemetry are nowhere near stressing the link even at extended range. Would help to know your update rate requirements before saying anything more definitive.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →