[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gpsd-commit-watch
Subject:    [Gpsd-commit-watch] r5588 - in trunk: . www
From:       esr at BerliOS <esr () mail ! berlios ! de>
Date:       2009-05-27 7:47:20
Message-ID: 200905270747.n4R7lKxa016949 () sheep ! berlios ! de
[Download RAW message or body]

Author: esr
Date: 2009-05-27 09:47:19 +0200 (Wed, 27 May 2009)
New Revision: 5588

Modified:
   trunk/driver_aivdm.c
   trunk/www/AIVDM.txt
Log:
Teach the AIVDM driver to handlw message type 11.


Modified: trunk/driver_aivdm.c
===================================================================
--- trunk/driver_aivdm.c	2009-05-27 07:19:47 UTC (rev 5587)
+++ trunk/driver_aivdm.c	2009-05-27 07:47:19 UTC (rev 5588)
@@ -2,6 +2,8 @@
  * Driver for AIS/AIVDM messages.
  *
  * See the file AIVDM.txt on the GPSD website for documentation and references.
+ *
+ * Decoding of message type 11 has not yet been tested against known-good data.
  */
 #include <sys/types.h>
 #include <stdio.h>
@@ -168,7 +170,8 @@
 			ais->type123.heading, 
 			ais->type123.utc_second);
 	    break;
-	case 4:	/* Base Station Report */
+	case 4: 	/* Base Station Report */
+	case 11:	/* UTC/Date Response */
 	    ais->type4.year = UBITS(38, 14);
 	    ais->type4.month = UBITS(52, 4);
 	    ais->type4.day = UBITS(56, 5);
@@ -585,6 +588,7 @@
 #undef TYPE123_SCALED_LABELED
 	break;
     case 4:	/* Base Station Report */
+    case 11:	/* UTC/Date Response */
 #define TYPE4_UNSCALED_UNLABELED \
"%04u:%02u:%02uT%02u:%02u:%02uZ,%u,%d,%d,%u,%u,%x\n"  #define TYPE4_UNSCALED_LABELED \
"%4u:%02u:%02uT%02u:%02u:%02uZ,q=%u,lon=%d,lat=%d,epfd=%u,sp=%u,radio=%x\n"  #define \
TYPE4_SCALED_UNLABELED	"%4u:%02u:%02uT%02u:%02u:%02uZ,%u,%.4f,%.4f,%s,%u,%x\n"

Modified: trunk/www/AIVDM.txt
===================================================================
--- trunk/www/AIVDM.txt	2009-05-27 07:19:47 UTC (rev 5587)
+++ trunk/www/AIVDM.txt	2009-05-27 07:47:19 UTC (rev 5588)
@@ -338,7 +338,7 @@
 for the ship's radio(s).  The first three digits convey information
 about the country in which the ID was issued <<ITU-MID>>.
 
-Detailed descriptions of message types 1-9, 12-14, and 18-19 follow.
+Detailed descriptions of message types 1-9, 11-14, and 18-19 follow.
 Information sufficient to decode other message types in the range 1-22
 can be found in <<IALA>>, but they are rare or not of general interest
 so we will not duplicate the information here. Message types 23-24 are
@@ -740,6 +740,10 @@
 are even at the same bit offsets.  Time stamp has the same special
 values as in the common navigation block, but is at a different offset.
 
+=== Type 11: UTC/Date Response ===
+
+Identical to message 4, with the semantics of a response to inquiry.
+
 === Type 12: Safety-Related Message ===
 
 This is a point-to-point text message.  The payload is interpreted as
@@ -816,6 +820,10 @@
 common navigation block.  Note that until just before the reserved field
 at bit 139 this is identical to message 18.  312 bits.
 
+In practice, the information in the ship name and dimension fields is
+not reliable, as it has to be hand-entered by humans rather than
+gathered automatically from sensors.
+
 `--------`---`------------------------`-----------------------------------------
 Field   Len Description                       Units
 --------------------------------------------------------------------------------

_______________________________________________
Gpsd-commit-watch mailing list
Gpsd-commit-watch@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/gpsd-commit-watch


[prev in list] [next in list] [prev in thread] [next in thread]