Re: ubxtool set GLONASS L1/L2

[Gary E. Miller]

Yo John!

On Wed, 6 May 2020 19:43:34 -0400
John Ackermann N8UR <address@hidden> wrote:

> Just pulled the latest head and am building now (my testbed for this
> stuff is a little old Atom 520 board, so not the fastest horse in the
> barn).

I build on RasPi 3, so I understand.

> Sad news... ubxtool happily took the "GLONASS,2" command now, but it
> appears not to have made any difference.

While you are waiting for me to fix this, you also have the Configuration
Items options:

        ubxtool -P 27,10 -z CFG-SIGNAL-GLO_L2_ENA,1

> Then sent -e GLONASS,2:
>       * the ubxtool "sent" message said GLONASS L1 enable

That is the decode of what was sent.  So it has to be in where you
were originally looking.

> The same set of commands on the F9T setting -P 29.00 ended up with
> GLONASS L1 enabled, but not L2.  So it worked, sort of.

ubxtool command sedning knows nothing of the receiver versions, only
the protocol version.  Which is not involved in -e GLONASS

> So there's not only a bug, it's a bug that acts differently on the two
> slightly different devices

Different u-blox are very picky, in different ways, about the CFG-GNSS
command.  Way too many otherwise legal settings that are illegal in
combination.  Try the Configuration Items as above, that is the u-blox
answer to the CFG-GNSS mess.

> What concerns me a bit is that in both cases the message following the
> -e GLONASS,2 command seems to tell it to enable only L1:

Yes.  I'm juggling too many balls today.  Another fix pushed to git
head.

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

pgpDqMMVB3Txc.pgp
Description: OpenPGP digital signature