@Sarah Moore yeah, you're thinking about this the right way — those two specs aren't typically achieved simultaneously on any BLE implementation, and the MultiNav Pro+ is no different. The 50km figure is the drone-to-drone line-of-sight number where both modules are airborne and ground reflections are eliminated, and that kind of extreme range is going to be at the most conservative PHY setting with the receiver sensitivity doing the heavy lifting. The 2Mbps is your peak throughput in favorable conditions, not your long-haul spec.
For a wildlife tracking deployment where your nodes are ground-based and spread out, you're probably looking at something closer to the 5km ground-to-ground range as a realistic ceiling, and if you're pushing toward the edge of that you'll want to lean on LE Coded PHY to maximize link budget — you'll give up throughput but for sensor telemetry that's almost never the bottleneck anyway. GNSS position plus a handful of environmental readings is tiny data, so 125kbps getting to you reliably beats 2Mbps dropping packets at distance every time.
My honest suggestion: design your protocol around LE Coded first, prove out your link at your furthest nodes, then dial up the PHY if you find you have headroom to spare. Much easier to relax constraints later than to redesign after you've already got nodes in the field.
