mirror of
https://github.com/praktimarc/kst4contest.git
synced 2026-07-13 16:16:44 +02:00
github-actions[bot]
294 lines
19 KiB
HTML
294 lines
19 KiB
HTML
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<title>{{ manual.title }} | KST4Contest Manual</title>
|
||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
<meta name="description" content="KST4Contest manual page: {{ manual.title }}">
|
||
<link rel="canonical" href="https://kst4contest.hamradioonline.de/manual/en/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?v=1783615687631">
|
||
<link rel="alternate" type="application/rss+xml" title="KST4Contest News" href="/feed.xml">
|
||
|
||
<meta property="og:image" content="https://kst4contest.hamradioonline.de/assets/social/kst4contest-og.png">
|
||
<meta property="og:image:width" content="1200">
|
||
<meta property="og:image:height" content="630">
|
||
<meta name="twitter:image" content="https://kst4contest.hamradioonline.de/assets/social/kst4contest-og.png">
|
||
|
||
</head>
|
||
|
||
<body>
|
||
<div class="site-bg"></div>
|
||
|
||
<header class="site-header">
|
||
<a class="brand" href="/">
|
||
<span class="brand-mark">◎</span>
|
||
<span>
|
||
<strong>KST4Contest</strong>
|
||
<small>ON4KST Contest Client</small>
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="site-nav">
|
||
|
||
<a href="/">Home</a>
|
||
|
||
<a href="/features/">Features</a>
|
||
|
||
<a href="/screenshots/">Screenshots</a>
|
||
|
||
<a href="/manual/">Manual</a>
|
||
|
||
<a href="/news/">News</a>
|
||
|
||
<a href="/roadmap/">Roadmap</a>
|
||
|
||
<a href="/about/">About</a>
|
||
|
||
<a href="/faq/">FAQ</a>
|
||
|
||
<a class="nav-cta" href="/download/">Download</a>
|
||
</nav>
|
||
</header>
|
||
|
||
<main>
|
||
|
||
<section class="section">
|
||
<div class="card manual-content">
|
||
<p><a href="/manual/en/">← Back to manual overview</a></p>
|
||
<h1>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="/manual/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="/manual/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="/manual/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] <=”</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 & 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">
|
||
<div class="footer-grid">
|
||
<div>
|
||
<strong>KST4Contest</strong>
|
||
<p>Contest-optimized ON4KST workflow for VHF/UHF/SHF operators.</p>
|
||
</div>
|
||
|
||
<div>
|
||
<strong>Project</strong>
|
||
<p><a href="/features/">Features</a></p>
|
||
<p><a href="/download/">Download</a></p>
|
||
<p><a href="/manual/">Manual</a></p>
|
||
<p><a href="/roadmap/">Roadmap</a></p>
|
||
</div>
|
||
|
||
<div>
|
||
<strong>Community</strong>
|
||
<p><a href="https://github.com/praktimarc/kst4contest">GitHub Repository</a></p>
|
||
<p><a href="https://github.com/praktimarc/kst4contest/issues">Issues</a></p>
|
||
<p><a href="/contact/">Contact</a></p>
|
||
</div>
|
||
|
||
<div>
|
||
<strong>Legal</strong>
|
||
<p><a href="/legal-notice/">Legal Notice</a></p>
|
||
<p><a href="/privacy/">Privacy Policy</a></p>
|
||
</div>
|
||
</div>
|
||
</footer>
|
||
</body>
|
||
</html> |