gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ubxtool


From: Gary E. Miller
Subject: Re: ubxtool
Date: Thu, 2 Apr 2020 10:58:26 -0700

Yo address@hidden!

I guess I should have mentioned that the contents of the unreadable jpg,
which are now below, are not useful.  For the reasons already discussed.
I already told you how to make it work.  Those instructions are still
at the bottom of this email.

Do that, then report those results.

On Thu, 2 Apr 2020 10:18:36 -0400
<address@hidden> wrote:

> Below is the text output from the ubxtool command. 
> 
> Also, how should I capture the ntrip stream?
> 
>  
> 
>  
> 
> pi@ApplePi:~ $ ubxtool -e NMEA
> 
> ubxtool: enable NMEA
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x09 (GBS) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x00 (GGA) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x01 (GLL) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x02 (GSA) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x07 (GST) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x03 (GSV) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x04 (RMC) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x05 (VTG) Rate 1
> 
>  
> 
> sent:
> 
> UBX-CFG-MSG:
> 
>   Rate set Class xf0 (NMEA) ID x08 (ZDA) Rate 1
> 
>  
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}
> 
> UBX-NAV-PVT:
> 
>   iTOW 350117000 time 2020/4/2  1:14:59 valid x37
> 
>   tAcc 69 nano 73028 fixType 3 flags x1 flags2 xeb
> 
>   numSV 7 lon -775415759 lat 432253739 height 50969
> 
>   hMSL 85960 hAcc 15148 vAcc 29283
> 
>   velN 30 velE 30 velD 11 gSpeed 42 headMot 15224380
> 
>   sAcc 731 headAcc 7142867 pDOP 546 reserved1 0 26042 11331
> 
>   headVeh 2900837 magDec 0 magAcc 0
> 
>  
> 
> UBX-NAV-POSECEF:
> 
>   iTOW 350117000 ecefX 100420219 Y -454526934 Z 434581460 pAcc 3297
> 
>  
> 
> UBX-NAV-DOP:
> 
>   iTOW 350117000 gDOP 695 pDOP 546 tDOP 430 vDOP 499
> 
>   hDOP 220 nDOP 128 eDOP 178
> 
>  
> 
> UBX-NAV-VELECEF:
> 
>   iTOW 350117000 ecef: VX 2 VY 3 VZ 1 vAcc:73
> 
>  
> 
> UBX-NAV-TIMEGPS:
> 
>   iTOW 350117000 fTOW 73026 week 2099 leapS 18 valid x7 tAcc 69
> 
>  
> 
> UBX-NAV-PVT:
> 
>   iTOW 350118000 time 2020/4/2  1:15: 0 valid x37
> 
>   tAcc 70 nano 72718 fixType 3 flags x1 flags2 xeb
> 
>   numSV 7 lon -775415731 lat 432253723 height 51260
> 
>   hMSL 86252 hAcc 15313 vAcc 29315
> 
>   velN -53 velE 88 velD 11 gSpeed 103 headMot 15224380
> 
>   sAcc 839 headAcc 7148150 pDOP 545 reserved1 0 26042 11331
> 
>   headVeh 2900837 magDec 0 magAcc 0
> 
>  
> 
> UBX-NAV-POSECEF:
> 
>   iTOW 350118000 ecefX 100420249 Y -454526962 Z 434581466 pAcc 3307
> 
>  
> 
> UBX-NAV-DOP:
> 
>   iTOW 350118000 gDOP 695 pDOP 545 tDOP 430 vDOP 499
> 
>   hDOP 220 nDOP 128 eDOP 178
> 
>  
> 
> UBX-NAV-VELECEF:
> 
>   iTOW 350118000 ecef: VX 9 VY -1 VZ -5 vAcc:84
> 
>  
> 
> UBX-NAV-TIMEGPS:
> 
>   iTOW 350118000 fTOW 72716 week 2099 leapS 18 valid x7 tAcc 70
> 
>  
> 
>  
> 
> -----Original Message-----
> From: gpsd-users <gpsd-users-bounces+rhowitt=address@hidden> On
> Behalf Of Gary E. Miller
> Sent: Wednesday, April 1, 2020 9:42 PM
> To: address@hidden
> Subject: Re: ubxtool
> 
>  
> 
> Yo  <mailto:address@hidden> address@hidden!
> 
>  
> 
> I can't read your jpg.  Please send screen caps as text.
> 
>  
> 
> On Wed, 1 Apr 2020 21:26:01 -0400
> 
> < <mailto:address@hidden> address@hidden> wrote:
> 
>  
> 
> > I have a ZED-F9P that I am trying to get to work with ntrip RTCM3   
> 
> > corrections from a CORS network.  
> 
>  
> 
> I do not think CORS sends what the ZED-F9P wants.  The F9P does not
> work with original RTCM3 packets.  If you could send a capture of
> that stream then I can check.
> 
>  
> 
> > I started to work with ubxtool  to  
> 
> > investigate some of the settings in the F9P.  After playing for a   
> 
> > little bit I want to get a fresh start with the F9P so I turned off
> >   
> 
> > the power to the raspberryPi and the F9P.  
> 
>  
> 
> Reseting an F9P can be pretty hard.  Especially if you have BBR.  But
> that is not you problem here.
> 
>  
> 
> > After everything rebooting  
> 
> > and the F9P had a 3D fix, I tried to use ubxtool again. When I try
> > to   
> 
> > run a command I get and error message saying "multiple devices are
> >  
> 
> > attached".  
> 
>  
> 
> Yup.  Perfectly normal.  The gpsd is seeing two devices: The CORS
> feed, and the F9P.  You just need to tell ubxtool which to use.
> 
>  
> 
> >  Gpsd is running. There is only one GPS and it is on  
> 
> > /dev/ttyACM0 and gpsmon shows valid data. Did I some how mess up a
> >  
> 
> > gpsd configuration? If so how do I reset it?  
> 
>  
> 
> Try this:
> 
>                gpspipe -w -n 5
> 
>  
> 
> Look at what "DEVICES" shows you.  Then connect to the one with the
> F9P. Prolly something like this:
> 
>                ubxtool -p MON-VER localhost:2947:/dev/ttyACM0
> 
>  
> 
> Note it is common for USB devices to jump around from ttyACM0 to ACM1
> to ACM2.
> 
>  
> 
> Also:
> 
>                what version of gpsd are you running?  (gpsd -V)
> 
>         how do you start gpsd?
> 
>  
> 
> When you get an RTK fix from the F9P please send a raw data capture.
> 
> Prolly something like this:
> 
>                gpspipe -R -n 300 localhost:2947"/dev/ttyACM0
> 
>  
> 
> RGDS
> 
> GARY
> 
> ---------------------------------------------------------------------------
> 
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
> 
>                 <mailto:address@hidden> address@hidden   <Tel:+1>
> Tel:+1 541 382 8588
> 
>  
> 
>                    Veritas liberabit vos. -- Quid est veritas?
> 
>     "If you can't measure it, you can't improve it." - Lord Kelvin
> 




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

Attachment: pgp6DTQ5yitBu.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]