USING PRE-APRS (older) TNC FOR HOME OPERATIONShttp://www.aprs.org/fix14439.html
Extracted from Bob Bruninga, WB4APR wb4apr att amsat.org
web page, found at: http://www.aprs.org/
You do not have to purchase a brand-spanking new APRS/GPS capable TNC in order to participate in APRS activities.
Many older TNC's can be used, including the AEA PK-88, TAPR-2, TAPR-2 clones made by various manufacturers, etc.
These units can be used at home stations or as mobile APRS stations.
For a home station, a simple APRS beacon can be configured.
The station position can be manually set (no need for a GPS receiver) in the beacon text and broadcast at 15 to 30 minute intervals.
For mobile APRS, these TNC's require a computer (or microcontroller) attached and running APRS software in order to update the GPS position.
Some of these older TNC's are not suitable as WIDE digipeaters, and as mobile/portable trackers, unless an additional computer is attached constantly.
TAPR-2 clones can be upgraded with new EPROM's to make them GPS-enabled.
There are certain caveats with this, because the original processor inside many TAPR-2 TNC's is slow and may not handle continuous sentences from a GPS.
If your GPS has enable/disable for individual sentences then you may want to turn off all strings,
and then re-enable just the $GPRMC or the $GPGGA string so the TNC can keep up with the data.
See the TAPR Site for information about updated EPROMS.
These updated EPROM's are only necessary if you wished to run a mobile APRS setup with no computer attached.
The processor in some TNCs (Paccomm Tiny-2) can be upgraded (~ 10 MHz).
When using an older TNC for your house/fixed location and WIDE1-1(old relay) station,
insert your position fix in the BTEXT, set the TNC to beacon at 30 minute intervals, and set up an alias of "WIDE1-1". Here is an example:
unproto aprs via WIDE2-1
beacon every 30 (might need to be 600 depending on TNC)
The above example is an APRS Digipeater, here is another example for a simple APRS beacon.
Details on various options and configurations can be found on Bob Bruninga's web page: http://www.aprs.org
Setting up an APRS Beacon using an AEA PK-88; an interfaced 2-meter radio set to 144.390 MHz (APRS freq.);
power supply for the radio and TNC; and 2-meter antenna.
This specific example was used for setting up the Beacon at the Elmhurst, IL EC location.
BTEXT (step #4 below) used for this specific beacon example:
!4154.61N/08756.41WoPHG5260 Elmhurst EC QSX 442.875+ yorkradioclub.com
1) Reset to factory defaults to make sure no wierd settings are in it.
2) MYCALL CALLSIGN
3) MYALIAS WIDE1-1, WIDE2-1
4) BTEXT !DDMM.mmN1DDDMM.mmW#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 below)
7) HID OFF <(this is important to eliminate this useless QRM)
That is all there is to it, for these older TNC's.
FOR old PACCOM TNC's WITH CALLSIGN SUBSTITUTION:
set MYA none (available for other use if any)
set MY1 WIDE1-1
set MY2 SAR (to support Search and Rescue)
set MY3 TEMP1-1 (this can be used during field day)
FOR D700's & Kantronics KPC-3+'s THAT HAVE THE UIDIGI COMMAND:
set MYALIAS none (available for other use if any)
set UIDIGI ON WIDE1-1, SAR, TEMP1-1
set UITRACE TEMP, 30 <== this supports TEMPn-N for Field Day
Notice that TEMPn-N support is also encouraged in ALL TNC's that can support it that are NOT otherwise being used as big digis.
This is because ARRL Field Day rules do not permit the use of the existing APRS infrastructure and normal digis for FD.
To show our ability to work in the field, we are supposed to set up temporary facilities.
For this reason, all TNC's not normally used for the routine infrastructure should have TEMPn-N support for use during emergencies (and FD).
Especially this is true of D700 mobiles.
We do NOT want mobiles routinely doing WIDEn-N, but we DO want them available to support special FD and other special events.
By having TEMPn-N support always turned on in all D700's (and all home fill-in digis that can support it) then we can instantly use this system if needed.
For all these TNC's, identify the type of TNC in the TOCALL of the UNPROTO path using the APNxxx TOCALLS below:
APN232 AEA PK232
APNMFJ MFJ TNC
APNTC2 TAPR-2 clone TNC
APN3xx Kantronics KPC-3 rom versions
APN9xx Kantronics KPC-9612 Roms
APNAxx WB6ZSU's APRServe
APNPxx Paccomm TNC with version xx
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 == Bob, WB4APR