[ntp:questions] PPS not recognized in NTP
Victor Andres
victor at cymonline.com
Fri Jul 6 11:37:48 UTC 2012
Thanks Dave, you are correct. The problem was with the header file
timepps.h.
I thought that in recent kernel version (3.x) isn't necessary include or add
any file to the source.
Checking the ntp configuration log I could see that it hasn't presence ...
here the problem.
I've copied the timepps.h (from ppstools) to /usr/include of the kernel
source that I'm going to use in the device.
Now:
#ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
*81.19.96.148 192.36.144.22 2 u 42 64 377 61.341 17.548
8.649
+192.168.2.123 130.206.3.166 2 u 49 64 377 14.596 -1.964
2.156
+130.206.3.166 .GPS. 1 u 56 64 377 37.706 -0.683
18.296
oPPS(0) .pps. 0 l 10 16 377 0.000 -0.004
0.031Thanks again.
Víctor Andrés Andrés
----- Original Message -----
From: "Dave Hart" <hart at ntp.org>
To: "Victor Andres" <victor at cymonline.com>
Cc: <questions at lists.ntp.org>
Sent: Thursday, July 05, 2012 5:19 PM
Subject: Re: [ntp:questions] PPS not recognized in NTP
> On Thu, Jul 5, 2012 at 09:54 UTC, Victor Andres wrote:
>> Once I'm sure the PPS signals are arriving correctly to system, I start
>> to
>> configure NTP.
>> In /etc/ntp.conf, I add the sentencies to use driver 22 ATOM - PPS
>> server 127.127.22.0
>> fudge 127.127.22.0 refid pps
>>
>> but I can't to see the peer listing ntpq -p, and if I run NTP -D1 I can
>> see
>> that it can not reconize it as a valid clock type 22:
>> ...
>> 5 Jul 08:27:48 ntpd[1168]: refclock_newpeer: clock type 22 invalid
>> 5 Jul 08:27:48 ntpd[1168]: 127.127.22.0 interface 127.0.0.1 -> (none)
>> ...
>> I've compiled NTP 4.2.6p5 with --enable-ATOM
>>
>> What could be the problem? perhaps the pps signal configuration?
>
> config.log will tell you for sure, but my guess would be you are
> missing the timepps.h header file that provides Linux PPSAPI.
>
> Cheers,
> Dave Hart
More information about the questions
mailing list