CQRLOG

CQRLOG

Advanced ham radio logger for Linux and macOS

Version 3.3.0, released 2026-10-25 · Download · What’s new

CQRLOG main window with New QSO, band map, grayline and DX cluster

What is CQRLOG

CQRLOG is a free, open-source logging program for radio amateurs, meant for everyday HF logging of CW and SSB contacts. While you work a station, it fills in what it knows: country, zones, previous contacts, QSL status and callbook data.

  • Rig and rotator control through hamlib
  • DX cluster, RBN and graphical band maps
  • LoTW, eQSL, ClubLog, HamQTH and HRDLog
  • DXCC, WAZ, ITU and IOTA statistics
  • MariaDB/MySQL database, ADIF import and export

Features

The station, not the computer

Type the callsign and CQRLOG shows the country, CQ and ITU zones, beam heading, your previous contacts with the station and whether it is a new country, band or mode for you. Name, QTH and locator come from HamQTH, QRZ.com or QRZCQ. Super Check Partial suggests calls while you type, and the whole QSO can be logged from the keyboard.

Country resolution you can rely on

DXCC, zones and IOTA are resolved with the country tables maintained by OK1RR, including dated exceptions for individual calls and expeditions. The tables update from inside the program, so old contacts keep the country that was valid at the time.

Radio, rotator and keyer

Frequency and mode are taken from the radio through hamlib, and clicking a spot tunes the radio. The rotator control gets the beam heading of the station you are working. CW goes out from memory keys through WinKeyer, K3NG, cwdaemon or hamlib, and the voice keyer plays recorded messages for SSB.

See who is on the band

DX cluster and the Reverse Beacon Network feed graphical band maps: as many windows as you like, each following the VFO or fixed on a band, with its own filter. Stations you still need stand out, and club membership can be shown next to the call. The grayline map shows where the spots come from.

Digital modes

In remote mode, contacts made in WSJT-X or fldigi are logged automatically, with the same country and QSL information as any other QSO. The WSJT-X monitor highlights CQ calls from stations you have not worked yet.

QSL without the paperwork

LoTW export is signed and uploaded in one step, and confirmations are downloaded back into the log. eQSL works both ways too. ClubLog, HamQTH and HRDLog can receive every QSO right after you save it. For paper QSLs there is a QSL manager database and label export.

Awards and statistics

DXCC, WAZ, ITU, IOTA, worked grids, big squares, DOK and US counties, by band and mode, worked and confirmed. Club membership statistics cover more than a hundred clubs, from FOC to EPC.

Your data stays yours

The log is a MariaDB/MySQL database. CQRLOG can run its own database server in your home directory, or use a server on your network so several computers share one log. Keep as many separate logs as you need, import and export ADIF, export Cabrillo, EDI and SOTA, and let CQRLOG back up the log every time you close it.

News

CQRLOG 3.3.0 2026-10-25

New

  • RBN: one shared connection for the whole program; the RBN monitor, the band maps and the Grayline all read from it, so closing the monitor window no longer disconnects
  • RBN: new RBN control window (New QSO -> Window) with a connection status dot, server preset, connect/disconnect, the global filter and a switch for sending spots to the band map; Preferences/RBN support gets 'Connect to RBN after program starts'
  • RBN: servers are kept as presets in the common database and managed in a small dialog; on the first start they are filled from the old RBN monitor and RBN settings
  • Graphical band map: several windows at once, each following the VFO (Auto) or showing a fixed band, with its own span, position and filter; open windows are restored after a restart; Window -> Band map and the map's M -> Band menu list every enabled band
  • Graphical band map: each window has its own filter with one rule for worked stations (the global band map rule, its own hours or date/time, or none), LoTW/eQSL and current mode only; the rule in force is shown in the status bar
  • Band maps: club membership of the spotted station can be shown after the callsign, e.g. 'OK1ABC (EPC, SOTA)'; Preferences/Bandmap, off by default
  • Band maps: whether a spotted station was already worked is checked in a background thread with a shared cache, so many spots and a database on another computer no longer freeze the program
  • Grayline: 'Link to main RBN connection' gets every spot whether the RBN monitor is open or not; its own 'Connect to RBN' can use any RBN preset; the spotter list grows instead of reporting 'list is full'
  • Network outages: database connections are checked every 5 minutes and reopened when they died; RBN and DX cluster detect a connection that went silent and reconnect; DX cluster reconnects by itself while it should be connected
  • LoTW: export can sign and upload in one step; a signed file whose upload failed is kept and offered for upload again; the number of uploaded QSOs is shown
  • HamQTH: callbook lookups, DX cluster lookups and log upload use the new HamQTH API v2
  • HamQTH: CQRLOG can report the rig frequency and mode to HamQTH, which shows you as on the air; Preferences/Online log, off by default
  • Emoji and other 4-byte characters from callbooks are stored correctly: the database connection uses utf8mb4 and the tables are converted on the first start (on a large log it can take a while)
  • New QSO: the Window menu is grouped with separators
  • RPM package for Fedora 44 (Qt6)
  • New website cqrlog.ok2cqr.com (cqrlog.com is used by the CQRLOGImproved fork now); the About window, help, export headers and packages point to it, bug reports go to GitHub Issues

Fixed

  • Grayline: the shadow was 45 to 105 minutes off depending on the season; the Sun position is now computed properly, the old time offset in Preferences is cleared once; with 'get UTC from computer time' off the map used local time without the offset
  • TRX control: with the rig switched off, polls piled up in rigctld and commands waited behind them after the rig came back on
  • TRX control: the frequency could not be entered manually after the radio was switched off during operation
  • The log list was empty after a database upgrade and File -> Open failed with 'index out of bounds'
  • An error in QSL via lookup or in the IOTA import left a transaction open and every later use failed with 'transaction already active'
  • WinKeyer honours 'Pot speed' on macOS, in flatpak and snap
  • Locator with a lowercase subsquare gave wrong coordinates
  • MacOS: system bell after every Esc, PgUp/PgDn CW speed change beeped, shortcuts reached the focused edit (beep, Option typed a character)
  • MacOS: callbook lookup is on Cmd+L, F11 is Show Desktop there
  • MacOS: TRX control shows the active band, mode and VFO in bold, the coloured caption was not visible
CQRLOG 3.2.1 2026-10-06

Fixed

  • Debian package: files were installed under /share and /bin instead of /usr, so the installation failed in postinst with 'cqrlog-apparmor-fix: not found'
  • Debian package: on Ubuntu 26.04 (MariaDB 11) the database server could not start with 'Permission denied' on ~/.config/cqrlog/database; the AppArmor fix now also updates the mariadbd profile and the changes are removed on uninstall
CQRLOG 3.2.0 2026-09-25

New

  • RBN monitor reconnects by itself after a lost connection or a socket error (5 s, doubling up to 300 s); never after a manual Disconnect and never to another server
  • RBN monitor keeps up with contest traffic: the worker no longer sleeps 100 ms after every spot, and the queue between the socket and the worker is limited to 500 lines (the oldest line is dropped, losses are reported in cqrlog-debug.log) instead of growing without a limit
  • Load club data and loading ZIP codes are much faster (500 rows per INSERT) and show progress
  • Big squares and County statistics are computed with one grouped query per page instead of a query per square/county
  • Checking whether a callsign was already worked (RBN and band map filters) is faster

Fixed

  • RBN monitor and Grayline: a spot line split between two network reads was lost; VHF spots without a space after the colon (DX de X-#:144433.50) were not recognized; long callsigns were truncated; the frequency depended on the locale decimal separator
  • RBN filter: 'Ignore worked in last XX hours' computed a wrong limit, and both it and 'Ignore worked after' compared the QSO time (UTC) with local time; the same applied to the band map filter
  • RBN monitor: closing the window only closed the socket and left the worker running behind the hidden window; reconnecting leaked the previous worker
  • Switching logs: spots in the RBN monitor, DX cluster and band maps were coloured and filtered against the previous log, they are now cleared; DX cluster stayed showing 'Disconnect' although it was no longer connected
  • Grayline: 'Link to RBN monitor' switched itself off on the second opening of the window and saved it as off
  • Configuration storage: band map sections were stored twice and CW / fldigi sections were glued to the next section name, so the following sections were not stored
  • Load club data: an error during the import was followed by a commit of the rolled back batch
  • Search: a text with the ' character broke the SQL query
  • Debug output no longer prints LoTW and eQSL passwords
  • Dark mode: default colours for new country/band/mode, zones, IOTA, band map and several labels were black and unreadable, they follow the system text colour now; the TRX control frequency label is no longer fixed blue
  • Switching between light and dark theme while CQRLOG runs left the grids with the green bar colour of the previous theme
  • Qt6 layout: Preferences, New QSO (comment to callsign, DXCC and QSL via buttons), graphical band map and statistics windows (DOK, WAZ/ITU, County, Big squares)
  • MacOS: collapsed comboboxes in TRX control, Cabrillo export and Worked grids
  • Flatpak: HTTPS (LoTW, callbooks) did not work because only the versioned libssl.so.3 / libssl.so.1.1 exist in the runtime
CQRLOG 3.1.0 2026-09-12

New

  • Check for a new version: after start CQRLOG asks GitHub for the latest release and, when a newer one exists, shows a dialog with the release notes, a button to open the release page and 'Don't show this version again'; can be switched off in Preferences/Program, manual check in Help -> Check for new version
  • New DXCC resolution engine: the prefix parser was rewritten with a test suite and verified against the old one over a real log and every validity date in the tables - zero differences; the old engine silently stopped resolving anything once the tables outgrew its fixed capacity, the new one has no such limit
  • Country files updated: DXCC tables and exceptions, LoTW and eQSL user lists, MASTER.SCP
  • Country files (DXCC tables, LoTW and eQSL user lists, MASTER.SCP) are downloaded from GitHub (ok2cqr.github.io/cqrlog-cnty-files) instead of ok2cqr.com; the QSL manager database still comes from ok2cqr.com

Fixed

  • Argentine callsigns with /F, /G, /I, /K, /M and /P suffixes now resolve to the right province
  • Rebuild DXCC statistics wrote every correction into the QSO selected in the QSO list instead of the QSO being checked
  • Database update from the callbook used the main database connection from a background thread; it now runs on a connection of its own, and cancelling leaves the QSO it was about to update untouched so the next run resumes exactly there
  • RBN monitor: spots sent to the band map had no LoTW/eQSL background colour
  • Load club data: the window looked frozen during the import, it now shows progress
  • New QSO: a stray column ('??' or an empty 'Title') could appear in the previous QSO grid and, once saved to the config, came back on every start
  • Export: a QSO with a profile number one above the highest existing QTH profile read past the profile list
  • Windows no longer interfere through the shared database cursors: saving a note or a call alert, DXCC lookups and the profile list used to close or roll back what another window had open (QTH profiles grid, notes grid, locator and county statistics)
  • MacOS: opening attachments, links and the mysql.err log in an external application did not work
  • HamQTH, HRDLog, cqrlog.com and the other web addresses use https
  • Linux: the database server is also found under its MariaDB name, mariadbd in /usr/sbin, /usr/libexec or /usr/bin, on systems that no longer ship the mysqld symlinks

All releases on GitHub · Full changelog (including changes for developers)

Download

Version 3.3.0, released 2026-10-25. Requires MariaDB or MySQL, hamlib and OpenSSL.

Ubuntu 26.04+ – .deb, Qt6 Download
Fedora 44 – .rpm, Qt6 Download
Flatpak – any Linux distribution Download
Snap – any Linux distribution also arm64 Download
AppImage – older Linux distributions, Qt5 Download
macOS – signed and notarized .dmg, Apple Silicon Download

Source code (GPL v2): github.com/ok2cqr/cqrlog

FAQ

Is this the same program as cqrlog.com?

No. This is the original CQRLOG by Petr Hlozek, OK2CQR. cqrlog.com is now used by CQRLOGImproved by Saku, OH1KH, a separate fork with its own releases and support. It's better when you mostly use digital modes.

Which package should I use on Linux?

On Ubuntu 26.04+ and Fedora 44 use the native package. On other distributions use Flatpak or Snap. The AppImage is a Qt5 build for older distributions and includes hamlib and MariaDB.

How do I install the Flatpak or the Snap?

Both are files from the release, not from an app store. Flatpak: flatpak install --user cqrlog.flatpak; when you update, add --reinstall, otherwise the old version stays installed. Snap: sudo snap install --dangerous cqrlog_*.snap, then sudo snap connect cqrlog:raw-usb for a serial rig.

Neither of them starts its own database server. Install MariaDB on the computer or use one on your network, and untick “Save log data to local machine” in the database connection window.

What do I need on macOS?

A Mac with Apple Silicon and a MariaDB server, for example from Homebrew: brew install mariadb and brew services start mariadb. hamlib and the other libraries are inside the app.

CQRLOG says that MySQL could not be started

With “Save log data to local machine” CQRLOG runs its own MariaDB server with the data in ~/.config/cqrlog/database. The server program must be installed (mariadb-server on Linux, brew install mariadb on macOS), but the system database service does not have to run.

The reason is in ~/.config/cqrlog/database/mysql.err; the error window has a button that opens it. Often it is a database server left running after CQRLOG crashed, which ends with a restart of the computer, or “Permission denied” from AppArmor on Ubuntu, which the CQRLOG .deb package sets up. If that does not help, open a GitHub issue and attach the last 20 lines of mysql.err.

Will an upgrade keep my log?

Yes. The database is upgraded on the first start of a new version; on a large log some upgrades take a while. Turn on the automatic backup in Preferences → Exit / Auto backup, so a copy of the log is saved every time you close CQRLOG.

Can several computers use one log?

Yes. Run MariaDB on one machine in your network and connect to it from each computer. CQRLOG reconnects by itself when the network or the server comes back after an outage.

How do I move my log from another program?

Export it as ADIF and import it in the QSO list window with File → Import → ADIF. Country, zones and statistics are computed during the import.

Does it work with FT8 and other digital modes?

Yes, through WSJT-X and fldigi. Turn on the remote mode in the New QSO window and the contacts you make there are logged automatically.

Where is the documentation?

The built-in help covers setup, the database, radio control and every window. Open it from Help in the menu.

Contact

Bugs and feature requests: GitHub Issues

Email: petr@ok2cqr.com (spare-time project, replies may take a while)