[time-nuts] Rubidium oscillator

[Brian Kirby]

If the unit cannot lock up to GPS, it may be sending bad electronic 
control voltage to the rubidium.  I would look at the "lock" signal from 
the rubidium to see if its on or off.

If its off, I would disconnect the EFC voltage from the GPS unit to the 
FRK, and see if the rubidium locks (should happen under 5 mins from a 
cold start).

A bad lamp can cause a lot of different problems.  You also need to look 
at the xtal signal voltage test point on the FRK.

Brian

Glenn Little WB4UIV wrote:
> I have a GPS disciplined Rubidium Standard. I know that it has a 1024 
> week problem. The engine was made by Trimble. They cannot locate any 
> information on this engine.
>
> The time displayed is off by as much as 30 minutes in 24 hours. The 
> amount that the clock is off varies. The displayed frequency error 
> after cold power up on day 1 was 756 E-12. On day 2 it displayed 1256 
> E-9. I suspect that the Rubidium standard has a problem. The Rubidium 
> standard id an FRK.
>
> What might be causing the problem with the time display? Could a bad 
> Rubidium lamp cause this?
>
> Thanks
> 73
> Glenn
> WB4UIV
>
>
>
>
> _______________________________________________
> 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.
>
>