Parrot Controller

ParrotController.exe [-nolog] [-gui] [-logdir directory] [-confdir directory] [config name] parrotcontroller [-nolog] [-gui] [-logdir directory] [-confdir directory] [config name] parrotcontrollerd [-daemon] [-nolog] [-logdir directory] [-confdir directory] [config name]

All versions have an optional parameter which signifies the configuration to be used, and this must be set on the command line when running as well as configuring the repeater. This name will appear on the title bar as well as affecting the name of the log file used. The location of the configuration file, which is used when running under Linux is normally found in the /etc directory. The -confdir option allows the location of the users’ home directory to be set explicitly, it is also a valid option under Windows but performs no function. The -daemon command line switch is used on the command line version to put the program into the background, and to disassociate it from the controlling terminal. The program will return immediately, but using the ps command will show that it is running in the background. A log of actions and errors is to be found in the file ParrotController-YYYY-MM-DD.log where YYYY-MM-DD is the current date. This file is normally found in the users home directory under Windows and /var/log under Linux, but this location may be overridden by the -logdir command line option. The log may be disabled by giving the -nolog option on the command line. Logging is still performed, but it goes to stderr and therefore may easily be ignored, or redirected to another target. A copy of the last three lines of the log is displayed at the bottom of the GUI screen. The Parrot Controller is designed to act as an alternative to a full gateway either for testing, or for operating in a different mode, as a D-Star Parrot. Firstly the Parrot mode needs to be selected in the D-Star Repeater, and the Parrot Controller needs to be configured. The Parrot Controller has two modes, Parrot and Beacon. In Beacon mode, the Parrot controller will keep sending the same DVTOOL file to the repeater as pre-defined intervals, therefore acting as a repeater. The file and the interval are selectable. DVTOOL files can either be created by using my D-Star Client software, or from DVTOOL program, or using this software as a Parrot and saving the file(s) generated. The configuration is relatively simple. The configuration is made up of four tabs.

The Mode Tab

This sets the operating mode, Parrot or Beacon.

The Parrot Tab

This has to be set when running in Parrot mode. There are two settings, the Turnaround Time and whether to keep the intermediate DVTOOL files. The Turnaround Time is the delay between retransmitting the received data after receiving it. Two seconds is the lowest feasible value, but longer may be needed if the connection to the repeater program is not local. The program creates temporary DVTOOL files which it then retransmits, these would normally be deleted after transmitting, but by setting the Keep File option to Yes, then they will be kept. They are stored in the users’ home directory.

The Beacon Tab

This is used to set the configuration in Beacon mode. A suitable DVTOOL file should be selected, this is easiest done by pressing the Browse... button and selecting the file wanted. The other setting is the time interval between sending the beacons.

The Network Tab

This sets the connection information to the Repeater software, and is required to be valid whichever mode the software is operating in. Many of the comments about setting the Network options in the repeater configurations also apply here.

In Parrot mode, the software will listen for a valid D-Star transmission that is being received by the repeater, and save the contents in a temporary DVTOOL file, which is saved in the users home directory. Once the transmission has ended, this software waits two seconds and then resends the data back to the repeater to be retransmitted. At the end of this transmission, the file is either kept or deleted, depending on the setting in the configuration of the Parrot Controller. These DVTOOL files can be used for the beacon later. Normally the GUI is disabled but it may be switched on in the Release build by specifying the -gui option on the command line, or by clicking on the View menu and enabling the GUI Updates.