[LinuxPPS] Why is my ATOM clock a falseticker?

[Paul Simons]

Oops, here is the relevant section: 

server 127.127.22.1 minpoll 4 maxpoll 4 # ATOM (PPS)
fudge 127.127.22.1 flag2 1              # Use the "clear" edge of the signal 

# "PPS pulses are usually short, and the leading edge is the on-time mark,
# so by looking at the time of two adjacent edges with cat /sys/class/pps/pps1/{assert,clear},
# you can see which one leads the other." 

server 127.127.5.0 prefer               # TrueTime clock
#No fudge 

On 01/30/2009, "Cirilo Bernardo" stated:

> On Sat, Jan 31, 2009 at 3:42 AM, Paul Simons <paul at thesimonet.org> wrote:
>> First, this list is great.  Thank you for your conversation and willingness
>> to share.  I took my Truetime 486-DC to a hardware type and he hooked a
>> oscilloscope to the pps and declared it a decent RS232 signal (0/+5v,
>> 200ms).  I stopped playing with the parallel port and wired it directly to
>> the serial port.  I applied Folkert's patch to ppsldisc.  I downloaded and
>> built the latest NTP (4.2.5p157) with the right timex.h and against librt:
>>
> [snip]
>
> Did you use the "prefer" keyword? What does your ntp config file look like?
>
> - Cirilo
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ml.enneenne.com/pipermail/linuxpps/attachments/20090130/82709a31/attachment.htm