Rsclub2_2/kst4contest
1
0
Fork 0
mirror of https://github.com/praktimarc/kst4contest.git synced 2026-07-13 16:16:44 +02:00
Code Issues Packages Projects Releases Wiki Activity

Improve manual landing pages

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files
website/_site/manual/en/airscout-integration/index.html
+156
View File
@@ -0,0 +1,156 @@
<!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/airscout-integration/">
<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/airscout-integration/">
<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>AirScout Integration</h1>
<h1 id="airscout-integration" tabindex="-1"><a class="header-anchor" href="#airscout-integration">AirScout Integration</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-AirScout-Integration">Deutsche Version</a></p>
</blockquote>
<p>AirScout (by DL2ALF) is a program for detecting aircraft for aircraft scatter operation. KST4Contest is tightly integrated with AirScout and shows reflectable aircraft directly in the user list.</p>
<blockquote>
<p><strong>Aircraft Scatter</strong> enables very long-distance communication on VHF and higher – even for stations with low altitude above sea level or unfavourable topographic conditions.</p>
</blockquote>
<hr>
<h2 id="downloading-airscout" tabindex="-1"><a class="header-anchor" href="#downloading-airscout">Downloading AirScout</a></h2>
<p>Download AirScout from:</p>
<ul>
<li><a href="http://airscout.eu/index.php/download">http://airscout.eu/index.php/download</a></li>
</ul>
<hr>
<h2 id="aircraft-data-feeds-(adsb)" tabindex="-1"><a class="header-anchor" href="#aircraft-data-feeds-(adsb)">Aircraft Data Feeds (ADSB)</a></h2>
<p>Public aircraft data feeds on the internet are often unreliable and limited in use. A recommended alternative is the dedicated ADSB feed service provided by <strong>OV3T (Thomas)</strong>:</p>
<ul>
<li><a href="https://airscatter.dk/">https://airscatter.dk/</a></li>
<li><a href="https://www.facebook.com/groups/825093981868542">https://www.facebook.com/groups/825093981868542</a></li>
</ul>
<p>An account is required for this service. Please consider donating to Thomas – the server costs are not free!</p>
<hr>
<h2 id="setting-up-airscout" tabindex="-1"><a class="header-anchor" href="#setting-up-airscout">Setting Up AirScout</a></h2>
<h3 id="step-1%3A-configure-the-adsb-feed-in-airscout" tabindex="-1"><a class="header-anchor" href="#step-1%3A-configure-the-adsb-feed-in-airscout">Step 1: Configure the ADSB Feed in AirScout</a></h3>
<ol>
<li>Start AirScout.</li>
<li>Enter your OV3T feed account details (username, password, URL) in the AirScout settings.</li>
</ol>
<p><img src="as_plane_feed_1.png" alt="AirscoutStep1">
<img src="as_plane_feed_2.png" alt="AirscoutStep2"></p>
<ol start="3">
<li>Test the connection.</li>
</ol>
<h3 id="step-2%3A-enable-udp-communication-for-kst4contest" tabindex="-1"><a class="header-anchor" href="#step-2%3A-enable-udp-communication-for-kst4contest">Step 2: Enable UDP Communication for KST4Contest</a></h3>
<p>In AirScout, enable the UDP interface:</p>
<ul>
<li>Activate the corresponding checkbox in the AirScout settings (only one checkbox needed).</li>
<li>Do not change the default ports unless there is a specific reason.</li>
</ul>
<h3 id="step-3%3A-kst4contest-settings" tabindex="-1"><a class="header-anchor" href="#step-3%3A-kst4contest-settings">Step 3: KST4Contest Settings</a></h3>
<p>In KST4Contest Preferences → <strong>AirScout Settings</strong>:</p>
<ul>
<li>Enable AirScout communication</li>
<li>Leave IP and port at their default values (unless changed)</li>
</ul>
<p><img src="as_plane_feed_3.png" alt="AirscoutStep3">{ width=85% }</p>
<hr>
<h2 id="communication-between-kst4contest-and-airscout-(from-v1.263)" tabindex="-1"><a class="header-anchor" href="#communication-between-kst4contest-and-airscout-(from-v1.263)">Communication Between KST4Contest and AirScout (from v1.263)</a></h2>
<p><strong>Improvement in v1.263</strong>: KST4Contest now only sends stations to AirScout whose QRB (distance) is less than the configured <strong>maximum QRB</strong>. The query interval has been extended from 12 seconds to <strong>60 seconds</strong>.</p>
<p><strong>Benefits:</strong></p>
<ul>
<li>Significantly less computation load for AirScout</li>
<li>Significantly less message traffic</li>
<li>The tracking issue with the “Show Path in AirScout” button is greatly improved</li>
<li>Less overall CPU usage</li>
</ul>
<p>Additionally: The name of the KST4Contest client and AirScout server was previously hardcoded (<code>KST</code> and <code>AS</code>). From v1.263, the names configured in the Preferences are used.</p>
<hr>
<h2 id="multiple-kst4contest-instances-and-airscout" tabindex="-1"><a class="header-anchor" href="#multiple-kst4contest-instances-and-airscout">Multiple KST4Contest Instances and AirScout</a></h2>
<blockquote>
<p><strong>Note</strong>: If multiple KST4Contest instances are running simultaneously and AirScout communication is enabled on both, AirScout will respond <strong>to both instances</strong>.</p>
</blockquote>
<p>This is not a problem if:</p>
<ul>
<li>Both instances use the same locator, <strong>or</strong></li>
<li>Both instances have different login callsigns.</li>
</ul>
<p>Otherwise, it may result in incorrect AP data.</p>
<hr>
<h2 id="ap-column-in-the-user-list" tabindex="-1"><a class="header-anchor" href="#ap-column-in-the-user-list">AP Column in the User List</a></h2>
<p>After setup, an <strong>AP column</strong> appears in the user list showing up to two reflectable aircraft per station.</p>
<p>Example display:</p>
<table>
<thead>
<tr>
<th>Station</th>
<th>AP Info</th>
</tr>
</thead>
<tbody>
<tr>
<td>DF9QX</td>
<td>2 Planes: 0 min / 0 min, 100% each</td>
</tr>
<tr>
<td>F5DYD</td>
<td>2 Planes: 14 min / 31 min, 50% each</td>
</tr>
</tbody>
</table>
<p>AP information is also available in the <strong>private messages window</strong>.</p>
<p>The percentage indicates the reflection potential (aircraft size, altitude, distance).</p>
<hr>
<h2 id="ap-variables-in-messages" tabindex="-1"><a class="header-anchor" href="#ap-variables-in-messages">AP Variables in Messages</a></h2>
<p>Aircraft data can be inserted directly into messages:</p>
<ul>
<li><code>FIRSTAP</code> → e.g. <code>a very big AP in 1 min</code></li>
<li><code>SECONDAP</code> → e.g. <code>Next big AP in 9 min</code></li>
</ul>
<p>Details: <a href="Macros-and-Variables#variables">Macros and Variables</a></p>
<hr>
<h2 id="%E2%80%9Cshow-path-in-airscout%E2%80%9D-button" tabindex="-1"><a class="header-anchor" href="#%E2%80%9Cshow-path-in-airscout%E2%80%9D-button">“Show Path in AirScout” Button</a></h2>
<p>In the user list there is a button with an arrow showing the direction (QTF) to the selected station. Clicking it maximises AirScout and shows the path with reflectable aircraft to the selected contact.</p>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/changelog/index.html
+293
View File
@@ -0,0 +1,293 @@
<!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/changelog/">
<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/changelog/">
<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>Changelog</h1>
<h1 id="changelog" tabindex="-1"><a class="header-anchor" href="#changelog">Changelog</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Changelog">Deutsche Version</a></p>
</blockquote>
<p>Version history of KST4Contest / PraktiKST.</p>
<hr>
<p>For the latest changelog, please refer to GitHub. The previous changelog is below.</p>
<h2 id="v1.41" tabindex="-1"><a class="header-anchor" href="#v1.41">v1.41</a></h2>
<p><strong>Station Map, Performance, Responsive UI</strong></p>
<p><strong>New:</strong></p>
<ul>
<li><strong>Station Map</strong>: Interactive OpenStreetMap-based map showing the geographic position of all active chat members. Includes station markers, antenna beam cone, connection line to the selected station, Maidenhead grid overlay, and a path profile chart with terrain elevation analysis (Fresnel zones, horizon detection). Terrain data from Copernicus GLO-30, Open-Meteo API, or offline DEM import. Aircraft scatter path analysis integrated. Works in AppImage and Flatpak without external CDN access (local tile proxy, bundled Leaflet.js).</li>
</ul>
<p><strong>Changed:</strong></p>
<ul>
<li><strong>Message table limit raised to 30,000</strong>: Chat and message tables are capped at 30,000 entries. Older messages are automatically discarded, keeping performance stable during multi-day contest operations.</li>
<li><strong>Screen-aware window sizing</strong>: On startup, the main window is sized to fit the current screen. If KST4Contest was last used on a larger monitor, the window is automatically scaled down. The UI layout is more compact and responsive on smaller screens.</li>
</ul>
<hr>
<h2 id="v1.40-(2026-02-16)" tabindex="-1"><a class="header-anchor" href="#v1.40-(2026-02-16)">v1.40 (2026-02-16)</a></h2>
<p><strong>Major Feature Release: Score System, AP Timeline, Win-Test, PSTRotator</strong></p>
<p><strong>New:</strong></p>
<ul>
<li><strong>Chatmember Score System</strong>: Every chat member is automatically scored based on antenna direction, activity time, message count, active bands, frequencies, sked direction (degrees), and other factors. Top candidates are highlighted in a dedicated list.</li>
<li><strong>AP Timeline</strong>: For each minute of possible aircraft arrival, up to 4 highly-scored stations are shown that should be workable. Aircraft with the highest potential are preferred over the fastest arrival. Chat members whose antenna is not pointing towards you are shown transparently.</li>
<li><strong>Win-Test Support</strong> (Beta since v1.31, now fully configurable): Log synchronisation, frequency parsing and <strong>sked handover via UDP</strong> fully integrated. Can be enabled/disabled in Preferences.</li>
<li><strong>PSTRotator Interface</strong> (Beta since v1.31, now fully configurable): Rotator position updates directly from KST4Contest. Can be enabled/disabled in Preferences.</li>
<li><strong>QSO Sniffer</strong>: Messages from configurable callsign lists are automatically forwarded to the PM window.</li>
<li><strong>Band Alert for logged stations</strong>: When a station is logged, a hint appears if that station has another active band that you are also QRV on.</li>
<li><strong>Sked Reminder ALERT</strong>: A sked alarm with automatic messages in configurable intervals (2+1 / 5+2+1 / 10+5+2+1 minutes before the sked) can be set up for each chat member, plus acoustic and visual notification.</li>
<li><strong>Load chat history on startup</strong>: Chat server history is loaded on connect to immediately see active members and recent messages.</li>
<li><strong>Skedfail button</strong>: In the FurtherInfo panel, a sked failure can be marked for a chat member, which lowers their priority score.</li>
</ul>
<p><strong>Changed:</strong></p>
<ul>
<li>AP notes added to internal DX cluster spots.</li>
<li>Chat member table scrolling follows the current message selection automatically.</li>
<li>Generic auto-reply and QRG auto-reply now fire a maximum of once every 45 seconds per callsign (prevents spam and message ping-pong).</li>
<li>New saveable settings: ServerDNS/Port, PSTRotator interface, Win-Test interface, callsign sniffer, Dark Mode on by default.</li>
<li>Date column removed from chat table (time only – saves space).</li>
</ul>
<p><strong>Fixed:</strong></p>
<ul>
<li>User list now automatically sorted on every new member sign-on.</li>
<li>Posonpill messages now terminate exactly one client instance (no longer affects all instances or wtKST).</li>
<li>wtKST: crash on KST4Contest disconnection fixed.</li>
<li>Multiple issues with callsign suffixes like <code>/p</code>, <code>-2</code>, etc. fixed throughout.</li>
<li><code>QTFDefault</code> was not saved correctly → fixed.</li>
<li>AirScout watchlist (ASWATCHLIST) was not being updated → fixed.</li>
<li>Dark Mode: QRG fields not displayed at full size → fixed.</li>
<li>Version number display corrected.</li>
</ul>
<hr>
<h2 id="v1.31-(2025-12-13)" tabindex="-1"><a class="header-anchor" href="#v1.31-(2025-12-13)">v1.31 (2025-12-13)</a></h2>
<p><strong>Win-Test + PSTRotator Beta, QSO Sniffer, DNS Hotfix</strong></p>
<p><strong>New:</strong></p>
<ul>
<li><strong>Win-Test support</strong> (Beta, not yet deactivatable): Log synchronisation and frequency parsing.</li>
<li><strong>PSTRotator support</strong> (Beta, not yet deactivatable).</li>
<li><strong>QSO Sniffer</strong>: Messages from configurable callsigns are forwarded to the PM window.</li>
</ul>
<p><strong>Changed:</strong></p>
<ul>
<li><strong>DNS server changed</strong>: From <code>www.on4kst.info</code> to <code>www.on4kst.org</code> (hotfix). The DNS server is now configurable in Preferences.</li>
</ul>
<p><strong>Fixed:</strong></p>
<ul>
<li>Endless loop in error case freezes the client → fixed.</li>
</ul>
<hr>
<h2 id="v1.266-(2025-10-03)" tabindex="-1"><a class="header-anchor" href="#v1.266-(2025-10-03)">v1.266 (2025-10-03)</a></h2>
<p><strong>AirScout Fix for Callsigns with Suffix</strong></p>
<p><strong>Fixed:</strong></p>
<ul>
<li>AirScout interface did not work when the login callsign contained a suffix (e.g. <code>9A1W-2</code>). AirScout cannot handle this format – only the base callsign without suffix is now passed to AirScout.</li>
</ul>
<p><em>(Bug reported and tested by 9A2HM / Kreso – many thanks!)</em></p>
<hr>
<h2 id="v1.265-(2025-09-28)" tabindex="-1"><a class="header-anchor" href="#v1.265-(2025-09-28)">v1.265 (2025-09-28)</a></h2>
<p><strong>Direction Buttons Stay Coloured When Active</strong></p>
<p><strong>Fixed:</strong></p>
<ul>
<li>Direction buttons (N / NE / E etc.) now keep their highlight colour when activated, making the active state immediately visible.</li>
</ul>
<hr>
<h2 id="v1.264-(2025-08-02)" tabindex="-1"><a class="header-anchor" href="#v1.264-(2025-08-02)">v1.264 (2025-08-02)</a></h2>
<p><strong>Simplelogfile: Improved Callsign Recognition</strong></p>
<p><strong>Fixed:</strong></p>
<ul>
<li>Callsigns like <code>S53CC</code>, <code>S51A</code>, etc. were not being marked as worked in the SimpleLogFile interpreter → recognition pattern improved.</li>
</ul>
<p><em>(Bug reported by Boris, S53CC – thank you!)</em></p>
<hr>
<h2 id="v1.263-(2025-06-08)" tabindex="-1"><a class="header-anchor" href="#v1.263-(2025-06-08)">v1.263 (2025-06-08)</a></h2>
<p><strong>AirScout Communication and Login Name</strong></p>
<p><strong>Changed:</strong></p>
<ul>
<li>AirScout communication fundamentally revised: Only stations with QRB &lt; max-QRB are now sent to AirScout.</li>
<li>Query interval extended from 12 seconds to <strong>60 seconds</strong>.</li>
<li>Significantly less computation load and message traffic → more stable AirScout tracking.</li>
<li>Name of the AS client and AS server is now configurable from the Preferences (was previously hardcoded to “KST” / “AS”).</li>
</ul>
<p><strong>Fixed:</strong></p>
<ul>
<li>“Track in AirScout” button was very sluggish → greatly improved by new communication logic.</li>
<li>Name in chat is now saveable (bug fixed).</li>
<li>Visual corrections before and after login.</li>
<li>Bug fixed that was reported by 9A2HM (Kreso).</li>
</ul>
<hr>
<h2 id="v1.262-(2025-05-21)" tabindex="-1"><a class="header-anchor" href="#v1.262-(2025-05-21)">v1.262 (2025-05-21)</a></h2>
<p><strong>Freeze Fix for Early Message Delivery</strong></p>
<p><strong>Fixed:</strong></p>
<ul>
<li>ON4KST sometimes delivers messages before login is complete. This caused errors in the message processing engine → now fixed.</li>
</ul>
<hr>
<h2 id="v1.26-(2025-05)" tabindex="-1"><a class="header-anchor" href="#v1.26-(2025-05)">v1.26 (2025-05)</a></h2>
<p><strong>Multi-Channel Login and Dark Mode</strong></p>
<p><strong>New:</strong></p>
<ul>
<li><strong>Dark Mode</strong>: Toggle via <code>Window → Use Dark Mode</code>.</li>
<li><strong>Multi-channel login</strong>: Simultaneous login to two chat categories.</li>
<li><strong>Opposite station multi-callsign login tagging</strong>: Support for stations with multiple callsigns.</li>
</ul>
<p><strong>Changed:</strong></p>
<ul>
<li>Colouring mechanism revised: Colours can now be customised via CSS.</li>
</ul>
<p><strong>Fixed:</strong></p>
<ul>
<li>Station tagging completely revised and corrected.</li>
</ul>
<hr>
<h2 id="v1.251-(2025-02)" tabindex="-1"><a class="header-anchor" href="#v1.251-(2025-02)">v1.251 (2025-02)</a></h2>
<p><strong>Bugfix for UDP Broadcast Spot Info</strong></p>
<p><strong>Fixed:</strong></p>
<ul>
<li>Problem reading UDP broadcast spot information fixed (reported by Steve Clements – thank you!).</li>
<li>Station tagging (further improved).</li>
</ul>
<hr>
<h2 id="v1.25-(2025-02)" tabindex="-1"><a class="header-anchor" href="#v1.25-(2025-02)">v1.25 (2025-02)</a></h2>
<p><strong>Wishlist Time</strong></p>
<p><strong>New:</strong></p>
<ul>
<li><strong>New settings tab: Messagehandling</strong>
<ul>
<li>Auto-reply to incoming messages configurable.</li>
<li>Automatic reply with own CQ QRG when someone asks for it.</li>
<li>Configurable default filter for the userinfo window <em>(for Gianluca :-) )</em>.</li>
</ul>
</li>
<li><strong>Coloured PM rows</strong>: New private messages appear red and fade every 30 seconds from yellow to white <em>(idea by IU3OAR, Gianluca)</em>.</li>
</ul>
<p><strong>Fixed:</strong></p>
<ul>
<li>Stations with suffixes like “-2” and “-70” were not being marked as worked → now ignored, station is correctly marked.</li>
</ul>
<hr>
<h2 id="v1.24-(2024-11)" tabindex="-1"><a class="header-anchor" href="#v1.24-(2024-11)">v1.24 (2024-11)</a></h2>
<p><strong>Wishlist + DX Cluster Spots</strong></p>
<p><strong>New:</strong></p>
<ul>
<li>Button to open the <strong><a href="http://QRZ.com">QRZ.com</a> profile</strong> of the selected station.</li>
<li>Button to open the <strong>QRZ-CQ profile</strong> of the selected station.</li>
<li><strong>DX Cluster Server integration</strong>: Direction warnings are sent as spots to the logging software (when QRG is known).</li>
</ul>
<p><em>(Coloured PM row feature also added – tnx Gianluca)</em></p>
<hr>
<h2 id="v1.23-(2024-10)" tabindex="-1"><a class="header-anchor" href="#v1.23-(2024-10)">v1.23 (2024-10)</a></h2>
<p><strong>Built-in DX Cluster Server</strong></p>
<p><strong>New:</strong></p>
<ul>
<li>KST4Contest now contains a <strong>built-in DX cluster server</strong>.</li>
<li>Generates DX cluster spots and sends them to the logging software when a direction warning is triggered and a QRG is known.</li>
<li>Spotter callsign must differ from the contest callsign (for correct filtering in the logging software).</li>
</ul>
<p><em>(Idea by OM0AAO, Viliam Petrik – thank you!)</em></p>
<hr>
<h2 id="v1.22-(2024-05)" tabindex="-1"><a class="header-anchor" href="#v1.22-(2024-05)">v1.22 (2024-05)</a></h2>
<p><strong>Usability Improvements and AirScout Button Fix</strong></p>
<p><strong>New:</strong></p>
<ul>
<li>New variables (tnx OM0AAO, Viliam Petrik):
<ul>
<li><code>MYLOCATORSHORT</code></li>
<li><code>MYQRGSHORT</code></li>
<li><code>QRZNAME</code></li>
</ul>
</li>
</ul>
<p><strong>Changed:</strong></p>
<ul>
<li>Send field focus: After clicking a callsign in the user list, the send field immediately receives focus – no double-click needed <em>(tnx Gianluca)</em>.</li>
</ul>
<p><strong>Fixed:</strong></p>
<ul>
<li>Worked-station filter is now live: Worked stations disappear immediately when the filter is activated <em>(tnx Gianluca)</em>.</li>
<li>QRB sorting was lexicographic → now numeric <em>(tnx Alessandro Murador)</em>.</li>
<li>AirScout “Show Path” button: Click now maximises AirScout and correctly shows the path.</li>
</ul>
<hr>
<h2 id="v1.21-(2024-04)" tabindex="-1"><a class="header-anchor" href="#v1.21-(2024-04)">v1.21 (2024-04)</a></h2>
<p><strong>Usability Improvements</strong></p>
<p><strong>Changed:</strong></p>
<ul>
<li>Window sizes and divider positions are saved in the configuration file when clicking “Save Settings” and restored on startup.</li>
<li>Filter section as flowpane → better display on smaller screens.</li>
</ul>
<hr>
<h2 id="v1.2-(2024-04)" tabindex="-1"><a class="header-anchor" href="#v1.2-(2024-04)">v1.2 (2024-04)</a></h2>
<p><strong>Band Selection and NOT-QRV Tags</strong></p>
<p><strong>New:</strong></p>
<ul>
<li><strong>Band selection</strong>: Selectable in Preferences which bands are active. Only buttons and fields for selected bands appear in the UI. Save and restart required.</li>
<li><strong>NOT-QRV tags per station and band</strong>: Stations can be marked as “not QRV” for each band. Combinable with the user list filter.</li>
<li><strong>QTF arrow</strong>: The “Show path in AS” button now shows an arrow with the QTF of the selected station.</li>
</ul>
<hr>
<h2 id="earlier-versions" tabindex="-1"><a class="header-anchor" href="#earlier-versions">Earlier Versions</a></h2>
<h3 id="v1.1" tabindex="-1"><a class="header-anchor" href="#v1.1">v1.1</a></h3>
<p>First publicly released version. Core features:</p>
<ul>
<li>Worked marking via Simplelogfile and UDP</li>
<li>Sked direction highlighting</li>
<li>QRG detection</li>
<li>Text snippets and shortcuts</li>
<li>AirScout interface (first version)</li>
<li>Interval beacon</li>
<li>PM catching for public messages containing your own callsign</li>
<li>Update notification service</li>
</ul>
<hr>
<h2 id="planned-features" tabindex="-1"><a class="header-anchor" href="#planned-features">Planned Features</a></h2>
<ul>
<li><code>MYQTF</code> variable (own antenna direction as text)</li>
<li><s>Lifetime for worked status (automatic reset)</s> ✅ <strong>Implemented in v1.40</strong> (3-day lifetime, no manual reset needed anymore)</li>
<li>Filtering the “Cluster &amp; QSO of others” window to own QTF</li>
<li>Further topography-based calculations for direction warnings</li>
</ul>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/configuration/index.html
+200
View File
@@ -0,0 +1,200 @@
<!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/configuration/">
<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/configuration/">
<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>Configuration</h1>
<h1 id="configuration" tabindex="-1"><a class="header-anchor" href="#configuration">Configuration</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Konfiguration">Deutsche Version</a></p>
</blockquote>
<p>After the first start, the <strong>settings window</strong> opens – this is the central starting point for all configuration. It is recommended to keep the settings window open during operation (e.g. to quickly toggle the beacon on and off).</p>
<blockquote>
<p><strong>Important</strong>: Always click <strong>“Save Settings”</strong> after any change! Settings are stored in <code>~/.praktikst/preferences.xml</code> on Linux and in <code>%USERPROFILE%\.praktikst\preferences.xml</code> (or <code>C:\Users\&lt;Username&gt;\.praktikst\preferences.xml</code>) on Windows. From v1.21 onwards, window sizes and divider positions are also saved when you click Save.</p>
</blockquote>
<hr>
<h2 id="station-settings" tabindex="-1"><a class="header-anchor" href="#station-settings">Station Settings</a></h2>
<p><img src="client_settings_window_station.png" alt="Station Settings"></p>
<h3 id="login-and-chat-categories" tabindex="-1"><a class="header-anchor" href="#login-and-chat-categories">Login and Chat Categories</a></h3>
<p>Enter your ON4KST chat credentials here (callsign and password).
Also, select the <strong>primary chat category</strong> (e.g., IARU Region 1 VHF/Microwave).</p>
<p>With the option for a <strong>second chat</strong> (Multi-Channel Login), you can log in to another category simultaneously (e.g., UHF/SHF). Both chats will then be monitored in parallel. You can optionally specify a different login name for the second chat (useful for Opposite Station Multi-Callsign Logging).</p>
<h3 id="callsign-and-locator" tabindex="-1"><a class="header-anchor" href="#callsign-and-locator">Callsign and Locator</a></h3>
<p>Enter your own callsign and Maidenhead locator (6 characters, e.g., <code>JN49IJ</code>). These values are needed for distance and direction calculations.</p>
<h3 id="active-bands" tabindex="-1"><a class="header-anchor" href="#active-bands">Active Bands</a></h3>
<p>Use the <strong>“my station uses band”</strong> checkboxes to select the active bands. Buttons and table rows will only appear in the user interface for selected bands. The software must be restarted after making changes.</p>
<h3 id="antenna-beamwidth" tabindex="-1"><a class="header-anchor" href="#antenna-beamwidth">Antenna Beamwidth</a></h3>
<p>Enter a realistic value for your antenna’s beamwidth (in degrees). This value is used for the <a href="Features#sked-direction-highlighting">Sked Direction Highlighting</a>. A test value of 50° has proven effective; DM5M uses quads with 69°.</p>
<blockquote>
<p><strong>Do not</strong> enter fantasy values – the direction calculations will become useless.</p>
</blockquote>
<h3 id="default-maximum-qrb" tabindex="-1"><a class="header-anchor" href="#default-maximum-qrb">Default Maximum QRB</a></h3>
<p>Maximum distance (in km) for which direction warnings should be triggered. A realistic value for DM5M is 900 km. Stations farther away are ignored for highlighting purposes.</p>
<hr>
<h2 id="server-settings-(from-v1.31)" tabindex="-1"><a class="header-anchor" href="#server-settings-(from-v1.31)">Server Settings (from v1.31)</a></h2>
<p>The chat server DNS and port are configurable in the Preferences:</p>
<ul>
<li><strong>Server DNS</strong>: Default <code>www.on4kst.org</code> (changed from <code>www.on4kst.info</code> in v1.31 hotfix).</li>
<li><strong>Port</strong>: Default port of the ON4KST server.</li>
</ul>
<p>A change is only needed if the server moves or an alternative endpoint is used.</p>
<hr>
<h2 id="log-sync-settings" tabindex="-1"><a class="header-anchor" href="#log-sync-settings">Log Sync Settings</a></h2>
<p>Three methods are available for automatically marking worked stations. Details: <a href="en-Log-Sync">Log Synchronisation</a>.</p>
<h3 id="universal-file-based-callsign-interpreter-(simplelogfile)" tabindex="-1"><a class="header-anchor" href="#universal-file-based-callsign-interpreter-(simplelogfile)">Universal File Based Callsign Interpreter (Simplelogfile)</a></h3>
<p>Interprets any log file using regex for callsign patterns. No band information is available. Suitable as a fallback or for log programs that are not directly supported.</p>
<h3 id="network-listener-for-logger%E2%80%99s-qso-udp-broadcast" tabindex="-1"><a class="header-anchor" href="#network-listener-for-logger%E2%80%99s-qso-udp-broadcast">Network Listener for Logger’s QSO UDP Broadcast</a></h3>
<p><strong>Recommended method.</strong> KST4Contest listens for UDP packets sent by the logging software to the broadcast address when a QSO is saved. Stations are marked with band information. UDP port: default <strong>12060</strong>. (Used by UCXLog, N1MM+, QARTest, <a href="http://DXLog.net">DXLog.net</a>, etc.).</p>
<h3 id="win-test-network-listener-(additional-udp-listener)" tabindex="-1"><a class="header-anchor" href="#win-test-network-listener-(additional-udp-listener)">Win-Test Network Listener (Additional UDP Listener)</a></h3>
<p>A dedicated network listener for Win-Test. KST4Contest receives and processes Win-Test-specific UDP packets (including sked handovers) on the configured port.</p>
<hr>
<h2 id="trx-sync-settings" tabindex="-1"><a class="header-anchor" href="#trx-sync-settings">TRX Sync Settings</a></h2>
<p>Receives the current transceiver frequency from the logging software via UDP. This enables the automatic population of the <code>MYQRG</code> variable. Useful for:</p>
<ul>
<li>Quickly inserting your own QRG into chat messages.</li>
<li>Automatic CQ beacon with current frequency.</li>
</ul>
<blockquote>
<p><strong>Note for multi-setup</strong>: When running two logging programs on two computers but only one KST4Contest instance, only one logging program should send frequency packets. KST4Contest cannot distinguish between sources.</p>
</blockquote>
<hr>
<h2 id="airscout-settings" tabindex="-1"><a class="header-anchor" href="#airscout-settings">AirScout Settings</a></h2>
<p>Configuration of the interface to AirScout for aircraft scatter detection. Details: <a href="en-AirScout-Integration">AirScout Integration</a>.</p>
<hr>
<h2 id="notification-settings" tabindex="-1"><a class="header-anchor" href="#notification-settings">Notification Settings</a></h2>
<p>Three notification types are available:</p>
<ol>
<li><strong>Simple sounds</strong>: TADA sound for incoming messages, tick for sked direction detection, etc.</li>
<li><strong>CW announcement</strong>: The callsign of a station sending a private message is output as a CW signal.</li>
<li><strong>Phonetic announcement</strong>: The callsign is pronounced phonetically.</li>
</ol>
<hr>
<h2 id="shortcut-settings" tabindex="-1"><a class="header-anchor" href="#shortcut-settings">Shortcut Settings</a></h2>
<p>Configuration of quick-access buttons that appear directly in the main window. Clicking a button inserts the configured text into the send field. All <a href="Macros-and-Variables#variables">variables</a> can be used.</p>
<hr>
<h2 id="snippet-settings" tabindex="-1"><a class="header-anchor" href="#snippet-settings">Snippet Settings</a></h2>
<p>Text snippets are accessible via:</p>
<ul>
<li><strong>Right-click</strong> on a callsign in the user list</li>
<li><strong>Right-click</strong> in the CQ message table</li>
<li><strong>Right-click</strong> in the PM message table</li>
<li><strong>Keyboard shortcuts</strong>: <code>Ctrl+1</code> to <code>Ctrl+0</code> for the first 10 snippets</li>
</ul>
<p>If a callsign is selected in the user list, the snippet is addressed as a direct message:
<code>/CQ CALLSIGN &lt;snippet text&gt;</code></p>
<hr>
<h2 id="beacon-settings" tabindex="-1"><a class="header-anchor" href="#beacon-settings">Beacon Settings</a></h2>
<p>Configuration of an automatic interval beacon in the public chat channel. Recommended: use the <code>MYQRG</code> variable in the text so the current frequency is always up to date. Interval and text are freely configurable.</p>
<blockquote>
<p><strong>Tip</strong>: Enable the beacon when calling CQ and quickly disable it in the settings window when not calling.</p>
</blockquote>
<hr>
<h2 id="messagehandling-settings-(from-v1.25)" tabindex="-1"><a class="header-anchor" href="#messagehandling-settings-(from-v1.25)">Messagehandling Settings (from v1.25)</a></h2>
<p>New settings section with the following options:</p>
<ul>
<li><strong>Auto-reply to all incoming messages</strong>: Configurable automatic reply to private messages.</li>
<li><strong>Auto-reply with own CQ QRG</strong>: When someone asks for your QRG, KST4Contest automatically replies with the content of the <code>MYQRG</code> variable.</li>
<li><strong>Default filter for the userinfo window</strong>: Pre-configured message filter for the station info window <em>(for Gianluca :-) )</em>.</li>
</ul>
<hr>
<h2 id="win-test-network-listener-(from-v1.31)" tabindex="-1"><a class="header-anchor" href="#win-test-network-listener-(from-v1.31)">Win-Test Network Listener (from v1.31)</a></h2>
<p>A dedicated listener for Win-Test-specific UDP packets. Enables:</p>
<ul>
<li><strong>Log synchronisation</strong>: Worked stations are retrieved from Win-Test and marked in the user list.</li>
<li><strong>Frequency parsing</strong>: The current TRX frequency from Win-Test populates the <code>MYQRG</code> variable.</li>
<li><strong>Sked handover (SKED push)</strong>: Skeds from KST4Contest are passed directly to Win-Test via UDP. Win-Test’s default UDP broadcast port (9871) is used.</li>
</ul>
<p>Settings:</p>
<ul>
<li><strong>Enable/Disable</strong>: Checkbox in Preferences (from v1.40).</li>
<li><strong>Port</strong>: Configurable UDP port for the Win-Test listener.</li>
<li><strong>Sked UDP address and port</strong>: Target address and port for SKED handover to Win-Test.</li>
</ul>
<blockquote>
<p><strong>Note</strong>: The Win-Test listener is an <strong>additional</strong> listener – the standard QSO UDP broadcast listener on port 12060 remains independent.</p>
</blockquote>
<hr>
<h2 id="pstrotator-settings-(from-v1.31)" tabindex="-1"><a class="header-anchor" href="#pstrotator-settings-(from-v1.31)">PSTRotator Settings (from v1.31)</a></h2>
<p>KST4Contest can control antenna direction via PSTRotator.</p>
<p>Settings:</p>
<ul>
<li><strong>Enable/Disable</strong>: Checkbox in Preferences (from v1.40).</li>
<li><strong>IP address</strong>: IP address of the PSTRotator computer (default: <code>127.0.0.1</code> when running on the same PC).</li>
<li><strong>Port</strong>: Communication port of PSTRotator.</li>
</ul>
<blockquote>
<p><strong>Note</strong>: After clicking a direction button, KST4Contest waits briefly for the rotator response. With slow rotors (e.g. SPID) there may be a small delay.</p>
</blockquote>
<hr>
<h2 id="sniffer-settings-(from-v1.31)" tabindex="-1"><a class="header-anchor" href="#sniffer-settings-(from-v1.31)">Sniffer Settings (from v1.31)</a></h2>
<p>The QSO sniffer filters chat messages from configurable callsigns and forwards them to the PM window.</p>
<p>Settings:</p>
<ul>
<li><strong>Callsign list</strong>: Comma-separated list of callsigns whose messages are always forwarded to the PM window.</li>
</ul>
<p>Use case: Keep track of important stations (e.g. DX expeditions or trusted contest allies) without constantly monitoring the main chat.</p>
<hr>
<h2 id="worked-station-database-settings" tabindex="-1"><a class="header-anchor" href="#worked-station-database-settings">Worked Station Database Settings</a></h2>
<p>The internal worked database contains:</p>
<ul>
<li>Worked status of all stations (per band)</li>
<li>NOT-QRV tags (since v1.2)</li>
</ul>
<p><strong>From v1.40</strong>: Entries have an automatic lifetime of <strong>3 days</strong> – manually resetting before each contest is no longer strictly necessary. For a full reset, the <strong>“Reinitialize”</strong> button is still available.</p>
<hr>
<h2 id="dark-mode-(from-v1.26)" tabindex="-1"><a class="header-anchor" href="#dark-mode-(from-v1.26)">Dark Mode (from v1.26)</a></h2>
<p>Toggle via the menu: <strong>Window → Use Dark Mode</strong>. The colors can be individually customized via CSS.</p>
<hr>
<h2 id="saving-settings" tabindex="-1"><a class="header-anchor" href="#saving-settings">Saving Settings</a></h2>
<p>Click <strong>“Save Settings”</strong> after <strong>every</strong> change! Without saving, all changes will be lost on the next start.</p>
<ul>
<li>Storage location: <code>~/.praktikst/preferences.xml</code> on Linux and <code>%USERPROFILE%\.praktikst\preferences.xml</code> (or <code>C:\Users\&lt;Username&gt;\.praktikst\preferences.xml</code>) on Windows</li>
<li>From v1.21: Window sizes and divider positions are also saved.</li>
<li>If you encounter problems: delete the configuration file → KST4Contest will create a new one with default values.</li>
</ul>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/dx-cluster-server/index.html
+120
View File
@@ -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 software’s cluster client / band map.</p>
<p>The logging software then displays the spot in the band map. Clicking the spot sets the transceiver’s 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>station’s QRG is known</strong> (read from the chat or manually entered).</li>
</ol>
<p>The generated spot contains:</p>
<ul>
<li>Station’s 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>
website/_site/manual/en/features/index.html
+241
View File
@@ -0,0 +1,241 @@
<!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/features/">
<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/features/">
<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>Features</h1>
<h1 id="features" tabindex="-1"><a class="header-anchor" href="#features">Features</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Funktionen">Deutsche Version</a></p>
</blockquote>
<p>Overview of all main features of KST4Contest.</p>
<hr>
<h2 id="sked-direction-highlighting" tabindex="-1"><a class="header-anchor" href="#sked-direction-highlighting">Sked Direction Highlighting</a></h2>
<p>One of the core features: when a station makes a sked request <strong>towards your direction</strong>, it is highlighted <strong>green and bold</strong> in the user list.</p>
<h3 id="how-does-it-work%3F" tabindex="-1"><a class="header-anchor" href="#how-does-it-work%3F">How does it work?</a></h3>
<p>The calculation is based on the following logic:</p>
<ul>
<li>When station A sends a sked request to station B, it is assumed that A is pointing its antenna towards B.</li>
<li>If the resulting direction from A to your own station is within half the beamwidth of your own antenna, A is highlighted.</li>
</ul>
<p><strong>Example</strong> (beamwidth 69°, half-angle 34.5°):</p>
<table>
<thead>
<tr>
<th>Situation</th>
<th>Result for DO5AMF in JN49</th>
</tr>
</thead>
<tbody>
<tr>
<td>Sked from F5FEN → DM5M</td>
<td>✅ Highlighted (F5FEN points towards DM5M, close to JN49)</td>
</tr>
<tr>
<td>Sked from DM5M → F5FEN</td>
<td>✅ Highlighted (DM5M replies towards F5FEN)</td>
</tr>
<tr>
<td>F1DBN is uninvolved</td>
<td>❌ No highlighting</td>
</tr>
<tr>
<td>DO5AMF/P (different location)</td>
<td>❌ No highlighting for sked reply</td>
</tr>
</tbody>
</table>
<p>The calculation does not include topographic path calculations – this is a deliberate simplification. It may be added in a future version.</p>
<blockquote>
<p>Configuration: <a href="Configuration#antenna-beamwidth">Configuration – Antenna Beamwidth</a></p>
</blockquote>
<hr>
<h2 id="sked-direction-spots-(built-in-dx-cluster)" tabindex="-1"><a class="header-anchor" href="#sked-direction-spots-(built-in-dx-cluster)">Sked Direction Spots (Built-in DX Cluster)</a></h2>
<p>From <strong>v1.23</strong>: Direction warnings are forwarded as DX cluster spots to the logging software when a QRG is known. Details: <a href="en-DX-Cluster-Server">DX Cluster Server</a>.</p>
<hr>
<h2 id="qrg-detection-(qrg-reading)" tabindex="-1"><a class="header-anchor" href="#qrg-detection-(qrg-reading)">QRG Detection (QRG Reading)</a></h2>
<p>KST4Contest processes every line of text flowing through the channel and automatically extracts <strong>frequency references</strong>. These are displayed in the user list in the <strong>QRG column</strong>.</p>
<p>Recognised formats: <code>144.205</code>, <code>432.088</code>, <code>.205</code> (with configured band assumption), etc.</p>
<p><strong>Benefit</strong>: Without asking, you can directly look up a station’s calling frequency and decide whether a contact is possible.</p>
<hr>
<h2 id="worked-marking" tabindex="-1"><a class="header-anchor" href="#worked-marking">Worked Marking</a></h2>
<p>Worked stations are visually marked in the user list – per band. Based on <a href="en-Log-Sync">Log Synchronisation</a> via UDP or Simplelogfile.</p>
<p>Reset the database before each contest: <a href="Configuration#worked-station-database-settings">Configuration – Worked Station Database Settings</a>.</p>
<hr>
<h2 id="not-qrv-tags-(from-v1.2)" tabindex="-1"><a class="header-anchor" href="#not-qrv-tags-(from-v1.2)">NOT-QRV Tags (from v1.2)</a></h2>
<p>When a station indicates it is not QRV on a specific band, this can be manually marked:</p>
<ol>
<li>Select the station in the user list.</li>
<li>Right-click → Set NOT-QRV for the appropriate band.</li>
</ol>
<p>These tags are stored in the internal database and persist after a KST4Contest restart. Can be reset via the settings.</p>
<p><strong>Benefit</strong>: Prevents repeated sked requests on bands where the station is not active – saves time for both sides.</p>
<hr>
<h2 id="direction-filter" tabindex="-1"><a class="header-anchor" href="#direction-filter">Direction Filter</a></h2>
<p>Shows only stations in the user list that are located in a specific direction. Toggle using the N / NE / E / SE / S / SW / W / NW buttons or by entering degrees manually.</p>
<p>Useful: While calling CQ in a specific direction, only show stations in that direction.</p>
<hr>
<h2 id="distance-filter" tabindex="-1"><a class="header-anchor" href="#distance-filter">Distance Filter</a></h2>
<p>Hide stations beyond a maximum distance. The <strong>“Show only QRB [km] &lt;=”</strong> button is a toggle.</p>
<hr>
<h2 id="worked-and-not-qrv-filter" tabindex="-1"><a class="header-anchor" href="#worked-and-not-qrv-filter">Worked and NOT-QRV Filter</a></h2>
<p>Toggle buttons (one per band) to hide already-worked stations and/or NOT-QRV-tagged stations. The filter takes effect <strong>immediately</strong> without manually reactivating (live since v1.22).</p>
<hr>
<h2 id="coloured-pm-rows-(from-v1.25)" tabindex="-1"><a class="header-anchor" href="#coloured-pm-rows-(from-v1.25)">Coloured PM Rows (from v1.25)</a></h2>
<p>New private messages appear in <strong>red</strong>. The colour fades every 30 seconds from yellow to white – like a rainbow fade. This makes it immediately clear how recent a message is.</p>
<p><em>(Idea by IU3OAR, Gianluca Costantino – thank you!)</em></p>
<hr>
<h2 id="pm-catching" tabindex="-1"><a class="header-anchor" href="#pm-catching">PM Catching</a></h2>
<p>Some users accidentally post direct messages publicly, e.g.:</p>
<pre><code>(DM5M) pse ur qrg
</code></pre>
<p>KST4Contest detects such messages that contain your own callsign and automatically sorts them into the <strong>private messages table</strong>. No messages are missed this way.</p>
<hr>
<h2 id="multi-channel-login-(from-v1.26)" tabindex="-1"><a class="header-anchor" href="#multi-channel-login-(from-v1.26)">Multi-Channel Login (from v1.26)</a></h2>
<p>Simultaneous login to <strong>two chat categories</strong> (e.g. 144 MHz and 432 MHz). Both chats are monitored in parallel.</p>
<hr>
<h2 id="dark-mode-(from-v1.26)" tabindex="-1"><a class="header-anchor" href="#dark-mode-(from-v1.26)">Dark Mode (from v1.26)</a></h2>
<p>Toggle via: <strong>Window → Use Dark Mode</strong></p>
<p>For individual colour adjustments: edit the CSS file (path in the program settings).</p>
<hr>
<h2 id="opposite-station-multi-callsign-login-tagging-(from-v1.26)" tabindex="-1"><a class="header-anchor" href="#opposite-station-multi-callsign-login-tagging-(from-v1.26)">Opposite Station Multi-Callsign Login Tagging (from v1.26)</a></h2>
<p>Support for stations that are active in the chat with multiple callsigns simultaneously (e.g. expedition setups).</p>
<hr>
<h2 id="qrz.com-and-qrz-cq-profile-buttons-(from-v1.24)" tabindex="-1"><a class="header-anchor" href="#qrz.com-and-qrz-cq-profile-buttons-(from-v1.24)"><a href="http://QRZ.com">QRZ.com</a> and QRZ-CQ Profile Buttons (from v1.24)</a></h2>
<p>For selected stations in the user list, there are direct buttons to open the <strong><a href="http://QRZ.com">QRZ.com</a> profile</strong> and the <strong>QRZ-CQ profile</strong> in the browser.</p>
<hr>
<h2 id="sked-reminders-with-alert-(from-v1.40)" tabindex="-1"><a class="header-anchor" href="#sked-reminders-with-alert-(from-v1.40)">Sked Reminders with ALERT (from v1.40)</a></h2>
<p>A sked reminder service with automatic messages can be activated for each chat member. Configurable interval patterns:</p>
<ul>
<li><strong>2+1 minutes</strong>: Messages at 2 min and 1 min before the sked.</li>
<li><strong>5+2+1 minutes</strong>: Messages at 5, 2 and 1 min before the sked.</li>
<li><strong>10+5+2+1 minutes</strong>: Messages at 10, 5, 2 and 1 min before the sked.</li>
</ul>
<p>In addition to the automated messages to the remote station, there is an <strong>acoustic and visual notification</strong> for your own operator so no sked is ever missed.</p>
<p>Activate from the FurtherInfo panel of the corresponding station.</p>
<hr>
<h2 id="qso-sniffer-(from-v1.31)" tabindex="-1"><a class="header-anchor" href="#qso-sniffer-(from-v1.31)">QSO Sniffer (from v1.31)</a></h2>
<p>The QSO sniffer monitors the chat for messages from a configurable callsign list and automatically forwards them to the <strong>PM window</strong>. This prevents relevant messages from being lost in the general chat traffic.</p>
<p>Configuration: <a href="en-Configuration#sniffer-settings-from-v131">Configuration – Sniffer Settings</a></p>
<hr>
<h2 id="win-test-integration-(from-v1.31%2C-fully-configurable-from-v1.40)" tabindex="-1"><a class="header-anchor" href="#win-test-integration-(from-v1.31%2C-fully-configurable-from-v1.40)">Win-Test Integration (from v1.31, fully configurable from v1.40)</a></h2>
<p>KST4Contest fully supports <a href="https://www.win-test.com/">Win-Test</a> as a logging programme:</p>
<ul>
<li><strong>Log synchronisation</strong>: Worked stations are automatically retrieved from Win-Test and marked in the user list.</li>
<li><strong>Frequency parsing</strong>: The current TRX frequency is read from Win-Test UDP packets and populates the <code>MYQRG</code> variable.</li>
<li><strong>Sked handover (SKED push via UDP)</strong>: Agreed skeds from KST4Contest can be pushed directly to Win-Test, so the remote callsign appears in Win-Test’s sked window.</li>
</ul>
<p>Details: <a href="en-Configuration#win-test-network-listener">Configuration – Win-Test Network Listener</a></p>
<hr>
<h2 id="pstrotator-interface-(from-v1.31%2C-fully-configurable-from-v1.40)" tabindex="-1"><a class="header-anchor" href="#pstrotator-interface-(from-v1.31%2C-fully-configurable-from-v1.40)">PSTRotator Interface (from v1.31, fully configurable from v1.40)</a></h2>
<p>KST4Contest can control antenna direction directly via <strong>PSTRotator</strong>. When a station is selected in the user list, the rotator can automatically be turned to the QTF of the selected station.</p>
<p>Configuration: <a href="en-Configuration#pstrotator-settings-from-v131">Configuration – PSTRotator Settings</a></p>
<hr>
<h2 id="band-alert-for-new-qsos-(from-v1.40)" tabindex="-1"><a class="header-anchor" href="#band-alert-for-new-qsos-(from-v1.40)">Band Alert for New QSOs (from v1.40)</a></h2>
<p>When a station is logged, KST4Contest automatically checks whether that station has shown any other active bands in the chat that you are also QRV on. If so, a <strong>hint alert</strong> appears so no multi-band opportunity is missed.</p>
<hr>
<h2 id="worked-tag-lifetime-(from-v1.40)" tabindex="-1"><a class="header-anchor" href="#worked-tag-lifetime-(from-v1.40)">Worked Tag Lifetime (from v1.40)</a></h2>
<p>Worked stations are automatically removed from the database after <strong>3 days</strong>. Manually resetting the worked database before each contest is therefore no longer strictly necessary – the database keeps itself up to date.</p>
<hr>
<h2 id="chatmember-score-system-%2F-priority-list-(from-v1.40)" tabindex="-1"><a class="header-anchor" href="#chatmember-score-system-%2F-priority-list-(from-v1.40)">Chatmember Score System / Priority List (from v1.40)</a></h2>
<p>KST4Contest automatically calculates a <strong>priority score</strong> for each active chat member. The score is derived from:</p>
<ul>
<li>Antenna direction of the remote station (is it pointing towards me?)</li>
<li>QRB (distance)</li>
<li>Activity time and message count</li>
<li>Active bands and frequencies</li>
<li>AP availability (AirScout)</li>
<li>Sked direction (degrees)</li>
<li>Sked success rate and skedfail markings</li>
</ul>
<p>The top candidates are highlighted in a dedicated priority list, helping you not to miss the most important contacts during contest stress.</p>
<p>Stations with a failed sked can be marked using the <strong>Skedfail button</strong> in the FurtherInfo panel – this temporarily lowers their score.</p>
<hr>
<h2 id="ap-timeline-(from-v1.40)" tabindex="-1"><a class="header-anchor" href="#ap-timeline-(from-v1.40)">AP Timeline (from v1.40)</a></h2>
<p>A visual timeline shows up to 4 highly-scored stations per minute slot that should be workable via aircraft scatter. Prioritisation criteria:</p>
<ul>
<li><strong>Highest reflection potential</strong> is preferred (not necessarily the fastest arrival).</li>
<li>Stations towards which your antenna is not pointing are shown <strong>transparently</strong>.</li>
</ul>
<p>This gives the contest operator a quick overview of which stations will be reachable via which aircraft and at what time.</p>
<hr>
<h2 id="interval-beacon" tabindex="-1"><a class="header-anchor" href="#interval-beacon">Interval Beacon</a></h2>
<p>Automatic CQ messages in the public channel at a configurable interval. Recommended: use the <code>MYQRG</code> variable so the current frequency is always accurate. Details: <a href="Configuration#beacon-settings">Configuration – Beacon Settings</a>.</p>
<hr>
<h2 id="simplelogfile" tabindex="-1"><a class="header-anchor" href="#simplelogfile">Simplelogfile</a></h2>
<p>File-based log evaluation using regex. Details: <a href="Log-Sync#method-1-universal-file-based-callsign-interpreter-simplelogfile">Log Synchronisation</a>.</p>
<hr>
<h2 id="cluster-%26-qso-of-others" tabindex="-1"><a class="header-anchor" href="#cluster-%26-qso-of-others">Cluster &amp; QSO of Others</a></h2>
<p>A separate window showing the QSO flow between other stations. Particularly interesting during quieter night-time hours of a contest. This window can be minimised when not needed. Future plan: filtering to stations in your selected QTF.</p>
<hr>
<h2 id="station-map-(from-v1.41)" tabindex="-1"><a class="header-anchor" href="#station-map-(from-v1.41)">Station Map (from v1.41)</a></h2>
<p>An interactive OpenStreetMap-based map showing the geographic position of all active chat members.</p>
<p><strong>Features:</strong></p>
<ul>
<li>Station markers with callsign labels, coloured by activity and sked state</li>
<li>Antenna <strong>beam cone</strong> visualisation for the own station</li>
<li><strong>Connection line</strong> to the currently selected station</li>
<li><strong>Maidenhead grid</strong> overlay (QRA locator grid)</li>
<li><strong>Path profile chart</strong>: Terrain elevation cross-section between own station and the selected station, including Fresnel zone analysis and obstruction/horizon detection</li>
<li>Multiple terrain data sources: <strong>Copernicus GLO-30</strong> (high-resolution DEM), <strong>Open-Meteo API</strong>, synthetic fallback, and <strong>offline DEM import</strong> for air-gapped use</li>
<li>Aircraft scatter path analysis integrated with the terrain data</li>
</ul>
<p>The map works in packaged environments (AppImage, Flatpak) without internet access to external CDNs: map tiles are fetched via a local tile proxy, and the Leaflet.js library is bundled inside the application.</p>
<hr>
<h2 id="optimised-message-handling-%2F-30%2C000-message-limit-(from-v1.41)" tabindex="-1"><a class="header-anchor" href="#optimised-message-handling-%2F-30%2C000-message-limit-(from-v1.41)">Optimised Message Handling / 30,000 Message Limit (from v1.41)</a></h2>
<p>The internal chat and message tables are capped at <strong>30,000 entries</strong>. Older messages are automatically discarded when the limit is reached. This keeps memory usage and rendering performance stable during multi-day contest operations.</p>
<hr>
<h2 id="screen-aware-window-sizing-(from-v1.41)" tabindex="-1"><a class="header-anchor" href="#screen-aware-window-sizing-(from-v1.41)">Screen-Aware Window Sizing (from v1.41)</a></h2>
<p>On startup, KST4Contest calculates a screen-aware size for the main window:</p>
<ul>
<li>The stored window size from the previous session is used – but <strong>never larger than the current screen</strong>.</li>
<li>If KST4Contest was last used on a larger monitor, the window is automatically scaled down to fit the current display without clipping.</li>
<li>The UI layout is more <strong>compact and responsive on smaller screens</strong>, showing the same information in less space.</li>
</ul>
<p>This prevents unusable oversized windows when switching between machines or monitors.</p>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/home/index.html
+149
View File
@@ -0,0 +1,149 @@
<!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/home/">
<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/home/">
<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>Home</h1>
<h1 id="kst4contest-%E2%80%93-wiki" tabindex="-1"><a class="header-anchor" href="#kst4contest-%E2%80%93-wiki">KST4Contest – Wiki</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Home">Deutsche Version</a></p>
</blockquote>
<p><strong>KST4Contest</strong> (also known as <em>PraktiKST</em>) is a Java-based chat client for the <a href="http://www.on4kst.info/chat/">ON4KST Chat</a>, specifically designed for contest operation on the VHF/UHF/SHF bands (144 MHz and above).</p>
<p>Developed by <strong>DO5AMF (Marc Fröhlich)</strong>, operator at DM5M.</p>
<hr>
<h2 id="quick-navigation" tabindex="-1"><a class="header-anchor" href="#quick-navigation">Quick Navigation</a></h2>
<table>
<thead>
<tr>
<th>Page</th>
<th>Contents</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="en-Installation">Installation</a></td>
<td>Download, Java requirements, update</td>
</tr>
<tr>
<td><a href="en-Configuration">Configuration</a></td>
<td>All settings in detail</td>
</tr>
<tr>
<td><a href="en-Log-Sync">Log Synchronisation</a></td>
<td>UCXLog, N1MM+, QARTest, <a href="http://DXLog.net">DXLog.net</a>, WinTest</td>
</tr>
<tr>
<td><a href="en-AirScout-Integration">AirScout Integration</a></td>
<td>Aircraft scatter detection</td>
</tr>
<tr>
<td><a href="en-DX-Cluster-Server">DX Cluster Server</a></td>
<td>Built-in DX cluster for your logging software</td>
</tr>
<tr>
<td><a href="en-Features">Features</a></td>
<td>All features at a glance</td>
</tr>
<tr>
<td><a href="en-Macros-and-Variables">Macros and Variables</a></td>
<td>Text snippets, shortcuts, variables</td>
</tr>
<tr>
<td><a href="en-User-Interface">User Interface</a></td>
<td>UI explanation and operation</td>
</tr>
<tr>
<td><a href="en-Changelog">Changelog</a></td>
<td>Version history</td>
</tr>
</tbody>
</table>
<hr>
<h2 id="what-is-kst4contest%3F" tabindex="-1"><a class="header-anchor" href="#what-is-kst4contest%3F">What is KST4Contest?</a></h2>
<p>The ON4KST Chat is the de-facto standard for skeds on the 144 MHz and higher bands. KST4Contest enhances the chat experience with contest-specific features:</p>
<ul>
<li><strong>Worked marking</strong>: Stations already worked are highlighted visually, synchronised directly from your logging software via UDP.</li>
<li><strong>Sked direction detection</strong>: When a station calls another one from your direction, it is highlighted green and bold.</li>
<li><strong>QRG detection</strong>: KST4Contest automatically reads frequencies from the chat traffic and shows them in the user list.</li>
<li><strong>AirScout interface</strong>: Reflectable aircraft are shown directly in the user list.</li>
<li><strong>Built-in DX cluster server</strong>: Spots are sent directly to your logging software.</li>
<li><strong>Dark mode</strong> (from v1.26): Easy on the eyes during night-time operation.</li>
<li><strong>Multi-channel login</strong> (from v1.26): Simultaneously logged into two chat categories.</li>
</ul>
<hr>
<h2 id="contact-%26-support" tabindex="-1"><a class="header-anchor" href="#contact-%26-support">Contact &amp; Support</a></h2>
<ul>
<li><strong>Email</strong>: <a href="mailto:praktimarc+kst4contest@gmail.com">praktimarc+kst4contest@gmail.com</a> <em>(for kst4contest topics only)</em></li>
<li><strong>GitHub</strong>: <a href="https://github.com/praktimarc/kst4contest">https://github.com/praktimarc/kst4contest</a></li>
<li><strong>Download</strong>: <a href="https://github.com/praktimarc/kst4contest/releases/latest">https://github.com/praktimarc/kst4contest/releases/latest</a></li>
</ul>
<h3 id="reporting-a-bug-(creating-an-issue)" tabindex="-1"><a class="header-anchor" href="#reporting-a-bug-(creating-an-issue)">Reporting a bug (creating an issue)</a></h3>
<p>When reporting a bug, please <strong>always attach the log file</strong>. KST4Contest automatically writes an error log (error messages only, no personal data):</p>
<table>
<thead>
<tr>
<th>Operating system</th>
<th>Log file location</th>
</tr>
</thead>
<tbody>
<tr>
<td>Linux / macOS</td>
<td><code>~/.praktiKST/kst4contest-errors.log</code></td>
</tr>
<tr>
<td>Windows</td>
<td><code>C:\Users\&lt;YourName&gt;\.praktiKST\kst4contest-errors.log</code></td>
</tr>
</tbody>
</table>
<p>When opening an issue on GitHub, a template is provided that guides you through all relevant fields.</p>
<hr>
<h2 id="acknowledgements" tabindex="-1"><a class="header-anchor" href="#acknowledgements">Acknowledgements</a></h2>
<p>Special thanks to: Gianluca Costantino (IU3OAR), Alessandro Murador (IZ3VTH), Reczetár István (HA1FV), OM0AAO (Viliam Petrik, DX cluster idea), DC9DJ (Konrad Neitzel, project structure), DO5ALF (Andreas, webmaster <a href="http://funkerportal.de">funkerportal.de</a>), PE0WGA (Franz van Velzen, tester) and all other testers and contributors.</p>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/installation/index.html
+264
View File
@@ -0,0 +1,264 @@
<!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/installation/">
<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/installation/">
<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>Installation</h1>
<h1 id="installation" tabindex="-1"><a class="header-anchor" href="#installation">Installation</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Installation">Deutsche Version</a></p>
</blockquote>
<h2 id="prerequisites" tabindex="-1"><a class="header-anchor" href="#prerequisites">Prerequisites</a></h2>
<p>An resolution of 1200px by 720px is recommended</p>
<h3 id="on4kst-account" tabindex="-1"><a class="header-anchor" href="#on4kst-account">ON4KST Account</a></h3>
<p>To use the chat, a registered account with the ON4KST chat service is required:</p>
<ul>
<li>Register at: <a href="http://www.on4kst.info/chat/register.php">http://www.on4kst.info/chat/register.php</a></li>
</ul>
<h3 id="chat-etiquette" tabindex="-1"><a class="header-anchor" href="#chat-etiquette">Chat Etiquette</a></h3>
<p>The official language in the ON4KST Chat is <strong>English</strong>. Please use English even when communicating with stations from your own country. Common HAM abbreviations (agn, dir, pse, rrr, tnx, 73 …) are widely used and understood.</p>
<h3 id="personal-messages" tabindex="-1"><a class="header-anchor" href="#personal-messages">Personal Messages</a></h3>
<p>To send a private message to another station, always use the following format:</p>
<pre><code>/CQ CALLSIGN message text
</code></pre>
<p>Example: <code>/CQ DL5ASG pse sked 144.205?</code></p>
<p>During heavy chat traffic (5–6 messages per second in a contest), public messages directed at a specific callsign are easily missed. However, KST4Contest also catches such messages if they are accidentally posted publicly (see <a href="Features#catching-personal-messages">Features – PM Catching</a>).</p>
<hr>
<h2 id="download" tabindex="-1"><a class="header-anchor" href="#download">Download</a></h2>
<h3 id="windows" tabindex="-1"><a class="header-anchor" href="#windows">Windows</a></h3>
<p>The latest version can be downloaded as a ZIP file:</p>
<p><strong><a href="https://github.com/praktimarc/kst4contest/releases/latest">https://github.com/praktimarc/kst4contest/releases/latest</a></strong></p>
<p>The filename has the format <code>praktiKST-v&lt;version_number&gt;-windows-x64.zip</code>.</p>
<h3 id="linux" tabindex="-1"><a class="header-anchor" href="#linux">Linux</a></h3>
<p>Multiple package formats are available from the releases page:</p>
<p><strong><a href="https://github.com/praktimarc/kst4contest/releases/latest">https://github.com/praktimarc/kst4contest/releases/latest</a></strong></p>
<table>
<thead>
<tr>
<th>Format</th>
<th>Filename</th>
<th>Suitable for</th>
</tr>
</thead>
<tbody>
<tr>
<td>AppImage</td>
<td><code>KST4Contest-v&lt;version&gt;-linux-x86_64.AppImage</code></td>
<td>All distributions</td>
</tr>
<tr>
<td>Debian package</td>
<td><code>KST4Contest-v&lt;version&gt;-debian-amd64.deb</code></td>
<td>Debian, Ubuntu, Linux Mint, …</td>
</tr>
<tr>
<td>RPM package</td>
<td><code>KST4Contest-v&lt;version&gt;-fedora-x86_64.rpm</code></td>
<td>Fedora, RHEL, openSUSE, …</td>
</tr>
<tr>
<td>Arch package</td>
<td><code>KST4Contest-v&lt;version&gt;-archlinux-x86_64.pkg.tar.zst</code></td>
<td>Arch Linux, Manjaro, …</td>
</tr>
<tr>
<td>Flatpak</td>
<td><code>de.x08.KST4Contest.flatpakref</code></td>
<td>All distributions with Flatpak</td>
</tr>
</tbody>
</table>
<blockquote>
<p><strong>Recommended for Linux:</strong> The Flatpak installation is the easiest way to stay up to date — <code>flatpak update</code> handles all future updates automatically. The repository is GPG-signed for security.</p>
</blockquote>
<h3 id="macos" tabindex="-1"><a class="header-anchor" href="#macos">macOS</a></h3>
<blockquote>
<p>⚠️ <strong>Best-Effort Support:</strong> macOS builds are provided as a convenience but are <strong>not fully tested</strong>. We build and release macOS binaries with every release, but we cannot test every scenario on macOS. If you encounter issues, please report them – we will do our best to address them, but cannot guarantee the same level of support as for Windows and Linux.</p>
</blockquote>
<p>The latest version can be downloaded as a DMG disk image (available for both Apple Silicon and Intel Macs):</p>
<p><strong><a href="https://github.com/praktimarc/kst4contest/releases/latest">https://github.com/praktimarc/kst4contest/releases/latest</a></strong></p>
<p>The filename has the format <code>KST4Contest-v&lt;version_number&gt;-macos-&lt;arch&gt;.dmg</code>, where <code>&lt;arch&gt;</code> is <code>arm64</code> (Apple Silicon) or <code>x86_64</code> (Intel).</p>
<hr>
<h2 id="installation-1" tabindex="-1"><a class="header-anchor" href="#installation-1">Installation</a></h2>
<h3 id="windows-1" tabindex="-1"><a class="header-anchor" href="#windows-1">Windows</a></h3>
<ol>
<li>Download the ZIP file.</li>
<li>Unzip the ZIP file into a folder of your choice.</li>
<li>Run <code>praktiKST.exe</code>.</li>
</ol>
<p>Settings are stored at <code>%USERPROFILE%\.praktikst\preferences.xml</code>.</p>
<h3 id="linux-1" tabindex="-1"><a class="header-anchor" href="#linux-1">Linux</a></h3>
<p>Settings are always stored at <code>~/.praktikst/preferences.xml</code>.</p>
<h4 id="appimage" tabindex="-1"><a class="header-anchor" href="#appimage">AppImage</a></h4>
<ol>
<li>Download the AppImage.</li>
<li>Make it executable: <code>chmod +x KST4Contest-v&lt;version&gt;-linux-x86_64.AppImage</code></li>
<li>Run it.</li>
</ol>
<h4 id="debian-%2F-ubuntu" tabindex="-1"><a class="header-anchor" href="#debian-%2F-ubuntu">Debian / Ubuntu</a></h4>
<pre><code class="language-bash">sudo apt install ./KST4Contest-v&lt;version&gt;-debian-amd64.deb
</code></pre>
<p>Or double-click the <code>.deb</code> file in your file manager.</p>
<h4 id="fedora-%2F-rhel" tabindex="-1"><a class="header-anchor" href="#fedora-%2F-rhel">Fedora / RHEL</a></h4>
<pre><code class="language-bash">sudo dnf install ./KST4Contest-v&lt;version&gt;-fedora-x86_64.rpm
</code></pre>
<h4 id="arch-linux" tabindex="-1"><a class="header-anchor" href="#arch-linux">Arch Linux</a></h4>
<pre><code class="language-bash">sudo pacman -U KST4Contest-v&lt;version&gt;-archlinux-x86_64.pkg.tar.zst
</code></pre>
<h4 id="flatpak" tabindex="-1"><a class="header-anchor" href="#flatpak">Flatpak</a></h4>
<p>Download <code>de.x08.KST4Contest.flatpakref</code> from the <a href="https://github.com/praktimarc/kst4contest/releases/latest">latest release</a> and open it, or run:</p>
<pre><code class="language-bash">flatpak install de.x08.KST4Contest.flatpakref
</code></pre>
<p>Or add the remote manually (recommended for nightly/beta access):</p>
<pre><code class="language-bash">flatpak remote-add --if-not-exists kst4contest https://praktimarc.github.io/kst4contest/kst4contest.flatpakrepo
flatpak install kst4contest de.x08.KST4Contest
</code></pre>
<h4 id="flatpak-channels-(nightly-%2F-beta-%2F-stable)" tabindex="-1"><a class="header-anchor" href="#flatpak-channels-(nightly-%2F-beta-%2F-stable)">Flatpak Channels (nightly / beta / stable)</a></h4>
<p>The Flatpak repository provides three channels, all served from the same remote:</p>
<table>
<thead>
<tr>
<th>Channel</th>
<th>Content</th>
<th>Built on</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>stable</code></td>
<td>Current stable version</td>
<td>Every normal release tag</td>
</tr>
<tr>
<td><code>beta</code></td>
<td>Pre-release version</td>
<td>Tags prefixed with <code>beta-</code></td>
</tr>
<tr>
<td><code>nightly</code></td>
<td>Development build (main branch)</td>
<td>Every push to main / daily</td>
</tr>
</tbody>
</table>
<p>Add the remote once, then install the channel you want:</p>
<pre><code class="language-bash">flatpak remote-add --if-not-exists kst4contest https://praktimarc.github.io/kst4contest/kst4contest.flatpakrepo
# Stable (default)
flatpak install kst4contest de.x08.KST4Contest
# Beta
flatpak install kst4contest de.x08.KST4Contest//beta
# Nightly
flatpak install kst4contest de.x08.KST4Contest//nightly
</code></pre>
<blockquote>
<p><strong>Note:</strong> Flatpak only allows one installed version per App-ID at a time. To switch channels, uninstall the current version first:</p>
<pre><code class="language-bash">flatpak uninstall de.x08.KST4Contest
flatpak install kst4contest de.x08.KST4Contest//nightly
</code></pre>
</blockquote>
<p>Updates work as usual with <code>flatpak update</code>.</p>
<p>The <code>flatpakref</code> files for beta and stable are attached to their respective <a href="https://github.com/praktimarc/kst4contest/releases">GitHub Releases</a>. The nightly <code>flatpakref</code> (<code>de.x08.KST4Contest.nightly.flatpakref</code>) is available as an artifact on the <a href="https://github.com/praktimarc/kst4contest/actions">GitHub Actions</a> tab (kept for 14 days) — for nightly builds, the manual remote approach above is usually more convenient.</p>
<h3 id="macos-1" tabindex="-1"><a class="header-anchor" href="#macos-1">macOS</a></h3>
<ol>
<li>Download the DMG file for your architecture (Apple Silicon or Intel).</li>
<li>Open the DMG file.</li>
<li>Drag <code>KST4Contest.app</code> into your <strong>Applications</strong> folder.</li>
<li>On first launch, macOS may show a warning because the app is not notarised. To open it:
<ul>
<li>Right-click (or Control-click) on <code>KST4Contest.app</code> in Finder and choose <strong>Open</strong>.</li>
<li>Alternatively, go to <strong>System Settings → Privacy &amp; Security</strong> and click <strong>Open Anyway</strong>.</li>
</ul>
</li>
<li>Run KST4Contest from your Applications folder or Launchpad.</li>
</ol>
<p>Settings are stored at <code>~/.praktikst/preferences.xml</code>.</p>
<hr>
<h2 id="updating" tabindex="-1"><a class="header-anchor" href="#updating">Updating</a></h2>
<p>KST4Contest includes an <strong>automatic update notification service</strong>: as soon as a new version is available, a window will appear at startup with:</p>
<ul>
<li>information that a new version is available,</li>
<li>a changelog,</li>
<li>the download link for the new version.</li>
</ul>
<p><img src="update_window.png" alt="Example Update Window"></p>
<h3 id="update-process" tabindex="-1"><a class="header-anchor" href="#update-process">Update Process</a></h3>
<h4 id="windows-2" tabindex="-1"><a class="header-anchor" href="#windows-2">Windows</a></h4>
<p>Currently, there is only one way to update:</p>
<ol>
<li>Delete the old folder.</li>
<li>Unzip the new ZIP file.</li>
</ol>
<p>The settings file (<code>preferences.xml</code>) is preserved because it is stored in the user folder, not the program folder.</p>
<h4 id="linux-2" tabindex="-1"><a class="header-anchor" href="#linux-2">Linux</a></h4>
<ul>
<li><strong>AppImage</strong>: Download the new AppImage, make it executable (<code>chmod +x</code>), optionally delete the old one.</li>
<li><strong>Debian/Ubuntu</strong>: <code>sudo apt install ./KST4Contest-v&lt;version&gt;-debian-amd64.deb</code></li>
<li><strong>Fedora/RHEL</strong>: <code>sudo dnf upgrade ./KST4Contest-v&lt;version&gt;-fedora-x86_64.rpm</code></li>
<li><strong>Arch Linux</strong>: <code>sudo pacman -U KST4Contest-v&lt;version&gt;-archlinux-x86_64.pkg.tar.zst</code></li>
<li><strong>Flatpak (repository)</strong>: <code>flatpak update</code> – updates all Flatpak apps including KST4Contest.</li>
</ul>
<h4 id="macos-2" tabindex="-1"><a class="header-anchor" href="#macos-2">macOS</a></h4>
<ol>
<li>Download the new DMG file.</li>
<li>Open the DMG.</li>
<li>Drag the new <code>KST4Contest.app</code> into your <strong>Applications</strong> folder, replacing the old version.</li>
</ol>
<hr>
<h2 id="known-issues-at-startup" tabindex="-1"><a class="header-anchor" href="#known-issues-at-startup">Known Issues at Startup</a></h2>
<h3 id="norton-360" tabindex="-1"><a class="header-anchor" href="#norton-360">Norton 360</a></h3>
<p>Norton 360 classifies <code>praktiKST.exe</code> as dangerous (false positive). An exception must be created for the file:</p>
<ol>
<li>Open Norton 360.</li>
<li>Security → History → Find the corresponding event.</li>
<li>Select “Restore &amp; Add Exception”.</li>
</ol>
<p><em>(Reported by PE0WGA, Franz van Velzen – thank you!)</em></p>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/log-sync/index.html
+178
View File
@@ -0,0 +1,178 @@
<!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">
</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>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="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!&quot; – 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">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/macros-and-variables/index.html
+189
View File
@@ -0,0 +1,189 @@
<!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/macros-and-variables/">
<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/macros-and-variables/">
<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>Macros and Variables</h1>
<h1 id="macros-and-variables" tabindex="-1"><a class="header-anchor" href="#macros-and-variables">Macros and Variables</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Makros-und-Variablen">Deutsche Version</a></p>
</blockquote>
<p>KST4Contest offers a flexible system of text snippets, shortcuts and built-in variables that significantly speed up the chat workflow during contests.</p>
<hr>
<h2 id="overview" tabindex="-1"><a class="header-anchor" href="#overview">Overview</a></h2>
<table>
<thead>
<tr>
<th>Type</th>
<th>Access</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Shortcuts</strong></td>
<td>Button in the toolbar</td>
<td>Quick text insert into the send field</td>
</tr>
<tr>
<td><strong>Snippets</strong></td>
<td>Right-click / Ctrl+1…0</td>
<td>Text building blocks, optional PM sending</td>
</tr>
<tr>
<td><strong>Variables</strong></td>
<td>Usable in all text fields</td>
<td>Dynamic values (QRG, locator, AP data)</td>
</tr>
</tbody>
</table>
<hr>
<h2 id="shortcuts-(quick-access-buttons)" tabindex="-1"><a class="header-anchor" href="#shortcuts-(quick-access-buttons)">Shortcuts (Quick-Access Buttons)</a></h2>
<p>Configurable in Preferences → <strong>Shortcut Settings</strong>.</p>
<ul>
<li>Each configured text creates <strong>one button</strong> in the user interface.</li>
<li>Clicking a button inserts the text into the <strong>send field</strong>.</li>
<li><strong>All variables</strong> can be used in shortcuts and are resolved immediately when inserted.</li>
<li>Longer texts are also possible.</li>
</ul>
<p><strong>Tip</strong>: Set up frequently used abbreviations like “pse”, “rrr”, “tnx”, “73” as shortcuts.</p>
<hr>
<h2 id="snippets-(text-building-blocks)" tabindex="-1"><a class="header-anchor" href="#snippets-(text-building-blocks)">Snippets (Text Building Blocks)</a></h2>
<p>Configurable in Preferences → <strong>Snippet Settings</strong>.</p>
<h3 id="access" tabindex="-1"><a class="header-anchor" href="#access">Access</a></h3>
<ul>
<li><strong>Right-click</strong> on a callsign in the user list</li>
<li><strong>Right-click</strong> in the CQ message table</li>
<li><strong>Right-click</strong> in the PM message table</li>
<li><strong>Keyboard shortcuts</strong>: <code>Ctrl+1</code> to <code>Ctrl+0</code> for the first 10 snippets</li>
</ul>
<h3 id="behaviour-with-a-selected-callsign" tabindex="-1"><a class="header-anchor" href="#behaviour-with-a-selected-callsign">Behaviour with a Selected Callsign</a></h3>
<p>When a callsign is selected in the user list, the snippet is addressed as a <strong>private message</strong>:</p>
<pre><code>/CQ CALLSIGN &lt;snippet text&gt;
</code></pre>
<p>Then <strong>Enter</strong> can be pressed to send directly – even if the send field does not have focus.</p>
<h3 id="hardware-macro-keyboard" tabindex="-1"><a class="header-anchor" href="#hardware-macro-keyboard">Hardware Macro Keyboard</a></h3>
<p><em>(Idea by IU3OAR, Gianluca Costantino)</em></p>
<p>The key combinations <code>Ctrl+1</code> to <code>Ctrl+0</code> can be assigned to a programmable macro keyboard. One key press triggers the snippet, another press (mapped to Enter) sends it immediately. In contest operation this saves considerable time.</p>
<h3 id="predefined-default-snippets" tabindex="-1"><a class="header-anchor" href="#predefined-default-snippets">Predefined Default Snippets</a></h3>
<p>On first start, some snippets are pre-configured, e.g.:</p>
<ul>
<li><code>Hi OM, try sked?</code></li>
<li><code>I am calling cq ur dir, pse lsn to me at MYQRG</code></li>
<li><code>pse ur qrg?</code></li>
<li><code>rrr, I move to your qrg nw, pse ant dir me</code></li>
</ul>
<p>These can be customised or deleted in the Preferences.</p>
<hr>
<h2 id="variables" tabindex="-1"><a class="header-anchor" href="#variables">Variables</a></h2>
<p>Variables in written texts (snippets, shortcuts, beacon, send field) are replaced by their current values at runtime. Simply type the variable name in <strong>uppercase</strong> in the text.</p>
<h3 id="myqrg" tabindex="-1"><a class="header-anchor" href="#myqrg">MYQRG</a></h3>
<p>Replaced by the current transceiver frequency.</p>
<ul>
<li>Source: TRX sync via UDP from the logging software (if enabled)</li>
<li>Fallback: Manually entered value in the MYQRG text field to the right of the send button</li>
<li>Format: <code>144.388.03</code></li>
</ul>
<p><strong>Example</strong>: <code>calling cq at MYQRG</code> → <code>calling cq at 144.388.03</code></p>
<h3 id="myqrgshort" tabindex="-1"><a class="header-anchor" href="#myqrgshort">MYQRGSHORT</a></h3>
<p>Like MYQRG, but only the first 7 characters.</p>
<ul>
<li>Format: <code>144.388</code></li>
</ul>
<p><strong>Example</strong>: <code>qrg: MYQRGSHORT</code> → <code>qrg: 144.388</code></p>
<h3 id="mylocator" tabindex="-1"><a class="header-anchor" href="#mylocator">MYLOCATOR</a></h3>
<p>Replaced by your own Maidenhead locator (6 characters).</p>
<ul>
<li>Format: <code>JO51IJ</code></li>
</ul>
<p><strong>Example</strong>: <code>my loc: MYLOCATOR</code> → <code>my loc: JO51IJ</code></p>
<h3 id="mylocatorshort" tabindex="-1"><a class="header-anchor" href="#mylocatorshort">MYLOCATORSHORT</a></h3>
<p>Like MYLOCATOR, but only the first 4 characters.</p>
<ul>
<li>Format: <code>JO51</code></li>
</ul>
<p><strong>Example</strong>: <code>loc: MYLOCATORSHORT</code> → <code>loc: JO51</code></p>
<h3 id="qrzname" tabindex="-1"><a class="header-anchor" href="#qrzname">QRZNAME</a></h3>
<p>Replaced by the <strong>name</strong> of the currently selected station from the chat name field.</p>
<p><strong>Example</strong>: <code>Hi QRZNAME, sked?</code> → <code>Hi Gianluca, sked?</code></p>
<h3 id="firstap" tabindex="-1"><a class="header-anchor" href="#firstap">FIRSTAP</a></h3>
<p>Replaced by data of the first reflectable aircraft to the selected station (if available).</p>
<ul>
<li>Condition: AirScout is active and an aircraft is available.</li>
<li>Example format: <code>a very big AP in 1 min</code></li>
</ul>
<p><strong>Example</strong>: <code>AP info: FIRSTAP</code> → <code>AP info: a very big AP in 1 min</code></p>
<h3 id="secondap" tabindex="-1"><a class="header-anchor" href="#secondap">SECONDAP</a></h3>
<p>Like FIRSTAP, but for the second available aircraft.</p>
<ul>
<li>Example format: <code>Next big AP in 9 min</code></li>
</ul>
<p><strong>Example</strong>: <code>also: SECONDAP</code> → <code>also: Next big AP in 9 min</code></p>
<h3 id="myqtf-(planned-for-v1.3)" tabindex="-1"><a class="header-anchor" href="#myqtf-(planned-for-v1.3)">MYQTF <em>(planned for v1.3)</em></a></h3>
<p>Replaced by the current antenna direction in words (e.g. <code>north</code>, <code>north east</code>, <code>east</code>, …).</p>
<ul>
<li>Source: Degree value in the MYQTF input field (to the right of the MYQRG field)</li>
</ul>
<hr>
<h2 id="variables-in-the-beacon" tabindex="-1"><a class="header-anchor" href="#variables-in-the-beacon">Variables in the Beacon</a></h2>
<p>All variables can also be used in the <strong>automatic beacon</strong> (interval messages). Recommended beacon configuration:</p>
<pre><code>calling cq at MYQRG, loc MYLOCATOR, GL all!
</code></pre>
<p>Since KST4Contest automatically reads QRG data from chat messages: if other stations also use KST4Contest, they will immediately see your QRG in the QRG column of their user list.</p>
<hr>
<h2 id="example-contest-workflow-with-macros" tabindex="-1"><a class="header-anchor" href="#example-contest-workflow-with-macros">Example Contest Workflow with Macros</a></h2>
<ol>
<li>Select a station in the user list → callsign is now pre-selected.</li>
<li>Press <code>Ctrl+1</code> → Snippet “Hi OM, try sked?” is addressed as a PM.</li>
<li>Press Enter → Message sent.</li>
<li>Station replies with frequency → QRG column is automatically filled.</li>
<li>Press <code>Ctrl+2</code> → Snippet “I am calling cq ur dir, pse lsn to me at 144.388” (MYQRG resolved).</li>
<li>Press Enter → Sent.</li>
</ol>
<p>No manual typing, no errors, no interruption to CQ calling.</p>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>
website/_site/manual/en/user-interface/index.html
+158
View File
@@ -0,0 +1,158 @@
<!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/user-interface/">
<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/user-interface/">
<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>User Interface</h1>
<h1 id="user-interface" tabindex="-1"><a class="header-anchor" href="#user-interface">User Interface</a></h1>
<blockquote>
<p>🇬🇧 You are reading the English version | 🇩🇪 <a href="de-Benutzeroberflaeche">Deutsche Version</a></p>
</blockquote>
<h2 id="connecting-to-the-chat" tabindex="-1"><a class="header-anchor" href="#connecting-to-the-chat">Connecting to the Chat</a></h2>
<ol>
<li>Select a <strong>chat category</strong> in the settings window (e.g. 144 MHz VHF, 432 MHz UHF, …).</li>
<li>Click the <strong>Connect</strong> button.</li>
<li>Wait for the connection to be established.</li>
</ol>
<blockquote>
<p>Disconnecting and reconnecting is only possible via the settings window. It is therefore recommended to keep the settings window open.</p>
</blockquote>
<hr>
<h2 id="main-window-overview" tabindex="-1"><a class="header-anchor" href="#main-window-overview">Main Window Overview</a></h2>
<p>The main window consists of several areas:</p>
<h3 id="pm-window-(top-left)" tabindex="-1"><a class="header-anchor" href="#pm-window-(top-left)">PM Window (top left)</a></h3>
<p>Shows all received <strong>private messages</strong> as well as intercepted public messages containing your own callsign. New messages appear in <strong>red</strong> and fade every 30 seconds from yellow to white.</p>
<h3 id="user-list-(chat-members)" tabindex="-1"><a class="header-anchor" href="#user-list-(chat-members)">User List (Chat Members)</a></h3>
<p>The central table of all currently active chat users. Columns (depending on configuration):</p>
<table>
<thead>
<tr>
<th>Column</th>
<th>Content</th>
</tr>
</thead>
<tbody>
<tr>
<td>Call</td>
<td>Station’s callsign</td>
</tr>
<tr>
<td>Name</td>
<td>Name from the chat name field</td>
</tr>
<tr>
<td>Loc</td>
<td>Maidenhead locator</td>
</tr>
<tr>
<td>QRB</td>
<td>Distance in km</td>
</tr>
<tr>
<td>QTF</td>
<td>Direction in degrees</td>
</tr>
<tr>
<td>QRG</td>
<td>Automatically detected frequency</td>
</tr>
<tr>
<td>AP</td>
<td>AirScout aircraft data (when active)</td>
</tr>
<tr>
<td>Band colours</td>
<td>Worked / NOT-QRV status per band</td>
</tr>
</tbody>
</table>
<p><strong>Sorting</strong>: Click column headers. QRB sorting is numerical (corrected in v1.22).</p>
<h3 id="send-field" tabindex="-1"><a class="header-anchor" href="#send-field">Send Field</a></h3>
<p>Text input for outgoing messages. After clicking a callsign in the user list, the send field automatically receives focus – start typing immediately without double-clicking (from v1.22).</p>
<h3 id="myqrg-field" tabindex="-1"><a class="header-anchor" href="#myqrg-field">MYQRG Field</a></h3>
<p>To the right of the send button. Shows the current own QRG, can also be entered manually.</p>
<h3 id="myqtf-field-(for-v1.3)" tabindex="-1"><a class="header-anchor" href="#myqtf-field-(for-v1.3)">MYQTF Field <em>(for v1.3)</em></a></h3>
<p>Input field for the current antenna direction. Used for the planned <code>MYQTF</code> variable.</p>
<hr>
<h2 id="filters" tabindex="-1"><a class="header-anchor" href="#filters">Filters</a></h2>
<p>The filter bar (from v1.21 as a flowpane for small screens):</p>
<ul>
<li><strong>Show only QTF</strong>: Activate direction filter (N/NE/E/… buttons or degree input)</li>
<li><strong>Show only QRB [km] &lt;=</strong>: Activate distance filter (toggle button)</li>
<li><strong>Hide Worked [Band]</strong>: Hide worked stations per band (one toggle per band)</li>
<li><strong>Hide NOT-QRV [Band]</strong>: Hide NOT-QRV-tagged stations per band</li>
</ul>
<hr>
<h2 id="station-info-panel-(further-info)" tabindex="-1"><a class="header-anchor" href="#station-info-panel-(further-info)">Station Info Panel (Further Info)</a></h2>
<p>Bottom right: Shows all messages of a selected station (CQ messages and PMs in one panel). A message filter can be pre-configured via the default filter in the Preferences.</p>
<p><strong>Sked reminders</strong> can also be activated here.</p>
<hr>
<h2 id="priority-list" tabindex="-1"><a class="header-anchor" href="#priority-list">Priority List</a></h2>
<p>Shows the top candidates calculated by the Score Service. Updates automatically in the background based on direction, distance and AP availability.</p>
<hr>
<h2 id="cluster-%26-qso-of-others" tabindex="-1"><a class="header-anchor" href="#cluster-%26-qso-of-others">Cluster &amp; QSO of Others</a></h2>
<p>Separate window (can be minimised). Shows the communication flow between other stations – interesting during quieter contest periods.</p>
<hr>
<h2 id="menu" tabindex="-1"><a class="header-anchor" href="#menu">Menu</a></h2>
<h3 id="window" tabindex="-1"><a class="header-anchor" href="#window">Window</a></h3>
<ul>
<li><strong>Use Dark Mode</strong> (from v1.26): Toggle dark colour scheme on/off.</li>
</ul>
<hr>
<h2 id="window-sizes-and-dividers" tabindex="-1"><a class="header-anchor" href="#window-sizes-and-dividers">Window Sizes and Dividers</a></h2>
<p>From <strong>v1.21</strong>, clicking <strong>“Save Settings”</strong> also saves window sizes and divider positions of all panels in the configuration file, which are restored on the next start.</p>
<p>If you encounter display problems: delete the configuration file → KST4Contest creates new default values.</p>
<hr>
<h2 id="operating-tips" tabindex="-1"><a class="header-anchor" href="#operating-tips">Operating Tips</a></h2>
<ul>
<li><strong>Keep the settings window open</strong>: Quick access to enable/disable the beacon.</li>
<li><strong>Right-click in the user list</strong>: Opens the snippet menu and further actions (<a href="http://QRZ.com">QRZ.com</a> profile, set NOT-QRV tags).</li>
<li><strong>Enter from anywhere</strong>: When text is in the send field, Enter sends directly – even if the focus is elsewhere.</li>
<li><strong>Stop the beacon</strong>: Switch off the beacon while scanning frequencies to avoid flooding the chat with messages.</li>
</ul>
</div>
</section>
</main>
<footer class="site-footer">
<p>KST4Contest – ON4KST contest workflow for VHF/UHF/SHF operators.</p>
</footer>
</body>
</html>