[time-nuts] Galileo service currently degraded

[Kevin Croissant]

Thanks for the info Gary! I will check this out -- I am using the F9P for
another project now, so that might be useful.

Unrelated to gpsd...
I forgot about this until now, but I actually encountered a WNRO bug in the
U-Blox M8N (or possibly my library?) when my data collection was running. I
only have this screenshot now from the incident, but you can also download
data from the website around the WNRO timestamp and see that all
constellations stopped collecting simultaneously.
Screenshot: https://gnssperformancemonitor.com/time-nuts/wnro.png -- look
at "Server Timestamp" to see what time the glitches all actually happened
at.
It seems to me that the cause was that the u-blox M8N looked at GPS for
timestamps, even when you explicitly turn off GPS. I never did any more
investigation into it since the 9th gen was coming out and it shouldn't be
a problem again for a while.

Did anyone else see WNRO glitches with the 8th gen?

Kevin

On Sat, Jul 13, 2019 at 8:13 PM Gary E. Miller <gem at rellim.com> wrote:

> Yo Kevin!
>
> On Sat, 13 Jul 2019 17:16:37 -0400
> Kevin Croissant <kevin at kevincroissant.com> wrote:
>
> > Looking at gpsd, I'm still not sure that it supports UBX,
>
> gpsd has supported u-blox since the SiRF2-ublox TIM chip in 2007.
>
> gpsd now support all the way up to the ZED series.
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         gem at 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
>


-- 
Kevin Croissant