Re: ublox F9P - rover: no RTK fix with default gpsd ublox initialisation

[Gary E. Miller]

Yo Michael!

On Tue, 11 Oct 2022 13:27:57 +0200
Michael Haberler <haberlerm@gmail.com> wrote:

> > I can't help you with str2str, I never use it.  WHy are you not
> > using the built-in gpsd ntrip client?  
> 
> I'm still blundering up my learning curve, so please be patient

Very few have it really working well.

> it was the first configuration I got to work - separation of
> concerns, allows me to fix one issue at time

Sadly, all this stuff is very intertwined.

> I go the impression
> ntrip specs to be a moving target, as seem casters and I could not
> get two casters to work with the builtin ntrip client which work
> perfectly fine with the RTCM3 stream sent via str2str

Nope.  NTRIP is very stable.  Hardly changed in 20 years.  All an NTRIP
client does is pass on the RTCM3 data from the server to the client, without
touching it.

The moving targer is what data is sent as RTCM3, and what you receiver
needs.  That is a mess.

> I will provide
> logs etc for these failures, and will happily switch to the builtin
> ntrip client once I get it working

Why bother to get str2str working if you are just going to drop it?

> but let's keep that separate for now - AFAICT it is unrelated to my
> issue

If you say so.  I'm not convinced.

> will use gpsd from command line only for debuggung


You sent this, in antoher message:

mah@oe-sox:~/src/gpsd/gpsd-3.24/gpsd$ ./gpsd --passive --speed 460800 --debug 5 
--listenany --nowait --foreground  /dev/ublox-zed-f9p 2>&1 |tee 
/home/mah/src/gpsd/debug/gpsd-D5.log

Several things suboptimal.  gpsd should be started as root.

If you are going to use --passive, then you need to manually configure
the receiver, which you are not doing.

 /dev/ublox-zed-f9p is USB native, and has no speed, so your --speed is
a NOP.

> > A good start is to send us the output of gpsdebudinfo.  
> 
> I assume you mean the debug log output of gspd

Nope, bad assumption.  Best to pay attention to my words, not your
assumptions.  I see you did send up the results of that.

I guess you did not read the output:

You ran with sudo not as root.

    sudo will confuse the results.

Why do you have Magic Hat enabled on a non-raspberry pi?

    # Magic Hat enabled.

You are running gpsd as a user, not as root.
    
    gpsd    25209  mah    4u  IPv4 618468      0t0  TCP *:gpsd (LISTEN)
    gpsd    25209  mah    5u  IPv6 618469      0t0  TCP *:gpsd (LISTEN)

What is this next thing?

    602 ?        S<sl  13:10 /usr/bin/readsb --device 0 --device-type rtlsdr 
--gain -10 --ppm 0 --net-connector localhost,2947,gpsd_in --max-range 450 
--write-json-every 1 --db-file-lt --write-binCraft-old --net --net-heartbeat 60 
--net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 30001 --net-ro-port 
30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 
--json-location-accuracy 2 --range-outline-hours 24 --net-json-port=30012 
--write-json /run/readsb --quiet

What is this next thing?

Oct 11 16:45:18 oe-sox gpsd[24955]: gpsd:WARN: NMEA0183: TXT: Warning: PFEC inv 
format
Oct 11 16:45:18 oe-sox gpsd[24955]: gpsd:WARN: NMEA0183: TXT: Warning: PTNL inv 
format
Oct 11 16:45:19 oe-sox gpsd[24955]: gpsd:WARN: NMEA0183: TXT: Warning: PFEC inv 
format
Oct 11 16:45:19 oe-sox gpsd[24955]: gpsd:WARN: NMEA0183: TXT: Warning: PASH inv 
format
Oct 11 16:45:19 oe-sox gpsd[24955]: gpsd:WARN: NMEA0183: TXT: Warning: PMTK inv 
format

AppArmor and gpsd do not play nice together:

apparmor module is loaded.
9 profiles are loaded.
9 profiles are in enforce mode.
   /usr/bin/man
   /usr/sbin/chronyd
   /usr/sbin/gpsd


> I ran with and without passive, see logs below

As I mentioned before, running with --passive means the receiver is in
an unknown state.  So unless you configured the device, no point even
looking at the output, it is unrepeatable.

> I uploaded them to
> https://static.mah.priv.at/pub/gpsd-debug because they are a tad
> bulky I kept the RTCM3 stream to UART1 running with str2str all the
> time so no attempt to use builtin ntrip client for now

I can't help with str2str...

> I uploaded them to https://static.mah.priv.at/pub/gpsd-debug

Resuing the same file names for 2 tests is confusing to me.

> first, with --passive, gets an RTK fix:

But --passive means random and unknown receiver configuration, so useless.

In your case, it meant NMEA, of unknown version, etc.`

Your non-passive was u-blox binary, so not comparable at all.

The way NMEA and ubx report RTK is very different, and both depend on
how you have configured the receiver.

> mah@oe-sox:~/src/gpsd/gpsd-3.24/gpsd$ ./gpsd --passive --speed 460800
> --debug 5 --listenany --nowait --foreground /dev/ublox-zed-f9p 2>&1
> |tee /home/mah/src/gpsd/debug/gpsd-D5.log

Don't run as root.  --speed is a NOP.

> anything else I can provide?

See above.

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

pgpuZeJza5Mg6.pgp
Description: OpenPGP digital signature