diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2010-04-01 10:34:33 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2010-04-01 10:34:33 -0400 |
| commit | bf38d5265021d0f88ab5e9f5793985b5881f510f (patch) | |
| tree | d1badb48e802d54b672301f8afbe82adeff6802b /TODO | |
| parent | ac0d3b83d717f5f2b038b2ddf431e9fe3bbfa7fe (diff) | |
| download | gpsd-bf38d5265021d0f88ab5e9f5793985b5881f510f.tar.gz | |
Add report of time reference instability on loss of fix.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -22,6 +22,16 @@ fix the driver yourself and send us the patch, contact Bill Powell <bpowell@tntc.com> at True North Technologies and tell him he needs to reverse his refusal to send us an eval unit. +*** time reference instability on loss of fix + +[23:14] <agcme> I've discovered when the gpsd feed to ntpd goes crazy +[23:14] <agcme> it happens when the GPS receiver loses the fix +[23:15] <agcme> these errors start popping up: gpsd: PPS ntpshm_pps: no current GPS seconds: 1247359355 +[23:17] <agcme> It did it several times but most of the time when the fix came back everything went back to normal. However, at some point regaining a fix does not restore the ntpd shm data and it stays completely lost. +[23:18] <agcme> Right now ntpd says the PPS offset is currently -12885008 seconds +[23:19] <agcme> The NMEA offset is only -129.3 seconds +[23:20] <agcme> The receiver has a fix on six satellites right now + *** Driver issues **** gpsctl -b should work on UBX, but does not. |