[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BUG: ubxtool enable/disable RAWX fails
From: |
Gary E. Miller |
Subject: |
Re: BUG: ubxtool enable/disable RAWX fails |
Date: |
Tue, 28 Apr 2020 14:07:33 -0700 |
Yo John!
On Tue, 28 Apr 2020 16:12:30 -0400
John Ackermann N8UR <address@hidden> wrote:
> Gary, you're not reading carefully enough. Both the ubxtool -P issue,
> and the bad RINEX files, occur when I am using a *NEO-M8P* as well as
> a ZED-F9P. So the problem is with the 8 series as well, or at least
> maybe more recent 8 series (though this unit is about 9 months old)
> if they updated the protocol from earlier versions.
There are two version of the 8P. One does RTCM2, and one does RTCM3.
I suspect the RTCM3 is a backport of the 9 code.
We know the RTCM2 version works. I have used it many times.
> To be sure, I just unplugged the F9P entirely. I used uCenter to
> reset the *NEO-M8P* to factory default, then plugged it back in to
> the Linux box.
I do not trust u-center.
> I then followed the instructions in the gpsrinex page. It appears
> that some messages, such as turning off NMEA and maybe disabling the
> non-GPS constellations, worked.
Easy to tell with ubxtool.
> But issuing ubxtool -e RAWX did not cause RAWX messages to be emitted.
Works for me.
> Doing ubxtool -p MON-VER reports the version to be 20.30. When I did:
>
> ubxtool -P 20.30 -e RAWX
>
> I started getting RAWX output.
>
> THIS IS ON A SERIES 8 RECEIVER.
better to let MON-VER do the talking. All filters are lossy.
> Running
> ubxtool -p CONFIG -v 2 -P xx
> ubxtool -p STATUS -v 2 -P xx
>
> failed with a floating point conversion error.
Duh. xx is not a floating point number!
> Plugging in "20.30"
> for xx, I got the results shown in the two attached log files.
That would be correct. If you have better text for the doc, send it.
Your GLONASS is off, shold be on:
UBX-CFG-GNSS:
msgVer 0 numTrkChHw 28 numTrkChUse 28 numConfigBlocks 4
gnssId 0 TrkCh 8 maxTrCh 16 reserved 0 Flags x01010001
GPS L1C/A enabled
gnssId 3 TrkCh 2 maxTrCh 16 reserved 0 Flags x01010000
BeiDou B1I
gnssId 5 TrkCh 0 maxTrCh 3 reserved 0 Flags x01010001
QZSS L1C/A enabled
gnssId 6 TrkCh 8 maxTrCh 14 reserved 0 Flags x01010000
GLONASS L1
Yes, it is tricky to do. But the examples do work.
UBX-CFG-NAV5:
mask 0xffff dynModel 0 fixmode 3 fixedAlt 0 FixedAltVar 10000
Not sure how much it matters to the RZWX, but dynModel 1 would be better.
Your RAWX is working, but w/o the GLONASS:
UBX-RXM-RAWX:
rcvTow 245122.993 week 2103 leapS 18 numMeas 10 recStat 0x1 version 1
reserved1[2] 0xdf 0x3b
recStat (leapSec)
prmes 18334623.271 cpMes 96349066.305 doMes 71.112305
gnssId 0 svId 28 sigId 0 freqId 0 locktime 64500 cno 49
prStdev 5 cpStdev 1 doStdev 8 trkStat 15
[...]
And here is the big one:
Note the rcvTow: 245122.993. NRCan wants measurements on the top of
the second. So this will not work with NRCan. This has been known
for a while. No known workaround.
All good RINEX files we have tested have rcvTow very close to the top
of the second. This have been much discussed recently here.
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
pgpVvZ3hBCLYM.pgp
Description: OpenPGP digital signature