So I flashed this frimware and restarted tests using my Gps provided time.
I guess there is more precise clock than a Gps available to me.
So apparently, if I do E.setPrescaler(32000) then it will drift (same value as usual), while with E.setRTCPrescaler(29536), it is only once (a time sync I think) and not later.
Longer tests are required...
Anyway, nice way to correct potential time shifts as it is now possible to measure the coefficient of shift and apply it automatically.
Just to ask more, E.getRTCPrescaler() would be usefull too. :)
Thank you.
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.
Ok,
So I flashed this frimware and restarted tests using my Gps provided time.
I guess there is more precise clock than a Gps available to me.
So apparently, if I do E.setPrescaler(32000) then it will drift (same value as usual), while with E.setRTCPrescaler(29536), it is only once (a time sync I think) and not later.
Longer tests are required...
Anyway, nice way to correct potential time shifts as it is now possible to measure the coefficient of shift and apply it automatically.
Just to ask more, E.getRTCPrescaler() would be usefull too. :)
Thank you.