Yo Hans! On Tue, 3 Mar 2026 23:23:48 +0100 Hans Mayer <[email protected]> wrote:
> it is a strange behaviour.
UNtil you understand it.
> > So, how did you configure you x20p?
>
> Not at all,
> ubxtool -p RESET
Without the -P, that will not work. Even then, not much can be done
with the gen20.
> by chance I realised it's working from a remote system. This system
> did have an old version from gpsd. The git log showed a date from Feb
> 1st. So I did an upgrade to the latest commit and I had the same
> behaviour as on the server with the X20P, namely the missing values.
The fault lies in the gen20 receivers, not in gpsd.
The u-blox folks screwed the pooch on the Gen10 and Gen20. There is
NO WAY for gpsd to auto configure them. You must explicitly enable
the needed messages.
> > qual comes from a few sources, like NAV-SAT. It is usually not on
> > the JSON unless there is an error condition. Like Sat unhealthy.
> >
> > prRes also comes from NAC-SAT, NAV-SIG, or NAV-SIGINFO. Did you
> > enable them?
> This was the solution
> ubxtool -z CFG-MSGOUT-UBX_NAV_SIG_UART1,1
> In the moment I entered this command xgps showes the values.
Just a start. A lot more you should do. Did you read the
unxtool-examples for the newer u-blox?
> But more interesting when I disable it again xgps is still showing
> the values.
Harder to disable than you think. How do you think you did it?
> Until I terminate xgps and start it again. disconnect and connect is
> not enough.
As expected. The rate of skyview from a receiver can be very slow, so
xgps and cgps show the last values until new values come. Maybe a
timeout should be applied.
> ( But this I don't want to know why it's the case )
>
> I have a solution, but we can say it worked with older versions and
> X20P too.
Sure, things worked a lot better on u-blox gen9 and before. It is
gen10 and gen20 that require major manual intervention.
> P.S.: Is there a chance to get back the alias like "ubxtool -e
> NAV-SIG" also for HPG 2.02 ?
Nope. With Gen9 and before, gpsd could send a command to say
"enable NAV-SIG" on this port, and this port only. But there is
no such command on Gen10 and Gen20. That command is just GONE.
You must use "Configuration Items". You did read ubxtool-examples,
right?
So you have to fo what you did:
ubxtool -z CFG-MSGOUT-UBX_NAV_SIG_UART1,1
For each message you want/need. For each port you need it on.
There is no way to query the receiver for "what port am I on". Without
knowing the current port, gpsd would have to enable NAV-SAT on all
ports, and that would overload some ports, break the ability to
configure different ports differently, and likely overload the CPU.
> Or at least a hint in related man pages. I know Gary, no one is
> reading man pages.
ubxtool-examples is a lot longer than just a hint.
It need not be this way, but that is what u-blox wants. I have
complained. I think one or two of them may be starting to understand.
They think everyone uses Windows and loves u-center.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
[email protected] Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgp8izFtZpC6w.pgp
Description: OpenPGP digital signature
