| |
PA2AGA > HDDIG 23.09.99 05:59l 187 Lines 7393 Bytes #-9769 (0) @ EU
BID : HD_99_238I
Read: GUEST
Subj: HamDigitalDigest 99/238I
Path: DB0AAB<DB0PV<DB0MAK<OK0PKL<OK0PPR<OK0PPL<OK0POK<OK0PAB<HA5OB<HA3PG<
SV1AAW<EA7URC<PE0MAR<PI8VNW
Sent: 990922/2342Z @:PI8VNW.#ZH2.NLD.EU #:1533 [HvHolland] FBB7.00g $:HD_99_238
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA19569 ; Wed, 22 Sep 99 22:24:25 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00015824 ; Wed, 22 Sep 99 21:24:19 MET
Date: Wed, 22 Sep 99 21:17:36 MET
Message-Id: <hd_99_238I>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/238I
X-BBS-Msg-Type: B
> a little better.
Some dumb questions from the peanut gallery, here:
What HF frequency has the most reliability for what distance at
all hours of the day? When we find that answer we would know how far
apart HF Gateway/BBS nodes should be. Or can we have the software
determine the MUF for a given time period? Then we can have primary
and secondary frequencies for the node to use without a lot of time
used scanning for DX. Can we have the network house keeping routines
keep each node aprised of the distance or locations of the other nodes?
MUG/LUF stats are available all the time and normally predictable. There
should be an easy way to get them into the HF node software.
Please understand that I ask these questions as a systems guy, not a
programmer. I hope I haven't gotten to far off the track.
Tony -- KF3BX
predictable. Next is software development to make use of these stats.
After that the
--------------CFF2085208B659DA0CB17A74
Content-Type: text/x-vcard; charset=us-ascii;
name="agiroux.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Tony Giroux
Content-Disposition: attachment;
filename="agiroux.vcf"
begin:vcard
n: -- Tony;KF3BX
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:agiroux@cvn.net
x-mozilla-cpt:;0
fn:KF3BX -- Tony
end:vcard
--------------CFF2085208B659DA0CB17A74--
>.
------------------------------
Date: Tue, 21 Sep 1999 17:35:01 -0700
From: "Cathryn Mataga" <cathryn@junglevision.com>
Subject: Those Wide, Open Spaces
Tony Giroux wrote in message <37E81A6A.E3B69A49@cvn.net>...
> What HF frequency has the most reliability for what distance at
>all hours of the day? When we find that answer we would know how far
>apart HF Gateway/BBS nodes should be. Or can we have the software
>determine the MUF for a given time period? Then we can have primary
>and secondary frequencies for the node to use without a lot of time
>used scanning for DX. Can we have the network house keeping routines
>keep each node aprised of the distance or locations of the other nodes?
>MUG/LUF stats are available all the time and normally predictable. There
>should be an easy way to get them into the HF node software.
Well, the scoop is that the super duper new generation of BBS's equiped
with the ultra-nifty, but slightly expensive PCTII boxes are able to scan
scan many bands and many HF frequencies. If I want to call one of these
systems, I just need to guess at which frequency is best, usually 20m
lately -- probably 30m or 40m when sunspots aren't so good. And, if
conditions are good, they decode my call and answer on any number
of HF bands. There are a few little issues. Doing this at 100 watts
is pretty easy, but running power with this kind of scanning setup is a
little
involved -- I would guess. That is without buying one of the top of the
line amps.
Which way do you point the beams? Do the beams turn to fixed positions
for each part of the day -- or what. I dont know.
Also, sometimes, with HF, no matter what band you are on, with a
country as big as the US, you just plain can't get there from here. That is
with a modest HF station like mine. Maybe there is some way to predict
HF paths reliably, but I'm not aware of it. You know, the CB-ers call it
skip for a reason -- that is the signals tend to skip lots of places in
between
here and there. So, sometimes you'll hear stations far away, but not up
close.
Or you'll hear them very far away, but slightly closer won't come in.
There's
a lot of strange unpredictability here. This deserves a whole book in
itself.
Maybe if you'd want to systemize this in some way, perhaps then each
HF gateway, would collect statistics on which links were available to it
at what times -- since I think with all the antenna variables and such,
this information, practically can only be measured and not calculated. And,
then transmit this information back to a central hub for the region where
maybe a clever piece of code somewhere could stew all the numbers
together including how much throughput each HF link was capable of and
parcel out the messages in an optimum manner. That means, perhaps,
taking data from past connections, and mixing that with some sunspot
numbers and the time and date or whatever, and coming up with a sensible
forcast that a connection would be good. I don't know, this is all just
speculation.
>.
------------------------------
Date: Tue, 21 Sep 1999 19:27:14 -0700
From: "Hank Oredson" <horedson@att.net>
Subject: Those Wide, Open Spaces
Cathryn Mataga <cathryn@junglevision.com> wrote in message
news:7AVF3.2462$1i3.39397@nuq-read.news.verio.net...
> Tony Giroux wrote in message <37E81A6A.E3B69A49@cvn.net>...
> > What HF frequency has the most reliability for what distance at
> >all hours of the day? When we find that answer we would know how far
> >apart HF Gateway/BBS nodes should be. Or can we have the software
> >determine the MUF for a given time period? Then we can have primary
> >and secondary frequencies for the node to use without a lot of time
> >used scanning for DX. Can we have the network house keeping routines
> >keep each node aprised of the distance or locations of the other nodes?
> >MUG/LUF stats are available all the time and normally predictable. There
> >should be an easy way to get them into the HF node software.
>
> Well, the scoop is that the super duper new generation of BBS's equiped
> with the ultra-nifty, but slightly expensive PCTII boxes are able to scan
> scan many bands and many HF frequencies.
<rest deleted>
Does not need an expensive controller. Some folks use PK-232
and standard PACTOR, or use the P-38 CLOVER/PACTOR
boards (can be found used for $200 or less). An old junker
386 or 486 is good enough to run some of the software, some
requires Windows and a faster machine. However it is a good
idea to have a reasonably good HF setup ...
--
... Hank
http://horedson.home.att.net
>.
------------------------------
Date: Tue, 21 Sep 1999 19:24:30 -0700
From: "Hank Oredson" <horedson@att.net>
Subject: Those Wide, Open Spaces
Tony Giroux <agiroux@cvn.net> wrote in message
news:37E81A6A.E3B69A49@cvn.net...
>
> Some dumb questions from the peanut gallery, here:
Um ... not so dumb. Nobody has mentioned the architecture of the
store and forward network on HF.
> What HF frequency has the most reliability for what distance at
> all hours of the day? When we find that answer we would know how far
> apart HF Gateway/BBS nodes should be. Or can we have the software
> determine the MUF for a given time period? Then we can have primary
> and secondary frequencies for the node to use without a lot of time
> used scanning for DX. Can we have the network house keeping routines
> keep each node aprised of the distance or locations of the other nodes?
> MUG/LUF stats are available all the time and normally predictable. There
> should be an easy way to get them into the HF node software.
To be continued in digest: hd_99_238J
Read previous mail | Read next mail
| |
