[time-nuts] Fury - Rubidium

Scott Mace smace at intt.net
Thu Jul 29 01:20:24 UTC 2010


After about 19hours of holdover, only ~45ns.  Now let's see how well it 
recovers.

	Scott

On 07/28/2010 01:02 AM, SAIDJACK at aol.com wrote:
> Hi Scott,
>
> a cool thing to try is to put the unit into manual holdover by issuing  the
> command
>
>     sync:holdover:init
>
> The unit will act as if the GPS antenna has been removed, but GPSCon will
> continue to show the 1PPS phase drift against GPS. Thus you can see how
> stable  your LPRO is over time when the unit is in holdover.
>
> You can restart normal locking with the command
>
>     sync:holdover:rec:init
>
> On a good DOCXO, we would see less than 2000ns drift over a day when the
> unit has been stable for a week or so. I believe the limits of the time
> interval  display are about +/- 2000ns.
>
> bye,
> Said
>
>
> In a message dated 7/27/2010 08:42:01 Pacific Daylight Time, smace at intt.net
>   writes:
>
> I test  it by changing the antenna delay.  It should recover within a
> reasonable time.  Bumping the coarsedac is typically too much change  and
> takes longer to recover.  I run it with a 20ns offset to my  z3801a, and
> they always stay within 20ns of other.
>
> I've had the  Fury running for about 5400 hours since the last reboot,
> running v1.21  firmware.  It stays within +-10ns,  usually it's between
> +-5ns.  Over 24hrs, gpscon reports TI average 0.15 or so and stddev
> around 2.5ns.
> _______________________________________________
> 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.
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: export.png
Type: image/png
Size: 24975 bytes
Desc: not available
URL: <http://www.febo.com/pipermail/time-nuts/attachments/20100728/a0a30e0e/attachment-0001.png>


More information about the time-nuts mailing list