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

[Andrew Yong]

Here’s the CGPS output for your guru meditation:

┌───────────────────────────────────────────┐┌─────────────────────────────────┐

│    Time:       2013-10-03T04:09:33.000Z   ││PRN:   Elev:  Azim:  SNR:  Used: │

│    Latitude:     1.[XXXX] N               ││   8    70    225    00      Y   │

│    Longitude:  103.[XXXX] E               ││   9    63    228    17      Y   │

│    Altitude:   -4.1 m                     ││   4    51    254    23      Y   │

│    Speed:      0.1 kph                    ││ 129    48    091    40      Y   │

│    Heading:    17.8 deg (true)            ││ 193    46    051    26      Y   │

│    Climb:      0.0 m/min                  ││   7    45    173    30      Y   │

│    Status:     3D FIX (19 secs)           ││  28    42    010    28      Y   │

│    Longitude Err:   +/- 3 m               ││  20    34    072    36      Y   │

│    Latitude Err:    +/- 1 m               ││  10    28    192    28      Y   │

│    Altitude Err:    +/- 7 m               ││  17    23    333    00      Y   │

│    Course Err:      n/a                   ││   2    19    232    23      Y   │

│    Speed Err:       +/- 22 kph            ││                                 │

│    Time offset:     0.570                 ││                                 │

│    Grid Square:     OJ11wh                ││                                 │

└───────────────────────────────────────────┘└─────────────────────────────────┘

Thanks for your input!

Andrew

On Thu, Oct 3, 2013 at 12:07 PM, Andrew Yong <address@hidden> wrote:

Hello Gary,

> On 3 Oct, 2013, at 5:24 am, "Gary E. Miller" <address@hidden> wrote:
>
> 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.

Yep, it has a great lock with 14 satellites detected (3D DGPS fix with SBAS satellites).

Have a clear view of the sky with an external antenna.

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