MultiNav Pro+ BLE - does it handle point-to-point without a phone in the loop?

Linda Lopez · 2026-06-23T21:05:19.000Z

Been working on a remote sensor deployment where I need two nodes talking directly to each other - no phone, no tablet, no gateway in the middle. Just module A sending data to module B over BLE. I'm assuming the MultiNav Pro+ BLE can operate in a pure peripheral/central setup where one module acts as the central and polls the other, but I haven't found anything in the docs that explicitly confirms this works without a host MCU managing the connection on both ends. Can it run autonomously or does it need something driving it on each side?

Replies

William Thomas•June 23, 2026

Yeah it can do peer-to-peer without a phone in the loop - you just need to configure one module as central and the other as peripheral via the AT command set before deployment, and from there it handles the connection autonomously. The host MCU requirement depends on your firmware version tbh, so worth double-checking which build you're on since there were some changes around v2.3 that made the auto-reconnect behavior a lot more reliable for exactly this kind of headless setup.

Adam•June 23, 2026

@Linda Lopez yeah this is a solid use case for the MultiNav Pro+ and it does work in a headless peer-to-peer setup — the module can handle the connection management autonomously once it's configured, so you don't need an active host MCU babysitting the link on either end. The AT command config to set central/peripheral roles is the right starting point, and once that's saved to flash it persists across power cycles which matters a lot for remote deployments.

The one thing I'd flag is that your sensor data flow architecture matters here — if module B is just receiving and logging, that's straightforward, but if you need it to do anything meaningful with the data it's still going to need something on that end to process it, even if it's just a small microcontroller. The BLE module itself is handling the RF link autonomously, not the application logic on top of it.

I'd also recommend jumping into the Dev Hub and checking the AI Firmware Builder if you haven't already — describe your exact deployment topology (sensor node, data sink, polling interval, whatever) and it'll generate firmware that handles the connection setup and data flow cleanly, which is a lot faster than piecing it together from the AT command docs alone.

Richard Jones•June 23, 2026

William's right on the AT command approach - just to add, once you've got the central configured with the target peripheral's MAC address it'll auto-initiate on power-up without any host MCU involvement, so you can genuinely run it headless on both ends. I've done almost exactly this for a sensor node setup and it works pretty solidly as long as you're not pushing the range too hard.

Sarah Hernandez•June 23, 2026

One thing worth adding from my own deployments - make sure you lock in the peripheral's MAC address on the central *before* you seal up the enclosures, because if you're using random address mode it'll rotate and your central will lose track of it after a power cycle. Static public address mode saved me a headache on exactly this kind of remote setup.

Elizabeth Martinez•June 23, 2026

Sarah's point about the MAC address is super important and easy to overlook - I got burned by that exact thing on my first outdoor deployment and spent way too long debugging what I thought was a range issue. Also worth noting that if you're on v2.4+ there's a `AT+AUTOCONN` command that persists across power cycles so you don't have to re-initiate the pairing sequence every time the central reboots.

Charles Jackson•June 23, 2026

Solid thread - one more thing to watch out for is connection interval tuning, if your sensor data is low-frequency you can push the interval up pretty aggressively to save power and it won't affect the headless behavior at all. Just don't go too conservative on the supervision timeout or you'll get phantom disconnects when the central's doing nothing for a while.

Karen Lopez•June 23, 2026

All solid advice here - just want to second Charles on the supervision timeout thing because I definitely had phantom disconnects haunting me until I bumped it up, way longer than I thought would be necessary. If you're running low duty cycle sensor polling, something like 6-10x your connection interval as the supervision timeout is a decent starting point to dial from.

Charles Smith•June 23, 2026

Yeah the MultiNav Pro+ BLE handles this fine in headless mode - both ends can run autonomously once the connection's established, no host MCU needed on either side. Stack the `AT+AUTOCONN` tip from Elizabeth with static addressing like Sarah said and you're basically set-and-forget. Only gotcha I'd add on top of what's already been said is make sure your peripheral's advertising interval isn't too long or the central will take forever to reconnect after a power cycle.

Karen Miller•June 23, 2026

Good callout Charles - on the advertising interval thing, I've found somewhere around 100-500ms hits a sweet spot for reconnect speed without torching your power budget on the peripheral side. If you're really power-constrained you can get away with longer but just know you'll feel it in the reconnect latency after a cold boot.