[ntp:questions] UTC Time from NMEA receiver one second behind DCF?
hb7267 at gmx.de
Fri Aug 15 18:33:17 UTC 2008
> hal-usenet at ip-64-139-1-69.sjc.megapath.net (Hal Murray) writes:
>>>> It looks like a weekly pattern. It will be interesting to see what
>>>> happens during the next week.
>>>Yes, that fits my observations well, including the weekly pattern...so
>>>far. I suppose you don't know of any workaround for ntp purposes?
>>If it really is a weekly pattern, then it should be possible to
>>hack the NMEA driver to "fix" the problem. I doubt if anybody is
>>likely to do it.
> A much better fix is to throw away that receiver and get a non-broken one.
> for timing purposes a gps receiver that decides on its own to report the
> wrong time is not worth fixing. Your time is worth more than that.
Just in case anyone is interested: The bug is active again right now
Here is a sample ntpq -p
remote refid st t when poll reach delay offset
LOCAL(0) .LOCL. 10 l 53 64 3 0.000 0.000
GPS_NMEA(0) .GPS. 3 l 51 64 3 0.000 -987.23
ptbtime2.ptb.de .PTB. 1 u 51 64 3 70.359 21.022
Here are a couple of NMEA messages off my Navilock:
When talking about a workaround I was thinking about a combination of
statuses that are found in these messages that only occurs when the bug is
active. Trying to guess the times at which it will strike is clearly
Nevertheless the Garmin unit is on order.
BTW: I didn't know that ordering GPS units from the U.S. would be *that*
More information about the questions