And then all that can be done is lock the oscillator to a solution derived from the birds... this can explain why a receiver can fail to correctly lock an oscillator or give a strange PPS. That is, it is possible, in case of errors, to have, for example, a PPS displaced by 1mS but state that the solution is good.
On Sun, Feb 5, 2012 at 1:31 PM, Magnus Danielson <mag...@rubidium.dyndns.org > wrote: > On 02/02/2012 10:13 AM, Azelio Boriani wrote: > >> OK, got it: no need to lock the receiver clock to birds to get stable data >> (e.g. Oncore+Cs) but the clock can be locked to birds to get even better >> data and obtain "for free" a reference clock (TBolt). The use of a stable >> clock (not locked to birds) feeding the receiver can show the various >> errors that affect the downlink having removed the clock instabilities. >> > > Not quite right. If you lock up the clock, you do not lock to the birds, > but to GPS time or UTC as received over GPS. The observed time of the birds > would be a bad solution since you can't see a particular bird continously > unless you is in geosync orbit. > > Cheers, > Magnus > > ______________________________**_________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/** > mailman/listinfo/time-nuts<https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts> > and follow the instructions there. > _______________________________________________ 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.