Re: How do you access UBX MON-HW messages in a gpsd client

From:

Patrick Conroy

Subject:

Date:

Tue, 19 Mar 2024 21:01:09 -0600

Gary - just for curiosity, is the jamming field normalized across devices? Or will the value (the interpretation of the value) end up being device specific?

Is 74 good or bad? :)

On Tue, Mar 19, 2024 at 5:40 PM Gary E. Miller <gem@rellim.com> wrote:

Yo All!

I just pushed to git head code that succeeds in getting the new jam
key to GPSD SJON.

It looks like thuis, note the last key:value pair:

{"class":"TPV","device":"/dev/ttyACM0","status":2,"mode":3,"time":"2024-03-19T23:04:53.000Z","leapseconds":18,"ept":0.005,"lat":44.068790000,"lon":-121.314043000,"altHAE":1113.6700,"altMSL":1135.0200,"alt":1135.0200,"epv":3.489,"track":72.1306,"magtrack":86.5490,"magvar":14.4,"speed":0.009,"climb":0.086,"eps":0.31,"epc":6.97,"ecefx":-2386054.74,"ecefy":-3922204.73,"ecefz":4414361.25,"ecefvx":-0.01,"ecefvy":-0.02,"ecefvz":0.01,"ecefpAcc":3.99,"ecefvAcc":0.31,"geoidSep":-22.154,"eph":1.934,"sep":5.510,"jam":74}

Or, usgin jq to make it pretty:

kong ! # jq < tmp
{
"class": "TPV",
"device": "/dev/ttyACM0",
"status": 2,
"mode": 3,
"time": "2024-03-19T23:04:53.000Z",
"leapseconds": 18,
"ept": 0.005,
"lat": 44.068790000,
"lon": -121.314043000,
"altHAE": 1113.6700,
"altMSL": 1135.0200,
"alt": 1135.0200,
"epv": 3.489,
"track": 72.1306,
"magtrack": 86.5490,
"magvar": 14.4,
"speed": 0.009,
"climb": 0.086,
"eps": 0.31,
"epc": 6.97,
"ecefx": -2386054.74,
"ecefy": -3922204.73,
"ecefz": 4414361.25,
"ecefvx": -0.01,
"ecefvy": -0.02,
"ecefvz": 0.01,
"ecefpAcc": 3.99,
"ecefvAcc": 0.31,
"geoidSep": -22.154,
"eph": 1.934,
"sep": 5.510,
"jam": 74
}

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