[Lowfer] Time coherent scheduling, was: Group of Four

[Mike Staines]

Dave wrote:
>   Alternatively or as well-There's a good case here for you all to develop
> GPS synchronized element timings-and then sort out who goes when!

Actually, I have some code floating around here (never finished) that would
generate QRSS keying based on time. My original plan was to do something
like the propagation beacons on HF where each beacon could have a segment of
time on the frequency.

I did not use GPS for timing however. I just used the PC clock. But with the
various time protocols on the internet the PC clocks can be accurate enough
for this kind of work.

Thinking about it, I might just explore the thought a little more. Since the
time slot for each station would be known there is no need for "IDs". If a
carrier shows up at 12:01 pm on a given frequency then it *has* to be a
particular station. If we provide one minute slots for each beacon, and the
beacons transmit carrier for that one minute, then in 10 minutes we could
potentially see the propagation conditions for 10 different areas of
listening.

This would also address the issue of nearby beacons "clobbering" listeners.
The local beacon (even your own beacon) would only be on, say, 1/10 of the
time leaving 90% of the time available for looking.

A final thought... This might also help with post-processing of signals
(i.e. recording to wave files, etc) since you could index to a particular
time that a signal should be present and not waste time processing data when
you know the signal should not be present.

My contribution for the year.

Thoughts?

Mike
wa1ptc