[time-nuts] Low-long-term-drift clock for board level integration?
bownes at gmail.com
Mon Feb 20 20:53:47 UTC 2012
Think trying to measure the distance between two distant moving spacecraft
with no idea what the gravitational gradient is between them or the ability
to measure the doppler.
Unless, of course, Bill is doing much different things than he was when I
last ran into him. :)
On Mon, Feb 20, 2012 at 3:32 PM, Hal Murray <hmurray at megapathdsl.net> wrote:
> > You may be able to do a similar thing in your receivers. For example if
> > master node were to send a timing message at known times (say once at
> > top of every hour) the receivers could use that to determine their local
> > clock offset and rate for those cases where the path was the same (or
> > even for a list of paths).
> Nope. The problem is queuing delays in routers. Satellites don't have
> I think those delays is what he is trying to measure.
> These are my opinions, not necessarily my employer's. I hate spam.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to
> and follow the instructions there.
More information about the time-nuts