[Feature Request] Hot-Start Support

[PaulZC]

As mentioned in issue #27, it would be useful to have an example and/or code support for hot start (when waking from sleep)

[UT2UH]

Any updates on the right approach to hot-start speeding up?

[PaulZC]

Hi @UT2UH ,
Sorry - no - not yet... Still on the back-burner for now. But we will get to this as a new product we are working on will need it.
Best wishes,
Paul

[JMyrng]

Hi @PaulZC,

any info's on that new product or the code support?

Seems like I'm searching for exactly that.
Regards,
myrng

Edit:
A little more info about my problem: The description of powerOff() says that the module is woken up when getLatitude() is called, but unfortunately this does not happen for me.

[PaulZC]

Hi @JMyrng ,

Sadly, no, no progress as yet. We've been working on a new family of boards which will benefit from hot-start support, but we haven't yet had time to add and test the new code.

Thank you for your patience - I'll give you an update as soon as I can.

Can you give me more information about your powerOff() issue? Which module are you using? What duration are you using? Which interfaces do you have connected? I'm assuming the module is going to sleep and you cannot then wake it up with getLatitude(). Is that true? Are you using setAutoPVT?

Best wishes,
Paul

[JMyrng]

We've been working on a new family of boards which will benefit from hot-start support

Are you allowed to tell me the module names? Maybe the MAX-M10S from uBlox? Is it possible to switch off the LDOs via enable pin on the new boards? That would be very useful for low-power applications.

Can you give me more information about your powerOff() issue?

model: M9N, controller: MKR1310, interface: I2C, duration: variable between 15 and 60 min
Yes, I used powerOff() in conjunction with setAutoPVTcallback(). After that I switched to powerOffwithInterrupt() but that gave me some errors with my I2C communication. If I find the time today, I'll try to simplify my problem and create a new issue.

At the moment, however, I am no longer looking for a software solution, but am switching off all power to the module. I have desoldered the battery and supply Vbackup directly with 3.3 V.

Best regards,
JMyrng

[PaulZC]

Hi @JMyrng ,

The first board will be based on ZOE-M8Q but, yes, an M10 will follow soon after. Low power operation has been designed in from the start, and the sleep current is very low. We will publish the exact figure when the new boards are launched, but I think you will be pleased!

It is probably not clear / obvious, but setAutoPVT will not work with powerOff... setAutoPVT instructs the module to automatically generate PVT messages, without polling. Once autoPVT is enabled, getLatitude() does not poll the PVT data and so there is no message generated which would cause the module to wake up... Please try calling (e.g.) getNavigationRate(). That will generate a poll request causing the module to wake.

Best wishes,
Paul

[JMyrng]

I'm really looking forward to the M10 module! Please consider breaking out the Vbackup and the enable pins.

Thanks for that clarification! Maybe that should be noted in the examples/ code? I can't test it at the moment because I've changed my code too much, but I'm sure it will work if I need it again (e.g. on the M10).

Best regards,
JMyrng

Edit:
last question: M10M or M10S?

[PaulZC]

Hi @UT2UH / @JMyrng ,

Please see the release notes for v2.1.0 - we've added full support for AssistNow Online, Offline and Autonomous to deliver very quick Time-To-First-Fixes. Please give the new examples a try - I think you will be very pleased. Please raise a new issue if you see any gremlins!

Enjoy!

Best wishes,
Paul