[ntp:questions] nmea stopped working all of a sudden

Hal Murray hal-usenet at ip-64-139-1-69.sjc.megapath.net
Fri Aug 22 18:14:15 UTC 2008


>That worked out of the box and all of a sudden just stopped.
> Since I changed a lot of things in order to make the box work
> fully-automatic, I can't say for sure if I broke something
> or what happened.. Still I am very puzzled...

>Maybe I overlooked something?

>Here's some information:

>Here's my ntp.conf:-------------------------------
>driftfile /var/opt/ntp.drift
>
># NMEA GPS driver for u-blox receiver
>server 127.127.20.0 prefer #minpoll 4
>fudge 127.127.20.0 flag3 0
>#fudge 127.127.20.0 flag3 0 flag2 0 time1 0.124


>And here what I get with it:
>
>     remote           refid      st t when poll reach   delay   offset  jitter>==============================================================================> GPS_NMEA(0)     .GPS.            0 l    -   64    0    0.000    0.000   0.001

The 0 under reach says you aren't getting any data from that system.


>nmea: gpsread 72 $GPGGA,151022.00,5225.83871,N,01316.84595,E,1,07,0.99,39.8,M,44.9,M,,*60

That says the unit is working and providing GPGGA info.  The 1 after the E
says it thinks the data is valid.  (aka it is hearing enough satellites)

Go back up and look at the config file.  The default for the NMEA driver
is to expect GPRMC sentences.  So you should either fix your unit to
send them (and not waste time with the GPGGA stuff) or fix your config
file to use the GPGGA sentences.  I think that takes a mode subcommand.

-- 
These are my opinions, not necessarily my employer's.  I hate spam.




More information about the questions mailing list