[aprssig] Knoxville digi

[Patrick Green]

This digi's SS as well.  When I was in the area last, it behaved well.  The
only problem was when I'm in the coverage area, I have to remember to digi
TN instead of WIDE1-1 other than that, the dupes weren't noticabe by me if
there were dupes.  I wouldn't hassle the digi owner too much because he
could just turn it off if peeps keep badgering him about it.

73 de Pat --- KA9SCF.

On 6/29/06, Robert Bruninga <bruninga at usna.edu> wrote:
>
> There were some emails about the old WIDE digi in Knoxville.
> I didnt keep any of them, but had a final thought.
>
> If the problem is the hardware then there are easy fixes
> which can still use the existing hardware.
>
> If it is an old digi that only supports one ALIAS (WIDE)
> then simply change that to "WIDE1-1".  This will
> instantly upgrade the Knoxville area to respond to all
> mobiles passing through.  SIMply change its DIGI ICON
> to a "1" overlay and include "W1 only" in the position comment.
>
> If it can support more than one alias then used these aliases:
>
> WIDE1-1,WID2-2,WIDE2-1,WIDE3-3
>
> And give it an overlay of "P" and put "W1,2,3 one-hop only."
> in its comment field.
>
> THat way, you dont have to swap out any hardware,
> just change a few parameters.  While you are there, of course,
> make sure it is only beaconing its position no farther than
> 1 HOP, since it can hit all digipeaters within 100 ore more
> miles...
>
> Again, If I am missunderstanding the problem.... ignore me.
>
> de Wb4APR, Bob
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20060629/8ac9496b/attachment.html>