ELSEIF
Your brief EB
536 stories from 179 feeds 1068 clusters Refreshed 9 minutes ago next pull 20:24

TECH Signal 246 2 feeds carried it

Engineer rebuilds 1995 GPS time server with Raspberry Pi to avoid cellular network outages

A vintage TrueTime XL-AK GPS time server was restored using a Raspberry Pi and GNSS HAT to create a stratum 1 NTP server for local time synchronization.

WHY IT MATTERS

GPS-based time servers remain critical for network stability, and legacy hardware can be repurposed for modern precision timing needs. This project demonstrates how low-cost components can replace aging infrastructure while maintaining reliability.

Written by elseif from the cluster below · every claim links back to a source

The three things worth knowing

01

The rebuild replaces the original hardware with a Raspberry Pi 5 and GNSS HAT for stratum 1 NTP timekeeping.

02

Chrony and PPS (Pulse Per Second) are used for precise time synchronization, with fallback to internet NTP pools.

03

Thermal and CPU stability tweaks were applied to improve oscillator performance and timing accuracy.

THE READ

What the cluster adds up to.

ORIGINAL ANALYSIS

This project repurposes a 1995-era TrueTime XL-AK GPS time server by integrating a Raspberry Pi 5 and a GNSS HAT, converting it into a stratum 1 NTP server. The motivation stems from a recent cellular network outage caused by a similar GPS time server failure, highlighting the ongoing reliance on precise timing infrastructure. The rebuild retains the original enclosure and display while modernizing the internal components, demonstrating how legacy hardware can be adapted for contemporary use cases without full replacement.

The core of the upgrade involves replacing the original timing mechanism with a Raspberry Pi running Chrony, a time synchronization daemon. The GNSS HAT provides NMEA sentences and PPS signals, which are fed into Chrony for high-precision timekeeping. The configuration includes fallback to internet NTP pools, ensuring redundancy if the GPS signal is lost. Hardware timestamping on the Pi 5 further improves accuracy, though the system remains dependent on the stability of the Pi’s oscillator and thermal environment.

To mitigate timing drift, the engineer implemented several stability tweaks, including forcing the Pi’s CPU to run at a constant speed, isolating a CPU core for PPS interrupts, and insulating the device to reduce thermal fluctuations. These adjustments address the Pi’s inherent limitations as a timing source, particularly its non-temperature-compensated oscillator. While effective for small networks, the solution may not scale to enterprise-grade deployments without additional hardening or alternative hardware.

The project underscores the trade-offs between cost, precision, and reliability in timekeeping systems. A Raspberry Pi-based solution offers a low-cost alternative to commercial stratum 1 servers but requires manual tuning to achieve comparable performance. The use of open-source software like Chrony and gpsd lowers barriers to entry, though the setup process involves compiling custom drivers and configuring kernel parameters. For engineers, this serves as a practical example of how to balance modern components with legacy constraints.

Written by elseif from the cluster below · checked for specifics the sources never contained

THE CLUSTER

Same story, 2 feeds.

ORDERED BY FIRST SEEN
Jeff Geerling Rebuilding a 1995 GPS Time Server so I don't get Telstra'd Open ↗
jeffgeerling.com via Hacker News Rebuilding a 1995 GPS Time Server so I don't get Telstra'd Open ↗