[ntp:questions] pps breaks when nmea is enabled for ntpd
David Taylor
david-taylor at blueyonder.co.uk.invalid
Mon Jun 17 04:57:45 UTC 2013
On 16/06/2013 20:51, Richard Cagley wrote:
> On Sat, Jun 15, 2013 at 10:17 PM, David Taylor <
> david-taylor at blueyonder.co.uk.invalid> wrote:
>
>> You know the PPS is working because the tally code changes from "*" to "o"
>> in the ntpq -p output:
>
> After 30 min mine doesn't seem to change. If I kill ntpd and run ppstest
> again it fails. It would appear I'm back to my original question. Why does
> starting up the NMEA driver kill the pps line? (output below) I see this on
> startup. Is it significant?
> addto_syslog: refclock_ppsapi: time_pps_create: Operation not supported
>
> / # ntpq -p
> remote refid st t when poll reach delay offset
> jitter
> ==============================================================================
> *GPS_NMEA(0) .gPPS. 0 l 1 16 377 0.000 -5.956
> 2.752
Sorry, Richard, but I don't know why this should be. I'm not too
familiar with Linux systems, so I hope someone else may be able to help.
--
Cheers,
David
Web: http://www.satsignal.eu
More information about the questions
mailing list