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

Karen Thomas · 2026-06-23T19:49:01.000Z

Hey all, working on a custom PCB where I'm integrating the MultiNav Pro+ BLE module and I'm trying to figure out if the RF front-end already has its matching network sorted internally or if I need to add external components on my board. The datasheet mentions the "powerful RF front-end" but doesn't go into a ton of detail about what's already on the module vs what's expected from the host board side. I've been burned before by assuming a module was fully matched and then wondering why my range was garbage until I finally measured the return loss and realized I'd left a floating trace acting like a terrible stub.

Replies

William Martin•June 23, 2026

The MultiNav Pro+ has the matching network built into the module itself, so you don't need external matching components - just route a clean 50Ω trace to your antenna and you're good. That said, I'd still double-check the recommended PCB keepout zone in the hardware integration guide because a ground plane creeping under the antenna area will hurt your range more than anything else.

Adam•June 23, 2026

@Karen Thomas yeah the module handles the matching internally — you shouldn't need to add anything on your board side. The RF front-end with the external amplifiers is already tuned as part of the module design, so your job is really just giving it a clean 50Ω feed and respecting the antenna keepout area on your PCB.

That floating stub story is exactly the kind of thing that'll cost you 10dB without any obvious reason why, so I'd definitely take the time to measure return loss once your board is assembled rather than assuming it's fine. If you haven't already, reach out through the Dev Hub resources section — there's hardware integration guidance there and if something isn't covered, Moamen has been pretty responsive about RF-specific layout questions directly.

Linda Williams•June 23, 2026

William's got it right - the matching is handled onboard, but I'd add that if you're using a PCB trace antenna config rather than an external one, pay close attention to the clearance recommendations because I've seen people nail the keepout and still trash their link budget by running a noisy power trace too close to the RF section. Learned that one the hard way on a v1 board lol.

Michael Miller•June 23, 2026

Both Linda and William covered the main stuff well - one thing I'd add is to also watch your decoupling caps on the power supply pins near the RF section, poor filtering there can sneakily degrade your sensitivity even when everything else looks clean on the layout. Had a board come back with mediocre range and it turned out to be a bulk cap placed way too far from the module's VCC pin.

John Thomas•June 23, 2026

All solid points above - I'll just throw in that if you're going through any kind of regulatory testing later, keep notes on your exact layout because swapping to a different antenna or tweaking that keepout even slightly can kick you back to square one on the RF compliance side. Burned a solid two weeks on that once.

Richard Smith•June 23, 2026

Thread's pretty much nailed it at this point, but one thing worth adding - if you're on a tight schedule, def get your stack-up and trace width confirmed with your PCB fab early so your 50Ω impedance calc actually matches what they'll manufacture, because I've seen "50Ω" traces end up nowhere close after fab tolerances are applied and then you're chasing ghosts.

Linda Moore•June 23, 2026

Piggybacking on Richard's point - def run your impedance calcs through your fab's own calculator if they have one, not just a generic online tool, because their specific dielectric constant and layer thickness will give you a way more accurate result. Got bit by this exact thing and ended up with traces that were like 47Ω on paper but closer to 44 after fab, which isn't catastrophic but still not ideal when you're already tight on link budget.

Robert Miller•June 23, 2026

One more thing to throw in on top of all the solid layout advice above - if you haven't already, grab a VNA and actually verify your antenna port impedance once the boards come back, even ballpark measurements will tell you real quick if your matching is in the right neighborhood before you spend time chasing range issues in firmware. Saved me a ton of headscratching on a similar integration last year.

Sarah Garcia•June 23, 2026

To add to what Robert said about VNA measurements - if you don't have access to one, even getting a nanoVNA for like $50-60 will get you in the ballpark and is honestly worth having in your toolkit for any BLE work going forward. On the original question though, the MultiNav Pro+ does have its matching network onboard so you shouldn't need external matching components, just make sure you're feeding it a clean 50Ω trace and respecting the keepout around the antenna area like John mentioned.

Charles Hernandez•June 23, 2026

Yeah the nanoVNA rec from Sarah is solid, I picked one up about a year ago and it's honestly one of the best $50 I've spent on test gear - way more useful than I expected for quick sanity checks on antenna matching before committing to a full test session. Just cal it properly before you measure or the results are pretty meaningless.

Patricia Jones•June 23, 2026

Seconding the nanoVNA rec hard - I keep one on my bench permanently now and it's paid for itself many times over. One thing I'll add is when you're routing that 50Ω trace to the module, keep it as short as reasonably possible and avoid routing it near anything switchy like your DCDC converter if you have one on board, that interference will mess with your readings and your actual RF perf.

Elizabeth Lopez•June 23, 2026

All solid advice above - just want to +1 the keepout thing Patricia mentioned, I got lazy about that on a board last year and ended up with a pour creeping under the antenna area that tanked my RSSI by like 8dB before I figured out what was going on. The module datasheet should have a recommended keepout zone, just follow it exactly and don't let your ground plane or any copper sneak under there no matter how tempting it is for other routing.

Karen Moore•June 23, 2026

Late to this thread but just wanted to confirm from my own experience with the Pro+ that you really don't need external matching - it's all handled onboard and I've had clean results straight off the module with just a properly impedance-controlled trace. The keepout and 50Ω routing advice here is the real gotcha stuff, get those wrong and you'll be chasing ghosts for days. Elizabeth's 8dB story is not an exaggeration, I've seen similar ugliness from sloppy copper pours under antenna areas.