- Joined
- Jan 27, 2013
- Messages
- 52,470
- Reaction score
- 30,342
- Location
- Sydney, Australia ~ Shenzhen, China
- Country
- Australia
- Dash Cam
- Too many ¯\_(ツ)_/¯
my feeling is that the trees are not the problem in this instance.
your hunch is correct, it's not signal quality that causes the spikes, it's to do with handover between satellites as new ones come into view and their actual position compared to the stored ephemeris and almanac data for that satellite as to where the GPS thought that satellite was going to be, it's quite complex and still needs further adjustment, we've been getting support from the GPS manufacturer to help fine tune the handling of this data to try and eliminate this from occurring, right now I don't have a time frame on how long it will take to sort this but it is something we are actively working on (amongst other stuff of course)
in broad terms a new satellite comes into view, its position is maybe a few hundred kilometers away from where the GPS thought it was going to be when it next came into view (which is quite normal) and the position is quickly updated, this is erroneously interpreted as very rapid location change (speed is just a calculation of time taken to cover a distance) so some of your location information is rapidly updated which in turn is interpreted as a rapid change in speed, generally only lasts for a second or two and then it's back to how it should be, wish it was a quick fix but it's relatively new ground on Novatek so just one of those things we need to work out, it has been improved already but we're not quite there yet with solving all the possible scenarios that can contribute to this happening, keep the reports coming when it does happen though as we need to look for any patterns to this occurring, anything that repeats under certain situations or is repeatable is ultimately always easier to analyze and work out how to remedy
Edit: fixed a couple of typos where I wrote GPS instead of satellite
Last edited: