Settings

Settings

KLog's configuration lives in one Setup dialog, opened from the Tools menu (Settings ...) or the toolbar. The dialog is organized in tabs/pages, described below. Configuration is stored locally (on Linux, under ~/.klog/, e.g. the klogrc file and logbook.dat; the equivalent per-user application-data locations are used on Windows and macOS).

The field names below are taken from the current KLog source code. Minor wording may differ slightly between versions — please update this page if you spot a difference with your installed version.

User Data & Station Profile

Your personal and station data, used to fill in every QSO and every upload to online services:

• Callsign — the station callsign used for logging.
• Operators — operators using this station (comma separated if more than one).
• Name, Address (lines 1-4), City, Zip Code, Country.
• CQ Zone, ITU Zone.
• Locator (your Maidenhead grid locator; KLog warns if it is not valid).
• Antenna 1 / 2 / 3 and Rig 1 — free-text description of your station equipment.

This information (callsign, operators, dates, station callsign per log) can also be managed per-logbook — see Station Profiles and Logs below.

Band & Mode

Two simple lists — Bands and Modes — used to enable/disable which bands and modes appear in the band/mode selectors while logging. Untick the ones you never use to keep the dropdowns short.

Radio Interface (Hamlib)

KLog can read the frequency/mode directly from your radio through Hamlib:

• Activate HamLib — turns the radio connection on/off.
• Radio — select your rig model from Hamlib's supported radio list.
• Connection type: Serial (choose the serial port and speed) or Network (host/port, for radios exposed over a network, e.g. via rigctld).
• Poll interval — how often (in milliseconds) KLog polls the radio for its frequency/mode.
• Read-Only mode — KLog only reads from the radio and never changes its settings.
• Test button — click to test the connection to the radio; shows Test: OK or Test: NOK.

Once active, the frequency read from the radio is shown live in the main window, and selecting a band while Hamlib is not active makes KLog default to the lower band-edge frequency. See Radio Interfaces for day-to-day usage and Entering a QSO for how this interacts with logging.

DX Cluster

Configuration for the built-in DX Cluster client (Telnet cluster) and the DX Assistant spot filter:

• Add/remove DX Cluster servers (Add / Delete a server entry).
• DX Assistant — Enable DX Assistant to turn on the assistant panel; Enable ClubLog Most Wanted integration to highlight most-wanted entities.
• Spot sources — choose which spots to bring in: WSJT-X spots (requires the UDP Server to be started on the UDP page) and/or your own DX Cluster connection.
• Show HF spots, Show V/UHF spots, Show WARC spots, Show worked spots, Show confirmed spots — filters for which spots are displayed.
• Messages: Show ANN/FULL messages, Show WWV messages, Show WCY messages — cluster announcement/propagation messages.
• Others: Send DX Spots to the map, Save DX Cluster activity (keep a local log of cluster traffic).

See DX Cluster for how to actually connect to a cluster and use the spot list day-to-day.

Satellites

Manage the satellite database used by Satellite QSOs:

• New, Edit, Remove a satellite entry (Name, Downlink, uplink, Modes, ID).
• Import / Export your satellite list to/from a file.
• Update Satellite Data (also available from the Tools menu) refreshes the built-in satellite list.

World / Entity Editor

Manages the DXCC "world" database (cty.csv) that KLog uses to recognize entities, continents, zones and to compute bearing/distance for each contact:

• Import World — load a new cty.csv (e.g. BigCTY) file. Export World to save your current data.
• Add/Edit/Delete Special Callsigns — override the entity/zone information KLog would otherwise guess for a specific callsign (useful for DXpeditions or unusual prefixes). Fields: Callsign, Entity, Continent, CQ Zone, ITU Zone, ARRL ID.
• Update cty.csv is also reachable from the Tools menu, to refresh entity data without opening Setup.

This is the same data the First Run Wizard offers to download on first start.

Online Services (eLog)

Credentials and default behavior for the QSL/logbook online services. Each service has its own Activate checkbox; see the dedicated integration pages for the full upload/download workflow:

• LoTW — LoTW user, LoTW password, path to the TQSL software (Use TQSL, TQSL path), select the default option for new QSOs in LoTW.
• eQSL.cc — Activate eQSL.cc, eQSL.cc user, eQSL.cc password, select the default option for new QSOs in eQSL. See eQSL.
• ClubLog — Activate ClubLog, ClubLog email, ClubLog password, ClubLog App password, select the default option for new QSOs in Clublog, Check automatically. See Clublog.
• QRZ.com — Activate QRZ.com, LogBook Key, Paying Subscriber / Check it if you are paying for a qrz.com subscription, Check in Qrz.com all Calls as they are entered, select the default option for new QSOs in QRZ.com. See QRZ Logbook.

UDP / WSJT-X

Enables the UDP server KLog uses to talk to WSJT-X (and compatible software):

• Start UDP Server — turn the listener on.
• UDP Port, Network interface, Multicast address (multicast group address WSJT-X is sending the datagrams to).
• Allow WSJT-X to send logged QSOs to KLog, Automatically log QSOs from WSJT-X.
• Update status information from WSJT-X — shows WSJT-X's current status (band/mode/Tx) inside KLog.
• QSOs notification timeout (in milliseconds).

See WSJT-X / UDP Integration for the full setup and usage walkthrough.

Logs

KLog logbooks can hold several independent logs (e.g. one per callsign, per contest, or per year). This page manages them:

• New, Edit, Remove a log. Fields: Station Callsign, Date (start date), Operators (comma separated), Comments, and a read-only QSOs count.
• Removing a log deletes all the QSOs it contains — KLog asks for confirmation first.
• A Log View page lets you choose which Fields (ADIF columns) are shown in the log table at the bottom of the main window.

See Logging for day-to-day use of multiple logs.

Colors

Customize how QSOs are highlighted in the log and award views:

• Default palette or WSJT-X palette (mimics WSJT-X's coloring), or fully custom colors.
• Dark Mode / Light Mode toggle.
• Per-status colors: New One (ATNO — All Time New One), Worked in this band (worked but not confirmed), Confirmed in this band, and the Default color.

Miscellaneous

General behavior options that don't fit elsewhere:

• Check for new versions automatically.
• Time in UTC / real time — select to use UTC time or your local real time in the QSO entry clock.
• Log in real time.
• Imperial system — use miles instead of kilometers for distance.
• Complete QSO with previous data — pre-fill a new QSO with data from the previous one.
• Reset to My Data for all QSOs.
• Check band & mode for needed status — used by the Awards/DX Cluster "needed" indicators.
• Check non-valid calls, Dupe time range — duplicate-QSO checking window.
• Show seconds in the QSO editor / log.
• Show the Station Callsign used in the search box — the Search box also shows the callsign on the air for the QSO.
• Manage DX-Marathon — enable DX-Marathon tracking (see Awards).
• Provide Info for statistics — opt in/out of anonymous usage statistics.
• ADIF handling: Save ADIF on exit, Use this default filename, path to the default ADIF file, Delete always temp ADIF file after uploading QSOs. See ADIF Import / Export.
• Mark QSO to send QSL when QSL is received, Mark sent eQSL & LoTW in new QSO as queued, Send QSOs in real time to online services.
• Move DB — relocate the database file (logbook.dat) to another directory (e.g. a cloud-synced folder such as Google Drive or Dropbox, to access your log from multiple devices — see the note on the Home page).
• Log level — verbosity of KLog's internal debug log.

---

Back to Home · See also: First Run / Setup Wizard, Troubleshooting.