mirror of
https://github.com/praktimarc/kst4contest.git
synced 2026-07-13 08:07:11 +02:00
github-actions[bot]
237 lines
13 KiB
HTML
237 lines
13 KiB
HTML
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<title>{{ manual.title }} | KST4Contest Manual</title>
|
||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
<meta name="description" content="KST4Contest manual page: {{ manual.title }}">
|
||
<link rel="canonical" href="https://kst4contest.hamradioonline.de/manual/en/log-sync/">
|
||
|
||
<meta property="og:type" content="website">
|
||
<meta property="og:title" content="{{ manual.title }} | KST4Contest Manual">
|
||
<meta property="og:description" content="KST4Contest manual page: {{ manual.title }}">
|
||
<meta property="og:url" content="https://kst4contest.hamradioonline.de/manual/en/log-sync/">
|
||
<meta property="og:site_name" content="KST4Contest">
|
||
|
||
<meta name="twitter:card" content="summary_large_image">
|
||
<meta name="twitter:title" content="{{ manual.title }} | KST4Contest Manual">
|
||
<meta name="twitter:description" content="KST4Contest manual page: {{ manual.title }}">
|
||
|
||
<link rel="stylesheet" href="/assets/css/main.css?v=1783891386578">
|
||
<link rel="alternate" type="application/rss+xml" title="KST4Contest News" href="/feed.xml">
|
||
|
||
<meta property="og:image" content="https://kst4contest.hamradioonline.de/assets/social/kst4contest-og.png">
|
||
<meta property="og:image:width" content="1200">
|
||
<meta property="og:image:height" content="630">
|
||
<meta name="twitter:image" content="https://kst4contest.hamradioonline.de/assets/social/kst4contest-og.png">
|
||
|
||
</head>
|
||
|
||
<body>
|
||
<div class="site-bg"></div>
|
||
|
||
<header class="site-header">
|
||
<a class="brand" href="/">
|
||
<span class="brand-mark">◎</span>
|
||
<span>
|
||
<strong>KST4Contest</strong>
|
||
<small>ON4KST Contest Client</small>
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="site-nav">
|
||
|
||
<a href="/">Home</a>
|
||
|
||
<a href="/features/">Features</a>
|
||
|
||
<a href="/screenshots/">Screenshots</a>
|
||
|
||
<a href="/manual/">Manual</a>
|
||
|
||
<a href="/news/">News</a>
|
||
|
||
<a href="/roadmap/">Roadmap</a>
|
||
|
||
<a href="/about/">About</a>
|
||
|
||
<a href="/faq/">FAQ</a>
|
||
|
||
<a href="/support/">Support</a>
|
||
|
||
<a class="nav-cta" href="/download/">Download</a>
|
||
</nav>
|
||
</header>
|
||
|
||
<main>
|
||
|
||
<section class="section">
|
||
<div class="card manual-content">
|
||
<p><a href="/manual/en/">← Back to manual overview</a></p>
|
||
<h1>Log Sync</h1>
|
||
<h1 id="log-synchronisation" tabindex="-1"><a class="header-anchor" href="#log-synchronisation">Log Synchronisation</a></h1>
|
||
<blockquote>
|
||
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="/manual/de/log-synchronisation/">Deutsche Version</a></p>
|
||
</blockquote>
|
||
<p>KST4Contest automatically marks worked stations in the chat user list. Two basic methods are available:</p>
|
||
<hr>
|
||
<p><img src="client_settings_window_logsync.png" alt="Log Sync Settings Window"></p>
|
||
<h2 id="method-1%3A-universal-file-based-callsign-interpreter-(simplelogfile)" tabindex="-1"><a class="header-anchor" href="#method-1%3A-universal-file-based-callsign-interpreter-(simplelogfile)">Method 1: Universal File Based Callsign Interpreter (Simplelogfile)</a></h2>
|
||
<p>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.</p>
|
||
<p><strong>Advantage</strong>: Works with almost any logging program that writes a file.
|
||
<strong>Disadvantage</strong>: No band information available – stations are only marked as “worked”, not on which band.</p>
|
||
<p>Enter the path to the log file in the Preferences. The file is only read, never modified (read-only).</p>
|
||
<blockquote>
|
||
<p><strong>Tip</strong>: 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.</p>
|
||
</blockquote>
|
||
<hr>
|
||
<h2 id="method-2%3A-network-listener-(udp-broadcast)-%E2%80%93-recommended" tabindex="-1"><a class="header-anchor" href="#method-2%3A-network-listener-(udp-broadcast)-%E2%80%93-recommended">Method 2: Network Listener (UDP Broadcast) – Recommended</a></h2>
|
||
<p>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 <strong>band information</strong> in its internal SQLite database.</p>
|
||
<blockquote>
|
||
<p><strong>Important</strong>: KST4Contest must be <strong>running in parallel with the logging software</strong>. QSOs logged while KST4Contest is not running will not be captured – except with QARTest (which can send the complete log).</p>
|
||
</blockquote>
|
||
<p><strong>Default UDP port</strong>: 12060 (matches the default of most logging programs)</p>
|
||
<hr>
|
||
<h2 id="supported-logging-software" tabindex="-1"><a class="header-anchor" href="#supported-logging-software">Supported Logging Software</a></h2>
|
||
<h3 id="ucxlog-(dl7ucx)" tabindex="-1"><a class="header-anchor" href="#ucxlog-(dl7ucx)">UCXLog (DL7UCX)</a></h3>
|
||
<p><img src="ucxlog_logsync.png" alt="UCXLog Configuration"></p>
|
||
<p>UCXLog sends QSO UDP packets and transceiver frequency packets.</p>
|
||
<p><strong>Settings in UCXLog:</strong></p>
|
||
<ul>
|
||
<li>Enable UDP broadcast</li>
|
||
<li>Enter the IP address of the KST4Contest computer (for local operation: <code>127.0.0.1</code>)</li>
|
||
<li>Port: 12060 (default)</li>
|
||
</ul>
|
||
<p>Note the green-highlighted fields in the UCXLog settings: IP and port must be filled in.</p>
|
||
<p>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 <code>127.0.0.1</code>.</p>
|
||
<h3 id="qartest-(ik3qar)" tabindex="-1"><a class="header-anchor" href="#qartest-(ik3qar)">QARTest (IK3QAR)</a></h3>
|
||
<p><img src="qartest_logsync.png" alt="QARTest Configuration"></p>
|
||
<p><strong>Special feature</strong>: QARTest can send the <strong>complete log</strong> to KST4Contest (button “Invia log completo” in the QARTest settings). This means QSOs logged before KST4Contest was started are also captured.</p>
|
||
<p><strong>Settings in QARTest:</strong></p>
|
||
<ul>
|
||
<li>Configure UDP broadcast and IP/port as with UCXLog</li>
|
||
<li>Use “Invia log completo” for a full log upload</li>
|
||
</ul>
|
||
<p><em>(„Buona funzionalità caro IK3QAR!" – DO5AMF)</em></p>
|
||
<h3 id="n1mm%2B" tabindex="-1"><a class="header-anchor" href="#n1mm%2B">N1MM+</a></h3>
|
||
<p><strong>Settings in N1MM+:</strong></p>
|
||
<p>In N1MM+ under <code>Config → Configure Ports, Mode Control, Winkey, etc. → Broadcast Data</code>:</p>
|
||
<ul>
|
||
<li>Enable <code>Radio Info</code> (for TRX sync / QRG)</li>
|
||
<li>Enable <code>Contact Info</code> (for QSO sync)</li>
|
||
<li>IP: <code>127.0.0.1</code> (or IP of the KST4Contest computer)</li>
|
||
<li>Port: 12060</li>
|
||
</ul>
|
||
<p>For the built-in DX cluster server: configure N1MM+ as a DX cluster client (server: <code>127.0.0.1</code>, port as set in KST4Contest).</p>
|
||
<h3 id="dxlog.net" tabindex="-1"><a class="header-anchor" href="#dxlog.net"><a href="http://DXLog.net">DXLog.net</a></a></h3>
|
||
<p><img src="dxlog_net_logsync.png" alt="DXLog.net Configuration"></p>
|
||
<p><strong>Settings in <a href="http://DXLog.net">DXLog.net</a>:</strong></p>
|
||
<ul>
|
||
<li>Enable UDP broadcast</li>
|
||
<li>Enter the IP of the KST4Contest computer (green-highlighted fields)</li>
|
||
<li>Port: 12060</li>
|
||
</ul>
|
||
<h3 id="win-test" tabindex="-1"><a class="header-anchor" href="#win-test">Win-Test</a></h3>
|
||
<p>Win-Test is supported with a dedicated UDP network listener that understands the native Win-Test network protocol.</p>
|
||
<p><strong>Advantages of Win-Test Integration:</strong></p>
|
||
<ul>
|
||
<li>Automatic QSO synchronization to mark worked stations.</li>
|
||
<li><strong>Sked Handover (ADDSKED):</strong> Using the “Create sked” button in the station info panel not only creates a sked in KST4Contest but also <em>sends it directly via UDP to the Win-Test network as an ADDSKED packet</em> – automatically, as soon as the listener is active. No separate toggle is needed.</li>
|
||
<li>You can choose between “AUTO”, “SSB”, or “CW” sked modes.</li>
|
||
<li><strong>Automatic QRG resolution for SKEDs:</strong> KST4Contest selects the sked frequency intelligently:
|
||
<ol>
|
||
<li>If the other station mentioned their QRG in a recent chat message, that frequency is used.</li>
|
||
<li>Otherwise, your own current QRG is used (from Win-Test STATUS or manual entry).</li>
|
||
</ol>
|
||
</li>
|
||
</ul>
|
||
<p><strong>Settings in the “Log Synchronisation” tab:</strong></p>
|
||
<ul>
|
||
<li>Enable <code>Receive Win-Test network based UDP log messages</code>.</li>
|
||
<li><code>UDP-Port for Win-Test listener</code> (default: 9871).</li>
|
||
<li><code>KST station name in Win-Test network (src of SKED packets)</code>: Defines the station name KST4Contest uses in the WT network (e.g. “KST”).</li>
|
||
<li><code>Win-Test network broadcast address</code>: Usually detected automatically; required to send sked packets to the network.</li>
|
||
</ul>
|
||
<p><strong>Settings in the “TRX Synchronisation” tab:</strong></p>
|
||
<ul>
|
||
<li><code>Win-Test STATUS QRG Sync</code>: When enabled, KST4Contest takes the current transceiver frequency from the Win-Test STATUS packet and uses it as your own QRG (MYQRG).</li>
|
||
<li><code>Use pass frequency from Win-Test STATUS</code>: Instead of the main TRX frequency, the pass frequency contained in the STATUS packet is used as MYQRG (useful for multi-op setups that operate with a dedicated pass QRG).</li>
|
||
<li><code>Win-Test station name filter</code>: If a name is entered here (e.g. “STN1”), KST4Contest only processes packets from that specific Win-Test instance. Leave empty to accept all.</li>
|
||
</ul>
|
||
<p><strong>Settings in Win-Test:</strong></p>
|
||
<ul>
|
||
<li>The network in Win-Test must be active.</li>
|
||
<li>Win-Test must be configured to send/receive its broadcasts on the corresponding port (default 9871).</li>
|
||
</ul>
|
||
<hr>
|
||
<h2 id="trx-frequency-synchronisation" tabindex="-1"><a class="header-anchor" href="#trx-frequency-synchronisation">TRX Frequency Synchronisation</a></h2>
|
||
<p>In addition to QSO synchronisation, UCXLog and other programs also transmit the <strong>current transceiver frequency</strong> via UDP. KST4Contest processes this information and makes it available as the <code>MYQRG</code> variable.</p>
|
||
<p><img src="qrg_buttons.png" alt="Frequency Buttons"></p>
|
||
<p><strong>Result</strong>: 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.</p>
|
||
<p><strong>Sources for your own QRG (MYQRG):</strong></p>
|
||
<ul>
|
||
<li>UCXLog, N1MM+, <a href="http://DXLog.net">DXLog.net</a>, QARTest via UDP port 12060</li>
|
||
<li>Win-Test STATUS packet (optional, configurable in the “TRX Synchronisation” tab under “Win-Test STATUS QRG Sync”)</li>
|
||
<li>Manual entry in the QRG field</li>
|
||
</ul>
|
||
<blockquote>
|
||
<p><strong>Note for multi-setup</strong>: With two logging programs on two computers, only <strong>one</strong> should send frequency packets. KST4Contest cannot distinguish between sources and processes all incoming packets.</p>
|
||
</blockquote>
|
||
<hr>
|
||
<h2 id="multi-setup%3A-2-radios%2C-2-computers" tabindex="-1"><a class="header-anchor" href="#multi-setup%3A-2-radios%2C-2-computers">Multi-Setup: 2 Radios, 2 Computers</a></h2>
|
||
<p>For DM5M-style setups (2 radios, 2 computers, one KST4Contest instance or two separate):</p>
|
||
<p><strong>Option A – One shared KST4Contest instance:</strong></p>
|
||
<ul>
|
||
<li>Both logging programs send QSO packets to the IP of the KST4Contest computer</li>
|
||
<li>Only one logging program sends frequency packets (recommended: the VHF logging program)</li>
|
||
</ul>
|
||
<p><strong>Option B – Two separate KST4Contest instances (recommended):</strong></p>
|
||
<ul>
|
||
<li>Each logging program communicates with its own KST4Contest instance via <code>127.0.0.1</code></li>
|
||
<li>Two separate chat logins</li>
|
||
<li>Better separation and fewer conflicts</li>
|
||
</ul>
|
||
<hr>
|
||
<h2 id="internal-database" tabindex="-1"><a class="header-anchor" href="#internal-database">Internal Database</a></h2>
|
||
<p>KST4Contest stores worked information in an internal <strong>SQLite database</strong>. This is independent of the logging program’s database and is only populated via the UDP broadcast.</p>
|
||
<p>Before each new contest: reset the database! → <a href="Configuration#worked-station-database-settings">Configuration – Worked Station Database Settings</a></p>
|
||
|
||
</div>
|
||
</section>
|
||
</main>
|
||
|
||
<footer class="site-footer">
|
||
<div class="footer-grid">
|
||
<div>
|
||
<strong>KST4Contest</strong>
|
||
<p>Contest-optimized ON4KST workflow for VHF/UHF/SHF operators.</p>
|
||
</div>
|
||
|
||
<div>
|
||
<strong>Project</strong>
|
||
<p><a href="/features/">Features</a></p>
|
||
<p><a href="/download/">Download</a></p>
|
||
<p><a href="/manual/">Manual</a></p>
|
||
<p><a href="/roadmap/">Roadmap</a></p>
|
||
</div>
|
||
|
||
<div>
|
||
<strong>Community</strong>
|
||
<p><a href="https://github.com/praktimarc/kst4contest">GitHub Repository</a></p>
|
||
<p><a href="https://github.com/praktimarc/kst4contest/issues">Issues</a></p>
|
||
<p><a href="/contact/">Contact</a></p>
|
||
<p><a href="/support/">❤️ Support KST4Contest</a></p>
|
||
</div>
|
||
|
||
<div>
|
||
<strong>Legal</strong>
|
||
<p><a href="/legal-notice/">Legal Notice</a></p>
|
||
<p><a href="/privacy/">Privacy Policy</a></p>
|
||
</div>
|
||
</div>
|
||
</footer>
|
||
|
||
|
||
|
||
</body>
|
||
</html> |