[time-nuts] Measuring Rubidium frequencies
David C. Partridge
david.partridge at dsl.pipex.com
Fri Jun 6 15:41:07 EDT 2008
The 1992 doesn't display the leading 1 when its in when in maximum accuracy
mode. So for 0.0000 read 10.0000 and of course apply the 10**6 multiplier.
From: time-nuts-bounces at febo.com [mailto:time-nuts-bounces at febo.com] On
Behalf Of Adrian
Sent: 06 June 2008 18:10
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Measuring Rubidium frequencies
it might be much easier than you're thinking...
Are you sure the GPDSO's are locked?
Are you sure the rubidium oscillators are locked?
What is the reading of your GPDSO's when you measure them with the internal
counter time base?
I would say that neither 0.00001722 nor 0.00000000 can be correct for a
10.000,000 MHz signal.
Something with your figures appears to be dead wrong, IMO.
Jim Robbins schrieb:
> Hi all,
> I have a problem which I am unable to understand and need some help. I
have two M100 Rubidiums, a Racal 1992 counter, a factory standard T'Bolt and
a Symmetricom Starloc II. When I set up either GPSDO as the External
Timebase for the 1992 and measure either Rubidium, I get the same reading of
9.99998278. When I use the 1992's Internal Timebase, I get 9.99999995. All
equipment has warmed up. The antenna is a Symmetricom HP 58532A on the
roof. On a few occasions I have seen the frequency drift up to
0.00001722. I would have expected that both Rubies would have read
0.00000000. Any ideas would be much appreciated.
> many thanks,
> Jim Robbins
> time-nuts mailing list -- time-nuts at febo.com To unsubscribe, go to
> and follow the instructions there.
time-nuts mailing list -- time-nuts at febo.com To unsubscribe, go to
and follow the instructions there.
More information about the time-nuts