http://tucnak.nagano.cz/wiki/api.php?action=feedcontributions&user=G1ogy&feedformat=atomTučňák Wiki - User contributions [en]2024-03-29T01:34:59ZUser contributionsMediaWiki 1.30.2http://tucnak.nagano.cz/wiki/index.php?title=Rain_Scatter&diff=2559Rain Scatter2017-02-10T15:06:30Z<p>G1ogy: Spelling updates.</p>
<hr />
<div>One of new feature (2016) in Tucnak is Rain Scatter map. It merges data from public rain radars and shows it in [[Subwin_types#Graphics_map|map]]. Merge means that palette of images is unified, higher rain intensity is painted on the top. If some rain provider is delayed, Tucnak loads latest available image.<br />
<br />
[[Image:Rainscatter.png|thumb|none|900px|Rain Scatter map in Tucnak]]<br />
<br />
The time in the left bottom corner is date of displayed image for all providers. If red, Tucnak was not able to load the image. In this case clouds are displayed in greyscale to inform operator.<br />
<br />
=Options=<br />
Settings is in dialog Rainscatter options:<br />
<br />
[[Image:Rainscatter_options.png|thumb|none|900px|Rain Scatter Options]]<br />
<br />
* '''Enable''' - enable or disable the rain subsystem<br />
* '''Meteox''' - load data from meteox.com. It covers area from G to OK. Displays time in CE(S)T.<br />
* '''Wetteronline''' - load data from wetteronline.de. Covers area from 0th longitude to west UR. It cannot be delayed, I think it returns prognose in this case. Update interval: 5 minutes. Displays time in UTC [Z].<br />
* '''CHMI''' - data is from chmi.cz. It is often delayed due to network problems. It covers OK and narrow band around. Has very good and detailed palette.<br />
<br />
* '''Debug''' - shows pixels instead of filled areas. Good for mapping image to land by border compare. Also saves temporary images into current directory. Do not use in contest.<br />
<br />
=How to operate=<br />
Best band is 10 GHz, good is also 6cm. With strong rain you can hear typical "S" sound also on lower microwave bands. <br />
<br />
Look for high intensity rain. Strongest is red/white [[Image:Rainscatter_palette.png]]. Hover mouse pointer above, read azimuth and turn antenna. Tune band, look for any station. Then turn antenna in AZ/EL to get stronger sigs. Look for stations or call CQ if your power is enough.<br />
<br />
From time to time adjust antenna AZ/EL, clouds are travelling.</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Setup&diff=1706Setup2012-02-11T14:34:43Z<p>G1ogy: /* Alsa options */</p>
<hr />
<div>{{Languages}}<br />
<br />
[[Image:menusetup.png|none|frame|Setup menu]]<br />
<br />
All configuration changes are in memory only until you [[Setup#Save_configuration|save configuration]].<br />
<br />
=Contest defaults=<br />
<br />
[[Image:Contestdefaults.png|none|frame|Contest defaults]]<br />
<br />
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.<br />
<br />
=Band defaults=<br />
<br />
[[Image:Bandsettings.png|none|frame|Band defaults]]<br />
<br />
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).<br />
<br />
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.<br />
<br />
This setting is the only one which must be set. Other items are better set here too but it isn't necessary. <br />
<br />
QRV setting in this contest isn't effect on this place. Category can be one of Multi/Single/Check.<br />
<br />
TX and RX Equip settings contains description 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.<br />
<br />
Fill operator's callsigns into Operators field delimitely by semicolon. It is possible to fill it by Fill operators in menu [[Contest]].<br />
<br />
Remark field is assigned for remarks to contest commitee.<br />
<br />
Single/Multi categories are categories valid (probably) only in Czech republic. They are used mostly for EDI files naming.<br />
<br />
Band boundaries are entered in kilohertz. At this time they are used for DX-cluster spot filtration.<br />
<br />
Adif band name is band description used in ADIF format.<br />
<br />
QRG for skeds is initial frequency entered by operator to inform other operators about clean/CQ frequency on which they should take skeds. Format is not limited, you can use any string like ".120" etc.<br />
<br />
Transverter's LO QRG is frequency which tucnak adds to frequency read from transceiver's CAT and result shows on the screen:<br />
<math>f_\mathrm{display}=f_\mathrm{CAT} + f_\mathrm{lo} [Hz]</math><br />
Note some radios support transceiver mode for example radio is tuned on 14 MHz, CAT reports also 14 MHz but transceiver's display shows 144 MHz.<br />
LO frequency must be computed by operator, you can use Fix QRG in [[Edit]] menu.<br />
<br />
This is local frequency for one band. Normally enter 0 to use [[Setup#Rig options|Global LO frequency]].<br />
<br />
Band switch value is value sent to some keying devices to inform your contest hardware about active band in Tucnak.<br />
<br />
=Responsible operator=<br />
<br />
[[Image:Responsibleoperator.png|none|frame|Responsible operator]]<br />
<br />
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.<br />
<br />
=CW keying=<br />
<br />
[[Image:Cwdaemon.png|none|frame|CW daemon]]<br />
<br />
Since version 2.0 Tucnak does not use the external program 'cwdaemon' for keying and transmitting CW. Its functions are included in Tucnak. <br />
<br />
Keying methods are:<br />
* None - no CW output is used<br />
* lp - uses kernel module ppdev for keying. Recommended device is [[Dávač 3.3]]. Pin configuration is:<br />
** 1 STROBE - grounded when active.<br />
** 14 AUTOLF - switch TRX modulation input to microphone or soundcard output<br />
** 16 INIT - PTT<br />
** 17 SELECT IN - CW<br />
* ttys - uses control pins of serial port. Pinout for D-SUB9:<br />
** 4 DTR - CW<br />
** 5 GND - ground<br />
** 7 RTS - PTT<br />
* davac4 - USB SSB/CW keyer [[Davac4]] by OK1ZIA<br />
* cwdaemon - controls [http://www.qsl.net/pg4i/linux/cwdaemon.html cwdaemon] by Joop PG4I<br />
* winkey - uses [[Winkey]] by [http://www.k1el.com K1EL]<br />
<br />
Keying device f.e. /dev/parport0, /dev/ttyS0, /dev/ttyUSB0<br />
<br />
Hostname, UDP port are reserved.<br />
<br />
Initial speed says keying speed in WPM after program start. You can change it using PageUp or PageDown keys.<br />
<br />
Weighting - changes ratio of mark and space in CW. <br />
<br />
<math>t_\mathrm{mark}=\frac{1\,200\,000}{\mathrm{speed}}+500 * \mathrm{weight}\ [\mu s]</math><br />
<br />
<math>t_\mathrm{space}=\frac{1\,200\,000}{\mathrm{speed}}-500 * \mathrm{weight}\ [\mu s]</math><br />
<br />
WPM range describes the speed that can be set with PageUp/PageDown keys. Minimal WPM is also used for Winkey - it can handle only 31 speed steps. Normally minimal speed is set to 10 WPM which means winkey range 10-41 WPM. If you need for example 50 WPM, set minimal WPM to at least 19.<br />
<br />
Use speaker - beeps using program soundwrapper.<br />
<br />
PTT lead in - (experimental feature) Tucnak turns on PTT some time before CW to key on TRX and PA's to prevent "eating" of begin of code. It also allows the TX chain to stabilise before sending. Suggest 100 -> 250 ms.<br />
<br />
=Winkey options=<br />
<br />
[[Image:Winkeyoptions.png|none|frame|Winkey options]]<br />
<br />
Fast initialisation means that Tucnak doesn't wait for Winkey initialisation. It can be used mostly for winkey2 which is commonly supplied from USB. It has no effect for other version-depending commands (buttons), tucnak reads winkey version.<br />
<br />
Use speed pot/use buttons - doesn't need comment. Normally is no reason to turn they off.<br />
<br />
Curtis A/B, Ultimate, hand bug - set's paddle mode. I think optimal is Curtis B.<br />
<br />
Paddle swap - also without comment :-)<br />
<br />
=Audio=<br />
<br />
[[Image:Audio.png|none|frame|Audio options]]<br />
<br />
Since 2.0 Tucnak takes also SSB functionality for CQs and traffic recording. <br />
<br />
==Common options==<br />
Alsa, OSS, SSBD are supported "audio drivers".<br />
<br />
'''Record traffic''' switches on/off recording band activity on receiving. If this option isn't active then all next options are irrelevant. To prevent consuming of all free space, use options '''Max. record duration''' and '''Minimal disk free space'''.<br />
<br />
'''Record format''' option describe coding of output file. Supported options are.<br />
<br />
* PCM 8 and 16 bits<br />
* Logarithmic PCM u-law and A-law<br />
* IMA and MS adaptation PCM<br />
* GSM version 6.10 (preferred for me)<br />
<br />
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 sndfile-play distributed with libsndfile.<br />
<br />
Option '''Channels''' 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.<br />
<br />
'''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. <br />
<br />
'''Playback volume''' provides possibility to set playback volume for SSB CQ. Enter -1 to disable this feature. Common valid volumes are 0 to 100 but can be different if you use some special hardware with fancy cost-down. <br />
<br />
Note in versions prior 2.26 is bug that doesn't allow to load negative value from rc file. As workaround you can try to enter invalid mixer device.<br />
<br />
'''Capture volume''' the same for traffic recording.<br />
<br />
'''Template for recorded filename''' is template for naming recording files. Description of possible macros you can find in section [[Setup#CQ_macros|CQ macros]].<br />
<br />
==Alsa options==<br />
'''Alsa playback device''' and '''Alsa capture device''' hold Alsa devices, plugs etc. Valid values are for example:<br />
* default - default device in your configuration<br />
* hw0,0 - first card, first PCM (first DAC)<br />
* hw0,1 - first card, second PCM (second DAC, f.e. Ensonic ES1371)<br />
* hw1,0 - second card ...<br />
* plughw0,0 - see Alsa documentation<br />
* dmix<br />
* pulse - recent versions of non-Debian linux use "PulseAudio" sound system. Tested [G1OGY](Playback ONLY) on Ubuntu 10.04LTS & Ubuntu 11.10. <br />
<br />
'''Period time''' is maximal amount of time for holding samples in card buffer for capture. Rasonable values are in hundreds (tenth of second).<br />
<br />
'''Buffer time''' is maximal total size of buffer. Must be greater than Period time, f.e. 4*Buffer timer.<br />
<br />
'''Alsa mixer device''' f.e. hw0, hw1, ...<br />
<br />
'''Capture source''' button shows submnenu for capture. In menu are all detected sources on specified soundcard.<br />
<br />
==OSS options==<br />
'''OSS DSP''' describes path to special file which is connected with sound card kernel driver. Typically is /dev/dsp.<br />
<br />
'''Max. num of fragments''' tells number of buffer fragment which can be holded in buffer. If you have problems with recording or witdh transition RX -> TX, try to set to 4 or similar small number. Then check recorded files for buffer underruns.<br />
<br />
'''OSS mixer''' path to OSS mixer. typically /dev/mixer.<br />
<br />
'''Record source''' - input for recording signal.<br />
<br />
==SSBD options==<br />
'''Currently unimplemented!''' SSBD is now obsolete. Settings is here for eventual future control of other software/devices (PowerSDR, digimodes...)<br />
<br />
'''SSBD hostname''' and '''UDP port''' - set IP address and UDP port of ssb daemon.<br />
<br />
==Problems==<br />
* Tucnak does not record band traffic<br />
*# Is '''Record traffic''' on?<br />
*# Is '''Max. record duration''' set enough value?<br />
*# Is '''Minimal disk free space''' set to higher than actual free space?<br />
*# Don't you use cwdaemon? In 2.33 the bi-directional communication is broken so Tucnak don't know when CW stops<br />
*# Isn't contest more than two days old? When is, tucnak thinks you only viewing old contest.<br />
<br />
=CW CQ=<br />
<br />
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.<br />
<br />
[[Image:Cwcq.png|none|frame|CW CQ]]<br />
<br />
There are these items in dialoque for setting CQ: <br />
<br />
'''text''' of CQ. You can use plain text and macros<br />
<br />
'''speed''' is normally undefined but you can define speed only for this CQ (f.e. for fast 73)<br />
<br />
'''repeat''' CQ will be repeated until you press ESC, TAB or other CQ key<br />
<br />
'''delay''' determines time between CQ messages <br />
<br />
'''allow if...''' allows to run message if there is any macro undefined. Typically you don't want to give empty string if you have no callsign entered.<br />
<br />
=SSB CQ=<br />
<br />
[[Image:ssbcq.png|none|frame|SSB CQ]]<br />
<br />
'''filename''' - file which is played as CQ. You can use macros f.e. /home/user/tucnak/cq/$MC_$O.wav to have multiple files for more callsign and more operators. Some audio output devices can have limitations to the audio format - samplerate, channels.<br />
<br />
'''repeat''' and '''delay''' has same effect as in previous chapter<br />
<br />
=CQ macros=<br />
<br />
It's possible to define macros in texts of CW CQ and in name of SSB CQ file. Macros are case insensitive.<br />
<br />
* $$ - character $<br />
* $B - callsign of opposite station if differs from sent $C. Useful for "$B TU 73" in run mode. Does not work with [[winkey|Winkey]] and cwdaemon.<br />
* $C - callsign of opposite station. Warning! Callsign may contains stroke then can be problem to use macros in filename of CQ SSB. Look at $V<br />
* $D - date of contest (20031228)<br />
* $E - if contest code was entered during recording, string "code" will be added. Useful for post-contest record check, you can see important files by their filenames<br />
* $I - contents of inputline. Dots are replaced by question marks. Good idea is to follow $I by question mark in CQ definition.<br />
* $N - contest number from opposite station<br />
* $O - operator's callsign (for SSB CQ filenames)<br />
* $R - report from opposite station.<br />
* $S - serial number of record sample<br />
* $T - contest directory (/home/ok1zia/tucnak/20031004.2)<br />
* $V - callsign of opposite station, the stroke character is exchanged by the underline character<br />
* $W - locator of opposite station<br />
* $X - optional exchange from opposite station<br />
* $MC - my callsign<br />
* $MN - contest number to opposite station. For band or for all bands depening on [[Contest_options#QSO_NR|Global QSO NR]]<br />
* $MR - report to opposite station<br />
* $MW - my locator<br />
* $MX - my optional exchange<br />
<br />
You can also use case sensitive macros from strftime(3) for example:<br />
<br />
* %d - day of month 01..31<br />
* %H - hours 01..24<br />
* %M - minutes 00..59<br />
* %m - month 00..12<br />
* %S - seconds 00-59<br />
* %Y - year 1970-2038<br />
<br />
For others use command:<br />
<br />
man 3 strftime<br />
<br />
Macros have no effect in all contexts.<br />
<br />
=Rig options=<br />
<br />
Tucnak uses [http://hamlib.sourceforge.net hamlib] for accessing rig (transceiver) via CAT interface. You can use probably any interface which is working with other programs. Good helper is [http://tucnak.nagano.cz/Interfaces.pdf HB9DRV's guide to HRD]. Or you can build one of [[RIG interface|my RIG interfaces]].<br />
<br />
[[Image:Rigoptions.png|none|frame|Rig options]]<br />
<br />
'''Device''' device where the interface is connected. Typically /dev/ttyS0, /dev/ttyUSB0<br />
<br />
'''Model''' model of rig. It is number defined by hamlib. You can obtain it by running command '''rigctl -l''' or you can use:<br />
<br />
'''Choose''' Press button to show menu. In the first level you will choose manufacturer, in second level rig model. Model number is written to the previous field.<br />
<br />
'''Baudrate''' communication speed. Leave 0 to use default hamlib value<br />
<br />
'''CIV address''' address of rig if you have more Icom radios connected via one interface. Enter 0 for default address.<br />
<br />
'''Freq. shift SSB->CW''' some old radios (Icom, Kenwood) shifts frequency when changing mode SSB <--> CW. If you call CQ on SSB and someone calls you in CW, you must switch to CW and tune for about 800Hz up. Tucnak can compensate this shift when you use Alt+M to switch mode.<br />
<br />
'''Transverter's LO QRG''' is frequency which tucnak adds to frequency read from transceiver's CAT and result shows on the screen:<br />
<math>f_\mathrm{display}=f_\mathrm{CAT} + f_\mathrm{lo} [Hz]</math><br />
Note some radios support transceiver mode for example radio is tuned on 14 MHz, CAT reports also 14 MHz but transceiver's display shows 144 MHz.<br />
LO frequency must be computed by operator, you can use Fix QRG in [[Edit]] menu. This is global LO freq, if you use more transceivers, you can set more frequencies in [[Setup#Band defaults|Band defaults menu]].<br />
<br />
'''Rig poll interval''' set if communication with radio produces system load<br />
<br />
'''Set band from radio''' log's band is switched automatically when radio is tuned to other band<br />
<br />
'''Change band on radio''' radio's band is changed when operator switches band in log<br />
<br />
'''Change mode on radio''' radio's mode is changed when operator changes mode<br />
<br />
'''Clear RIT on RUN's QSO save''' in Run mode clear RIT after QSO is stored. Depends on radio/hamlib capabilities.<br />
<br />
=Autosave=<br />
<br />
[[Image:Autosave.png|none|frame|Autosave options]]<br />
<br />
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.<br />
<br />
Default setting of option '''Save to disk after QSO''' is 4. Zero disables saving to floppy disk. '''Path to floppy''' item sets path to floppy's mount point. Tucnak doesn't test if floppy disk is mounted or not.<br />
<br />
Other items are ignored.<br />
<br />
=Network & trace=<br />
<br />
[[Image:Networktrace.png|none|frame|Network & trace options]]<br />
<br />
Ignore interfaces - list of network interfaces which would be ignored when searching for more instances of Tucnak on the network (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.<br />
<br />
Ignore networks - the purpose this option is the same as Ignore interface option. You can determinate subnet address.<br />
<br />
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.<br />
<br />
=Miscellaneous options=<br />
<br />
[[Image:Miscoptions.png|none|frame|Miscellaneous options]]<br />
<br />
'''Log lines''' are last lines of tucnak's screen on which tucnak writes informations for users.<br />
<br />
'''Sked shift''' time added to current time filled in the Sked dialog.<br />
<br />
'''Starting band''' Band character (f.e. C=144 MHz) of band, which will be activated after contest open.<br />
<br />
'''Screen resolution''' Only for SDL mode - you can set resolution of tucnak's window in characters or in pixels<br />
<br />
'''Double font''' for very-high-resolution displays and bad eyes - fonts are resized from usual 9x16 to 18x32 pixels. It is not very usable but on IARU VHF 2008 I had nothing to do so I've imlpemented it.<br />
<br />
'''Slash key''' Slash key on some national keyboards is not easily accessible (only with shift). Here you can remap it to any other character. Use with care!<br />
<br />
'''Disable screensaver''' if you only test Tucnak at home, you probably don't want to disable screensaver. So turn these checkbox off.<br />
<br />
=Terminal options=<br />
<br />
[[Image:Terminal.png|none|frame|Terminal options]]<br />
<br />
These options come from [http://links.sourceforge.net links browser] so I'm not able to tell what they exactly mean. Try to make some experiments or look at source code :-)<br />
<br />
=Language=<br />
<br />
Set language of Tucnak's GUI. I think English is very good for contest log but some people like to have their mother tongue set.<br />
<br />
=Character set=<br />
<br />
This menu is used for setting characteristic of terminal as window frames. It's a legacy of links (as above), I don't have detailed knowledge about these options.<br />
<br />
=Load cfg from net=<br />
<br />
It shows addresses of all Tucnaks on the local network. If one is selected you will read his complete configuration (tucnakrc).<br />
<br />
=Load C_W from net=<br />
<br />
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.<br />
<br />
=Save configuration=<br />
<br />
It saves current configuration to file ~/tucnak/tucnakrc . You '''MUST''' do it to preserve any configuration changes !!</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Features&diff=1596Features2010-12-26T22:06:24Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
=Compatibility=<br />
* The Control of program was took from program [http://www.qsl.net/oz2m/ Taclog].<br />
* The support of most EU contests. It's possible to have open more contest logs than one in one time.<br />
* The export of contest logs to EDI and some other formats<br />
* The export to ADIF and HTML formats.<br />
* It is possible to work with the most kinds of terminals or under X11 using SDL library<br />
* It is possible to work remotelly by using ssh or telnet (as [http://www.google.com/search?q=putty putty]).<br />
<br />
=Easy operation=<br />
* Easy instalation - only one binary is sufficient for base usage.<br />
* You can control your rig (SSB PTT and CW). Is also possible to send SSB and CW CQ or transmit CW directly by typing from keyboard.<br />
* Single items (Callsign, WWL, report, etc.) are automatically identified and inserted.<br />
* The searching of typed-in 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.<br />
* Is possible to write remark for a QSO directly from input line or to set QSL card flag.<br />
* The Wizard for creating a new contest. It automatically sets parameters of a selected contest<br />
<br />
=Variability=<br />
* 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)<br />
* Is possible to run more than one process of Tucnak on one computer (server).<br />
* The support of many languages if somebody translates it from English or Czech :). Currently English, Czech, Slovak, German and Portuguese.<br />
<br />
=Security=<br />
* All the written items of QSO (or part of QSO) are written also to the swap file. If your computer crashes you can read QSO data from this swap file with simple ASCII editor, e.g. [http://www.vim.org/ Vim].<br />
* The Automatic saving data to disk and diskette.<br />
* Record of contest to WAV files by a few possible codings (PCM, ADPCM, x-law, GSM coding).<br />
* Record volume monitoring.<br />
* Unrecognized input strings are not deleted but they are displayed.<br />
* The saving incomplete QSO and the marking of it.<br />
<br />
=Databases=<br />
* The Database of couple Callsign, World Wide Locator and QRV bands<br />
* 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.<br />
* The cross control couple callsign - locator.<br />
* Import of VHF database by DL8EBW<br />
* The basic statistics - number of worked DXCC and WWL<br />
* There is a color world map with worked QSO in graphic mode.<br />
<br />
=Networking=<br />
* The executing shell in one of tucnak window. You can simple connect it to packet radio by programs for example node, call or telnet.<br />
* Connecting to very popular [http://www.on4kst.com/chat/start.php ON4KST chat] with call and "session" highlighting.<br />
* The talking with other running Tucnaks similary as in WW-Convers (talk window).<br />
* The sending of skeds to other (higher) bands.<br />
* The DX spot handling from shell windows and putting it to the bandmap<br />
* Loading configuration and C_W database over the net.<br />
* Spying of other operator's inputline and working QSO<br />
* Antenna rotators control<br />
<br />
=Freedom=<br />
* Tucnak is a free software distributed under the GNU [http://www.gnu.org/ General Public License].<br />
* Packages for Debian and Debian-like Linux distributions</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Supported_Contests&diff=1171Supported Contests2009-11-02T00:40:11Z<p>G1ogy: /* List of Tucnak Supported Contests */</p>
<hr />
<div>{{Languages}}<br />
<br />
=List of Tucnak Supported Contests=<br />
(please add all contest already working)<br />
<br />
* IARU VHF / UHF Contest<br />
* VHF Marconi CW Contest<br />
* [[AGCW CW Contest]]<br />
* RSGB V/UHF Contests - Standard and Multipliers: M1-M4 [http://www.rsgbcc.org/vhf RSGB VHF Contest Committee]<br />
<br />
<br />
== Wish List==<br />
(add Contest , YOU would like to run with Tucnak, don't forget to add, at least, a link to the contest rules)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Supported_Contests&diff=1170Supported Contests2009-11-02T00:38:46Z<p>G1ogy: /* Wish List */</p>
<hr />
<div>{{Languages}}<br />
<br />
=List of Tucnak Supported Contests=<br />
(please add all contest already working)<br />
<br />
* IARU VHF / UHF Contest<br />
* VHF Marconi CW Contest<br />
* [[AGCW CW Contest]]<br />
* RSGB V/UHF Contests - Standard and Multipliers: M1-M4 [http://www.vhfcc.org RSGB VHF Contest Committee]<br />
<br />
<br />
== Wish List==<br />
(add Contest , YOU would like to run with Tucnak, don't forget to add, at least, a link to the contest rules)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Converting_TACLog_v_1,9xx_C_W_files_for_use_with_Tucnak&diff=1169Converting TACLog v 1,9xx C W files for use with Tucnak2009-11-02T00:37:26Z<p>G1ogy: </p>
<hr />
<div>== Synopsis ==<br />
<br />
Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of the uncertainty out of installing and operating a linux PC, the opportunity is ripe for TACLog die-hards to consider change.<br />
<br />
A modern Linux 'Workstation' desktop is not ~that~ far removed from the perhaps more familiar Windows® environment and has all of the necessary tools available by default, along with a 'package manager' to assist in installing readily available software for all manner of purposes.<br />
<br />
When you decide that you need a 21st century TACLog; Tucnak is, inevitably, the way-to-go. <br />
<br />
Tucnak maintains the freeform QSO entry style previously unique to TACLog; all of the operational F-key sequences; the Voice and CW keyers; along with many crucial enhancements particularly of relevance to multi-multi V/U/SHF contesting.<br />
<br />
These features are well-described elsewhere. With this article I wish to outline the relative simplicity of converting a version 1,9xx TACLog C_W file to work on a Tucnak installation.<br />
<br />
== Method ==<br />
<br />
The TACLog C_W (callsign) file is incompatible with Tucnak but can be converted so that all that history is not lost when migrating from MS-DOS® to Linux.<br />
<br />
Most (all?) TACLog users will know how to update the callsign file (C_W file) with information obtained from a new contest - [MM-4-5-1] `Add C_Ws from data'.<br><br />
Many will also know that the C_W file is held in a special format (Pascal Record type) which means that it is unsuitable for direct manipulation by simple tools such as a text editor. Some will know that the C_W file can be converted to a pure text format (readable in EDIT or MS Notepad) using the C_W-to-Text converter utility called `C_W.EXE' found in the main TACLOG directory, (commonly C:\TACLOG).<br><br />
<br />
This `HOW-TO' requires some DOS-jockey work and some Linux command line ops and expects some familiarity with the Linux GUI environment and file manager but is safe to use and will not obliterate your data! I will provide some screen shots and a step-by-step description of the process. Those readers familiar with C_W.EXE may skip down to Step 4 directly, as you are likely to already have your C_W data in TACLOG.TXT format.<br />
<br />
<br />
<br />
== Outline ==<br />
<br />
* Convert TACLOG.C_W to TACLOG.TXT using C_W.EXE (distributed with TACLog)<br />
* Copy TACLOG.TXT to the Tucnak linux machine.<br />
* Convert TACLOG.TXT (CALL LOC LOC2 DATE) to Tucnak format with tac2tuc.pl (distributed with Tucnak v2.13 & later)<br />
* Copy the output file to the Tucnak directory while renaming it to tucnakcw<br />
* Run Tucnak with your own, historical, callsign data<br />
<br />
<br />
<br />
== Prerequisites ==<br />
<br />
* I expect that you will have installed Tucnak using a 'package manager', the command-line installer tool appropriate to your distribution (yum, apt-get, emerge, etc) or by compiling the source-code available elsewhere on this site. I also expect you to have run it up and maybe played around some - if just for curiosity.<br />
* A working copy of TACLog or, at least, a valid TACLOG.C_W file (which can be found in the main <Drive>:\TACLOG directory on your DOS or Windows machine). <br><br />
* A recent version of C_W.EXE (distributed with TACLog and again found in the main directory). <br><br />
* access to `tac2tuc.pl' from an installed version of Tucnak 2.13 or later (/usr/[local/]share/tucnak2/tac2tuc.pl) or the source code of Tucnak v2.13 or later (.../tucnak2-2.13/share/tac2tuc.pl) or a download of tac2tuc.pl from [http://www.g1ogy.com/softitems.html g1ogy.com] <br><br />
* `perl' installed on your Tucnak (linux) machine (usually by default). <br><br />
<br />
----<br />
<br />
''OK? Got your toolbox? Let's get to work! '' <br><br />
<br />
----<br />
<br />
== Step by Step ==<br />
<br />
*Step 1.<br><br />
On your TACLog machine (DOS or Windows® - your choice) create a 'working directory' so that there will be no confusion about where and what we are doing. We'll call it <code>C:\TACWORK</code>. You will need maximum 5MB of working-space (that's small, but significant on an old DOS box).<br />
<br />
*Step 2.<br><br />
Find the TACLOG directory. From there, COPY (not move!) the two files: <code>TACLOG.C_W</code> and <code>C_W.EXE</code> into <code>C:\TACWORK</code>. <br><br />
<br />
*Step 3.<br><br />
If you are in Windows® start a Command Prompt window (win9x = start | Run | command <code>[Enter]</code> : in Win 2000/WinXP/Vista = Start | Run | cmd <code>[Enter]</code>) <br><br />
Now Change Directory [CD] to your <code>TACWORK</code> directory.<br />
<br />
Type: <br />
<code>C_W [Enter]</code><br><br />
<br />
Here is the HELP for <code>C_W.EXE</code>. It is pretty simple. You will see that <code>C_W.EXE</code> has an `automatic' mode that converts <code>TACLOG.C_W</code> into <code>TACLOG.TXT</code> using the '0' command parameter.<br><br />
Type:<br><br />
<code>C_W 0 TACLOG.C_W [Enter]</code><br><br />
<br />
A few seconds later you will have a file called <code>TACLOG.TXT</code> which will open in MS Notepad or EDIT.COM and look something like this, format-wise:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT JN75TR 20010825<br />
9A0DX JN82IW JN83JA 20020601<br />
9A0M JN86EL JN86FJ 20010305<br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
Notice (above) <b>that there are two locators on the same line for some of the calls</b>, followed by the ~most recent~ date that that call was changed in the file. This format is not the same as Tucnak uses and so it must be converted to look something like this:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT 20010825<br />
9A0C JN75TR<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA<br />
9A0M JN86EL 20010305<br />
9A0M JN86FJ <br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
This is where the program <code>tac2tuc.pl</code> comes in. <br />
<br />
You'll now notice that there is an extra row for each callsign that had two locators in the TACLog list. You'll also notice that the new lines for the second locator have no date. The perl program called <code>tac2tuc.pl</code> will fill in this date with 12 December 1901. Why? The line needs a date for Tucnak, there is no information available about the true date and Well, what happened on 12/12/1901? It is as good a 'default' date for a "radio" program as any I can think of ! And because it is so long ago, it also makes sure that the first locator retains its place-precedence when displayed on the Tucnak input line - just like TACLog. <br><br />
<pre><br />
9A0C JN75XT 20010825<br />
9A0C JN75TR 19011212<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA 19011212<br />
9A0M JN86EL 20010305<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
A note about Linux "users": You may know that linux has the notion of "users" with names and passwords who are allowed to log in and operate the machine - this is like Windows NT or XP or (gulp!) Vista. You may not know that more than one user can log in to a linux machine at the same time to do work and each user has their own working space on the disk for data and (by choice) programs. These working spaces are known as HOME directories.<br />
<br />
When you install a linux distribution it will (usually) ask you to enter a user name (and password) for the "usual" user of the machine. There will also be a user <code> root </code> created. This is the SuperUser or Administrator account and with modern 'workstation' linuxes is not usually directly used. You can also create more users after the installation is done and the box is up and running. I often create a user called <code>radio</code> and run all my live contest operations in that guise. This means that I can mess-around or experiment in my personal user account and working space and not damage or disturb the proper 'contest' logs.<br />
<br />
So, I suggest that TACLOG.TXT is copied to your personal home directory - not 'radio' - so that you can experiment in relative safety. <code>tac2tuc.pl</code> may be copied there as well. You might like to make a directory <code>tucwork</code> here to use for any conversions or other experiments with Tucnak data. Please do <b>not</b> put the conversion files into the <code>tucnak</code> directory if there is one there already or you are tempted to make one. <code>/home/<user-name>/tucnak</code> is where the Tucnak program ~itself~ will write files - we do not want to confuse ourselves or the program!<br />
<br />
<br />
*Step 4.<br><br />
<br />
On the linux machine, logged in as your normal user, create a directory <code>tucwork</code> [ you can use the GUI File Manager or the Command line: <code> mkdir tucwork </code> ].<br />
<br />
*Step 5.<br><br />
You must now find a way to get the file <code>C:\TACWORK\TACLOG.TXT</code> from the DOS/WINDOWS machine on to the Linux machine. Floppy disk; USB 'stick'; network copy; can each be used. I will leave the choice of method up to the operator!<br />
<br />
*Step 6.<br><br />
On linux, open a terminal window. Usually you will already be in your HOME directory, so Change Directory - `cd' - to your <code>tucwork</code> directory where you copied <code>TACLOG.TXT</code> (Step 5) and where you should copy <code>tac2tuc.pl</code>, however you have obtained it. See: Prerequisites<br />
<br />
type:<br><br />
<code> $ ls [Enter] </code><br />
<br />
Check the Letter CASE (upper/lower) of the file <code>TACLOG.TXT</code>. In some instances it will remain in DOS-like 'UPPER' case, on others it may be converted to 'lower' case or possibly 'Camel' case. Linux file names are <b>case sensitive</b> so it is important that you know how to type:<br />
<br />
<code> $ perl tac2tuc.pl TACLOG.TXT [Enter]</code><br />
<br />
Do it!.<br><br />
A few seconds later there will be a file called <code>tac2tuc.cw</code> waiting to be checked. You can open it in the Linux GUI Text Editor (gedit) or with a text-mode editor (vi or nano).<br />
<br />
*Step 7.<br><br />
I would do:<br><br />
<code> $ cp tac2tuc.cw tac2tuc.cw.YYYYMMDD </code> (where these letters represent Y-ear, M-onth and D-ay)<br />
This retains a safety copy in your <code>tucwork</code> directory.<br><br />
Then:<br><br />
<code> $ cp tac2tuc.cw ../tucnak/tucnakcw </code><br><br />
This makes a copy in the current user's local tucnak directory<br><br />
and if you already have a `radio' user on the PC<br><br />
<br />
<code> $ sudo cp tac2tuc.cw /home/radio/tucnak/tucnakcw </code><br />
<br />
The <code>sudo</code> program allows you to become `superuser' for just that one <code>copy</code> command and write the file into another user's `home' directory. It will ask for a password - this is your own (logged on user) password not that of the superuser nor the `radio' user.<br />
<br />
*Step 8.<br><br />
Now, start up Tucnak, create a test contest and enter a known callsign on the input line plus <code>[Enter]</code>. Observe the appearance of the relevant locator(s), in reverse video, just like TACLog!<br />
You will also see the partial-call lookup feature in operation (just enter prefix-number-first letter). Now try entering just a locator...<br />
(checkout the Tucnak Hot-Key listing [http://tucnak.nagano.cz/wiki/Hotkeys here] ).<br><br />
<br />
You are done! CU in the contest....<br><br />
--'OGY 00:12, 12 September 2008 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Converting_TACLog_v_1,9xx_C_W_files_for_use_with_Tucnak&diff=1168Converting TACLog v 1,9xx C W files for use with Tucnak2009-11-02T00:36:12Z<p>G1ogy: </p>
<hr />
<div>== Synopsis ==<br />
<br />
Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of the uncertainty out of installing and operating a linux PC, the opportunity is ripe for TACLog die-hards to consider change.<br />
<br />
A modern Linux 'Workstation' desktop is not ~that~ far removed from the perhaps more familiar Windows® environment and has all of the necessary tools available by default, along with a 'package manager' to assist in installing readily available software for all manner of purposes.<br />
<br />
When you decide that you need a 21st century TACLog; Tucnak is, inevitably, the way-to-go. <br />
<br />
Tucnak maintains the freeform QSO entry style previously unique to TACLog; all of the operational F-key sequences; the Voice and CW keyers; along with many crucial enhancements particularly of relevance to multi-multi V/U/SHF contesting.<br />
<br />
These features are well-described elsewhere. With this article I wish to outline the relative simplicity of converting a version 1,9xx TACLog C_W file to work on a Tucnak installation.<br />
<br />
== Method ==<br />
<br />
The TACLog C_W (callsign) file is incompatible with Tucnak but can be converted so that all that history is not lost when migrating from MS-DOS® to Linux.<br />
<br />
Most (all?) TACLog users will know how to update the callsign file (C_W file) with information obtained from a new contest - [MM-4-5-1] `Add C_Ws from data'.<br><br />
Many will also know that the C_W file is held in a special format (Pascal Record type) which means that it is unsuitable for direct manipulation by simple tools such as a text editor. Some will know that the C_W file can be converted to a pure text format (readable in EDIT or MS Notepad) using the C_W-to-Text converter utility called `C_W.EXE' found in the main TACLOG directory, (commonly C:\TACLOG).<br><br />
<br />
This `HOW-TO' requires some DOS-jockey work and some Linux command line ops and expects some familiarity with the Linux GUI environment and file manager but is safe to use and will not obliterate your data! I will provide some screen shots and a step-by-step description of the process. Those readers familiar with C_W.EXE may skip down to Step 4 directly, as you are likely to already have your C_W data in TACLOG.TXT format.<br />
<br />
<br />
<br />
== Outline ==<br />
<br />
* Convert TACLOG.C_W to TACLOG.TXT using C_W.EXE (distributed with TACLog)<br />
* Copy TACLOG.TXT to the Tucnak linux machine.<br />
* Convert TACLOG.TXT (CALL LOC LOC2 DATE) to Tucnak format with tac2tuc.pl (distributed with Tucnak v2.13 & later)<br />
* Copy the output file to the Tucnak directory while renaming it to tucnakcw<br />
* Run Tucnak with your own, historical, callsign data<br />
<br />
<br />
<br />
== Prerequisites ==<br />
<br />
* I expect that you will have installed Tucnak using a 'package manager', the command-line installer tool appropriate to your distribution (yum, apt-get, emerge, etc) or by compiling the source-code available elsewhere on this site. I also expect you to have run it up and maybe played around some - if just for curiosity.<br />
* A working copy of TACLog or, at least, a valid TACLOG.C_W file (which can be found in the main <Drive>:\TACLOG directory on your DOS or Windows machine). <br><br />
* A recent version of C_W.EXE (distributed with TACLog and again found in the main directory). <br><br />
* access to `tac2tuc.pl' from an installed version of Tucnak 2.13 or later (/usr/[local/]share/tucnak2/tac2tuc.pl) or the source code of Tucnak v2.13 or later (.../tucnak2-2.13/share/tac2tuc.pl) or a download of tac2tuc.pl from [http://www.g1ogy.com/softitems.html g1ogy.com] <br><br />
* `perl' installed on your Tucnak (linux) machine (usually by default). <br><br />
<br />
----<br />
<br />
''OK? Got your toolbox? Let's get to work! '' <br><br />
<br />
----<br />
<br />
== Step by Step ==<br />
<br />
*Step 1.<br><br />
On your TACLog machine (DOS or Windows® - your choice) create a 'working directory' so that there will be no confusion about where and what we are doing. We'll call it <code>C:\TACWORK</code>. You will need maximum 5MB of working-space (that's small, but significant on an old DOS box).<br />
<br />
*Step 2.<br><br />
Find the TACLOG directory. From there, COPY (not move!) the two files: <code>TACLOG.C_W</code> and <code>C_W.EXE</code> into <code>C:\TACWORK</code>. <br><br />
<br />
*Step 3.<br><br />
If you are in Windows® start a Command Prompt window (win9x = start | Run | command <code>[Enter]</code> : in Win 2000/WinXP/Vista = Start | Run | cmd <code>[Enter]</code>) <br><br />
Now Change Directory [CD] to your <code>TACWORK</code> directory.<br />
<br />
Type: <br />
<code>C_W [Enter]</code><br><br />
<br />
Here is the HELP for <code>C_W.EXE</code>. It is pretty simple. You will see that <code>C_W.EXE</code> has an `automatic' mode that converts <code>TACLOG.C_W</code> into <code>TACLOG.TXT</code> using the '0' command parameter.<br><br />
Type:<br><br />
<code>C_W 0 TACLOG.C_W [Enter]</code><br><br />
<br />
A few seconds later you will have a file called <code>TACLOG.TXT</code> which will open in MS Notepad or EDIT.COM and look something like this, format-wise:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT JN75TR 20010825<br />
9A0DX JN82IW JN83JA 20020601<br />
9A0M JN86EL JN86FJ 20010305<br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
Notice (above) <b>that there are two locators on the same line for some of the calls</b>, followed by the ~most recent~ date that that call was changed in the file. This format is not the same as Tucnak uses and so it must be converted to look something like this:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT 20010825<br />
9A0C JN75TR<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA<br />
9A0M JN86EL 20010305<br />
9A0M JN86FJ <br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
This is where the program <code>tac2tuc.pl</code> comes in. <br />
<br />
You'll now notice that there is an extra row for each callsign that had two locators in the TACLog list. You'll also notice that the new lines for the second locator have no date. The perl program called <code>tac2tuc.pl</code> will fill in this date with 12 December 1901. Why? The line needs a date for Tucnak, there is no information available about the true date and Well, what happened on 12/12/1901? It is as good a 'default' date for a "radio" program as any I can think of ! And because it is so long ago, it also makes sure that the first locator retains its place-precedence when displayed on the Tucnak input line - just like TACLog. <br><br />
<pre><br />
9A0C JN75XT 20010825<br />
9A0C JN75TR 19011212<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA 19011212<br />
9A0M JN86EL 20010305<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
A note about Linux "users": You may know that linux has the notion of "users" with names and passwords who are allowed to log in and operate the machine - this is like Windows NT or XP or (gulp!) Vista. You may not know that more than one user can log in to a linux machine at the same time to do work and each user has their own working space on the disk for data and (by choice) programs. These working spaces are known as HOME directories.<br />
<br />
When you install a linux distribution it will (usually) ask you to enter a user name (and password) for the "usual" user of the machine. There will also be a user <code> root </code> created. This is the SuperUser or Administrator account and with modern 'workstation' linuxes is not usually directly used. You can also create more users after the installation is done and the box is up and running. I often create a user called <code>radio</code> and run all my live contest operations in that guise. This means that I can mess-around or experiment in my personal user account and working space and not damage or disturb the proper 'contest' logs.<br />
<br />
So, I suggest that TACLOG.TXT is copied to your personal home directory - not 'radio' - so that you can experiment in relative safety. <code>tac2tuc.pl</code> may be copied there as well. You might like to make a directory <code>tucwork</code> here to use for any conversions or other experiments with Tucnak data. Please do <b>not</b> put the conversion files into the <code>tucnak</code> directory if there is one there already or you are tempted to make one. <code>/home/<user-name>/tucnak</code> is where the Tucnak program ~itself~ will write files - we do not want to confuse ourselves or the program!<br />
<br />
<br />
*Step 4.<br><br />
<br />
On the linux machine, logged in as your normal user, create a directory <code>tucwork</code> [ you can use the GUI File Manager or the Command line: <code> mkdir tucwork </code> ].<br />
<br />
*Step 5.<br><br />
You must now find a way to get the file <code>C:\TACWORK\TACLOG.TXT</code> from the DOS/WINDOWS machine on to the Linux machine. Floppy disk; USB 'stick'; network copy; can each be used. I will leave the choice of method up to the operator!<br />
<br />
*Step 6.<br><br />
On linux, open a terminal window. Usually you will already be in your HOME directory, so Change Directory - `cd' - to your <code>tucwork</code> directory where you copied <code>TACLOG.TXT</code> (Step 5) and where you should copy <code>tac2tuc.pl</code>, however you have obtained it. See: Prerequisites<br />
<br />
type:<br><br />
<code> $ ls [Enter] </code><br />
<br />
Check the Letter CASE (upper/lower) of the file <code>TACLOG.TXT</code>. In some instances it will remain in DOS-like 'UPPER' case, on others it may be converted to 'lower' case or possibly 'Camel' case. Linux file names are <b>case sensitive</b> so it is important that you know how to type:<br />
<br />
<code> $ perl tac2tuc.pl TACLOG.TXT [Enter]</code><br />
<br />
Do it!.<br><br />
A few seconds later there will be a file called <code>tac2tuc.cw</code> waiting to be checked. You can open it in the Linux GUI Text Editor (gedit) or with a text-mode editor (vi or nano).<br />
<br />
*Step 7.<br><br />
I would do:<br><br />
<code> $ cp tac2tuc.cw tac2tuc.cw.YYYYMMDD </code> (where these letters represent Y-ear, M-onth and D-ay)<br />
This retains a safety copy in your <code>tucwork</code> directory.<br><br />
Then:<br><br />
<code> $ cp tac2tuc.cw ../tucnak/tucnakcw </code><br><br />
This makes a copy in the current user's local tucnak directory<br><br />
and if you already have a `radio' user on the PC<br><br />
<br />
<code> $ sudo cp tac2tuc.cw /home/radio/tucnak/tucnakcw </code><br />
<br />
The <code>sudo</code> program allows you to become `superuser' for just that one <code>copy</code> command and write the file into another user's `home' directory. It will ask for a password - this is your own (logged on user) password not that of the superuser nor the `radio' user.<br />
<br />
*Step 8.<br><br />
Now, start up Tucnak, create a test contest and enter a known callsign on the input line plus <code>[Enter]</code>. Observe the appearance of the relevant locator(s), in reverse video, just like TACLog!<br />
You will also see the partial-call lookup feature in operation (just enter prefix-number-first letter). Now try entering just a locator...<br />
(checkout the Tucnak Hot-Key listing [http://tucnak.nagano.cz/wiki/Hotkeys here] ).<br><br />
<br />
You are done! CU in the contest....<br><br />
--'OGY 00:12, 2 November 2008 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Converting_TACLog_v_1,9xx_C_W_files_for_use_with_Tucnak&diff=1167Converting TACLog v 1,9xx C W files for use with Tucnak2009-11-02T00:34:56Z<p>G1ogy: </p>
<hr />
<div><br />
== Synopsis ==<br />
<br />
Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of the uncertainty out of installing and operating a linux PC, the opportunity is ripe for TACLog die-hards to consider change.<br />
<br />
A modern Linux 'Workstation' desktop is not ~that~ far removed from the perhaps more familiar Windows® environment and has all of the necessary tools available by default, along with a 'package manager' to assist in installing readily available software for all manner of purposes.<br />
<br />
When you decide that you need a 21st century TACLog; Tucnak is, inevitably, the way-to-go. <br />
<br />
Tucnak maintains the freeform QSO entry style previously unique to TACLog; all of the operational F-key sequences; the Voice and CW keyers; along with many crucial enhancements particularly of relevance to multi-multi V/U/SHF contesting.<br />
<br />
These features are well-described elsewhere. With this article I wish to outline the relative simplicity of converting a version 1,9xx TACLog C_W file to work on a Tucnak installation.<br />
<br />
== Method ==<br />
<br />
The TACLog C_W (callsign) file is incompatible with Tucnak but can be converted so that all that history is not lost when migrating from MS-DOS® to Linux.<br />
<br />
Most (all?) TACLog users will know how to update the callsign file (C_W file) with information obtained from a new contest - [MM-4-5-1] `Add C_Ws from data'.<br><br />
Many will also know that the C_W file is held in a special format (Pascal Record type) which means that it is unsuitable for direct manipulation by simple tools such as a text editor. Some will know that the C_W file can be converted to a pure text format (readable in EDIT or MS Notepad) using the C_W-to-Text converter utility called `C_W.EXE' found in the main TACLOG directory, (commonly C:\TACLOG).<br><br />
<br />
This `HOW-TO' requires some DOS-jockey work and some Linux command line ops and expects some familiarity with the Linux GUI environment and file manager but is safe to use and will not obliterate your data! I will provide some screen shots and a step-by-step description of the process. Those readers familiar with C_W.EXE may skip down to Step 4 directly, as you are likely to already have your C_W data in TACLOG.TXT format.<br />
<br />
<br />
<br />
== Outline ==<br />
<br />
* Convert TACLOG.C_W to TACLOG.TXT using C_W.EXE (distributed with TACLog)<br />
* Copy TACLOG.TXT to the Tucnak linux machine.<br />
* Convert TACLOG.TXT (CALL LOC LOC2 DATE) to Tucnak format with tac2tuc.pl (distributed with Tucnak v2.13 & later)<br />
* Copy the output file to the Tucnak directory while renaming it to tucnakcw<br />
* Run Tucnak with your own, historical, callsign data<br />
<br />
<br />
<br />
== Prerequisites ==<br />
<br />
* I expect that you will have installed Tucnak using a 'package manager', the command-line installer tool appropriate to your distribution (yum, apt-get, emerge, etc) or by compiling the source-code available elsewhere on this site. I also expect you to have run it up and maybe played around some - if just for curiosity.<br />
* A working copy of TACLog or, at least, a valid TACLOG.C_W file (which can be found in the main <Drive>:\TACLOG directory on your DOS or Windows machine). <br><br />
* A recent version of C_W.EXE (distributed with TACLog and again found in the main directory). <br><br />
* access to `tac2tuc.pl' from an installed version of Tucnak 2.13 or later (/usr/[local/]share/tucnak2/tac2tuc.pl) or the source code of Tucnak v2.13 or later (.../tucnak2-2.13/share/tac2tuc.pl) or a download of tac2tuc.pl from [http://www.g1ogy.com/softitems.html g1ogy.com] <br><br />
* `perl' installed on your Tucnak (linux) machine (usually by default). <br><br />
<br />
----<br />
<br />
''OK? Got your toolbox? Let's get to work! '' <br><br />
<br />
----<br />
<br />
== Step by Step ==<br />
<br />
*Step 1.<br><br />
On your TACLog machine (DOS or Windows® - your choice) create a 'working directory' so that there will be no confusion about where and what we are doing. We'll call it <code>C:\TACWORK</code>. You will need maximum 5MB of working-space (that's small, but significant on an old DOS box).<br />
<br />
*Step 2.<br><br />
Find the TACLOG directory. From there, COPY (not move!) the two files: <code>TACLOG.C_W</code> and <code>C_W.EXE</code> into <code>C:\TACWORK</code>. <br><br />
<br />
*Step 3.<br><br />
If you are in Windows® start a Command Prompt window (win9x = start | Run | command <code>[Enter]</code> : in Win 2000/WinXP/Vista = Start | Run | cmd <code>[Enter]</code>) <br><br />
Now Change Directory [CD] to your <code>TACWORK</code> directory.<br />
<br />
Type: <br />
<code>C_W [Enter]</code><br><br />
<br />
Here is the HELP for <code>C_W.EXE</code>. It is pretty simple. You will see that <code>C_W.EXE</code> has an `automatic' mode that converts <code>TACLOG.C_W</code> into <code>TACLOG.TXT</code> using the '0' command parameter.<br><br />
Type:<br><br />
<code>C_W 0 TACLOG.C_W [Enter]</code><br><br />
<br />
A few seconds later you will have a file called <code>TACLOG.TXT</code> which will open in MS Notepad or EDIT.COM and look something like this, format-wise:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT JN75TR 20010825<br />
9A0DX JN82IW JN83JA 20020601<br />
9A0M JN86EL JN86FJ 20010305<br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
Notice (above) <b>that there are two locators on the same line for some of the calls</b>, followed by the ~most recent~ date that that call was changed in the file. This format is not the same as Tucnak uses and so it must be converted to look something like this:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT 20010825<br />
9A0C JN75TR<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA<br />
9A0M JN86EL 20010305<br />
9A0M JN86FJ <br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
This is where the program <code>tac2tuc.pl</code> comes in. <br />
<br />
You'll now notice that there is an extra row for each callsign that had two locators in the TACLog list. You'll also notice that the new lines for the second locator have no date. The perl program called <code>tac2tuc.pl</code> will fill in this date with 12 December 1901. Why? The line needs a date for Tucnak, there is no information available about the true date and Well, what happened on 12/12/1901? It is as good a 'default' date for a "radio" program as any I can think of ! And because it is so long ago, it also makes sure that the first locator retains its place-precedence when displayed on the Tucnak input line - just like TACLog. <br><br />
<pre><br />
9A0C JN75XT 20010825<br />
9A0C JN75TR 19011212<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA 19011212<br />
9A0M JN86EL 20010305<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
A note about Linux "users": You may know that linux has the notion of "users" with names and passwords who are allowed to log in and operate the machine - this is like Windows NT or XP or (gulp!) Vista. You may not know that more than one user can log in to a linux machine at the same time to do work and each user has their own working space on the disk for data and (by choice) programs. These working spaces are known as HOME directories.<br />
<br />
When you install a linux distribution it will (usually) ask you to enter a user name (and password) for the "usual" user of the machine. There will also be a user <code> root </code> created. This is the SuperUser or Administrator account and with modern 'workstation' linuxes is not usually directly used. You can also create more users after the installation is done and the box is up and running. I often create a user called <code>radio</code> and run all my live contest operations in that guise. This means that I can mess-around or experiment in my personal user account and working space and not damage or disturb the proper 'contest' logs.<br />
<br />
So, I suggest that TACLOG.TXT is copied to your personal home directory - not 'radio' - so that you can experiment in relative safety. <code>tac2tuc.pl</code> may be copied there as well. You might like to make a directory <code>tucwork</code> here to use for any conversions or other experiments with Tucnak data. Please do <b>not</b> put the conversion files into the <code>tucnak</code> directory if there is one there already or you are tempted to make one. <code>/home/<user-name>/tucnak</code> is where the Tucnak program ~itself~ will write files - we do not want to confuse ourselves or the program!<br />
<br />
<br />
*Step 4.<br><br />
<br />
On the linux machine, logged in as your normal user, create a directory <code>tucwork</code> [ you can use the GUI File Manager or the Command line: <code> mkdir tucwork </code> ].<br />
<br />
*Step 5.<br><br />
You must now find a way to get the file <code>C:\TACWORK\TACLOG.TXT</code> from the DOS/WINDOWS machine on to the Linux machine. Floppy disk; USB 'stick'; network copy; can each be used. I will leave the choice of method up to the operator!<br />
<br />
*Step 6.<br><br />
On linux, open a terminal window. Usually you will already be in your HOME directory, so Change Directory - `cd' - to your <code>tucwork</code> directory where you copied <code>TACLOG.TXT</code> (Step 5) and where you should copy <code>tac2tuc.pl</code>, however you have obtained it. See: Prerequisites<br />
<br />
type:<br><br />
<code> $ ls [Enter] </code><br />
<br />
Check the Letter CASE (upper/lower) of the file <code>TACLOG.TXT</code>. In some instances it will remain in DOS-like 'UPPER' case, on others it may be converted to 'lower' case or possibly 'Camel' case. Linux file names are <b>case sensitive</b> so it is important that you know how to type:<br />
<br />
<code> $ perl tac2tuc.pl TACLOG.TXT [Enter]</code><br />
<br />
Do it!.<br><br />
A few seconds later there will be a file called <code>tac2tuc.cw</code> waiting to be checked. You can open it in the Linux GUI Text Editor (gedit) or with a text-mode editor (vi or nano).<br />
<br />
*Step 7.<br><br />
I would do:<br><br />
<code> $ cp tac2tuc.cw tac2tuc.cw.YYYYMMDD </code> (where these letters represent Y-ear, M-onth and D-ay)<br />
This retains a safety copy in your <code>tucwork</code> directory.<br><br />
Then:<br><br />
<code> $ cp tac2tuc.cw ../tucnak/tucnakcw </code><br><br />
This makes a copy in the current user's local tucnak directory<br><br />
and if you already have a `radio' user on the PC<br><br />
<br />
<code> $ sudo cp tac2tuc.cw /home/radio/tucnak/tucnakcw </code><br />
<br />
The <code>sudo</code> program allows you to become `superuser' for just that one <code>copy</code> command and write the file into another user's `home' directory. It will ask for a password - this is your own (logged on user) password not that of the superuser nor the `radio' user.<br />
<br />
*Step 8.<br><br />
Now, start up Tucnak, create a test contest and enter a known callsign on the input line plus <code>[Enter]</code>. Observe the appearance of the relevant locator(s), in reverse video, just like TACLog!<br />
You will also see the partial-call lookup feature in operation (just enter prefix-number-first letter). Now try entering just a locator...<br />
(checkout the Tucnak Hot-Key listing [http://tucnak.nagano.cz/wiki/Hotkeys here] ).<br><br />
<br />
You are done! CU in the contest....<br><br />
--'OGY 00:12, 2 November 2009 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Converting_TACLog_v_1,9xx_C_W_files_for_use_with_Tucnak&diff=1166Converting TACLog v 1,9xx C W files for use with Tucnak2009-11-02T00:12:31Z<p>G1ogy: </p>
<hr />
<div><br />
<br />
== Synopsis ==<br />
<br />
Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of the uncertainty out of installing and operating a linux PC, the opportunity is ripe for TACLog die-hards to consider change.<br />
<br />
A modern Linux 'Workstation' desktop is not ~that~ far removed from the perhaps more familiar Windows® environment and has all of the necessary tools available by default, along with a 'package manager' to assist in installing readily available software for all manner of purposes.<br />
<br />
When you decide that you need a 21st century TACLog; Tucnak is, inevitably, the way-to-go. <br />
<br />
Tucnak maintains the freeform QSO entry style previously unique to TACLog; all of the operational F-key sequences; the Voice and CW keyers; along with many crucial enhancements particularly of relevance to multi-multi V/U/SHF contesting.<br />
<br />
These features are well-described elsewhere. With this article I wish to outline the relative simplicity of converting a version 1,9xx TACLog C_W file to work on a Tucnak installation.<br />
<br />
== Method ==<br />
<br />
The TACLog C_W (callsign) file is incompatible with Tucnak but can be converted so that all that history is not lost when migrating from MS-DOS® to Linux.<br />
<br />
Most (all?) TACLog users will know how to update the callsign file (C_W file) with information obtained from a new contest - [MM-4-5-1] `Add C_Ws from data'.<br><br />
Many will also know that the C_W file is held in a special format (Pascal Record type) which means that it is unsuitable for direct manipulation by simple tools such as a text editor. Some will know that the C_W file can be converted to a pure text format (readable in EDIT or MS Notepad) using the C_W-to-Text converter utility called `C_W.EXE' found in the main TACLOG directory, (commonly C:\TACLOG).<br><br />
<br />
This `HOW-TO' requires some DOS-jockey work and some Linux command line ops and expects some familiarity with the Linux GUI environment and file manager but is safe to use and will not obliterate your data! I will provide some screen shots and a step-by-step description of the process. Those readers familiar with C_W.EXE may skip down to Step 4 directly, as you are likely to already have your C_W data in TACLOG.TXT format.<br />
<br />
<br />
<br />
== Outline ==<br />
<br />
* Convert TACLOG.C_W to TACLOG.TXT using C_W.EXE (distributed with TACLog)<br />
* Copy TACLOG.TXT to the Tucnak linux machine.<br />
* Convert TACLOG.TXT (CALL LOC LOC2 DATE) to Tucnak format with tac2tuc.pl (distributed with Tucnak v2.13 & later)<br />
* Copy the output file to the Tucnak directory while renaming it to tucnakcw<br />
* Run Tucnak with your own callsign data<br />
<br />
<br />
<br />
== Prerequisites ==<br />
<br />
* I expect that you will have installed Tucnak using a 'package manager', the command-line installer tool appropriate to your distribution (yum, apt-get, emerge, etc) or by compiling the source-code available elsewhere on this site. I also expect you to have run it up and maybe played around some - if just for curiosity.<br />
* A working copy of TACLog or, at least, a valid TACLOG.C_W file (which can be found in the main <Drive>:\TACLOG directory on your DOS or Windows machine). <br><br />
* A recent version of C_W.EXE (distributed with TACLog and again found in the main directory). <br><br />
* access to `tac2tuc.pl' from an installed version of Tucnak 2.13 or later (/usr/[local/]share/tucnak2/tac2tuc.pl) or the source code of Tucnak v2.13 or later (.../tucnak2-2.13/share/tac2tuc.pl) or a download of tac2tuc.pl from [http://www.g1ogy.com/softitems.html g1ogy.com] <br><br />
* `perl' installed on your Tucnak (linux) machine (usually by default). <br><br />
<br />
----<br />
<br />
''OK? Got your toolbox? Let's get to work! '' <br><br />
<br />
----<br />
<br />
== Step by Step ==<br />
<br />
*Step 1.<br><br />
On your TACLog machine (DOS or Windows® - your choice) create a 'working directory' so that there will be no confusion about where and what we are doing. We'll call it <code>C:\TACWORK</code>. You will need maximum 5MB of working-space (that's small, but significant on an old DOS box).<br />
<br />
*Step 2.<br><br />
Find the TACLOG directory. From there, COPY (not move!) the two files: <code>TACLOG.C_W</code> and <code>C_W.EXE</code> into <code>C:\TACWORK</code>. <br><br />
<br />
*Step 3.<br><br />
If you are in Windows® start a Command Prompt window (win9x = start | Run | command <code>[Enter]</code> : in Win 2000/WinXP/Vista = Start | Run | cmd <code>[Enter]</code>) <br><br />
Now Change Directory [CD] to your <code>TACWORK</code> directory.<br />
<br />
Type: <br />
<code>C_W [Enter]</code><br><br />
<br />
Here is the HELP for <code>C_W.EXE</code>. It is pretty simple. You will see that <code>C_W.EXE</code> has an `automatic' mode that converts <code>TACLOG.C_W</code> into <code>TACLOG.TXT</code> using the '0' command parameter.<br><br />
Type:<br><br />
<code>C_W 0 TACLOG.C_W [Enter]</code><br><br />
<br />
A few seconds later you will have a file called <code>TACLOG.TXT</code> which will open in MS Notepad or EDIT.COM and look something like this, format-wise:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT JN75TR 20010825<br />
9A0DX JN82IW JN83JA 20020601<br />
9A0M JN86EL JN86FJ 20010305<br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
Notice (above) <b>that there are two locators on the same line for some of the calls</b>, followed by the ~most recent~ date that that call was changed in the file. This format is not the same as Tucnak uses and so it must be converted to look something like this:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT 20010825<br />
9A0C JN75TR<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA<br />
9A0M JN86EL 20010305<br />
9A0M JN86FJ <br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
This is where the program <code>tac2tuc.pl</code> comes in. <br />
<br />
You'll now notice that there is an extra row for each callsign that had two locators in the TACLog list. You'll also notice that the new lines for the second locator have no date. The perl program called <code>tac2tuc.pl</code> will fill in this date with 12 December 1901. Why? The line needs a date for Tucnak, there is no information available about the true date and Well, what happened on 12/12/1901? It is as good a 'default' date for a "radio" program as any I can think of ! And because it is so long ago, it also makes sure that the first locator retains its place-precedence when displayed on the Tucnak input line - just like TACLog. <br><br />
<pre><br />
9A0C JN75XT 20010825<br />
9A0C JN75TR 19011212<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA 19011212<br />
9A0M JN86EL 20010305<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
A note about Linux "users": You may know that linux has the notion of "users" with names and passwords who are allowed to log in and operate the machine - this is like Windows NT or XP or (gulp!) Vista. You may not know that more than one user can log in to a linux machine at the same time to do work and each user has their own working space on the disk for data and (by choice) programs. These working spaces are known as HOME directories.<br />
<br />
When you install a linux distribution it will (usually) ask you to enter a user name (and password) for the "usual" user of the machine. There will also be a user <code> root </code> created. This is the SuperUser or Administrator account and with modern 'workstation' linuxes is not usually directly used. You can also create more users after the installation is done and the box is up and running. I often create a user called <code>radio</code> and run all my live contest operations in that guise. This means that I can mess-around or experiment in my personal user account and working space and not damage or disturb the proper 'contest' logs.<br />
<br />
So, I suggest that TACLOG.TXT is copied to your personal home directory - not 'radio' - so that you can experiment in relative safety. <code>tac2tuc.pl</code> may be copied there as well. You might like to make a directory <code>tucwork</code> here to use for any conversions or other experiments with Tucnak data. Please do <b>not</b> put the conversion files into the <code>tucnak</code> directory if there is one there already or you are tempted to make one. <code>/home/<user-name>/tucnak</code> is where the Tucnak program ~itself~ will write files - we do not want to confuse ourselves or the program!<br />
<br />
<br />
*Step 4.<br><br />
<br />
On the linux machine, logged in as your normal user, create a directory <code>tucwork</code> [ you can use the GUI File Manager or the Command line: <code> mkdir tucwork </code> ].<br />
<br />
*Step 5.<br><br />
You must now find a way to get the file <code>C:\TACWORK\TACLOG.TXT</code> from the DOS/WINDOWS machine on to the Linux machine. Floppy disk; USB 'stick'; network copy; can each be used. I will leave the choice of method up to the operator!<br />
<br />
*Step 6.<br><br />
On linux, open a terminal window. Usually you will already be in your HOME directory, so Change Directory - `cd' - to your <code>tucwork</code> directory where you copied <code>TACLOG.TXT</code> (Step 5) and where you should copy <code>tac2tuc.pl</code>, however you have obtained it. See: Prerequisites<br />
<br />
type:<br><br />
<code> $ ls [Enter] </code><br />
<br />
Check the Letter CASE (upper/lower) of the file <code>TACLOG.TXT</code>. In some instances it will remain in DOS-like 'UPPER' case, on others it may be converted to 'lower' case or possibly 'Camel' case. Linux file names are <b>case sensitive</b> so it is important that you know how to type:<br />
<br />
<code> $ perl tac2tuc.pl TACLOG.TXT [Enter]</code><br />
<br />
Do it!.<br><br />
A few seconds later there will be a file called <code>tac2tuc.cw</code> waiting to be checked. You can open it in the Linux GUI Text Editor (gedit) or with a text-mode editor (vi or nano).<br />
<br />
*Step 7.<br><br />
I would do:<br><br />
<code> $ cp tac2tuc.cw tac2tuc.cw.YYYYMMDD </code> (where these letters represent Y-ear, M-onth and D-ay)<br />
This retains a safety copy in your <code>tucwork</code> directory.<br><br />
Then:<br><br />
<code> $ cp tac2tuc.cw ../tucnak/tucnakcw </code><br><br />
This makes a copy in the current user's local tucnak directory<br><br />
and if you already have a `radio' user on the PC<br><br />
<br />
<code> $ sudo cp tac2tuc.cw /home/radio/tucnak/tucnakcw </code><br />
<br />
The <code>sudo</code> program allows you to become `superuser' for just that one <code>copy</code> command and write the file into another user's `home' directory. It will ask for a password - this is your own (logged on user) password not that of the superuser nor the `radio' user.<br />
<br />
*Step 8.<br><br />
Now, start up Tucnak, create a test contest and enter a known callsign on the input line plus <code>[Enter]</code>. Observe the appearance of the relevant locator(s), in reverse video, just like TACLog!<br />
You will also see the partial-call lookup feature in operation (just enter prefix-number-first letter). Now try entering just a locator...<br />
(checkout the Tucnak Hot-Key listing [http://tucnak.nagano.cz/wiki/Hotkeys here] ).<br><br />
<br />
You are done! CU in the contest....<br><br />
--'OGY 00:12, 2 November 2009 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Notes_on_hand-editing_Tucnak_EDI_files_for_G-land_OE_Contests&diff=1165Notes on hand-editing Tucnak EDI files for G-land OE Contests2009-11-01T23:55:18Z<p>G1ogy: /* Background */</p>
<hr />
<div>== Background ==<br />
'''<font color=red>These notes are now obselete''' because OE/EXC handling for all G-Land Multiplier Contests are included within tucnak starting with v 2.20.<br><br />
Many thanks!</font><br />
<br />
----<br />
<br />
Every year, in the UK VHF&up Contest calendar, there are 6 contests (plus the whole 'Backpacker' series) that use the exchange of 'Postal District code' as an additional Multiplier - an "Optional Exchange" or "OE".<br><br />
In certain parts of the UK the postal districts cover a large area so, to promote activity to and from these areas, their District Code can be counted more than once: 3x for GM Districts and 6x for GI.<br />
<br />
Tucnak does not (yet) support multi-counting of OEs. Nor does it print a list of OEs worked during the contest in the 'Statistics' output file. <br />
<br />
To summarise:<br />
<br />
*1) 'G' OE Contests may use Postal District (forced to 2 char) for OE <br />
*2) Set "OE Must be inserted = ON" in contest setup. (OEs are too valuable to forget)<br />
*3) Non-G stations get "OO" for OE (there is no OO postal district in G[I|J|M|W|U]-land)<br />
*3) Mistakes - no OE sent or rcvd - get "XX" (there is no XX postal district in G[I|J|M|W|U]-land)<br />
*4) Postal districts in GM and GI can be worked multiple times for OE award<br />
<br />
== Post-contest editing ==<br />
<br />
There follows the steps required to hand-edit a Tucnak EDI (Contest Entry) file in order to bring the content of the file into line with RSGB (VHF) Contest Committee regulations: <br />
<br />
*a) Edit** EDI file to set correct (G-style) 'PSect' (Open | Single OP Fixed | Single Op Other | etc, etc).<br />
*b) Edit 'MOpe1'/'MOpe2' as necessary - if 'Global' setting is used for Operator.<br />
*c) Review Statistics File to identify multi-scoring OEs. DXCC listings in the Statistics export will identify GM and GI QSOs and numbers involved. <br />
*d) GI contacts can count 6 OEs for same Postal District (Only 1 PD in whole of GI ('BT'))<br />
*e) Find and manually note all GM contacts and count Q/OE. GM PDs count up to 3 times per OE.<br />
*f) Find first "OO" QSO: Edit the Multiplier section (end of row) to remove multiplier 'N' for the OE (first 'N' column). Same for 'XX' if used.<br />
*g) 'Search & Replace' ;OO; with ;; - same for XX if used. G-land contest adjudicator MAY penalise "incorrect" OE of "OO" or "XX".<br />
*h) IN/DE-crement 'CExcs' as appropriate (Take away 'OO' and 'XX'; Add any Multi-counting GM/GI OEs)<br />
*i) Total up correct Multipliers and replace 'CToSc' with product: [CQSOP x Total Mult]<br />
<br />
Save and close.<br />
<br />
Edit** means use a pure TEXT editor (Gedit, vi, TextPad, MS Notepad) not a "Word processor". <br />
<br />
<br />
--'OGY 01:17, 17 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%22Karmic%22_(9.10)&diff=1164Ubuntu "Karmic" (9.10)2009-11-01T23:48:06Z<p>G1ogy: /* Compiling Tucnak on Ubuntu 9.10 - Karmic [64-bit] */</p>
<hr />
<div>== Compiling Tucnak on Ubuntu 9.10 - Karmic [64-bit] ==<br />
<br />
Having acquired Windows 7 64-bit and installed it (not without some interesting departures from the norm) it seemed quite contrary to go with the 64-bit version of the newly released Ubuntu.<br><br />
So, now with Ubuntu 9.10 [64-bit] installed, dual-boot (not without some interesting departures from the norm) activities fell to installing Tucnak. It was a non-op to install from the built .deb files on the website and in any case I wanted a 2.28 so a src build ...<br />
<br />
<code><br />
sudo apt-get install libglib2.0-dev libsndfile-dev libsdl-dev libpng-dev libasound-dev libftdi-dev libgpmg1-dev libaa1-dev libaudio-dev libcaca-dev libcucul-dev libdirectfb-dev libesd0-dev libxext-dev libxt-dev nas libhamlib-dev libfftw3-dev libfftw3-3 audiooss<br />
</code><br />
<br />
seemed appropriate. (completely fresh install of Karmic - not an upgrade. YMMV)<br><br />
<br />
./configure was good and a build and dpkg install to `/usr/local` appears good so far:<br />
Callsign & EXC [OE] lookups, QSO Calculations and the FFT Scope functions all work (limited testing).<br><br />
<br />
There is a .deb available (installs to /usr/local) at [http://www.m1cro.org.uk/tucnak/build-2.28_x-64/tucnak2_2.28-1_amd64.deb tucnak2_2.28-1_amd64] that you can try.<br><br />
(don't concern yourself about the 'amd64' arch. It is only a name - and this was built on an Intel box.)<br><br />
CU in the contest!<br><br />
'73<br><br />
--'OGY 23:39, 1 November 2009 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%22Karmic%22_(9.10)&diff=1163Ubuntu "Karmic" (9.10)2009-11-01T23:39:54Z<p>G1ogy: Created page with '== Compiling Tucnak on Ubuntu 9.10 - Karmic [64-bit] == Having acquired Windows 7 64-bit and installed it (not without some interesting departures from the norm) it seemed quite...'</p>
<hr />
<div>== Compiling Tucnak on Ubuntu 9.10 - Karmic [64-bit] ==<br />
<br />
Having acquired Windows 7 64-bit and installed it (not without some interesting departures from the norm) it seemed quite contrary to go with the 64-bit version of the newly released Ubuntu.<br><br />
So, now with Ubuntu 9.10 [64-bit] installed, dual-boot (not without some interesting departures from the norm) activities fell to installing Tucnak. It was a non-op to install from the built .deb files on the website and in any case I wanted a 2.28 so a src build ...<br />
<br />
<code><br />
sudo apt-get install libglib2.0-dev libsndfile-dev libsdl-dev libpng-dev libasound-dev libftdi-dev libgpmg1-dev libaa1-dev libaudio-dev libcaca-dev libcucul-dev libdirectfb-dev libesd0-dev libxext-dev libxt-dev nas libhamlib-dev libfftw3-dev libfftw3-3 audiooss<br />
</code><br />
<br />
seemed appropriate. (completely fresh install of Karmic - not an upgrade. YMMV)<br><br />
<br />
./configure was good and a build and dpkg install to `/usr/local` appears good so far:<br />
Callsign & OE lookups, QSO Calculations and the FFT Scope functions all work (limited testing).<br><br />
<br />
There is a .deb available (installs to /usr/local) at [http://www.m1cro.org.uk/tucnak/build-2.28_x-64/tucnak2_2.28-1_amd64.deb tucnak2_2.28-1_amd64] that you can try.<br><br />
(don't concern yourself about the 'amd64' arch. It is only a name - and this was built on an Intel box.)<br><br />
CU in the contest!<br><br />
'73<br><br />
--'OGY 23:39, 1 November 2009 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=1162Main Page2009-11-01T23:00:09Z<p>G1ogy: /* Documentation */</p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
If you want to be informed about site changes, add this URL into your RSS reader: http://tucnak.nagano.cz/wiki/index.php?title=Special:Recentchanges&feed=rss<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
*[[DE Main Page|Deutsch]] Maintained by Hannes DK1HJ, tnx!<br />
*[[RU Main Page|Русский]] Maintained by Sergey RA3WND и Vitaliy [[User:UR6LAD|UR6LAD]], tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
* [http://translate.google.cz/translate?hl=ru&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Русский]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
ArchLinux users can build the AUR package [http://aur.archlinux.org/packages.php?ID=29821 tucnak2]<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
**[[Supported Contests]] <br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
** [[After contest]]<br />
* [[Menu]]<br />
** [[Contest]]<br />
** [[File]]<br />
** [[Edit]]<br />
** [[Bands]]<br />
** [[Subwins]]<br />
** [[Setup]]<br />
** [[Help]]<br />
* [[Subwin types]]<br />
* [[Supported hardware]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
<br />
* Installing<br />
** [[Ubuntu "Jaunty" (9.04)]]<br />
** [[Ubuntu "Intrepid" (8.10)]]<br />
* Compiling<br />
** [[Ubuntu "Karmic" (9.10)]]<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]], OK2AIA, HG6Z, OM0AMI, [[User:UR6LAD|UR6LAD]], OK1KQH, OM3KEG.<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[NOW Obselete - Implemented since V 2.20: Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=1161Main Page2009-11-01T22:25:24Z<p>G1ogy: /* Converting from TACLog */</p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
If you want to be informed about site changes, add this URL into your RSS reader: http://tucnak.nagano.cz/wiki/index.php?title=Special:Recentchanges&feed=rss<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
*[[DE Main Page|Deutsch]] Maintained by Hannes DK1HJ, tnx!<br />
*[[RU Main Page|Русский]] Maintained by Sergey RA3WND и Vitaliy [[User:UR6LAD|UR6LAD]], tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
* [http://translate.google.cz/translate?hl=ru&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Русский]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
ArchLinux users can build the AUR package [http://aur.archlinux.org/packages.php?ID=29821 tucnak2]<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
**[[Supported Contests]] <br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
** [[After contest]]<br />
* [[Menu]]<br />
** [[Contest]]<br />
** [[File]]<br />
** [[Edit]]<br />
** [[Bands]]<br />
** [[Subwins]]<br />
** [[Setup]]<br />
** [[Help]]<br />
* [[Subwin types]]<br />
* [[Supported hardware]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
<br />
* Installing<br />
** [[Ubuntu "Jaunty" (9.04)]]<br />
** [[Ubuntu "Intrepid" (8.10)]]<br />
* Compiling<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]], OK2AIA, HG6Z, OM0AMI, [[User:UR6LAD|UR6LAD]], OK1KQH, OM3KEG.<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[NOW Obselete - Implemented since V 2.20: Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=930Main Page2009-05-30T20:05:07Z<p>G1ogy: /* Documentation */</p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
If you want to be informed about site changes, add this URL into your RSS reader: http://tucnak.nagano.cz/wiki/index.php?title=Special:Recentchanges&feed=rss<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
*[[DE Main Page|Deutsch]] Maintained by Hannes DK1HJ, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
**[[Supported Contests]] <br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
** [[Contest]]<br />
** [[File]]<br />
** [[Edit]]<br />
** [[Bands]]<br />
** [[Subwins]]<br />
** [[Setup]]<br />
** [[Help]]<br />
* [[Supported hardware]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* Installing<br />
** [[Ubuntu "Jaunty" (9.04)]]<br />
** [[Ubuntu "Intrepid" (8.10)]]<br />
* Compiling<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www/g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]], OK2AIA, HG6Z<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%22Jaunty%22_(9.04)&diff=929Ubuntu "Jaunty" (9.04)2009-05-30T20:04:25Z<p>G1ogy: Created page with '== Installing Tucnak on Ubuntu 9.04 - Jaunty == Tucknak 2.26 installs directly from the Wiki Download page on a fresh (updated) instance of Ubuntu "Jaunty Jackalope". Synaptic ...'</p>
<hr />
<div>== Installing Tucnak on Ubuntu 9.04 - Jaunty ==<br />
<br />
Tucknak 2.26 installs directly from the Wiki Download page on a fresh (updated) instance of Ubuntu "Jaunty Jackalope".<br />
<br />
Synaptic (Package Manager) prepends two dependencies: hamlib, libfdti; automatically.<br><br />
A'' no sweat'', point 'n click installation.<br><br />
--'OGY 20:04, 30 May 2009 (UTC)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Supported_Contests&diff=851Supported Contests2009-04-05T20:31:06Z<p>G1ogy: /* List of Tucnak Supported Contests */</p>
<hr />
<div>=List of Tucnak Supported Contests=<br />
(please add all contest already working)<br />
<br />
* IARU VHF / UHF Contest<br />
* VHF Marconi CW Contest<br />
* [[AGCW CW Contest]]<br />
* RSGB V/UHF Contests - Standard and Multipliers: M1-M4 [http://www.vhfcc.org RSGB VHF Contest Committee]<br />
<br />
<br />
== Wish List==<br />
(add Contest , YOU would like to run with Tucnak, don't forget to add at leats a link to the contest rules)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Hotkeys&diff=763Hotkeys2009-02-28T22:09:08Z<p>G1ogy: /* View/Download Hotkeys PDF File */</p>
<hr />
<div>{{Languages}}<br />
<br />
* F2: saves QSOs from all bands<br />
* F3: erases input line and report<br />
* F3: opens a new contest<br />
* F4: switches between windows<br />
* F5..F8: exec call 0 .. 3 (CW or SSB)<br />
* F9,F10: menu<br />
* F11..F12: exec call 4 .. 5<br />
* Alt+B: switches bands<br />
* Alt+C: swaps callsigns in unfinished QSO<br />
* Alt+D: confirms callsign from database<br />
* Alt+E: confirms optional exchange<br />
* Alt+F: sets preferred QRG for skeds<br />
* Alt+G: S&P's request for QSO/RUN's confirm<br />
* Alt+H: shows history of input line<br />
* Alt+K: displays previous "/CQ" item in [[KST chat]]<br />
* Ctrl+K: asks for callsign and writes /CQ command as above (only under SDL)<br />
* All+M: swaps CW/SSB modes<br />
* Alt+N: displays next item in history<br />
* Alt+O: changes operator<br />
* Alt+P: displays previous item in history<br />
* Alt+Q: exits from program<br />
* Alt+R: shows rotator control window (see [[Rotators]])<br />
* Alt+S: sends sked<br />
* Alt+T: tune for PA<br />
* Alt+U: adds QSO to unfinished QSO<br />
* Alt+V: swaps locator<br />
* Alt+X: confirms locator from database<br />
* Alt+Y: erases unfinished QSO only<br />
* Alt+1..0: directly switchs to window 1 .. 10<br />
* Ctrl+A: turns first rotator to current angle (see [[Rotators]])<br />
* Ctrl+B: turns second rotator to current angle<br />
* Ctrl+L: redraws screen<br />
* Ctrl+P: play last recorded WAV file<br />
* Ctrl+V: allows insert special characters to input line. F.e. Press Ctrl+V then C to send Ctrl+C to program in shell.<br />
* Ctrl+Y: erases input line<br />
* Ctrl+A..Z: changes band<br />
* Ctrl+0..9: directly switchs to window 10 .. 19<br />
* TAB: switches on PTT in SSB mode. Switch on transmitting from keyboard in CW mode.<br />
* Up Arrow: sets window active<br />
* ESC: finish CQ or switches to input line<br />
* Enter: if CW window is active it's closed<br />
* [: left horizontal scroll of log or window contents<br />
* ]: right horizontal scroll of log or window contents<br />
<br />
=Key in map window=<br />
<br />
Graphics polar map is shown only when Tucnak is run with SDL (X11, framebuffer).<br />
<br />
* r: redraw map<br />
* Cursor keys: moves the map<br />
* +,-: zoom map<br />
* F1: saves graphics window to contest directory in PNG picture format<br />
<br />
=Other useful operating system keystokes=<br />
<br />
* Alt+Fx - Changes active console to virtual console x (in console mode)<br />
* Ctrl+Alt+Fx - as above in X Window System<br />
* Alt+Left/Right Arrow - changes console from one to rigth/left<br />
<br />
=View/Download Hotkeys PDF File=<br />
<br />
*[http://www.m1cro.org.uk/tucnak/tucnak-special-keys.pdf Hotkeys PDF from M1CRO.org.uk] <br />
*[http://www.m1cro.org.uk/tucnak/tucnak.shtml M1CRO Tucnak page]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Hotkeys&diff=762Hotkeys2009-02-28T22:06:23Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
* F2: saves QSOs from all bands<br />
* F3: erases input line and report<br />
* F3: opens a new contest<br />
* F4: switches between windows<br />
* F5..F8: exec call 0 .. 3 (CW or SSB)<br />
* F9,F10: menu<br />
* F11..F12: exec call 4 .. 5<br />
* Alt+B: switches bands<br />
* Alt+C: swaps callsigns in unfinished QSO<br />
* Alt+D: confirms callsign from database<br />
* Alt+E: confirms optional exchange<br />
* Alt+F: sets preferred QRG for skeds<br />
* Alt+G: S&P's request for QSO/RUN's confirm<br />
* Alt+H: shows history of input line<br />
* Alt+K: displays previous "/CQ" item in [[KST chat]]<br />
* Ctrl+K: asks for callsign and writes /CQ command as above (only under SDL)<br />
* All+M: swaps CW/SSB modes<br />
* Alt+N: displays next item in history<br />
* Alt+O: changes operator<br />
* Alt+P: displays previous item in history<br />
* Alt+Q: exits from program<br />
* Alt+R: shows rotator control window (see [[Rotators]])<br />
* Alt+S: sends sked<br />
* Alt+T: tune for PA<br />
* Alt+U: adds QSO to unfinished QSO<br />
* Alt+V: swaps locator<br />
* Alt+X: confirms locator from database<br />
* Alt+Y: erases unfinished QSO only<br />
* Alt+1..0: directly switchs to window 1 .. 10<br />
* Ctrl+A: turns first rotator to current angle (see [[Rotators]])<br />
* Ctrl+B: turns second rotator to current angle<br />
* Ctrl+L: redraws screen<br />
* Ctrl+P: play last recorded WAV file<br />
* Ctrl+V: allows insert special characters to input line. F.e. Press Ctrl+V then C to send Ctrl+C to program in shell.<br />
* Ctrl+Y: erases input line<br />
* Ctrl+A..Z: changes band<br />
* Ctrl+0..9: directly switchs to window 10 .. 19<br />
* TAB: switches on PTT in SSB mode. Switch on transmitting from keyboard in CW mode.<br />
* Up Arrow: sets window active<br />
* ESC: finish CQ or switches to input line<br />
* Enter: if CW window is active it's closed<br />
* [: left horizontal scroll of log or window contents<br />
* ]: right horizontal scroll of log or window contents<br />
<br />
=Key in map window=<br />
<br />
Graphics polar map is shown only when Tucnak is run with SDL (X11, framebuffer).<br />
<br />
* r: redraw map<br />
* Cursor keys: moves the map<br />
* +,-: zoom map<br />
* F1: saves graphics window to contest directory in PNG picture format<br />
<br />
=Other useful operating system keystokes=<br />
<br />
* Alt+Fx - Changes active console to virtual console x (in console mode)<br />
* Ctrl+Alt+Fx - as above in X Window System<br />
* Alt+Left/Right Arrow - changes console from one to rigth/left<br />
<br />
=View/Download Hotkeys PDF File=<br />
<br />
*[http://www.m1cro.org.uk/tucnak/tucnak-special-keys.pdf Hotkeys PDF from M1CRO.org.uk]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Setup&diff=618Setup2008-12-12T00:05:28Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
[[Image:menusetup.png|none|frame|Setup menu]]<br />
<br />
All configuration changes are in memory only until you [[Setup#Save_configuration|save configuration]].<br />
<br />
=Contest defaults=<br />
<br />
[[Image:Contestdefaults.png|none|frame|Contest defaults]]<br />
<br />
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.<br />
<br />
=Band defaults=<br />
<br />
[[Image:Bandsettings.png|none|frame|Band defaults]]<br />
<br />
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).<br />
<br />
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.<br />
<br />
This setting is the only one which must be set. Other items are better set here too but it isn't necessary. <br />
<br />
QRV setting in this contest isn't effect on this place. Category can be one of Multi/Single/Check.<br />
<br />
TX and RX Equip settings contains description 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.<br />
<br />
Fill operator's callsigns into Operators field delimitely by semicolon. It is possible to fill it by Fill operators in menu [[Contest]].<br />
<br />
Remark field is assigned for remarks to contest commitee.<br />
<br />
Single/Multi categories are categories valid (probably) only in Czech republic. They are used mostly for EDI files naming.<br />
<br />
Band boundaries are entered in kilohertz. At this time they are used for DX-cluster spot filtration.<br />
<br />
Adif band name is band description used in ADIF format.<br />
<br />
QRG for skeds is initial frequency entered by operator to inform other operators about clean/CQ frequency on which they should take skeds. Format is not limited, you can use any string like ".120" etc.<br />
<br />
Transverter's LO QRG is frequency which tucnak adds to frequency read from transceiver's CAT and result shows on the screen:<br />
<math>f_\mathrm{display}=f_\mathrm{CAT} + f_\mathrm{lo} [Hz]</math><br />
Note some radios support transceiver mode for example radio is tuned on 14 MHz, CAT reports also 14 MHz but transceiver's display shows 144 MHz.<br />
LO frequency must be computed by operator, you can use Fix QRG in [[Edit]] menu.<br />
<br />
This is local frequency for one band. Normally enter 0 to use [[Setup#Rig options|Global LO frequency]].<br />
<br />
=Responsible operator=<br />
<br />
[[Image:Responsibleoperator.png|none|frame|Responsible operator]]<br />
<br />
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.<br />
<br />
=CW keying=<br />
<br />
[[Image:Cwdaemon.png|none|frame|CW daemon]]<br />
<br />
Since version 2.0 Tucnak does not use the external program 'cwdaemon' for keying and transmitting CW. Its functions are included in Tucnak. <br />
<br />
Keying methods are:<br />
* None - no CW output is used<br />
* lp - uses kernel module ppdev for keying. Recommended device is http://ok1zia.nagano.cz/web/davac3. Pin configuration is:<br />
** 1 STROBE - grounded when active.<br />
** 14 AUTOLF - switch TRX modulation input to microphone or soundcard output<br />
** 16 INIT - PTT<br />
** 17 SELECT IN - CW<br />
* ttys - uses control pins of serial port. Pinout for D-SUB9:<br />
** 4 DTR - CW<br />
** 5 GND - ground<br />
** 7 RTS - PTT<br />
* davac4 - USB SSB/CW keyer [[Davac4]] by OK1ZIA<br />
* cwdaemon - controls [http://www.qsl.net/pg4i/linux/cwdaemon.html cwdaemon] by Joop PG4I<br />
* winkey - uses [[Winkey]] by [http://www.k1el.com K1EL]]<br />
<br />
Keying device f.e. /dev/parport0, /dev/ttyS0, /dev/ttyUSB0<br />
<br />
Hostname, UDP port are reserved.<br />
<br />
Initial speed says keying speed in WPM after program start. You can change it using PageUp or PageDown keys.<br />
<br />
Weighting - changes ratio of mark and space in CW. <br />
<br />
<math>t_\mathrm{mark}=\frac{1\,200\,000}{\mathrm{speed}}+500\cdot \mathrm{weight}\ [\mu s]</math><br />
<br />
<math>t_\mathrm{space}=\frac{1\,200\,000}{\mathrm{speed}}-500\cdot \mathrm{weight}\ [\mu s]</math><br />
<br />
WPM range describes the speed that can be set with PageUp/PageDown keys. Minimal WPM is also used for Winkey - it can handle only 31 speed steps. Normally minimal speed is set to 10 WPM which means winkey range 10-41 WPM. If you need for example 50 WPM, set minimal WPM to at least 19.<br />
<br />
Use speaker - beeps using program soundwrapper.<br />
<br />
PTT lead in - (experimental feature) Tucnak turns on PTT some time before CW to key on TRX and PA's to prevent "eating" of begin of code. It also allows the TX chain to stabilise before sending. Suggest 100 -> 250 ms.<br />
<br />
=Winkey options=<br />
<br />
[[Image:Winkeyoptions.png|none|frame|Winkey options]]<br />
<br />
Fast initialisation means that Tucnak doesn't wait for Winkey initialisation. It can be used mostly for winkey2 which is commonly supplied from USB. It has no effect for other version-depending commands (buttons), tucnak reads winkey version.<br />
<br />
Use speed pot/use buttons - doesn't need comment. Normally is no reason to turn they off.<br />
<br />
Curtis A/B, Ultimate, hand bug - set's paddle mode. I think optimal is Curtis B.<br />
<br />
Paddle swap - also without comment :-)<br />
<br />
=Audio=<br />
<br />
[[Image:Audio.png|none|frame|Audio options]]<br />
<br />
Since 2.0 Tucnak takes also SSB functionality for CQs and traffic recording. <br />
<br />
==Common options==<br />
Alsa, OSS, SSBD are supported "audio drivers".<br />
<br />
'''Record traffic''' switches on/off recording band activity on receiving. If this option isn't active then all next options are irrelevant. To prevent consuming of all free space, use options '''Max. record duration''' and '''Minimal disk free space'''.<br />
<br />
'''Record format''' option describe coding of output file. Supported options are.<br />
<br />
* PCM 8 and 16 bits<br />
* Logarithmic PCM u-law and A-law<br />
* IMA and MS adaptation PCM<br />
* GSM version 6.10 (preferred for me)<br />
<br />
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 sndfile-play distributed with libsndfile.<br />
<br />
Option '''Channels''' 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.<br />
<br />
'''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. <br />
<br />
'''Template for recorded filename''' is template for naming recording files. Description of possible macros you can find in section [[Setup#CQ_macros|CQ macros]].<br />
<br />
==Alsa options==<br />
'''Alsa playback revice''' and '''Alsa capture device''' hold Alsa devices, plugs etc. Valid values are for example:<br />
* default - default device in your configuration<br />
* hw0,0 - first card, first PCM (first DAC)<br />
* hw0,1 - first card, second PCM (second DAC, f.e. Ensonic ES1371)<br />
* hw1,0 - second card ...<br />
* plughw0,0 - see Alsa documentation<br />
* dmix<br />
<br />
'''Period time''' is maximal amount of time for holding samples in card buffer for capture. Rasonable values are in hundreds (tenth of second).<br />
<br />
'''Buffer time''' is maximal total size of buffer. Must be greater than Period time, f.e. 4*Buffer timer.<br />
<br />
'''Alsa mixer device''' f.e. hw0, hw1, ...<br />
<br />
'''Capture source''' button shows submnenu for capture. In menu are all detected sources on specified soundcard.<br />
<br />
==OSS options==<br />
'''OSS DSP''' describes path to special file which is connected with sound card kernel driver. Typically is /dev/dsp.<br />
<br />
'''Max. num of fragments''' tells number of buffer fragment which can be holded in buffer. If you have problems with recording or witdh transition RX -> TX, try to set to 4 or similar small number. Then check recorded files for buffer underruns.<br />
<br />
'''OSS mixer''' path to OSS mixer. typically /dev/mixer.<br />
<br />
'''Record source''' - input for recording signal.<br />
<br />
==SSBD options==<br />
'''Currently unimplemented!''' SSBD is now obsolete. Settings is here for eventual future control of other software/devices (PowerSDR, digimodes...)<br />
<br />
'''SSBD hostname''' and '''UDP port''' - set IP address and UDP port of ssb daemon.<br />
<br />
=CW CQ=<br />
<br />
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.<br />
<br />
[[Image:Cwcq.png|none|frame|CW CQ]]<br />
<br />
There are these items in dialoque for setting CQ: <br />
<br />
'''text''' of CQ. You can use plain text and macros<br />
<br />
'''speed''' is normally undefined but you can define speed only for this CQ (f.e. for fast 73)<br />
<br />
'''repeat''' CQ will be repeated until you press ESC, TAB or other CQ key<br />
<br />
'''delay''' determines time between CQ messages <br />
<br />
'''allow if...''' allows to run message if there is any macro undefined. Typically you don't want to give empty string if you have no callsign entered.<br />
<br />
=SSB CQ=<br />
<br />
[[Image:ssbcq.png|none|frame|SSB CQ]]<br />
<br />
'''filename''' - file which is played as CQ. You can use macros f.e. /home/user/tucnak/cq/$MC_$O.wav to have multiple files for more callsign and more operators. Some audio output devices can have limitations to the audio format - samplerate, channels.<br />
<br />
'''repeat''' and '''delay''' has same effect as in previous chapter<br />
<br />
=CQ macros=<br />
<br />
It's possible to define macros in texts of CW CQ and in name of SSB CQ file. Macros are case insensitive.<br />
<br />
* $$ - character $<br />
* $C - callsign of opposite station. Warning! Callsign may contains stroke then can be problem to use macros in filename of CQ SSB. Look at $V<br />
* $D - date of contest (20031228)<br />
* $N - contest number from opposite station<br />
* $O - operator's callsign (for SSB CQ filenames)<br />
* $R - report from opposite station.<br />
* $S - serial number of record sample<br />
* $T - contest directory (/home/ok1zia/tucnak/20031004.2)<br />
* $V - callsign of opposite station, the stroke character is exchanged by the underline character<br />
* $W - locator of opposite station<br />
* $X - optional exchange from opposite station<br />
* $MC - my callsign<br />
* $MN - contest number to opposite station.<br />
* $MR - report to opposite station<br />
* $MW - my locator<br />
* $MX - my optional exchange<br />
<br />
You can also use case sensitive macros from strftime(3) for example:<br />
<br />
* %d - day of month 01..31<br />
* %H - hours 01..24<br />
* %M - minutes 00..59<br />
* %m - month 00..12<br />
* %S - seconds 00-59<br />
* %Y - year 1970-2038<br />
<br />
For others use command:<br />
<br />
man 3 strftime<br />
<br />
Macros has not effect in all context.<br />
<br />
=Rig options=<br />
<br />
Tucnak uses [http://hamlib.sourceforge.net hamlib] for accessing rig (transceiver) via CAT interface. You can use probably any interface which is working with other programs. Good helper is [http://tucnak.nagano.cz/Interfaces.pdf HB9DRV's guide to HRD]. Or you can build one of [[RIG interface|my RIG interfaces]].<br />
<br />
[[Image:Rigoptions.png|none|frame|Rig options]]<br />
<br />
'''Device''' device where the interface is connected. Typically /dev/ttyS0, /dev/ttyUSB0<br />
<br />
'''Model''' model of rig. It is number defined by hamlib. You can obtain it by running command '''rigctl -l''' or you can use:<br />
<br />
'''Choose''' Press button to show menu. In the first level you will choose manufacturer, in second level rig model. Model number is written to the previous field.<br />
<br />
'''CIV address''' address of rig if you have more Icom radios connected via one interface. Enter 0 for default address.<br />
<br />
'''Freq. shift SSB->CW''' some old radios (Icom, Kenwood) shifts frequency when changing mode SSB <--> CW. If you call CQ on SSB and someone calls you in CW, you must switch to CW and tune for about 800Hz up. Tucnak can compensate this shift when you use Alt+M to switch mode.<br />
<br />
'''Transverter's LO QRG''' is frequency which tucnak adds to frequency read from transceiver's CAT and result shows on the screen:<br />
<math>f_\mathrm{display}=f_\mathrm{CAT} + f_\mathrm{lo} [Hz]</math><br />
Note some radios support transceiver mode for example radio is tuned on 14 MHz, CAT reports also 14 MHz but transceiver's display shows 144 MHz.<br />
LO frequency must be computed by operator, you can use Fix QRG in [[Edit]] menu. This is global LO freq, if you use more transceivers, you can set more frequencies in [[Setup#Band defaults|Band defaults menu]].<br />
<br />
=Autosave=<br />
<br />
[[Image:Autosave.png|none|frame|Autosave options]]<br />
<br />
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.<br />
<br />
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.<br />
<br />
Other items are ignored.<br />
<br />
=Network & trace=<br />
<br />
[[Image:Networktrace.png|none|frame|Network & trace options]]<br />
<br />
Ignore interfaces - list of network interfaces which would be ignored when searching for more instances of Tucnak on the network (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.<br />
<br />
Ignore networks - the purpose this option is the same as Ignore interface option. You can determinate subnet address.<br />
<br />
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.<br />
<br />
=Miscellaneous options=<br />
<br />
[[Image:Miscoptions.png|none|frame|Miscellaneous options]]<br />
<br />
'''Log lines''' are last lines of tucnak's screen on which tucnak writes informations for users.<br />
<br />
'''Sked shift''' time added to current time filled in the Sked dialog.<br />
<br />
'''Starting band''' Band character (f.e. C=144 MHz) of band, which will be activated after contest open.<br />
<br />
'''Screen resolution''' Only for SDL mode - you can set resolution of tucnak's window in characters or in pixels<br />
<br />
'''Double font''' for very-high-resolution displays and bad eyes - fonts are resized from usual 9x16 to 18x32 pixels. It is not very usable but on IARU VHF 2008 I had nothing to do so I've imlpemented it.<br />
<br />
'''Slash key''' Slash key on some national keyboards is not easily accessible (only with shift). Here you can remap it to any other character. Use with care!<br />
<br />
'''Disable screensaver''' if you only test Tucnak at home, you probably don't want to disable screensaver. So turn these checkbox off.<br />
<br />
=Terminal options=<br />
<br />
[[Image:Terminal.png|none|frame|Terminal options]]<br />
<br />
These options come from [http://links.sourceforge.net links browser] so I'm not able to tell what they exactly mean. Try to make some experiments or look at source code :-)<br />
<br />
=Language=<br />
<br />
Set language of Tucnak's GUI. I think English is very good for contest log but some people like to have their mother tongue set.<br />
<br />
=Character set=<br />
<br />
This menu is used for setting characteristic of terminal as window frames. It's a legacy of links (as above), I don't have detailed knowledge about these options.<br />
<br />
=Load cfg from net=<br />
<br />
It shows addresses of all Tucnaks on the local network. If one is selected you will read his complete configuration (tucnakrc).<br />
<br />
=Load C_W from net=<br />
<br />
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.<br />
<br />
=Save configuration=<br />
<br />
It saves current configuration to file ~/tucnak/tucnakrc . You '''MUST''' do it to preserve any configuration changes !!</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Setup&diff=617Setup2008-12-11T23:10:18Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
[[Image:menusetup.png|none|frame|Setup menu]]<br />
<br />
All configuration changes are in memory only until you [[Setup#Save_configuration|save configuration]].<br />
<br />
=Contest defaults=<br />
<br />
[[Image:Contestdefaults.png|none|frame|Contest defaults]]<br />
<br />
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.<br />
<br />
=Band defaults=<br />
<br />
[[Image:Bandsettings.png|none|frame|Band defaults]]<br />
<br />
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).<br />
<br />
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.<br />
<br />
This setting is the only one which must be set. Other items are better set here too but it isn't necessary. <br />
<br />
QRV setting in this contest isn't effect on this place. Category can be one of Multi/Single/Check.<br />
<br />
TX and RX Equip settings contains description 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.<br />
<br />
Fill operator's callsigns into Operators field delimitely by semicolon. It is possible to fill it by Fill operators in menu [[Contest]].<br />
<br />
Remark field is assigned for remarks to contest commitee.<br />
<br />
Single/Multi categories are categories valid (probably) only in Czech republic. They are used mostly for EDI files naming.<br />
<br />
Band boundaries are entered in kilohertz. At this time they are used for DX-cluster spot filtration.<br />
<br />
Adif band name is band description used in ADIF format.<br />
<br />
QRG for skeds is initial frequency entered by operator to inform other operators about clean/CQ frequency on which they should take skeds. Format is not limited, you can use any string like ".120" etc.<br />
<br />
Transverter's LO QRG is frequency which tucnak adds to frequency read from transceiver's CAT and result shows on the screen:<br />
<math>f_\mathrm{display}=f_\mathrm{CAT} + f_\mathrm{lo} [Hz]</math><br />
Note some radios support transceiver mode for example radio is tuned on 14 MHz, CAT reports also 14 MHz but transceiver's display shows 144 MHz.<br />
LO frequency must be computed by operator, you can use Fix QRG in [[Edit]] menu.<br />
<br />
This is local frequency for one band. Normally enter 0 to use [[Setup#Rig options|Global LO frequency]].<br />
<br />
=Responsible operator=<br />
<br />
[[Image:Responsibleoperator.png|none|frame|Responsible operator]]<br />
<br />
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.<br />
<br />
=CW keying=<br />
<br />
[[Image:Cwdaemon.png|none|frame|CW daemon]]<br />
<br />
Since version 2.0 Tucnak does not use the external program 'cwdaemon' for keying and transmitting CW. Its functions are included in Tucnak. <br />
<br />
Keying methods are:<br />
* None - no CW output is used<br />
* lp - uses kernel module ppdev for keying. Recommended device is http://ok1zia.nagano.cz/web/davac3. Pin configuration is:<br />
** 1 STROBE - grounded when active.<br />
** 14 AUTOLF - switch TRX modulation input to microphone or soundcard output<br />
** 16 INIT - PTT<br />
** 17 SELECT IN - CW<br />
* ttys - uses control pins of serial port. Pinout for D-SUB9:<br />
** 4 DTR - CW<br />
** 5 GND - ground<br />
** 7 RTS - PTT<br />
* davac4 - USB SSB/CW keyer [[Davac4]] by OK1ZIA<br />
* cwdaemon - controls [http://www.qsl.net/pg4i/linux/cwdaemon.html cwdaemon] by Joop PG4I<br />
* winkey - uses [[Winkey]] by [http://www.k1el.com K1EL]]<br />
<br />
Keying device f.e. /dev/parport0, /dev/ttyS0, /dev/ttyUSB0<br />
<br />
Hostname, UDP port are reserved.<br />
<br />
Initial speed says keying speed in WPM after program start. You can change it using PageUp or PageDown keys.<br />
<br />
Weighting - changes ratio of mark and space in CW. <br />
<br />
<math>t_\mathrm{mark}=\frac{1\,200\,000}{\mathrm{speed}}+500\cdot \mathrm{weight}\ [\mu s]</math><br />
<br />
<math>t_\mathrm{space}=\frac{1\,200\,000}{\mathrm{speed}}-500\cdot \mathrm{weight}\ [\mu s]</math><br />
<br />
WPM range describes the speed that can be set with PageUp/PageDown keys. Minimal WPM is also used for Winkey - it can handle only 31 speed steps. Normally minimal speed is set to 10 WPM which means winkey range 10-41 WPM. If you need for example 50 WPM, set minimal WPM to at least 19.<br />
<br />
Use speaker - beeps using program soundwrapper.<br />
<br />
PTT lead in - (experimental feature) Tucnak turns on PTT some time before CW to key on TRX and PA's to prevent "eating" of begin of code. It also allows the TX chain to stabilise before sending. Suggest 100 -> 250 ms.<br />
<br />
=Winkey options=<br />
<br />
[[Image:Winkeyoptions.png|none|frame|Winkey options]]<br />
<br />
Fast initialisation means that Tucnak doesn't wait for Winkey initialisation. It can be used mostly for winkey2 which is commonly supplied from USB. It has no effect for other version-depending commands (buttons), tucnak reads winkey version.<br />
<br />
Use speed pot/use buttons - doesn't need comment. Normally is no reason to turn they off.<br />
<br />
Curtis A/B, Ultimate, hand bug - set's paddle mode. I think optimal is Curtis B.<br />
<br />
Paddle swap - also without comment :-)<br />
<br />
=Audio=<br />
<br />
[[Image:Audio.png|none|frame|Audio options]]<br />
<br />
Since 2.0 Tucnak takes also SSB functionality for CQs and traffic recording. <br />
<br />
==Common options==<br />
Alsa, OSS, SSBD are supported "audio drivers".<br />
<br />
'''Record traffic''' switches on/off recording band activity on receiving. If this option isn't active then all next options are irrelevant. To prevent consuming of all free space, use options '''Max. record duration''' and '''Minimal disk free space'''.<br />
<br />
'''Record format''' option describe coding of output file. Supported options are.<br />
<br />
* PCM 8 and 16 bits<br />
* Logarithmic PCM u-law and A-law<br />
* IMA and MS adaptation PCM<br />
* GSM version 6.10 (preferred for me)<br />
<br />
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 sndfile-play distributed with libsndfile.<br />
<br />
Option '''Channels''' 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.<br />
<br />
'''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. <br />
<br />
'''Template for recorded filename''' is template for naming recording files. Description of possible macros you can find in section [[Setup#CQ_macros|CQ macros]].<br />
<br />
==Alsa options==<br />
'''Alsa playback revice''' and '''Alsa capture device''' hold Alsa devices, plugs etc. Valid values are for example:<br />
* default - default device in your configuration<br />
* hw0,0 - first card, first PCM (first DAC)<br />
* hw0,1 - first card, second PCM (second DAC, f.e. Ensonic ES1371)<br />
* hw1,0 - second card ...<br />
* plughw0,0 - see Alsa documentation<br />
* dmix<br />
<br />
'''Period time''' is maximal amount of time for holding samples in card buffer for capture. Rasonable values are in hundreds (tenth of second).<br />
<br />
'''Buffer time''' is maximal total size of buffer. Must be greater than Period time, f.e. 4*Buffer timer.<br />
<br />
'''Alsa mixer device''' f.e. hw0, hw1, ...<br />
<br />
'''Capture source''' button shows submnenu for capture. In menu are all detected sources on specified soundcard.<br />
<br />
==OSS options==<br />
'''OSS DSP''' describes path to special file which is connected with sound card kernel driver. Typically is /dev/dsp.<br />
<br />
'''Max. num of fragments''' tells number of buffer fragment which can be holded in buffer. If you have problems with recording or witdh transition RX -> TX, try to set to 4 or similar small number. Then check recorded files for buffer underruns.<br />
<br />
'''OSS mixer''' path to OSS mixer. typically /dev/mixer.<br />
<br />
'''Record source''' - input for recording signal.<br />
<br />
==SSBD options==<br />
'''Currently unimplemented!''' SSBD is now obsolete. Settings is here for eventual future control of other software/devices (PowerSDR, digimodes...)<br />
<br />
'''SSBD hostname''' and '''UDP port''' - set IP address and UDP port of ssb daemon.<br />
<br />
=CW CQ=<br />
<br />
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.<br />
<br />
[[Image:Cwcq.png|none|frame|CW CQ]]<br />
<br />
There are these items in dialoque for setting CQ: <br />
<br />
'''text''' of CQ. You can use plain text and macros<br />
<br />
'''speed''' is normally undefined but you can define speed only for this CQ (f.e. for fast 73)<br />
<br />
'''repeat''' CQ will be repeated until you press ESC, TAB or other CQ key<br />
<br />
'''delay''' determines time between CQ messages <br />
<br />
'''allow if...''' allows to run message if there is any macro undefined. Typically you don't want to give empty string if you have no callsign entered.<br />
<br />
=SSB CQ=<br />
<br />
[[Image:ssbcq.png|none|frame|SSB CQ]]<br />
<br />
'''filename''' - file which is played as CQ. You can use macros f.e. /home/user/tucnak/cq/$MC_$O.wav to have multiple files for more callsign and more operators. Some audio output devices can have limitations to the audio format - samplerate, channels.<br />
<br />
'''repeat''' and '''delay''' has same effect as in previous chapter<br />
<br />
=CQ macros=<br />
<br />
It's possible to define macros in texts of CW CQ and in name of SSB CQ file. Macros are case insensitive.<br />
<br />
* $$ - character $<br />
* $C - callsign of opposite station. Warning! Callsign may contains stroke then can be problem to use macros in filename of CQ SSB. Look at $V<br />
* $D - date of contest (20031228)<br />
* $N - contest number from opposite station<br />
* $O - operator's callsign (for SSB CQ filenames)<br />
* $R - report from opposite station.<br />
* $S - serial number of record sample<br />
* $T - contest directory (/home/ok1zia/tucnak/20031004.2)<br />
* $V - callsign of opposite station, the stroke character is exchanged by the underline character<br />
* $W - locator of opposite station<br />
* $X - optional exchange from opposite station<br />
* $MC - my callsign<br />
* $MN - contest number from opposite station.<br />
* $MR - report for opposite station<br />
* $MW - my locator<br />
* $MX - my optional exchange<br />
<br />
You can also use case sensitive macros from strftime(3) for example:<br />
<br />
* %d - day of month 01..31<br />
* %H - hours 01..24<br />
* %M - minutes 00..59<br />
* %m - month 00..12<br />
* %S - seconds 00-59<br />
* %Y - year 1970-2038<br />
<br />
For others use command:<br />
<br />
man 3 strftime<br />
<br />
Macros has not effect in all context.<br />
<br />
=Rig options=<br />
<br />
Tucnak uses [http://hamlib.sourceforge.net hamlib] for accessing rig (transceiver) via CAT interface. You can use probably any interface which is working with other programs. Good helper is [http://tucnak.nagano.cz/Interfaces.pdf HB9DRV's guide to HRD]. Or you can build one of [[RIG interface|my RIG interfaces]].<br />
<br />
[[Image:Rigoptions.png|none|frame|Rig options]]<br />
<br />
'''Device''' device where the interface is connected. Typically /dev/ttyS0, /dev/ttyUSB0<br />
<br />
'''Model''' model of rig. It is number defined by hamlib. You can obtain it by running command '''rigctl -l''' or you can use:<br />
<br />
'''Choose''' Press button to show menu. In the first level you will choose manufacturer, in second level rig model. Model number is written to the previous field.<br />
<br />
'''CIV address''' address of rig if you have more Icom radios connected via one interface. Enter 0 for default address.<br />
<br />
'''Freq. shift SSB->CW''' some old radios (Icom, Kenwood) shifts frequency when changing mode SSB <--> CW. If you call CQ on SSB and someone calls you in CW, you must switch to CW and tune for about 800Hz up. Tucnak can compensate this shift when you use Alt+M to switch mode.<br />
<br />
'''Transverter's LO QRG''' is frequency which tucnak adds to frequency read from transceiver's CAT and result shows on the screen:<br />
<math>f_\mathrm{display}=f_\mathrm{CAT} + f_\mathrm{lo} [Hz]</math><br />
Note some radios support transceiver mode for example radio is tuned on 14 MHz, CAT reports also 14 MHz but transceiver's display shows 144 MHz.<br />
LO frequency must be computed by operator, you can use Fix QRG in [[Edit]] menu. This is global LO freq, if you use more transceivers, you can set more frequencies in [[Setup#Band defaults|Band defaults menu]].<br />
<br />
=Autosave=<br />
<br />
[[Image:Autosave.png|none|frame|Autosave options]]<br />
<br />
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.<br />
<br />
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.<br />
<br />
Other items are ignored.<br />
<br />
=Network & trace=<br />
<br />
[[Image:Networktrace.png|none|frame|Network & trace options]]<br />
<br />
Ignore interfaces - list of network interfaces which would be ignored when searching for more instances of Tucnak on the network (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.<br />
<br />
Ignore networks - the purpose this option is the same as Ignore interface option. You can determinate subnet address.<br />
<br />
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.<br />
<br />
=Miscellaneous options=<br />
<br />
[[Image:Miscoptions.png|none|frame|Miscellaneous options]]<br />
<br />
'''Log lines''' are last lines of tucnak's screen on which tucnak writes informations for users.<br />
<br />
'''Sked shift''' time added to current time filled in the Sked dialog.<br />
<br />
'''Starting band''' Band character (f.e. C=144 MHz) of band, which will be activated after contest open.<br />
<br />
'''Screen resolution''' Only for SDL mode - you can set resolution of tucnak's window in characters or in pixels<br />
<br />
'''Double font''' for very-high-resolution displays and bad eyes - fonts are resized from usual 9x16 to 18x32 pixels. It is not very usable but on IARU VHF 2008 I had nothing to do so I've imlpemented it.<br />
<br />
'''Slash key''' Slash key on some national keyboards is not easily accessible (only with shift). Here you can remap it to any other character. Use with care!<br />
<br />
'''Disable screensaver''' if you only test Tucnak at home, you probably don't want to disable screensaver. So turn these checkbox off.<br />
<br />
=Terminal options=<br />
<br />
[[Image:Terminal.png|none|frame|Terminal options]]<br />
<br />
These options come from [http://links.sourceforge.net links browser] so I'm not able to tell what they exactly mean. Try to make some experiments or look at source code :-)<br />
<br />
=Language=<br />
<br />
Set language of Tucnak's GUI. I think English is very good for contest log but some people like to have their mother tongue set.<br />
<br />
=Character set=<br />
<br />
This menu is used for setting characteristic of terminal as window frames. It's a legacy of links (as above), I don't have detailed knowledge about these options.<br />
<br />
=Load cfg from net=<br />
<br />
It shows addresses of all Tucnaks on the local network. If one is selected you will read his complete configuration (tucnakrc).<br />
<br />
=Load C_W from net=<br />
<br />
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.<br />
<br />
=Save configuration=<br />
<br />
It saves current configuration to file ~/tucnak/tucnakrc . You '''MUST''' do it to preserve any configuration changes !!</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Duplicate_callsign&diff=615Duplicate callsign2008-12-10T22:52:04Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
If you write callsign which is saved before then Duplicate QSO dialogue is displayed. You have several choices, see below.<br />
<br />
* Clear this QSO - clear this QSO (as F3 key), old QSO isn't changed<br />
* Edit old QSO - edit changes in old QSO<br />
* Mark old QSO as ERROR - Mark old QSO as ERROR, a new QSO is relevant now<br />
* Store as DUPE - Old QSO is kept, new QSO has zero points and is logged as DUPE.</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%22Intrepid%22_(8.10)&diff=571Ubuntu "Intrepid" (8.10)2008-11-21T00:39:39Z<p>G1ogy: /* Installing Tucnak on Ubuntu 8.10 - Intrepid */</p>
<hr />
<div>== Installing Tucnak on Ubuntu 8.10 - Intrepid ==<br />
<br />
<br />
The new release of Ubuntu linux is v8.10 "Intrepid Ibis".<br><br />
A fresh install of Intrepid does not include a library required by Tucnak and so the logger will not install; neither v2.15 from the standard Ubuntu "Amateur Radio (Universe)" repository nor by downloading a version of Tucnak from the download page here on the Wiki.<br><br />
<p><br />
The workaround (for me) was to download and install the latest version of `libgpmg1' from the Ubuntu "Hardy" package repository http://packages.ubuntu.com/hardy/libgpmg1 [ libgpmg1 (1.19.6-25ubuntu1) ]. <br><br />
<br />
Tucnak now has its dependences satisfied and will install itself (along with libhamlib2) and operate successfully.<br><br />
--'OGY 15:47, 1 November 2008 (CET)<br />
<br />
<br><br><br><br />
<br />
A small addition for a more complete approach:<br><br />
<br />
1) install libgpmg1 as above<br><br />
2) add the repository "Universe" to Software Sources (one ''tickbox'' on the front tab)<br><br />
3) install Tucnak 2.15 (or whatever is the current version in ''Universe'' - this installs other, needed libraries)<br><br />
4) download and install Tucknak v2.XX from the Wiki 'Download' page.<br><br />
--'OGY 01:39, 21 November 2008 (CET)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%22Intrepid%22_(8.10)&diff=541Ubuntu "Intrepid" (8.10)2008-11-01T14:54:38Z<p>G1ogy: </p>
<hr />
<div>== Installing Tucnak on Ubuntu 8.10 - Intrepid ==<br />
<br />
<br />
The new release of Ubuntu linux is v8.10 "Intrepid Ibis".<br><br />
A fresh install of Intrepid does not include a library required by Tucnak and so the logger will not install; neither v2.15 from the standard Ubuntu "Amateur Radio (Universe)" repository nor by downloading a version of Tucnak from the download page here on the Wiki.<br><br />
<p><br />
The workaround (for me) was to download and install the latest version of `libgpmg1' from the Ubuntu "Hardy" package repository http://packages.ubuntu.com/hardy/libgpmg1 [ libgpmg1 (1.19.6-25ubuntu1) ]. <br><br />
<br />
Tucnak now has its dependences satisfied and will install itself (along with libhamlib2) and operate successfully.<br><br />
--'OGY 15:47, 1 November 2008 (CET)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=540Main Page2008-11-01T14:53:42Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* Installing<br />
** [[Ubuntu "Intrepid" (8.10)]]<br />
* Compiling<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www/g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=539Main Page2008-11-01T14:52:44Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* Installing<br />
** [[Ubuntu 'Intrepid' (8.10)]]<br />
* Compiling<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www/g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=538Main Page2008-11-01T14:51:57Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* Installing<br />
** [[Ubuntu "Intrepid" (8.10)]]<br />
* Compiling<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www/g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%22Intrepid%22_(8.10)&diff=537Ubuntu "Intrepid" (8.10)2008-11-01T14:47:52Z<p>G1ogy: Ubuntu 8.10 / Tucnak : dependencies satisfied</p>
<hr />
<div>== Installing Tucnak on Ubuntu 8.10 - Intrepid ==<br />
<br />
<br />
The new release of Ubuntu linux is v8.10 "Intrepid Ibis".<br><br />
A fresh install of Intrepid does not include a library required by Tucnak and so the logger will not install; either v2.15 from the standard Ubuntu "Amateur Radio (Universe)" repository nor by downloading a version of Tucnak from the download page here on the Wiki.<br><br />
<p><br />
The workaround (for me) was to download and install the latest version of `libgpmg1' from the Ubuntu "Hardy" package repository http://packages.ubuntu.com/hardy/libgpmg1 [ libgpmg1 (1.19.6-25ubuntu1) ]. <br><br />
<br />
Tucnak now has its dependences satisfied and will install itself (along with libhamlib2) and operate successfully.<br><br />
--'OGY 15:47, 1 November 2008 (CET)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=536Main Page2008-11-01T14:33:21Z<p>G1ogy: Tucknak requires a library not available for Ubuntu v8.10 "Intrepid Ibis" : Install of libgpmg1 from "Hardy" is necessary.</p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* [[Installing]]<br />
** [[Ubuntu "Intrepid" (8.10)]]<br />
* [[Compiling]]<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www/g1ogy.com/ G1OGY],[http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E], [[User:Dl5ybz|DL5YBZ]]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Converting_TACLog_v_1,9xx_C_W_files_for_use_with_Tucnak&diff=513Converting TACLog v 1,9xx C W files for use with Tucnak2008-09-13T00:12:52Z<p>G1ogy: /* Step by Step */</p>
<hr />
<div>THIS PAGE IS UNDER CONSTRUCTION [20080912]<br />
<br />
== Synopsis ==<br />
<br />
Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of the uncertainty out of installing and operating a linux PC, the opportunity is ripe for TACLog die-hards to consider change.<br />
<br />
A modern Linux 'Workstation' desktop is not ~that~ far removed from the perhaps more familiar Windows® environment and has all of the necessary tools available by default, along with a 'package manager' to assist in installing readily available software for all manner of purposes.<br />
<br />
When you decide that you need a 21st century TACLog; Tucnak is, inevitably, the way-to-go. <br />
<br />
Tucnak maintains the freeform QSO entry style previously unique to TACLog; all of the operational F-key sequences; the Voice and CW keyers; along with many crucial enhancements particularly of relevance to multi-multi V/U/SHF contesting.<br />
<br />
These features are well-described elsewhere. With this article I wish to outline the relative simplicity of converting a version 1,9xx TACLog C_W file to work on a Tucnak installation.<br />
<br />
== Method ==<br />
<br />
The TACLog C_W (callsign) file is incompatible with Tucnak but can be converted so that all that history is not lost when migrating from MS-DOS® to Linux.<br />
<br />
Most (all?) TACLog users will know how to update the callsign file (C_W file) with information obtained from a new contest - [MM-4-5-1] `Add C_Ws from data'.<br><br />
Many will also know that the C_W file is held in a special format (Pascal Record type) which means that it is unsuitable for direct manipulation by simple tools such as a text editor. Some will know that the C_W file can be converted to a pure text format (readable in EDIT or MS Notepad) using the C_W-to-Text converter utility called `C_W.EXE' found in the main TACLOG directory, (commonly C:\TACLOG).<br><br />
<br />
This `HOW-TO' requires some DOS-jockey work and some Linux command line ops and expects some familiarity with the Linux GUI environment and file manager but is safe to use and will not obliterate your data! I will provide some screen shots and a step-by-step description of the process. Those readers familiar with C_W.EXE may skip down to Step 4 directly, as you are likely to already have your C_W data in TACLOG.TXT format.<br />
<br />
<br />
<br />
== Outline ==<br />
<br />
* Convert TACLOG.C_W to TACLOG.TXT using C_W.EXE (distributed with TACLog)<br />
* Copy TACLOG.TXT to the Tucnak linux machine.<br />
* Convert TACLOG.TXT (CALL LOC LOC2 DATE) to Tucnak format with tac2tuc.pl (distributed with Tucnak v2.13 & later)<br />
* Copy the output file to the Tucnak directory while renaming it to tucnakcw<br />
* Run Tucnak with your own callsign data<br />
<br />
<br />
<br />
== Prerequisites ==<br />
<br />
* I expect that you will have installed Tucnak using a 'package manager', the command-line installer tool appropriate to your distribution (yum, apt-get, emerge, etc) or by compiling the source-code available elsewhere on this site. I also expect you to have run it up and maybe played around some - if just for curiosity.<br />
* A working copy of TACLog or, at least, a valid TACLOG.C_W file (which can be found in the main <Drive>:\TACLOG directory on your DOS or Windows machine). <br><br />
* A recent version of C_W.EXE (distributed with TACLog and again found in the main directory). <br><br />
* access to `tac2tuc.pl' from an installed version of Tucnak 2.13 or later (/usr/[local/]share/tucnak2/tac2tuc.pl) or the source code of Tucnak v2.13 or later (.../tucnak2-2.13/share/tac2tuc.pl) or a download of tac2tuc.pl from [http://www.g1ogy.com/softitems.html g1ogy.com] <br><br />
* `perl' installed on your Tucnak (linux) machine (usually by default). <br><br />
<br />
----<br />
<br />
''OK? Got your toolbox? Let's get to work! '' <br><br />
<br />
----<br />
<br />
== Step by Step ==<br />
<br />
*Step 1.<br><br />
On your TACLog machine (DOS or Windows® - your choice) create a 'working directory' so that there will be no confusion about where and what we are doing. We'll call it <code>C:\TACWORK</code>. You will need maximum 5MB of working-space (that's small, but significant on an old DOS box).<br />
<br />
*Step 2.<br><br />
Find the TACLOG directory. From there, COPY (not move!) the two files: <code>TACLOG.C_W</code> and <code>C_W.EXE</code> into <code>C:\TACWORK</code>. <br><br />
<br />
*Step 3.<br><br />
If you are in Windows® start a Command Prompt window (win9x = start | Run | command <code>[Enter]</code> : in Win 2000/WinXP/Vista = Start | Run | cmd <code>[Enter]</code>) <br><br />
Now Change Directory [CD] to your <code>TACWORK</code> directory.<br />
<br />
Type: <br />
<code>C_W [Enter]</code><br><br />
<br />
Here is the HELP for <code>C_W.EXE</code>. It is pretty simple. You will see that <code>C_W.EXE</code> has an `automatic' mode that converts <code>TACLOG.C_W</code> into <code>TACLOG.TXT</code> using the '0' command parameter.<br><br />
Type:<br><br />
<code>C_W 0 TACLOG.C_W [Enter]</code><br><br />
<br />
A few seconds later you will have a file called <code>TACLOG.TXT</code> which will open in MS Notepad or EDIT.COM and look something like this, format-wise:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT JN75TR 20010825<br />
9A0DX JN82IW JN83JA 20020601<br />
9A0M JN86EL JN86FJ 20010305<br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
Notice (above) <b>that there are two locators on the same line for some of the calls</b>, followed by the ~most recent~ date that that call was changed in the file. This format is not the same as Tucnak uses and so it must be converted to look something like this:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT 20010825<br />
9A0C JN75TR<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA<br />
9A0M JN86EL 20010305<br />
9A0M JN86FJ <br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
This is where the program <code>tac2tuc.pl</code> comes in. <br />
<br />
You'll now notice that there is an extra row for each callsign that had two locators in the TACLog list. You'll also notice that the new lines for the second locator have no date. The perl program called <code>tac2tuc.pl</code> will fill in this date with 12 December 1901. Why? The line needs a date for Tucnak, there is no information available about the true date and Well, what happened on 12/12/1901? It is as good a 'default' date for a "radio" program as any I can think of ! And because it is so long ago, it also makes sure that the first locator retains its place-precedence when displayed on the Tucnak input line - just like TACLog. <br><br />
<pre><br />
9A0C JN75XT 20010825<br />
9A0C JN75TR 19011212<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA 19011212<br />
9A0M JN86EL 20010305<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
A note about Linux "users": You may know that linux has the notion of "users" with names and passwords who are allowed to log in and operate the machine - this is like Windows NT or XP or (gulp!) Vista. You may not know that more than one user can log in to a linux machine at the same time to do work and each user has their own working space on the disk for data and (by choice) programs. These working spaces are known as HOME directories.<br />
<br />
When you install a linux distribution it will (usually) ask you to enter a user name (and password) for the "usual" user of the machine. There will also be a user <code> root </code> created. This is the SuperUser or Administrator account and with modern 'workstation' linuxes is not usually directly used. You can also create more users after the installation is done and the box is up and running. I often create a user called <code>radio</code> and run all my live contest operations in that guise. This means that I can mess-around or experiment in my personal user account and working space and not damage or disturb the proper 'contest' logs.<br />
<br />
So, I suggest that TACLOG.TXT is copied to your personal home directory - not 'radio' - so that you can experiment in relative safety. <code>tac2tuc.pl</code> may be copied there as well. You might like to make a directory <code>tucwork</code> here to use for any conversions or other experiments with Tucnak data. Please do <b>not</b> put the conversion files into the <code>tucnak</code> directory if there is one there already or you are tempted to make one. <code>/home/<user-name>/tucnak</code> is where the Tucnak program ~itself~ will write files - we do not want to confuse ourselves or the program!<br />
<br />
<br />
*Step 4.<br><br />
<br />
On the linux machine, logged in as your normal user, create a directory <code>tucwork</code> [ you can use the GUI File Manager or the Command line: <code> mkdir tucwork </code> ].<br />
<br />
*Step 5.<br><br />
You must now find a way to get the file <code>C:\TACWORK\TACLOG.TXT</code> from the DOS/WINDOWS machine on to the Linux machine. Floppy disk; USB 'stick'; network copy; can each be used. I will leave the choice of method up to the operator!<br />
<br />
*Step 6.<br><br />
On linux, open a terminal window. Usually you will already be in your HOME directory, so Change Directory - `cd' - to your <code>tucwork</code> directory where you copied <code>TACLOG.TXT</code> (Step 5) and where you should copy <code>tac2tuc.pl</code>, however you have obtained it. See: Prerequisites<br />
<br />
type:<br><br />
<code> $ ls [Enter] </code><br />
<br />
Check the Letter CASE (upper/lower) of the file <code>TACLOG.TXT</code>. In some instances it will remain in DOS-like 'UPPER' case, on others it may be converted to 'lower' case or possibly 'Camel' case. Linux file names are <b>case sensitive</b> so it is important that you know how to type:<br />
<br />
<code> $ perl tac2tuc.pl TACLOG.TXT [Enter]</code><br />
<br />
Do it!.<br><br />
A few seconds later there will be a file called <code>tac2tuc.cw</code> waiting to be checked. You can open it in the Linux GUI Text Editor (gedit) or with a text-mode editor (vi or nano).<br />
<br />
*Step 7.<br><br />
I would do:<br><br />
<code> $ cp tac2tuc.cw tac2tuc.cw.YYYYMMDD </code> (where these letters represent Y-ear, M-onth and D-ay)<br />
This retains a safety copy in your <code>tucwork</code> directory.<br><br />
Then:<br><br />
<code> $ cp tac2tuc.cw ../tucnak/tucnakcw </code><br><br />
This makes a copy in the current user's local tucnak directory<br><br />
and if you already have a `radio' user on the PC<br><br />
<br />
<code> $ sudo cp tac2tuc.cw /home/radio/tucnak/tucnakcw </code><br />
<br />
The <code>sudo</code> program allows you to become `superuser' for just that one <code>copy</code> command and write the file into another user's `home' directory. It will ask for a password - this is your own (logged on user) password not that of the superuser nor the `radio' user.<br />
<br />
*Step 8.<br><br />
Now, start up Tucnak, create a test contest and enter a known callsign on the input line plus <code>[Enter]</code>. Observe the appearance of the relevant locator(s), in reverse video, just like TACLog!<br />
You will also see the partial-call lookup feature in operation (just enter prefix-number-first letter). Now try entering just a locator...<br />
(checkout the Tucnak Hot-Key listing [http://tucnak.nagano.cz/wiki/Hotkeys here] ).<br><br />
<br />
You are done! CU in the contest....<br></div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Converting_TACLog_v_1,9xx_C_W_files_for_use_with_Tucnak&diff=512Converting TACLog v 1,9xx C W files for use with Tucnak2008-09-12T23:57:33Z<p>G1ogy: New page: THIS PAGE IS UNDER CONSTRUCTION [20080912] == Synopsis == Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of ...</p>
<hr />
<div>THIS PAGE IS UNDER CONSTRUCTION [20080912]<br />
<br />
== Synopsis ==<br />
<br />
Following the (not so) recent developments in linux distributions such as Ubuntu (a Debian derivative) which have taken much of the uncertainty out of installing and operating a linux PC, the opportunity is ripe for TACLog die-hards to consider change.<br />
<br />
A modern Linux 'Workstation' desktop is not ~that~ far removed from the perhaps more familiar Windows® environment and has all of the necessary tools available by default, along with a 'package manager' to assist in installing readily available software for all manner of purposes.<br />
<br />
When you decide that you need a 21st century TACLog; Tucnak is, inevitably, the way-to-go. <br />
<br />
Tucnak maintains the freeform QSO entry style previously unique to TACLog; all of the operational F-key sequences; the Voice and CW keyers; along with many crucial enhancements particularly of relevance to multi-multi V/U/SHF contesting.<br />
<br />
These features are well-described elsewhere. With this article I wish to outline the relative simplicity of converting a version 1,9xx TACLog C_W file to work on a Tucnak installation.<br />
<br />
== Method ==<br />
<br />
The TACLog C_W (callsign) file is incompatible with Tucnak but can be converted so that all that history is not lost when migrating from MS-DOS® to Linux.<br />
<br />
Most (all?) TACLog users will know how to update the callsign file (C_W file) with information obtained from a new contest - [MM-4-5-1] `Add C_Ws from data'.<br><br />
Many will also know that the C_W file is held in a special format (Pascal Record type) which means that it is unsuitable for direct manipulation by simple tools such as a text editor. Some will know that the C_W file can be converted to a pure text format (readable in EDIT or MS Notepad) using the C_W-to-Text converter utility called `C_W.EXE' found in the main TACLOG directory, (commonly C:\TACLOG).<br><br />
<br />
This `HOW-TO' requires some DOS-jockey work and some Linux command line ops and expects some familiarity with the Linux GUI environment and file manager but is safe to use and will not obliterate your data! I will provide some screen shots and a step-by-step description of the process. Those readers familiar with C_W.EXE may skip down to Step 4 directly, as you are likely to already have your C_W data in TACLOG.TXT format.<br />
<br />
<br />
<br />
== Outline ==<br />
<br />
* Convert TACLOG.C_W to TACLOG.TXT using C_W.EXE (distributed with TACLog)<br />
* Copy TACLOG.TXT to the Tucnak linux machine.<br />
* Convert TACLOG.TXT (CALL LOC LOC2 DATE) to Tucnak format with tac2tuc.pl (distributed with Tucnak v2.13 & later)<br />
* Copy the output file to the Tucnak directory while renaming it to tucnakcw<br />
* Run Tucnak with your own callsign data<br />
<br />
<br />
<br />
== Prerequisites ==<br />
<br />
* I expect that you will have installed Tucnak using a 'package manager', the command-line installer tool appropriate to your distribution (yum, apt-get, emerge, etc) or by compiling the source-code available elsewhere on this site. I also expect you to have run it up and maybe played around some - if just for curiosity.<br />
* A working copy of TACLog or, at least, a valid TACLOG.C_W file (which can be found in the main <Drive>:\TACLOG directory on your DOS or Windows machine). <br><br />
* A recent version of C_W.EXE (distributed with TACLog and again found in the main directory). <br><br />
* access to `tac2tuc.pl' from an installed version of Tucnak 2.13 or later (/usr/[local/]share/tucnak2/tac2tuc.pl) or the source code of Tucnak v2.13 or later (.../tucnak2-2.13/share/tac2tuc.pl) or a download of tac2tuc.pl from [http://www.g1ogy.com/softitems.html g1ogy.com] <br><br />
* `perl' installed on your Tucnak (linux) machine (usually by default). <br><br />
<br />
----<br />
<br />
''OK? Got your toolbox? Let's get to work! '' <br><br />
<br />
----<br />
<br />
== Step by Step ==<br />
<br />
*Step 1.<br><br />
On your TACLog machine (DOS or Windows® - your choice) create a 'working directory' so that there will be no confusion about where and what we are doing. We'll call it <code>C:\TACWORK</code>. You will need maximum 5MB of working-space (that's small, but significant on an old DOS box).<br />
<br />
*Step 2.<br><br />
Find the TACLOG directory. From there, COPY (not move!) the two files: <code>TACLOG.C_W</code> and <code>C_W.EXE</code> into <code>C:\TACWORK</code>. <br><br />
<br />
*Step 3.<br><br />
If you are in Windows® start a Command Prompt window (win9x = start | Run | command <code>[Enter]</code> : in Win 2000/WinXP/Vista = Start | Run | cmd <code>[Enter]</code>) <br><br />
Now Change Directory [CD] to your <code>TACWORK</code> directory.<br />
<br />
Type: <br />
<code>C_W [Enter]</code><br><br />
<br />
Here is the HELP for <code>C_W.EXE</code>. It is pretty simple. You will see that <code>C_W.EXE</code> has an `automatic' mode that converts <code>TACLOG.C_W</code> into <code>TACLOG.TXT</code> using the '0' command parameter.<br><br />
Type:<br><br />
<code>C_W 0 TACLOG.C_W [Enter]</code><br><br />
<br />
A few seconds later you will have a file called <code>TACLOG.TXT</code> which will open in MS Notepad or EDIT.COM and look something like this, format-wise:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT JN75TR 20010825<br />
9A0DX JN82IW JN83JA 20020601<br />
9A0M JN86EL JN86FJ 20010305<br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
Notice (above) <b>that there are two locators on the same line for some of the calls</b>, followed by the ~most recent~ date that that call was changed in the file. This format is not the same as Tucnak uses and so it must be converted to look something like this:<br />
<pre><br />
8S6Z JO67AT 20000605<br />
9A/IK3UNA/P JN74FN 20010829<br />
9A0BVH JN85JO 20010211<br />
9A0C JN75XT 20010825<br />
9A0C JN75TR<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA<br />
9A0M JN86EL 20010305<br />
9A0M JN86FJ <br />
9A0V JN95MI 20000605<br />
9A0V/P JN85OV 19980905<br />
9A16D JN83BA 20000605<br />
</pre><br />
<br />
This is where the program <code>tac2tuc.pl</code> comes in. <br />
<br />
You'll now notice that there is an extra row for each callsign that had two locators in the TACLog list. You'll also notice that the new lines for the second locator have no date. The perl program called <code>tac2tuc.pl</code> will fill in this date with 12 December 1901. Why? The line needs a date for Tucnak, there is no information available about the true date and Well, what happened on 12/12/1901? It is as good a 'default' date for a "radio" program as any I can think of ! And because it is so long ago, it also makes sure that the first locator retains its place-precedence when displayed on the Tucnak input line - just like TACLog. <br><br />
<pre><br />
9A0C JN75XT 20010825<br />
9A0C JN75TR 19011212<br />
9A0DX JN82IW 20020601<br />
9A0DX JN83JA 19011212<br />
9A0M JN86EL 20010305<br />
</pre><br />
<br />
<br />
**TimeOut!.<br><br />
A note about Linux "users": You may know that linux has the notion of "users" with names and passwords who are allowed to log in and operate the machine - this is like Windows NT or XP or (gulp!) Vista. You may not know that more than one user can log in to a linux machine at the same time to do work and each user has their own working space on the disk for data and (by choice) programs. These working spaces are known as HOME directories.<br />
<br />
When you install a linux distribution it will (usually) ask you to enter a user name (and password) for the "usual" user of the machine. There will also be a user <code> root </code> created. This is the SuperUser or Administrator account and with modern 'workstation' linuxes is not usually directly used. You can also create more users after the installation is done and the box is up and running. I often create a user called <code>radio</code> and run all my live contest operations in that guise. This means that I can mess-around or experiment in my personal user account and working space and not damage or disturb the proper 'contest' logs.<br />
<br />
So, I suggest that TACLOG.TXT is copied to your personal home directory - not 'radio' - so that you can experiment in relative safety. <code>tac2tuc.pl</code> may be copied there as well. You might like to make a directory <code>tucwork</code> here to use for any conversions or other experiments with Tucnak data. Please do <b>not</b> put the conversion files into the <code>tucnak</code> directory if there is one there already or you are tempted to make one. <code>/home/<user-name>/tucnak</code> is where the Tucnak program ~itself~ will write files - we do not want to confuse ourselves or the program!<br />
<br />
<br />
*Step 4.<br><br />
<br />
On the linux machine, logged in as your normal user, create a directory <code>tucwork</code> [ you can use the GUI File Manager or the Command line: <code> mkdir tucwork </code> ].<br />
<br />
*Step 5.<br><br />
You must now find a way to get the file <code>C:\TACWORK\TACLOG.TXT</code> from the DOS/WINDOWS machine on to the Linux machine. Floppy disk; USB 'stick'; network copy; can each be used. I will leave the choice of method up to the operator!<br />
<br />
*Step 6..<br><br />
On linux, open a terminal window. Usually you will already be in your HOME directory, so Change Directory - `cd' - to your <code>tucwork</code> directory where you copied <code>TACLOG.TXT</code> (Step 5) and where you should copy <code>tac2tuc.pl</code>, however you have obtained it. See: Prerequisites<br />
<br />
type:.<br><br />
<code> $ ls [Enter] </code><br />
<br />
Check the Letter CASE (upper/lower) of the file <code>TACLOG.TXT</code>. In some instances it will remain in DOS-like 'UPPER' case, on others it may be converted to 'lower' case or possibly 'Camel' case. Linux file names are <b>case sensitive</b> so it is important that you know how to type:<br />
<br />
<code> $ perl tac2tuc.pl TACLOG.TXT [Enter]</code><br />
<br />
Do it!.<br><br />
A few seconds later there will be a file called <code>tac2tuc.cw</code> waiting to be checked. You can open it in the Linux GUI Text Editor (gedit) or with a text-mode editor (vi or nano).<br />
<br />
*Step 7.<br><br />
I would do:<br><br />
<code> $ cp tac2tuc.cw tac2tuc.cw.YYYYMMDD </code> (where these letters represent Y-ear, M-onth and D-ay)<br />
This retains a safety copy in your <code>tucwork</code> directory.<br><br />
Then:<br><br />
<code> $ sudo mv tac2tuc.cw /home/radio/tucnak/tucnakcw </code><br />
<br />
The <code>sudo</code> program allows you to become `superuser' for just that one <code>move</code> command and write the file into another user's `home' directory. It will ask for a password - this is your own (logged on user) password not that of the superuser nor the `radio' user.<br />
<br />
*Step 8.<br><br />
Now, start up Tucnak, create a test contest and enter a known callsign on the input line plus <code>[Enter]</code>. Observe the appearance of the relevant locator(s), in reverse video, just like TACLog!<br />
You will also see the partial-call lookup feature in operation (just enter prefix-number-first letter). Now try entering just a locator...<br />
(checkout the Tucnak Hot-Key listing [http://tucnak.nagano.cz/wiki/Hotkeys here] ).<br><br />
<br />
You are done! CU in the contest....<br></div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=511Main Page2008-09-12T22:50:01Z<p>G1ogy: /* Converting from TACLog */</p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* [[Compiling]]<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Converting TACLog v 1,9xx C_W files for use with Tucnak]]<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Notes_on_hand-editing_Tucnak_EDI_files_for_G-land_OE_Contests&diff=510Notes on hand-editing Tucnak EDI files for G-land OE Contests2008-09-12T21:27:41Z<p>G1ogy: </p>
<hr />
<div>== Background ==<br />
<br />
Every year, in the UK VHF&up Contest calendar, there are 6 contests (plus the whole 'Backpacker' series) that use the exchange of 'Postal District code' as an additional Multiplier - an "Optional Exchange" or "OE".<br><br />
In certain parts of the UK the postal districts cover a large area so, to promote activity to and from these areas, their District Code can be counted more than once: 3x for GM Districts and 6x for GI.<br />
<br />
Tucnak does not (yet) support multi-counting of OEs. Nor does it print a list of OEs worked during the contest in the 'Statistics' output file. <br />
<br />
To summarise:<br />
<br />
*1) 'G' OE Contests may use Postal District (forced to 2 char) for OE <br />
*2) Set "OE Must be inserted = ON" in contest setup. (OEs are too valuable to forget)<br />
*3) Non-G stations get "OO" for OE (there is no OO postal district in G[I|J|M|W|U]-land)<br />
*3) Mistakes - no OE sent or rcvd - get "XX" (there is no XX postal district in G[I|J|M|W|U]-land)<br />
*4) Postal districts in GM and GI can be worked multiple times for OE award<br />
<br />
<br />
== Post-contest editing ==<br />
<br />
There follows the steps required to hand-edit a Tucnak EDI (Contest Entry) file in order to bring the content of the file into line with RSGB (VHF) Contest Committee regulations: <br />
<br />
*a) Edit** EDI file to set correct (G-style) 'PSect' (Open | Single OP Fixed | Single Op Other | etc, etc).<br />
*b) Edit 'MOpe1'/'MOpe2' as necessary - if 'Global' setting is used for Operator.<br />
*c) Review Statistics File to identify multi-scoring OEs. DXCC listings in the Statistics export will identify GM and GI QSOs and numbers involved. <br />
*d) GI contacts can count 6 OEs for same Postal District (Only 1 PD in whole of GI ('BT'))<br />
*e) Find and manually note all GM contacts and count Q/OE. GM PDs count up to 3 times per OE.<br />
*f) Find first "OO" QSO: Edit the Multiplier section (end of row) to remove multiplier 'N' for the OE (first 'N' column). Same for 'XX' if used.<br />
*g) 'Search & Replace' ;OO; with ;; - same for XX if used. G-land contest adjudicator MAY penalise "incorrect" OE of "OO" or "XX".<br />
*h) IN/DE-crement 'CExcs' as appropriate (Take away 'OO' and 'XX'; Add any Multi-counting GM/GI OEs)<br />
*i) Total up correct Multipliers and replace 'CToSc' with product: [CQSOP x Total Mult]<br />
<br />
Save and close.<br />
<br />
Edit** means use a pure TEXT editor (Gedit, vi, TextPad, MS Notepad) not a "Word processor". <br />
<br />
<br />
--'OGY 01:17, 17 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Notes_on_hand-editing_Tucnak_EDI_files_for_G-land_OE_Contests&diff=481Notes on hand-editing Tucnak EDI files for G-land OE Contests2008-08-22T22:50:46Z<p>G1ogy: </p>
<hr />
<div>== Background ==<br />
<br />
Every year, in the UK VHF&up Contest calendar, there are 6 contests (plus the whole 'Backpacker' series) that use the exchange of 'Postal District code' as an additional Multiplier - an "Optional Exchange" or "OE".<br><br />
In certain parts of the UK the postal districts cover a large area so, to promote activity to and from these areas, their District Code can be counted more than once: 3x for GM Districts and 6x for GI.<br />
<br />
Tucnak does not (yet) support multi-counting of OEs. Nor does it print a list of OEs worked during the contest in the 'Statistics' output file. <br />
<br />
To summarise:<br />
<br />
*1) 'G' OE Contests may use Postal District (forced to 2 char) for OE <br />
*2) Set "OE Must be inserted = ON" in contest setup. (OEs are too valuable to forget)<br />
*3) Non-G stations get "OO" for OE (there is no OO postal district in G[I|J|M|W|U]-land)<br />
*3) Mistakes - no OE sent or rcvd - get "XX" (there is no XX postal district in G[I|J|M|W|U]-land)<br />
*4) Postal districts in GM and GI can be worked multiple times for OE award<br />
<br />
<br />
== Post-contest editing ==<br />
<br />
There follows the steps required to hand-edit a Tucnak EDI (Contest Entry) file in order to bring the content of the file into line with RSGB (VHF) Contest Committee regulations: <br />
<br />
*a) Edit** EDI file to set correct (G-style) 'PSect' (Open | Single OP Fixed | Single Op Other | etc, etc).<br />
*b) Edit 'MOpe1'/'MOpe2' as necessary - if 'Global' setting is used for Operator.<br />
*c) Review Statistics File to identify multi-scoring OEs. DXCC listings in the Statistics export will identify GM and GI QSOs and numbers involved. <br />
*d) GI contacts can count 6 OEs for same Postal District (Only 1 PD in whole of GI ('BT'))<br />
*e) Find and manually note all GM contacts and count Q/OE. GM PDs count up to 3 times per OE.<br />
*f) 'Search & Replace' ;OO; with ;; - same for XX if used. G-land contest adjudicator MAY penalise "incorrect" OE of "OO" or "XX".<br />
*g) Find first "OO" QSO: Edit the Multiplier section (end of row) to remove multiplier 'N' for the OE (first 'N' column). Same for 'XX' if used.<br />
*h) IN/DE-crement 'CExcs' as appropriate (Take away 'OO' and 'XX'; Add any Multi-counting GM/GI OEs)<br />
*i) Total up correct Multipliers and replace 'CToSc' with product: [CQSOP x Total Mult]<br />
<br />
Save and close.<br />
<br />
Edit** means use a pure TEXT editor (Gedit, vi, TextPad, MS Notepad) not a "Word processor". <br />
<br />
<br />
--'OGY 01:17, 17 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%27Hardy%27_(8.04_LTS)&diff=480Ubuntu 'Hardy' (8.04 LTS)2008-08-22T22:42:18Z<p>G1ogy: </p>
<hr />
<div>To compile Tucnak v2.13 on Ubuntu 'Hardy Heron' (8.04 LTS), on an Intel machine, additional libraries are needed:<br><br />
1) install all available updates from the STANDARD repositories.<br><br />
2) install the following additional libraries (the document files are optional):<br><br />
<br />
$ sudo apt-get install libglib2.0-dev libsndfile-dev libsdl-dev libpng-dev libasound-dev libftdi-dev libgpmg1-dev libaa1-dev libartsc0-dev libaudio-dev libcaca-dev libcucul-dev libdirectfb-dev libesd0-dev libxext-dev libxt-dev nas libasound2-doc libglib2.0-doc<br><br />
<br />
This worked for me with NO configure or compile warnings. YMMV, but this will be a good start!<br />
<br />
--'OGY 00:40, 23 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%27Hardy%27_(8.04_LTS)&diff=479Ubuntu 'Hardy' (8.04 LTS)2008-08-22T22:40:59Z<p>G1ogy: </p>
<hr />
<div>To compile Tucnak v2.13 on Ubuntu 'Hardy Heron' (8.04 LTS), on an Intel machine, additional libraries are needed:<br><br />
1) install all available updates from the STANDARD repositories.<br><br />
2) install the following additional libraries (the document files are optional):<br><br />
<br />
$ sudo apt-get install libglib2.0-dev libsndfile-dev libsdl-dev libpng-dev libasound-dev libftdi-dev libgpmg1-dev libaa1-dev libartsc0-dev libaudio-dev libcaca-dev libcucul-dev libdirectfb-dev libesd0-dev libxext-dev libxt-dev libasound2-doc nas libglib2.0-doc<br><br />
<br />
This worked for me with NO configure or compile warnings. YMMV, but this will be a good start!<br />
<br />
--'OGY 00:40, 23 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Ubuntu_%27Hardy%27_(8.04_LTS)&diff=478Ubuntu 'Hardy' (8.04 LTS)2008-08-22T22:31:18Z<p>G1ogy: run</p>
<hr />
<div>To compile Tucnak v2.13 on Ubuntu 'Hardy Heron' (8.04 LTS) additional libraries are needed:<br><br />
1) install all availale updates from the STANDARD repositories.<br><br />
2) install the following libraries (the document files are optional):<br></div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=477Main Page2008-08-22T22:27:00Z<p>G1ogy: /* Documentation */</p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
openSUSE users can find rpm packages here http://download.opensuse.org/repositories/hamradio/ <br />
Even simpler, search for "tucnak" at http://software.opensuse.org/search and follow the instructions for 1-click installation.<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
* [[Compiling]]<br />
** [[Ubuntu 'Hardy' (8.04 LTS)]]<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
[[Merge QSOs from all bands to one window]]<br />
<br />
[[All bands statistics]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=470Main Page2008-08-16T23:41:50Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
*Articles<br />
**[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=469Main Page2008-08-16T23:38:40Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)<br />
<br />
[[Notes on hand-editing Tucnak EDI files for G-land OE Contests]]</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=468Main Page2008-08-16T23:36:16Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
Machine translation can be done by Google:<br />
* [http://translate.google.cz/translate?hl=cs&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Čeština]<br />
* [http://translate.google.cz/translate?hl=de&sl=en&u=http://tucnak.nagano.cz/wiki/Main_Page Deutsch]<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully completed yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
** [[Tutorial]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
<br />
=Tucnak users=<br />
[http://ok2m.nagano.cz OK2M], [http://www.dr5a.de/equipment/ DR5A], [http://www.qslnet.de/member/ok5tr/ OK5TR], [http://ok1hra.nagano.cz OK1HRA], [http://www.m1cro.org.uk/ G0VHF/M1CRO], [http://www.ok2fug.com/?p=117#more-117 OK2FUG], [http://ok1rca.tym.cz OK1RCA], [http://www.landshut.org/members/db1ras/funkfreunde/contestdl1e.htm DL1E]<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]<br />
<br />
=Development=<br />
[[Shortwave features]]<br />
<br />
[[Optional exchange draft]]<br />
<br />
=Converting from TACLog=<br />
<br />
The source of inspiration for Tucnak was the DOS program TACLog (Author: Bo, OZ2M) as Lada, OK1ZIA freely admits. In the late 1990s TACLog was in regular use by over 200 stations, many continuing with the same logger today.<br><br />
It is becoming increasingly difficult to run a full-service TACLog, with CQ-caller, CW keyer and auto PTT as it must run directly on MS-DOS and requires a 'real' Soundblaster card.<br><br />
In this section I hope to provide useful information for those contemplating changing from TACLog to Tucnak and I would like to encourage everyone to add their knowledge and experience here to help and assist others coming after.<br><br />
--'OGY 01:36, 17 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Notes_on_hand-editing_Tucnak_EDI_files_for_G-land_OE_Contests&diff=467Notes on hand-editing Tucnak EDI files for G-land OE Contests2008-08-16T23:17:04Z<p>G1ogy: New page: == Background == Every year, in the UK VHF&up Contest calendar, there are 6 contests (plus the whole 'Backpacker' series) that use the exchange of 'Postal District code' as an additional ...</p>
<hr />
<div>== Background ==<br />
<br />
Every year, in the UK VHF&up Contest calendar, there are 6 contests (plus the whole 'Backpacker' series) that use the exchange of 'Postal District code' as an additional Multiplier - an "Optional Exchange" or "OE".<br><br />
In certain parts of the UK the postal districts cover a large area so, to promote activity to and from these areas, their District Code can be counted more than once: 3x for GM Districts and 6x for GI.<br />
<br />
Tucnak does not (yet) support multi-counting of OEs. Nor does it print a list of OEs worked during the contest in the 'Statistics' output file. <br />
<br />
To summarise:<br />
<br />
*1) 'G' OE Contests may use Postal District (forced to 2 char) for OE <br />
*2) Set "OE Must be inserted = ON" in contest setup. (OEs are too valuable to forget)<br />
*3) Non-G stations get "OO" for OE (there is no OO postal district in G[I|J|M|W|U]-land)<br />
*3) Mistakes - no OE sent or rcvd - get "XX" (there is no XX postal district in G[I|J|M|W|U]-land)<br />
*4) Postal districts in GM and GI can be worked multiple times for OE award<br />
<br />
<br />
== Post-contest editing ==<br />
<br />
There follows the steps required to hand-edit a Tucnak EDI (Contest Entry) file in order to bring the content of the file into line with RSGB (VHF) Contest Committee regulations: <br />
<br />
*a) Edit** EDI file to set correct (G-style) 'PSect' (Open | Single OP Fixed | Single Op Other | etc, etc).<br />
*b) Edit 'MOpe1'/'MOpe2' as necessary - if 'Global' setting is used for Operator.<br />
*c) Review Statistics File to identify multi-scoring OEs. DXCC listings in the Statistics export will identify GM and GI QSOs and numbers involved. <br />
*d)GI contacts can count 6 OEs for same Postal District (Only 1 PD in whole of GI ('BT'))<br />
*e) Find and manually note all GM contacts and count Q/OE. GM PDs count up to 3 times per OE.<br />
*f) 'Search & Replace' ;OO; with ;; - same for XX if used. G-land contest adjudicator MAY penalise "incorrect" OE of "OO" or "XX".<br />
*g) Find first "OO" QSO: Edit the Multiplier section (end of row) to remove multiplier 'N' for the OE (first 'N' column). Same for 'XX' if used.<br />
*h) IN/DE-crement 'CExcs' as appropriate (Take away 'OO' and 'XX'; Add any Multi-counting GM/GI OEs)<br />
*i) Total up correct Multipliers and replace 'CToSc' with product: [CQSOP x Total Mult]<br />
<br />
Save and close.<br />
<br />
Edit** means use a pure TEXT editor (Gedit, vi, TextPad, MS Notepad) not a "Word processor". <br />
<br />
<br />
--'OGY 01:17, 17 August 2008 (CEST)</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Advanced&diff=405Advanced2008-05-15T23:29:44Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
If you insert a callsign which is known in the C_W database, the program will 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 contained in the database, Tucnak fills in the large square with highest activity or that of the Capital City of worked DXCC and calculates approximate QTF.<br />
<br />
Similar situation is if you insert known locator. There'll be displayed two inverted callsigns which you can swap -press <Alt+C> and confirm by pressing <Alt+D>. Alternatively Tucnak shows prefix(es) of possible DXCC only if the entry isn't any known callsign<br />
<br />
Tucnak checks if pair of locator and callsign exists. If Tucnak thinks that it's invalid then it shows at locator some of these characters.<br />
<br />
* ! - large square doesn't lie in DXCC. If callsign and locator are correct an invalid record is in tucnakdw.<br />
* ? - Tucnak knows locators of this station but typed locator is different<br />
* nothing - callsign is unknown or locator corresponds with callsign.</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Advanced&diff=404Advanced2008-05-15T23:27:19Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
If You insert callsign which is known in C_W database, the program will 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 contained in the database, Tucnak fills in the large square with highest activity or Capital City of worked DXCC and calculates aproximate QTF.<br />
<br />
Similar situation is if you insert known locator. There'll be displayed two inverted callsigns which you can swap -press <Alt+C> and confirm by pressing <Alt+D>. Alternatively Tucnak shows prefixes of possible DXCC only if the entry isn't any known callsign<br />
<br />
Tucnak checks if pair of locator and callsign exists. If Tucnak thinks that it's invalid then it shows at locator some of these characters.<br />
<br />
* ! - large square doesn't lie in DXCC. If callsign and locator are correct an invalid record is in tucnakdw.<br />
* ? - Tucnak knows locators of this station but typed locator is different<br />
* nothing - callsign is unknown or locator corresponds with callsign.</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Duplicate_callsign&diff=403Duplicate callsign2008-05-15T23:22:17Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
If you write callsign which is saved before then Duplicate QSO dialogue is displayed. You have several choices, see below.<br />
<br />
* Clear this QSO - clear this QSO (as F3 key), old QSO isn't changed<br />
* Edit old QSO edit changes in old QSO<br />
* Mark old QSO as ERROR - Mark old QSO as ERROR, a new QSO is relevant now<br />
* Store as DUPE - Old report is achieved, new has zero points but it's logged as DUPE.</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Duplicate_callsign&diff=402Duplicate callsign2008-05-15T23:21:48Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
If you write callsign which is saved before then Duplicate QSO dialogue is displayed. You have several choices, see below.<br />
<br />
* Clear this QSO - clear this QSO (as F3 key), old QSO isn't changed<br />
* Edit old QSO edit changes in old QSO<br />
* Mark old QSO as ERROR - Mark old QSO as ERROR, a new QSO is relevant now<br />
* Store as DUPE - Old report is achieved, new have zero points but it's loged as DUPE.</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Hotkeys&diff=401Hotkeys2008-05-15T23:15:41Z<p>G1ogy: /* Other usefull system keystokes */</p>
<hr />
<div>{{Languages}}<br />
<br />
* F2: saves QSOs from all bands<br />
* F3: erases input line and report<br />
* F3: opens a new contest<br />
* F4: switches between windows<br />
* F5..F8: exec call 0 .. 3 (CW or SSB)<br />
* F9,F10: menu<br />
* F11..F12: exec call 4 .. 5<br />
* Alt+B: switches bands<br />
* Alt+C: swaps callsigns in unfinished QSO<br />
* Alt+D: confirms offered callsign<br />
* Alt+F: sets preferred QRG for skeds<br />
* Alt+G: S&P's request for QSO/RUN's confirm<br />
* Alt+H: shows history of input line<br />
* All+M: swaps CW/SSB modes<br />
* Alt+N: displays next item in history<br />
* Alt+O: changes operator<br />
* Alt+P: displays previous item in history<br />
* Alt+S: sends sked<br />
* Alt+Q: exits from program<br />
* Alt+U: adds QSO to unfinished QSO<br />
* Alt+V: swaps locator<br />
* Alt+X: confirms offer locator<br />
* Alt+Y: erases unfinished QSO only<br />
* Alt+1..0: directly switchs to window 1 .. 10<br />
* Ctrl+L: redraws screen<br />
* Ctrl+P: shows polar map (only in graphics mode)<br />
* Ctrl+V: allows insert special characters to input line. (TODO)<br />
* Ctrl+Y: erases input line<br />
* Ctrl+A..X: changes band<br />
* TAB: switches on PTT in SSB mode. Switch on transmitting from keyboard in CW mode.<br />
* Up Arrow: sets window active<br />
* ESC: finish CQ or switches to input line<br />
* Enter: if CW window is active it's closed<br />
* [: horizontal scroll log to left (TODO)<br />
* ]: horizontal scroll to right<br />
<br />
=Key in graphics window=<br />
<br />
* c: centers map to QTH<br />
* l: enables/disables line from QTH to station<br />
* r: redraw map<br />
* ESC, q: closes graphics window<br />
* Cursor keys: moves the map about 100 disp. points<br />
* +,-: zoom map<br />
* F1: saves graphics window to contest directory in BMP picture format<br />
<br />
=Other useful system keystokes=<br />
<br />
* Alt+Fx - Changes active console to virtual console x (in console mode)<br />
* Ctrl+Alt+Fx - as above in X Window System<br />
* Alt+Left/Right Arrow - changes console from one to rigth/left</div>G1ogyhttp://tucnak.nagano.cz/wiki/index.php?title=Main_Page&diff=395Main Page2008-04-27T13:57:02Z<p>G1ogy: </p>
<hr />
<div>{{Languages}}<br />
<br />
= Tucnak Wiki=<br />
<br />
This site is intended to serve as documentation for Tucnak - hamradio VHF contest log. You can read it, create your own pages or correct spelling. <br />
<br />
Site is in English only. I'm not able to maintain more languages than one. English is preferred because most of hams understand it. But this wiki is not restricted only to English - you can write pages in your mother tongue.<br />
<br />
Because of spammer's attacks you must register to contribute to this wiki. Sorry.<br />
<br />
=About Tucnak=<br />
<br />
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 http://tucnak.nagano.cz.<br />
<br />
=Available translations of wiki=<br />
*[[FR Main Page|Français]] Maintained by Jerôme F0FLO, tnx!<br />
<br />
=Download=<br />
Please download Tucnak here http://tucnak.nagano.cz/download.php#ver2<br />
<br />
=Screenshots=<br />
<gallery><br />
Image:Qsos.png|QSOs window<br />
Image:Stats.png|Statistics<br />
Image:Map.png|Polar map<br />
</gallery><br />
<br />
=Documentation=<br />
Not fully comleted yet, I'm working on it...<br />
* [[Features]]<br />
* [[Quick Start]]<br />
* [[Install]]<br />
* Settings<br />
** [[Post Install Settings]]<br />
** [[Files]]<br />
** [[Variables]]<br />
** [[Command line]]<br />
* [[New Contest]]<br />
* [[Network]]<br />
* Control<br />
** [[Basic control]]<br />
** [[Edit QSO]]<br />
** [[Hotkeys]]<br />
* [[Output formats]]<br />
* [[Activity]]<br />
** [[Duplicate callsign]]<br />
** [[Advanced]]<br />
* [[Menu]]<br />
* [[Using NTP]]<br />
* [[References]]<br />
* [[Thanks]]<br />
TODO subwin types<br />
<br />
=How to help?=<br />
<br />
* By testing stable and development branch of Tucnak and sending error list to me.<br />
* Help with refill data files like tucnakdw and tucnakwiz.<br />
* Laud about Tucnak :-)<br />
* If you have some idea how to improve Tucnak, please mail me this idea.<br />
* Write a new part of Tucnak.<br />
* Translate this documentation to other languages (or repair bugs in the English version :-) ).<br />
* Create package for your distribution.<br />
* Voluntary small contribute for beers please sent to author (to me).<br />
<br />
73! Ladislav Vaiz, OK1ZIA<br><br />
<MYCALL>@nagano.cz<br />
<br />
=Obsolete branch 1=<br />
Tucnak: [http://tucnak.nagano.cz/tucnak1en.html english documentation], [http://tucnak.nagano.cz/tucnak1cz.html česká dokumentace]<br />
<br />
SSB daemon: [http://tucnak.nagano.cz/ssbd0en.html english documentation], [http://tucnak.nagano.cz/ssbd0cz.html česká dokumentace]</div>G1ogy