KPC3+ (PLUS) Version 8.3 Settings (and 9.1) WIDEn-N DIGIs 14 Jun 2021 ---------------------------------------------------------------------- Update 14 Jun 21 Added note about Problem(0) - Log delayed packets Update 19 Jul 14 Suggests using digi location vs callsign for the name Update 24 Jul 09 added 2 LTexts for local EchoLink and IRLP objects Update 16 Nov 08 to clean up some text Update 2 Sep 08 added KA-node enabling for digi maintenance Update 8 Nov 07 clarified that "W2" in a digi text means that W2 is the current local recommendation for that area, not necessarily the trap limit. Update 24 Jan 07 clean up the BText for local repeaters Update 18 Oct 05 to include 9.1 ROMS. PROBLEM(0): There is a random problem with KPC3 digis that at some point hold up and then regurgitate LOTS of packets. Here is a possible fix. Kantronics recommends shorting the RTS and CTS pins together within my serial cable. (PINS 4/5 on DB25 and PINS 7/8 on DB9). Shorting the RTS and CTS together prevents the software from holding the RTS pin low. If the RTS pin is at low voltage the KPC3+ will start buffering and does not get caught back up. This applies to all 8.3 and 9.1 ROMS running on the KPC-3+(PLUS) TNC. With one small change (noted below), it also applies to KPC-3+ TNC's running the last version of the 8.2 ROMS ending in "7265". The difference is noted below in section 4) and "6E". Typically, all KPC-3+ digis already support the basics of New n-N Paradigm, that is, WIDEn-N digipeating. But there are better ways to use these features that have been developed since January 2005 that includes: - add path tracing to WIDEn-N for the health of the network - add TRAPPING of large values of N to cut out-of-area-QRM - add Proportional-pathing to the digi's beacon to cut QRM - added SSn-N path for efficient area-wide routing - added standrdized TEXT to let users see capabilities - Added new overlay "S" so users could see these new digis FIRST: RESET the TNC to factory defaults to start fresh. 1) Resetting the TNC should remove the obsolete "RELAY", "WIDE", "TRACE", and "SS" aliases which are obsolete. 2) Set these commands for normal operation: MYCALL - Digi callsign or preferably LOCATION name INTFACE - Terminal. So you can enter the remaining parameters HID OFF - These packets are of no value to APRS CD SOFTWARE - For the best collision avoidance method UIDWAIT OFF - To speed up the response TXD 18 - To shorten the TX delay by 40% from the 300ms default XMITLVL xxx - Set TX modulation level to less than full distortion! MYA NONE SECOND: Set up the KA-Node process so that you can maintain distant digis via a path from a local digi if you own more than one digi. MYNode XXXXXX-7 The KA node callsign NUMNodes 2 Will support up to 2 connections THIRD: Eliminate the settings that are detrimental to the network. * UIDWAIT should be OFF. (the default). With it on, your digi is not doing the fundamental APRS fratricide that is the primary mechanism for minimizing channel loading. All digis that hear the same packet are supposed to DIGI it at the SAME time so that all those copies only take up one additional time slot. (but outward located digs will hear it without collision (and continue outward propogation) FORTH: Set up the DIGI ALIASES to perform the New-N digipeating. 1) UITRACE WIDE,30 - This tells the digi to support WIDEn-N and to insert its own callsign so that the path is fully traceable. 2) UIFLOOD SS,30,ID - Where SS or SSS or SSSS is your State or local ARRL or other Ham radio comunications section organization name. Notice, that having ID ON is a complete reversal to previous recommendations that wanted NOID to be set. Now we want ID ON to improve path tracing. Users of SSn-N paths are encouraged to use the path of WIDE1-1,SSn-N so that they get FIRST and LAST digi identification. These packets will arrive as DIGI1,DIGIn*,SSn-N, showing the first and last DIGI's used. 3) UIDUPE to 30. This is a new command in version 9.1 roms. FIFTH: Now set up the digi's own beacons into the network: 1) Prior to July 09, we used all four LTexts to implement Proportional Pathing on the digi's own data, so that beacons went out direct every 10 minutes, but 1 hop every 30 and 2 hops every hour. Now we only use two LTexts for a direct 10 minute and 2 hop 1 hour beacon so we can use the other two LTexts for local info to mobiles. See www.aprs.org/digis/digi-rates.txt. LT 1 DIGI's beacon text (direct every 10 minutes) LT 2 DIGI's beacon text (1 or 2 hops every hour) LT 3 first frequency object LT 4 second frequency object BLT 1 EVERY 00:10:00 START 00:00:03