[FADCA] Points of Clarification

[bud Thompson]

Deltona
Thursday April 11 0730EST

Hi, Gang:

Figured it's time to offer some clarification - we've had a lot of =
e-mail lately that has slightly broadened the original topic -

1.  Under auspices of FADCA I am providing a presentation at the State =
EOC "State Warning Point" in Tallahassee during the SEDAN meeting on =
Saturday May 4th.

2.  Part of that demonstration will include an over-the-air =
demonstration.

3.  Many FADCA folks will gather Friday at a motel (Best Western?) for =
fellowship and to support this effort.  Some will be bringing =
equipment/software to help others with installs, etc. (What fun.)

4. FADCA will have a significant presence during the SEDAN meeting on =
Saturday. (Whoopee!)

Anyone who attends Saturday needs to be prepared to field questions that =
I may not feel qualified to answer.

bud's spin - and what I'm preparing for Saturday

The major emphasis will be the presentation, not the over-the-air =
demonstration.=20

The presentation will be aimed directly at showing how a layered packet =
network can (best) support LOCAL  emergency communications within a =
county or groups of counties.  It will also show how the use of HF over =
larger distances (say, 200 miles) enhances getting =
data/information/messages throughout the state, including to/from the =
SEOC (which happens to be distant from much of the state).  The =
presentation will also discuss the fact that BBS-to-BBS transfer is the =
best method of managing data/information/message files.

We will specifically request/suggest that the SEOC add/include BBS =
transfer capability into/at  the State Warning Point.=20

Getting that added (in some form) is the main reason for our appearance =
and presentation.  We need to be prepared to suggest how that can be =
accomplished w/o upsetting the existing SEDAN PBBS/keyboarding input on =
145.77 at the SEOC.

NOTE:  I also feel that we should have a suggested plan for the two =
networks to work together to better cover the state.=20

I AM STILL AWAITING INPUT FROM FADCA ON THAT LAST POINT!  (Maybe with =
all my e-mail I've missed that.)

The over-the-air HF demonstration has one single (overt) purpose:=20

1.  To show how data/message traffic can be transferred from within the =
Last Mile (on HF) to an internet-connected station (WL2K) anywhere =
outside the Last Mile and be processed to the addressees' e-mail inbox.  =
Connecting from inside to outside the Last Mile is not limited to WL2K =
stations, but that is where the ubiquitous internet is found.  If time =
permits we'll link to several WL2K and several non-WL2K stations.

Certainly a covert purpose is to show that ham radio digital technology =
has progress beyond keyboarding at 1200b.  No need to say that, it will =
be evident throughout the presentation/demonstration.

If we had our layered network in place from TLH through to Gainesville =
or Ocala or JAX, then we should demo that for a fact.  That would be =
very effective and meaningful to our purpose.=20

I don't see any way of doing that on May 4th.  =20

The only thing we might demo via packet/vhf  would be BBS-to-BBS =
transfers from the demo station at the SEOC out to a temporary BBS at =
the motel or wherever.  I don't know how effective that demo might be as =
it would be just straight point-to-point at 1200b.  I'm not against it, =
just want to be sure it will be meaningful for the time spent.  If we do =
that, it must be with binary-compression rather than straight text or it =
will not be meaningful at all.

I'd appreciate any input / suggestions on this topic within the next few =
days, as I'm working on the Power Point presentation and want to have =
that really finalized late next week. While I could make some needed =
changes Friday night in TLH, I'd prefer to have it all ready to go much =
sooner!

I will be contacting John Fleming Monday to work out the details =
regarding the times, projection equipment, antennas, etc.

Thanks a bunch.

73,
bud N0IA






--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---