On Sun, Jul 30, 2017, at 04:49 AM, Mark Sims wrote:
> It looks like it took three hours for the effects of the rollover glitch
> to mostly settle out.
>
> BTW, if you only use Lady Heather with a Thunderbolt, you can force the
> rollover state from the command line or heather.cfg file by using
It looks like it took three hours for the effects of the rollover glitch to
mostly settle out.
BTW, if you only use Lady Heather with a Thunderbolt, you can force the
rollover state from the command line or heather.cfg file by using the /ro
command line option. If you do that you won't have
Attached is a plot of Thunderbolt data before and after the event. 2 seconds
after rollover the Thunderbolt reported it was re-initializing the loop filter
and 4 seconds after the event it reported is was starting to phase lock the
1PPS. The DAC jumped 0.023V V which is around 75 mHz of
Plus Trimble's usage is rather misleading... you can do true overdetermined
clock in either a static or moving environment... it properly requires more
sats to be tracked than necessary to determine the time. Position hold mode
(and Trimble's overdetermined clock mode) requires a fixed
Hi
> On Mar 6, 2017, at 1:38 AM, Mark Sims wrote:
>
> Does it have a saved/surveyed position? With a saved position you can
> reasonable time performance with 1 sat. Without a saved position all bets
> are off, there is no way for the receiver to determine the
>
On Mon, 6 Mar 2017 00:38:35 +, you wrote:
>Does it have a saved/surveyed position? With a saved position you can
>reasonable time performance with 1 sat. Without a saved position all bets
>are off, there is no way for the receiver to determine the receiver/satellite
>clock difference.
Does it have a saved/surveyed position? With a saved position you can
reasonable time performance with 1 sat. Without a saved position all bets are
off, there is no way for the receiver to determine the receiver/satellite
clock difference.
Trimble reports that the device is in
On Sun, 5 Mar 2017 18:35:25 +0100, you wrote:
>One thing a 6100 will let you do is to calibrate the PPS out of your gizmo
>to +/- 5 ns (one sigma). While its
>not an impressive number by TimeNuts standards, it is one of the few ways to
>get that job done.
I want to eventually characterize
Hi
> On Mar 5, 2017, at 6:31 AM, Trevor N. wrote:
>
> On Sat, 4 Mar 2017 20:39:45 -0800, you wrote:
>
>> Matthias Jelen did a test on the Trimble Thunderbolt here:
>>
>> https://www.febo.com/pipermail/time-nuts/2014-September/086664.html
>>
On Sat, 4 Mar 2017 20:39:45 -0800, you wrote:
>Matthias Jelen did a test on the Trimble Thunderbolt here:
>
>https://www.febo.com/pipermail/time-nuts/2014-September/086664.html
>https://www.febo.com/pipermail/time-nuts/2015-May/091805.html
> I didn't see any reports of anyone (successfully) implementing a test for it.
...
> I obtained all of the receivers the driver currently supports, along with a
> Spirent GSS6100 simulator.
...
Hi Trevor,
Matthias Jelen did a test on the Trimble Thunderbolt here:
Brooke,
FYI: the prior art for that Trimble patent is:
http://leapsecond.com/notes/gpswnro.htm
/tvb
Hi Matthias:
Trimble thought they had come up with a way to account for GPS week rollover,
but the Earth has not cooperated. See:
Leap-second cure for 1999 GPS rollover problem
)*7168, or 50796 + N*7168.
See also the gpsweek tool under http://leapsecond.com/tools/
Sample usage: gpsweek 1980 2100 | grep rollover
/tvb
- Original Message -
From: Mark Sims hol...@hotmail.com
To: time-nuts@febo.com
Sent: Tuesday, September 16, 2014 1:41 PM
Subject: [time-nuts
confirmation.
Thanks,
/tvb
- Original Message -
From: Matthias Jelen matthias.je...@gmx.de
To: Tom Van Baak t...@leapsecond.com; Discussion of precise time and
frequency measurement time-nuts@febo.com
Sent: Tuesday, September 16, 2014 1:52 PM
Subject: Re: [time-nuts] Thunderbolt Rollover
Hi Tom
I don't think you can use a GPS almanac from 2012.
Why not? Just pretend that the time you want is 2012+1024 weeks. You won't
be able to watch it pass through the magic rollover time, but you can verify
that it works correctly once it gets past that magic time.
Crazy question
Hi Matthias:
Trimble thought they had come up with a way to account for GPS week rollover,
but the Earth has not cooperated. See:
Leap-second cure for 1999 GPS rollover problem
https://www.google.com/patents/US5923618
Do you know anything about the Northern Telecom GPS Satellite Simulator
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hello,
I got a Trimble Thunderbolt a few months ago and implemented
a simple monitor on a MCU to display time, no of satellites
etc. on a lcd display.
While working on this, I found the hint for the upcoming
rollover in 2017 in the user manual. I couldn?t find any
details on this in the
into the timestamps for dates after July 2017.
/tvb
- Original Message -
From: Matthias Jelen matthias.je...@gmx.de
To: time-nuts@febo.com
Sent: Tuesday, September 16, 2014 12:06 PM
Subject: [time-nuts] Thunderbolt Rollover
Hello,
I got a Trimble Thunderbolt a few months ago and implemented
Version 4 of Lady Heather(not yet released) has rollover compensation built in.
If the detected date is less than the current system date it adds 1024 weeks
to the Tbolt date/time by default. You can also specify an alternate rollover
offset or disable rollover compensation.
matthias.je...@gmx.de said:
So I took the unit to work and hooked it to a signal generator capable of
simulating GPS, GNSS etc...
Neat. Thanks, both for running the experiment and for sharing the results.
Thunderbolt will be usable after July, 2017 - I?d be happy to live with a
wrong
, and is on the list) to add the 936 week offset
back into the timestamps for dates after July 2017.
/tvb
- Original Message -
From: Matthias Jelen matthias.je...@gmx.de
To: time-nuts@febo.com
Sent: Tuesday, September 16, 2014 12:06 PM
Subject: [time-nuts] Thunderbolt Rollover
Hello,
I
22 matches
Mail list logo