[aprssig] PACCOMM TNC & WIDEn-N clarification

[Robert Bruninga]

It is fine as a fill-in digi since after it digipeats
the a WIDE1-1,WIDE2-1 packet, that packt
then becomes WIDE1-1*,WIDE2-1 and so
it looks just fine to the surounding WIDEn-N
digis who will then digipeat it down to
WIDE1-1*,WIDE2* where it stops.   Bob

>>> n0yxv at gihams.org 10/21/05 7:03 PM >>>
I've got an old KPC2 that I've used to experiment from time to time as a
fill in (temp) Digi using the alias of WIDE1-1 (only). That way the only
things I repeat are things that haven't already been Digi'd. Only problem is
that since it can't count down WIDE1-1 to WIDE* it retransmits the signal as
WIDE1-1(or whatever you have in your UNPROTO path). I tried to enter WIDE*
in the UNPROTO path but it wouldn't take the * character. If it works in
your area it's a way to use the old TNC's as a sudo WIDEn-N (Fill IN) Digi.
Would NOT work for a wide area Digi.

Somebody correct me if I'm wrong it's been a long time since I tried this
(as an experiment only).

> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org [mailto:aprssig-
> bounces at lists.tapr.org] On Behalf Of Robert Bruninga
> Sent: Thursday, October 20, 2005 10:16 PM
> To: smithb at bpsmicro.com; aprssig at lists.tapr.org 
> Subject: Re: [aprssig] PACCOMM TNC & WIDEn-N clarification
> 
> Yes, you are correct.  The only way through an
> old Paccomm digi converted over to the New-N
> paradigm is to use a dual-entry path like
> WIDE1-1,WIDE2-1.
> 
> But I now see this confuses people and appears
> to contradict other writings.  Maybe I should
> change that to FIXED stations in the vicnity of
> those old digis should use the path of WIDE2-1,WIDE2-1
> etc..
> 
> bob
> 
> 
> >>> smithb at bpsmicro.com 10/20/05 7:36 PM >>>
> A couple of the local digis are running the old PACCOMM TNCs based on the
> specifications on Bob's page at
> http://www.ew.usna.edu/~bruninga/aprs/PacComm-settings.txt . These aren't
> my
> digis, but I'm one of the alternate "sysops" for the owner.
> One of the local home stations was using WIDE1-1,WIDE2-1 in his path, and
> I
> explained that in our area, home stations should get by with just WIDE2-1
> (or in some remote cases, WIDE2-2 to hit the city). He responded that if
> he
> used either of those, the digi in question (the only one that hears him
> direct) would *not* digipeat him, but if he used the WIDE1-1,WIDE2-1, it
> did.
> 
> I was a bit confused, but in re-reading Bob's page I saw the following:
> 
> >>>
> USERS IN THE AREA OF A PACCOMM DIGI:  All fixed stations in range of
> this digi need to set their outgoing path of WIDE1-1,WIDEn-N where N is
> the common value in the region minus one.  If this is a 3-3 area, then
> use WIDE1-1,WIDE2-2.  If it is a 2 hop area, then use WIDE1-1,WIDE2-1.
> <<<
> 
> So if I'm reading this correctly, anybody trying to go through this digi
> as
> their first hop *must* have WIDE1-1 at the beginning of the path, or else
> the paccomm will ignore them. I'm assuming if that's true, then in the
> "old
> days" this would also ignore all packets without "RELAY" at the beginning.
> 
> Can anybody confirm that my understanding is correct, or educate me as to
> why I'm seeing what I'm seeing? Is the next best viable option to look at
> getting UIDIGI PROMs burnt for these digis? Is UIDIGI a better option?
> 
> Thanks;
> Brad.
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org 
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig 


_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org 
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig