summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2013-11-12 22:03:55 -0500
committerEric S. Raymond <esr@thyrsus.com>2013-11-12 22:03:55 -0500
commit7e56b10ee95dcaa8c6fba17fd276724159c4f003 (patch)
treefe872bbb90c68883045ced02e01725dce11016b0 /TODO
parente1425dc4ee2d7a5e5a985b792c37b273a2056e87 (diff)
downloadgpsd-7e56b10ee95dcaa8c6fba17fd276724159c4f003.tar.gz
Update the TODO list.
Our notions about a time-service mode aren't really well-formed enough to be a TO-DO item yet.
Diffstat (limited to 'TODO')
-rw-r--r--TODO26
1 files changed, 21 insertions, 5 deletions
diff --git a/TODO b/TODO
index 83dde991..2a8128b6 100644
--- a/TODO
+++ b/TODO
@@ -27,6 +27,27 @@ Presently PPS Offset is displayed in direct mode for NMEA, SiRF, and
UBX devices. Others should probably do likewise, notably the
Motorola Oncore and Garmin drivers.
+**** gpsmon driver switching and blocking on error
+
+Hal Murray reports:
+
+ If I run .gpsmon /dev/ttyUSB0
+
+ It starts up in NMEA0183 mode as I expect.
+ "i" switches to SiRF, again, as I expect.
+
+ "n" switches the display to NMEA layout, but the header still says SiRF.
+ Another "n" now says: Device type has no mode switcher.
+ At this point, "i" doesn't do anything. (no pause either)
+
+The second 'n' is losing information that it shouldn't.
+
+ If I start over and feed it an "f", it starts blinking "Unknown command "f"
+ The logging and display update stops. After I type another character, it
+ clears the blinking error message and stars logging/updating again.
+
+Display update should not stop while this is going on.
+
*** Dispatcher/network issues
**** Reading AISHub data via UDP confuses xgps with short writes
@@ -37,11 +58,6 @@ packet aggregation issue as it doesn't happen with test logs.
*** Driver issues
-*** Add a method for presetting time and enabling/disabing time service mode
-
-We could implement this right away on the u-blox 6. Zodiac and Delorme
-devices could use it too.
-
**** RTCM3 analysis is incomplete
We can presently decode RTCM3 messages of type 1001-1014, 1029, and