WSJT Integration

KLog can link with WSJT-X (and compatible software using the same UDP protocol, e.g. JTDX) to automatically log QSOs made in FT8 and other digital modes, and to feed live spots into the DX Cluster / DX Assistant.

Configuring KLog

In Settings → UDP / WSJT-X:

1. Tick Start UDP Server.
2. Set the UDP Port, Network interface and Multicast address to match WSJT-X's own UDP Server settings (WSJT-X → Settings → Reporting).
3. Enable Allow WSJT-X to send logged QSOs to KLog and Automatically log QSOs from WSJT-X so completed QSOs are logged into KLog without manual entry.
4. Optionally enable Update status information from WSJT-X to see WSJT-X's current band/mode/Tx status inside KLog, and set the QSOs notification timeout.

[ADD SCREENSHOT HERE: UDP settings page with Start UDP Server enabled and the port/multicast fields filled in]

Configuring WSJT-X

In WSJT-X, open File → Settings → Reporting and enable UDP Server / "Accept UDP requests", pointing the UDP server address/port to match what you configured in KLog (typically 127.0.0.1 and the same port, or the same multicast group if running WSJT-X and KLog on different machines).

[ADD SCREENSHOT HERE: WSJT-X Reporting settings tab with UDP Server enabled]

Using it

Once both sides are configured and KLog's UDP server is running:

• QSOs logged in WSJT-X appear automatically in KLog's log, without needing to press Add manually.
• WSJT-X spots (decoded callsigns) can appear as WSJT-X-sourced entries in the DX Assistant, if that spot source is enabled in Settings → DX Cluster (this requires the UDP Server to be running).
• KLog's Entering a QSO page describes Manual Mode, which lets you log a separate, manual QSO (e.g. a voice contact) while WSJT-X keeps feeding automatic FT8 QSOs in the background — after saving the manual QSO, the data coming from WSJT-X/the radio is shown again.

[ADD SCREENSHOT HERE: KLog main window next to WSJT-X, showing a QSO that was just auto-logged from WSJT-X]

Troubleshooting

If QSOs from WSJT-X are not appearing in KLog: confirm both applications use the same UDP port and, if not running on 127.0.0.1, the same multicast address; check that no firewall is blocking the UDP traffic; and confirm Start UDP Server is actually running in KLog (test by generating a WSJT-X "status" or completing a QSO). See also Troubleshooting.