It is not that simple that with less updates power goes equally down. Every update has an acquisition time and the longer the updates are apart, the longer the acquisition may take because things may have changed more drastically. It is a matter of 'continuous' tracking with reasonable frequency, with 'reasonable' meaning balancing out pros and cons of each aspect involved in delivering sufficient accurate fix(es).
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
It is not that simple that with less updates power goes equally down. Every update has an acquisition time and the longer the updates are apart, the longer the acquisition may take because things may have changed more drastically. It is a matter of 'continuous' tracking with reasonable frequency, with 'reasonable' meaning balancing out pros and cons of each aspect involved in delivering sufficient accurate fix(es).
Attached documents explain that there is/are optimum/s in relation to update interval length / frequency, accuracy and power. First reading with good explanations is in the attached document about design considering power consumption minimization for the M6 series of u-blox receivers. Second document includes field tests with the M7 and M8 series. And finally I link to the document - which you also may have found -about the M8130-KT as is in the BangleJS https://www.u-blox.com/sites/default/files/products/documents/u-blox8-M8_ReceiverDescrProtSpec_(UBX-13003221)_Public.pdf - same as you find under Hardware at https://www.espruino.com/Bangle.js+Technical
2 Attachments