[aprssig] PACCOMM TNC & WIDEn-N clarification
Robert Bruninga bruninga at usna.eduFri Oct 21 03:30:35 UTC 2005
- Previous message: [aprssig] Lets Fix New-N now!
- Next message: [aprssig] PACCOMM TNC & WIDEn-N clarification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Oh, and I also meant to add to that, that the old PacComm digi's simply need to be on the list for replacement. Yes, they can be made to work in the New-N paradigm as a "P" digi, but that was only to allow continuous operation while efforts were being made to eventually REPLACE it with somethign that fully suports WIDEn-N... >>> bruninga at usna.edu 10/20/05 11:16 PM >>> 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
- Previous message: [aprssig] Lets Fix New-N now!
- Next message: [aprssig] PACCOMM TNC & WIDEn-N clarification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
