mirror of
https://github.com/praktimarc/kst4contest.git
synced 2026-03-30 04:31:04 +02:00
Philipp Wagner (DN9APW)
f93f3acbb0
Wiki Sync fix Wiki no longer empty commits Add files via upload a
112 lines
4.7 KiB
Markdown
112 lines
4.7 KiB
Markdown
# Log Synchronisation
|
||
|
||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Log-Synchronisation)
|
||
|
||
KST4Contest automatically marks worked stations in the chat user list. Two basic methods are available:
|
||
|
||
---
|
||
|
||
## Method 1: Universal File Based Callsign Interpreter (Simplelogfile)
|
||
|
||
KST4Contest reads a log file and searches for callsign patterns using a regular expression. Binary log files are also supported – unreadable binary content is simply ignored.
|
||
|
||
**Advantage**: Works with almost any logging program that writes a file.
|
||
**Disadvantage**: No band information available – stations are only marked as "worked", not on which band.
|
||
|
||
Enter the path to the log file in the Preferences. The file is only read, never modified (read-only).
|
||
|
||
> **Tip**: The Simplelogfile function can also be used to mark stations that are definitely unreachable (e.g. personal notes). This will be replaced in a later version by a better tagging system.
|
||
|
||
---
|
||
|
||
## Method 2: Network Listener (UDP Broadcast) – Recommended
|
||
|
||
When saving a QSO, the logging software sends a UDP packet to the broadcast address of the home network. KST4Contest receives this packet and marks the station including **band information** in its internal SQLite database.
|
||
|
||
> **Important**: KST4Contest must be **running in parallel with the logging software**. QSOs logged while KST4Contest is not running will not be captured – except with QARTest (which can send the complete log).
|
||
|
||
**Default UDP port**: 12060 (matches the default of most logging programs)
|
||
|
||
---
|
||
|
||
## Supported Logging Software
|
||
|
||
### UCXLog (DL7UCX)
|
||
|
||
UCXLog sends QSO UDP packets and transceiver frequency packets.
|
||
|
||
**Settings in UCXLog:**
|
||
- Enable UDP broadcast
|
||
- Enter the IP address of the KST4Contest computer (for local operation: `127.0.0.1`)
|
||
- Port: 12060 (default)
|
||
|
||
Note the green-highlighted fields in the UCXLog settings: IP and port must be filled in.
|
||
|
||
Note for multi-setup (2 computers, 2 radios, one KST4Contest instance): Both logging programs must send QSO packets to the IP of the KST4Contest computer. In this case, at least one IP is not `127.0.0.1`.
|
||
|
||
### QARTest (IK3QAR)
|
||
|
||
**Special feature**: QARTest can send the **complete log** to KST4Contest (button "Invia log completo" in the QARTest settings). This means QSOs logged before KST4Contest was started are also captured.
|
||
|
||
**Settings in QARTest:**
|
||
- Configure UDP broadcast and IP/port as with UCXLog
|
||
- Use "Invia log completo" for a full log upload
|
||
|
||
*(„Buona funzionalità caro IK3QAR!" – DO5AMF)*
|
||
|
||
### N1MM+
|
||
|
||
**Settings in N1MM+:**
|
||
|
||
In N1MM+ under `Config → Configure Ports, Mode Control, Winkey, etc. → Broadcast Data`:
|
||
- Enable `Radio Info` (for TRX sync / QRG)
|
||
- Enable `Contact Info` (for QSO sync)
|
||
- IP: `127.0.0.1` (or IP of the KST4Contest computer)
|
||
- Port: 12060
|
||
|
||
For the built-in DX cluster server: configure N1MM+ as a DX cluster client (server: `127.0.0.1`, port as set in KST4Contest).
|
||
|
||
### DXLog.net
|
||
|
||
**Settings in DXLog.net:**
|
||
- Enable UDP broadcast
|
||
- Enter the IP of the KST4Contest computer (green-highlighted fields)
|
||
- Port: 12060
|
||
|
||
### WinTest
|
||
|
||
WinTest is also supported. KST4Contest receives WinTest UDP packets via a dedicated listener. Configuration is analogous to the other programs.
|
||
|
||
---
|
||
|
||
## TRX Frequency Synchronisation
|
||
|
||
In addition to QSO synchronisation, UCXLog and other programs also transmit the **current transceiver frequency** via UDP. KST4Contest processes this information and makes it available as the `MYQRG` variable.
|
||
|
||
**Result**: Your own QRG never needs to be typed manually in the chat – clicking the MYQRG button or using the variable in the beacon is sufficient.
|
||
|
||
> **Note for multi-setup**: With two logging programs on two computers, only **one** should send frequency packets. KST4Contest cannot distinguish between sources and processes all incoming packets.
|
||
|
||
---
|
||
|
||
## Multi-Setup: 2 Radios, 2 Computers
|
||
|
||
For DM5M-style setups (2 radios, 2 computers, one KST4Contest instance or two separate):
|
||
|
||
**Option A – One shared KST4Contest instance:**
|
||
- Both logging programs send QSO packets to the IP of the KST4Contest computer
|
||
- Only one logging program sends frequency packets (recommended: the VHF logging program)
|
||
|
||
**Option B – Two separate KST4Contest instances (recommended):**
|
||
- Each logging program communicates with its own KST4Contest instance via `127.0.0.1`
|
||
- Two separate chat logins
|
||
- Better separation and fewer conflicts
|
||
|
||
---
|
||
|
||
## Internal Database
|
||
|
||
KST4Contest stores worked information in an internal **SQLite database**. This is independent of the logging program's database and is only populated via the UDP broadcast.
|
||
|
||
Before each new contest: reset the database! → [Configuration – Worked Station Database Settings](Configuration#worked-station-database-settings)
|