[aprssig] Digpeater setup

[Dave Sparks]

----- Original Message ----- 
From: "Robert Bruninga" <bruninga at usna.edu>
To: <wa7ros at juno.com>; <aprssig at lists.tapr.org>
Sent: Tuesday, March 29, 2005 6:12 PM
Subject: Re: [aprssig] Digpeater setup


>>>> wa7ros at juno.com 3/29/05 8:48:27 PM >>>
>>> UIDIGI RELAY,WIDE,WIDE6-6,WIDE7-7  (traps 66 and 77)
>>> UIFLOOD NE,30,ID
>>> UITRACE  WIDE,30
>>
>>How can that UIDIGI setting manage to pass RELAY and
>>WIDE and all the WIDEn-n up through WIDE5-5; while at
>>the SAME time be suppressing WIDE6-6 and Wide7-7?
>
> SImple.  The UIDIGI ALIAS list prempts any other mechanism,
> so the WIDE6-6 packet is digipeated with call sign substitution
> of the MYCALL of the digi, and the WIDE6-6 disappears and
> will not go any further.  Thus it acts like a "trap"
>
> But I disagree. with your original premise.  We now recommend
> that use of WIDE and RELAY are obsolete too.   So WIDE
> should not be in the UIDIGI alias list.  We do think we should
> probably leave RELAY in there, but we want to discourage
> anyone from using it routinely because it does more damage than
> good.  But its there if someone has a specific need.

Hi Bob,

I hope I'm not bringing up something that has already been discussed, but 
isn't there a role to be played by a modified RELAY digi?  What about a 
setup where such a station keeps track of recent messages received directly, 
and then digis them only *IF* they aren't heard being resent by a WIDE digi 
within a certain period of time, like 20 sec., let's say?

The problem with mountainous terrain, is that local terrain can block 
line-of-sight propagation to a much higher, but distant mountain top digi. 
IOW, the HAAT figure at a mobile APRS station is negative.

Dave, KD6PDZ