Re: [ntp:questions] Palisade Reference Clock

2010-09-01 Thread Chris H
If I do this while running ntpd while true = '1'; do echo " " > /dev/ttyS0 sleep 10; done I get: addto_syslog: select(): nfound=-1, error: Interrupted system call addto_syslog: select(): nfound=-1, error: Interrupted system call addto_syslog: select(): nfound=-1, error: Interrupted system call a

Re: [ntp:questions] Palisade Reference Clock

2010-09-01 Thread Marc Leclerc
Have you looked at both firmware docs to insure that there is no changes in the packet data. I had to play with this driver to talk to a resolution SMT and just a few changes in bits definition gave me the same error. the driver will fail even if the error is from another packet (secondary ti

Re: [ntp:questions] Palisade Reference Clock

2010-09-01 Thread Chris H
I think I was too excited too soon. First packet appeared, subsequent packets failed :) On Wed, 2010-09-01 at 19:14 +1200, Chris H wrote: > https://support.ntp.org/bugs/show_bug.cgi?id=1075 > > Appears to have fixed the problem.. > > The PPS Width is too small, and this patch / bug report,

Re: [ntp:questions] Palisade Reference Clock

2010-09-01 Thread Chris H
https://support.ntp.org/bugs/show_bug.cgi?id=1075 Appears to have fixed the problem.. The PPS Width is too small, and this patch / bug report, fixes the issue :) On Tue, 2010-08-31 at 11:34 +0100, George Ross wrote: > > > Have you tried running the daemon in debugging mode, per the > > > dri

Re: [ntp:questions] Palisade Reference Clock

2010-08-31 Thread George Ross
> > Have you tried running the daemon in debugging mode, per the driver29.html > > page? What does that say? We found that quite useful on the one occasion > > where we had any problem with our unit. > > I still get clk_noreply... :( You should see the driver logging what it's doing though, w

Re: [ntp:questions] Palisade Reference Clock

2010-08-31 Thread Chris H
> We have an Acutime 2000, which has pretty much just worked since we bought > it in 2005. We haven't felt the urge to do anything to the firmware, and > I've no idea what it's running -- whatever was current at the time. Just looking at the bug fixes between 7.02 and 7.12, I thought it was a g

Re: [ntp:questions] Palisade Reference Clock

2010-08-30 Thread George Ross
> I am new to Reference Clocks, and I am just simply stumped now. > > I have a Palisade smart antenna, with firmware version 7.12 (I did an > upgrade from the Trimble website). > Previous to this I had 7.10, and it worked correctly, my model number is > 26664-10 so I am able to have event trigger.

[ntp:questions] Palisade Reference Clock

2010-08-30 Thread Chris H
Hello group. I am new to Reference Clocks, and I am just simply stumped now. I have a Palisade smart antenna, with firmware version 7.12 (I did an upgrade from the Trimble website). Previous to this I had 7.10, and it worked correctly, my model number is 26664-10 so I am able to have event trigge