Rsclub2_2/kst4contest
1
0
Fork 0
mirror of https://github.com/praktimarc/kst4contest.git synced 2026-08-27 04:28:41 +02:00
Code Issues Packages Projects Releases Wiki Activity

manual: overhaul cluster-server and feature list

Browse Source
This commit is contained in:
Marc Froehlich
2026-08-26 22:43:16 +02:00
parent 9378bf2afd
commit 7fe33613e9
3 changed files with 242 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
github_docs/de-DX-Cluster-Server.md
+24 -5
View File
@@ -23,7 +23,7 @@ Im Klartext: Die Information muss nicht erst im Chat gefunden, gelesen, gemerkt
---
## Wie wird eine Richtungsgelegenheit hergeleitet?
## Automatische Spots aus Richtungsgelegenheiten
Angenommen, Station A schreibt eine gerichtete Nachricht an Station B. KST4Contest verwendet die Richtung von A zu B als Näherung für die aktuelle Antennenrichtung von Station A. Anschließend wird geprüft, ob die eigene Station aus Sicht von A innerhalb des angenommenen Antennenkorridors liegt.
@@ -51,6 +51,22 @@ Das Verfahren berücksichtigt weder Gelände noch aktuelle Ausbreitungsbedingung
---
## Manueller Spot für die ausgewählte Kartenstation
Ein Spot kann auch bewusst ausgelöst werden. Wähle dazu eine Station auf der Stationskarte und verwende **Trigger cluster spot** im Detailbereich.
Diese manuelle Auslösung benötigt keine zuvor erkannte gerichtete Nachricht. Auch maximaler QRB und Antennen-Öffnungswinkel entscheiden in diesem Fall nicht darüber, ob der Spot gesendet wird. Erforderlich sind:
- ein aktivierter lokaler DX-Cluster-Server,
- mindestens ein verbundener DX-Cluster-Client und
- eine für die ausgewählte Kartenstation verwendbare QRG.
Damit kann der Operator eine bereits ausgewählte Station gezielt in die Bandmap übernehmen, auch wenn die Bedingungen für einen automatischen Richtungs-Spot nicht vorliegen. Die Bedienung der Karte ist unter [Stationskarte](de-Benutzeroberflaeche#stationskarte) beschrieben.
Automatische und manuelle Spots werden ausschließlich an die mit KST4Contest verbundenen Clients gesendet. Es erfolgt keine Weiterleitung an einen öffentlichen Internet-Cluster.
---
## Welche Frequenz wird verwendet?
Ein DX-Cluster-Spot benötigt eine eindeutige Frequenz. KST4Contest verwendet dafür dieselbe QRG-Erkennung wie die Benutzerliste und die übrigen bandbezogenen Funktionen.
@@ -171,12 +187,11 @@ Ein Spot enthält:
- das konfigurierte Spotter-Rufzeichen,
- die normalisierte Frequenz,
- das Rufzeichen der erkannten Station,
- das vollständige sichtbare Rufzeichen der erkannten oder ausgewählten Station,
- den Locator,
- Flugzeug-Scatter-Informationen, falls vorhanden,
- die aktuelle UTC-Zeit.
Wenn für die Station aktuelle Aircraft-Scatter-Informationen vorliegen, kann KST4Contest diese als zusätzliche AP-Information in den Kommentar des Spots aufnehmen.
Bei automatisch erzeugten Richtungs-Spots kann KST4Contest bis zu zwei aktuelle AirScout-Einträge als zusätzliche AP-Information in den Kommentar aufnehmen. Fehlende AirScout-Daten verhindern den Spot nicht. Ein manuell über die Stationskarte ausgelöster Spot verwendet den Locator der ausgewählten Station ohne diese optionale Ergänzung.
---
@@ -193,7 +208,7 @@ Prüfe:
- Blockiert eine Firewall die Verbindung?
- Ist im Logger das DX-Cluster-Fenster beziehungsweise die Bandmap aktiviert?
### Testspot funktioniert, aber reale Spots fehlen
### Testspot funktioniert, aber automatische Spots fehlen
Dann funktioniert die Verbindung grundsätzlich. Für die betreffende Chat-Situation war wahrscheinlich mindestens eine fachliche Bedingung nicht erfüllt:
@@ -205,6 +220,10 @@ Dann funktioniert die Verbindung grundsätzlich. Für die betreffende Chat-Situa
KST4Contest sendet absichtlich nicht jede gefundene Frequenz an den Logger. Andernfalls würde aus einer Arbeitserleichterung sehr schnell eine lokale Spot-Schleuder.
### Manuell ausgelöster Spot fehlt
Prüfe, ob auf der Karte eine Station ausgewählt ist und für sie eine verwendbare QRG vorliegt. Der lokale Server muss aktiviert und mindestens ein Client verbunden sein. Die Geometrie einer gerichteten Nachricht, maximaler QRB und Antennen-Öffnungswinkel sind für die manuelle Auslösung keine Voraussetzungen.
### Der Spot erscheint auf dem falschen Band
Prüfe zuerst, welche Frequenzen für die betreffende Station innerhalb der letzten 30 Minuten erkannt wurden. Bei einer relativen Angabe hat dieser Stationskontext Vorrang vor dem globalen Fallback.
github_docs/en-DX-Cluster-Server.md
+202 -44
View File
@@ -2,50 +2,164 @@
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-DX-Cluster-Server)
From **version 1.23**, KST4Contest includes a built-in DX cluster server. It sends spots directly to the logging software whenever a direction warning is triggered.
Since version 1.23, KST4Contest has included a local DX Cluster server. It forwards detected directional opportunities and their frequencies to the DX Cluster client of a logging programme.
*(Idea by OM0AAO, Viliam Petrik – thank you!)*
The idea came from OM0AAO, Viliam Petrik. Thank you!
---
## What is the Built-in DX Cluster Server For?
## Why Use a Local DX Cluster Server?
When KST4Contest detects that a station is requesting a sked from your direction and a QRG is known, it **automatically generates a DX cluster spot** and feeds it directly to the logging software's cluster client / band map.
Finding an interesting frequency in the chat is only the first step. During a contest, that information needs to reach the place where it can be used immediately: the logging programme and its bandmap.
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.
KST4Contest therefore combines two pieces of information it already has:
1. A directed chat message can indicate the approximate direction in which the sending station may be pointing its antenna.
2. A frequency for that station may be known from the same message or an earlier one.
When both pieces fit, KST4Contest creates a local DX Cluster spot. The logger can display it in its bandmap and, depending on its own configuration, tune the transceiver to the frequency when the spot is clicked.
In practical terms, the operator does not have to find the information in the chat, read it, remember it and enter it again in the logger. These small interruptions consume a surprising amount of attention during a contest.
---
## Setup
## Automatic Spots from Directional Opportunities
### In KST4Contest
Assume that station A sends a directed message to station B. KST4Contest uses the direction from A to B as an approximation of the current antenna direction of station A. It then checks whether the local station lies inside the assumed antenna corridor as seen from A.
In Preferences → **DX Cluster Server Settings**:
Two directions are compared:
1. Enter the **port** of the internal server (e.g. 7300 or 8000 – must match the logging software).
2. Enter a **spotter callsign** – **this must be a different callsign than your contest callsign!**
- 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.
3. Enter the **assumed MHz**: 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.
- the direction from station A to station B;
- the direction from station A to the local station.
### In UCXLog
The **Antenna Beamwidth** configured under the Station settings is the complete angle. Half of that value is applied on either side of the direction A → B. A setting of `70°` therefore produces a corridor of `±35°`.
- Configure a DX cluster server connection:
- Host: `127.0.0.1` (or IP of the KST4Contest computer)
- Port: As configured in KST4Contest
- Password: can be left empty
- Use the **"Send a test message to your log"** button to test the connection.
ON4KST does not supply antenna data for the remote station. KST4Contest therefore also uses the locally configured beamwidth as an approximation for station A. This is not a measurement of the station's actual antenna direction. It is a deliberately simple geometrical assumption.
### In N1MM+
An automatic DX Cluster spot is created only when all of the following conditions are met:
Similar settings:
- Host: `127.0.0.1` (or IP of the KST4Contest computer)
- Port: As configured in KST4Contest
1. A directed message between two other stations has been detected.
2. Valid locators are known for the sender and receiver.
3. The sender is within the configured **Default Maximum QRB** from the local station.
4. The local station lies inside the assumed antenna corridor as seen from the sender.
5. A usable frequency is known for the sender or detected in the current message.
6. The local DX Cluster server is enabled.
When these conditions are met, the spot is created while the message is processed. The green directional highlight shown in parallel remains visible for five minutes and may be extended or removed by later messages.
The calculation does not consider terrain, current propagation or the station's actual operating intention. It identifies a plausible opportunity. The full derivation and a numerical example are available under [Sked Direction Highlighting](en-Features#sked-direction-highlighting).
---
## Manual Spot for the Selected Map Station
A spot can also be triggered deliberately. Select a station on the station map and use **Trigger cluster spot** in the detail panel.
This manual action does not require a previously detected directed message. The maximum QRB and antenna beamwidth also do not decide whether the spot is sent. It requires:
- the local DX Cluster server to be enabled;
- at least one connected DX Cluster client; and
- a usable QRG for the selected map station.
This lets the operator send an already selected station to the bandmap even when the conditions for an automatic directional spot are not present. Map operation is described under [Station Map](en-User-Interface#station-map).
Both automatic and manual spots are sent only to clients connected to KST4Contest. They are not forwarded to a public Internet cluster.
---
## Which Frequency Is Used?
A DX Cluster spot needs an unambiguous frequency. KST4Contest uses the same QRG detection as the user list and the other band-related functions.
Complete frequencies determine their band directly:
```text
144.205
432,088
1296.338
10368.100
```
Relative values contain only the frequency part within a band:
```text
.205
,205
qrg 205
freq is 205
on 205
205 MHz
```
A bare three-digit number such as `205` is not evaluated without frequency-related context. The same applies to `599`, `144` or text such as `worked 210 stations`. This prevents signal reports, band names or QSO totals from being stored as plausible-looking frequencies and later sent to the logger.
For a relative QRG, KST4Contest determines the band in this order:
1. It checks whether a suitable band context has been detected for the same sender during the previous 30 minutes.
2. If several current bands are known, it uses the most recently updated plausible context.
3. Only when no suitable station context exists does it use the band selected under **Fallback band for relative QRG detection**.
Example:
```text
Global fallback: 144 MHz
Most recent complete QRG for the station: 432.088 MHz
New chat value from the same station: .100
Detected QRG: 432.100 MHz
DX Cluster frequency: 432100.0 kHz
```
Without the current 432 MHz context, the same value would use the global fallback and become `144.100 MHz`.
QRG detection runs before the direction and spot checks. If a station mentions its frequency for the first time in the directed message which also triggers a directional opportunity, the resulting spot can already contain that frequency. A newly detected QRG replaces an older value for the station.
The fallback band is a global QRG-detection setting. Its effect is not limited to the DX Cluster server. Configuration, supported bands and related behaviour are described under [Fallback Band for Relative QRG Detection](en-Configuration#fallback-band-for-relative-qrg-detection).
---
## Setting Up KST4Contest
Open the **Notification** tab in Preferences.
![Notification settings and local DX Cluster server](client_settings_window_notification.png)
Configure the following:
1. Enable **Enable the local DX Cluster server …**.
2. Enter a free **TCP port**. The default is `8000`.
3. Select the appropriate band under **Fallback band for relative QRG detection**.
4. Enter a **Spotter callsign**.
The spotter callsign should preferably differ from the contest callsign. Some loggers filter spots which appear to originate from the local station or handle them differently. Using the same callsign is not prohibited by KST4Contest, but it may make a correctly generated spot invisible in the bandmap.
Changes to the enabled state and TCP port take effect immediately while KST4Contest is connected to the chat. Changing the port disconnects existing DX Cluster clients; the logger must reconnect to the new port.
Use **Save Settings** to store the settings permanently in `preferences.xml`.
---
## Setting Up the Logging Programme
Configure the logging programme as a DX Cluster client connected to KST4Contest.
| Setting | KST4Contest and logger on the same computer | Logger on another computer |
|---|---|---|
| Host | `127.0.0.1` | IP address of the KST4Contest computer |
| Port | TCP port configured in KST4Contest | TCP port configured in KST4Contest |
| Login | Any callsign, if the logger requires one | Any callsign, if the logger requires one |
| Password | Not required | Not required |
KST4Contest does not use the login sent by the logger for authentication. The connection is intended for the local computer or a trusted station network.
If the logger runs on another computer, its TCP connection must be allowed through the local firewall on the KST4Contest computer. Do not expose the port directly to the Internet without additional protection.
Several DX Cluster clients can be connected at the same time. Every generated spot is sent to all clients which are currently connected.
---
## Testing the Connection
After the logger's DX cluster client has connected, use **Send test spot** to generate the following entry:
The **Send test spot** button creates the following test entry:
```text
Spotted callsign: DO5AMF
@@ -53,48 +167,92 @@ Comment: Testing DXC-Spot: Congrats, you donated $100!
Frequency: .300 on the configured fallback band
```
With `144 MHz` selected as the fallback band, the spot appears at approximately `144.300 MHz`.
With `144 MHz` selected as the fallback band, the spot therefore appears at approximately `144.300 MHz`.
The comment is a deliberately retained Easter egg. It makes the test entry easy to identify but has no other function. In particular, no donation or other external action is triggered.
The comment is a deliberately retained Easter egg. It only makes the test spot easy to recognise in the logger. No donation or other external action is triggered.
Three conditions must be met before running the test:
1. KST4Contest is connected to the ON4KST chat.
2. The local DX cluster server is enabled.
3. The logging software's DX cluster client is connected to KST4Contest.
2. The local DX Cluster server is enabled.
3. The logging programme's DX Cluster client is connected to KST4Contest.
If no client is connected, KST4Contest displays a corresponding message. A successful test therefore confirms that at least one connected client received the generated spot.
---
## How It Works
## Content of a Generated Spot
A spot is generated when **both** conditions are met:
A spot contains:
1. A **direction warning** has been triggered (station is making a sked in your direction).
2. The **station's QRG is known** (read from the chat or manually entered).
- the configured spotter callsign;
- the normalised frequency;
- the complete visible callsign of the detected or selected station;
- the locator; and
- the current UTC time.
The generated spot contains:
- Station's callsign
- Frequency
- Spot time
For automatically generated directional spots, KST4Contest can add up to two current AirScout entries to the comment. Missing AirScout data does not prevent the spot from being sent. A spot triggered manually from the station map uses the selected station's locator without this optional addition.
The logging software can then display the spot in the band map and tune the TRX to that frequency with a mouse click.
An automatic comment with AirScout information may look like this:
```text
JN49GL , AP: 1min, 100%; 4min, 75%
```
---
## Multi-Computer Setup
## If No Spot Appears
If KST4Contest runs on a separate computer (not the logging computer):
### The Test Spot Does Not Reach the Logger
- Host in the logging software: IP of the KST4Contest computer (not `127.0.0.1`)
- Same configuration as for the QSO UDP broadcast packets (see [Log Synchronisation](en-Log-Sync))
Check:
- Is KST4Contest connected to the chat?
- Is the local DX Cluster server enabled?
- Does the logger use the same TCP port?
- Does the logger use `127.0.0.1` when both programmes run locally?
- Is a firewall blocking the connection?
- Is the DX Cluster window or bandmap enabled in the logger?
### The Test Works, but Automatic Spots Are Missing
The TCP connection is then working in principle. At least one condition for the relevant chat situation was probably not met:
- no directed message between two other stations;
- missing locator;
- sender outside the maximum QRB;
- direction outside the configured beamwidth;
- no detected frequency.
KST4Contest deliberately does not send every frequency it finds to the logger. Otherwise, a feature intended to reduce distraction would quickly become a local spot generator with rather too much enthusiasm.
### A Manually Triggered Spot Is Missing
Check that a station is selected on the map and that it has a usable QRG. The local server must be enabled and at least one client must be connected. Directional-message geometry, maximum QRB and beamwidth are not prerequisites for the manual action.
### The Spot Appears on the Wrong Band
First check which frequencies were detected for the station during the previous 30 minutes. For a relative value, this station context takes priority over the global fallback.
If no current station context exists, check **Fallback band for relative QRG detection**. The fallback is used only when the band cannot be determined from a complete frequency or the sender's current context.
### The Logger Hides the Spot
Try a spotter callsign which differs from the contest callsign. Depending on the logger, spots from the local callsign may be filtered or handled specially. KST4Contest itself does not require the two callsigns to differ.
---
## Tested Logging Software
## Tested Logging Programmes
- **UCXLog** ✓
- **N1MM+** ✓
The interface has been used with:
Further test reports are welcome – please send by email to DO5AMF.
- UCXLog
- N1MM+
Other loggers may work if they support a normal TCP connection to a DX Cluster server and accept conventional `DX de ...` spot lines.
Related reference pages:
- [User Interface](en-User-Interface)
- [Features](en-Features)
- [Configuration](en-Configuration)
website/src/features/dx-cluster.md
+15 -10
View File
@@ -4,7 +4,7 @@ icon: 📡
category: Logger Integration
since: "1.23"
summary: Forward detected directional opportunities and their known frequencies as local DX Cluster spots to compatible contest loggers.
description: KST4Contest provides a local TCP DX Cluster server which turns selected ON4KST direction and frequency information into spots for a logger bandmap.
description: KST4Contest provides a local TCP DX Cluster server which forwards automatic directional opportunities or a manually selected map station to a logger bandmap.
tagsList:
- DX Cluster
- bandmap
@@ -29,9 +29,9 @@ The purpose is practical: when a station appears to be pointing in the local dir
That is the entire idea. The function is a bridge between the KST4Contest analysis and the logger, not another source of general DX traffic.
## When is a spot generated?
## Automatic and manual spots
A real spot is generated only when all of the following conditions are met:
An automatic spot is generated only when all of the following conditions are met:
1. A directed message between two other stations has been detected.
2. Valid locators are available for the sender and receiver.
@@ -39,10 +39,12 @@ A real spot is generated only when all of the following conditions are met:
4. The local station lies inside the assumed antenna corridor of the sender.
5. A usable frequency is known for the sender.
6. The local DX Cluster server is enabled.
7. At least one DX-Cluster client is connected to the server.
KST4Contest deliberately does not forward every frequency mentioned in the chat. Otherwise, a function intended to reduce distraction would produce its own local spot flood.
A spot can also be triggered deliberately. Select a station on the station map and use **Trigger cluster spot** in the detail panel. This manual action does not require a directed message, a match with the maximum QRB or a match with the configured antenna beamwidth. It uses the selected station and its known QRG directly.
For either route, at least one DX-Cluster client must be connected to receive the spot. Both automatic and manual spots remain inside the local or trusted station network; KST4Contest does not forward them to a public DX Cluster.
## How is the directional opportunity derived?
Assume that station A sends a directed message to station B. KST4Contest uses the direction from A to B as an approximation of the current antenna direction of station A.
@@ -124,22 +126,23 @@ A bare three-digit value is accepted only when the surrounding text identifies i
## What does the spot contain?
The generated spot contains:
Every generated spot contains:
- the configured spotter callsign;
- the normalised frequency;
- the complete callsign of the detected station;
- the sender's locator;
- up to two optional AirScout entries; and
- the complete visible callsign of the detected or selected station;
- the locator of that station;
- the current UTC time.
Automatically generated directional spots can additionally include up to two current AirScout entries. A manually triggered map spot uses the selected station's locator without this optional addition.
An example comment with AirScout information may look like this:
```text
JN49GL , AP: 1min, 100%; 4min, 75%
```
AirScout information is optional. A missing AirScout response does not prevent the spot from being sent.
AirScout information is optional. A missing AirScout response does not prevent an automatic directional spot from being sent.
> AP-independent spot creation, corrected sender-locator handling and band-generic frequency conversion are included from v1.42 onwards.
@@ -199,6 +202,8 @@ A successful test confirms that at least one client received the generated spot.
- Was a valid frequency known?
- Did a station-specific band context change the relative QRG?
For a manual spot, check that the station remains selected on the map and has a usable QRG. Maximum QRB, beamwidth and directed-message geometry are not prerequisites for **Trigger cluster spot**.
## What the spot means — and what it does not
The spot means that KST4Contest detected a plausible directional opportunity and knew a frequency for the sender.