[time-nuts] TymServe 2100 1995 Issue - A Kludgy Fix

Brian Inglis Brian.Inglis at SystematicSw.ab.ca
Tue May 5 20:07:41 EDT 2015


On 2015-05-05 11:47, Hal Murray wrote:
>
> cfharris at erols.com said:
>> Surely the receiver is still producing correct frames that identify the
>> future leapsecond, and those frames could be read, and used to set a little
>> routine that wakes up at the appropriate second, and adjusts the overall
>> offset?
>
> Is there any leap-warning info in NMEA mode?  I don't remember seeing
> anything like that when scanning the documentation and the NMEA driver in
> ntpd doesn't have any code like that.

GPS provides only the current UTC offset from GPS time, which could be made
available via a custom vendor message, or derived from the difference between
messages which provide UTC and messages (e.g. $GPZDG) which provide GPS time.

Stratum 1 NTP servers need to be provided with a copy of the NIST leap second
file and will propagate the warning to higher (numeric) stratum clients.

-- 
Take care. Thanks, Brian Inglis


More information about the time-nuts mailing list