My latest scope clock uses a DS3232 RTC chip for general timekeeping. This chip only keeps time to the nearest second, as far as the user-readable registers are concerned. I also have a USB port that can read the time from a GlobalSat GPS puck. This reports the time once a second through the Arduino TinyGPS library, with the age of the time in milliseconds (typically 250). This should let me compensate for the read delay by setting the tick (50/60Hz) counter in my local time variables. What do any of you time nuts do about displaying the time accurately, and making the RTC be reasonably accurate compared to the GPS? Do you discipline the RTC with GPS? Do you just ignore the RTC when GPS is available? Set the RTC occasionally?
-- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/CAPbqtvfSPwVxsSFADbxm%2BNyVgSsk1AY42GgP%3Dmq0uygGJMBqZg%40mail.gmail.com.
