Hello,

Yes, I did have to configure a /dev/PPS device. The RPI OS setups what is provided by the vendor.

Yes, I did consult this PDF before purchasing and using. I read this statement.

Future u-blox receivers are likely to employ multiple GNSS system times and/or receiver local times (in order to support multiple GNSS systems in parallel), so users should not rely on UBX messages
that report GNSS system time or receiver local time being supported in future. It is therefore recommended to give preference to those messages that report UTC time.


Also, USB dongle and GPIO dongles are two different things. Sufficient to say, the USB version is not producing this error. And given the GPIO pin out identified, this is still a local configuration issue and not a universal alert. As this statement attests, I can confidently use UTC time. Wow! KSTARS uses UTC also. That makes it a win for me.

Here is another.


6.6 Real Time Clock
u-blox receivers contain circuitry to support a real time clock, which (if correctly fitted and powered) keeps time while the receiver is otherwise powered off. When the receiver powers up, it attempts to use the real time clock to initialise receiver local time and in most cases this leads to appreciably faster first fixes.

I added an RTC to assist with faster locks. Also, a state of Static is when the movement Delta is near 0. Then drift is less likely when Static. With limited GPIO pins, USB is the better option. Two options exist for 3V RTC devices. Most exhaust fans block pin 1. I used the second 3V pin group. This allowed use of the RTC.

Read More...