Re: [ntp:questions] Learnings: FC8 Linux ntpd syncs to NMEA message but not PPS

2009-01-30 Thread Rob
phil.new...@wendysarbys.com wrote: > - If you have NMEA output from the GPS in your ntp.conf file > (127.127.20.0), expect it to have "reach 0" reported when you finally get > PPS (127.127.28.0) working. You can have NMEA or PPS from your serial > input, you just can't have both at the same time

Re: [ntp:questions] Learnings: FC8 Linux ntpd syncs to NMEA message but not PPS

2009-01-29 Thread Folkert van Heusden
> > PPS (127.127.28.0) working. You can have NMEA or PPS from your serial > > input, you just can't have both at the same time from the same GPS on the > > same port. > > There is no reason why you could not have both, except that the programs (eg > shmpps) has not been written to use both. It is

Re: [ntp:questions] Learnings: FC8 Linux ntpd syncs to NMEA message but not PPS

2009-01-29 Thread Bill Unruh
On Thu, 29 Jan 2009, phil.new...@wendysarbys.com wrote: > - If you have NMEA output from the GPS in your ntp.conf file > (127.127.20.0), expect it to have "reach 0" reported when you finally get > PPS (127.127.28.0) working. You can have NMEA or PPS from your serial > input, you just can't have b

[ntp:questions] Learnings: FC8 Linux ntpd syncs to NMEA message but not PPS

2009-01-29 Thread Phil . Newlon
I have now managed, with the patient help from Bill U., to get my Linux NTP system running using the PPS signal from a Garmin 18x LVC. I thought I would share what I had to do to make it all work. * References: http://time.qnan.org/ http://time.qnan.org/shmpps.tar http://www.david-taylor.myb