FW: ubxtool

[rhowitt]

-----Original Message-----
From: address@hidden <address@hidden> 
Sent: Tuesday, April 7, 2020 1:39 PM
To: 'address@hidden' <address@hidden>
Subject: RE: ubxtool

Gary,

Got the analyzer hooked and have done captures from Windows to GPS (
rtklib's strsrv )  and GPSD to GPS.
Not sure how you wanted the data so to start I did a hex dump to a binary
file.
Description of the attached files.
FAIL-F9P...       contains the GPSD RTCM data.      RTK LED was off
Succes-F9P...  contains the STRSRV RTCM data.   RTK LED was  blinking 

F9P_UART_TX--PI   contains F9P send to the PI, during the Fail session
F9P-UART_TX--PC   contains F9P send to the PCX , during the Success session


I use the Saleae analyzer so if needed I can dump the whole analysis to a
file that will contain both the digital and analog signals.
You can download their software (free) and "replay" the log file .

Let me know if you need any other data.

Regards,
Rick

-----Original Message-----
From: gpsd-users <gpsd-users-bounces+rhowitt=address@hidden> On Behalf
Of address@hidden
Sent: Monday, April 6, 2020 10:33 AM
To: 'Gary E. Miller' <address@hidden>; 'gpsd users' <address@hidden>
Subject: RE: ubxtool

Gary,

I am working on putting an analyzer on the GPS dev board. But ran into a
problem that the breakout pin that is suppose to be showing RX data into the
board is not showing any data.  Even though RTKlib's strsrv is sending data
to the GPS and the GPS is blinking it's RTK LED.  Currently the dev board is
based on USB, where it breaks out the serial traffic from the USB. 

So working on solution to by-pass USB altogether and just use serial.

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

Yo address@hidden!

On Sat, 4 Apr 2020 20:38:47 -0400
<address@hidden> wrote:

> 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

Good.  As I said in the message before the one just just replied to:

-- No point running gpsd with different debug levels if you don't send the
-- debug output.

> Was there RTCM3 data in the log file?

As I said in the message before the one just just replied to:

-- > gpsd:PROG: RTCM3: unknown type 1075, length 376
-- > gpsd:DATA: packet type 18 from ntrip://rhowittRpi:Walfer2019 with
--
-- gpsd got an RTCM3 type 1075 packet.

And I also said:

-- Ignoring gpsd_ntrip.data as you did not send the matching output.
--
-- Looking at gpsd_ntrip1.dat, looks like the same data types as before.
-- 
    -- 1006
    -- 1008
    -- 1013
    -- 1033
    -- 1075
    -- 1085
    -- 1095
    -- 1230

Clear?

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

No rush.  I don't expect there to be a problem in that link, just being
complete.

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

SUCCESS-F9P_UART_RX--STRSRV_NTRIP_on_PC.bin
Description: application/dflog

F9P_UART_TX--PI.bin
Description: application/dflog

FAIL-F9P_UART_RX--GPSD_NTRIP_on_PI.bin
Description: application/dflog

F9P_UART_TX--PC.bin
Description: application/dflog