@Patricia Williams good question, and the timing matters since you're about to commit hardware to a full build.
The MultiNav Pro+ is built around the STM32WB07, which runs ST's dual-core architecture — one core handles the application, the other runs the BLE stack in isolation. You get access to the full BLE 5.x feature set including connection intervals, PHY selection, and TX power control, so a star topology with a central coordinator is very much within what the hardware supports natively.
For your specific use case — one coordinator, ~12 peripheral nodes on fixed telemetry intervals — the main thing you'll want to dial in is the connection interval and supervision timeout per peripheral. BLE handles this fine in a multi-connection central role, though 12 simultaneous connections does push toward the upper end of what you'd want to stress-test before finalizing your timing budget. The AI Firmware Builder in the Dev Hub is actually worth throwing your topology at — describe the coordinator/node scheme and it'll generate a working starting point you can pull apart, which is faster than building from ST's BLE middleware from scratch.
If you want to get into it more specifically — fixed interval, guaranteed delivery, any latency requirements — post the details and we can work through whether there are any stack-level constraints worth knowing before you order.
