CQRLog on Linux — Complete Ham Radio Logging Setup and Operating Guide

What is CQRLog and who it is for

CQRLog has been the standard ham radio logger for Linux since 2008. Written in Free Pascal/Lazarus by OK2CQR and maintained by an active development community, it stores QSOs in a MariaDB database rather than flat files — giving it significant advantages over simpler loggers in terms of search speed, data integrity, and the ability to manage large logs efficiently.

The application integrates everything a serious HF operator needs into one interface: real-time DX cluster telnet with callsign lookup, automatic country and continent resolution using the OK1RR DXCC database, grayline map, QSL management for paper and electronic QSLing, direct LoTW and eQSL upload, Hamlib rig control, and award tracking for DXCC, WAZ, WAS, and IOTA.

Installation on Ubuntu and Debian

Ubuntu 22.04, 24.04 and Debian 11, 12

This installs CQRLog and its dependencies including MariaDB, Hamlib, and all required libraries.

Install the latest version from GitHub

The repository version may lag the latest release. Download the current .deb from the CQRLog GitHub releases page:

Build from source

Raspberry Pi

CQRLog runs on Raspberry Pi 4 with Raspberry Pi OS. Use the apt install method. Performance is adequate for normal logging use though the startup time is longer than on a desktop machine due to MariaDB initialization.

Verify installation

Database setup and first launch

CQRLog uses an embedded MariaDB database that it manages itself. You do not need to configure a database server manually — CQRLog handles all of this on first launch.

First launch procedure

1. Launch CQRLog from your application menu or run cqrlog in a terminal
2. On first run CQRLog checks for the database and prompts to create it — click Create
3. CQRLog starts the embedded MariaDB instance and creates the logging database
4. The New Log wizard opens — enter a log name (your callsign is common) and your station details
5. CQRLog opens the main logging window

Database location

CQRLog stores its database in ~/.config/cqrlog/database/. This directory contains all your QSO data. Back it up regularly — see the Backup section below.

Multiple logs

CQRLog supports multiple separate logs within the same database — useful for contest logs, club callsign operation, or /P and /MM operation. Create additional logs via File → New Log. Switch between logs from the same menu. Each log has its own station settings, DXCC statistics, and QSL status tracking.

Station configuration

Configure your station details under Settings → Station Info. These values are used for DXCC lookups, award tracking, and QSL cards.

Essential station settings

• Callsign — your full callsign including any portable suffix
• Name — your name as it appears on QSL cards
• QTH — your location city and country
• Locator — your Maidenhead grid square (4 or 6 characters)
• IARU Region — 1 (Europe/Africa), 2 (Americas), or 3 (Asia/Pacific)
• CQ Zone and ITU Zone — used for WAZ and other awards

Country file — keeping DXCC data current

CQRLog uses the cty.dat file to resolve DXCC entities from callsigns. Update it regularly to ensure new entities and changes are reflected correctly:

Then in CQRLog go to Settings → Country Files → Update to reload the new file.

Rig control with Hamlib and rigctld

CQRLog uses Hamlib to read your radio's frequency and mode automatically, filling them in when you log a contact. Configure it under Settings → TRX Control.

Method 1 — Direct Hamlib connection

1. Go to Settings → TRX Control
2. Select your rig model from the Rig dropdown
3. Set the Device to your serial port — usually /dev/ttyUSB0
4. Set the Baud Rate to match your radio's CAT baud rate
5. Click Connect — CQRLog starts polling the radio every 2 seconds

Method 2 — Via rigctld (recommended for shared rig control)

If you also run Fldigi or WSJT-X, use rigctld as a shared rig control daemon so all applications access the same serial port through one broker:

In CQRLog Settings → TRX Control: set Rig type to rigctld, Host to localhost, Port to 4532.

Serial port permissions

Hamlib model numbers for popular radios

DX cluster integration

CQRLog has a built-in DX cluster telnet client that shows live spots from the worldwide DX cluster network. Clicking a spot tunes your radio to that frequency via rig control automatically.

Connecting to a DX cluster

Go to Settings → DX Cluster and configure:

• Host — cluster server address
• Port — cluster port (usually 7300 or 23)
• Callsign — your callsign for cluster login

Popular DX cluster nodes

Understanding cluster spot colors

CQRLog color-codes DX cluster spots based on your log status:

• Red — new DXCC entity not yet worked on any band or mode
• Orange — new band or mode slot for an entity you have worked
• Yellow — worked but not confirmed on LoTW or paper QSL
• Green — worked and confirmed — already counts for DXCC
• Grey — worked and confirmed on this specific band/mode

Focus on red spots when chasing new DXCC entities — they represent countries you have never worked before.

Setting cluster filters

On busy days the cluster can be overwhelming. Set filters to show only what matters:

Callbook lookup — QRZ and HamQTH

CQRLog can look up callsign details automatically when you enter a callsign — filling in the station's name, QTH, grid square, DXCC entity, and other details. Configure under Settings → Callbook.

QRZ.com XML lookup

QRZ.com provides an XML API for callsign lookups. You need a QRZ.com account (free) and for full data access a QRZ.com XML subscription ($30/year). Enter your QRZ credentials in Settings → Callbook → QRZ.com.

HamQTH (free alternative)

HamQTH.com provides a free callsign lookup API with no subscription required. Register at hamqth.com and enter your credentials in Settings → Callbook → HamQTH. Coverage is slightly less comprehensive than QRZ but excellent for most callsigns.

Local cty.dat lookup

Even without a callbook subscription CQRLog resolves DXCC entity, CQ zone, and ITU zone from the local cty.dat file. This is the minimum needed for award tracking and is completely free.

Operating guide — logging contacts efficiently

Basic contact logging workflow

1. Enter the callsign in the Callsign field and press Tab
2. CQRLog resolves the DXCC entity, CQ zone, and ITU zone automatically from cty.dat
3. If callbook is configured, name and QTH fill in automatically
4. The Band and Mode fields fill from rig control if active
5. Enter RST sent and received — default is 59/59 for phone, 599/599 for CW and digital
6. Add any notes in the QSL field if needed
7. Press Enter or click Save — the contact is logged and CQRLog checks for duplicates

Duplicate checking

CQRLog automatically checks your log for duplicate contacts when you enter a callsign. A yellow indicator means you have worked this station before on the same band and mode — potentially a duplicate. A red indicator means you have a confirmed QSL for this contact. You can log duplicates if needed (for example, making another contact during a different contest period) but the warning helps during busy pileup operating.

Using the DX cluster during an operating session

Keep the DX cluster panel open during operation. When an interesting spot appears:

1. Click the spot — CQRLog sends the frequency to your radio via rig control
2. The radio tunes to the spotted frequency automatically
3. Listen and work the station if the propagation is there
4. When the QSO completes, the callsign is pre-filled in the log entry from the cluster spot

Logging split frequency contacts

For DX stations running split operation (listening on a different frequency from where they transmit), log the DX station's transmit frequency — the one they are broadcasting on. Enter it in the QRG field manually if it differs from your current rig frequency.

Speed logging during a contest

For contest operating, set up exchange macros and keyboard shortcuts. CQRLog supports serial number assignment for contests — it automatically increments the serial number with each logged contact. Use Tab to move between fields quickly and Enter to log without touching the mouse.

Searching and editing past contacts

Access your full log via Log → Browse Log. Search by:

• Callsign — find all contacts with a specific station
• Date range — show contacts from a specific period
• Band and mode — filter by operating parameters
• DXCC entity — find all contacts with a specific country
• QSL status — find unconfirmed contacts for follow-up

Double-click any contact to open it for editing. Changes are saved to the database immediately.

LoTW setup and automatic upload

ARRL's Logbook of The World (LoTW) is the most widely accepted electronic QSL system for DXCC credit. CQRLog can upload contacts to LoTW automatically after each QSO.

Installing TQSL

Getting your LoTW certificate

1. Register at lotw.arrl.org if you have not already
2. Open TQSL and go to File → Request New Station Location
3. Enter your callsign — ARRL verifies your license and issues a certificate by post
4. When the certificate arrives by email open TQSL and install it via File → Load Certificate from File
5. Create a Station Location in TQSL for each callsign/location combination you operate from

Configuring LoTW in CQRLog

1. Go to Settings → LoTW
2. Set the TQSL binary path — usually /usr/bin/tqsl
3. Enter your LoTW callsign
4. Select your certificate from the dropdown
5. Enable Upload QSOs to LoTW after logging for automatic upload

Batch LoTW upload

To upload all unconfirmed contacts at once go to Awards → LoTW → Upload All Unconfirmed. CQRLog exports the contacts, signs them with TQSL, and uploads to LoTW in one operation. Allow 24–48 hours for LoTW to process and update your confirmations.

Checking LoTW confirmations

Download new confirmations from LoTW via Awards → LoTW → Download New Confirmations. CQRLog marks newly confirmed contacts in the log and updates your DXCC totals automatically.

eQSL configuration

eQSL.cc is a free electronic QSL system popular among digital mode operators. Configure it under Settings → eQSL.

Setup

1. Register at eqsl.cc (free)
2. In CQRLog Settings → eQSL enter your eQSL username and password
3. Enable Upload QSOs to eQSL after logging for automatic upload
4. Download incoming eQSLs via Awards → eQSL → Download New

eQSL vs LoTW

For DXCC credit only LoTW confirmations count — ARRL does not accept eQSL for DXCC. However eQSL is accepted for some other awards and is a good backup QSL system. Many operators upload to both simultaneously. There is no reason not to use both — the overhead is minimal.

DXCC, WAZ and award tracking

CQRLog tracks your progress toward major amateur radio awards automatically based on your log contents and QSL confirmations.

DXCC tracking

Go to Awards → DXCC to see your DXCC breakdown by band and mode. The display shows:

• Worked — number of DXCC entities you have made at least one contact with
• Confirmed — confirmed via LoTW, eQSL, or paper QSL
• Needed — entities you have not yet worked on each band/mode

Click any entity to see all contacts with that country. The Needed list at the bottom shows which countries to prioritize for new DXCC or new band/mode slots.

WAZ (Worked All Zones) tracking

Go to Awards → WAZ to see your progress toward working all 40 CQ zones. WAZ requires confirmed contacts from all zones — CQRLog shows which zones you have worked and which are confirmed on each band.

WAS (Worked All States) tracking

Go to Awards → WAS for US state tracking. CQRLog resolves the state from callsign prefixes and shows your progress toward the 50-state award on each band and mode.

IOTA tracking

Enter IOTA reference numbers in the IOTA field when logging island contacts. CQRLog tracks your IOTA references and shows total island groups worked and confirmed.

Keeping the country database current

DXCC entity status changes occasionally — new entities are added (country splits, new administrations) and old ones are deleted. Keep your cty.dat file updated to ensure CQRLog correctly identifies new entities. Download the latest from country-files.com and update via Settings → Country Files → Update.

Contest logging in CQRLog

CQRLog supports contest logging with serial number tracking, exchange handling, and Cabrillo export for log submission.

Setting up a contest log

1. Create a new log via File → New Log
2. Give it a descriptive name — "CQWW-SSB-2026" for example
3. In the log settings enable contest mode and select the contest type
4. CQRLog automatically assigns and tracks serial numbers for sent exchange

Supported contests

CQRLog includes exchange templates for major contests including CQWW SSB and CW, CQ WPX, ARRL DX, ARRL 10m, WAE, and others. Select the contest type when creating the log and CQRLog configures the exchange fields appropriately.

Cabrillo export for submission

After the contest export your log in Cabrillo format for submission: File → Export → Cabrillo. The exported file is ready for submission to the contest organizer. Review it before submitting to verify callsigns and exchanges are correct.

After the contest — importing to main log

After submitting the contest log, import the contacts into your main log via File → Import → ADIF to keep your overall log complete for award tracking. CQRLog's duplicate detection ensures contacts already in your main log are not duplicated.

Integration with Fldigi and WSJT-X

Fldigi integration

CQRLog can receive completed contacts from Fldigi in real time via Fldigi's built-in logging interface:

1. In CQRLog go to Settings → TRX Control → Fldigi
2. Enable the Fldigi connection on port 7362
3. When you save a contact in Fldigi it appears in CQRLog automatically

With rig control shared via Flrig, both Fldigi and CQRLog read frequency and mode from the same rig control daemon — ensuring your log entries have accurate frequency information without manual entry.

WSJT-X integration

CQRLog can monitor WSJT-X's log file and import new contacts as they are logged:

1. In CQRLog go to Settings → Log → WSJT-X log file
2. Set the path to ~/.local/share/WSJT-X/wsjtx_log.adi
3. CQRLog checks for new contacts every few seconds and imports them automatically

Alternatively use WSJT-X's UDP logging interface — enable it under File → Settings → Reporting → UDP Server in WSJT-X and point CQRLog at the same UDP port for real-time contact delivery.

JTDX integration

JTDX integration works the same way as WSJT-X. Set the log file path to ~/.local/share/JTDX/jtdx_log.adi in CQRLog's settings. If you use both WSJT-X and JTDX, point CQRLog at whichever one you are currently using — or set up two separate monitor paths.

Backup and restore

Your CQRLog database is irreplaceable — back it up regularly. A lost log cannot be recovered from LoTW or eQSL alone.

Built-in backup

Use File → Backup to create a compressed archive of your entire CQRLog database. Store this file in at least two locations — local and cloud storage or an external drive.

Manual database backup

Automated backup with cron

Restore from backup

Troubleshooting common problems

CQRLog won't start — database error

• CQRLog requires MariaDB to start — check if it is running: sudo systemctl status mariadb
• Start MariaDB if stopped: sudo systemctl start mariadb
• Check disk space — MariaDB fails if the filesystem is full: df -h ~
• Check CQRLog log file for specific error: cat ~/.config/cqrlog/cqrlog.log
• Delete the lock file if CQRLog crashed: rm ~/.config/cqrlog/database/mysql.sock.lock

Rig control not working

• Check dialout group: groups | grep dialout
• Verify serial port exists: ls /dev/ttyUSB*
• Check baud rate matches radio's CAT baud rate exactly
• If using rigctld, verify it is running: ps aux | grep rigctld
• Test Hamlib independently: rigctl -m [model] -r /dev/ttyUSB0 -s [baud] f
• Check that Fldigi or another application is not already holding the serial port

DX cluster connection fails

• Test the connection manually: telnet dxspider.co.uk 7300
• Check firewall rules — some networks block outgoing telnet connections
• Try a different cluster node from the table above
• Verify your callsign is entered correctly in DX cluster settings

LoTW upload fails

• Verify TQSL is installed: which tqsl
• Check TQSL path in CQRLog Settings → LoTW
• Test TQSL from terminal: tqsl — it should open without errors
• Verify your certificate is not expired — open TQSL and check certificate validity
• Check internet connectivity and that LoTW servers are not down

Callbook lookup not working

• Check your QRZ or HamQTH credentials in Settings → Callbook
• QRZ.com XML requires a paid subscription for full data — the free account has limited access
• Check internet connectivity
• Try HamQTH as a free alternative to QRZ XML

DXCC counts seem wrong

• Update the cty.dat file — an outdated country file may misidentify entities
• Check that LoTW confirmations have been downloaded recently via Awards → LoTW → Download New Confirmations
• Verify your log entries have correct callsigns — a typo can cause misidentification
• Run Awards → DXCC → Rebuild Statistics to recalculate from scratch

Frequently asked questions

Related tools