Re: [gpsd-users] GPSD : Get vertical and horizontal accuracy (Vacc and Hacc)

[Krishna]

Hi Gary,

Thanks for your reply.
Please provide more information on eph and epv fields. Any web 
documentation/link is helpful.
Our customer is using algorithm which uses NAV_POSLLH  parameters for 
processing.
Whether these fields internally derived by POSLLH UBX command? 
>From the GPSD source code, I understand that "display_nav_sol" in UBX_NAV_SOL 
>case updates the eph and epv fields. Whether my understanding is correct?

Regards,
Krishna

-----Original Message-----
From: gpsd-users [mailto:gpsd-users-bounces+krishnaks=address@hidden] On Behalf 
Of Gary E. Miller
Sent: Wednesday, June 12, 2019 11:56 PM
To: address@hidden
Subject: Re: [gpsd-users] GPSD : Get vertical and horizontal accuracy (Vacc and 
Hacc)

Yo Krishna!

On Wed, 12 Jun 2019 13:01:39 +0530
"Krishna" <address@hidden> wrote:

> We are using u-blox UBX-M8030 GPS module in the ARM based target 
> platform.
> 
> Currently we are using v3.16 for our evaluation.

Ouch.  That is pretty old.  3.18.1 is current.  3.19 is very soon.

> We would like to get vertical accuracy and horizontal accuracy fields 
> using GPSD framework. These fields are part of POSLLH (Geodetic
> position) UBX packet.

I assume you mean hAcc (byte offset 20) and vAcc (byte offset 24).

Pretty useless as they are undefined by u-blox.  But they are reported as eph 
and epv, their standard names, in the TPV JSON sentence.

> It looks like, by default, GPSD will not fill/process these details.

Not for a wheil.

> Let us know if there is any configuration to enable these feature. 

We already read your mind in the past and fixed it in the past.

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