Files
Remark: The character ~ (tilde) is a short cut of the user home directory (bash# echo $HOME). Under Windows the Tucnak folder is C:\Users\<USER>\AppData\Roaming\Tucnak.
The files described below are saved in plain text format. You can edit them, but you must keep the format of the files. Otherwise Tucnak may not work properly. The files are in UTF-8, so a text such as the name of the contest can contain any character.
Note: the files in /usr/share/tucnak/ are only examples and Tucnak does not read them. The default values are compiled into the Tucnak binary. You can copy the files into ~/tucnak and modify them. Tucnak will then use the files in ~/tucnak instead of the compiled-in data.
Binaries
tucnak
It is one binary file. If you install Tucnak from the source code, it is installed to /usr/local/bin. If you install it from a package, it is usually installed to /usr/bin.
soundwrapper
A setuid binary that allows access to /dev/console for the PC speaker control (Linux only).
Configuration
~/tucnak/tucnakrc
The configuration file of Tucnak. If Tucnak does not find it, it uses the compiled-in defaults.
Call database
~/tucnak/tucnakcw
The file with callsign-locator pairs. Each callsign has at most two locators. The format is similar to Taclog's taclog.c_w, but it is not the same when one call has two WWLs. The format is:
CALL WWL YYYYMMDD QRV
For example:
DR5A JO30EM 20071006 CEGHK
The second locator is saved on the next line.
Also look at Update C_W from contest and Update C_W from band.
If you are connected to ON4KST chat, Tucnak sometimes sends the sh/us command and gathers the locators.
~/tucnak/tucnaknames
Here you can save the first names of operators and say 'Hello John' to them :-). You maintain this file manually.
CALL Name
For example:
OK1ZIA NAME
~/tucnak/qrv
The template for qrv. It is copied to the contest directory when you create a new contest. Note: it is not copied when you create the contest from the network. In that case the qrv database is transferred over the network.
~/tucnak/tucnakmasters
A user definable master.scp database for shortwave. If it is not present, Tucnak uses the compiled-in database (probably not up to date).
~/tucnak/tucnakexcXXX
Like tucnakcw, it contains a database of callsigns, their optional exchanges (EXC, OE) and a date stamp. XXX is the name of the EXC, for example OKRES (Czech districts), but in lowercase (~/tucnak/tucnakexcokres). The format is:
CALL EXC YYYYMMDD
For example:
OK2BKP GKR 20081006
~/tucnak/tucnakvexcXXX
The list of all valid optional exchanges, if verified EXCs are used. XXX is the name of the EXC, for example OKRES (Czech districts), but in lowercase (~/tucnak/tucnakvexcokres). The format is free. Tucnak reads all lines from the file and uses all words separated by spaces or tabs. For example:
APA APB APC APD APE APF APG APH API APJ BBN BBE BKD BKO BKH BME BMB BNY BPZ BPV BPB BRA CBU CCK CJH CPE CPI CPR CST CTA
DXC files & others
All these files are optional. Tucnak reads them when they exist. Otherwise it uses its compiled-in defaults.
~/tucnak/tucnakdw
The file with information about DXCC countries. For each country it contains the possible large squares and the centre of activity. Tucnak does not write to this file. The format of the 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
~/tucnak/cty.dat
It extends the information in tucnakdw. Tucnak does not write to this file. You can download a new version from https://www.country-files.com/ and put it into ~/tucnak.
~/tucnak/tucnakwiz
This file contains information about the contests, such as the kind of scoring. Tucnak does not write to this file. The items are described in Contest options.
Example of the file:
[Region I Standard Contest] pexch= tttype=1 qsoused=1 qsomult=1 qsoglob=0 wwlused=1 wwlbonu=0 wwlmult=0 wwlcfm=1 excused=0 excbonu=0 excmult=0 exccfm=1 exctype=0 excname= rstused=1 defrstr=0 dxcbonu=0 dxcmult=0 qsop_method=1 total_method=1 bands=ABCEGHIJKLMNOPQ [Region I Std test 59 expert] pexch= tttype=3 ...
~/tucnak/tucnakbeacons
The beacon database is maintained by the UK Microwave Group. Tucnak has its own compiled-in database. You can update it online with the menu Edit / Import beaconspot.uk. The website updates the data about once a week. The downloaded data is saved to ~/tucnak/tucnakbeacons for offline use.
Contest files
Each contest is saved to a different directory. The name of the directory is the date of the contest, for example ~/tucnak/20261120. You can have many contests on one day. You can also have one contest on one computer under one user (through telnet, ssh) with many running Tucnaks. Each contest with the same date has a different number after the dot, for example ~/tucnak/20261120.1.
Files in ~/tucnak/<date>:
Data files
They are named <letter>.txt, for example c.txt, e.txt. These are the main files of the individual bands. They contain information about the station, QTH, and the points of both finished and unfinished contacts. The format is compatible with the EDI format. The files have DOS line endings (\r\n) for compatibility.
Swap files
They are named <letter>.swp, for example c.swp, e.swp. All text typed in the input line and ended with the Enter key is saved here. You can reconstruct all contest exchanges manually from this file.
desc
It contains the information displayed at the start of the contest: the date, the callsign and the name of the contest.
log
The content of the log window.
spy
The hosts and bands that Tucnak watches (spy).
talk
The content of the talk window. It is a good idea to read it after the contest :-)
hicalls
It contains the highlighted calls from the DX cluster and the ON4KST chat.
qrv
Some items are updated when you select a line in the KST window.
;DR5A;JO30EM;GHK;G5H3K1;@QRV;1299419310
Each line starts with a semicolon. Then follow the callsign and the locator. GHK are the bands on which this call is QRV. The next item is the number of contacts we made in the last period. A negative number means that we never made a QSO with this call, but other stations did. @QRV is a remark with additional information (@QRV means that the information comes from the qrv script). The last item is the time stamp of when the call was last seen on KST.
chart
It holds information about the files displayed in the chart window.
0;/home/ok1zia/tucnak/20110305/h.txt
Zero means that the record is for the first chart window. The file name (TXT or EDI) follows.
Output files
The files are usually saved to the contest directory.
ADIF
The file name is YYYYMMDD_CALL.adi. All QSOs are exported into one file.
Cabrillo
The file name is YYYYMMDD_CALL.cbr. All QSOs are exported into one file.
STF
The file name is YYYYMMDD_CALL.stf. All QSOs are exported into one file.
SOTA
The file name is YYYYMMDD_CALL.csv.
EDI
The files are named CategoryCall.edi, for example 06OK2M.edi. If the band has no category, the name is CALL_x.edi, where x is the band letter. The format is very similar to the txt files, the only difference is the missing section [TUCNAK extension].
PNG
Press F1 to make a screenshot of the Tucnak window. ALT+F1 takes a screenshot only of the top dialog/window. The file names are snapXN.png, where X is the band letter and N is a number 0, 1, 2, ... (snapN.png when no band is active). The screenshots are saved to the contest directory, or to ~/tucnak/ when no contest is opened.
You can use optipng to reduce image size. Similar tool is advpng but it seems it doesn't work with Tucnak's snapshots.
HTML
Contacts from all bands are saved in YYYYMMDD_CALL.html. It also creates a map and a chart for all bands with at least one QSO.
Wiki
It creates a post-contest report in MediaWiki format, named YYYYMMDD_CALL.wiki. You can use it as a skeleton for a contest story web page. It also creates a map and a chart for all bands with at least one QSO.
System files
- /etc/mtab
- /proc/mounts
- /proc/self/status
- /var/lock/LCK..tty* (or /var/lock/lockdev/LCK..tty*), the lock files of serial devices (made by libzia)