Configuring AGWPE Ports

SV2AGW's AGW Packet Engine provides a multiple-TNC interface supporting both physical hardware TNCs and a software "soundmodem" working through the PC's sound card and an associated port used for PTT. Any number of the ports defined on the local AGWPE server can be accessed as YAAC ports.

To add a new AGWPE port, click the Add button on the Configure Ports tab. The port editing dialog will appear. Set the port type to AGWPE.

AGWPE config panel screenshot

The other parameters you will need to specify for the port are:

the IP address of the host running the AGWPE server; if left blank, this means the same computer as YAAC is running on. If the AGWPE server is accessed on a non-standard TCP port number (default is port 8000), the TCP port number can also be specified. The port for the AGWPE server can be seen in the AGWPE Interface Setup dialog as shown below; other emulating programs will have different configuration interfaces.
if accessing the AGWPE server on a different computer than the one running YAAC, you will probably need to specify the username and password configured in the AGWPE server to control access to its services; if accessing a machine-local AGWPE server, you can probably leave these fields blank. This should probably be left blank for AGWPE emulators like DireWolf or LDSPED.
the name of the AGWPE TNC "port" to use, as named through AGWPE's own configuration user interface.
The callsign you will be using to identify your transmissions over this port. This should be your legal government-assigned callsign with an optional numeric SSID suffix from 1 to 15.
Whether or not you want to allow YAAC to make transmissions through the port. If left disabled, you will only be able to monitor APRS traffic through this port. You must specify a callsign to be able to transmit.
The sub-list of aliases that will be digipeated through this port, based on the total list of known aliases defined in the general configuration. If YAAC receives a message with one of the checked digipeat aliases and this port is enabled for transmission, the message will be re-broadcast through the radio on this port. If no aliases are selected, this port will not digipeat. Multiple aliases can be selected. The aliases must also be enabled for digipeating on the configuration dialog's Digipeat tab.
Which of potentially several beacon definitions will be transmitted through this port. If none is checked when the port configuration is saved, the default beacon will be used (and will show up as checked when this configuration panel is next opened). To specify that a beacon should not be sent out this port, a beacon should be selected that is not enabled on the Beacon tab of the expert-mode configuration dialog.
Whether transmission through this port should be delayed until an assigned timeslot at some offset after the beginning of a repeating interval.

Once you have the settings the way you want them, click OK. Ensure that the TNC is connected to AGWPE before you click OK. At that time, YAAC will begin using AGWPE as a communications proxy.

Other programs for other platforms emulate the functionality of the AGWPE server daemon. These include ldsped (for Linux systems using the kernel AX.25 support), Sivan Toledo 4X6IZ's soundmodem program, DireWolf, and the UZ7HO soundmodem.