Remark: Character ~ (tilde) is short cut of user home directory (bash# echo $HOME).
Files which are described below are saved in plain text format. Is possible to edit these files but it is necessary to keep format of files. In other case Tucnak shouldn't work properly.
- 1 Binaries
- 2 Configuration
- 3 Call database
- 4 DXC files & others
- 5 Contest files
- 6 Output files
Is one binary file. If Tucnak is install from source code it's installed to /usr/local/bin. If Tucnak is install from package it's installed to /usr/bin mostly. On Debian it's /usr/bin/tucnak2 and command tucnak2 is found via /etc/alternatives.
Suided binary allows to access to /dev/console for PC speaker control
Configuration file of Tucnak program. When it don't found configuration file it reads from internal hardcoded default.
This file has the same structure as tucnakrc file. Is determine to set specific local options. Tucnak only reads this file after loading tucnakrc. It is necessary to create and maintain it manually.
File with apair callsign-locator. Each callsign has saved maximally two locators. Format is similar to Taclog's taclog.c_w but not same when one call has two wwls. Format is:
CALL WWL YYYYMMDD QRV
DR5A JO30EM 20071006 CEGHK
Second locator is saved as next line.
Here you can save first names of operators and say them 'Hello John' :-). Tucnak updates this database on demand from DL8EBW database. Of course you can maintain it manually.
DXC files & others
All these files are optional. Tucnak is reading these when are existing, in other case uses own hardcoded defaults.
File with information about DXCC countries. Each country has saved information about possible large squares and centre of activity in the country. Tucnak doesn't write to this file. Format of file is:
# 1th row - The official prefix of the DXCC # 2nd row - The list of WWL in the DXCC (separated by a gap). # The first WWL is the most effective one or midlands # or Capital City of DXCC. # 3rd row - The most effective WWL from JN69UO # There is a free row between DXCC's # OK JN79 JO70 JO60 JO80 JO90 JN69 JN89 JN99 JN68 JN78 JN88 JN98 JO71 JN89JM JO80IA
Follows up information to tucnakdw. Tucnak doesn't write to this file. You can download new version from http://www.country-files.com/cty/index.htm and place it into ~/tucnak.
This file contains information about contest as kind of pointing, etc. Tucnak doesn't write to this file.
Each contest is saved to differed directory. Name of directories is created from date of contest e.g. ~/tucnak/2003083.1. It is possible to have many contest in one day or one contest on one computer under one user (thought telnet, ssh) with many running Tucnaks. Each contest with the same date has different number behind point.
Files in ~/tucnak/<date>:
Named <letter>.txt e.g. c.txt, e.txt. This files are main files for individual bands. Files use information about station, QTH, points of both finished and unfinished contacts. Format is compatible with EDI format and should be accepted by contest comitee. Files has DOS end of line (`\n' `\r') for compatibility.
Are <letter>.swp eg. c.swp, e.swp. Here is saved all typed text from input line ended by Enter key. You are able to reconstruct all contest exchange manually from this file.
Contains information displayed in start of contest as date of contest, callsign and name of contest.
Content of log window.
Information about received skeds
Content of talk window. That's good idea to read after contest :-)
Commonly files are saved to contest directory.
Filenames have format YYYYMMDD_CALL.adif. Exported are all qsos into one file.
Files are named CathegoryCall.edi, f.e. 06OK2M.edi. Format is very similar as txt files, the only one difference is missing section [TUCNAK extension].
By pressing F1 you can make screenshot of Tucnak window. ALT+F1 takes snapshot only of top dialog/window. Filenames are in format snapN.png where N is number 0, 1, 2, ... Screenshot are saved to contest directory or in ~/tucnak/ when no contest is opened.
Contacts from all bands are saved in YYYYMMDD_CALL.html. Files are created with tag <IMG src="snap0.png">. Recommended way is to create one screenshot (maybe with map) and modify width and height arguments in IMG tag.