An alternative to the Kantronics TNC is UI-Digi. Click here for more info: http://dxspots.com/fix14439_uidigi-rom.html

Many of the primary WIDEn-N digipeaters in the NWAPRS use the Kantronics KPC-3 with version 8.2 or higher eprom or any version KPC-3 Plus TNC. The settings described below are for the KPC-3/3 Plus. This is not the only TNC that will function as true WIDEn-N digi under the n-N paradigm. TNC2 clones with the UIDIGI eprom can also implement the n-N paradigm. Another option is to use a computer running Digi_Ned software, which allows much more powerful APRS digipeating rules than a KPC-3.

Normally WIDEn-N digi mailboxes will be disabled to discourage use of regular packet connects to the digipeater. Packet and NODE hopping is likewise discouraged. Tying up the digi with connected packets further reduces the overall system performance.

WIDEn-N DIGIPEATER SETTINGS KANTRONICS KPC-3 (VER 8.2 or newer), or KPC-3 Plus (any version EPROM)
Revised April 2007 (latest changes in RED)

	KANTRONIC KPC-3 (ver 8.2), KPC-3 Plus VALUE
ABAUD	4800
BEACON	E 10
BLT	1 E 00:30:00 START 00:00:00 2 E 00:30:00 START 00:10:00 3 E 01:00:00 START 00:20:00 4 E 01:00:00 START 00:50:00
BTEXT	;145.15- *111111z3742.40N/12340.40WrT100 Spok MicaPeak On a D700, the text will display as:      145.15-      T100 Spok       MicaPeak ;FFF.FFF+x*111111zDDMM.mmN/DDDMM.mmWrAAAAAAAAAABBBBBBBBBB88888888.... Where ";FFF.FFF+x *111111z" is the frequency, +/- is the offset, x is an optional local unique character, and *111111z is the default null Date-Time field for the OBJECT format      or      Where ";FFF.FF+xy *111111z" is the frequency, +/- is the offset, x and y are each one of over 3600 unique characters A-Z or 0-9, and *111111z is the default null Date-Time field Where "DDMM.mmN/DDDMM.mmWr"is the LAT/LONG (Degrees, Minutes, and Tenths of Minutes format) and "r" symbol is for a voice repeater Where "AAAAAAAAAA,BBBBBBBBBB,88888888 "are the 10x10x8 free-text fields for easy display on a Kenwood D700 radio (D7A will only display 10x10 free-text fields See http://www.ew.usna.edu/~bruninga/localinfo.html for more info
CD	SOFTWARE
CMSG	DISC
HEADERLN	OFF
HID	OFF
INTERFACE	TERMINAL
LT 1-4 (ALL EXACTLY THE SAME)	1 !4720.20NS12320.45W#PHG5660/W2,WAn,Willapa Valley WA7RW Note: Put actual callsign (no SSID) at end if using a geographical alias in MYCALL (Geocoord format is DDMM.mm that's tenths of minutes, not seconds)
LTP	1 APN382 2 APN382 3 APN382 VIA WIDE2-1 4 APN382 VIA WIDE2-2
MYALIAS	DISABLED
MYCALL	TACTICALNAME, e.g. KOPEAK or SOMTN
MYNODE	DISABLED
MYREMOTE	Use a logon callsign of your choice. For K7GPS-10, the logon is GPSR-10. The R means Remote. This will be matched up with the secret text used in RTEXT to authenticate the logon.
NTEXT	not used
NUMNODES	0
PACLEN	0
PASSALL	OFF
RTEXT	(Secret text known only to control operator so you can access remotely)
UNPROTO	APN382 If using a KPC-3 ver 8.2.
UIDIGI	If KPC-3 ver 8.2 rel 7265: ON WIDE1-1,WIDE4-4,WIDE5-5,WIDE6-6 If KPC-3Plus: ON WIDE4-4,WIDE5-5,WIDE6-6
UIFLOOD	SS,30,ID eg:   WA,30,ID Note: Use one of the following: WA,ID,MT,OR,BC,AB
UITRACE	WIDE,30
UIDWAIT	OFF

Ver 9.0 and up:

• BLT: The BLT parameter controls the timing of when the LT buffers are sent. We can control how often the buffers are sent, and also when they start.
  • BLT 1 E 00:30:00 START 00:00:00 Here we are setting BLT 1 up so that the TNC sends LT 1 once every 30 minutes at the top of the hour, and then again at 30 minutes past the hour, with no digipeat.
  • BLT 2 E 00:30:00 START 00:10:00 Here we are setting BLT 2 up so that the TNC sends LT 2 once every 30 minutes at 10 minutes past the hour, and then again at 40 minutes past the hour, with no digipeat.
  • BLT 3 E 01:00:00 START 00:20:00 Here we are setting BLT 3 up so that the TNC sends LT 3 once per hour at 20 minutes past the hour, and it is digipeated to a path of WIDE2-1 (one hop).
  • BLT 4 E 01:00:00 START 00:50:00 Here we are setting BLT 4 up so that the TNC sends LT 4 once per hour at 50 minutes past the hour, and it is digipeated to a path of WIDE2-2 (two hops).
    
• LT: The LT buffers are all programmed the same. They contain an APRS position packet that describes the location of the digipeater, and also contains some descriptive information. We can include information that describes the configuration of the digipeater. In the packet below, we are letting users know that the digipeater supports the WIDEn-N paradigm, and also statewide paths with the "S' overlay character. We also indicate the WIDEn-N capabilities, and the local suggested number of hops with the 'W2'. 'WAn' tells users that the digipeater is part of the Washington digipeater network, and supports WAn-N. Following that is descriptive text for the location, followed by the assigned callsign of the digipeater control operator. With approximately 85% of the mobile stations with display capability being the Kenwood TH-D7a and TM-D700, it's a good idea to format the text to fit their screens. The TH-D7a display will show two lines of 10 characters. The TM-D700 will display two lines of 10 characters and one line of 8 characters. Information of most importance to mobiles should appear in the first 20 characters. It is very important to include a callsign here if you are using a descriptive alias in the MYCALL parameter.

  All current versions of APRS support the OVERLAY character feature on some symbols. This feature is encouraged all of the APRS digipeater sites. To use an overlay character, just insert it in place of the "/" that separates the LAT/LONG in the LT lines as follows:
  L if using the paradigm settings but NOT supporting SSn-N
  S if using the paradigm settings and also supporting SSn-N
  1 if OK'd to enable home station WIDEn-N digipeater using WIDE1-1 (very rare use only)

  • LT 1 !4720.20NS12320.45W#PHG5660/W2,WAn,WillapaValley WA7RW

Here's the explanation for determining your Power Height Gain calculation which is part of the LT statement above:

Digits	0	1	2	3	4	5	6	7	8	9	as used in PHG
Power	0	1	4	9	16	25	36	49	64	81	watts
Height	10	20	40	80	160	320	640	1280	2560	5120	HAAT
Gain	0	1	2	3	4	5	6	7	8	9	db
Dir	Omni	NE	E	SE	S	SW	W	NW	N

• For example. We're putting up a new digipeater. The radio output is 10 watts so the P setting is closest to #3. The site elevation is 2500 feet, with the antenna 100 feet up the tower. The surrounding elevation for about 10 miles out averages 300 fee. Therefore 2500+100=2600-300=2300 feet, and the Height setting is closest to #8. The antenna is a medium gain of about 4db, so the Gain setting is #4. It's an omni directional antenna so the Direction setting is #0. Therefore the correct setting is PHG3840.
  
  So to put it all together in a complete setting:
  

  LT 1	!	4720.20N	S	12320.45W	#	PHG5660	W2,WAn,WillapaHills WA7RW
  LTs 1-4	Exclamation Point	Latitude in degrees, minutes, 10ths of minutes and N hemisphere	Overlay setting which means it's a WIDEn-N and SSn-N digipeater	Longitude in degrees, minutes, 10ths of minutes and W hemisphere	Designates the APRS icon as a green star	Power, Height, Gain, as calculated above	Tells all the default setting for this area is WIDE2-2, that SSn-N digipeating is supported for WAshington, geographical reference, and callsign of the system operator

• LTP: The LTP parameter tells the TNC where to send the LT buffers. Each LT buffer can be sent to different destinations if so desired. Since in the APRS concept, objects that are further away are of less importance that objects that are closer, we can tailor the output of the digipeater so that we tell users close by about the digipeater often. Users further away get informed less often, and users even further get informed even less. This is done by the combined effects of the BLT and LTP parameters. Remember that packets originated from a digipeater effectively get an extra hop since they start out from a digipeater. Local users sending via WIDE3-3 hit the digi for their first hop. The second hop is acted upon by the next layer of digis. When packets are originated by a digi, the first hop is acted upon by the same digis one layer out that were handling the user packets as a second hop. The digipeater originated packets in effect get an extra hop.
  • LTP 1 APN382 This simply sets a destination address with no hops enabled. This combined with the BLT 1 timing makes this packet go out to locals at 00 and 30 minutes after the hour.
  • LTP 2 APN382 This simply sets a destination address with no hops enabled. This combined with the BLT 2 timing makes this packet go out to locals at 10 and 40 minutes after the hour.
  • LTP 3 APN382 VIA WIDE2-1 This sets a destination address with one hop enabled. This combined with the BLT 3 timing makes this packet go out one hop at 20 minutes after the hour.
  • LTP 4 APN382 VIA WIDE2-2 This sets a destination address with two hops enabled. This combined with the BLT 4 timing makes this packet go out two hops at 50 minutes past the hour. NOTE: We don't use WIDE1-1, as that would cause any fill-in digis in range to digipeat the packet. That would not be desirable. By using WIDE2-1, only the main digipeaters will act upon the packet.
    
• MYCALL: The NWAPRS group suggests that a descriptive alias be used rather than a callsign. When the MYCALL is substituted into a packet, it is easier for the end user to see where packet has been. It is easier to figure out where a packet has been when the list shows KOPEAK,SIGNAL,MOXIE*, rather than WA7RW,N3EG-10,KC7WFD-10. Just remember to include the control operator callsign in the LT buffer if you use a descriptive alias to stay legal.
  
• UNPROTO: This sets the destination address and path that any UI packets ORIGINATED from this station follow. In this configuration only the BEACON packets will follow this path.
  • APN Network nodes, digis, etc
  • APN3xx Kantronics KPC-3 rom versions (ver 8.2=APN382, ver 8.3=APN383, ver 9.0=APN390)
  • APN9xx Kantronics KPC-9612 Roms
  • APNAxx WB6ZSU's APRServe
  • APNK01 Kenwood TM-D700
  • APNMxx MJF TNC roms
  • APNPxx Paccom TNC roms
  • APNDxx DIGI_NED
  • APNUxx UIdigi
    
• UIDIGI: This routine allows up to 4 aliases to implement simple callsign substitution digipeating. UIDIGI implements a rudimentary anti-duping routine. The TNC will check to see if this packet originated from or has already been digipeated by itself by looking for its MYCALL anywhere in the packet. Because the UIDIGI routine is run before UIFLOOD and UITRACE, we can use UIDIGI to trap paths that are considered abusive. By including the high value WIDEn-N aliases here, we still digipeat the user's packet once, but it gets marked as complete, and will not activate any more digipeaters. 
  • UIDIGI ON WIDE4-4,WIDE5-5,WIDE6-6
  • If you have a KPC-3 v8.2 TNC with release xxxx-7265 or earlier, as many
    of you have, you need to set:
    
    UIDIGI ON WIDE1-1,WIDE4-4,WIDE5-5,WIDE6-6
    
    You can check the version of TNC firmware by connecting to the TNC, and issuing the command: Version
    
    The TNC will respond with something like this:
    
    KPC3-3F427265-8.2
    
    Where:
    
    XXXX-XXXX7265 v8.2
    
    is the important part to check. Any version of 8.2 prior to and including 7265 exhibit this bug.
    
    These versions of firmware have a small bug in the UITRACE routine that can be overcome by changing the UIDIGI setting.
    
    The bug causes the TNC to insert it's callsign has-been-digipeated bit set on the name of the digipeater instead of on the used up WIDE1 path.
    
    You can find evidence of the bug when monitoring the RF stream
    
    Incorrect behavior looks like this: KOPEAK*,WIDE1,WIDE2-2
    Proper behavior looks like this: KOPEAK,WIDE1*,WIDE2-2
    
    This bug does not appear in any version of the KPC-3+ firmware.
    
• UIFLOOD: This routine used to support the old WIDEn-N alias. It is now being used to implement the SSn-N alias. The ID tag is now enabled to allow limited tracing of digipeater paths. The 30 parameter sets the time that a packet checksum is kept in memory to eliminate duplicates. The anti-duping routine used here is totally separate from the one used by UIDIGI. A GPS equipped Mobile running with position reports every 15 seconds will not get blocked by this, as the packet payload has changed.
  • UIFLOOD WA,30,ID
    
• UITRACE: This routine used to support the old TRACEn-N alias. It is now being used to implement the WIDEn-N alias. This allows full tracing of digipeater paths. The 30 parameter sets the time that a packet checksum is kept in memory to eliminate duplicates. The anti-duping routine used here is totally separate from the one used by UIDIGI. A GPS-equipped mobile running with position reports every 15 seconds will not get blocked by this, as the packet payload has changed.
  • UITRACE WIDE,30