[aprssig] SSn-N Coordination

[Wes Johnston, AI4PX]

The T2 digi from argentdata can support multiple (7??) digi aliases.  It
also supports preemptive digipeating, which I suppose could be used to
bridge a packet inward from PA to CPA and WPA to CPA if you really needed
the traffic in your area.

I'm not familiar with the capabilities of byonics stuff....

The kantronics TNC can only support two aliases.

You could program a digi to respond to both PA and WPA.  I know the
population density varies dramatically from the southeast corner to the
west, but I just can't understand segmenting the state.

Wes
---
"Language shapes the way we think, and determines what we can think about."
-- B. L. Whorf



On Tue, Feb 15, 2011 at 07:56, Jim Alles <kb3tbx at gmail.com> wrote:

> Hello All,
>
> I am just becoming aware of this aspect of APRS configuration.  I live in
> Pennsylvania.  From what I have observed, we have PAn-N in the East, and
> WPAn-N in the West, and I live in-between.  As far as the ARRL section, I
> believe we are in Western PA.
>
> Could we use the PAn-N alias for someone to 'ask permission' to transit the
> state E-W?  It would mean that our primary Digis (we seem to have pretty
> good coverage - 2 hops is capable of getting us throughout the state) would
> only xmit a less than third hop when seeing WIDEn-N.
>
> someone using a PAn-N could use three hops to get across the state, but it
> would also be contained so the packet doesn't end up in Canada.
>
> I am also thinking that I want a CPAn-N alias for North- to South coverage
> of the Central part of the state.  This would be the usual restrictive mode.
>
> Personally, I expect to be keeping most of my transmissions directed mostly
> at W3YA-1 explicitly.
>
> Am I confused? How many Aliases can a typical digi handle?
>
> Thanks & 73,
> Jim A. KB3TBX
>
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.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/20110215/91b49046/attachment.html>