diff options
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 22 |
1 files changed, 11 insertions, 11 deletions
@@ -93,27 +93,27 @@ packet-cracking needed to get the data off the chips. We have an RTCM packet decoder. Here's the plan for the rest of it: -1) Add code to packet.c that can recognize RTCM104 data packets. This - would be the hard part -- that format is *nasty*. +1) Finish the packet.c code that recognizes RTCM104 data packets. + When that's done we'll have RTCM104 sessions integrated into the + gpsd architecture; we can hand RTCM104 sources like DGPS radios to + gpsd on the command line or via the control socket, just like + GPSes. -2) Write a trivial RTCM104 driver that just copies recognized packets - into a save buffer. Now we have RTCM104 sessions integrated into - the gpsd architecture; we can hand RTCM104 sources like DGPS radios - to gpsd on the command line or via the control socket, just like GPSes. - -3) Arrange for packets from any attached RTCM104 sessions to get +2) Arrange for packets from any attached RTCM104 sessions to get automatically copied from their save buffers to any GPSes attached. -4) When there are attached RTCM104 sources, tell the daemon to serve +3) When there are attached RTCM104 sources, tell the daemon to serve these packets on port 2101. At this point we will have replaced - dgpsip's server function, through not yet its RTCM dumper function. + dgpsip's server function. -5) Get rid of the -d option by hacking open_device() so that when it +4) Get rid of the -d option by hacking open_device() so that when it sees a command-line option of the form server:port (with no embedded backslashes) it opens a socket to read from that server. Now any GPS-packet and RTCM data sources given on the command line can be remote as well as local. +5) Make RTCM encoding work with an 'invert' option to rtcmdecode. + *** Do the research to figure out just what is going on with status bits NMEA actually has *four* kinds of validity bits: Mode, Status, the |