gpsd-users
[Top][All Lists]
Advanced

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

Re: gpsd and ublox


From: James Browning
Subject: Re: gpsd and ublox
Date: Fri, 8 Mar 2024 07:46:30 -0800 (PST)

> On 03/07/2024 11:50 AM PST joebeis64@duck.com wrote:
> 
> As stated in an earlier message, we are interfacing with a UBLOX M8 device 
> and would love to start using GPSD. We are just starting to look at GPSD and 
> how we can retrofit our software to utilize it. I have been looking at the 
> GSPD documentation and also the UBLOX M8 receiver documentation (thanks for 
> the pointer). I have a few questions that I have after looking at the GPSD 
> documentation and the receiver documentation. Again remember this comes from 
> the perspective of Yocto Warrior version which is GPSD 3.17 (I know it sucks 
> to be me).
> 
> With respect to UBX messages. We configure the receiver to send 3 messages 
> (UBX-NAV-STATUS, UBX-NAV-TIMEGPS and UMX-TIM-TP). Is there a way for a GPSD 
> Client to get to bent these UBX messages? Or are they consumed by GPSD? I 
> understand that GPSD handles several different flavors of receivers behind 
> the scenes but wants to present a common look and feel to all users of GPSP. 
> Do you have any suggestion on how we can get those messages?


It is possible to get the raw input messages received by gpsd (in
either binary or hexadecimal form). If using the Python module, you
would need to either set gps.WATCH_RAW or gps.WATCH_RARE
respectively while unsetting gps.WATCH_JSON, probably while setting
gps.WATCH_OLDSTYLE rather than gps.WATCH_NEWSTYLE and filter out the
mandatory version watch and device JSON headers.

If not using the Python module, you would need to set the
appropriate arguments in the watch request; the gpsd_json(5) web
https://gpsd.io/gpsd_json.html and manual pages have the details.

-30-



reply via email to

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