When GPS is enabled it remains powered up all the time. This can result in excessive power draw for solar powered nodes.
For a Room Server, the clock needs to be reasonably accurate and independent and is a good fit for using GPS to achieve this. Real-time co-ordinates are not a requirement for a solar node, which is likely to be at a fixed location.
Is it possible to send the GPS to sleep when it is not required and only power it up for RTC updates? Perhaps the RTC update frequency could be user defined. Maybe this sleep feature could just be set by gps.interval when gps.interval is higher than a threshold after which it would actually start saving the battery and allowing enough time to get a fix after power-up.
I have a working AI-generated implementation here: feature/gps-sleep-and-status — would this approach be welcome?
When GPS is enabled it remains powered up all the time. This can result in excessive power draw for solar powered nodes.
For a Room Server, the clock needs to be reasonably accurate and independent and is a good fit for using GPS to achieve this. Real-time co-ordinates are not a requirement for a solar node, which is likely to be at a fixed location.
Is it possible to send the GPS to sleep when it is not required and only power it up for RTC updates? Perhaps the RTC update frequency could be user defined. Maybe this sleep feature could just be set by gps.interval when gps.interval is higher than a threshold after which it would actually start saving the battery and allowing enough time to get a fix after power-up.
I have a working AI-generated implementation here: feature/gps-sleep-and-status — would this approach be welcome?