Improve manual landing pages

This commit is contained in:
Marc Froehlich
2026-07-06 03:00:18 +02:00
parent db83d6a9df
commit 248a7c0462
21 changed files with 3897 additions and 0 deletions
@@ -0,0 +1,120 @@
<!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/dx-cluster-server/">
<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/dx-cluster-server/">
<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">
</head>
<body>
<header class="site-header">
<a class="brand" href="/">KST4Contest</a>
<nav>
<a href="/features/">Features</a>
<a href="/download/">Download</a>
<a href="/manual/">Manual</a>
<a href="/screenshots/">Screenshots</a>
<a href="/news/">News</a>
<a href="https://github.com/praktimarc/kst4contest">GitHub</a>
<a href="/faq/">FAQ</a>
</nav>
</header>
<main>
<section class="section">
<div class="card manual-content">
<p><a href="/manual/en/">← Back to manual overview</a></p>
<h1>DX Cluster Server</h1>
<h1 id="built-in-dx-cluster-server" tabindex="-1"><a class="header-anchor" href="#built-in-dx-cluster-server">Built-in DX Cluster Server</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-DX-Cluster-Server">Deutsche Version</a></p>
</blockquote>
<p>From <strong>version 1.23</strong>, KST4Contest includes a built-in DX cluster server. It sends spots directly to the logging software whenever a direction warning is triggered.</p>
<p><em>(Idea by OM0AAO, Viliam Petrik thank you!)</em></p>
<hr>
<h2 id="what-is-the-built-in-dx-cluster-server-for%3F" tabindex="-1"><a class="header-anchor" href="#what-is-the-built-in-dx-cluster-server-for%3F">What is the Built-in DX Cluster Server For?</a></h2>
<p>When KST4Contest detects that a station is requesting a sked from your direction and a QRG is known, it <strong>automatically generates a DX cluster spot</strong> and feeds it directly to the logging softwares cluster client / band map.</p>
<p>The logging software then displays the spot in the band map. Clicking the spot sets the transceivers frequency and mode directly without any manual typing.</p>
<hr>
<h2 id="setup" tabindex="-1"><a class="header-anchor" href="#setup">Setup</a></h2>
<h3 id="in-kst4contest" tabindex="-1"><a class="header-anchor" href="#in-kst4contest">In KST4Contest</a></h3>
<p>In Preferences → <strong>DX Cluster Server Settings</strong>:</p>
<ol>
<li>Enter the <strong>port</strong> of the internal server (e.g. 7300 or 8000 must match the logging software).</li>
<li>Enter a <strong>spotter callsign</strong> <strong>this must be a different callsign than your contest callsign!</strong>
<ul>
<li>Reason: Logging programs filter spots from your own callsign as “already worked”. If the spotter uses the same callsign, the spots will not be displayed.</li>
</ul>
</li>
<li>Enter the <strong>assumed MHz</strong>: For frequency references like “.205” in the chat, KST4Contest needs to decide whether 144.205, 432.205 or 1296.205 is meant. For single-band contests, simply enter the corresponding band centre. Full frequency references like “144.205” or “1296.338” in the chat are always correctly identified.</li>
</ol>
<h3 id="in-ucxlog" tabindex="-1"><a class="header-anchor" href="#in-ucxlog">In UCXLog</a></h3>
<ul>
<li>Configure a DX cluster server connection:
<ul>
<li>Host: <code>127.0.0.1</code> (or IP of the KST4Contest computer)</li>
<li>Port: As configured in KST4Contest</li>
<li>Password: can be left empty</li>
</ul>
</li>
<li>Use the <strong>“Send a test message to your log”</strong> button to test the connection.</li>
</ul>
<h3 id="in-n1mm%2B" tabindex="-1"><a class="header-anchor" href="#in-n1mm%2B">In N1MM+</a></h3>
<p>Similar settings:</p>
<ul>
<li>Host: <code>127.0.0.1</code> (or IP of the KST4Contest computer)</li>
<li>Port: As configured in KST4Contest</li>
</ul>
<hr>
<h2 id="how-it-works" tabindex="-1"><a class="header-anchor" href="#how-it-works">How It Works</a></h2>
<p>A spot is generated when <strong>both</strong> conditions are met:</p>
<ol>
<li>A <strong>direction warning</strong> has been triggered (station is making a sked in your direction).</li>
<li>The <strong>stations QRG is known</strong> (read from the chat or manually entered).</li>
</ol>
<p>The generated spot contains:</p>
<ul>
<li>Stations callsign</li>
<li>Frequency</li>
<li>Spot time</li>
</ul>
<p>The logging software can then display the spot in the band map and tune the TRX to that frequency with a mouse click.</p>
<hr>
<h2 id="multi-computer-setup" tabindex="-1"><a class="header-anchor" href="#multi-computer-setup">Multi-Computer Setup</a></h2>
<p>If KST4Contest runs on a separate computer (not the logging computer):</p>
<ul>
<li>Host in the logging software: IP of the KST4Contest computer (not <code>127.0.0.1</code>)</li>
<li>Same configuration as for the QSO UDP broadcast packets (see <a href="en-Log-Sync">Log Synchronisation</a>)</li>
</ul>
<hr>
<h2 id="tested-logging-software" tabindex="-1"><a class="header-anchor" href="#tested-logging-software">Tested Logging Software</a></h2>
<ul>
<li><strong>UCXLog</strong></li>
<li><strong>N1MM+</strong></li>
</ul>
<p>Further test reports are welcome please send by email to DO5AMF.</p>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>