On 12/09/2010 03:16 PM, jimlux wrote:
Hal Murray wrote:
If you can indeed track a 1W signal from ~ Colorado, there might
indeed be
some timing use for the system.
I have a start at understanding how much data you can get through a
channel. There is a tradeoff between data rate and error rate a
Hal Murray wrote:
If you can indeed track a 1W signal from ~ Colorado, there might indeed be
some timing use for the system.
I have a start at understanding how much data you can get through a channel.
There is a tradeoff between data rate and error rate and it depends on the
signal/noise r
Hi
... and for a very low power system, there's no reason to stick with a "short"
512 bit data set, or a "fast" 1 second rep rate.
If the signal is a "only at night" sort of thing (as I'm guessing it is over
that path), all you really might do is a couple of time transfers a night. A
code tha
In message <20101209105031.6104c800...@ip-64-139-1-69.sjc.megapath.net>, Hal
Murray writes:
>Is there a similar sort of high level picture about sending timing info? I'm
>not even sure what the units are.
Basically with timing you only send one bit: "now"
The most precise way to send that bit
> If you can indeed track a 1W signal from ~ Colorado, there might indeed be
> some timing use for the system.
I have a start at understanding how much data you can get through a channel.
There is a tradeoff between data rate and error rate and it depends on the
signal/noise ratio.
Is there
