Select to expand quote
decrepit said..
That was my point, about accuracy, I've no idea how often it checks the sat time. Once it's synced on initial start up it seems to just run as a watch, GPS signal or not.
Woops revise that, I've just turned it on after several days off and its about 1hr 30min fast. After it's synced it agrees to the second with this computer.
If I could remember just how long it's been off, we could work out how long it would take to be over a second fast, hmm probably not long at all maybe two days. So if it isn't checking the GPS signal regularly it gains 1.5hrs in 48, or 1hr in 32 or 112sec in an hour? That seems like a lot, am I doing this right?
The device-local "clock" in a GPS device, is usually implied to be the Crystal-oscillator (TCXO) or similar - this thing needs to be super accurate, or your GPS wouldn't be able to lock onto the GPS carrier.
In devices that are wrist-watches showing the local time, there will also be some electronics which attempts to "keep the local time" -> since they are rather cheap components, they aren't too accurate... so the local time tends to drift. [ You have one of these on your PC - if you have it disconnected from mains-power you tend to not notice this as they are often accurate for months - but I have seen some PC's drift 5 mins per hour. A modern PC will use "NTP" to resync to an atomic clock. ]
The GPS system sends down time-codes accurate to about 10 nanoseconds -> whenever you get a GPS-lock, the local time will get updated to the GPS time-codes Obviously a cheap GPS cannot do 10ns accuracy - we tend to see only a few decimal places of accuracy... but some GPS's devices are capable of using the time-codes to be quite accurate [ Indeed you can build yourself a stratum-1 atomic clock for about $20. ]