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

[Didier Juges]

Since the Thunderbolt is hard coded to detect a particular week to
determine if it should add 1024 to the week number, I would guess that each
product has a magic date based on the anticipated release date of the
product (week 936 for the Thunderbolt), and it will work for 1024 weeks
from that date.

I cannot imagine a work around since the problem stems from the GPS service
only identifying the current date within a particular 1024 weeks epoch
unless the government changes the amount of data that is sent over the GPS
system. Somebody has to use other method to determine the epoch and add the
corresponding offset.



On Thu, Jul 27, 2017 at 12:36 PM, Keith Loiselle <keith.loiselle at gmail.com>
wrote:

> Hi,
>
> It came to our attention at Jackson Labs that the Trimble Thunderbolt will
> fail to start with the correct date after July 30, 2017.   See the clip
> from the Thunderbolt manual below.
>
> Does anyone have any updates from Trimble regarding fixes for this
> problem?  Does does this affect other Trimble products (i.e. Mini-T,
> Resolution T) in the same way?
>
> [image: Inline image 1]
>
> Please note that Jackson Labs products are not affected by the up-coming
> April 2019 GPS week roll over, and can determine the correct date until the
> following dates:
>
>
>
>    uBlox-8 based products - 4/24/2033
>
>    uBlox-6 based products - 5/12/2030
>
>    Legacy uBlox-5 based products - 12/3/2028
>
> Thanks,
> Keith
>
> _______________________________________________
> 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.
>