Re: [gpsd-users] Support for PPS on 10Hz Devices

[Gary E. Miller]

Yo Andrew!

On Thu, 3 Oct 2013 02:59:37 +0800
Andrew Yong <address@hidden> wrote:

> I’ve left my gpsd running spitting out debug | grep ntpshm for a
> while; GPSD is accepting the PPS leading edge consistently every
> second, however I still get this after running GPSD for about an hour:
> 
> gpsd:RAW: NTPD ntpshm_put: Clock: 1380740261.000000 @
> 1380740261.113936, fudge: 0.000
> gpsd:RAW: PPS ntpshm_pps: no current GPS seconds: -1380740261113936
> gpsd:RAW: NTPD ntpshm_put: Clock: 1380740262.000000 @
> 1380740262.124404, fudge: 0.000
> gpsd:RAW: PPS ntpshm_pps: no current GPS seconds: -1380740262124404
> gpsd:RAW: NTPD ntpshm_put: Clock: 1380740263.000000 @
> 1380740263.172770, fudge: 0.000
> gpsd:RAW: PPS ntpshm_pps: no current GPS seconds: -1380740263172770
> gpsd:RAW: NTPD ntpshm_put: Clock: 1380740264.000000 @
> 1380740264.192086, fudge: 0.000
> 
> Any idea why this may be? NMEA is coming in at 1Hz.

Looks like your GPS does not have a lock.  PPS just tells you the top
of the second, not which second.  That must come from the NMEA.  Do
you have a good view of the sky and a 3D fix?  Hint: use cgps to see
your fix and time.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
        address@hidden  Tel:+1(541)382-8588

signature.asc
Description: PGP signature