YAAC is a (mostly) platform-independent Java application written by Andrew Pavlin, KA2DDO, for monitoring and contributing to the Automatic Packet Reporting System (APRS) network (invented and trademarked by Bob Bruninga, WB4APR).
YAAC is Free Software; it is an Open-Source program, licensed under the GNU Lesser General Public License, and complete source code is provided. Feel free to create improvements and extensions to YAAC.
YAAC can be used as a stand-alone APRS client, an APRS RF-Internet gateway (I-Gate), or as a AX.25 router. It supports 11 different data reporting views as delivered, and can be extended with user-written "plugins" to add more functionality. YAAC's map rendering does not depend on Internet connectivity, so it can be used wherever a portable computer and radio/TNC can be located.
Here is where the beta release of YAAC can be downloaded. If you plan on joining the beta-test effort, please join our mailing list first. Existing list members can post to the list by e-mailing to firstname.lastname@example.org.
Bug reports can be e-mailed to the above mailing list, submitted to the bug tracker on SourceForge (note you will have to have a free SourceForge account in order to submit tickets, click here to get one if you don't already have one), or submitted to YAAC's private bug-tracking system.
For more information about YAAC, you can read the author's presentation at the 2012 ARRL/TAPR Digital Communication Conference, or watch it on HamRadioNow.
A zip file contains the current binary distribution; unzip this file in a directory on your system, maintaining the internal subdirectory structure of the zip file. This is all that is needed to install the executable distribution. The file YAAC.jar in the directory is the main program; the lib subdirectory contains libraries (both Java and native code) needed to support YAAC. The change notes for the current binary are available here. Those interested in tinkering with the source code under the Open Source GNU Lesser General Public License can download it here or from the SourceForge project page.
The current operating systems supported by YAAC are:
YAAC has been tested on Raspbian (the ARM version of Debian Linux for the Raspberry Pi single-board computer (soft-float ABI version) with the OpenJDK Java runtime and librxtx packages installed, but is still being debugged, as YAAC's current implementation rapidly wears out SD memory cards with logging, and the soft-float ABI causes pitifully poor map rendering speed. Your mileage may vary.
YAAC may also theoretically work on Solaris with SPARC processors, but has not been tested on that Sun platform. YAAC will not work on embedded systems using a headless (non-GUI-support) version of the Java runtime; YAAC requires the Java Abstract Widget Toolkit (AWT) and Swing graphics support to operate. Similarly, due to the lack of AWT support, YAAC will not work on Android either (a work in progress...).
YAAC has been tested with the following hardware, but will work with other compatible hardware:
Equivalent hardware should also work. If you are testing YAAC on a different platform, please let us know what it is, so we can add it to the supported list.
Because YAAC is written in the Java language, you will need to have a suitable version (at least Java 6) of the Java Runtime Environment installed on your system (either just the JRE or the full Java Development Kit [JDK] which includes a copy of the JRE). Either the standard Sun/Oracle distribution, OpenJDK, or a vendor-specific distribution for your platform should work, as long as it is up to the appropriate release of the Java standards. You can test this by getting a command shell on your system and issuing the command
Note that Fedora Core 15 (and possibly some other distros of Linux) has moved the device locking directory to a non-standard location, so the device file locking code in the RXTX library (used by YAAC) becomes confused and is unable to open serial port device files. The current work-around is to change the file permissions and ownership on the /var/lock directory so device lock files can be placed here by YAAC. The YAAC author plans to submit suitable changes to the RXTX project to overcome this limitation, but is presently using the standard 2.2pre2 binary release (bundled in the YAAC.zip file), except for Linux distros; these are using a custom rebuild of the latest 2.2 code (solely to turn on support for non-standard-named serial port devices). The set of library variants provided in the RXTX binary distribution is the major limiting factor regarding platforms upon which YAAC will run; in theory, YAAC could run on platforms without RXTX support, but does not because of the code that searches for the appropriate RXTX native libraries for the executing platform.
Starting YAAC is easy. All you should have to do is double-click on the YAAC.jar file (for environments where the Java Runtime is integrated into the file manager). If this does not work in your environment, obtain a command shell on your system, cd to the directory where you unpacked the YAAC.zip file's contents, and issue the command
java -jar YAAC.jar
Either way, this should bring up the YAAC user interface screen.
If it doesn't, please let us know, reporting any error messages displayed when you attempted to start it.
YAAC doesn't do much without a connection to some source of APRS data. The details are in YAAC's built-in online help, but basically you need to open the File->Configure dialog (we recommend using the configuration wizard for a new installation or if you are new to YAAC), and update the appropriate options to use your callsign and appropriate interfacing equipment to the APRS network (either over the Internet through the Tier 2 APRS-IS servers, or through actual radio equipment via a TNC). Hardware TNCs (whether separate boxes or built-in to modern radio transceivers like the Kenwood TM-D710) will always be connected through a serial port, so your computer will need one for each TNC (RS232 or USB, as appropriate for your TNC hardware). The same applies for GPS receivers.
If you want to use YAAC as an I-Gate (APRS Internet gateway) or otherwise as a transmitter to the APRS-IS backbone on the Internet, e-mail YAAC's author to get an APRS-IS passcode, telling us your amateur radio callsign; without using a valid passcode for your callsign, you will not be able to send any messages to APRS-IS. Note this is a restriction of the APRS-IS network, not of YAAC.
YAAC supports map data produced by the OpenStreetMap project, and has an efficient downloader built into YAAC for pre-processed map data served by the YAAC author. If you would rather do it yourself, you can download a bzipped OSM file for your geographical area from planet.openstreetmap.org or a suitable mirror site (you can download the entire planet file if you like, but it will take a long time). Then follow the directions in YAAC's online help to import the OpenStreetMap data into YAAC's internal map data format.
YAAC also supports world-wide terrain (elevation) data made available to the public domain by the U.S. Geological Survey, through an automatic downloader built into YAAC.
YAAC has extensive built-in help; just click on the Help menu and select Contents to get the help table of contents displayed. Some parts of YAAC also have single-button help; pressing the F1 key on the keyboard will bring up help if the current window being looked at has a help connection. Help is self-contained within the YAAC distribution, so it can be used when YAAC is disconnected from the Internet.
If you have a problem with YAAC, and you can't figure out what to do after reading the help, there are three options:
Either of the bug-tracking systems will require that you establish a (free) account associated with your e-mail address, so the author can contact you for more information regarding your problem.
The author also accepts requests for new features through these means.