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

[Phil Stracchino]

On 07/27/16 15:12, Gary E. Miller wrote:
> Yo Phil!

Thanks for responding.  :)


> I think there is a misunderstanding here.  The ONLY difference between
> a GR-601 and a GR-601W is the addition of ONE patch wire.  Sadly
> the OEM vendor did not even change the model number on the label.

I wasn't aware the manufacturer did not update the label.  I hope I
haven't jumped to false conclusions.  The compatibility list leads me to
believe that the 601W should identify as a native USB device, rather
than only as a USB-serial interface.

What does lsusb say about your GR-601W?  Mine reports this:

Bus 005 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port

> I have several left, but I suspect that you already have one.
> 
> Have you tried this:
>       # killall -9 gpsd
>       # gpsmon /dev/ttyUSB0
> 
> Then verified that you have a 3D fix, and PPS is shown in the lower
> window?

Oh, I get a great solid 3D fix, typically from 8 satellites but
sometimes as low as 6 or as high as 10, but I'm getting no PPS signal
that I can see and recognize.  gpsmon reports the following stanzas:


(76)
$GPGGA,200248.00,4333.62576,N,07121.30481,W,1,08,1.03,313.3,M,-32.4,M,,*6E\x0d\x0a
(58) $GPGSA,A,3,06,12,17,02,28,19,03,24,,,,,1.67,1.03,1.32*06\x0d\x0a
(68)
$GPGSV,4,1,13,02,33,256,28,03,27,047,28,06,73,283,38,09,09,115,*7D\x0d\x0a
(68)
$GPGSV,4,2,13,12,26,316,30,17,62,092,36,19,79,022,19,22,07,039,*72\x0d\x0a
(66)
$GPGSV,4,3,13,23,12,089,,24,08,270,24,28,20,167,28,46,32,215,*75\x0d\x0a
(31) $GPGSV,4,4,13,51,28,226,27*46\x0d\x0a
(52) $GPGLL,4333.62576,N,07121.30481,W,200248.00,A,A*7B\x0d\x0a
(68)
$GPRMC,200249.00,A,4333.62578,N,07121.30487,W,0.086,,270716,,,A*60\x0d\x0a
(35) $GPVTG,,T,,M,0.086,N,0.159,K,A*20\x0d\x0a


Right now, ntpd -q is reporting the following:

minbar:root:~:35 # ntpq -p
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
 us.pool.ntp.org .POOL.          16 p    -   64    0    0.000    0.000
0.000
 SHM(0)          .GPS.            0 l    -   64    0    0.000    0.000
0.000
 SHM(1)          .PPS.            0 l    -   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


This is actually a regression from my last attempt, about a week ago
now; at that time the WHEN status on SHM(0) (GPS) was updating, but
SHM(1) (PPS) was not.  Now *neither* is updating.  In fact, NONE of the
WHEN fields are updating today.  Am I possibly misunderstanding something?


The really annoying thing about this is that some years ago, I had it
working once using a MS DeLorme GPS receiver (Pharos chipset), but I
could never reboot the machine cleanly because there was something wonky
somewhere (that I never managed to track down) which had the effect that
the PL2303 driver could never be unloaded once loaded.  Which meant a
fsck and RAID1 recovery on every boot.  *That* got old really fast, as
I'm sure you can imagine.



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

signature.asc
Description: OpenPGP digital signature