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

Dave B g8kbvdave at googlemail.com
Fri Jul 28 11:36:47 EDT 2017


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)


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

More information about the time-nuts mailing list