David, In the NTPv3 spec the leap bits are to be set on the day of the leap. This is compliant with the new NTPv4 spec; that spec is more liberal in order to support and prioritize leap warnings when multiple means are available. In cases where the radio delivers a timecode via serial port, some radios include provisions for leap warning; some do not. I don't know if an NMEA sentence has provisions for that. There are no provisions for leap warning in IRIG devices I have.
I don't know if the Meinberg GPS or EndRun CDMA receiver include provisions for leap warning. If so, it should appear in the NTP header on the day of the leap. Both receivers use an embedded Linux system which in principle has the same provisions as the public distribution.. Dave David J Taylor wrote: > David L. Mills wrote: > >> Guys, >> >> See http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html#leap for what >> actually is in the implementation. As visivle here, the Spectracom >> (GPS/WWVB) driver, ACTS telephone modem driver and WWV audio driver do >> correctly display leap information. The Meinberg GPS receiver, EndRun >> CDMA receiver and audio IRIG driver do not display leapsecond >> information. > > [] > >> Dave > > > Dave, > > Thanks for that summary. My own GPS system using the Garmin GPS18 LVC and > the official ntp code for FreeBSD also does /not/ show the leap second. > > Is this something fundamental to all GPS - in that they don't indicate > until nearer the end of the month? > > Thanks, > David > > _______________________________________________ > questions mailing list > [email protected] > https://lists.ntp.org/mailman/listinfo/questions _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
