RE: ubxtool

[rhowitt]

Gary,
 I am just a software systems integrator hoping to piece together a cell
modem, an F9P and a RaspberryPi and make them into a fairly accurate
tracking system for a fruit farmer I am working with. I know enough about
GPS/RTK to be dangerous , but know that I have a long way to go and look
forward to your sage advice.

I have been able to hook this same F9P up to a Windows system and use
RTKlib's str2str utility with the same NTRIP caster and have gotten an RTK
fix.

Just to review, the message below indicates that a RTCM3 message was
received by GPSD,  correct?

           gpsd:SPIN: packet_get() fd 6 -> 854 (0)
          gpsd:PROG: RTCM3: unknown type 1075, length 324
          gpsd:DATA: packet type 18 from ntrip://rhowittRpi:Walfer2019 with
{ONLINE|RTCM3|PACKET}
          gpsd:IO: SER: => GPS:
d3014443302062dde0220020c1d4401a00000000202101007f7fe677e7a52223aa22282927a6
237fffffffff95c2d1d017e4568bf5f84
d2877b6a02e037613b7f47f71fb2e14c7cbbf66815402c605a00c81e7d3ae476533d6e7a4cf7
b9f1c83a108a214244d3c13f70a09bc
10b4a1f13bd27c9d323a4ef4bfea105be8b0398a930a061fcc6c80bfa403d2200f48a03fe587
ecea1fca207f28fe8e69fa4095e90257a83a20f51a8388860e22183be8df9f40fedfb2050370
112f414e9c053c9e14f287d7377f6399fd8e5ff649e0612a817a86067e4619783865e0a1ab0b
66666666666666666666666666666666000000005d65fa657e18618eb5cd5e38db5cb5cb4555
db95b363763afeb6fd69fac7f5b6e86dd0bba0c0d301a903520a6002f006100c6082b7a4ef49
1bd0378828f05190a2e3ee07df0fc11ae1e4f3c9c8efa1df43be87b4000c750d

          So what would be the reason that the RTCM3 message gets to gpsd,
but it is not passed on to F9P?
          Does GPSD not know to send this on to the F9P?
          Is this some how related to the other problem that ubxtool was
having ( multiple devices connected)?

Any words of wisdom to point me in direction ?


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

Yo address@hidden!

I had time to look at this a bit more.

On Thu, 2 Apr 2020 15:17:43 -0400
<address@hidden> wrote:

> The F9P never gets an RTK fix, but the CORS ntrip server is connected 
> and a packet is being sent every second.

Once a second is not near fast enough for NTRIP...

> Attached is gpspipe output which was collected with this command
> string: gpspipe -R -n 300 localhost:2947 -o /api/gpsd_ntrip.dat

The "localhost:2947" is redundant as that is the default.

There is no data, other than u-blox, in that capture file.  No RTCM data.
Your gpsd log fragment does show RTCM 3 data, so I'm not sure why if it not
in the dat file. 

Which differs from the other file you sent which had something, but it was
not RTCM, with the u-blox binary.

Neither data file shows the u-blox ever got an RTK fix.

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