Re: Ubuntu 18.04.3 build from source testing

[Gary E. Miller]

Yo Steve!

On Thu, 19 Dec 2019 15:44:27 -0600 (CST)
Steve Bourland <address@hidden> wrote:

>    Looking through xgps.py and then at gpspipe -r and I only see:
> 
> $GPZDA,213916.00,19,12,2019,00,00*69
> $GPGGA,213916.00,2926.7339,N,09836.3953,W,1,07,1.05,193.20,M,-26.443,M,,*59
> $GPRMC,213916.00,A,2926.7339,N,09836.3953,W,0.0040,69.672,191219,4.1,E*43
> $GPGSA,A,3,3,7,14,16,26,27,31,,,,,,1.6,1.1,1.3*32
> $GPGBS,213916.00,11.178,11.105,7.504,,,,*43

xgps does not use the psuedonmea, so unrelated to your issue.

You did report SKY sentences, which is what xgps uses.

> for sentences, no GPGSV sentences, so I think the reason I am getting
> the "object has no attribute 'svid'" error is because no, I don't
> have any satellites in view data in the binary coming from the
> Garmin.

If there are no sats in view, then there are no sat records to not have svid.
So no problem.

> Not sure why it isn't coming/being parsed (haven't looked at
> the binary itself to see if the data is actually being sent), but
> tempted to try again to push this device back to NMEA.  Thinking
> things are "working as they should," just not handling the "error" as
> "cleanly" as it could. Thanks,

Did you test with today's git head?  I think this is fixed.  The garmin
driver was never sending svid, and xgps was always expecting it.

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

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

pgpuHBnWWx9cL.pgp
Description: OpenPGP digital signature