gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] In which GR-601 does not equal GR-601W


From: Phil Stracchino
Subject: Re: [gpsd-users] In which GR-601 does not equal GR-601W
Date: Wed, 27 Jul 2016 20:13:31 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

On 07/27/16 18:29, Gary E. Miller wrote:
> Once you get a somewhat current gpsd installed, your next step is to
> run gpsd and then check the SHM output:
> 
>     # gpsd -n /dev/ttyUSB0
>     # ntpshmmon
>     ntpshmmon version 1
>     #      Name Seen@                Clock                Real                
>  L Prec
>     sample NTP0 1469658476.791020864 1469658476.541874837 
> 1469658476.703999996 0  -1
>     sample NTP1 1469658476.791027079 1469658476.000102462 
> 1469658476.000000000 0 -20
>     sample NTP1 1469658477.000156795 1469658477.000124713 
> 1469658477.000000000 0 -20
>     sample NTP0 1469658477.543001744 1469658477.542868714 
> 1469658477.703999996 0  -1
>     sample NTP1 1469658478.001211671 1469658478.000129902 
> 1469658478.000000000 0 -20
>     sample NTP0 1469658478.544318197 1469658478.544093779 
> 1469658478.703999996 0  -1
>     sample NTP1 1469658479.001060953 1469658479.000117875 
> 1469658479.000000000 0 -20
> 

And finally I have SHM PPS data:

minbar:root:~:76 # ntpshmmon
ntpshmmon version 1
#      Name   Seen@                Clock                Real
  L Prec
sample NTP0 1469663570.449378719 1469663570.448817722
1469663570.000000000 0  -1
sample NTP0 1469663571.134746057 1469663571.133854364
1469663571.000000000 0  -1
sample NTP0 1469663572.134474051 1469663572.133876878
1469663572.000000000 0  -1
sample NTP0 1469663573.134077437 1469663573.133910379
1469663573.000000000 0  -1
sample NTP1 1469663574.014864114 1469663574.013901161
1469663574.000000000 0 -10
sample NTP0 1469663574.134784012 1469663574.133944023
1469663574.000000000 0  -1
sample NTP1 1469663575.014214382 1469663575.013936154
1469663575.000000000 0 -10
sample NTP0 1469663575.136216335 1469663575.135984450
1469663575.000000000 0  -1
sample NTP1 1469663576.014538038 1469663576.013971810
1469663576.000000000 0 -10
sample NTP0 1469663576.134444429 1469663576.134013597
1469663576.000000000 0  -1
sample NTP1 1469663577.014051932 1469663577.014006394
1469663577.000000000 0 -10


And FINALLY I have PPS reaching ntpd.  :)

minbar:root:~:74 # ntpq -p
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
+SHM(0)          .GPS.            0 l   29   64    3    0.000  -125.02
9.436
*SHM(1)          .PPS.            0 l   28   64    3    0.000   -3.257
10.796
 us.pool.ntp.org .POOL.          16 p    -   64    0    0.000    0.000
0.000
 10.24.32.255    .BCST.          16 B    -   64    0    0.000    0.000
0.000
 10.24.33.255    .BCST.          16 B    -   64    0    0.000    0.000
0.000
 10.24.34.255    .BCST.          16 B    -   64    0    0.000    0.000
0.000


I should only ever have to apply a time1 fudge on NTP0 (GPS), right,
never on NTP1 (PPS)?



-- 
  Phil Stracchino
  Babylon Communications
  address@hidden
  address@hidden
  Landline: 603.293.8485

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]