RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ BLE - does the RF front-end need any external matching at 50km?

Mary MillerJune 23, 2026
Been digging into the MultiNav Pro+ BLE module and I'm trying to understand what's actually happening on the RF side to hit that 50km range figure. I get that there's a "powerful RF front-end" mentioned in the specs but I'm wondering if that means there's an integrated LNA and PA already matched internally, or if I need to do any external impedance matching / filtering on my PCB design to actually realize that range in practice. Coming from using standard nRF52 modules where you just slap a chip antenna on and call it a day, this feels like it might be a different beast.</TITLE>
 
I'm designing a custom carrier board and I want to get the antenna feedline right before I spin the PCB. Are there any layout guidelines or reference designs available? Specifically wondering about the trace impedance to the antenna port, whether there's a recommended external filter for 2.4GHz, and if the module already handles all of that internally so I don't have to think about it. Would love to know if anyone's actually done a custom board with this thing rather than just using the dev kit.
 
Also side question - at the full rated output power, does the module get warm enough that I need to think about thermal relief on the ground pours around it? Asking because one corner of my enclosure is going to be pretty tight and I don't want heat buildup messing with the sensors module sitting nearby. Any real world board layout experience with this combo would be super helpful.
💬 1 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

AdamJune 23, 2026
@Mary Miller good questions and it's clear you're thinking about this the right way rather than just winging the layout.
 
On the matching question — the RF front-end on the MultiNav Pro+ is designed to be self-contained, meaning the LNA and PA are already handled internally with the matching done on-module. You're not in nRF52 bare-die territory where you need to sweat an external matching network. That said, you still need to treat your feedline seriously. A 50-ohm microstrip from the module's antenna port to your connector or antenna feed point is non-negotiable — any impedance discontinuity there will hurt you, and at 50km you're already working with a link budget that doesn't have much headroom to throw away. Get your trace width calculated properly for your stackup, keep it short, and avoid vias in that run if you can.
 
For external filtering at 2.4GHz, I wouldn't add a SAW or bandpass filter unless you're operating in a genuinely hostile RF environment (like next to a WiFi access point on a drone). The module's own front-end selectivity should be adequate for typical deployments, and adding a filter you don't need just adds insertion loss right where you least want it.
 
On thermal — at full TX power you will notice some warmth on the module, but in my experience it's not in the range where you need to treat it like a power amp with a heatsink. That said, if your enclosure corner is tight and you're stacking the sensors module close, I'd keep at least a few mm of airspace and make sure your ground pours have good copper fill around it rather than isolating it — better to conduct heat away than trap it. The sensors module doing temperature measurements right next to a warm RF PA is the more practical concern there honestly, so if you can orient them with a bit of separation or even a small cutout in the PCB that's worth considering.
 
For reference designs — best move is to post your carrier board outline in the Dev Hub and tag Moamen directly, there may be layout notes that haven't made it into the public docs yet.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →