[aprssig] Recommended IGate Connection
cap at cruzio.com
Mon Sep 11 16:46:05 CDT 2006
I was going to suggest that just like using WIDE2-1 you could use "SSn-N" ,
"SS"1-1 (WY1-1 in WYoming), for that one digi hop without tripping any
fill-in digis. But that would trip the digi on top of the very tall
mountain (you mentioned) too.
The fill-in digis operate WIDE1-1 ONLY and their own MYcall, but don't
operate any "SSn-N".
Often, a _little bit_ of redundancy can be worthwhile. Using a named digi's
MYcall is fine until that particular digi goes down.
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org
> [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Joel Maslak
> Sent: Monday, September 11, 2006 06:28 AM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] Recommended IGate Connection
> On Sep 11, 2006, at 5:19 AM, Jason Winningham wrote:
> > On Sep 10, 2006, at 11:08 PM, Joel Maslak wrote:
> >> I'm running an IGate for a relatively small geographic area
> >> (transmit path of WIDE2-1, considering shortening even more to one
> >> specific named WIDE).
> > WIDE2-1 is a one hop path; the only way to get it shorter is to
> > transmit with an empty path, direct only.
> > WIDE is a one hop path element, obsolete in most areas. WIDE2-1
> > (or WIDE1-1) is the "newN-N paradigm" equivalent.
> Actually, I meant to say I'd be using the actual call of the digi I'd
> be interested in (a digi that kind of sits in a hole with me, versus
> WIDE2-1 which hits both that digi and one on top of a very tall
More information about the aprssig