WARNING! Backup your data often! BACKUP your log directory at the end of EVERY session! All that you need to backup and store in a safe place is the log database directory located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function in Preferences. This autobackup function creates an ADIF file with a backup of your log. /td>
[Menu]

CQRLOG for LINUX by OK2CQR & OK1RR

Contest support

You will find contest selection from NewQSO/Window dropdown menu. Contest support of Cqrlog is very limited, but will serve you well if you just like to take a part to contest without winning in mind.
Contest window is just a "child form" for NewQSO to make qso logging faster when working in contests. With Tru and Msg is Loc setting it is useful also in VHF, UHF, SHF Tropo, Es etc. openings for fast qso logging. Perhaps also in some other operations like WWFF activations.

Note: This is NOT a contest logging add-on!!! It is a contest-notepad. It is meant to be a tool for "Sunday contesters working in Tourist Class". Do not expect wonders!

When contest window is open NewQSO has contest exchange fields visible. You may have to stretch NewQSO window horizontally to see them. You do not normally need NewQSO window during contest.
Only need for NewQSO is in case you have to edit an already worked qso. Select qso normally via QSO list and press edit QSO button and you are able to edit qso, also the contest message part of it.

Repeat: NewQSO is not meant to be used during contest qso feeds. All new qsos are entered via contest window.

RECOMMENDATION:
Make new log for each contest, consider not to allow qrz/hamqth search, it may slow down qso feed.
It might be a good idea to have two logs the "contest" that is used during a contest and then cleared for new contest and the other as "contest archive" where contents of "contest" are moved with adif export after Cabrillo log is sent.
Benefit of having "contest" log with one contest is also that you get DXCC statistic right after cursor leaves callsign column. You can place contest window just above NewQSO/DXCC statistic.(see pic above).

Contest window has a simple dupe check that turns typed duplicate callsign bold red printed. If you save a duplicate qso it is marked as "/D" in "RST sent" field. When doing Cabrillo export it is operator's duty to decide what to do with "/D" reports
To get duplication check working properly you must either create a new log for every contest or set dupe start date (I.E. contest starting day) with button "from YYYY-MM-DD"

Hotkeys:

Hotkeys work same way as with New QSO window.

Contest window has following fields and checkboxes:

Buttons you really do not need (you should NOT use mouse when working contest!):


All settings, including contest name, are saved when closing contest form. When opening cqrlog and contest form again after rest period you can directly continue contest working.

Typical contest qso goes like this:
Type callsign->press TAB->type contest rxnumber->press TAB->type contest message->press ENTER. Or hit ENTER after rxnumber if no additional message is exchanged. When S&P is checked you maybe need to launch some Cw messages manually.

Remember that pressing ENTER key at any column saves qso with existing values. How ever there must be callsign of least three characters long. Sent/Received number and message(s) are not needed.
There is no need to use the mouse. Keep your hands on keyboard (and possible on CW key / PTT (if not foot pedal in use)). It is faster.

Contest numbers and messages are saved in log in their own columns. Use preferences/Visible columns to show them in Qso list.

CW messages can be used for sending contest messages. Look at help section CW Operation how to use macros in messages.
NOTE: If you use macro that sends whole contest message (%xrs = RST, STX, STXString) message will skip empty ones. This way %xrs works for all contests.

Status view support

NOTE: If you have one log called contest that you clear always before contest, to have just qsos of that contest, and after contest you move all qsos with adif export to another log called archive you can view contest status afterwards from that log if you have used unique contest names I.E. added contest start date to name.
Find contest with Filter/Contest filter and copy name from selection list box and paste it to Contest window. You do not have to activate contest filter to see the status of that contest.

OK1WC memorial contest status is supported.

If contest name has "mwc" or "ok1wc" included (no case sensitive) then status counting is activated. At the start of contest (and any oher time when no qso to save) it can be seen by pressing 2xESC. After saving a qso Status view is updated.
TRXControl must show that rig is on 80m or 40m band. If you do not have cat controlled rig select "Hamlib dummy #1" as rig and set correct band and mode from TRXControl's band buttons.
Only bands 80M and 40M and mode CW are counted (See rules of contest).


Nordic Activity Contest (NAC) status is supported.

If contest name has "nac" included (no case sensitive) then status counting is activated. At the start of contest (and any oher time when no qso to save) it can be seen by pressing 2xESC. After saving a qso Status view is updated.


Common status is supported.

If contest name has any name that does not fit rules of two above status counting is activated. At the start of contest (and any oher time when no qso to save) it can be seen by pressing 2xESC. After saving a qso Status view is updated.
There are several items shown in Status display. You can control them by left click below text Status (but above status display itself).
The DX and own continent counts (EU in picture) are defined against your callsign in preferences/station/call.

To see Status section you may need to stretch the bottom part of Contest window.
NOTE: Status counting may have errors! It is just for showing progress of contest, not to show final score.

After contest

Most contests expect Cabrillo log format. Cqrlog has a limited support of Cabrillo exports. Mostly enough for a Sunday contester.
In case you want to use external Cabrillo program you have to make ADIF export of qsos and then use another program.


I found nice adif2cabrillo program for Linux from http://users.telenet.be/on4qz/ that supports ADIF importing.

Starting is bit complicated:
You need to compile it from source. Qt5 with qmake (called qmake-qt5 if your distro is Fedora) is needed to be able to compile it.
Then there are no templates for different contests. You have to create them, but after that it serves you well! It accepts nicely exported ADIF format from cqrlog and dig out STX and SRX as expected.

ADIF exports fields to right tags.
<RST_SENT:3>599<STX:3>001
<RST_RCVD:3>599<SRX:3>002
<RST_SENT:3>599<STX:3>003<STX_STRING:2>SA
<RST_RCVD:3>599<SRX:3>003<SRX_STRING:2>dd
<RST_SENT:3>599<STX:3>002<STX_STRING:2>SA
<RST_RCVD:3>599<SRX:3>003<SRX_STRING:2>kb
<RST_SENT:3>599<STX:3>001<STX_STRING:2>SA
<RST_RCVD:3>599<SRX:3>002<SRX_STRING:2>SB

HTML export will look like this:


[Menu]