locked Re: Clock Sync #Timesync


Kevin McQuiggin (VE7ZD/KN7Q)
 

On 04/07/2021 15:40, Jim Pennino via groups.io wrote:
Re fake chips: I have no idea and don't care though u-blox might. The only features used by ntp is the output of NMEA sentences so any other capability the u-blox 8 series has is irrelevant to ntp. FYI u-blox makes dozens of different chips with different capabilities all of which identify as u-blox 8.

Actually ntpd doesn’t work very well using NMEA sentences via USB or serial port as input.  This is because of variance in the timing of the serial data stream and the way that the machine's CPU responds to interrupts on the serial or USB port from the GPS where the GPS unit is connected.  Timing can be all over the map due to CPU workload and other tasks which are running.

If you have a local GPS receiver, then a FAR better approach is to use a pulsed output from the device to generate a high priority interrupt that is handled directly by the time management processes.  This involves another daemon called gpsd and use of a GPS receiver that outputs a nanosecond-accurate “pulse per second” signal.  Cheap receivers usually do not provide a PPS signal but several slightly more expensive ones do.  

There is a good writeup on how to do this at https://www.lammertbies.nl/comm/info/gps-time.  

I use a Garmin Garmin 18x LVC GPS Navigator Unit, which is available on Amazon for about USD$68.  See the link for how to connect what to where!

73,

Kevin VE7ZD/KN7Q






Hi Jim,

one issue with "fake" u-blox boards (note they usually have real u-blox GPS/GNSS receivers but lack on the rest of the board) is that some have insufficiently sized SPI memory chips and as a result cannot be upgraded to newer firmware versions. That can be annoying if a new satellite constellation needs to be supported, for example.

73
Bil
G4WJS.





Join main@WSJTX.groups.io to automatically receive all group messages.