[time-nuts] Redundant GPSDO configuration / hardware
kb8tq at n1k.org
Fri Oct 9 18:11:04 EDT 2015
There are an enormous number of branches and twists in coming up with a “zero failure”
One of many:
If the system uses GPS (or any GNSS) *and* Joe pulls up with a GPS jammer in his truck, all GPS
systems go off the air. If Joe parks in the parking lot for a few weeks, the systems
are all down for that period of time…..
Unfortunately this sort of thing *does* happen. It may actually be more likely than some of the
other sorts of failures you have on your list. If your system is something that is likely to be
deliberately attacked (military drone), then it’s actually a pretty likely thing.
> On Oct 9, 2015, at 4:36 PM, skipp Isaham via time-nuts <time-nuts at febo.com> wrote:
> Redundant GPSDO configuration / hardware
> Hello to the Group,
> I realize integrated redundant GPSDO systems are available. If I wanted to
> obtain a near zero failure down time using (dual) separate GPSDO hardware, is
> there a conventional or practical method to integrate or construct a hot standby
> system from hardware not originally part of an integrated package/system? An
> example might be the use of different brand or model GPSDO hardware.
> If a popular method is used to integrate two separate GPSDO outputs in to
> a practical hot standby system, I would appreciate reading your suggestions
> and information. Even comments about obtaining GPSDO output for a control
> system that simply can not fail while in regular service/operation.
> Thank you in advance for your replies.
> skipp025 at yahoo dot com
> 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.
More information about the time-nuts