| |
ZL3AI > APRDIG 21.09.03 09:05l 202 Lines 7180 Bytes #999 (0) @ WW
BID : 1951-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 18, 5/5
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0BEL<7M3TJZ<LZ3NP<W4JAX<VK4TUB<ZL2BAU<
ZL3VML
Sent: 030920/1402Z @:ZL3VML.#80.NZL.OC #:8731 [Chch-NZ] FBB7.00i $:1951-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Isabel and APRS weather
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Thu, 18 Sep 2003 17:53:00 -0400
X-Message-Number: 34
>CNN reporting 59MPH but others are reporting 90 MPH. I think the storm
>is not as bad as was expected when it hit land and they are milking it
>for all it's got!
>
>Rich
From what I understand, once the storm made landfall, wind gust are
pretty much below 60mph over land. However, northeast and east
of the eye there is still a large area of the storm over water, and wind
speeds there are still approaching 90mph, and stay high until a few
miles inland.
Mike
----------------------------------------------------------------------
Subject: via pcsat
From: "Cap Pennell" <cap@cruzio.com>
Date: Thu, 18 Sep 2003 15:15:00 -0700
X-Message-Number: 35
From the Canary Islands! Cool!
This packet is now showing at http://pcsat.aprs.org
EA8ADH-2]APU24V,VA3HRA,PCSAT-1*,TRACE,WIDE7-7,WIDE,TRACE7-7,WIDE7-7,TRACE=
7-7
,qAo,N1BHX:;145475 *290946z2756.07N/01535.10Wm LINK DE INTERNET E-Q S O R=
UM
ESPA=A5OL
http://map.findu.com/EA8ADH-2
73, Cap KE6AFE
----------------------------------------------------------------------
Subject: RE: Isabel and APRS weather
From: "Ken Brown" <W2KB@comcast.net>
Date: Thu, 18 Sep 2003 18:19:33 -0400
X-Message-Number: 36
One common problem, this time of year, is that the foliage dramatically
reduces the wind speed, unless the anemometer is totally in the clear. I
would guess that my station's readings (W2KB) is somewhere around half of
the actual except in cold weather when the leaves are off the trees when it
is very close.
---Ken
----------------------------------------------------------------------
Subject: : WB4APR's typing
From: John Becker <w0jab@big-river.net>
Date: Thu, 18 Sep 2003 18:16:36 -0500
X-Message-Number: 37
Acocdrnig to an elgnsih unviesitry sutdy the oredr of letetrs in a wrod
dosen't mttaer, the olny thnig thta's iopmrantt is that the frsit and lsat
ltteer of eevry word is in the crcreot ptoision. the rset can be jmbueld
and one is stlil able to raed the txet wiohtut
so thaire
----------------------------------------------------------------------
Subject: UIDWAIT and DWAIT settings
From: "Scott Miller" <scott@opentrac.org>
Date: Thu, 18 Sep 2003 16:25:11 -0700
X-Message-Number: 38
I was asked to go over a local digi's settings (it's a 9612) and make
optimization recommendations. I'm not really familliar with the 9612, but I
skimmed through the manual and one thing that sticks out is the UIDWAIT.
Apparently this determines if APRS traffic will be subjected to the DWAIT
delay time for digipeater collision avoidance. Now, since this thing IS the
local digipeater, I would assume you'd want it off so it'll take the channel
and retransmit immediately. Is that true? Is there any case where you
wouldn't want to do that, perhaps with overlapping coverage areas?
Also, any suggestions on slottime settings? I haven't messed with the
persist stuff in awhile. I think just getting the TXD set right (it's at
400 right now) will help the channel a lot, but the operators report the
carrier detect light is on 50% of the time. Might be another case of a 'too
good' digi location.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: RELAY,WIDE,WIDE
From: Neil Johnson <njohnsn@njohnsn.com>
Date: Thu, 18 Sep 2003 18:49:21 -0500
X-Message-Number: 39
It seems to be that we have the age old debate of "circuit switched" vs.
"packet switched" networking.
Personally, I think the answer is that tracker's/telemetry shouldn't have
to worry about routing at all, just say, "Here I am" or "Here's my weather
report" (Other than letting saying, don't IGATE my traffic).
The routing intelligence should be in the digi's and igates. Since most are
fixed locations they should be able to "talk" to each other and figure out
who's going to digipeat or gate the traffic. As for messaging the digi's
and igate's will know where the station is at to relay the message.
To me, that's KISS.
--
Neil Johnson
http://www.njohnsn.com
PGP key available on request.
----------------------------------------------------------------------
Subject: Re: RELAY,WIDE,WIDE
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 18 Sep 2003 21:01:19 -0400 (EDT)
X-Message-Number: 40
On Thu, 18 Sep 2003, Rochte, Robert wrote:
>>I'm personally all for more centralized control, but it still
>>needs to work without control or coordination.
>
>I was thinking more along the lines of a *de*centralized, adaptive pathing
>algorithm of some sort, relying on real-time observations of the network.
But how does the network know where you want your packets to go?
Only the originator is in the best position to know that. And one
"network solution" does not fit all needs.
Bob
----------------------------------------------------------------------
Subject: RE: Proper DIGI ID interleaving
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 18 Sep 2003 21:03:53 -0400 (EDT)
X-Message-Number: 41
good points. I assume that no TNC keeps good enough time to worry about.
Bob
On Thu, 18 Sep 2003, Henk de Groot wrote:
>At 11:28 17-9-03 -0400, Bob Bruninga wrote:
>>More ideas.
>>On Tue, 16 Sep 2003, Cap Pennell suggested for 10 min direct, 30 min 1
>>hop, 1 hour 2 hop:
>>
>>>>WIDE2-2 EVERY 01:00:00 START 00:00:00
>>>>DIRECT EVERY 00:30:00 START 00:10:00
>>>>DIRECT EVERY 00:30:00 START 00:20:00
>>>>WIDE EVERY 01:00:00 START 00:30:00
>
>Are these times relative to whatever time the TNC is started or is it tied
>to the internal clock? If it is the latter then you get a huge load every
>10 minutes because every TNC with an accurately set clock will transmit at
>the same time (if people copy these settings).
>
>In DIGI_NED I used only relative times for that reason so beacons will
>naturaly spread out and not pile up at the same point in time (although the
>latest version also allow for a fixed start time if the user wants it).
>
>There is something to say about fixed times for digipeater beacons however.
>When at exactly every 10 minutes 1 packet worth of air time is allocated to
>digipeater broadcasting then paths do not matter. Every 10 minutes you have
>1 second or so of heavy QRM due to these digipeater beacons and after that
>you don't have to bother about load from digipeater beacons for 10 minutes.
>Packets with long paths will be killed by QRM anyway, making effectively
>every packet local and direct, zo path settings are irrelevant...
>
>I more like to have these beacons spread randomly so that they mix with the
>other normal traffic without any pile-ups as specific round-number times...
>
>Kind regards,
>
>Henk.
de WB4APR@amsat.org, Bob
PCsat WEB page http://www.ew.usna.edu/~bruninga/pcsat.html
ISS-APRS FAQ: http://www.ew.usna.edu/~bruninga/iss-faq.html
CUBESAT Designs http://www.ew.usna.edu/~bruninga/cubesat.html
APRS LIVE pages http://www.ew.usna.edu/~bruninga/aprs.html
APRS SATELLITES http://www.ew.usna.edu/~bruninga/astars.html
MIM/Mic-E/Mic-Lite http://ssdl.stanford.edu/mims/
---
END OF DIGEST
Read previous mail | Read next mail
| |
