[time-nuts] thunderbolt for ntpd or gpsd

Scott Mace smace at intt.net
Sun Aug 10 20:42:02 UTC 2008


ntpshm_put() needs to be called in the 0xab case as well for ntp to work.

	Scott

--- gpsd/trunk/tsip.c   2008-08-08 23:38:27.000000000 -0500
+++ ../gpsd/trunk/tsip.c        2008-08-09 04:14:09.000000000 -0500
@@ -65,7 +65,7 @@
         /* XXX clever heuristic to decide if the parity change is required. */
         session->driver.tsip.parity = session->gpsdata.parity;
         session->driver.tsip.stopbits = session->gpsdata.stopbits;
-       gpsd_set_speed(session, session->gpsdata.baudrate, 'O', 1);
+       gpsd_set_speed(session, session->gpsdata.baudrate, 'N', 1);
         break;

      case 1:
@@ -674,6 +674,10 @@

             session->gpsdata.fix.time =  session->gpsdata.sentence_time =
               gpstime_to_unix((int)s1, f1) - (double)u1;
+#ifdef NTPSHM_ENABLE
+           if (session->context->enable_ntpshm)
+               (void)ntpshm_put(session,session->gpsdata.sentence_time+0.075);
+#endif
             mask |= TIME_SET;
           }


Wayne Knowles wrote:
> Tim, Chris,
> 
> Over a month ago I experimented with getting GPSD and the Tunderbolt working 
> together.
> I quickly added support for the missing TSIP packet types, and was able to get 
> xgps to display lat, long, time  and constellation status.   I did manage to 
> get NTP to work, have not invested the time into getting the 1PPS signal 
> working under FreeBSD yet.
> 
> I have attached my patches against the gpsd source repository.   Note that I 
> did not invest much time understanding the internals of gpsd beforehand so 
> some aspects may not be fully implemented.
> 
> --
> Wayne ZL2BKC
> 
> 
> On Fri, Jun 13, 2008 at 8:58 AM, Christian Vogel <vogelchr at vogel.cx> wrote:
>> gpsd: GPS Time 485697.250000 1483 14.000000
> that's encouraging
> 
>> gpsd: Sat info: mode 1, satellites used 5:  18 9 28 15 26
> As is this.
> 
>> gpsd: Unhandled TSIP superpacket type 0xab
> 
> "thar's yer problem"...  kinda.
> 
> yes, we don't handle 0xAB, but that's just timing information. I see
> no indication that the receiver is outputting position reports. I
> should have this sorted a few hours after my Thunderbolt arrives.
> Guess I need to prod the receiver into telling me where it thinks it
> is.
> 
>> Unfortunately, it does not show any information about time or position on
>> a connected cgps/xgps client.
>>
>>        Chris
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts at febo.com
>> To unsubscribe, go to 
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.




More information about the Time-nuts_lists.febo.com mailing list