On Friday 26 October 2007, Simon Arlott wrote: > On 26/10/07 21:23, Chuck wrote: > > hmm... this is what i have so far from messing around. this keeps the offset > > for the gps clock in reasonable range or else it is skewed off by 230ms or so > > and there is always an X by it. i suppose it doesnt matter since the pulse > > (gps1) is always * and is usually within 100 us at worst, 5us at best. > > > > there seems to be a considerable change from poll to poll. it never settles > > down into a nice small range hardly varying as i expected it to do. > > > > server 127.127.28.0 minpoll 4 maxpoll 4 > > fudge 127.127.28.0 time1 -0.200 refid GPS > > > > server 127.127.28.1 minpoll 4 maxpoll 4 prefer > > fudge 127.127.28.1 refid GPS1 > > Only the PPS signal is timed to the start of the second. The NMEA data is not. > When there's no fix the PPS signal will be (relatively) ok, but the time output > can be out of sync. Either combine the NMEA output with the PPS signal or only > use PPS. >
so there is no reason to use the .0? i just followed the instructions on a webpage :) > -- > Simon Arlott > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
