RE: ubxtool

[rhowitt]

Yes , -R was used for both.

gpspipe -R -n 300 localhost:2947 -o /api/gpsd_ntrip.dat
gpspipe -R -n 300 localhost:2947 -o /api/gpsd_ntrip1.dat

Was there RTCM3 data in the log file?

I am setting up , hopefully, to capture the stream as it goes from the Pi to
the F9P. May have something tomorrow.


-----Original Message-----
From: gpsd-users <gpsd-users-bounces+rhowitt=address@hidden> On Behalf
Of Gary E. Miller
Sent: Saturday, April 4, 2020 2:58 PM
To: gpsd users <address@hidden>
Subject: Re: ubxtool

Yo address@hidden!

On Sat, 4 Apr 2020 11:46:56 -0400
<address@hidden> wrote:

> >>Your data is good confirmation of what can work with the u-blox 9.
> >>Now we need to figure out why the similar data passed through gpsd 
> >>is not
> working. 
> >> Can you get a capture of what gpsd is sedning to a receiver?  
> 
> Can I using gpspipe  or  should I use a logic analyzer?

I assume that "gpspipe -R" is grabbing what goes to the receiver.  But since
we don't know ehere the bug is, that assumption needs to be validated.
So looking at the data from gpsd to the receiver is a good next step.

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