David J Taylor via time-nuts writes:
> The graph in ntpviz shows the jitter and temp almost perfectly correlated.
Based on my experience it should really be a correlation of temperature
rate of change vs. jitter. On my self-ovenized servers I see on average
around 200ns jitter (close to the
From: shouldbe q931
Have you considered driving multiple Pi from the same PPS source ? And to
keep their temperature stable, keeping all three in the same enclosure ?
Cheers
Arne
==
Yes, that would be an interesting experiment, Arne, but I don't have the
On Tue, Nov 5, 2019 at 12:03 PM David J Taylor via time-nuts
wrote:
>
> Folks,
>
> As a matter of interest, I've just compared the reported jitter on a RPi 3B,
> RPi 3B+ and RPi-4B, all PPS synced with classic NTP, all in the same room,
> but with slightly different puck antenna locations.
Have
From: Richard Laager
On 11/2/19 1:15 AM, Hal Murray wrote:
rlaa...@wiktel.com said:
I'm curious if this would provide any meaningful improvement in system
clock
accuracy, for NTP, if I'm already a GPS PPS hat. If there's a reasonable
chance this could be interesting, I'm thinking about
stevesommars...@gmail.com said:
> If the bad guys can intercept NTP traffic timestamps can be altered, unless
> NTP authentication is used. [This rarely happens.]
For those not familiar with this area...
There are 2 ways to authenticate NTP packets.
You can setup a shared key. This
> This is a pretty baseless fear. The servers in the ntp pool
> are constantly monitored and those that are off by more than 100ms
> are quickly removed (within 2-3 hours, IIRC).
In computer security it's a big no-no to use unknown or untrusted
sources of information, as simple as that. A random
