Re: [gpsd-users] Leap second has arrived but GPS not updated?

[Tomalak Geret'kal]

On 01/07/2012 17:28, Alexander Carver wrote:
> On 6/30/2012 23:48, Alexander Carver wrote:
>
> > So, almost seven hours after the fact, the offset finally 
> > updates.
> >
> > But here's the weird thing:  The time reported by gpsd to 
> > ntpd didn't
> > change after the update.  I have the offset fudged in the 
> > config for
> > ntpd (the extra second).  When the real offset appeared 
> > on the receiver,
> > my reported offset should have been wrong but it's not, 
> > it's showing
> > it's only different by about 30 milliseconds instead of a 
> > full second
> > again.
> >
> > I did restart gpsd but that didn't change anything, it's 
> > still reporting
> > a "wrong" time to ntpd.
> >
> > I may just have to restart everything.
>
> Now I'm even more confused.  As of about an hour ago, the 
> GPS UTC offset has gone *backward* from 16 to 15 again.  
> I'm not sure what happened or why.  At about 0700 UTC it 
> started showing an offset of 16 seconds. Somewhere after 
> 1300 it stepped backwards.  I still have satellites in 
> view, six are locked for a fix plus the one SBAS is good.
Sounds to me like your receiver has a "default" of 15 in its 
NV RAM, plus a bug preventing it from properly extracting 
the UTC Correction parameter from almanac.

Tom