Switch out the X1 Oscillator on a RPI 2/3

Question

Just like a lot of people I'm using a RPi as a NTP server (more info about the basic setup here: https://framkant.org/2017/03/stratum-1-ntp-server-with-freebsd-on-raspberry-pi/)

I have found that the stability is really bad and it's especially sensitive to temperature changes. Even me walking out the door in the morning changes the indoor temperature enough to affect the timekeeping.

In order to resolve this I would like to change the X1 oscillator to something more stable like a TCXO or OCXO. But I not really sure what I need to know/think about before doing this.

• Do I need a special type of oscillator other than one with the correct frequency?
• How hard would it actually be to replace the part? (soldering and so on)
• Is the X1 actually the part I want to replace?

Edit:

For reference, here is a graph of the timekeeping today with a spike from me making dinner in a room approx 10m away. :D (The scale is microseconds (milli*milli))

Answer 1

All RPi boards use standalone quartz crystals, not external oscillators. It's impossible to replace a crystal by an oscillator without some redesign of the schematic, and it will be very hard to do on an already populated PCB.

Check out the datasheet you've found: the IQXT-260 oscillator has 4 or 6 pins depending on the package. The X1 part on the RPi has only two pins.

Answer 2

1. You'll need one with exactly the same circuit characteristics as the stock XO.

2. If you're skilled with a hot-air rework station, and have all the right tools and equipment, it's not too hard. It's virtually impossible if you don't, though.

3. Likely not. NTP is designed to work around variable system clocks through network consensus, so changing the XO won't give you much. Using a GPS's PPS signal effectively gives you a GPS/Multi-GNSS Disciplined Oscillator, so as long as you have skyview, you've got atomic clock accuracy even without a network. If you don't have skyview or network, it wouldn't be impossible to piece something together based on a used rubidium frequency standard — but even the cheapest of those have fearsome power requirements and are far from plug-and-play.

Answer 3

This is a not a very fruitful idea, for several reasons.

The clock circuit on an embedded device like the PI is not designed for accuracy or stability, there are more elements than the XO that will affect jitter and drift.

1. Stability and drift in the Phase-Locked Loop (PLL) inside the Broadcom CPU which generates the core clock
2. Temperature Drift in XO resonance circuit
3. Temeperature drift in the latching/clocking threshold detection circuits.
4. etc. etc.

Additionally, Any hand rework, even with good equipment, runs the risk of wiping out any improvement from a better spec'd oscillator. They are very sensitive parts.

The improvement in temperature stability switching to a different XO in the same package is marginal, you are buying better tolerance and matching characteristics that reduce clock drift and temperature dependence for the device class, but physically speaking all crystals will expand/contract with temperature changes and all will experience clock drift, very hard to compensate for this.

In the end its unnecessary, if you want to run an NTP node it will work regardless, if you want to function as a (local) time standard you will need to interface external equipment, Like a GPS, thermally stable clock, cesium clock, etc...

However, If you want to experiment with stabilizing the on-board oscillator this I would suggest and alternative approach

---

OCXO

Clock references in precise equipment are usually in a constant temperature oven, and require some time to stabilize. These "ovens" provide a constant temperature (not necessarily HOT), usually controlled by a Peltier Element

These devices are known as Oven Controlled Crystal Oscillator (OCXO). Unfortunately they require a significant change to the circuitry and are not drop in replacements.

They Look like This:

To experiment, you could replicate some of the stability of an OCXO by putting a Thermo-Electric Cooler (TEC aka Peltier Element) to keep the XO and the broadcom CPU at a constant temperature.

In other words, eliminate the temperature issue by keeping the Raspberry PI at constant temperature.

Answer 4

I agree that the Raspberrypi crystal is the weak point in a pi based ntp server. Your idea is interesting but you are very far from bringing the best out of the raspberrypi/GPS combo. With the unmodified Raspberrypi and PPS (not kernel pps) it is possible to get offsets of +-3 us peak, offset standard deviation (RMS) less than 1 us, jitter 2 us given a poll time of 16 s which is the suggested polling rate. And my pi crystal is constantly 7 ppm off! Your polling time seems to be much higher given your curve with many visible steps. I attach some graphs to illustrate what's possible now.

Answer 5

Although not a direct answer to your question, http://www.osengr.org/Projects/NTP-Server/NTP-Server.shtml with the "advanced" variant may give you an idea on what is needed for such a setup. Considered there is already an TCXO in your GPS module there is no need adding another one on the microprocessor. The Raspberrypi has other components placed very closely to the crystal. I would sure damage something trying to solder in this area.