Re: GSV strings not being parsed?

[Ben Barker]

Actually I spoke too soon. I do wonder if it is something to do with having multiple types of GSV messages incoming. As it turns out we don't absolutely need GSV, but it's odd they aren't being processed: 

tcpdump shows the GSV messages coming in, but in gpsmon I only see the GGA and the RMC messages

tcpdump dst 255.255.255.255 and port 6125 -A

$GPGSV,3,3,12,23,45,075,46,26,16,167,28,27,89,031,51,30,11,328,42,0*61................................
$GLGSV,3,1,10,66,10,006,32,67,30,056,34,68,21,110,32,73,33,211,43,0*77................................
$GLGSV,3,2,10,74,51,275,33,75,20,334,41,82,16,068,35,83,58,047,32,0*7E................................
$GLGSV,3,3,10,84,48,272,32,92,27,317,,0*75............................................................
$GAGSV,2,1,08,02,40,303,44,10,65,064,47,11,84,223,43,12,38,062,39,0*74................................
$GAGSV,2,2,08,19,12,067,25,24,19,168,26,25,59,220,46,36,32,239,38,0*7A

But gpsd shows no GSV messages: 

telnet localhost 2947
Connected to localhost
{"class":"VERSION","release":"3.19","rev":"3.19","proto_major":3,"proto_minor":14}
?WATCH={"enable":true,"nmea":true}
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"udp://255.255.255.255:6125","driver":"NMEA0183","activated":"2023-02-15T19:02:59.151Z","flags":1}]}
{"class":"WATCH","enable":true,"json":false,"nmea":true,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}
$GPRMC,190300,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*17
$GPGGA,190300,5254.6985,N,00127.6425,W,1,12,0.5,52.9,M,47.5,M,,0000*60
$GPRMC,190301,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*16
$GPGGA,190301,5254.6985,N,00127.6425,W,1,12,0.5,52.9,M,47.5,M,,0000*61
$GPRMC,190302,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*15
$GPGGA,190302,5254.6985,N,00127.6425,W,1,12,0.5,52.9,M,47.5,M,,0000*62
$GPRMC,190303,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*14
$GPGGA,190303,5254.6985,N,00127.6425,W,1,12,0.5,52.9,M,47.5,M,,0000*63
$GPRMC,190304,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*13
$GPGGA,190304,5254.6985,N,00127.6425,W,1,12,0.5,52.9,M,47.5,M,,0000*64
$GPRMC,190305,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*12
$GPGGA,190305,5254.6985,N,00127.6425,W,1,12,0.5,52.9,M,47.5,M,,0000*65
$GPRMC,190306,A,5254.6985,N,00127.6425,W,0.01,305.32,150223,,,A,V*11

On Wed, Feb 15, 2023 at 6:52 PM Gary E. Miller <gem@rellim.com> wrote:

Yo Ben!

On Wed, 15 Feb 2023 09:29:17 +0000
Ben Barker <ben@bbarker.co.uk> wrote:

> ..and now it's fine after a system reboot. Not sure why, but not
> complaining!

I like easy ones.

>
> On Wed, Feb 15, 2023 at 9:15 AM Ben Barker <ben@bbarker.co.uk> wrote:
>
> > Hi,
> > I have a GPS receiver that outputs the following NMEA strings:
> >
> > GPRMC
> > GPGGA
> >
> > GPGSV < GPS
> > GAGSV < Galilleo
> > GLGSV <Glonass
> >
> > These messages are available on a UDP broadcast which GPSd has been
> > configured to listen to:
> >
> > udp://255.255.255.255:6125
> >
> > (82)
> > {"class":"VERSION","release":"3.19","rev":"3.19","proto_major":3,"proto_minor":14}
> > (155) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"udp://
> > 255.255.255.255:6125
> > ","driver":"NMEA0183","activated":"2023-02-15T09:08:58.181Z","flags":1}]}
> > (122)
> > {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timing":false,"split24":false,"pps":true}
> > (70)
> > $GPRMC,090859,A,5156.9587,N,00102.7157,E,0.01,244.25,150223,,,A,V*07
> > (72)
> > $GPGGA,090859,5156.9587,N,00102.7157,E,1,12,0.6,12.0,M,45.7,M,,0000*7C
> > (70)
> > $GPRMC,090900,A,5156.9586,N,00102.7157,E,0.00,244.25,150223,,,A,V*0A
> > (72)
> > $GPGGA,090900,5156.9586,N,00102.7157,E,1,12,0.6,12.0,M,45.7,M,,0000*70
> > (70)
> > $GPRMC,090901,A,5156.9586,N,00102.7158,E,0.00,244.25,150223,,,A,V*04
> > (72)
> > $GPGGA,090901,5156.9586,N,00102.7158,E,1,12,0.6,12.0,M,45.7,M,,0000*7E
> > (70)
> > $GPRMC,090902,A,5156.9586,N,00102.7158,E,0.01,244.25,150223,,,A,V*06
> > (72)
> > $GPGGA,090902,5156.9586,N,00102.7158,E,1,12,0.6,12.0,M,45.7,M,,0000*7D
> >
> >
> > However, it does not seem to be picking up on any of the GSV
> > strings. Is there an obvious reason for this...? Is it being thrown
> > by having the three types of GSV messages present?
> > 




RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin