join
donate

Lose the per-driver PPS code

What StatusSorted ascending
arbiter (seems OK)
as2201 (seems OK)
hpgps (seems OK)
Master bug_small.png Bug #557
parse bug_small.png Bug #558
oncore bug_small.png Bug #559
jupiter bug_small.png Bug #560
msfees bug_small.png Bug #561
mx4200 bug_small.png Bug #562
nmea bug_small.png Bug #563
ripencc bug_small.png Bug #564
trak bug_small.png Bug #565
true bug_small.png Bug #566
zyfer bug_small.png Bug #567

Dave wants to lose the per-driver PPS code and let the ATOM driver handle it all.

Let's use this topic to discuss issues about this set of bugs.

IDEA! The original topic name (LoseThePer-driverPPSCode) was not a WikiName (which interferes with the automatic link creation). I've moved the content here and changed the original topic to be a redirect. -- SteveKostecke



Harlan: Do the remarks "seems OK" mean - OK as they do not use any of the PPSAPI?

-- FrankKardel - 01 Feb 2006


Yes, it means that I did a grep PPS refclock*.c and the ones marked "seems OK" only discussed PPS in their comments.

-- HarlanStenn - 01 Feb 2006



The thing is that the refclock drivers know exactly whether the PPS of the device they are controlling is valid by the information from the device itself.

ATOM/PPS must use PPS derived time stamps only when the clock is doing well. ATOM/PPS has currently no way whatsoever to know about the health state of PPS (I currently see a 500ppm frequency check) - it assumes that PPS is always valid when it is there.

We have seen refclock/network scenarios where knowing whether PPS is healthy was absolutely crucial (effect: oscillating clock setting of several 100ms).

The scenario was invalid PPS information from a PPS source and valid time time information from the network.

For ATOM/PPS we would need an interface where the PPS health information is available to ATOM/PPS.

Currently this task is managed in the refclock drivers (some better, some worse).

-- FrankKardel - 01 Feb 2006


It would be nice to have ntpq display the appropriate peer tally code depending on the health of PPS for ATOMized drivers

-- SteveKostecke - 01 FEb 2006



This topic: Dev > WebHome > LoseThePerDriverPPSCode
Topic revision: r6 - 2006-02-01 - 16:56:49 - SteveKostecke
 
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback