Setting up A WIDE1-1 FILL-IN Digipeater                    18 Nov 2005
----------------------------------------------------------------------

The purpose of a WIDE1-1 or FILL-IN digipeater is to provide a way
for passing mobiles in a dead zone to be able to be digipeated out
without that same digipeater adding to the congestion elsewhere by
digipeating every other packet heard from everywhere else.  In 
otherwords, it only responds to mobiles and/or stations that 
explicitly use its callsign in their path.  These digis used to be
called RELAY digis, but that is now obsolete.  The reason is that as
a RELAY only-digi, there was no advantage taken of the perfect dupe-
elimination mechanisms built into the WIDEn-N algorithms.  Thus, in
early 2005 we decided to change all RELAY-only digis over to WIDE1-1.

To use these digis, mobiles typically use the path of WIDE1-1,WIDEn-N.
This way the first hop can be done by ANY digipeater, but all other
WIDEn-N digis will recognize any other dupes and will only process the 
same packet only once.

Fortunately almost any TNC can be used as a WIDE1-1 or FILL-IN digi
because no special algorithms are used.  The TNC is set to digipeat
only packets addressed VIA WIDE1-1 or VIA its own MYCALL.  Further
it does not ID beyond its own DIRECT range, thus, it does not add
any QRM to the network and finally HID is turned OFF so that this
TNC does not polute the spectrum with the every 10 minute HID packet
that is of no value to APRS.

Use these settings to make any TNC into a WIDE1-1 FILL-IN-DIGI:

1) Reset to factory defaults to make sure no wierd settings are in it.
2) MYCALL  CALLSIGN
3) MYALIAS WIDE1-1
4) BTEXT !DDMM.hhN1DDDMM.hhW#W1-1 any_other-comment_here
5) B E 60 (60 is 60-ten seconds (10 minutes in TAPR-2))
6) UNPROTO APNXXX   <The XXX identifies the type of TNC. See list)
7) HID OFF          <this is important to eliminate this useless QRM)
8) DIGI ON

Other than figuring out exactly how your TNC handles time in the
BEACON EVERY command (minutes or 10's of seconds or seconds)...
We want a 10 minute local beacon from all DIGI's.  They are our
lifelines and we need to know which ones are serving us.

That is all there is to it.

Oh, here are the APNxxx TOCALLS to use to identify the type of TNC
you are using:

  APN232 PK232
  APN3xx Kantronics KPC-3 rom versions 
  APN9xx Kantronics KPC-9612 Roms 
  APNAxx WB6ZSU's APRServe 
  APNDxx DIGI_NED 
  APNMxx MFJ TNC roms 
  APNPxx Paccom TNC roms 
  APNTxx SV2AGW's TNT tnc as a digi 
  APNUxx UIdigi APNXxx TNC-X (K6DBG) 
If you are using any other kind of TNC, then choose an APNxxx for
it and let me know so I can add it to the list.  Thanks
de WB4APR, Bob