Last modified 10 years ago Last modified on 06/20/09 12:50:32

APRS4R Configuration

The APRS4R-Software must be configured after installation. Whilst APRS4R has its own web interface to allow simple configuration it can also be modified manually using the configuration files if you so wish. Since detailed knowledge is required to routinely use the manual route (starting files, YAML Configuration), we therefore suggest that you stick to the web interface.

Web interface

The web interface is accessed via TCP port 8085, therefore it can be viewed by entering http://routerIPaddress:8085/ into your normal web browser. Once you hit enter a simple web page with two links should load. If you click the first link, APRS4R-Webschnittstelle, a dialogue box pops up asking you to sign in. In a default installation, the both the account name and password are aprs4r. After that you should get the following webpage:

The menu on the left side of the screen is as follows:

Status - Displays the general status of the program and announces log data Startup - Allows configuration, automatic start-up and starting profile selection Profiles - Profile administration (export, import, deletion of profiles) Log - Announcement of all log files Setup - Profile configuration (shop, memory, creation of profiles) Interface - Configuration of interfaces (TNC, Internet) Beacons - Configuration of beacons Gateway/Digipeater? - Configuration of Internet gateway or Digipeater Further modules - Configuration of further modules (weather, local server,…) Admin - Administration Password - Password administration Update - APRS4R-Update (Not implemented yet)

The most important thing when editing profiles (with setup) is to note that a profile must be loaded (using the load profile (Laden) button on the Setup page) before any editing can take place. After that, the loaded profile can be modified by adding other interfaces, beacons, Gateway / Digipeater modules and other processes. The changes will only be saved if the current profile is stored (via a profile button on the Setup page). The software must be restarted for any changes to take place. This can be achieved by navigating to the Startup page and pressing "Stoppen" to stop the software and then "Starten" to restart it.

Changing the login password for the APRS4R-Webschnittstelle can be done via the Admin the menu option password. On delivery the password aprs4r is preset for the user aprs4r.

Initial Configuration

The following approach is recommended as a basic APRS4R configuration:

Set up page, add a new profile

Thus a new profile is based on a standard profile and contains a number of preconfigured beacons, in each case a configuration for a Fill-in or a Wide Digipeater and example configurations for weather, XML export and local APRS server.

Attitudes adapt Over the ranges interfaces, beacons, gateway/Digipeater and further modules one can adapt the attitudes of the current profile.

In order to be able to use the existing modules, these must be activated (activated: “”). Used modules cannot be deleted for the sake of clarity from the profile.

Set UP side, there profile store In order to store after the adaptation of the attitudes the profile, one is involved on the set UP side and registers in the associated field a profile name (e.g. mycall.yaml) and presses then the profile storage button.

Starting UP side, there profiles select and start

On the starting UP side the stored profile can be selected now and be started then thereby the APRS4R-Software. After a successful start one can see the last expenditures for log of the APRS4R-Software on the status side.

If the start should fail, one can regard possibly on the log side all log files and a reference on an error get.

manually ¶ Note: Files and attitudes to APRS4R should be edited only then by hand, if one knows exactly, what to be done are (and not, if one thinks that one knows, what to be done is). Due to errors when manual editing the configuration can become incorrect, so that the APRS software cannot be started any longer. Much assistance in the forum or on the mailing list is not to be expected then, since it does not concern a general APRS4R-Fehler, but around a specific user error.

Altogether the configuration of the APRS4R-Software consists of different files, which are put down in several listings.

Configuration files ¶ The actual configuration files (also profiles called) are put down in the listing /etc/aprs4r and possess the file suffix .yaml. The configuration file default.yaml serves as collecting main and may not be changed, since it is overwritten with the new installing or when bringing a new APRS4R-Version in without demand. In this file are a row of configuration examples put down.

Additionally to the APRS4R-Profilen lie still further files in the listing /etc/aprs4r. All files with the suffix .log 4r are configuration files for the used log4r-Bibliothek, normally are not necessary it to make changes at these files.

automatic start ¶ In order to let the APRS4R-Software automatic start with the start of the Routers, two steps are necessary. First must be configured by the command /etc/init.d/aprs4r the enable automatic start of the APRS4R-Startskripts. Additionally it is still necessary to create the file aprs4r in the listing /etc/default and to deposit information there over the profile which can be used.

# START_DAEMON= " false " START_DAEMON= " true "

# active profiles PROFILE= " mycall.yaml "

By means of START_DAEMON= " true " indicated that the APRS4R-Software is to be also really started, the parameter of PROFILES contains then the name the profile, which is to be used.

Backup/Restore? of the Routers ¶