CMELOG Introduction Tutorial
Updated November 19, 2025 , aligned with CMELOG v1.0.

Why use CMELOG? There is a lot of Ham Radio logging software out there. However, several of these software have hard-to-navigate graphical user interfaces, cluttered with fields seldom used - making it hard to quickly find what you really need, preventing fast operation.

But CMELOG is different - it is command driven, and available on Linux, Windows and Raspberry PI.

Some main benefits of CMELOG:

• The command-driven approach makes it possible to work very quick and intuitive, with all information literally speaking at your fingertips.
• Can view all (or any subset of) your QSOs on a world map, with zoom capability.
• Very flexible way of searching the log - commands can be combined into “filter chains” by one command pipelining data to the next. No need to predefine database commands, it’s just to type your search condition right away using intuitive commands, including any ADIF log field values you might need to match.
• Tells if a callsign has been worked before, when and on what bands. If a callsign is not worked before, the name of the DXCC is given from the callsign, or from just a prefix. Clear indication if a DXCC has never been worked before (ATNO).

• DXCC statistics - shows for a given QSO selection what DXCCs that have been worked, and how many times. Also shows for each DXCC if it has been confirmed in LOTW, QRZ or eQSL.
• CMELOG is designed to either being supplemental to any other logging software or online service, OR acting as a main log. No need to stop using your current logging software as your main log (unless you want to make a full switch to CMELOG). Using CMELOG as a ‘front end’ for adding QSOs and searching your log, and then export to your main log at recurring occasions can often be a convenient solution.
• Can receive QSO data from WSJT-X directly in real time, automatically logging the QSOs when they are made.
• QSL notifications for LOTW, QRZ and eQSL
• Supports multiple callsigns and QTHs by separate logbooks.
• Flexible functions for export, import and merge of QSOs and logbooks.
• All QSOs are all the time safely kept on disc, preventing data loss in case of any unexpected interruptions.
• Available for Linux, Raspberry PI and Windows.
• Ideal for portable use - can host your full log on a Raspberry PI (with screen attached), or on a Windows or Linux laptop. Only the map function is dependent on internet connection, all other functionality is available offline as well. After the portable operation, QSOs made can be easily uploaded to an online service or any other logging software when back in the shack at your home QTH.

CMELOG working principles

CMELOG used supplementary to another log program

CMELOG is designed to cooperate with other logging tools or services. This means that there is no need t stop using your current logging program that can still be your main log - CMELOG can act as a front-end for enhanced search capabilities, map functions and fast QSO entries, a combination giving the best of both.

To support the use case of being supplementary to another logging tool or online service, CMELOG internally handles two logs for each logbook - one called the Main log, the other called the Delta log. QSOs in the Main log are marked with green color, QSOs in Delta log are marked with white color. Imported logs from other tools and services are stored in the main log. QSOs added from CMELOG are stored in the Delta log, which later can be uploaded to an online service, or imported into some other logging software. After that has been done, the CMELOG command merge is used to move the added QSOs from the Delta log into the Main log and empty the Delta log.

The next QSO entered in CMELOG will start a new Delta log, preparing for the next upload/data transfer and merge cycle. Note that handling of the Main and Delta log is internal to CMELOG and concealed, making all QSOs from both logs always available seamlessly in all operations like searches etc. But the principle is important for understanding the process of uploading or transferring new QSOs logged in CMELOG to other tools.

CMELOG used as your main logging tool

If you want to use CMELOG as your main logging tool, and maybe just export QSOs from time to time (maybe after contests or portable operations), than you do not have to care about Main and Delta logs, nor the need to merge them. Just remember to backup your log files from time to time in case of disc or computer failure (logbooks are stored in the log directory under the CMELOG installation directory).

Multiple logbooks

CMELOG supports multiple logbooks, so there can be one for each callsign or QTH used, or specific events like contests or portable field operations. Each logbook has it’s own Main and Delta log, making all operations work the same. Switching from one logbook to another can be done at any time using the logbook open command without any risk of loosing QSO data. 

How to install and get started

First, install CMELOG:

• For Windows, run the cmelog.msi installer file. During installation, the Windows Defender firewall (or other antivirus software) might ask about allowing network access, that is for opening an UDP/IP port to CMELOG for receiving QSOs from WSJT-X. On Windows 11, there can be a question about allowing POSIX threads - that is for the same reason, so answer yes (CMELOG starts a thread in the background listening on an UDP socket for QSOs coming from WSJT-X ).
  
  After installation, start CMELOG by the Windows start menu or the desktop shortcut.
  
  Hint for Windows 11: CMELOG runs in a Windows command window, and it might appear in a little bit more logical way if the following setting is changed:
  Windows settings->System->Advanced->Terminal set to “Windows Console Host”. This disables multiple tabs in consoles (unless you need this for other purposes, in which case this settings should not be changed).
• For Linux and Raspberry PI, move the cmelog.tar.gz file to any directory of choice and then unpack it: tar -xvf cmelog.tar.gz. Then run the application as ./cmelog.

When starting CMELOG for the very first time, there is a need to enter some parameters that will be inserted into each logged QSO and written to exported ADIF files. Starting CMELOG the first time will look like this example:

Welcome to CMELOG!
This is the first time CMELOG is installed on this computer.
Enter your station callsign: SA6CME
Enter your gridsquare: JO57xq
Enter your name: Lars Linderos
Enter your city: Gothenburg

This only happens at the very first installation. Any later installations of new CMELOG versions will preserve both settings and logbooks (on some computers it might be needed to first uninstall the old version of CMELOG in Windows settings before the new version can be installed. Also in that case, settings and logs are preserved).

Then, if you want to start adding new QSOs right away, just do so by using the qso command, like ”qso sm6nza 80m cw 599 599” (or just “qso” followed by return for prompted input if you prefer that).

If you want to search your existing log using the powerful and flexible possibilities of CMELOG, and possibly put your QSOs on the world map, the first thing to do is to import your log from an ADIF file exported from your current logging tool. After that, any CMELOG commands can be used, like the map and dxcc commands used as examples here:

import adif my_logfile.adi
all map
band 20m map
all dxcc

Next thing is to explore what CMELOG commands that are available by launching help information by using the commands

• help          - command Reference guide, with examples
• ?                 - short command summary
• tutorial   - shows this introduction page

Examples of some commands to search your log (just to give some ideas - any combinations, in any order,  are possible):

call 5k0ua                                                            - list QSOs for callsign, or print dxcc name if no QSO
call  t33                                                                  - print name of DXCC with prefix t33
country japan band 20m mode ssb        - list SSB QSOs with Japan on 20m band 

comment nice print comment                 - lists and print QSOs with comments containing "nice"
year 2023 band 10m print name,qth    - list QSOs on 10m during 2023, print name and qth
band 30m not cont eu                                   - list all DX QSOs on 30m band (i.e. outside Europe)
year 2024 dxcc                                                  - list DXCCs worked during 2024

Known issues and limitations
Known bugs

• KB-1001: Bug [All platforms] edit command keeping original QSO.
  The edit command can fail to delete the original QSO, keeping both the original and the modified version of the QSO in the log. Workaround is to manually delete the original QSO using the delete command. This bug will be corrected in the upcoming v1.1 release.

Limitations

• KI-1003: Limitation [All platforms] Currently, discarding of QSO duplicates in adif import is not yet implemented.
• KI-1004: Limitation [All platforms] In map view, if several QSOs are in the same grid, the last QSO overwrites and shadows the others. In a coming release, multiple QSOs will be shown in the popup box when clicking the flag.
• KI-1005: Limitation [All platforms] The map function only display log entries having the ADIF gridsquare field defined.
• KI-1006: Limitation [All platforms] QSL statistics for LOTW and/or eQSL only works for log entries having the corresponding ADIF fields lotw_qsl_rcvd and/or eqsl_qsl_rcvd defined.

Platforms supported

CMELOG has currently been successfully tested on the following platforms:

• Ubuntu Linux v22.04
• Raspberry PI 5 model B, PI OS v6.12.20
• Windows 10 IoT Enterprise LTSC version 21H2
• Windows 10 Home version 19045.5796
• Windows 11 Home, version 25H2 26200.7171

CMELOG is likely to work on other Windows versions, Linux distributions and Raspberry PI versions as well, but that has not been tested.