gpsd-users
[Top][All Lists]
Advanced

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

Re: Ublox and GPSD 3.22


From: Jeff Curtis
Subject: Re: Ublox and GPSD 3.22
Date: Sat, 2 Jul 2022 09:36:44 -0400

Attachment: log.raw
Description: Binary data

Attachment: telnetCapture.txt
Description: Text document

Hello,

 

Running Raspberry PI Raspbian bullseye and Ublox compatible USB GPS receiver.

 

Install GPSD via apt-get which installs gpsd 3.22

 

Starting gpsd with the following command:

 

gpsd -G -n -F /var/run/gpsd.sock /dev/serial0 /dev/pps0

 

Run cgps

 

cgps shows 3D Fix for status but latitude, longitude, and altitude are all zero

 

Run xgps

 

xgps shows 3d fix and updating correct ecef values, but latitude, longitude and altitude are all zeros.

 

Capture raw log with command gpspipe -R -x 20 > log.raw (Attached)

 

Decode with gpsdecode < 'log (1).raw’ Lat and long values are present

 

telnet to port 2947 and issue command ?WATCH={"enable":true,"json":true}; and log results (Attached)

 

Lat long and Altitude values are all zeros



Thanks,


Jeff





On Jun 30, 2022, at 11:01 PM, Gary E. Miller <gem@rellim.com> wrote:

Yo Jeff!

On Thu, 30 Jun 2022 21:07:52 -0400
Jeff Curtis <jeffreyscurtis@mac.com> wrote:

Forgive me— Here is a raw log with and associated screenshots of xgps
and caps showing the lat /lon as zeros-  My story hasn’t changed, to
get around the issue I have to use the -p switch so gpsd doesn’t
configure the device to ublox mode. This only happened after I
upgraded the os and GPSD.

Once again, when I take your raw log, I see good lat/lon/alt

$ gpsdecode < 'log (1).raw'
[...]
{"class":"TPV","device":"stdin","mode":3,"time":"2022-07-01T00:58:24.000Z","ept":0.005,"lat":40.302825265,"lon":-73.980219058,"altHAE":-27.2387,"altMSL":6.3198,"alt":6.3198,"epx":27.674,"epy":41.046,"epv":75.900,"track":64.9518,"magtrack":52.2391,"magvar":-12.7,"speed":0.024,"climb":0.003,"eps":82.09,"epc":151.80,"ecefx":1344247.43,"ecefy":-4681846.85,"ecefz":4103668.94,"ecefvx":0.02,"ecefvy":0.01,"ecefvz":0.01,"ecefpAcc":20.12,"ecefvAcc":0.85,"velN":0.010,"velE":0.022,"velD":-0.003,"geoidSep":-33.558,"eph":63.080,"sep":88.920}

See attached for the full output of gpsdecode.

Looks to me like a broken binary.

Since ther is no matching info on gpsd version, gpsd startup parameters,
where the gpsd binary is from, no way for me to comment further.



RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com  Tel:+1 541 382 8588

   Veritas liberabit vos. -- Quid est veritas?
   "If you can't measure it, you can't improve it." - Lord Kelvin
<log1.json>


reply via email to

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