MultiNav Pro+ Power Kit - programming workflow with the super-cap system?

Jessica Bradford•June 13, 2026

Hey everyone, been setting up my MultiNav Pro+ stack for a remote asset tracking build and I'm running into something a bit confusing with the Power/Program Kit. Specifically around the programming workflow when the super-cap system is involved. Like, when I flash firmware through the kit, is the super-cap actively supplying the module during the flash cycle, or does the programmer side take over and bypass it? I'm asking because I had one flash session where the module seemed to reset mid-write and I'm wondering if a voltage dip from the cap caused it or if it's just a timing thing on my end.

💬 3 replies👍 0 likes👁 0 views

Replies

Adam•June 13, 2026

@Jessica Bradford good question and honestly one that comes up more than you'd think with supercap-based systems.

The supercap is actively supplying the module during the flash cycle — the STLink side handles the programming interface but it's not a dedicated power rail that bypasses the cap. So if your cap was partially discharged when you started that session, a voltage dip mid-write is a very real possibility, especially since flash operations tend to pull a bit more current than idle. The classic sign of this is exactly what you described — a mid-write reset rather than a clean fail at the start.

Before your next flash session, make sure the cap is at full charge first (the 5-minute charge gets you there), and if you can, try to avoid flashing immediately after a long runtime where the cap's been depleted. That should eliminate the voltage-dip scenario as the culprit — if you still get mid-write resets after that, then it's more likely a timing or connection issue on the STLink side worth digging into separately.

Jonathan Cook•June 13, 2026

From what I've seen with that kit, the super-cap doesn't get bypassed during flashing - it's still in the loop, which can cause exactly the reset you're describing if it hasn't fully charged before you kick off the write cycle. Try adding a few seconds of dwell time after power-up before triggering the flash, that fixed it for me on a similar build. If you're scripting the workflow there's usually a ready signal you can poll to confirm the cap is topped off before proceeding.

Joseph Mason•June 13, 2026

Jonathan's right on the dwell time thing - I'd also double check that your supply rail can actually charge the cap fast enough, because if you're running off a current-limited USB port or a weak bench supply it can take way longer than you'd expect to hit ready state. I burnt a few sessions figuring that one out on mine.