@Keith Benson yeah this is a good question and honestly the docs could be clearer on this — the STM32WB07 at the core of the MultiNav Pro+ supports up to 8 simultaneous BLE connections in central role, but in practice with a persistent multi-peripheral setup I'd treat 4-6 as your comfortable ceiling before you start seeing connection interval contention eating into your throughput and latency. The more connections you're maintaining, the more the scheduler has to timeslice across them, and at long range where you're already pushing sensitivity limits, any scheduler hiccup can show up as dropped packets or connection events being missed.
One thing worth thinking about in your architecture — if your remote nodes are mostly pushing sensor data on a schedule rather than doing bidirectional real-time stuff, you can tune the connection intervals aggressively per-peripheral to give the central more breathing room. The firmware repo on GitHub has the connection parameter configs exposed, so you can experiment with that without digging into the stack directly. Would also be worth noting whether all your nodes are at max range simultaneously or if some are closer — that affects how hard the RF frontend is working and indirectly your timing margins.
What's the data rate you're targeting per node? That'll help narrow down whether interval tuning alone gets you there or if you need to think about a tiered hub topology.
