NAVCEN issued an alert regarding receiver errors in handling the current pending leap second data like has occurred with the Skytraq receiver. Several brands/models were affected. I have not seen the original alert, but here is an article summarizing:
http://www.insidegnss.com/node/4398 Keith Keith On Mon, Feb 2, 2015 at 9:35 AM, Keith Loiselle <[email protected]> wrote: > We have received some additional information from Skytraq regarding the > leap second error: > > "The faulty version firmware indicates leap seconds (17) from now to June > 16th (two weeks before June 30th). During June 16th ~ June 30th, leap > second will recover to 16 and change properly to 17 on June 30th midnight. > For future leap seconds, if the leap second change is still broadcasted > ahead of time for more than 2 weeks, it'll still have this problem for > coming leap seconds." > > Keith > > > > Keith > > On Wed, Jan 28, 2015 at 9:27 AM, Tom Van Baak <[email protected]> wrote: > >> > I have verified the Skytraq claim on my stand alone NS-T. >> > Tue Jan 27 06:52:06 UTC 2015 $GPGGA,065206.000,4847.3506 >> >> Hi Mike, >> >> Please use more precise timestamps so your results can be believed. In >> general it's not adequate to use one second unix time stamps to identify a >> possible one second NMEA error. >> >> Instead try using something like dateu.c (www.leapsecond.com/tools/) to >> output microsecond timestamps. >> >> /tvb >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> > > _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
