Discussion in 'General Technical Questions and Answers' started by KA0ZIS, Aug 20, 2008.
Can anyone tell me how to configure the KPC3 for stand alone (home base, not mobile) use for APRS?
It looks like there are several example configs available via Google.
Try these settings. They worked for me after changing the obvious callsign, mynode, and the appropriate other location specific settings.
Initialization file for configuring KCP3+ as an APRS digipeater
Find and replace "callsign" throughout this file with the desired callsign.
Edit the LT1 through LT4 lines to include the coordinates and PHG of the digipeater
along with any beacon message string desired.
Edit the LTP1 through LTP4 lines to reflect the desired paths to be used for
beacons at the time intervals defined in BLT1 through BLT4.
After editing, delete this commented section and save the file under a new name.
Use a terminal program such as Procomm or Windows HyperTerminal to connect with
the KPC3+ Verify you can get a CMD: prompt, type commands into the KPC3 and see
responses. Then do a text file upload to read this file into the KPC3+ Set the
terminal program to add a delay of 100-200mS between lines to give the KPC3 time
to process each line.
Note that this listing is a DISPLAY dump from an already-configured KPC3+. The TNC will choke on this listing if you just try to
edit and upload this list. This version has been edited for the correct command for SETTING, not just Displaying the settings.
The user of this list is solely responsible for the settings so verify any changes are correct for your use.
BEACON EVERY 10
BLT 1 EVERY 00:30:30
BLT 2 EVERY 00:10:00
BLT 3 EVERY 01:20:00
BLT 4 EVERY 01:50:00
BTEXT callsign-3 APRS Digipeater
BUDLIST OFF NONE
CONLIST OFF NONE
CTEXT You are being re-routed to the PBBS
CTRL A OFF
CTRL B OFF
CWID EVERY 0
CWIDTEXT DE callsign
DAYSTR mm/dd/yy hh:mm:ss (edit as needed)
LLIST OFF NONE
LT 1 !3823.74NN12041.37W#PHG0000/A=000480 beacon message (Note 1: /A=xxxxxx is your altitude. This is optional)
LT 2 !3823.74NN12041.37W#PHG0000/A=000480 beacon message (Note 2: Edit the beacon message to suit your needs)
LT 3 !3823.74NN12041.37W#PHG0000/A=000480 beacon message (Note 3: PHG settings are explained at end of this document)
LT 4 !3823.74NN12041.37W#PHG0000/A=000480 beacon message
(example: LT 1 !4251.96NS07117.84W#PHG6570/A=000480 Ryan Hill; South Derry, NH
LT 1 - 4 should all be the same. The first set of numbers are your latitute and longitude. (Important-make sure that the ! character is in front of first digit) the seconds are in decimal.
ie: 15 seconds would be entered .25 30 seconds as .50 etc.
PHG settings are explained at end of this document
LTP 1 APN83
LTP 2 APN83
LTP 3 APN83 VIA WIDE2-1
LTP 4 APN83 VIA WIDE2-2
PACTIME AFTER 10
PBFORWRD NONE EVERY 0
PBLIST OFF NONE
PBLO NEW VARIABLE
RTEXT password string
UIDIGI ON WIDE1-1,callsign
The 7-byte PHG (phgd) Data Extension specifies the transmitter power,
effective antenna height-above-average-terrain, antenna gain and antenna
directivity. APRS uses this information to plot radio range circles around
The 7 characters of this Data Extension are encoded as follows:
Characters 1–3: PHG (fixed)
Character 4: p Power code
Character 5: h Height code
Character 6: g Antenna gain code
Character 7: d Directivity code
The PHG codes are listed in the table below:
phgd Code: 0 1 2 3 4 5 6 7 8 9 Units
Power 0 1 4 9 16 25 36 49 64 81 watts
Height 10 20 40 80 160 320 640 1280 2560 5120 feet
Gain 0 1 2 3 4 5 6 7 8 9 dB
Directivity omni 45 90 135 180 225 270 315 360
The height code represents the effective height of the antenna above average
local terrain, not above ground or sea level — this is to provide a rough
indication of the antenna’s effectiveness in the local area .
The height code may in fact be any ASCII character 0–9 and above. This is
so that larger heights for balloons, aircraft or satellites may be specified.
: is the height code for 10240 feet (approximately 1.9 miles).
; is the height code for 20480 feet (approximately 3.9 miles), and so on.
The Directivity code offsets the PHG circle by one third in the indicated
direction. This means a front-to-back ratio of 2 to 1. Most often this is used
to indicate a favored direction or a null, even if an omni antenna is at the site.
An example of the PHG Data Extension:
PHG6570 means a power of 25 watts, an antenna height of 160 feet above the average local terrain,
an antenna gain of 7 dB and maximum gain omnidirectional. PHG6573 would be same with directivity
to the southeast or 135 degrees.
nice job of explaining the settings
73 de ke6anm