remotetrx.conf man page
remotetrx.conf — Configuration file for the SvxLink remote transceiver server
remotetrx is the SvxLink remote transceiver server. This man-page describe the configuration file format for it.
The RemoteTrx application can handle more than one transceiver at a time. You may for example want to handle both a 2m and a 70cm receiver on a site. One sound card is sufficient for doing this since the left channel can be used for one receiver and the right channel can be used for the other receiver. The Global/TRXS configuration variable is used to tell the RemoteTrx application which transceivers to set up. Each transceiver have an uplink that is used to interface to the main SvxLink server. The most common type is the net uplink which link to the main SvxLink server over the Internet using TCP/IP. It is also possible to have an uplink via RF but the functionality is then limited.
The term "uplink" might be a bit confusing for some people. In this case it does not refer to any specific direction in which the data or audio is flowing. It's just the name for the link up to the main SvxLink server.
RemoteTrx look for configuration files in a number of places. First it tries to find a user specific configuration file. It will look for a user specific configuration file in two places: $HOME/.svxlink/remotetrx.conf. If no user specific configuration file can be found, remotetrx will look for the system wide configuration file /etc/svxlink/remotetrx.conf. The --config command line option may also be used to specify an arbitrary configuration file.
The configuration file is in the famous INI-file format. A generic example of how such a file might look like is shown below.
This is a simple format that contain name=value pairs that belong to a section. In written text, a specific configuration variable can be referred to as SECTION1/VALUE2 meaning "configuration variable VALUE2 in section SECTION1".
The same variable name can exist in two different sections. For example VALUE1 in section SECTION1 have the value 1 and VALUE1 in section SECTION2 have the value 2. Values containing spaces at the beginning or end of the line must be surrounded by citation characters (see SECTION1/VALUE2). Likewise with a multi line value (see SECTION1/VALUE3).
Here is the description of all configuration variables that remotetrx understands. The configuration variables are described section for section.
The Global section contains application global configuration data.
This configuration variable specify a comma separated list of transceiver configuration sections.
Specify the path to a directory that contain additional configuration files. If a relative path is specified, the path will be relative to the directory where the main configuration file is at. All files in the specified directory will be read as additional configuration. Filenames starting with a dot are ignored.
This variable specifies the format of the timestamp that is written in front of each row in the log file. The format string is in the same format as specified in the strftime(3) manual page. The default is "%c" which is described as: "the preferred date and time representation for the current locale". The environment variables LC_TIME, LC_ALL and LANG will affect how this time format will look. For example, setting LC_TIME="sv_SE.UTF8" will give you swedish timestamp representation. Other examples of format specifiers are:
- %d - The day of the month as a decimal number (range 01 to 31)
- %b - The abbreviated month name according to the current locale
- %Y - The year as a decimal number including the century
- %H - The hour as a decimal number using a 24-hour clock (range 00 to 23)
- %M - The minute as a decimal number (range 00 to 59)
- %S - The second as a decimal number (range 00 to 61)
So, TIMESTAMP_FORMAT="%d %b %Y %H:%M:%S" would give a timestamp looking something like: "29 Nov 2005 22:31:59".
This configuration variable determines the sampling rate used for audio input/output. SvxLink always work with a sampling rate of 16kHz internally but there still are som benefits from using a higher sampling rate. On some sound cards the filters look pretty bad at 16kHz and the amplitude response will not be uniform which among other things can cause problems for the software DTMF decoder.
Some sound cards also sound very bad at 16kHz due to insufficient anti-alias filtering or resampling effects. These, often cheeper, sound cards sound OK at 48kHz.
The downside of choosing a higher sampling rate is that it puts a little bit more load on the CPU so if you have a very slow machine (<300MHz), it might not have the computational power to handle it.
Supported sampling rates are: 16000 and 48000.
Use this configuration variable to specify how many channels to use when opening a sound card. For normal sound cards the only practical values to use are 1 for mono and 2 for stereo. The latter is the default.
When using the sound card in stereo mode it is possible to use the left and right channels independenly to drive two transceivers. When using the sound card in mono mode, both left and right channels transmit/receive the same audio.
- /etc/svxlink/remotetrx.conf (or deprecated /etc/remotetrx.conf)
The system wide configuration file.
Per user configuration file.
Additional configuration files.
Tobias Blomberg (SM0SVX) <sm0svx at users dot sourceforge dot net>
svxlink(1), svxlink.conf(1), remotetrx(1), siglevdetcal(1)