gpsd-users
[Top][All Lists]
Advanced

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

Re: [gpsd-users] Where is my RTK fix?


From: pisymbol .
Subject: Re: [gpsd-users] Where is my RTK fix?
Date: Wed, 11 Sep 2019 16:42:06 -0400



On Wed, Sep 11, 2019 at 3:58 PM Gary E. Miller <address@hidden> wrote:
> Oh I was looking at this:
>
> 2208 #define STATUS_NO_FIX   0   /* no */
> 2209 #define STATUS_FIX  1   /* yes, GPS, without DGPS */
> 2210 #define STATUS_DGPS_FIX 2   /* yes, with DGPS */
> 2211 #define STATUS_RTK_FIX  3   /* yes, with RTK Fixed */
> 2212 #define STATUS_RTK_FLT  4   /* yes, with RTK Float */
> 2213 #define STATUS_DR   5   /* yes, with dead reckoning */
> 2214 #define STATUS_GNSSDR   6   /* yes, with GNSS + dead reckoning */
> 2215 #define STATUS_TIME 7   /* yes, time only (surveyed in, manual)
> */ 2216 #define STATUS_SIM  8   /* yes, simulated */
>
> I need to look at it more carefully then.

Field 6 is called the "Quality Indicator", which is split up into "mode"
and "status".

Right. But STATUS_RTK_FIX  (3) is what gpsd sets after parsing GGA NMEA in processGGA() (confirmed in gdb).

So it looks like this issue was fixed in 3.19 but broken in 3.17-5, Confirmed by a custom build.

Gary, is there any reason why 3.19 hasn't been pushed upstream so 18.04+ (and <insert your favorite distro here>)  just installs it automatically? This is a bit frustrating that I have to build gpsd from source to pick up a fix like this.

-aps

reply via email to

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