<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
For those wondering what a GPS certification letter for the rollover bug looks like, here’s Garmin’s. Note the phrase “for many years, Garmin has anticipated and prepared for this event...”:
<div><br>
</div>
<div>
<h1 id="faq-title" class="sp__faq__title sp__tab-content__heading" style="box-sizing: border-box; margin: 0px 0px 1rem; padding: 0px 0px 0.5rem; border-width: 0px 0px 1px; border-bottom-style: solid; border-bottom-color: rgb(204, 204, 204); vertical-align: baseline; font-weight: 400; font-stretch: inherit; line-height: 1.4;">
<font size="3"><span style="background-color: rgba(255, 255, 255, 0);">Garmin GPS Week Number Rollover Statement</span></font></h1>
<div class="sp__faq__content" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; vertical-align: baseline; font-stretch: inherit; line-height: 20px; overflow-x: auto;">
<p style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: 1.6;">
<strong style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: inherit; background-color: rgba(255, 255, 255, 0);">What is the GPS
Week Number Rollover (WNRO)?</strong></p>
<p style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: 1.6;">
<span style="background-color: rgba(255, 255, 255, 0);">The GPS system is world renowned for its ability to provide accurate and reliable positioning and timing information worldwide. The GPS satellites transmit to users the date and time accurate to nanoseconds.
However, back in 1980, when the GPS system first began to keep track of time, the date and time was represented by a counter that could only count forward to a maximum of 1024 weeks, or about 19.7 years. After 1024 weeks had elapsed, this counter “rolled over”
to zero, and GPS time started counting forward again. This first rollover occurred in August of 1999. The second rollover will occur on April 6, 2019.</span></p>
<p style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: 1.6;">
<strong style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: inherit; background-color: rgba(255, 255, 255, 0);">Is My Device Affected?</strong></p>
<p style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: 1.6;">
<span style="background-color: rgba(255, 255, 255, 0);">For many years, Garmin has anticipated and prepared for this event. Regardless, Garmin has been performing exhaustive testing of current and legacy devices to determine if they will be affected by the
GPS week number rollover. Our testing shows the vast majority of Garmin GPS devices will handle the WNRO without issues.</span></p>
<p style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: 1.6;">
<strong style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: inherit; background-color: rgba(255, 255, 255, 0);">What is the Effect
of a GPS Week Number Rollover Issue?</strong></p>
<p style="box-sizing: border-box; margin: 0px 0px 16px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: 1.6;">
<span style="background-color: rgba(255, 255, 255, 0);">For GPS devices that are affected, after the rollover occurs, an incorrect date and time will be displayed. This incorrect time will also be used to timestamp track logs, compute sunrise and sunset, and
other functions that rely upon the correct date and time. However, <strong style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; vertical-align: baseline; font-style: inherit; font-variant-caps: inherit; font-stretch: inherit; line-height: inherit;">the
positioning accuracy will not be affected</strong>. The device will continue to deliver the same positioning performance as before the rollover.</span></p>
</div>
<br>
<div dir="ltr"> -mel</div>
<div dir="ltr"><br>
On May 1, 2019, at 8:56 PM, Mel Beckman <<a href="mailto:mel@beckman.org">mel@beckman.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr"><span>Gary, Gary, Gary,</span><br>
<span></span><br>
<span>You don’t need a $30,000 GPS simulator to verify if a GPS product in your inventory has the rollover bug. You simply ask the supplier to certify that they don’t have the rollover bug. They use their _$100,000_ GPS simulator If needed, but usually it’s
done with a trivial code review. </span><br>
<span></span><br>
<span>If the supplier can’t provide such a certification, then they are no longer a supplier. This tends to persuade them to certify.
</span><br>
<span></span><br>
<span>If you as an air carrier (or any other critical GPS consumer) fail to ask for such a certification in time to field a replacement, that’s your fault.</span><br>
<span></span><br>
<span>You might not be aware, but zero US air carriers had any unplanned downtime from the GPS rollover. I can’t say the same thing for certain Asian air carriers :)</span><br>
<span></span><br>
<span>-mel via cell</span><br>
<span></span><br>
<blockquote type="cite"><span>On May 1, 2019, at 8:39 PM, Gary E. Miller <<a href="mailto:gem@rellim.com">gem@rellim.com</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Yo Mel!</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>On Thu, 2 May 2019 03:30:03 +0000</span><br>
</blockquote>
<blockquote type="cite"><span>Mel Beckman <<a href="mailto:mel@beckman.org">mel@beckman.org</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>I’m also an FAA licensed A&P mechanic, and have worked for airlines</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>in fleet maintenance. Air carriers have extremely thorough systems</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>reviews, by law, through the Airworthiness Directive program, which</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>started identifying 2019 GPS rollover vulnerabilities in ... 2009!</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Nobody was surprised. If any GPS systems “went nuts”, it was through</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>the incompetence and negligence of their owners.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>How many GPS owners happen to have $30,000 GPS simulators to check</span><br>
</blockquote>
<blockquote type="cite"><span>their $300 GPS/NTP servers? Some of mine did, most did not.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Seems to me the negligence is in the GPS manufacturer that failed to</span><br>
</blockquote>
<blockquote type="cite"><span>notify their customers.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>To be fair, Avidyne and Telit did notify their customers, but not with</span><br>
</blockquote>
<blockquote type="cite"><span>a fix or enough lead time to swap out the units.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>RGDS</span><br>
</blockquote>
<blockquote type="cite"><span>GARY</span><br>
</blockquote>
<blockquote type="cite"><span>---------------------------------------------------------------------------</span><br>
</blockquote>
<blockquote type="cite"><span>Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703</span><br>
</blockquote>
<blockquote type="cite"><span> <a href="mailto:gem@rellim.com">gem@rellim.com</a> Tel:+1 541 382 8588</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span> Veritas liberabit vos. -- Quid est veritas?</span><br>
</blockquote>
<blockquote type="cite"><span> "If you can’t measure it, you can’t improve it." - Lord Kelvin</span><br>
</blockquote>
</div>
</blockquote>
</div>
</body>
</html>