That is what should happen anyway. When your NTP daemon has a network/GPS/PPS lock, it will try to avoid jumping the system time, and instead call clock_adjtime() to request the kernel adjust the rate of the system clock to correct for the observed errors.The solution in the video can hold an accurate enough time signal even if no GPS is available, and catches up as soon as GPS becomes available again.
When external synchronization is lost, the clock should continue to run at the last corrected rate. Even with subsequent temperature changes, this is likely to remain an order of magnitude better than the uncorrected rate.
How long do you need to be able to run without connectivity, and how much drift is acceptable, in ms or ppm?
Actually that was a Pi1. It makes a bit more sense to hack an older board for internet fame, rather than risk one of the current higher RAM models.However, this was for a raspberry 4.
Statistics: Posted by jojopi — Mon Jul 01, 2024 12:33 pm
