On 03-11-2019 12:15, Udo van den Heuvel via devel wrote: > > On 03-11-2019 12:06, Hal Murray wrote: >> >>> We do see pps and nmea but ntpd does not choose the local gps. Why? >> >> How do you "see" them? > > I use `ntpq -pn` to see what the status is. > > >>> NMEA(0) .GPS. 0 l 8 64 377 0.0000 0.0000 0.0019 >> >> I don't understand what's going on. The 377 says it is working, but the >> 0.0000 and 0.0019 say that it isn't working. >> >> Do you have the baud rate correct? > > Yes. > `cat /dev/gps0` shows the NEMA stream. > >> What is in clockstats? > > We have clocklist: > > ntpq> clocklist > associd=0 status=0012 1 event, clk_bad_format, > name="NMEA", > timecode="$GPGGA,111253,5150.2223,N,00457.3970,E,1,08,1.0,-106.4,M,45.5,M,,*6F", > poll=14, noreply=0, badformat=1, baddata=0, fudgetime1=0.0, > fudgetime2=260.0, stratum=0, refid=GPS, flags=5, device="NMEA GPS Clock" > > > Then the 'badformat' is worrying. > What is wrong and how can I fix this? > > Also: when the GPS gives bad data, then why doesn't it use a different > clock as peer?
We furthermore find: Nov 3 11:58:32 bv ntpd[15925]: REFCLOCK: refclock_ppsapi: time_pps_create: Operation not supported Nov 3 11:58:32 bv ntpd[15925]: REFCLOCK: NMEA(0) flag1 1 but PPSAPI fails yet: # grep PPS .config CONFIG_PPS=y # CONFIG_PPS_DEBUG is not set CONFIG_NTP_PPS=y # PPS clients support CONFIG_PPS_CLIENT_KTIMER=m CONFIG_PPS_CLIENT_LDISC=y # CONFIG_PPS_CLIENT_PARPORT is not set # CONFIG_PPS_CLIENT_GPIO is not set # PPS generators support # Udo _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
