<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Bob,<BR>
The local Super digi W9AZ-14 is 2.5 miles from the balloon launch site at 300 feet.<BR>
It belongs to our club, I set it up. It's a KPC3+ ver9.1 UIDWAIT is OFF.<BR>
Both of our S-digis are setup under the New-N paradigm, no variations.<BR>
My IGate is only 9 miles from the launch site.<BR>
<BR>
I understand the arguments but you've got to understand the aprs coverage<BR>
in Indiana where these balloons end up is not very good from what I can see.<BR>
I agree with Bob the 30 second beaconing is too often but I know this is a new practice<BR>
for this balloon group.<BR>
<BR>
The last time I sat and watched the balloon's progress was from my D-700 display<BR>
while I was transmitting as the fox in our local club foxhunt last month.<BR>
The balloons transmissions were spread out at least 2 minutes I think back then.<BR>
No problems noted. I was announcing the altitude and distance of the balloon to the<BR>
foxhunters as I was waiting to be found. Very Interesting.<BR>
<BR>
73'<BR>Clay Melhorn N9IO Bonfield, IL<BR>Webmaster:<BR>KARS - Kankakee Area Radio Society - W9AZ <A href="http://www.w9az.com/">http://www.w9az.com/</A><BR>ARRL (Central Division) <A href="http://www.central.arrl.org/">http://www.central.arrl.org/</A><BR> <BR> <BR> <BR><BR><BR><BR> <BR>> From: bruninga@usna.edu<BR>> To: aprssig@tapr.org<BR>> Date: Thu, 23 Jul 2009 18:36:08 -0400<BR>> Subject: Re: [aprssig] NE Illinois Balloon Tracks<BR>> <BR>> >> Note that these balloons were using <BR>> >> very APRS-abusive paths<BR>> >><BR>> >> If you're going to fly... balloon altitudes,<BR>> >> please restrict your trackers to no path, <BR>> >> or at most a WIDE2-1. <BR>> <BR>> I think that is too strong. There were only two errors on this<BR>> flight, and neither of them are included in the text above:<BR>> <BR>> 1) They had a 30 second rate which is TOO OFTEN for a ballooon<BR>> (on the national channel)<BR>> 2) They used WIDE1-1 in a 2 hop path<BR>> <BR>> The BIGGEST problem was the inconsiderate use of 30 second rate.<BR>> The WIDE1-1 initial path is only a minor issue. Although it is<BR>> not recommended, it is not as bad as claimed. And I defend the<BR>> Balloonists desire to have a 2 hop path on the ground.<BR>> <BR>> Everyone must remember that with the New-N paradigm and<BR>> universal WIDEn-N digipeating, that a 2 hop path and a 1 hop<BR>> path from a high altitude balloon are almost no different to the<BR>> channel. Each digipeater will digipeat the packet ONCE AND ONLY<BR>> ONCE. In either case. And the WIDE1-1 digi's will also<BR>> digipeat the packet ONCE AND ONLY ONCE. <BR>> <BR>> And all of this once-and-only-once is happing in the SAME time<BR>> slot. SO there should not be any more QRM than if the packet<BR>> used WIDE2-1... UNLESS the local digipeaters have never been<BR>> fully setup as New-N. In that case, it is not the fault of the<BR>> balloonist, but the local network.<BR>> <BR>> Digipeaters are supposed to have UIDWAIT set to 0 so that all<BR>> digipeated packets happen at the same time. If your local digi<BR>> does not have that set, it is part of the problem, not the<BR>> balloonists.<BR>> <BR>> Just something to think about.<BR>> <BR>> Bob, Wb4APR<BR>> <BR>> <BR>> <BR>> _______________________________________________<BR>> aprssig mailing list<BR>> aprssig@tapr.org<BR>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig<BR><br /><hr />NEW mobile Hotmail. Optimized for YOUR phone. <a href='http://windowslive.com/Mobile?ocid=TXT_TAGLM_WL_CS_MB_new_hotmail_072009' target='_new'>Click here.</a></body>
</html>