Add Text Here...

Carl F Otto - Consulting: Creative Product Development and Inventor.

Certified to perform OSHA mock inspections, with innovative problem solutions.

Briefing:

Google is trying to solve the old problem users of NTP have with their software not handling leap seconds. These problems are within the NTP user’s software code on the various operating systems and applications. As one programmer commented, “Perhaps I am cynical, but I don't know why anybody would want to use Google's NTP servers, or any other commercial entity's resources, when there are NIST alternatives.”[1]

Google’s smear just spreads the second change over a 20 hour period by making seconds longer. I believe that would create 20 hours of GPS corrections to make up for the accumulative 88 feet a second out of lane if traveling at 60 MPH for the one second change, for things like Autonomous Vehicles. That may increase the number of users of PTP because it doesn’t have leaps.

However, after the January Precise Time and Time Interval (PTTI) meeting, maybe we will know if UTC will be frozen so leap seconds go away. They actually already have TAI and GPS as just counts of seconds. Perhaps they could just wean people off UTC if they knew they can get the TAI to UTC difference or TAI to world rotation. I suggested to my NASA managers that it was time to start using a star date system and many agreed but it never went anywhere.

In April of 2019 GPS 1024 weeks will roll over to 0 week. This is a Y2K type of problem. I have been testing various manufactureres using a GPS simulator and verified that Masterclock's products will not suffer any problems with this transision. May I strongly suggest you verify any GPS products you are using? Other's may advertize all kinds of specifications, but week 1024 roll to week 0 is not yet part of any speciffication that I have seen.

[1] https://www.reddit.com/r/google/comments/15orcx/has_anyone_tried_using_googles_ntp_servers/

ottocf@earthlink.net

Your resource for innovation

consuting@CarlFOtto.com