Quick Start
New Contest


Tucnak branch 1

Tucnak 1 is obsolete. Look at Tucnak 2 wiki..

Tucnak is a VHF contest logbook. Tucnak is executable on Linux operating system and also for other UNIX like operating systems. Can be run uder MS Windows with Cygwin library too (older version). You can download Tucnak from

If you register user of BBS OK0NAG you can read the actual version of this dokument by typing command www


Main window

Main window of Tucnak

Graphics polar map

Graphics polar map


Please download Tucnak here

The most important feature

  • The Control of program was took from program Taclog.
  • The support of most EU contests. It's possible to have open more contest logs than one in one time.
  • The export of contest logs to EDI format and generating of contest report (OK VHF activity contest format).
  • You can work on more bands on several computers. Then you have information about QSOs from all bands on all computers. You can open log from one band on several computers (used for the second operating station)
  • Is possible to run more than one process of Tucnak on one computer.
  • All the written items of QSO (or part of QSO) are written also to the swap file. If your computer crashs you can read QSO data from this swap file with simple ASCII editor, e.g. Vim).
  • For CW and SSB keying is possible to use program cwdaemon. Is also possible to transmit CW directly by typing from keyboard.
  • The Automatic saving data to disk and diskette.
  • The Database of couple Callsign and World Wide Locator.
  • The Database of DXCC, valid locators for DXCC, locators with high activity from DXCC or middle locators of DXCC. It uses files cty.dat from K1EA and tucnakdw.
  • Single items (Callsign, WWL, report, etc.) are automaticaly identified and inserted.
  • The searching of typing string (Callsign, WWL) in actual log, in logs from other bands and in the C_W database of couple Callsign/WWL. It runs on background.
  • The cross control couple callsign - locator.
  • The talking with other running Tucnaks similary as in WW-Convers (talk window).
  • The sending of skeds to other (higher) bands.
  • The saving NC QSO and the marking of it.
  • The executing shell in one of tucnak window. You can simple connect it to packet radio by programs for example Node, Call or Telnet.
  • The DX spot handling from shell windows and putting it to the bandmap
  • The Wizard for creating a new contest. It automatically sets parameters of a selected contest
  • It is possible to work with the most kinds of terminals.
  • It is possible to work remotelly by using ssh or telnet (as putty).
  • The basic statistics - number of worked DXCC and WWL, simple text mode map of squares.
  • There is a color world map with worked QSO in graphic mode.
  • The support of many languages if somebody translates it from English or Czech :)
  • Tucnak is a free software distributed under the GNU General Public License.

New features in branch 1

  • The SSB CQ is generated by ssbd program. This program also records whole contest to WAV file by a few possible codings (PCM, ADPCM, x-law, GSM coding).
  • The graphics polar map with contacts and `relevance' of different azimuts.
  • Unrecognized input strings are not deleted but they are displayed.
  • The export to ADIF and HTML formats.
  • Next methods of counting of QSOs (3, 5 - 11).
  • Loading configuration and C_W database over the net.
  • Is possible to write remark for a QSO directly from input line or to set QSL card flag.
  • Improved searching of locator by callsign. That's trying with/without /P.


(For working in text mode)

  • Processor 486 (or other platform)
  • RAM 8MB
  • A bit MB of disk
  • VGA or other console (xterm, vt100), recommended min 80x24
  • glibc 2.2.4 (is maybe possible an older version too)
  • glib 1.2 or 2.x

I used use Tucnak program at notebook 486DX/25, 8MB ram, 100MB disk. This configuration is usable for work on one band. If you want to work on more bands you must run Tucnak at more powerful computer. You can run Tucnak also remotelly at faster hardware.

If you want to run the program on Windows system you need more powerful computer (as pentium II 500 Mhz).

Quick Start

  • bash$ tucnak (Shell prompt)
  • <F9>, Contest defaults. Fill callsign, WWL and adress (PAdrX).
  • <F9>; Setup, Band options. Settings working bands. Is important to check QRV and category (Multi/Single/Check). It is suitable fill information of equipment
  • [ OK ]
  • <F9>, Contest, New from wizard
  • Region I Standard Contest
  • [ OK ]
  • OK1MZM
  • <Alt+X> (Confirm locator JN69PR.)
  • 59001 (then is filling date and time automaticaly)
  • <Enter>
  • ...
  • <F9> Contest, Export as EDI
  • <F9> File, Exit
  • Send log to comitee. Log is saved in ~/tucnak/<date>/*.edi

Changing of bands is possible by <F9> Bands. CTRL + assigned character for band.

If you want to run Tucnak in the networking is necessary to have filled these items:

  • Contest callsign
  • Date of contest
  • Name of contest. This item is very important.


I would like to say thanks you to:

  • Bo Hansen, OZ2M for TACLOG
  • Free software community
  • Milos OK1MZM for creating tucnakdw database and above all for testing alfa versions.
  • Peoples from radioclub OK1KRQ and OK1ORU for trusting when they've been testing tucnak in a big VHF contests (I. a III.subr 2003, PDM 2003 and others).
  • Guy, DL8EBW and VHF-DX-Group DL-West for nice VHF database
  • Mike, OM4AA, for bug reporting


The primary URL for tucnak downloading is

Download first source code or binary packages of Tucnak. There are maybe binary packages for your distribution but it can be out of date.

Tucnak requires glib 1.2 library. It's probably part of your distribution. If you want to compile Tucnak from source code you must have installed development version of glib library too (devel package - libglib1.2-dev*.deb (Debian), glib-devel*.rpm (RedHat), libglib1.2*.rpm (Mandrake)). The library you can download from (not :-)

If you want to use a graphics polar map, it's necessary to have installed SDL library (if you can compile it from source code you must have install devel packages too - libsdl1.2-dev*.deb (Debian), SDL-devel-1.2*.rpm (RedHat), libSDL1.2-devel*.rpm (Mandrake). You must install package tucnak1-data from section download.

Installation from source code

Installation from source code is universal way how to install program. There must be installed developments tools for C language on your PC.

Extracting source code

tar xzf tucnak1-1.13.tar.gz
Changing directory:
cd tucnak1-1.13
Run configure:
Compile code by command:
And install tucnak as root:
make install

Program is normally installed into directory /usr/local/bin. Maybe you will add path to Tucnak binary. You can add line export HOME=/usr/local/bin:$HOME to end of file /etc/rc.local in bash shell and then restart rc.local (or restart system).

Configuration files are allways saved in /etc directory.

Install on Debian


Simplest way is to add lines

deb binary-i386/
deb-src source/

to your /etc/apt/sources.list . After it use

apt-get update

and install selected packages:

apt-get install tucnak1

Download manually and install

Download package tucnak1-1.13*_i386.deb. Install it by command:

dpkg --install tucnak1-1.13*_i386.deb

Download sources and create package

If binary package doesn't present, create them by extracting source code by commnad:

make deb

Install on RedHat like distribution

Download package tucnak1-1.13*.i386.rpm, and install it by command:

rpm -i tucnak1-1.13*.i386.rpm

If rpm binary package doesn't exist, create them by extracting source code and execute commnads: (you must install package rpm-build first on Mandrake)

make rpm

Source package RPM (SRPM) you can create by:

make srpm

Files are saved in /usr/src/[redhat|RPM|packages|rpm]/* (depending on your distribution). Is necessary to have a write right to this directory.

Remark: Creating packages isn't perfectly tested. If you have any question for function or you know how to fix any mistake then write me, please.

Post install settings

Now is suitable to set Tucnak for specific station. It's good idea to have a few users for different callsigns in operating system. I have two users, ok1krq for a big contest (club callsign OK1KRQ) and for other contests I use my callsign OK1ZIA as user ok1zia.

Log to system as a contest user and run Tucnak. Enter to menu by F10; key. Next progress is described in Setup menu.

Menu Contest defaults

There is possible to set these items in this menu: callsign in contest, club callsign (use only if you can export contest log in EDI format), locator (6 characters), contest QTH (is equal items PAdr1 and PAdr2 in EDI, Optional Exchange and standard proposed reports for SSB and CW.

Band defaults

This submenu contains setting of all bands. Active bands (QRV is checked) are separated from other bands. You can take away bands which are never used (as 220MHz in Europe).

You can enter single band setting by pressing ENTER key. Item `QRV on this band' is usually set for all bands where are permit transmittes.

This setting is the only one which must be set. Other items are better set here too but it isn't necessary. QRV setting in this contest isn't effect on this place.

QRV setting in this contest isn't effect on this place. Cathegory can be one of Multi/Single/Check.

TX and RX Equip settings contains describing of equipments. Power is written with units. ASL and AGL means a height between antenna and sea/ground. Inserted values are in meters, delimiter is semicolon.

Fill operator's callsigns into Operators field delimitely by semicolon. Remark field is assigned for remarks to contest commitee.

Responsible operator

There are set information of responsible operator for communication with contest commitee in this dialogue. All items are in free format and don't need commentary.

CW daemon

Tucnak uses for keying and transmitting CW external program cwdaemon.

Interface between cwdaemon and tucnak doesn't still finished. Valid items are only hostname (IP address computer's where running cwdaemon) and UDP port. Other settings are necessary set from command line.

Run cwdaemon as root.

cwdaemon -n -l 0x3bc

Option -n causes writing debug information to console. Option - l change address of parallel port (e.g. on my notebook 0x3bc).

SSB daemon

All options of ssbd are setting in Tucnak. You can run ssbd on other computer over the network. This is useful on laptop without soundcard.

Program ssbd needs no commandline parameters except UDP port number. All other settings are done over network. Settings are:

Hostname and UDP port set IP address and UDP port which is connected for ssbd.

Path to DSP describes path to special file which is connected with sound card kernel driver. Typically is /dev/dsp.

Record traffic switches on/off recording band activity on receiving. If this option isn't active then all next options are irrelevant.

Template for recorded filename is template for naming recording files. Description of possible macros you can find in section CQ macros.

Next options describe coding of output file. Supported options are.

  • PCM 8 and 16 bits
  • Logarithmic PCM u-law and A-law
  • IMA and MS adaptation PCM
  • GSM version 6.10

PCM coding is suitable for conversion to other formats (MP3, Ogg). GSM coding has low size. One minute of recording have size about 130 kB of disk space. That is less then 200 MB for 24 hours. This coding doesn't have to supported by your favourite player! GSM format replay for example mplayer (with codec) or sdnfile-play distributed with libsndfile.

Option Channel sets number of sound channels. Set it to 1 (mono). You can set it to 2 or 4 it depends on your sound card capability.

Sample rate sets the number of sample per second. `CD' quality has value 44100. This value is needless for radio activity. It's recommended to lower value to half (22050) or quarter (11025) because some programs or sound cards can't work with other values. If SSB CQ or recording don't work properly mail to me, please.


The list of all CW texts are showed after selecting this item. There is showed the key for running the message in brakes. Character `R' means that the message is repeated (CQ). Also is showing start of text.

There are these items in dialoque for setting CQ: text of CQ and repeating of the text one. Item delay determines time between starts of CQ messages (not between end of first and start of second). Last item allows to run message if there is any macro undefined.


See description in previous chapter.

CQ macros

It's possible to define macros in texts of CW CQ and in name of SSB CQ file. Macros are case insesitive.

  • $$ - character $
  • $C - callsign of opposite station. Warning! Callsign may contains stroke then can be problem to use macros in filename of CQ SSB
  • $D - date of contest (20031228)
  • $N - contest number from opposite station
  • $O - operator's callsign (for SSB CQ filenames)
  • $R - report from opposite station.
  • $S - serial number of record sample (is refilled by ssbd)
  • $T - contest directory (/home/ok1zia/tucnak/20031004.2)
  • $V - callsign of opposite station, the stroke character is exchanged by the underline character
  • $W - locator of opposite station
  • $X - optional exchange from opposite station
  • $MC - my callsign
  • $MN - contest number from opposite station.
  • $MR - report for opposite station
  • $MW - my locator
  • $MX - my optional exchange

Macros has not effect in all context.


It sets and saves parameters of QSO to disk. Option `Save to disk after QSO' is recommended set to 1 to save all reports. Fsync option immediately saves QSOs from cache to disk.

Default setting of option Save to floppy after QSO is 4. Zero disables saving to floppy disk. Path to floppy item sets path to floppy's mount point. Tucnak don't test if floppy disk is mounted.

Other items are ignored.

Network & trace

Ignore interfaces - list of network interfaces which would be ignored for searching next copy Tucnaks on the net (transmit broadcasts) as connect to Internet, public IP address from provider, AX.25 interface. The delimiter between interfaces is space character. Broadcasts loads slow nets.

Ignore networks - the purpose this option is the same as Ignore interface option. You can determinate subnet address.

Announce to nets - it's an inverse function of previous options. There is specification of IP address where have been sending broadcasts in this option. The routers usually have disabled forward broadcastings.

Menu Terminal options

This menu is used for setting characteristic of terminal as window frames.

Load cfg from net

It shows addresses of all Tucnaks on the net. If one is selected you can read his complete configuration (tucnakrc).

Load C_W from net

It loads complete C_W database from selected Tucnak and saves it to ~/tucnak/tucnakcw. In database are saved two newest locators for each callsign.

Save configuration

It saves configuration to file ~/tucnak/tucnakrc

WARNING! Using of different versions of Tucnak is NOT recommended because older tucnak doesn't known all configuration options in tucnakrc file and if it saves as configuration in older version of Tucnak then options are lost where old version of Tucnak isn't known. If you use different versions of Tucnak then is recommended to use them under different users. Don't use two diferent versions of Tucnak under one user!


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.

  • tucnak - 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.
  • tucnakrc - configuration file of Tucnak program. Tucnak reads this file from directory ~/tucnak/. When it don't found configuration file in ~/tucnak/ it reads from /etc. File is saved only to ~/tucnak/ directory.
  • tucnakrc.local - This file has the same structure as tucnakrc file. Is determine to set specific local options as define LPT address e.g. cwda_port = 0x3bc. Tucnak only reads this file and it is necessary to create and edit it manually.
  • tucnakcw - File with apair callsign-locator. Each callsign has saved maximally two locators.
  • tucnakdw -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. The file is read from directories /etc/ and ~/tucnak/.
  • cty.dat - Follows up information to tucnakdw. Tucnak don't write to this file. The file is read from directories /etc/ and ~/tucnak/.
  • tucnakwiz - this file contains information about contest as kind of pointing, etc. Tucnak doesn't write to this file. The file is read from /etc/ and ~/tucnak/.
  • tucnakcor - (since 1.00). It's readed from ~/tucnak. When it fails then it's read from /usr(/local)/share1/tucnak/. It's data for generating the polar world wide map.

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>:

  • <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 organizer of contest. Files has DOS end of line (`\n' `\r').
  • <letter>.swp eg. c.swp, e.swp. are files where is saved all typed text from input line ended by enter key. You are able to reconstruct all reports manually from this file. desc - contains information displayed during start of contest as date of contest, callsign and name of contest.
  • desc - contains information displayed in start of contest as date of contest, callsign and name of contest.
  • log - content of log window.
  • sked - information about received skeds
  • talk - content of talk window. That's good idea to read after contest :-).

Band's label are marked according to EDI format e.g. `50 MHz', `70 MHz', ..... `248 GHz'. All bands has assigned one letter label which is used on place where isn't enough place.

Environment variables

  • HOME - user's home directory. This variable is equivalent with `~'.
  • TUCNAK_DEBUG - if this variable is set then debug information is written to stderr. If you can define file name to save debug information you must refill this variable.

Command line options

  • -d - it enables listing debug information to stderr.
  • --debug=file - it saves debug information to file <file>

New contest

You have two choices for creating a new contest log. You may select contest which was defined before by select New contest from wizard in Contest menu or select New and to set parameters of contest manually. You can add contest to tucnakwiz file (manually) fof next using in the future.


Set name of contest on the first place in dialogue New Contest . Callsign, club and locator are probably sets. Optional exchange option isn't implemented yet.

Write date of begin of contest to item Date of contest. This item has effect only for naming contest's directory, not for export contest to EDI format.

Next options determine style of giving points.

Above OK and Cancel buttons are buttons with all bands which are set as QRV. You can set off some bands for actual contest only. Option Read-only prohibits any changes on band. It's suitable for network working.

Next items are described in Band defaults section.

Click on button 'EDI prop' in dialogue New Contest to go to dialogue where you can change name of your QTH. It is possible to set which operator is responsible to send log in Responsible op.

Button Responsible op executes dialog for setting of informations about responsible operator. See section Responsible operator.

Now press <OK>.


For using networking you must keep few rules.

  • Computers must be reachable on each other. Tucnaks communicate between itself by UDP broadcasts which are sending to all net interfaces which are known at time of program start.
    • Simple example is one ethernet segment.
    • But this is not necessary if you need to run Tucnak on router computer to spreed broadcasts around master.
    • It is possible to use more Tucnaks on one computers (server). Server is remote available from other computers throw telnet/ssh. Communication between Tucnaks are through lo (Local Loopback) interface.
    • Hint: if you use telnet/ssh to remote access try program screen, see Appendix B.
  • Master Tucnak is Tucnak which have lowest IP/port Address. Is recommended to have a master Tucnak on fastest part of network.
  • List of connected Tucnaks is visible in File-> Network info menu.
  • Attention! Is really necessary to have set the same time (plus minus few second) on all computers. In a long contest is necessary to install ntp daemons because of differents between individual computers may be a few seconds during 24 hours. Ntp daemon is described in  appendix A.
  • Set the same contest, date of contest and name of contest in all Tucnaks.
  • If more Tucnaks run under one user then second Tucnak creates contest's directory <YYYYMMDD.1> This feature can't work under CygWin or on some net file systems.
  • If there are accomplished all conditions, Tucnaks begins to replicate contacts, DX spots and other.


Main window contains windows with various information. Switch between windows is doing by <F4> key or directly by <ALT + number>. In a bottom side of main Tucnak's window is on input line. Above the input line is temporary displayed actual QSO. Main window from the input line is activated by up arrow key. Press <ESC> key to be return in input line.

Callsigns, callsign's suffix, operator's callsign and suffix are highlighted in most of windows. Callsigns between <* and *> the whole line is highlighted (private message from WW convers).

Kinds of windows:

  • QSOs There are a few last QSOs displayed in this window. Letters on right side of report indicate new square, country, optexc. Occurrence of remark and QSL request are displayed in next column. If input line contains minimally two letters then stations or WWLs which contains this string are displayed. Is possible to use a dot character as wild a character. Tucnak is looking for station in actual band's contacts, other band's contacts and in C_W database. If you are in QSO window (enter by Up Arrow) you can edit selected QSO by pressing <ENTER> key.
  • Hint: Quick search is suitable for find:
    • If you have QSO with station on this band (typing suffix or last two letters of locator).
    • If you has QSO with station in other bands is showed actual known locator.
    • If the station is in C_W database then Tucnak gives locator in which the station was last contest.
  • Sked window displays all skeds sent in contest between bands. Sked is sends by <Alt+S>.
  • Talk window allow talking between operators on network.
  • Unfinished window shows all NC QSO on actually band.
  • Statistics window shows basic statistics about the actual band. That's: an average of points per QSOs, worked locators and DXCC.
  • Log window displays other information. Last two line from log are displayed in last bottom line of the main window.
  • Shell window is a simple terminal with executed shell. You can execute external programs as call or telnet to connect to packet.
  • DXC - spots comming through all shell windows are parsed. If a DX spot is recognised is added into this window ordered by QRG. You can press Enter to add callsign in temporary QSO without typing it.

Edit call

Dialogue for editing QSO is displayed from QSOs window pressing <ENTER> key on select QSO. There isn't checked any control of written items in this dialogue. If You have any good idea how to improve this dialogue, mail me, please

If you change one or booth locators and not change mode, the QSO mode is updated from reports. In other case this dialog is dumb, it makes no validity control.

Option Error signs QSO as bad QSO and Tucnak counts zero points by this QSO. Report is possible sign back as good.

Hotkeys in a contest

  • F2: saves QSOs from all bands
  • F3: erases input line and report
  • F3: opens a new contest
  • F4: switches between windows
  • F5..F8: exec call 0 .. 3 (CW or SSB)
  • F9,F10: menu
  • F11..F12: exec call 4 .. 5
  • Alt+B: switches bands
  • Alt+C: swaps callsigns in unfinished QSO
  • Alt+D: confirms offered callsign
  • Alt+F: sets preferred QRG for skeds
  • Alt+G: S&P's request for QSO/RUN's confirm
  • Alt+H: shows history of input line
  • All+M: swaps CW/SSB modes
  • Alt+N: displays next item in history
  • Alt+O: changes operator
  • Alt+P: displays previous item in history
  • Alt+S: sends sked
  • Alt+Q: exits from program
  • Alt+U: adds QSO to unfinished QSO
  • Alt+V: swaps locator
  • Alt+X: confirms offer locator
  • Alt+Y: erases unfinished QSO only
  • Alt+1..0: directly switchs to window 1 .. 10
  • Ctrl+L: redraws screen
  • Ctrl+P: shows polar map (only in graphics mode)
  • Ctrl+V: allows insert special characters to input line. (TODO)
  • Ctrl+Y: erases input line
  • Ctrl+A..X: changes band
  • TAB: switches on PTT in SSB mode. Switch on transmitting from keyboard in CW mode.
  • Up Arrow: sets window active
  • ESC: finish CQ or switches to input line
  • Enter: if CW window is active it's closed
  • [: horizontal scroll log to left (TODO)
  • ]: horizontal scroll to right

Other usefull keys:

  • Alt+Fx - Changes active console to console x (in console mode)
  • Ctrl+Alt+Fx - as above in X Window System
  • Alt+Left/Right Arrow - changes console from one to rigth/left

Key in graphics window

  • c: centers map to QTH
  • l: enables/disables line from QTH to station
  • r: redraw map
  • ESC, q: closes graphics window
  • Cursor keys: moves the map about 100 disp. points
  • +,-: zoom map
  • F1: saves graphics window to contest directory in BMP picture format


Program automaticaly recognizes kind of typed items and correctly put it into unfinished QSO where is located above input line.

  • Callsign - e.g. OK1MZM, HB0/OK1MCS/P. If QSO with the station in the contest exists then dialogue Duplicate QSO is displayed. When tucnak doesn't recognize entered string as callsign (exotic callsign), enter slash after callsign (SP0PAPA/).
  • Report for the station - e.g. 59, 559, 59S. This item is presetet doesn't need it type.
  • Report and contest number from other station are written together. Number higher as 1000 is written with `_' character (59_1001). If the qso number is not used, you can enter received contest number ended by comma (59,).
  • Locator - e.g. JN69PV
  • Date - 20030809, Only last four numbers is possible to write. The year is automaticaly filled with present year.
  • Time - e.g. 14.22, is possible to write short record as .22
  • Suffix/locator - e.g. AB can be suffix of station or last two characters of locator.
  • Suffix - three letters mean suffix only
  • Optional exchange - any string ended by point (.).
  • Q - QSL send request.
  • #REMARK - remark to report. In input line isn't possible write any space characters.
  • Save QSO - if all items of QSO are written QSO may be saved by ENTER key.

It is possible to write more items which are delimited by space characters. If any item isn't recognized then it's displayed left above top input line.

Hint: You can return all to QSOs line byAlt+P.

Duplicate call

If you write callsign which is saved before then Duplicate QSO dialogue is displayed. You have any choices, see bellow.

  • Clear this QSO - clear this QSO (as F3 key), old QSO isn't changed
  • Edit old QSO edit changes in old QSO
  • Mark old QSO as ERROR - Mark old QSO as ERROR, a new QSO is relevant now
  • Store as DUPE - Old report is achieved, new have zero points but it's loged as DUPE.

Advanced function

If You insert callsign which is known in C_W database, program automatically fill up to two locators. Locators are inverse displayed. If locator on higher row is valid you must confirm it by pressing <Alt+X> key. If second WWL is valid you must swap locators by pressing <Alt+V> key. If callsign isn't contain in database, Tucnak fill a large square with highest activity or Capital City of worked DXCC and calculates aproximate QTF.

Similar situation is if you insert known locator. There'll display two inverted callsign which can swap press <Alt+C> and confirm by press <Alt+D> or shows prefixes of possible DXCC only if isn't known any callsign

Tucnak checks if pair of locator and callsign exists. If Tucnak think that it's invalid then shows at locator some of this characters.

  • ! - large square doesn't lie in DXCC. If callsign and locator are correct an invalid record is in tucnakdw.
  • ? - Tucnak knows locators of this station but typed locator is different
  • nothing - callsign is unknown or locator corresponds with callsign.

Output from program

Tucnak's outputs are compatible with EDI format and are saved to the .txt files with Tucnak's specific extensions which will be ignored by contest commitee


The export to plain EDI format with command Contest -> Export as EDI. Output is in file e.g. 02OK1KRQ.edi.


It's another output. Output file has suffix txt. This output is generating in OK VHF Activity contest format.


The main format for exporting contest log to general purpose log. If you have some questions to format output files or compatibility with logbook , please mail me

Menu File

Open/Close graphics window

Opens / closes window with graphics polar worl wide map. Exit from map's window is possible by <q> or <ESC> key.

If contest is opened the map shows QSOs as yellow crosses. The station whitch is the nearest to mouse cursor is hightlighted by red colour. There are information about call, QRB and QTF between QTH and this station at the right window.

Remark.: You must compile Tucnak with support SDL if you want to use the map.


This menu is active only if you begin a contest.


If you already have had unfinished QSO with the station you can mark this QSO as Error QSO and make complete QSO later.

Change operator

Sets operator's callsign. The callsign is used for talk. It's also saved with each QSO for statistics.

Fill operators

Settings of all bands have a list of operators (items Mope1 and Mope2 EDI format). Each list contains callsigns of all operators which have one or more QSO. This feature is suitable used before you send logs to contest commitee.

Update C_W from contest

Adds pair callsign - locator from all bands to actual tucnakcw database.

Update C_W from band

Adds pair callsign - locator from active band to actual tucnakcw database

Import DL8EBW database

Load the VHF-Database by VHF-DX-Group from file /usr/share/tucnak1/vhf.dbf. Import only WWLs and names, and saves them to files ~/tucnak/tucnakcw and ~/tucnak/tucnaknames.

Menu Bands

There are all bands which are checked as QRV in the contest in this menu. You can switch active bands by <Alt+B> and by a letter of band. Band's letter corresponds with letter which are in right menu's column.

Menu Subwins

You can invoke this menu by pressing <Alt+W> keys. All windows which are possible to use are displayed in this menu.

Add subwin

A list of windows, which are supported. The selected window is added as last item of window's list. It isn't possible to save list of windows.

Items Command and Respawn are not used.

Close subwin

Closes actual window.

How to Help?

  • By testing stable and development branch of Tucnak and sending error list to me.
  • Help with refill data files like tucnakdw and tucnakwiz.
  • Laud about Tucnak :-)
  • If you have some idea how to improve Tucnak, please mail me this idea.
  • Write a new part of Tucnak.
  • Translate this documentation to other languages (or repair errors in the English version :-) ).
  • Create package for your distribution.
  • Voluntary small contribute for beers please sent to author (to me).

73! Ladislav Vaiz, OK1ZIA

Appendix A - Time synchronization by NTP protocol

Package ntp you probably have in your distribution. Older version have named xntp. You need programs ntpdate which is used for a single set date and (x)ntp for synchronization time for all time of system running. Ntp daemon has /etc/ntpd.conf configuration file.

In file /etc/ntp.conf should be contained next lines.

fudge stratum 10
- Using local time if not present master time server.

If you can then use time server from the Internet.If you can then use time server from the Internet.


The slave computers will have in configure file address master computer.

Next items you have on default setting.

driftfile /etc/ntp/drift
multicastclient broadcastdelay authenticate no

If different between times on computers are highest than few second is better set to clock by ntpdate program if computer boots. This case is possible to use witting master computer address to file /etc/ntp/step-tickers or write command ntpdate <master> on end of /etc/local file.

Hint: ntpd synchronize time after several minute, sometimes you'll have to very patient.

Valid HTML 4.01!  Valid CSS!  Created with Vim  Viewable with any browser