ADIF import

The main purpose is to add QSO records from other logging and/or contesting programs. You may need it if you migrate from another logger or if you are adding contacts made in a contest (any modern contesting program has the ADIF export facility, some older programs may need a third party conversion utility).

Cqrlog now follows ADIF 3.1.0 specification of special UTF8 characters. Mainly they can be found from Name, QTH, Comment and Notes fields. Specification says that when there is special character(s) some adif tags may have suffix _INTL to show this. Like <QTH_INTL:6>Pyhtää
If pure ASCII charcters are found the usual tag format is used. Like <QTH:4>Pori
Every time special UTF8 character is found in tags, where specification allows, UTF8 printing routines are used and the _INTL suffix is added.
At import side tags with suffix _INTL are read with UTF8 routines. Without _INTL with normal ASCII routines. This makes importing backward compatible with old cqrlog exports that have set tag lenght wrong if there has been special UTF8 characters in tag data.

Go to QSO list (Ctrl-O on the main logging screen or File -> Show QSO list from the menu).



From the menu here choose File -> Import -> ADIF.

Click on 'ADIF' and an 'Open file' dialog appears.



Navigate to the file you want to import and click 'Open'. You will see a new dialog, click the 'Import' button here. You can also add a QTH profile and a note ('Comment to QSO(s):') which will appear on every imported QSO record. Using this option, a portable, mobile or QRP operation can be clearly marked.
You can also filter by date range of adif file records. Checking "No check for duplicates" and "ADIF file contains..." may speed up big ADIF imports.



If you import a huge file, you will see a progress bar, however import of a small file is so fast that you never notice the progress indicator.

If the ADIF file contains a grid locator (tag MY_GRIDSQUARE) that will be used upon import. In the case that this is not present the grid locator from the selected profile will be used. If also that is absent or incorret the default locator from the config will be used. However the user can choose to override a MY_GRIDSQUARE from ADIF file by selecting the checkbox. In this case MY_GRIDSQUARE from the ADIF file is overriden by the locator from the selected profile or if no profile is selected the default locator from the config is used.

The window now shows the import completion, the number of imported records and the number of errors. If the ADIF file contains incorrect entries, they will be stored separately in the file errors_HH_MM_SS.adi located in the user's home folder. You can open, import or delete the file by pointing the name with left mouse click.

If you plan to import fixed error file you have to fix every qso record line at point(s) the ERROR: -line(s) show. After fixing a qso record you must delete corresponding ERROR: -line(s).
Text editor to use must be defined at preferences/External viewers. If reimported error file still has errors you can delete it from popup menu and continue with new error file.
NOTE: If you change tag text you have to check the length of text that is after tag name, before text itself, as :xx> where xx is the count of characters in tag string.

<Complete adif qso record here>
ERROR: Wrong QSO IOTA: NO

NOTE: Error file now contains also qsos that are imported with shrunken adif tags. There is no need to import them again. You can fix shrunken tags with QSL list/Edit QSO.

<Complete adif qso record here>
ERROR: Imported with shrink(s):
STATE shrink to 4 chrs:05 // Yamagata-ken -> 05 /
QSL_VIA shrink to 30 chrs:via Bureau, Direct, e-QSL, LoTW -> via Bureau, Direct, e-QSL, LoT

Duplicate entries (contacts already in the log) are indicated with a separate dialog allowing you to exclude or include these records. This will be asked every time a duplicate is found. If you check Case of duplicates; Remember my answer it is asked only once and then the same answer is used every time a duplicate is found.

ADIF export

Go to QSO list using Ctrl-O or choose the QSO list from the upper menu - item 'File'.



From the QSO list, choose 'Export' in the menu - item 'File'.



Choose 'ADIF'. An usual a dialog appears (depending on the desktop used). Choose a location and file name.





When OK is pressed export begins.

HTML export

The same as above, only difference is to set column names and widths (in character counts). Note that contest Nr and Msg column names will get "R" or "S" added as last letter of column name.



If "HTML auto size columns" is checked width setting is ignored and column width is set by longest text (in header or data).



Choose the 'HTML' option from QSO list Export menu.

EDI export

This function can be used to export contest logs in .edi file format. This export requires a suitable filter to be set. Generally only one band per file is allowed. Also make sure that the fields like exchange sent/received are set properly before exporting. If you choose this export you will see the follwing window.



You can set the filename to export to as well as some meta data describing the equipment you used for this contest.

After export is done you can see the summary of exported qsos. Also Open exported file button appears.
If you have set preferences/External viewers/text files exported file will be opened when button is pressed.



If your contest did not use serial numbers you can uncheck Export requires serial nr that may clear out export error qsos.

Cabrillo export

This dialog can be used to export contest logs in Carbillo format. Cabrillo is very compilcated to export as almost all contests have their own QSO line layout and score counting. That's why Export has no score counting, but it offers some statistics from exported qsos to help manual counting of claimed score.

For export Qso list/filter/create or Qso list/filter/Contest filter has to be set to select qsos to be exported.
If you used Qso list/filter/Contest filter you can press button Frm Flt to get contest name from filtered result.

QSO-line header follows most used layout and can not be modified, except width of callsign space that affects both calls (my&wkd).
Use UpCase letters for all QSO records is defaut checked and converts QSO lines to upper case. Mainly changes exchange messages if they have been written with low case letters. This setting can be saved to log settings file.
Info sent and rcvd can be modified using selections. Some contests do not use reports, they can be omitted from checbox.
Exchange1 and Exchange2 can contain data by selected by selectors with given space width 1-99. If empty they are ignored.
TX count is the transmitter count at the end of line. It can also be empty and so ingnored
Many template layouts to study can be found from http://www.contestlogchecker.com/cabrillo-templates.html

With Count pfx user can get statistic count from qsos to certain country. Type in callsign prefix of country. If export thinks prefix is wrong it clears column when moved away from it. Then try again. Example: VA is not ok, but VA1 will turn accepted as VE.

Export remebers last used settings (by used log). You can also save and load settings for different contests using save and load buttons.
At bottom of form there is prograss indicator and after export there is some statistics and possible error message shown. You can also open resulted Cabrillo file with defined text editor (preferences/external viewers) using button "Open resulted file".
If red error text is displayed after export you can open error log by clicking the red error text line.

As cabrillo export output is very basic you may need to edit exported file afterwards with text editor to suit your purposes!

Program version update:

Ubuntu 16.04, 17.10, 18.04 users can use CQRLOG’s repository on Launchpad. To add repository to your system, put into terminal this:

sudo add-apt-repository ppa:ok2cqr/ppa;sudo apt-get update;sudo apt-get install cqrlog

For those who does not use Ubuntu, load install package, or binaries, from: Cqrlog.com download page.

The binaries should work in any distribution. Please don't forget to install MySQL server, MySQL client, Hamlib libraries and if LoTW support is desired, trustedqsl package and libssl-devel must be installed.

Note: Very often Cqrlog version update requires just file /usr/bin/cqrlog change to latest version. If your package manager does not support latest version and you have well running old version in use just copy folder ~/.config/cqrlog with all files and subfolders to safe place as backup. Copy also /usr/bin/cqrlog to same place. Then download the tgz file "Complete application directory for other distributions", extract file /usr/bin/cqrlog from there and copy it to your /usr/bin folder (you need to use root priveleges I.E sudo for that). If everything works you have latest version. If not, just copy back your saved folder ~/.config/cqrlog and the old /usr/bin/cqrlog.

How to update Country files:

1. Unpack and copy all the files into the /ctyfiles folder in your CQRLOG main folder. The purpose of this folder is to store these files only, it is not bound to CQRLOG and does not affect its function.
2. Start CQRLOG and select the 'Show QSO list' from the 'File' item in the main menu. You can also get there using shortcut Ctrl-O.
3. If you are already in the QSO list, go to menu. Click the 'File' item, then the 'Import' option. Choose the DXCC data option, located at lowest position. A dialog appears, navigate to your /ctyfiles folder. Click the 'Open' button. All files are read and if the import completes, a small window with the message 'Import complete. Please restart program' appears. Click the OK button and quit CQRLOG.
4. Restart CQRLOG. The update is finished.

Note: While opening your new country files [see 3.], you dont need to open a particular file. The 'Open' button starts a procedure which reads ALL files in the /ctyfiles folder.

WARNING! Don't attempt to create your own country files. This can result in the program crashing or incorrect statistics. If you find an incorrectly resolved station (no matter if current log or an old record), send a note directly to me: martin@ok1rr.com. ALWAYS replace all files in the /ctyfiles folder! If you leave an old file or update only a single file from the new version, the resulting tables will become out-of-sync which leads to incorrect statistics. Also, the logger may not work properly.

WARNING! If you update your country files or upgrade the CQRLOG version, always perform the 'Rebuild DXCC statistics' which is accessible from the QSO list screen.

Some users have reported that their DXCC statistics became 'out of sync' and the actual DXCC scoring does not match the results reported by CQRLOG.

Remember that a regular rebuild of your DXCC statistics is a matter of importance. Rebuild if you upgrade country files, rebuild also if you upgrade the program version!

QSL Manager Database update

Since version 0.8.0 CQRLOG uses its own QSL Manager database in a very simple, plain text format (CSV, semicolon separated). The update is very simple. The automated update checks the availability of a new version, downloads and unpacks the tar.gz file if available. The new version must be imported - go to QSO list (Ctrl-O or from menu File -> Show QSO list) and choose the File -> Import -> Import qsl managers database.

A manual update is also possible if you download a recent version from the CQRLOG site http://www.cqrlog.com.



The QSL Manager database format is as follows:

call;qsl_manager;publishing_date
Example:
3D2BV;JA1PBV;2008-01

You can maintain your own records but we carefully maintain this database with verified records from reliable sources (DX Bulletins). The database is updated monthly and the covered timespan of QSL Managers is limited to 10 years after publishing date. After this time, the expired records will be removed and stored in another file (archive) which will be available on the CQRLOG site http://www.cqrlog.com.

Note: Because the HamQTH.com/QRZ.COM entries very often contain details useful for direct lookup but not suitable to print on QSL labels, choose the option 'Ignore HamQTH.com/QRZ.COM qsl info' in the Preferences -> New QSO dialog.

If a station has more than one QSL Manager, click the small button to the left of the QSL VIA field.



A popup window of selections appears:



Navigate to the appropriate QSL manager, use the publishing date column or verify the QSL manager from another source. This ensures that the QSL label will contain the proper QSL manager.

Statistics rebuilding



The only way to rebuild your statistics is from the QSO list. The 'Statistics' menu item has the 'Rebuild DXCC statistics' option (the similar option on the logging screen does NOT have a 'Rebuild' option).

WARNING! The statistics rebuilding takes a long time if your log contains tens of thousands records!

A warning appears before the rebuilding process. If you answer 'Yes', be prepared for a long wait.

Membership databases

CQRLOG supports online tracking of up to 5 memberships simultaneously. The membership databases can also be used for filter creation, along with a date span (from-to). The tracking and filtering feature is not limited to membership, you can create your own databases using lists of your particular interests (short-term awards, local groups etc.). The databases have a pure text format with data columns separated by a semicolon ';'.

The default installation contains data of some 57 clubs: AFM, AGCW, ARKTIKA, A1-CLUB, A1-OP, CAV, CCT, CFO, CFT, CONVENIAT, CTC, CWJF, CWSP, DIG, DTC, EHSC, EPC, FFR, FIRAC, FISTS, FMC, FOC, GACW, GQRPC, HACWG, HHC, HH, HSC, HTC, JAIG, MARCONISTA, MCL, MFCA, MF, OKDXC, OKDXF, OTC-SARA, PRC, PRL, QCWA, RAFARS, RIA, RNARS, RRDXA, RTC, SHSC, SKCC, SPAR, SPDXC, TEN-TEN, TFC, UDXC, UFT, VHSC, VRK, WAP, 070-CLUB, 9ACWG.
You can go to

/home/~/.config/cqrlog/members

(the tilde ~ represents the name of your personal subdirectory within the 'home' folder).

Any membership file also contains a header consisting of two lines:

HSC
High Speed Club

where the first line represents the short name of the club and the second line is the long club name. Both names must be in the header on separate lines. The first line must be the same as the filename without suffix, ie. the HSC membership list must be

hsc.txt

The mandatory suffix is .txt and the filename must be in lowercase.

You can examine the syntax which is more descriptive than this short example, however there are basically 3 types of membership list files:

1. Simple list of call signs. It does not contain any membership number or date limits. Syntax:

  W5LGY
  W5LJT
  W5LKL
  W5LP

ie. a single call per line.

2. List of call signs with membership numbers. Syntax:

  DL5JAN;4603
  DL5JBM;4746
  DL5JBN;4642
  DL5JBW;5740

ie. a single call and membership number per line. The call and the membership number are separated by a semicolon ';'.

3. List of call signs with membership numbers and date limits.Used for short term awards or time span limited memberships. Syntax:

  6O2NG;533;1957-04;2005-03
  6Y5SR;868;1966-03;1982-07
  6Y5XG;331;1951-05;-
  7J1AEF;1297;1976-06;-

ie. a single call, membership number and datelimits from-to, separated by a semicolon ';', per line. See above the two optins: 6O2NG with membership number 533 was a member of the club from April, 1957 to March, 2005. 6Y5XG with number 331 started his membership May, 1951 and is still a member. The dash instead of a date (separated from the begin date by a semicolon) denotes that the membership is still active. A dash can be used only in the field for 'to'.

WARNING! You must keep lists of your particular interests updated yourself! It is impossible for the authors to keep all these tables up-to-date, however if you update a list and would like to share it with others, you are welcome!

Log backup

Your log is in the

/home/~/.config/cqrlog/

(the tilde ~ represents the name of your personal subdirectory within the 'home' folder).

Backup this directory, however it is big. If you want to save space, export your log into an ADIF file which is about half the size of the database directory. ADIF is also version independent. Zipped or tared ADIF files also have a reasonable size if your log contains several 100 000 records.