My uBlox NEO-6M device always corrects its timestamp after boot. After a warm start, for example, it is approximately 3 seconds ahead of UTC but will start issuing the correct timestamp in about 1-7 minutes. I'd like to get a 'confidence' value that indicates whether the timestamp is accurate or will be corrected sometime in the future (there is often more than one correction).
I've looked at the values 'fix.ept' (estimated time uncertainty) and 'dop.tdop' (time dilution of precision), but these remain stable before and after a correction at 0.005 and ~1.26 respectively, and I'm receiving PPS signals minutes before the timestamp is corrected.
I'm not really looking for a Chrony/NTPD solution--I don't want to slew the system clock or resort to statistical techniques to determine precision. I'd like to know if there is any way to determine if the GPS timestamp is accurate as quickly as possible in an isolated, non-networked environment. Possible, or a pipe dream?
Thanks,
Simon.