Hi Gordon,
I've designed and programmed my personal GPS devices based on M8N and M9N.
Data from a Ublox chip normally is very accurate, but I use the binary protocol and not NMEA.
Attached are 2 files, 1 is data from the Bangle, the other is from my own logger at 5hz.
I've highlighted the suspicious part in the Bangle screenshot.
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.
Hi Gordon,
I've designed and programmed my personal GPS devices based on M8N and M9N.
Data from a Ublox chip normally is very accurate, but I use the binary protocol and not NMEA.
Attached are 2 files, 1 is data from the Bangle, the other is from my own logger at 5hz.
I've highlighted the suspicious part in the Bangle screenshot.
When I look at the track points
There is 19m between them, 19m/s = 68,4km/h
For my personal devices I use double for lat/lon data, it almost looks like the current grid is not dense enough.
I used km/h NMEA data from the Ublox on another Bangle and it is spot on! (other wrist)
So I really suspect the lat/lon data from the recorded file.
The Ublox spec has 8 digits, the recorded file 6 (page 141)
https://www.u-blox.com/en/docs/UBX-13003221
Could it be the difference between 32 and 64 bit?
2 Attachments