PacComm Settings for MD / VA TRACE-only DIGIPEATERs         10 April 2005
-------------------------------------------------------------------------

Although the old original PacComm TRACE-only digipeaters are obsolete, 
under the New n-N Paradigm, they can still be used locall to support the
more locally used WIDE2-2 and lower paths.  Notice that the original 
RELAY, WIDE, SS, TRACE, and TRACEn-N are obsolete and are no longer supported.  
The following  settings will make the PacComm TNC's work locally to
support the New n-N Paradigm:

FIRST:  RESET the TNC to factory defaults to get rid of any hacks and tweaks
that you may have developed over the years.  And install your MYCALL.

SECOND:  Set HID OFF     -  These packets are of no value to APRS

THIRD:  Set up the four Aliases for the New n-N Paradigm.  These will
fully support all WIDE2-2 users, mobile WIDE1-1,WIDE2-1 users and the
visiting WIDE3-3 mobile (for one hop).
  MYA  WIDE1-1
  MY1  WIDE2-2
  MY2  WIDE2-1
  MY3  WIDE3-3

FOURTH:  Set up the Digipeater's POSITION ID and Transmission rate.  We
can get two paths and 2 rates using the UNPROTO and LPATH commands.  Set
one to every 13 minutes direct and one to every 31 minutes via two hops.

BEACON EVERY 78           <== a local  beacon every 12 minutes
UNPROTO APNPxx            <== via direct
LOC E 186                 <== a one-hop beacon every 31 minutes
LPATH   APNPxx VIA WIDE2-2   <== via adjacent WIDE's

Notice:  The UNPROTO and LPATH should use the TOCALL of APNPxx where 
APN identifies it as digipeater firmware.   The "P" identifies it as 
PacComm ROM and "xx" identifies the ROM version.

FIFTH:  Setting your POSITION TEXT:  Your Position packet should tell
users what they need to know about this digipeater.  It goes into the 
BText and LText and should be 100% identical to keep APRS logging software 
from seeing constant changes and logging everyone of them all day long. 

BT !DDMM.hhNPDDDMM.hhW#PHGphgd/11,22,21,33 AARC Radio CLub, etc...
LT !DDMM.hhNPDDDMM.hhW#PHGphgd/11,22,21,33 AARC Radio CLub, etc...

a) After the LAT/LONG# Always include the PHGXXXX  (See DIGIS.TXT)
b) next, a list of the aliases, such as "11,22,21,33" etc
c) The overlay character between the LAT/LONG should now be a "P"
d) There is no need for altitude /A=001377 since this is all included
   in a proper PHG statement.  If you insist, then put it at the end
   so it doesnt take up space on the front panel of the kenwoods.

CONCLUSION:

That's all there is to it.  Please don't diddle with any other 
parameters.  The defaults for those are the correct settings.  If you
dink with them you can only make performance worse.

de WB4APR, bob