Mark Sims wrote: >> When is some organization going to explain what happened in February for >> almost two hours starting at 00:16 GMT? That subject has gone silent. Rob, >> NC0B > I heard back from NAVCEN. They said it was a Trimble issue and that Trimble > would contact me (they didn't). But that does not jive with reports of > failures in Motorola, Navman, etc receivers.
I think we need to distinguish here. The January 26 issue was due to faulty data sent by the satellites, which caused GPS receivers to apply a wrong UTC correction which caused the UTC time to be off by 13.7 us. As explained by Luc Gaudin from http://naelcom.com (who obviously sell Trimble GPS receivers) the February 13 issue was indeed just a Trimble firmware problem. See: https://www.febo.com/pipermail/time-nuts/2016-February/096042.html https://www.febo.com/pipermail/time-nuts/2016-February/096050.html Martin _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.