Minimal terminal clock synced to NTP. Exploring alternative time sources (GPS) and formats (LTC, MTC, Swatch Internet Time).
Already have an account? Log in.
To make the experience fit your profile, pick a username and tell us what interests you.
Key Features
chrono-ntp currently uses NTP servers to determine an accurate time offset independent of the local system clock. While this works well on networked systems, the next step is to support GPS as an alternative time source.
Many USB GPS receivers expose a serial interface and provide NMEA sentences, including time and date information derived from GPS signals. Using GPS would allow chrono-ntp to operate as a network-independent reference clock, useful in environments without reliable internet access or where an external time source is preferred.
The plan:
At the moment, I’m looking for a suitable USB GPS receiver to test this with real hardware rather than relying solely on simulated NMEA data. Once a device is selected, initial work will focus on basic parsing and validation before integrating it cleanly into chrono-ntp’s existing architecture.
This should keep the tool simple while expanding it beyond network-based time synchronization.
True, but where is the fun in that? :) I wanted something that is self-contained and also allows nerdy time formats like Coordinated Lunar Time. It also allows me to get deeper into the concepts of Go, since I mostly use TypeScript in my professional work.
Christian
Russell
M. Bindhammer
HIGEDARUMA
Aren't modern OSes already running a system service to sync the system clocks to NTP and other sources? For example Linux runs chronyd or the older ntpd. Chronyd can also interface to a GPS receiver using gpsd. See #An NTP server using GNSS for time So to get the NTP time, just show the system time.