Re: GSV strings not being parsed?

[Ben Barker]

Ah fair point. 

The trailing ....... were part of the capture from tcpdump I think rather than part of the message - though I will check that. 

I'll also check if the version of the daemon is our problem 

Have a great evening! 

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

Yo Ben!

On Wed, 15 Feb 2023 19:04:33 +0000
Ben Barker <ben@bbarker.co.uk> wrote:

> 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:

gpsd has no trouble with the newer GSV message formats.  Just look in the
gpsd regressions and you can see many examples of various conforming
and non-conforming GSV that gpsd handles.

> 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................................

Uh, oh.  What are those trainling dots?  Those are not legal.

> But gpsd shows no GSV messages:

Right, because you are not getting any legal GSV messages.

> {"class":"VERSION","release":"3.19","rev":"3.19","proto_major":3,"proto_minor":14}

Uh, you realize that 3.19 is 3.5 years old?

Where did you get a gpsd that old?

We don't support stuff that old.

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