[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ubxtool
From: |
rhowitt |
Subject: |
RE: ubxtool |
Date: |
Sat, 4 Apr 2020 11:56:52 -0400 |
Here are two more runs using gpspipe.
Gpsd_ntrip.dat was run with this gpd command line:
gpsd -n /dev/ttyACM0
ntrip://rhowittRpi:address@hidden:8082/NYPF -N -D 7
Gpsd_ntrip1.dat was run with this gpsd command line:
gpsd -n /dev/ttyACM0
ntrip://rhowittRpi:address@hidden:8082/NYPF -N
And here are a few lines of output from the -D 7 showing that RTCM data was
being received.
gpsd:PROG: NTP: ntpshm_put(/dev/ttyACM0,-20) 1586014991.999724552 @
1586014992.069765092
gpsd:SPIN: packet_get() fd 5 -> 0 (0)
gpsd:SPIN: pselect() {3 4 5 6} -> { 6 } at 1586014992.149474098 (errno 0)
gpsd:SPIN: packet_get() fd 6 -> 906 (0)
gpsd:PROG: RTCM3: unknown type 1075, length 376
gpsd:DATA: packet type 18 from ntrip://rhowittRpi:Walfer2019 with
{ONLINE|RTCM3|PACKET}
gpsd:IO: SER: => GPS:
d301784330208917d342002099c0a43100000000202101007ff7fe7e7ff2a2229a6a421aa2a2
423a87ffffffffff92d2d22eb2c06b36ff25d8afb438127808fee7fa81f5181c3fb3fef00f6f
c401120d811b4636d4720f586e997d38fb018d2e191032e71eae3d4c8118fe7846efffe037c2
b738ce63925e249ec949141317302b1b8206feee029c03478e0eb61dcc3cc044b07e30fec0b9
5082bc8e0af1d02c13ff614afd68fdf5a407d9b3a0d6010353040d4c3792d55e451df91479e5
7e3fc3eb5f1485fc5211f19c0fa2407e823704c5ce1293e04a4f21402482e55c0babffc3811f
14697c51a9f1377841882109328424cc10e1702221e0770101dbf7ffffffffffffffffffffff
fe1ffffffffffffe00000000050ec9663765ad53d55d17658db86b85f4cd5e34c97e186985b8
e95d759121223e44b486006600cc019802f9845408a6114c4a7894e129c1e879ccf397e733cd
4fa90f522ffc5ff9fff07eed17bc2f976a1ed44da85b4d4242048109021417b79f6f7edee069
2383
gpsd:IO: <= DGPS: 382 bytes of RTCM relayed.
gpsd:SPIN: packet_get() fd 6 -> 0 (11)
gpsd:PROG: RTCM3: unknown type 1085, length 198
gpsd:DATA: packet type 18 from ntrip://rhowittRpi:Walfer2019 with
{ONLINE|RTCM3|PACKET}
gpsd:IO: SER: => GPS:
d300c643d020d011480200208603e180000000002040000077ffe8a8c94828e90a09e91060ed
6953904cd2dee49f0cecfaeac60489f8c8420037fc9beedf99a117004805e4080f35d0cda18a
73b066bc336c64a7282e436eec3de3bb39f6aa2e6c5a18032c000261fe7e01033a200c71ef44
537d22560d51f035a1cf2e37fcc53dfbab87ee798fb4ccbeeae60c39602dd0dfffffffffff0c
ffff0000617596dd95f5d785b5535c75c7b80b7031136144c28a3d54faaae841d063b147621e
eb3dd57e02fbfeee2ddc5cd2430b
gpsd:IO: <= DGPS: 204 bytes of RTCM relayed.
gpsd:SPIN: packet_get() fd 6 -> 0 (11)
gpsd:PROG: RTCM3: unknown type 1095, length 314
gpsd:DATA: packet type 18 from ntrip://rhowittRpi:Walfer2019 with
{ONLINE|RTCM3|PACKET}
gpsd:IO: SER: => GPS:
d3013a4470208917d3400020b49800c000000000200111007fffffffa8292ea62baaaaa7ffff
fffff7c9923f635cf3d32f1afe1e0c504bbfc17cbdfff038005c945028b05248a8913e228525
184a847498eaddd5efb1e15072a1454a0ae087810e861d14401e9bbd2d1a72f4f31b2d3c1278
e0f66921825044b0c9b205683616ede85ad4c1720b84ee1a137ba84ea2e14273fcd36df36e5f
ce96bf4206055bb61571385650215dd501fa9207ee301fa06087957a6039ea3edfa674bea8fa
06c5ea1d53b8771d21dc6684c2ea139b604f006140b3fffffffffffffffff7776eeeffffffff
8000000069a65a679e3a597577e79e3a5d6d57d77536dd8db8e9a65afac3f5c5ed1fd880c3b1
7842f605cc925d231246908717aa2f5c1ea97d4af0a9de83bf8b7987689edbfd84faff085b10
5a20103ea829a047c085012800ff9ea3
gpsd:IO: <= DGPS: 320 bytes of RTCM relayed.
-----Original Message-----
From: gpsd-users <gpsd-users-bounces+rhowitt=address@hidden> On Behalf
Of Gary E. Miller
Sent: Friday, April 3, 2020 10:32 PM
To: gpsd users <address@hidden>
Subject: Re: ubxtool
Yo address@hidden!
On Fri, 3 Apr 2020 13:41:48 -0400
<address@hidden> wrote:
> Strsvr has the ability to take an ntrip input stream and then send
> that to both the GPS and file.
Binary identical?
> I turned on the option to send the data to a file and recorded about
> 15 seconds of data. The output is binary, so I don't know if it is of
> any use. I have attached that file. If you need a longer recording
> let me know.
Raw data is always good. I fed your file into gpsd and it decoded fine.
I see your file is plain RTCM3. With these sentences:
1006 -- Stationary RTK Reference Station ARP with Antenna Height
1008 -- Antenna Descriptor & Serial Number
1013 -- System Parameters
1033 -- Receiver and Antenna Descriptors
1075 -- GPS MSM5
1085 -- GLONASS MSM5
1095 -- Galileo MSM5
1230 -- GLONASS L1 and L2 Code-Phase Biases
> Let me know if it is NOT of any use; I have some other options that
> may capture the data, if this data is not what you need.
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?
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
gpsd_ntrip.dat
Description: Binary data
gpsd_ntrip1.dat
Description: Binary data
- ubxtool, rhowitt, 2020/04/01
- Re: ubxtool, Gary E. Miller, 2020/04/01
- Message not available
- Re: ubxtool, Gary E. Miller, 2020/04/02
- Message not available
- Re: ubxtool, Gary E. Miller, 2020/04/02
- RE: ubxtool, rhowitt, 2020/04/02
- Re: ubxtool, Gary E. Miller, 2020/04/03
- RE: ubxtool, rhowitt, 2020/04/03
- Re: ubxtool, Gary E. Miller, 2020/04/03
- Message not available
- Re: ubxtool, Gary E. Miller, 2020/04/03
- RE: ubxtool,
rhowitt <=
- Re: ubxtool, Gary E. Miller, 2020/04/04
- Message not available
- Re: ubxtool, Gary E. Miller, 2020/04/04
- Re: ubxtool, Martin Boissonneault, 2020/04/04
- RE: ubxtool, rhowitt, 2020/04/04
- Re: ubxtool, Gary E. Miller, 2020/04/04
- RE: ubxtool, rhowitt, 2020/04/06
- Re: ubxtool, Gary E. Miller, 2020/04/06
- Message not available
- Message not available
- Re: ubxtool, Gary E. Miller, 2020/04/11
- FW: ubxtool, rhowitt, 2020/04/12
- Re: ubxtool, Gary E. Miller, 2020/04/13