RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ BLE - does the RF front-end need any external matching components?

James RodriguezJune 23, 2026
Hey all, working on a pretty compact PCB design and trying to figure out how much space I actually need to budget around the MultiNav Pro+ BLE module. My question is around the RF front-end - does it come pre-matched from the factory, or do I need to add external matching network components (like Pi network caps/inductors) between the module and my antenna? I've been burned before with modules that technically "work" out of the box but drop 3-4dB because the matching wasn't tuned for anything other than their reference design.
💬 1 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

AdamJune 23, 2026
@James Rodriguez great question, and yeah that 3-4dB hit from lazy matching is exactly the kind of thing that kills range on paper-spec modules.
 
The MultiNav Pro+ ships with the RF front-end pre-matched and optimized — that's actually a big part of how it hits the range figures it does, because Moamen tuned the matching for real-world deployment, not just the reference board. The external LNA and PA are already integrated and matched on the module itself, so you don't need to budget space for a Pi network between the module and your antenna feed point.
 
That said, you'll still want to keep your antenna feed line as short and clean as possible and make sure your PCB antenna or connector launch is reasonably well-controlled impedance-wise — the module can't compensate for a bad 50-ohm trace on your side. If you're using an external antenna via U.FL or SMA, keep that launch clean and you should be fine without any additional matching components.
 
If you want to be totally sure for your specific layout, worth posting your antenna approach here — someone in the community or Moamen himself might have seen a similar layout before.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →