[aprssig] Bob, Address the WIDE7-6 Possibility
Robbie - WA9INF
mwrobertson at comcast.net
Tue Feb 22 13:01:19 CST 2005
Exactly. I am NOT running any digipeater, there is good coverage around
me now. Except one area that is 6 miles from me, seems to be in a shadow
of all the digis... I would set my UI-View32 station up as a WIDEN if I
could figure out how not to cause the mobile of reaching a real WIDEN by
loosing my short hop to a WIDEN, <G>
Brad [VE3BSM] wrote:
> That's more or less what I'm wanting to do. I run a RELAY-only digi right
> now, and while I need to cover a hole in my area, it's a small enough hole
> that I don't want to digi any more than the absolute minimum.
> I'm running UI-View, and hopefully some settings may come out that'll let me
> accomplish my goal. Until then, RELAY-only it is.
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]
> On Behalf Of Curt, WE7U
> Sent: Tuesday, February 22, 2005 1:30 PM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] Bob, Address the WIDE7-6 Possibility
> On Tue, 22 Feb 2005, Jason Winningham wrote:
>>On Feb 22, 2005, at 12:17 PM, N5TIM wrote:
>>> Looks like this just put the HOME RELAYs out of work.
>>I'm thinking the most effective would be to change home RELAYS to
>>WIDEn-n, if they could be configured so that they digipeat _only_ if
>>the packet has never been digipeated. Since I'm guessing home RELAYs
>>are mostly software based, this should be feasible.
> Yet another tweak: Digipeat after a delay of XX seconds, but only if the
> packet hasn't been digipeated during that delay (first callsign in the
> digipeater field hasn't been used, or the SSID of a WIDEn-N hasn't been
> decremented yet).
> They'll remain quiet most of the time, except when needed.
> aprssig mailing list
> aprssig at lists.tapr.org
More information about the aprssig