[time-nuts] Trimble Thunderbolt no longer determines the correct date

Bob Bownes bownes at gmail.com
Fri Jul 28 12:34:05 EDT 2017

Forgive my naivete, but if this is something as simple as the t'bolt adding
a 10 bit number to a base date, could not the base date be changed in the
PROM? (Presuming one can get to it, etc) Though I suspect that might not be
all that simple of course. And I'm not taking mine apart to look. :)

On Fri, Jul 28, 2017 at 11:36 AM, Dave B via time-nuts <time-nuts at febo.com>

> Interesting.
> What about NTPD implementations, when using a TB as the reference time
> source?  Does that handle the week count roll over as well?  If that was
> added, from what version?
> I suspect I may have some updating to do!   I use a TB as a frequency
> ref' and local NTP/NTPD server reference.
> The local TB here is showing "week 1959" top left of LH's display window
> (Rev 5.01)
> Cheers.
> Dave G0WBX.
> ------------------------------------------------------------------------
> On 28/07/17 08:14, time-nuts-request at febo.com wrote:
> >> Well quite an unpleasant surprise. So after the 30th do the TBolts stop
> > Paul,
> >
> > This topic has been covered a number of times over the years. Some
> time-nuts have even run TBolt's under GPS simulators to verify that the 10
> MHz and 1PPS outputs will be fine. So apparently the only effect is that
> the date & time (in binary TSIP messages) are off by 1024 weeks. This
> rollover-related effect is by now a "common" issue with many GPS receivers.
> >
> > The current version of Mark's Lady Heather program has code to detect
> this and fix it so you're good to go for the next 19.6 years.
> >
> > /tvb
> _______________________________________________
> 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 mailing list