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?
A second general question is about leap seconds. Is it expected that the receiver handles leap seconds and it is transparent to GPSD? Or does GPSD do something with leap seconds? Things like leap seconds are reported in the UBX messages mentioned above so that is why we use them. The following was taken from the ublox documentation:
u-blox receivers are designed to handle leap seconds in their UTC output and consequently users processing UTC times from either NMEA and UBX messages should be prepared to handle minutes that are either 59 or 61 seconds long. Leap second information can be polled from the u-blox receiver with the message UBX-NAV-TIMELS for Protocol Version 18 and above.
One other question is if time always reported as UTC Time by GPSD (WATCH_JSON)? Or is it sometimes in GPS Seconds?
I hope I am clear with the above. It not then please ask questions. We are experimenting with writing a GPSD Client such that we can use it as a shim between GPSD and our current application as well as support others who want to directly interface with GPSD.
Thank you!
Joe B.