HamlogEx User Manual

Version: HamlogEx 0.12.1 (日本語版)

Contents

1. Overview
2. Getting started
3. Main window
4. How to use
5. Feature list
6. Keyboard shortcuts
7. Appendix

1. Overview

1.1 What is HamlogEx?

HamlogEx is a Windows application for keeping an amateur radio station log. It works much like Turbo HAMLOG, the logging program widely used in Japan, and it can import Turbo HAMLOG data (CSV and ADIF) so you can carry on with your existing log.

Main features:

• Entry, search and history in one window: the QSO entry form, filters, the QSO list, the radio frequency and the past QSOs with the station are all shown in a single window.
• Radio control: ICOM, YAESU, KENWOOD and JRC radios and Hamlib (rigctld) are supported. The frequency and mode are filled in automatically. Two radios can be connected at the same time.
• QSL work: QSL card and label printing (with an on-screen layout editor), sent/received tracking, JARL bureau sorting order, and E-Mail QSL (hQSL method).
• Awards and DX: worked/confirmed tracking for DXCC, WAS, JCC, JCG, WAKU, cities/guns/wards, POTA, SOTA, WWFF, IOTA and more; country and zone lookup with cty.dat; NEW ONE detection; DX cluster; callbook lookup (QRZ.com, HamQTH).
• Electronic QSL and online logbooks: upload to eQSL.cc, LoTW, Club Log and QRZ.com, and download eQSL and LoTW confirmations.
• Contests and portable operation: contest mode (exchange, serial numbers, dupe check, Cabrillo / JARL e-log export), CW keyer and CQ machine, rotator control, QSO counter, saving each QSO to several logs, and network sharing (multi-op).
• Digital modes: QSOs from WSJT-X / JTDX are logged automatically.
• Data maintenance: backup and restore, QSO data checks, and bulk text replace.
• Modern UI in two languages: light, dark or Windows-matched theme. English and Japanese, switched automatically to match Windows.

1.2 Relationship to Turbo HAMLOG

HamlogEx is independent software and is not related to Turbo HAMLOG by JG1MOU. It takes Turbo HAMLOG's features as a reference and redesigns the user interface. Turbo HAMLOG's log file (Hamlog.hdb) cannot be opened directly because its format is not published. Export your log from Turbo HAMLOG as CSV or ADIF and import it (see 2.4 Migrating from Turbo HAMLOG).

1.3 System requirements

1.4 How data is stored

• QSOs are stored in a log file (extension .hxlog, an SQLite database). You can have as many log files as you like (per callsign, per portable operation, and so on).
• Times are stored in UTC internally and shown/entered in the time base you choose (JST / UTC / Windows local time).
• Settings are saved in %APPDATA%\HamlogEx\settings.json. See 7.4 Where data is stored for all locations.

2. Getting started

2.1 Starting HamlogEx

Run HamlogEx.exe. On the first start, Documents\HamlogEx\MyLog.hxlog is created and the JCC/JCG area code table (about 2,600 codes) is loaded into it automatically. From then on, the log file you used last is opened.

To build from source, open HamlogEx.sln in Visual Studio 2026 (with the .NET desktop development workload and the .NET 10 SDK), set HamlogEx.App as the startup project and run it.

2.2 First settings

Open Tools > Settings and set the following:

2.3 Getting cty.dat

cty.dat is used to determine the country (DXCC entity), zones and prefix. Download it with Tools > Update cty.dat (country file). If you have the cty.dat that comes with Turbo HAMLOG (for example C:\Hamlog\cty.dat), it is found and used automatically. To add countries and zones to QSOs you have already imported, run Tools > Recalculate DXCC / zones for all QSOs.

2.4 Migrating from Turbo HAMLOG

1. In Turbo HAMLOG, export your QSOs in CSV (or ADIF) format.
2. In HamlogEx, choose File > Import (Turbo HAMLOG CSV / ADIF) and select the exported file.
3. Check the number of QSOs to import and click Yes.

• The CSV encoding (Shift_JIS / UTF-8) is detected automatically. The column order is the Turbo HAMLOG format (Call, Date, Time, His, My, Freq, Mode, Code, G・L, QSL, Name, QTH, Remarks1, Remarks2).
• A trailing J (JST) / U (UTC) on the time is recognised.
• If the 2nd/3rd character of the QSL field is a mark other than * (for example J#E), that character is imported as it is and can be used in the list, exports and print conditions.
• Turbo HAMLOG QSL card definitions can be converted with File > Import Turbo HAMLOG QSL definition in the print definition editor (see 4.8.5).
• Rig/Ant settings (RIGANT.DAT) can be loaded with Import... under the Rig/Ant table on the QSL printing tab of the settings.

3. Main window

The main window has the following parts:

4. How to use

4.1 Logging a QSO

4.1.1 Basic flow

1. Type the other station's callsign in the Call field. The date and time at the moment you type the first character are filled in automatically (when Set the current date and time when you start typing a callsign on the QSO entry tab of the settings, or Set time automatically in the entry form, is on). When it is off, enter the date and time yourself. If you log the QSO with them empty, the time of logging is used.
2. If you have worked the station before, name, QTH, code and grid are filled in from the previous QSOs, and the list appears in QSO history on the right.
3. If a radio is connected, frequency and mode are filled in automatically. Otherwise type them (frequency in MHz, such as 7 or 7.074).
4. Enter His (report sent), My (report received), Code, G・L, QSL, Name, QTH and Remarks1/2.
5. Press Enter to move to the next field; pressing Enter in the last field (Remarks2) logs the QSO. Ctrl+S or Ctrl+Enter logs it at any time.

The order, width and visibility of the fields can be changed on the Entry fields tab of the settings.

4.1.2 Entry aids

• DUPE: shown when a QSO with the same station, band and mode already exists. In contest mode, dupes within the contest are shown in the Contest field.
• Callbook: with QRZ.com or HamQTH set up on the Callbook / cluster tab, DX callsigns are looked up as you enter them and empty Name, QTH and G・L fields are filled (4.24).
• DX status: the entity, continent, zones and WPX prefix are shown from the callsign, together with NEW ONE (entity not yet worked), NEW BAND, NEW MODE and so on.
• Distance and bearing: the other station's position is taken from the area code table's latitude/longitude, the grid locator, or the entity position, in that order, and distance and bearing (arrow) are shown. Right-click the Code, G・L or QTH field and choose Open in Google Maps.
• Licence data: when enabled on the Entry assist tab, the registered location of Japanese stations is looked up through the Web-API of the Japanese Ministry of Internal Affairs and Communications (MIC) Radio Use Portal and shown. It is put into QTH if QTH is empty. This service is based on information obtained through the Web-API of the MIC Radio Use Portal, but its content is not guaranteed by the MIC.
• Automatic Japanese input switching: for the Name, QTH and Remarks fields you can choose whether the Japanese IME is turned on (on the Entry assist tab). Fields such as Call and Freq always use half-width alphanumerics.
• User lists: register lists such as club rosters on the Entry assist tab, and when the station being entered is in a list it is shown like [FISTS] #1234 Taro (hover for details). A list is a text/CSV file with the callsign in the first column and the station's information in the rest (tab, comma or space separated; lines starting with # or ; are ignored; portable suffixes are ignored when matching). Lists can also be used in print and replace conditions as UserList=FISTS, and on QSL cards as {UserList} and {UserInfo:FISTS}.

4.1.3 Watch data

For a station you heard but did not work, press Ctrl+W (Edit > Record as watch data) with the data entered to save it as watch data. When you later type that callsign, the watch data is shown at the lower right; double-click it to copy it into the entry form. The full list is under View > Watch data. The maximum number of entries (2,000 to 10,000) is set on the Entry assist tab.

4.1.4 Default RST and QSL field

• RST by mode: on the QSO entry tab, set a default RST for each mode (standard: CW/RTTY = 599, SSB/FM = 59, FT8 = -10). When the mode changes, His and My are replaced. Values you typed yourself are kept. Modes that are not in the table use the default RST.
• QSL field: for the QSL route of a new QSO, choose Default above (always), Same as the last logged QSO or Same as the previous QSO with the station.

4.2 QSO list, search and editing

• Filter: type a callsign, keyword (name, QTH, remarks, etc.), band, mode, QSL status or date range (from/to) above the list, and the list is filtered immediately. Ctrl+F moves to the keyword field, and View > Clear filter shows everything again.
• Edit: double-click a row (or press Enter or Ctrl+E) to open the edit window. QSL mark characters other than * set in Turbo HAMLOG are kept when you edit. If you do not change the date, time or frequency fields, the original values are kept (the seconds of QSOs from WSJT-X and the frequency of band-only QSOs do not change).
• Delete: select rows and press Del. Several rows can be deleted at once.
• Logging, deleting or editing QSOs and changing QSL received marks immediately re-evaluates the "new" indications in the entry form, the DX cluster and the digital mode window.
• QSL status: select rows and choose QSL > Mark as sent / Mark as received / Clear sent/received.
• Copy: select rows and press Ctrl+C (or right-click > Copy) to copy them as tab-separated text with headers, ready to paste into Excel.
• Columns: right-click a column header, or use the Log columns tab of the settings, to choose which columns are shown.
• Tune the radio: select a row and choose Tools > Tune radio to selected QSO to set the radio to that QSO's frequency and mode.
• Record number: the record number (position counted from the oldest QSO) of the selected QSO is shown in the status bar. View > Go to record number (Ctrl+G) finds a QSO by its number (4.20).

4.3 Log files

• Export covers only the QSOs shown by the current filter. Clear the filter to export everything.
• When importing, countries and zones are added automatically with cty.dat (this can be changed on the DX / awards tab).
• Open log only accepts existing files (so a mistyped name does not create an empty log). Create new logs with New log.
• How importing works:
• QSOs are added 500 at a time. Meanwhile QSOs from WSJT-X and network sharing are logged right away and the window keeps responding. Log from the entry form after the import has finished.
• If the import fails, everything imported so far is removed again and the reason is shown.
• Lines with an unreadable date or time (full-width digits, etc.) are reported as warnings and the import continues.
• The text encoding is detected automatically. Turbo HAMLOG CSV files containing only half-width katakana are read as Shift_JIS. Files with a BOM are read correctly even when an encoding is chosen.
• ADIF export:
• DV (D-STAR) is written as MODE=DIGITALVOICE SUBMODE=DSTAR, DMR as SUBMODE=DMR, and so on, following the ADIF specification (DV comes back as DV when imported).
• FREQ is written only when it agrees with BAND. Bands that are not in the band table keep their imported BAND and frequency.

4.4 Views and statistics

• View > Statistics: number of QSOs, stations and codes, a band × mode table, QSOs and QSLs received per code (JCC/JCG), and QSOs per call area (1 to 0 and DX). The per-area table can be printed and exported to Excel (.xlsx). The Charts tab shows QSOs and stations by year, month, band, mode, hour and continent as bar charts (4.26).
• QSO counter: the status bar shows the QSOs and stations since the counter was started. View > Reset QSO counter sets it back to zero.
• View > Awards: see 4.10 Awards.
• View > DX station / entity search: see 4.11 DX support.

4.5 Radio control

4.5.1 Setting up the connection

1. Open Tools > Settings > Radio and, on the radio 1 tab, turn on Use radio control.
2. Choose the model and set the connection type (serial / TCP), COM port, baud rate and so on. For ICOM radios you can also change the CI-V address.
3. Click Test connection to check that the frequency can be read.
4. Turn on Connect at startup to connect automatically when HamlogEx starts.

When connected, the frequency and mode are shown at the upper right and the entry form's frequency and mode follow the radio (Use radio frequency/mode in the entry form on the QSO entry tab).

• Data modes: when the radio is set to USB-D or another data mode from a spot or QSO, ICOM radios that support 1A 06 and the TS-590S/SG and TS-890S switch DATA on or off. The TS-990S sets the data mode with its mode command (OM).
• YAESU frequency digits: the FTDX3000, FTDX1200 and FTDX5000 use 8 digits; newer models such as the FTDX101 and FT-991A use 9.
• ICOM collisions: when a CI-V collision occurs (another device transmitted at the same time), the command is sent again, including PTT and CW.
• rigctld: when replies get out of step (unreadable frequency or 0 Hz), the values are read again.

4.5.2 Using two radios

Set up the second radio on the radio 2 tab of the Radio settings. The frequency and mode of both radios are shown at the upper right of the main window.

• To choose which radio feeds the entry form, click its display at the upper right, or press Ctrl+Shift+R (Tools > Switch radio for the entry (1 ⇔ 2)).
• If Radio for the entry is set to Automatic (last operated radio), HamlogEx switches to whichever radio's frequency or mode changed last.
• Connect radio on the command bar connects or disconnects all enabled radios together.

4.5.3 Adding radio models

• By configuration (no programming): click Open rigs.json in the settings to open %APPDATA%\HamlogEx\rigs.json and add the model (for models that use an existing protocol).
• A new protocol: put a DLL that implements IRadioDriverFactory from the HamlogEx.Radio library into the Plugins folder (for developers; see the README).

4.6 Digital modes (WSJT-X / JTDX)

1. In WSJT-X, under Settings > Reporting, set the UDP Server to 127.0.0.1, port 2237, and turn on Accept UDP requests.
2. Enable the integration on the Digital tab of the HamlogEx settings, then click Start in Tools > Digital modes (WSJT-X / JTDX). - By default only packets sent from this PC are accepted, so others on the network cannot log QSOs. When WSJT-X runs on another PC, turn on Accept from WSJT-X / JTDX on other PCs (only in a trusted network).

• When you log a QSO in WSJT-X, it is logged in HamlogEx automatically (you can also choose to send it to the entry form instead). The same QSO is never logged twice.
• Decoded stations are listed with colours for new entities, new bands and so on, and are also highlighted in WSJT-X. Double-click a row to call that station (double-clicking the scroll bar or header does not call).
• After logging, deleting or editing a QSO, receiving a QSL or switching logs, the "new" status of the rows shown and the highlights in WSJT-X are re-evaluated (a station that is still new on another band keeps its highlight).
• When several WSJT-X instances are running, each decode is judged with the frequency and mode of its own instance.
• Instead of UDP, ALL.TXT can be monitored. If you choose a JTDX monthly file (such as 202610_ALL.TXT), HamlogEx moves to the new month's file when the month changes. When you also use GridTracker or similar, set Forward UDP to port.
• With multicast, HamlogEx joins the group on loopback and on each network. If the same packet arrives twice, it is used once.
• Latest QSO from wsjtx.log... imports directly from the WSJT-X log.

4.7 QSL management and printing cards and labels

4.7.1 QSL manager

In QSL > QSL manager, switch between not sent, sent but not received, received and so on, and mark QSOs as sent or received in bulk.

• JARL sorting order sorts the QSOs in the order used for the JARL QSL bureau (call area → prefix → suffix, overseas stations last) and shows the number of cards per group.
• eQSL and LoTW confirmations can also be recorded. Uploading and downloading confirmations online is done with QSL > Online QSL / logbooks (4.23).
• The selected QSOs can be exported as ADIF / Turbo HAMLOG CSV for QSL printing software such as MMQSL.

4.7.2 Printing cards and labels

• QSL > Print QSL cards: prints the QSOs selected in the list (or, if none are selected, the QSOs whose QSL has not been sent) using the print definition. After printing you are asked whether to mark them as sent.
• QSL > Print QSL labels: prints on commercial label sheets (A4, 12 labels, etc.), in JARL sorting order.
• QSOs with the same station are combined on one card, up to the QSOs per card of the print definition.
• The paper is requested at the size of the print definition (A4, A5, A6, B5, Letter and Hagaki postcards also by name). If the printer chooses paper of a different size, you are asked before printing.
• If the print definition file set in the settings cannot be found or read, you are asked whether to continue with the standard definition (the same applies to E-Mail QSL images).
• Large images such as camera photos used as backgrounds are scaled down to 4,000 pixels wide when loaded.

4.7.3 Excluding stations from printing

When the filter option on the QSL printing tab is on, the following stations are not printed (Japanese stations only):

• Stations that are not in the transferable stations list (e.g. JARL members)
• Stations in the do-not-print stations list

Each list is a text/CSV file with one callsign per line. Turbo HAMLOG's JARL.mDAT is not read, because it is encrypted and its use by other software is not permitted.

4.7.4 QR codes on cards and matching received cards

HamlogEx can print a QSO-matching QR code on cards in the same format as Turbo HAMLOG (Ver5.40 and later), and match received cards by scanning their QR codes.

• Printing: in the print definition editor, choose Add > QR code. Its contents default to {QslQr}, which becomes !!MyCall_date_time_frequency_mode_ToCall in JST (for example !!JG1MOU_230904_0921_7.041_FT8_JA1QRZ). The station callsign is the QSO's station callsign or, if empty, your callsign from the settings; {QslQr:JA1ZZZ} sets it explicitly. Put a URL or other text instead to print an ordinary QR code. Set the size (mm) and the margin (0–4 cells).
• #QRCode and #QRCodeS in Turbo HAMLOG QSL definitions are imported too.
• Matching: open QSL > Match received QSL by QR code and scan with a USB QR reader (it types into the box and presses Enter). If you read the code with a camera app, copy the text and press F4.
• QSOs with the sending station, within ±15 minutes and on the same band, are listed. Select one and press Insert (or Mark as received).
• With Mark as received automatically when exactly one QSO matches, a scan is all it takes.
• Codes typed with = instead of _ (a reader set to a US layout) or in full-width characters are read too.

4.8 Print definition editor

Create and edit the layout of QSL cards, labels and E-Mail QSL images (print definition files, *.hxprint.json) on screen. Open it from QSL > Print definition editor, or with the Edit buttons in the QSL manager and the settings.

4.8.1 Basic operations

• Use Insert to add text, tables, lines, rectangles and images. Drag them on the card to move them and drag the square handle at the lower right to resize them.
• On the right, the Element tab sets text, font, colour, line width and the print condition; the Paper / layout tab sets the paper size, QSOs per card, label layout and background image.
• Grid and snap-to-grid (hold Alt to disable temporarily), arrow keys to move by 0.1 mm (5 mm with Shift), undo (Ctrl+Z) / redo (Ctrl+Y), duplicate (Ctrl+D) and z-order changes are available.
• With Sample on the toolbar you can change the sample QSO's band, mode, callsign and QSL status to see how the card will actually look. Turn on Show fields to show placeholders such as {Call} as they are.
• Overflowing elements, tables without columns, missing images, misspelt placeholders and invalid print conditions are checked automatically and listed.
• Save and use saves the definition and makes it the one used for printing cards / labels / E-Mail QSL.
• When you Save as into another folder, relative image paths are adjusted to the new location (the undo history is cleared then). If saving fails, nothing changes.

4.8.2 Placeholders

Write something like {Call} in a text element or a table column, and it is replaced with the QSO data when printing. A format can also be given, as in {Date:yy/MM/dd}. See 7.1 Placeholders for the full list.

4.8.3 Print conditions

Give an element a print condition, and it is printed only for QSOs that match (for example "TNX QSL" when the QSL has been received, and "PSE QSL" otherwise).

• Examples: Mode=CW|RTTY, Band=40m and not Rcvd, Freq>=50, Rmks1*="POTA", (Dx or Portable) and Name
• Duplicate with inverted condition creates a copy of the element with the opposite condition.
• When several QSOs are printed on one card, the first QSO is used to evaluate conditions. Elements whose condition does not match are shown faded in the editor.
• See 7.2 Condition syntax for details.

4.8.4 Printing Rig/Ant (radio and antenna)

In the Rig/Ant table on the QSL printing tab, register the radio, power, antenna, antenna height, remarks and location for each band (and mode). Print them with {Rig}, {Pwr}, {Ant} and so on in the print definition.

• The first row whose band and mode match is used, from the top (empty cells match anything).
• A row with an ID is used only for QSOs whose Remarks contain Rig=ID (for example Rig=Portable). Write Rig#3 to use the third row.
• If {Pwr} is empty, the QSO's transmit power is used.

4.8.5 Importing Turbo HAMLOG QSL definitions

File > Import Turbo HAMLOG QSL definition in the print definition editor converts a Turbo HAMLOG QSL definition file (Shift_JIS / UTF-8).

• Text, line, rectangle and image commands, font settings, #MaxCall, fields (!cp, !DY, !HR, !RG, etc.) and condition commands (? Rcv, ? Potbl, ? DXST, etc.) are converted.
• Programming commands such as data reading (#Read), jumps, loops and variables are not converted; lines that could not be converted are listed.
• Check the layout in the editor after conversion. Replacing multi-QSO lines with a table element is recommended.

4.9 E-Mail QSL (hQSL method)

1. On the E-Mail QSL tab of the settings, set up the sending (SMTP) and receiving (IMAP / POP3) servers and check them with Test connection. Passwords are encrypted per Windows user. - The Auto security setting always encrypts: TLS from the start on ports 465, 993 and 995, otherwise STARTTLS. If the server does not support STARTTLS, it does not connect. Use None (unencrypted) only inside a trusted network.
2. Register the other stations' e-mail addresses in the User list of QSL > E-Mail QSL (senders of received QSLs are added automatically).
3. On the Send tab, select the QSOs, check with Preview image, then click Send. The QSL image (JPEG) and QSO data are attached. Sending and receiving can be stopped with Cancel (QSOs sent before that are marked as sent).
4. On the Receive tab, click Receive. Incoming QSLs are matched with your log (same station, time difference, band), marked as E-Mail QSL received, and the images are saved. Unmatched ones can be linked with Match again. - Receiving first checks only the headers (subject, X-Mailer, attachment names, etc.) of the mails since the chosen date, and downloads only the mails that look like E-Mail QSLs (with POP3, the headers of the newest 3,000 mails are checked, and mails that may have attachments are also downloaded and checked).

• The image layout is edited in the print definition editor (E-Mail QSL image).
• Turbo HAMLOG's hQSL format is not published, so e-mails sent from Turbo HAMLOG are read on a best-effort basis from the subject and attachment names.

4.10 Awards

View > Awards shows worked (W) and confirmed (C) totals for each award.

• Supported awards: DXCC, WAS, JCC, JCG, WAKU, cities/guns/wards, per band, per mode, POTA, SOTA, WWFF, IOTA, POTA (my activated parks)
• POTA and the like count each reference entered in the QSO. A QSO with several references (K-0001, K-0002) counts for each of them.
• You can choose which QSLs count as confirmed (paper QSL, hQSL, eQSL, LoTW).
• Show: all / worked / confirmed / worked but not confirmed / not worked. Search by code or name.
• Conditions: mode category (CW / phone / digital), mode (several allowed, as in FT8|FT4), band, period, satellite (include / exclude / only), station callsign, and not counting deleted cities/guns.
• Mode columns: three categories (CW / phone / digital) or one column per mode.
• Results can be exported as CSV for award applications (including a QSO that confirms each item).
• JCC counts cities with a 4-digit Code and, separately for each ward, Tokyo's 23 wards (6-digit 1001xx). Wards of designated cities (6 digits) count as their city. WAKU counts the wards of designated cities.

4.11 DX support

• View > DX station / entity search: search by callsign, prefix or country name and show entity information and your worked status. The Entities tab can show only entities not yet worked.
• Tools > Update cty.dat (country file): downloads the latest cty.dat.
• Tools > Recalculate DXCC / zones for all QSOs: re-determines the country, zones and WPX prefix of every QSO.
• Tools > DX cluster: lists spots and colors new ones (4.25), with a band map (4.30).
• View > Grayline map: day/night boundary and great-circle path on a world map (4.30).
• Tools > Rotator: turns the antenna to the station (4.29).
• Callbook lookup: looks up the name, QTH and grid of DX stations on QRZ.com or HamQTH (4.24).

4.12 Area code table (JCC / JCG)

HamlogEx includes a table of about 2,600 codes: JCC (cities), JCG (guns, i.e. Japanese rural districts), wards of designated cities, and towns/villages in guns (in Turbo HAMLOG notation such as 01008C). When you open a log whose code table is empty, the table is loaded automatically (this can be turned off on the QSO entry tab).

Tools > Edit area code table (JCC/JCG) lets you:

• Search by code or place name, filter by kind (JCC / JCG / Ku / Town), show or hide deleted cities/guns, and show only codes without latitude/longitude
• Edit the place name, kind, latitude/longitude and deletion date (double-click a cell), add and delete codes, then click Save to confirm
• Import and export CSV (format: code,name,kind,lat,lon,deleted)
• Load the bundled table (add only missing codes / reset names etc. to the standard values)

Registered latitude/longitude is used for distance, bearing and maps. Tools > Fill QTH from area codes puts the place names from the table into the QTH of logged QSOs.

4.13 Data maintenance

4.13.1 QSO data check

Tools > QSO data check finds typing errors and inconsistencies between fields.

• Choose the checks on the left and click Check (you can limit it to the QSOs shown by the current filter).
• Problems are listed with severity (error / warning / info), type, QSO, description and suggested fix.
• Problems with a suggested fix (band from frequency, place name from the code table, full-width to half-width characters, removing leading/trailing spaces, etc.) can be fixed with Fix selected or Fix all fixable.
• Double-click a row to edit the QSO. The results can be saved as CSV.

Checks: callsign format, band/frequency mismatch, out-of-band frequency, empty band or frequency, empty mode, RST/mode mismatch, code/QTH mismatch, code not in the table, empty code for a Japanese station, grid locator format, future or too-old dates, duplicate QSOs, leading/trailing spaces, full-width alphanumerics, QSL mark/date mismatch

4.13.2 Bulk text replace

Edit > Replace text (Ctrl+H) replaces text in a chosen field across many QSOs.

1. Choose the field (17 fields including QTH, Name, Remarks, Code, Mode and the 3-character QSL field) and how to match (contains / whole field / starts with / ends with / regular expression / fill empty / replace whole field).
2. Enter the text to find and the replacement.
3. If needed, narrow it with a condition (for example Mode=CW and Band=40m) and a target (all / shown in the list / selected).
4. Check the before/after values with Preview, clear the check box of rows you don't want to change, and click Replace. The replacement applies to the field that was previewed. If you change the field or conditions after previewing, preview again.

A backup is made automatically before replacing (this can be turned off).

4.14 Backup and restore

• File > Back up log and settings: saves the open log, settings, print definitions, the radio model file (rigs.json) and the print definitions and lists referenced by the settings into one zip file. The log can stay open while backing up.
• Automatic backup: on the Backup tab of the settings, set up automatic backup on exit (and when switching logs). A backup is made only when the log was changed. The file name contains the log name and a 6-character tag for the log's location (so logs with the same name in different folders do not remove each other's generations). The default folder is Documents\HamlogEx\Backup and 10 generations are kept by default.
• File > Restore from backup: choose a backup zip, choose what to restore (log [with a destination], settings, print definitions, etc.) and click Restore.
• The current state is backed up automatically before restoring.
• When restoring on another PC, files whose original folder does not exist are placed in %APPDATA%\HamlogEx\Restored and the settings are adjusted to point there.
• Only data files (print definitions, images, call lists, etc.) go back to their original folders. Other kinds of files are placed in Restored, and executable files (.exe, .bat, etc.) are never restored.
• Before putting print definitions and other files back into their original folders outside AppData, and before restoring external apps, "also save to", the backup folder or network sharing settings, HamlogEx shows them and asks. Choose No for a backup you received from someone else (the files go to Restored and your current settings are kept).
• If settings are restored, HamlogEx restarts.
• If the settings file is damaged: a settings file that cannot be read at startup is kept as settings.json.broken-<date time>, HamlogEx starts with the standard settings and tells you.

4.15 Settings

The tabs of Tools > Settings (listed down the left side of the window):

• Clicking OK does not clear the QSO being entered (the entry form is cleared only when the time display is changed). The settings cannot be opened while an import or similar task is running.
• Check boxes in lists toggle with a single click.

4.16 Language and theme

• The language follows the Windows display language automatically. You can also choose English or Japanese on the General tab (no restart needed).
• The theme can be light, dark or follow Windows.

4.17 Log list definition

File > Log list definition sets the layout of the printed log list and the text export (like Turbo HAMLOG's log list output definition file).

• Columns: header, contents, print width (mm; 0 = share the rest), text width (characters), alignment, monospace and bold for each column. Contents can mix placeholders (7.1) and text; {No} is the row number, and formats such as {Date:yy/MM/dd} work.
• Page and title: paper (A4 / A3 / B5 / B4 / Letter) and orientation, margin, font, font size, title (placeholders such as {MyCall} allowed), shading of every other row, vertical lines.
• QSOs to output: narrow with a condition (7.2), e.g. Band=40m and not Rcvd.
• Text output: format (fixed-width text / CSV / tab-separated), encoding (UTF-8 / Shift_JIS), header line. Fixed-width text counts full-width characters as 2.
• Save and use makes it the definition used by File > Print log and File > Export > Log list as text. Use standard goes back to the standard columns.
• The QSOs are those shown in the list (or the selected ones). Definitions are *.hxlist.json files in %APPDATA%\HamlogEx\PrintDefinitions (included in backups).

4.18 Shortcut keys and external applications

Set these on the Keys / apps tab of Tools > Settings.

• Shortcut keys: assign a key to each command. Click the Key cell and press the keys (Back / Delete clears). If you change or clear a standard key, the standard key stops working, and the keys shown in the menus change too. Apart from function keys, Esc and Insert, use a combination with Ctrl or Alt. A warning is shown when the same key is assigned twice.
• External applications: register up to 20 programs, files or web pages and start them from Tools > External apps (keys can be assigned too).
• & in the name sets the access key, and a name of just - adds a separator.
• {Call} {Freq} {Mode} {Band} {Code} {Grid} {Name} {Qth} {MyCall} in the path and arguments are replaced with the values of the QSO being entered (or the selected QSO when Call is empty). Example: the path https://www.qrz.com/db/{Call} opens the station on QRZ.com.
• Values put into the arguments are quoted automatically when they contain spaces. " & | < > ^ % and line breaks are removed from the values (so imported data cannot run other commands).
• In a file path, characters not allowed in file names and folder separators (\ / :) in the values become _, and .. is removed (for example JA1ABC/1 → JA1ABC_1).
• Keys used by the Japanese input method while converting (such as F6-F10) do not act as shortcuts.

4.19 Entry field layout and POTA fields

In Tools > Settings > Entry fields you choose the row (1-4) of each entry field, its order within the row (left to right), its relative width and whether it is shown. Reset to standard restores the standard layout. Call cannot be hidden.

• Row 4 has POTA, SOTA, WWFF and IOTA (the other station's references) and My POTA (the park you are activating; kept after saving). They are hidden by default, so tick Show for the ones you use. Separate several references with commas (e.g. K-0001, K-0002).
• The references are read and written in ADIF (POTA_REF SOTA_REF WWFF_REF IOTA MY_POTA_REF ...) and counted in the POTA / SOTA / WWFF / IOTA / POTA (my activated parks) awards. They can also be used as placeholders and in bulk replace.

4.20 Record number search and QSO counter

• View > Go to record number (Ctrl+G): enter a number to select that QSO in the list. Record numbers count QSOs from the oldest (1). The record number of the selected QSO is shown in the status bar. If the QSO is hidden by the filter, the filter is cleared.
• QSO counter: the status bar shows "N QSOs / M stations since ..." (useful for portable operation and contests). View > Reset QSO counter (or right-click the status bar) starts counting again from now.

4.21 Saving a QSO to several logs

Add log files (.hxlog) under "Also save each QSO to these logs" in Tools > Settings > Entry fields*. Every QSO saved from the entry fields (and from WSJT-X) is then also added to those logs, e.g. a club station log or a backup log.

• A log that cannot be found (drive removed, file moved) is reported and never created anew.
• The log that is currently open is ignored.

4.22 Contest mode

Set the contest ID (the Cabrillo CONTEST:, e.g. CQ-WW-CW), the period (UTC), the sent exchange and the Cabrillo header in Tools > Settings > Contest, and turn the mode on and off with Tools > Contest mode.

• In contest mode the entry area shows a Contest field (sent and received exchange). {Serial} in the sent exchange becomes the serial number (001, 002 ...), which advances with every QSO.
• A station already worked in the same contest on the same band (and mode, if set) is shown as DUPE.
• Enter the period as yyyy/MM/dd HH:mm (UTC). Settings cannot be saved if a date cannot be read or the end is before the start.
• File > Export > Cabrillo writes the QSOs with this contest ID (within the period, if set) in Cabrillo 3.0 format. Frequencies are in kHz on HF and band codes (50 144 432 1.2G etc.) from 50 MHz up. The contest ID and exchanges are also read and written in ADIF (CONTEST_ID STX SRX STX_STRING SRX_STRING).

4.23 Online QSL and logbooks (eQSL, LoTW, Club Log, QRZ.com)

Set up your accounts in Tools > Settings > Online QSL, then upload and download with QSL > Online QSL / logbooks. Passwords and keys are stored encrypted for your Windows user.

• Upload unsent sends only QSOs not sent yet (optionally from a date) and marks the QSOs that were accepted. QSOs refused as duplicates are marked as sent too.
• eQSL uploads go in batches of 200. If eQSL does not accept every QSO in a batch, that batch is sent again one QSO at a time and only the accepted QSOs are marked as sent. Rejected QSOs are listed with the reason and stay unsent.
• For Club Log, choose the Upload method in the settings: one QSO at a time (realtime.php, with a result for each QSO) or as one file (putlogs.php, the method Club Log recommends for bulk uploads; Club Log imports the file later).
• For Club Log and QRZ.com, uploading stops after three sign-in failures, access refusals or server errors in a row, and the number of QSOs not sent is shown (rejections of individual QSOs do not stop it).
• If TQSL skipped some QSOs for LoTW (duplicates, or outside the certificate's date range), this is reported. Clear the sent mark of QSOs outside the date range and upload them again later.
• Download confirmations matches each confirmation to a QSO with the same station, within 30 minutes and on the same band, and marks it as confirmed. A QSO with exactly the same callsign (including portable notation such as KH6/K1ABC) is preferred. Confirmations that do not match are listed.
• Each download continues from the previous one. The position is recorded per log, so switching logs does not lose another log's confirmations.
• Downloading the full history can take a while (HamlogEx waits up to 10 minutes for eQSL and 15 minutes for LoTW). Cancel stops it.
• With "Send each QSO to Club Log and QRZ.com as soon as it is saved" on, every QSO is sent when saved. QSOs that could not be sent stay unsent.
• The TQSL certificate password is passed on the TQSL command line, so saving it in TQSL itself is recommended.

4.24 Callbook lookup (QRZ.com, HamQTH)

Choose the service (QRZ.com XML or HamQTH.com) and enter your user name and password in Tools > Settings > Callbook / cluster. When you enter the callsign of a DX station it is looked up automatically, and empty Name, QTH and Grid fields are filled (the result is shown above the entry fields). Turn on "Also look up Japanese stations" for JA stations too. Test connection checks the settings.

• HamQTH.com is free (register an account). QRZ.com returns full data only with an XML subscription.

4.25 DX cluster

Tools > DX cluster connects to a telnet DX cluster (DX Spider, AR-Cluster, CC Cluster ...) and lists the spots. The server, login callsign and commands sent after login are set in Settings > Callbook / cluster.

• New entities (NEW ONE), new bands, new modes and new slots are colored. You can filter by band or show only new ones.
• Double-click a spot (or Use spot) to put the callsign in the entry fields and tune the rig to its frequency and mode (or put the frequency in the entry fields if no rig is connected). The mode is guessed from the comment and the frequency.
• Commands (e.g. sh/dx 20) can be sent from the field at the bottom. Closing the window keeps the connection (use Disconnect to close it).

4.26 Charts

The Charts tab of View > Statistics shows QSOs (wide bars) and stations (narrow bars) by year, by month (last 24 months), by band, by mode, by hour (UTC) and by continent.

4.27 JARL e-log

Writes the electronic log for JARL contests (ALL JA1, All Cities/Guns, Field Day, ...): the summary sheet (R2.1) and the log in JARL format.

1. In Tools > Settings > Contest, enter the contest ID and period, and under "JARL e-log" the contest name, category code, power and so on. Address, e-mail and comments come from the Cabrillo items on the same tab (ADDRESS, EMAIL, SOAPBOX); multi-op operators from OPERATORS.
2. Choose File > Export > JARL e-log, check the total score and signature, and click Save as file (the default name is callsign.log).
3. Before submitting, you can send it to logtest@jarl.org to have the format checked.

• Each log line is "date time band mode callsign sent-RST sent-number received-RST received-number". Numbers are written without the RST (599 20L → 599 and 20L). When the RST field is empty and the exchange starts with the RST (5920L on phone, 59920L on CW), it is split too. Exchanges like 13 M or 13M, where only a one-letter power code follows, are treated as prefecture and power, not as an RST.
• Times are JST for domestic contests (UTC can be set). The encoding is Shift_JIS (UTF-8 can be set).
• The total score (multipliers) differs between contests, so enter it yourself according to the rules.

4.28 CW keyer and CQ machine

Tools > CW keyer / CQ machine sends prepared messages in CW or by voice.

• CW: sent by a WinKeyer (K1EL WK2 / WK3) or the radio's built-in keyer (ICOM CI-V, KENWOOD KY, Hamlib rigctld). There are eight messages F1-F8; {MyCall} {Call} {Rst} {Exch} {Serial} {Name} are replaced with the values in the entry fields ({Exch} is the sent exchange in contest mode). Text typed in the box at the bottom can be sent too. A WinKeyer is not sent more while its buffer is busy (XOFF), so characters are not lost in long messages. When buttons are pressed one after another, each message is sent after the previous one (Esc stops the rest).
• Voice (CQ machine): assign WAV files to V1-V4; they are played on the chosen audio output (such as the radio's USB audio). The radio is switched to transmit over CAT while playing (or turn this off and use VOX). Pressing another button while playing stops the current message before playing the next one (without dropping transmit).
• With Repeat (CQ) on, a button repeats its message at the set interval (with an optional limit). Esc or Stop stops it.
• Keys in the keyer window: F1-F8 = CW, Shift+F1-F4 = voice, Esc = stop. From the main window, assign keys to "CW message F1" etc. on the Keys / apps tab.
• Settings are on Tools > Settings > Keyer / rotator. Record messages with any recording software as PCM WAV files.

4.29 Rotator

Tools > Rotator turns the antenna rotator through Hamlib rotctld (TCP) or the YAESU GS-232 format (serial).

• To station turns to the bearing of the station being entered (short path), Long path to the opposite direction. You can also type an azimuth and click Turn, or click the circle.
• The circle shows the current azimuth (needle), the target (dashed) and the station's bearing (dotted).
• Tools > Turn antenna to the station can be given a key so you can turn from the main window.
• An azimuth offset (antenna mounting error) can be set.

4.30 Band map and grayline map

• Band map: the Band map tab of the DX cluster window places the spots at their frequencies. New ones (NEW ONE, new band, new mode) are framed in color, and the radio's frequency is marked. Leave the band empty to follow the radio's band. Click a spot to use it (entry fields and radio). Use the wheel to zoom and drag to scroll.
• Grayline map: View > Grayline map draws the day/night boundary (grayline), the point under the sun, your position and the station being entered, and the great-circle path on a world map, updated every minute. Your position comes from the grid or latitude/longitude on the DX / awards tab.

4.31 Finding QSOs missing from the log (LoTW)

Find QSOs missing from the log (LoTW) in QSL > Online QSL / logbooks downloads your QSOs uploaded to LoTW (from the date on the left, or the last year) and lists those not in this log (no QSO with the same station, band and within 30 minutes). Add selected QSOs to the log saves the ones you tick, marked as uploaded to (and confirmed by) LoTW.

4.32 Text / image hit

Choose a folder on Tools > Settings > Network / files. Files in it (and its subfolders) named after a callsign are shown in the side panel when you enter that callsign.

• Examples: JA1ABC.txt (its text is shown), JA1ABC.jpg, JA1ABC_2.png, JA1ABC-QSL.jpg (shown as thumbnails). Portable calls are matched by the base callsign.
• Click to open with the default application. Handy for scanned QSL cards and notes about stations.
• After adding files, close the settings with OK to reload the folder.

4.33 Network sharing (multi-op)

Use HamlogEx on several PCs on the same network so that a QSO saved on any PC goes into the logs of all PCs (multi-op contests, several operating positions).

1. Before starting, give every PC the same log (backup and restore).
2. Make one PC the host and the others clients (Tools > Settings > Network / files). On clients, enter the host's computer name or IP address. Use the same port and passphrase (at least 8 characters) on every PC, and the same HamlogEx version (from 0.12.1 the passphrase check changed and older versions cannot connect). - The passphrase itself is never sent. Host and client both prove they know it using fresh random numbers each time, so a captured exchange cannot be replayed and a fake host is refused. QSOs and messages are not encrypted, so use it only in a trusted network.
3. Click Start in Tools > Network sharing on the host, then on the clients. Allow the port through Windows Firewall on the host.

• Saved QSOs are sent to the other PCs immediately. A QSO already in the log (same station, band, mode, within 1 minute) is not added twice. The contest dupe check includes the QSOs from other PCs.
• The window lists the connected stations (with the operator's callsign) and can send messages to all PCs. The status bar shows the number of stations.
• Clients reconnect every 10 seconds when the connection is lost. QSOs saved while the host is stopped are not sent, so align the logs afterwards.

5. Feature list

6. Keyboard shortcuts

6.1 Main window

These are the standard keys. They can be changed on the Keys / apps tab of the settings (4.18).

Keys used by the Japanese input method while converting do not act as shortcuts.

6.2 Calendar (date field)

A mouse click on a day enters it immediately. Today enters today's date.

6.3 Print definition editor

7. Appendix

7.1 Placeholders

7.2 Condition syntax

Used for print conditions (print definition editor) and for the condition in bulk text replace.

• Fields: placeholder names (Call, Band, Mode, Freq [number in MHz], Rmks1, etc.)
• User lists: UserList=FISTS (stations in the FISTS list; when a station is in several lists, any match counts), UserList (in any list), UserInfo*=1234
• Flags and others: Rcvd (QSL received), Sent (QSL sent), Dx (overseas station), Portable (portable suffix), Club (Japanese club station), Manager (via manager), Utc (UTC display), Qsl1 Qsl2 Qsl3 (each character of the QSL field), Hqsl Eqsl Lotw (received), Year Month Hour, Continent, Dxcc, Prefix, State
• POTA and others: Pota (has a POTA reference), Sota Wwff Iota MyPota, Contest=CQ-WW-CW
• Examples: Band=40m and not Rcvd, Mode=FT8|FT4, (Dx or Portable) and Name, Pota or Rmks1*="POTA"

7.3 File formats

7.4 Where data is stored

7.5 FAQ

Q. HamlogEx cannot connect to my radio. On the Radio tab, check that the model, COM port and baud rate match the radio's settings, and use Test connection. For ICOM radios, also check the CI-V address and the radio's CI-V settings (such as CI-V USB Echo Back). The radio cannot be connected while another program is using the same COM port.

Q. Countries and zones are not shown. cty.dat was not found. Run Tools > Update cty.dat (country file).

Q. JCC/JCG place names are not shown. The area code table may be empty. Click Load bundled table... in Tools > Edit area code table (JCC/JCG).

Q. Times are off by 9 hours. Check Time zone on the General tab. When imported times have no J / U suffix, they are taken to be in the current display time base.

Q. I want to move to another PC. Create a zip with File > Back up log and settings, then run File > Restore from backup on the new PC.

Q. I cannot upload to LoTW. Install ARRL's TQSL and create your certificate and a Station Location in TQSL. Enter that Station Location name on the Online QSL tab. If tqsl.exe is not found, set its location.

Q. The QRZ.com callbook shows only the name. QRZ.com returns only some fields without an XML data subscription. Choose HamQTH.com for a free service.

Q. I cannot connect to the DX cluster. Check the server name and port. If the login callsign is empty, your callsign from the QSO entry tab is used. A firewall may also block the telnet port (often in the 7000s).

Q. The WinKeyer sends nothing. Check the WinKeyer's COM port on the Keyer / rotator tab (the port cannot be opened while another program uses it). The speed is set with the slider in the keyer window. To use the radio's keyer, connect the radio first (YAESU radios cannot send CW text over CAT).

Q. Network sharing does not connect. Click Start on the host first, and allow the port (default 52100) through Windows Firewall on the host. Also check that every PC uses the same passphrase and that the host address on the clients is right.

Q. My settings were back to the defaults after starting. The settings file may have been damaged and unreadable. The original file is kept as %APPDATA%\HamlogEx\settings.json.broken-<date time>. Restore the settings from a backup or set them again.

Q. When printing, I am told that the paper differs from the definition. The printer does not support paper of the print definition's size, or other paper was chosen in the print dialog. Check the printer's paper settings. Yes prints anyway (the positions may be off).

Q. I cannot log a QSO during an import. Log from the entry form after the import has finished. QSOs from WSJT-X and network sharing are logged even during the import.

Q. The window opened off the screen. If the monitor arrangement has changed since last time and the title bar is not on any screen at startup, the window is moved to the centre of the main screen. If it is still not visible, Shift+right-click its taskbar button and choose Maximize.

Q. My JCC count is different from before. From v0.6, each of Tokyo's 23 wards counts as one city (following the current JARL list).

7.6 Main changes (v0.11.1 to v0.12.1)

See the change history in the README for details.

7.7 Notes

• Turbo HAMLOG is software by JG1MOU. HamlogEx is an independent project and is not related to it.
• Radio commands are based on each manufacturer's documentation, but they differ between models and firmware versions, so please test with your radio.
• The bundled JCC/JCG table is converted from JCC-JCG-List (Apache License 2.0, based on the JARL lists). See THIRD-PARTY-NOTICES.md for details.
• Licence data lookup uses the Web-API of the MIC Radio Use Portal.
• eQSL.cc, LoTW (ARRL), Club Log, QRZ.com, HamQTH.com and DX clusters are services run by their own operators. Follow each service's terms. A change on the service side may stop a feature from working.