[aprssig] The final WIDE2-1,WIDE1-1 solution!
bruninga at usna.edu
Sat Apr 2 20:53:02 CST 2005
Sounds like with pre-emptive digipeating you can still
support RELAY without problems. This is fine, and as
Phil says, no need to change horses in the precursor
to an event.
My excitement is not to be confused with immediacy.
My excitement is that we have a solution for those areas
that want to keep a FILL-IN digi while we phase out
RELAY. Transition to the New n-N paradigm can proceed
at a local pace as determined locally... WIDE2-2 works
everywhere now, so there is no rush... Bob
>>> ad6nh at arrl.net 04/02/05 2:20 PM >>>
My vote would be to "fix" the digis in the other metro areas and leave
RELAY alone. For example, we will be running an event in a few weeks
that winds its way through canyons and whatnot, and we will be setting
up a couple of temporary digis. We were going to set them up to respond
to RELAY. Why is this important? Mainly because many of the people
involved in this are very new APRS users, and explaining how to setup a
RELAY digi and put RELAY,WIDE2-2 in their trackers is much easier than
explaining how and why they should set up their digis to respond to
WIDE1-1 and then put WIDE1-1,WIDE2-2 in their trackers.
Phil - AD6NH
Greg Noneman wrote:
> Before we get into SoCal specifics, I want to be clear on what the
> plan is for RELAY support on the digis. Are we talking about
> immediately (or as fast as can be done) removing support for RELAY at
> all digipeaters or is there some transition period?
> Back to the LA situation. Yes, we may be somewhat unique. I don't
> know if anyone else is employing a one-hop network, but it sure is
> effective. Try taking a look at Phil's UI-Traffic Monitor Page
> (http://aprsca.net:8080/uiview/trafficlive.htm). As of today, with
> preemptive digipeating employed on two of the four digis, RELAY is
> perfectly supported and isn't causing extra packets. The same can be
> done with the proposed WIDE1-1,WIDE2-1 fill-in fix, but for us to have
> the same operation (no extra hops generated), it will either mean that
> the remaining two digis will have to go to UIDIGI firmware (with
> preemptive digipeating) or (if still running KPC3s) they will have to
> have WIDE1-1 removed from their UIDIGI path list.
> Right now, nothing much is required on our metro digis to support the
> change. For the two UIDIGI firmware units removing WIDE1-1 from the
> PREEMPTCALLS list will help. I think this will take time to flow into
> everyday operation. We can massage the digi network to best
> accommodate the situation. I think the tough thing will be getting
> those same people whose never removed RELAY from the trackers or never
> turned-on callsign substitution on their home RELAY digis to make the
> changes. As a result, we have some fixed percentage of bandwidth
> chewed-up by people using useless paths.
> On Apr 2, 2005, at 6:30 AM, Robert Bruninga wrote:
>> True. But in LA you simpily continue to promote WIDE2-2
>> only even for mobiles and cut off RELAY entirely. Yes an
>> occasional visitor may come in and get WIDE1-1,WIDE2-1
>> double hop, but it should not be a problem. Also since
>> it is only 4 digis that are currently enforcing the one-hop
>> scenario, if worst comes to worse, we simply "fix" those
>> digis with software if.
>> Yes LA is unique. Maybe we can think of other tweaks to
>> it to help make this fantastic WIDE1-1,WIDE2-1 idea work
>> (where needed). Still mobiles should use not use it unless
>> the area requires fill-in digis...
> aprssig mailing list
> aprssig at lists.tapr.org
aprssig mailing list
aprssig at lists.tapr.org
More information about the aprssig