On 05/02/2012 03:50 AM, Dennis Ferguson wrote:
On 2 May, 2012, at 04:30 , Tom Van Baak wrote:
The UTC offset is in words 6-10, page 18, subframe 4 -- every 12.5 minutes.
/tvb
The leap second warning is also in the same place. How the unit could
know that a leap second is pending but not
In my opinion nothing has to be changed. It is working OK this way. To
improve performance it is worth to use linear regulators for the power
supply +12V and -12V that are related to the OCXO supply and EFC.
On Wed, May 2, 2012 at 9:24 AM, francesco messineo
francesco.messi...@gmail.com wrote:
I think the tbolt may need to go through two 12.5 minute almanac cycles before
it updates/outputs all its data...
The first thing to do to improve performance is to run the a oscillator
autotune command. This will determine the correct osc gain and initial DAC
settings. It will also set the
time and frequency measurement
time-nuts@febo.com
Reply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] thunderbolt no UTC offset
francesco.messi...@gmail.com said:
I just powered on again my trimble thunderbolt after some time
Hi all,
I just powered on again my trimble thunderbolt after some time without antenna.
All alarms are green but the obvious leap second pending. BUT: I can't
use UTC time as both tboltmon and lady heather display a No UTC
offset message. I don't remember having seen this in the past. What's
francesco.messi...@gmail.com said:
I just powered on again my trimble thunderbolt after some time without
antenna. All alarms are green but the obvious leap second pending. BUT: I
can't use UTC time as both tboltmon and lady heather display a No UTC
offset message. I don't remember having
Hi Hal,
On 5/1/12, Hal Murray hmur...@megapathdsl.net wrote:
francesco.messi...@gmail.com said:
I just powered on again my trimble thunderbolt after some time without
antenna. All alarms are green but the obvious leap second pending. BUT: I
can't use UTC time as both tboltmon and lady
Incorrect, the UTC offset should be sent in the Almanac, the Almanac
having a period of 12.5 minutes max. Not one hour. It should take no more than
12.5 minutes to get the UTC offset when sats are properly being received.
bye,
Said
In a message dated 5/1/2012 11:45:06 Pacific Daylight
On 5/1/12, saidj...@aol.com saidj...@aol.com wrote:
Incorrect, the UTC offset should be sent in the Almanac, the Almanac
having a period of 12.5 minutes max. Not one hour. It should take no more
than
12.5 minutes to get the UTC offset when sats are properly being received.
when I posted my
: Tue, 01 May 2012 11:41:22
To: Discussion of precise time and frequency measurementtime-nuts@febo.com
Reply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] thunderbolt no UTC offset
francesco.messi...@gmail.com said:
I just powered
The UTC offset is in words 6-10, page 18, subframe 4 -- every 12.5 minutes.
/tvb
___
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.
On 05/01/2012 10:30 PM, Tom Van Baak wrote:
The UTC offset is in words 6-10, page 18, subframe 4 -- every 12.5 minutes.
It was added to the broadcast signal as an after-thought, as a separate
upgrade package if you wish. At least back then, I believe they had USNO
to measure the GPS time and
On 2 May, 2012, at 04:30 , Tom Van Baak wrote:
The UTC offset is in words 6-10, page 18, subframe 4 -- every 12.5 minutes.
/tvb
The leap second warning is also in the same place. How the unit could
know that a leap second is pending but not know the UTC offset is a
mystery.
Dennis Ferguson
13 matches
Mail list logo
