Raspberry Pi NTP Time Server Notes

I've been playing with NTP on Raspberry Pi for a few years now and I had a really good system going with a Pi 2B.  Ever since I have switched to a Pi 3 I have had issues with a False Tick on my PPS that I have been chasing keeping me from Stratum 1 glory!

I was puttering with it today and made two changes that are looking positive, so I thought I would share them.

1. https://learn.adafruit.com/adafruit-ultimate-gps-on-the-raspberry-pi/using-uart-instead-of-usb
   I followed these instructions to insure my configuration was optimized to the connection.  The big change was to the config.txt file edit to add enable_uart=1
2. http://www.satsignal.eu/raspberry-pi/Schmidt-RPZ-NTP-2016.pdf
   Updated my ntp.conf to reflect these notes.

My Pi quickly made the GPS the Syspeer!

Looking forward to letting it run for a while to see if PPS comes in.


pi@Telstar2:~ $ ntpq -c peer -c as -c rl


remote refid st t when poll reach delay offset jitter
==============================================================================
1.us.pool.ntp.o .POOL. 16 p - 1024 0 0.000 0.000 0.002
*SHM(0) .GPS. 0 l 3 8 377 0.000 61.197 62.375
xPPS(0) .PPS. 0 l 2 8 377 0.000 -39.896 8.612
172.16.1.255 .BCST. 16 B - 64 0 0.000 0.000 0.002
+time-d-wwv.nist .NIST. 1 u 13 64 377 47.668 -21.062 24.126
+3dgo.net 18.26.4.105 2 u 1047 1024 1 34.263 -3.189 2.058
-tock.no-such-ag 129.6.15.29 2 u 1048 1024 1 42.193 -7.840 1.825
-linode227395.st 192.5.41.41 2 u 3 1024 3 37.624 -38.834 34.088
-ntp2.wiktel.com 212.215.1.157 2 u 1042 1024 1 46.533 -6.673 2.901
-chimera.buffero 139.78.97.128 2 u 1043 1024 1 43.319 -6.320 1.988
#3.time.dbsinet. 209.51.161.238 2 u 5 1024 3 38.411 -4.024 11.058
-c-73-37-183-90. 199.102.46.70 2 u 1043 1024 1 55.524 -4.002 1.507
#soft-sea-01.ser 209.51.161.238 2 u 1035 1024 1 71.671 -14.885 4.472
-ntp.your.org .CDMA. 1 u 1034 1024 1 29.926 -12.408 2.628
-ntp1.wiktel.com .PPS. 1 u 1041 1024 1 43.801 -10.858 3.243

Pi for Echolink on RLC Controller - Part 4 - Read Me First

Pi for Echolink - Part 4

Short update - This did not work.   The Signalink did not provide a needed COR signal to the RLC-3.  Looking at a Rigblaster Plug & Play we can use with some additional wiring.