[time-nuts] Trimble Thunderbolt no longer determines the correct date
paulswedb at gmail.com
Thu Jul 27 20:36:08 EDT 2017
Well quite an unpleasant surprise. So after the 30th do the TBolts stop
working or is it a case of just the wrong date? I know my Hp3801s been
working just fine and its old. Is the TBolt the same issue. Wrong date but
still locks thats all I care about actually.
With to respect of some sort of a hack I can see that being fairly
On Thu, Jul 27, 2017 at 8:01 PM, Attila Kinali <attila at kinali.ch> wrote:
> On Thu, 27 Jul 2017 17:49:14 -0500
> Didier Juges <shalimr9 at gmail.com> wrote:
> > I cannot imagine a work around since the problem stems from the GPS
> > only identifying the current date within a particular 1024 weeks epoch
> > unless the government changes the amount of data that is sent over the
> > system. Somebody has to use other method to determine the epoch and add
> > corresponding offset.
> There is: There is a 13bit week number in message type 10. This gives
> a 157 year span instead of the ~19 years of the 10bit week number.
> This has been part of the GPS standard since IS-GPS-200D which was
> released in 2004. As such I am a little bit surprised that the u-blox
> receivers still don't support this message (the LEA-5 family was released
> in 2007 IIRC). But you can use the UBX RXM-SFRBX messages to get the
> raw GPS messages and decode them yourself.
> Attila Kinali
> You know, the very powerful and the very stupid have one thing in common.
> They don't alters their views to fit the facts, they alter the facts to
> fit the views, which can be uncomfortable if you happen to be one of the
> facts that needs altering. -- The Doctor
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> and follow the instructions there.
More information about the time-nuts