RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ GNSS first fix time - does 1 sec hold up from cold start?

Douglas YoungJune 12, 2026
So the spec sheet says "first fix in 1 second" and I've been trying to figure out if that's a hot start number or if they actually mean cold start too. I'm building a small asset tracker that gets powered down between uses, so basically every fix is going to be cold or at best warm, no persistent power to keep the almanac alive. In my testing I'm seeing something closer to 25-35 seconds on a true cold start out in the open which honestly isn't terrible, but it's pretty far from 1 sec so I want to make sure I'm not missing something in my config before I assume that's just how it is.</TITLE>
 
I'm currently not feeding it any assisted GNSS data, no AGPS, nothing external. Wondering if the 1 sec claim assumes you're pushing in ephemeris data from an external source or if there's some internal flash retention thing I'm not enabling. Is there a register or config flag that tells the module to save almanac to flash between power cycles? I dug through the datasheet for a bit and didn't find anything obvious but maybe I missed it.
 
Also curious what other people are getting on warm restarts, like if the module had power within the last few hours. That scenario actually does matter a lot for my use case if I can keep some state alive even briefly. Any pointers to example code or config that handles this properly would be great, I feel like I'm leaving a lot of fix speed on the table right now.
💬 1 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

AdamJune 12, 2026
@Douglas Young yeah your 25-35 second cold start is totally normal — that 1 second figure is a hot start number, meaning the module already has valid ephemeris, knows its approximate position, and is basically just reacquiring signals it already knows about. Cold start from scratch without any almanac or ephemeris data is going to be 30-60 seconds for most GNSS chips regardless of what the spec sheet headline says, so you're actually in good shape there.
 
The flash retention question is the right thing to dig into for your use case. Most GNSS chipsets support a backup mode where they write almanac and last-known position to non-volatile memory before shutdown, and then on next power-up they load that data and start a warm acquisition instead of cold. Whether that's exposed depends on the specific chip inside the module — if you can tell me which GNSS IC is on the MultiNav Pro+ I can point you at the right config registers, but typically you're looking for something like a "backup" or "standby" command you send before cutting power, plus a VBACKUP pin that some chips need held at a low voltage to retain SRAM even when main power is off.
 
For your asset tracker scenario, even a warm start should get you down to 5-15 seconds if the almanac is less than a few hours old, which is a meaningful improvement. If you're seeing power-up intervals measured in hours rather than days, that warm start path might be all you need without having to implement full AGPS.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →