>> Notes on the system config, and links to the ntp.conf are on those pages.
> GPS; GlobalSat MR-350P
Are all the PPS pulses getting through? The MR-350P has a very narrow pulse.
If you don't have a pulse stretcher, you can easily get enough pulses to
make it look like it is working while not
Yo Hal!
On Wed, 21 Sep 2016 19:24:31 -0700
Hal Murray wrote:
> Nice work. Thanks.
I wish it brought more clarity...
> Would you please remind us about what the PPS setups on those systems
> are. (I think you said the Xeon has a USB setup.)
https://pi3.rellim.com/day/
https://rellim.com/ntpst
Nice work. Thanks.
Would you please remind us about what the PPS setups on those systems are.
(I think you said the Xeon has a USB setup.)
And what do the column headings really mean?
Do you have a recipe for generating that data? I expect it comes from
ntpviz, but what do I type? Is ther
Yo All!
New data for poll=7 (128 Sec). Like before, all data is 90% bounds,
run over 24 hours or more. poll=8 up next.
Xeon:
Local Clock Local Clock Local ClockPPS PPS
Poll Freq Offset 90% Jitter 90% Stability 90% Offset 90% Jitter 90%
1 495ppb
Yo Hal!
On Wed, 21 Sep 2016 10:48:04 -0700
Hal Murray wrote:
> I worked out a (much) more complicated fix. I'll happily dump it if
> yours works.
I have nothing yet. Just a start of a patch, pushed a tiny bit last night.
> When I was testing things, ntpq showd a poll of 1, but clockstats was
I worked out a (much) more complicated fix. I'll happily dump it if yours
works.
When I was testing things, ntpq showd a poll of 1, but clockstats was acting
like it was 2. So there are 2 options for what "works" means.
--
These are my opinions. I hate spam.
