HELP FIX APRS 144.39!
MUST READ FOR APRS USERS!
The 144.39 APRS network is actively undergoing changes. Why is this
happening? A overview of the problems with 144.39 and the overall plan
to fix it are outlined here:
http://web.usna.navy.mil/~bruninga/aprs/fix14439.html
These changes have been discussed, poked, prodded, and tweaked for many
months now by participants on the APRS-SIG and we are finally at the
point where implementation has begun.
If you operate a digi, please review the following document which
outlines the proper setup for the Maryland/Virginia area:
http://web.usna.navy.mil/~bruninga/aprs/digi-settingsMD.txt
Specific setups for digi's are here:
KPC3+ - http://web.usna.navy.mil/~bruninga/aprs/kpc3+settings.txt
PacComm - http://web.usna.navy.mil/~bruninga/aprs/PacComm-settings.txt
APRS users, at a minimum, please CHECK
YOUR PATH and make sure it is appropriate.
The new accepted universal path is WIDE2-2. This will get your station
on the map in the local area and it is almost guaranteed to get you to
an IGATE so that you show up on Findu.
For details about user path setups, refer to this:
http://web.usna.navy.mil/~bruninga/aprs/digi-users.txt
To stay up to date on the evolution of APRS, join:
The
APRS SIG (special interest group)