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