[time-nuts] GPS module recommendation for Pi timing

[Peter Membrey]

Hi Brian,

We published this back in 2016 but it provides an analysis on the stability of the STC on the first three generations of Raspberry Pi as well as the stability profile of the uBlox M8Q:

https://crin.eng.uts.edu.au/~darryl/Publications/Pi-hat_current.pdf

Hopefully it will give you a starting point if nothing else :)

Kind Regards,

Peter Membrey



----- Original Message -----
From: "Brian Lloyd" <brian at lloyd.aero>
To: "Discussion of precise time and frequency measurement" <time-nuts at lists.febo.com>
Sent: Friday, 13 March, 2020 22:06:07
Subject: [time-nuts] GPS module recommendation for Pi timing

I have an application where I need to synchronize the internal TOD RTC in a
raspberry pi and need to pick a GPS module. We are building our own
hardware but still using the Pi so interconnection will be via GPIO/serial.
We won't try to use USB.

This is not an NTP application. These units will be in the field and will
most likely not have Internet access. I need their clocks to be pretty
close. I am shooting for 1ms ... if possible.

The new M9F and M9T modules from Ublox are a bit pricey. The M8T is a bit
more reasonable. OTOH I realize there are limits to how tightly I can
control the Pi's RTC and will run into diminishing returns, so even the M8T
might be overkill.

Has anyone here figured out what the reasonable limit is for timing on a
Pi, and what makes sense for a timing module for an application like this?

Thanks.

-- 



Brian Lloyd
706 Flightline
Spring Branch, TX 78070
brian at lloyd.aero
+1.210.802-8FLY (1.210.802-8359)
_______________________________________________
time-nuts mailing list -- time-nuts at lists.febo.com
To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com
and follow the instructions there.