Re: adding/removing ntrip devices via gpsdctl?

[Gary E. Miller]

Yo Michael!

On Thu, 20 Oct 2022 17:17:52 +0200
Michael Haberler <haberlerm@gmail.com> wrote:

> I can use the built-in ntrip client when passing the ntrip URI to
> gpsd at startup - after a few seconds gpspip -r shows
> 
>       
> {"class":"DEVICE","path":"ntrip://rtk2go.com:2101/stiwoll","driver":"RTCM104V3","activated":"2022-10-20T15:12:47.397Z","flags":4}

Cool.

> I had less luck with trying to add/remove ntrip client URI's with
> gpsdctl 

AFAIK, you are the first to try.

> like starting just with a GPS device, and later adding
> 
>       gpsdctl add ntrip://rtk2go.com:2101/stiwoll
> <ntrip://rtk2go.com:2101/Gutsche>
> 
> in this case gpspipe -r shows the device was activated, but no driver
> was selected:
> 
>       
> {"class":"DEVICE","path":"ntrip://rtk2go.com:2101/stiwoll","activated":"2022-10-20T15:14:57.435Z"}

Can you provide a -D4 log from gpsd when you try the add?  Then we can
see what is going on.

> is that a scenario which is supposed to work?

Never been tested, so without evidence that is ever worked, I'd say: No.

> I'd like to get out of the network dependency for gpsd startup, and
> possibly add/remove ntrip clients through UI interaction

I'd like a pony.  Maybe we can get this to work, dunno how hard that
might be without the -D4 log.

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

pgpLfgZLcnbRQ.pgp
Description: OpenPGP digital signature