Re: How do you access UBX MON-HW messages in a gpsd client

[Gary E. Miller]

Yo Thomas!

On Mon, 18 Mar 2024 23:35:03 +0000
Thomas Giglia <tgiglia@hotmail.com> wrote:

> Bottom line. My source looks like it came from a tarball I installed
> several months ago.

Regardless of when it was installed, that source is a lot older than
that.

Since the patches are a day old, no good for the present purposes.

> Created a new repos and cloned from git.
> Build and install completed successfully and according to the
> documentation.

Good.
 
> I will test the new "jam" field tomorrow.

Well, since you are ready to test, I took anouther look at the code,
and I see "jam" was not coming out in the JSON.  Ugly.  UBX is supposed
to start the data from every epoch with a UBX-NAV-PVT, and end every
epoch with a UBX-NAV-EOE.  Sadly, NAV-HW and NAV-RF are sent AFTER the
NAV-EOE.  So the cycle ender finds the NAV-HW too late for the current
epoch, and too soon for the next epoch.

I will have to sleep on this one before I come up with a good fix.

You can still starta the new gpsd with "-nND 5" and see the jamInd in
the log output.  You will no longer need to enable the MON-HW.

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

pgpIyK1e5aXnU.pgp
Description: OpenPGP digital signature