On Fri, Jan 6, 2012 at 9:48 AM, Chris Albertson <[email protected]> wrote: > On Fri, Jan 6, 2012 at 1:32 AM, leap235960 <[email protected]> wrote: >> Le vendredi 6 janvier 2012 04:44:36 UTC+1, Chris Albertson a écrit : >> >>> ntpq> peers >>> remote refid st t when poll reach delay offset >>> jitter >>> ============================================================================== >>> oGPS_ONCORE(0) .GPS. 0 l 14 16 357 0.000 0.004 >>> 377.962 >> >> All your samples show that the GPS PPS was not received in one poll period . >> Did you disturb the cabling? Reach should indicate 377 if there are no >> missing updates. >> Mike >> > Thanks. That is a key bit of information I did not know. I wondered how "reach" could ever not be 377 for a non-networked device.
So not the next problem. I look in "clockstat" file for the word "error" using grep and find many lines that read "ONCORE: oncore_get_timestamp, error serial pps". Not the most informative message. So I look inside the code to see what triggers this. The driver reads the PPS time stamp and noticed that the sequence number was the same as the last time it read the PPS time stamp. Now I have to figure out what would cause the sequence number not to increment. I doubt a pulse was missing. Chris Albertson Redondo Beach, California -- Chris Albertson Redondo Beach, California _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
