Click on Interfaces, then Properties.
An "Installed Interfaces" box should appear. This box will allow you to add, delete, and modify the properties of various devices you may want to use with Xastir.
Current options are:
To add a device, click on the add button. A "Choose Interface Type" box will appear. Click on the type of device you would like to add. Then click the Add button in the "Choose Interface Type" box. Properties for that device will appear. Fill out the requested information and click ok.
To delete the device, click on the device you wish to delete and then click the delete button.
To modify the properties of a device, click on the device you wish to modify, then click the properties button. The properties for that device will appear. Change the information you want and click ok.
More specific help is available under the help topics of each interface type below:
This section covers adding or modifying Serial TNC's or Serial TNC's with a
GPS on a HSP cable.
If you have a HSP cable, which allows you to share the TNC port with a GPS unit you may choose a TNC with GPS (HSP Cable). This is a special cable and may not work on all computers/GPS/TNC combinations. If you use this device the TNC and the GPS should be set to the same communications parameters. Generally 4800 bps, 8 data bits, no parity, and 1 stop bit.
The TNC Port is the Unix device that the TNC (or TNC and GPS) is hooked to. Normally you can use /dev/ttyS0 (com1), /dev/ttyS1 (com2) etc..
Now set the bps rate under port settings, and the parameters under port style. Port Style setting 8N1 is used for 8 data bits, No parity and 1 stop bit. 7E1 is used for 7 data bits, even parity and 1 stop bit. 7O1 is used for 7 data bits, odd parity, and 1 stop bit. These parameters must match your TNC and GPS.
Choose the correct IGate operation for this device. You may have several TNC devices, and this option can be different for each device. If you are not running an IGate leave it at the default option of "Disable".
Enter up to three UNPROTO paths. Xastir will assume the XX VIA part of the UNPROTO path. There are three paths allowed so that your signal will be heard if conditions are bad. XASTIR will cycle through each one that is filled in, one per transmission time. If you are local to a digi, just a WIDE may be a good choice. If you are using low power and/or are distant from a digi then RELAY, WIDE may work better. Or if you know the call of your closest digi you may use XXXCALL, WIDE. Most of you will only need one path. If you are in a remote area and your signal is difficult to get out you may need more. Check with a local group and ask what path may be best for your area. Some areas use the more efficient flooding protocols, in which case you might use WIDE3-3 or RELAY,WIDE3-3.
TNC Startup and Shutdown files: These fields specify a filename that is
located in the /usr/local/xastir/config directory. Each file is a standard
text file containing any commands you would like to send your TNC at the time
the device is activated (startup file) or shut down.
These hybrid interface types implement the options of both serial TNCs and GPSs. Please consult the configuration help for both serial TNCs and serial GPSs for further information on the configuration of these devices.
This section covers adding or modifying AX.25 TNC devices. AX.25 devices can
be any device that uses the Linux AX.25 drivers. This is a kernel level
driver, and device such as a Baycom or a sound modem can be used as a TNC.
These devices must be set up and running before Xastir can use them.
Choose the correct IGate operation for this device. You may have several TNC devices and this option can be different for each device. If you are not running an IGate leave it at the default option of "Disable".
Enter the AX.25 Device name you specified in the axports file for this device.
Enter in up to three UNPROTO paths. Xastir will assume the XX VIA part of the UNPROTO path. There are three paths allowed so that your signal will be heard if conditions are bad. If any of these are filled in XASTIR will cycle through one of them at each transmission time. If you are local, just a WIDE may be a good choice. If you are using low power and/or are distant from a digi then RELAY, WIDE may work better. Or if you know the call of your closest digi you may use XXXCALL, WIDE. Most of you will only need one path. If you are in a remote area and your signal is difficult to get out you may need more. Check with a local group and ask what path may be best for your area. Some areas use the more efficient flooding protocols, in which case you might use WIDE3-3 or RELAY,WIDE3-3.
NOTE: To use AX.25 devices with Xastir you will need to run the program as
"root". If you want to run Xastir as another user you may want to set the
suid bit on the Xastir program file. Please see the README.1ST for more
information; current Xastir drops the extra priveleges but has not been audited
for exploits. Use in this fashion in a multi-user environment at your own risk!
Set the serial port device for your GPS unit. Common values of /dev/ttyS0 (COM1) or /dev/ttyS1 (COM2) can be used.
Now set the bps rate under port settings, and the parameters under port
style. Port Style setting 8N1 is used for 8 data bits, No parity and 1 stop
bit. 7E1 is used for 7 data bits, even parity and 1 stop bit. 7O1 is used for
7 data bits, odd parity, and 1 stop bit. These parameters must match your GPS.
Most GPS units will use 4800 bps and 8,n,1.
If you need to share the GPS data with different programs or machines, this
option is best. Xastir will work with gpsd which will allow several
connections to share your GPS data.
Set the host name (or IP address) and the port number for the gpsd host on your network.
Internet Servers allow you to send and receive data for all over the world.
Enter the host name (or IP address) and the port number of the Internet Server you want to contact. A list of possible servers in in README.1ST.
Enter a valid pass-code to validate your connection, this will allow your data to be transmitted via an Igate. If you don't have a pass-code, use the included "callpass" program to generate one. Note that passcodes are dependent on callsigns. From the src directory, "make callpass" should create the executable if it isn't already compiled.
Selecting "Reconnect on failure" will tell Xastir to try to reconnect when the
data stream has failed.
Set the serial port device for your WX unit. Common values of /dev/ttyS0 (COM1) or /dev/ttyS1 (COM2) can be used.
Now set the bps rate under port settings, and the parameters under port
style. Port Style setting 8N1 is used for 8 data bits, No parity and 1 stop
bit. 7E1 is used for 7 data bits, even parity and 1 stop bit. 7O1 is used for
7 data bits, odd parity, and 1 stop bit. These parameters must match your WX
unit. The Data Type option will allow you to override what type of serial data
the program will look for. The auto-detect feature will first look for Weather
data in a binary type as the Radio Shack WX-200 uses. If no binary data is
found in the stream, Xastir will look for an ASCII type of WX station (like
Peet Bros.).
Xastir can use WX data servers such as wx200d. wx200d will allow several network connections, thus sharing the Weather data with several programs or computers.
Enter the host name (or IP address) and the port number of the WX data server you want to contact.
Selecting "Activate on start up" will tell Xastir to look for this device and set up communications with it when the program first starts.
Selecting "Reconnect on failure" will tell Xastir to try to reconnect when the data stream has failed.
As before the Data Type will override the auto detection.