mirror of
https://github.com/praktimarc/kst4contest.git
synced 2026-08-24 11:06:59 +02:00
Compare commits
8
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 Marc Froehlich
|
b00e4c1e3d | ||
|
Marc Froehlich
|
b3ca684f04 | ||
|
Marc Froehlich
|
1de9673d12 | ||
|
Marc Froehlich
|
c119f28b30 | ||
|
Marc Froehlich
|
6a7f07c62e | ||
|
Marc Froehlich
|
4f574ebec6 | ||
|
Marc Froehlich
|
7ce31e110b | ||
|
Marc Froehlich
|
92804a622a |
@@ -132,7 +132,24 @@ Im selben Bereich wird der aktuelle **Priority score** der ausgewählten Station
|
||||
|
||||
Mit **Sked fail** lässt sich ein fehlgeschlagener Versuch markieren. Der Score des normalisierten Basisrufzeichens wird dadurch stark reduziert. **Reset fail** entfernt diese Markierung wieder. Die Markierung gilt für alle aktiven Suffix- und Kategorievarianten der Station und bleibt innerhalb der laufenden Programmsitzung erhalten.
|
||||
|
||||
Darunter können ein Sked und die zugehörigen **Sked-Erinnerungen / Wecker** angelegt werden. Ein nahender Sked erhöht den Priority Score zeitabhängig; unmittelbar vor dem Termin erhält er eine sehr hohe Gewichtung.
|
||||
Darunter befinden sich die Bedienelemente zum Anlegen eines Skeds:
|
||||
|
||||
| Bedienelement | Bedeutung |
|
||||
|---|---|
|
||||
| **Sked in** | Zeit bis zum Sked |
|
||||
| **Band** | vereinbartes Band aus den eigenen aktivierten Bändern |
|
||||
| **Mode** | `SSB` oder `CW` für eine mögliche Win-Test-Übergabe |
|
||||
| **Create sked** | internen Sked anlegen |
|
||||
| **Remind-PM in** | automatische Reminder-PMs aktivieren |
|
||||
| **2+1**, **5+2+1**, **10+5+2+1** | Zeitpunkte der Reminder-PMs vor dem Termin |
|
||||
|
||||
|
||||
|
||||
Das vorgeschlagene Band wird aus aktuellen QRG- und Namensinformationen der Station hergeleitet. Vor dem Anlegen kann es ausdrücklich geändert werden. Die Mode-Auswahl betrifft nur die Übergabe an Win-Test; der interne Sked und die Reminder-PMs funktionieren unabhängig davon.
|
||||
|
||||
**Create sked** legt den Termin immer zuerst in KST4Contest an. Ist der Win-Test-Netzwerk-Listener aktiv, wird anschließend zusätzlich eine Übergabe an Win-Test versucht. Kann keine zum ausgewählten Band passende QRG ermittelt werden oder ist Win-Test nicht erreichbar, bleiben der interne Sked, seine Priorisierung und gegebenenfalls angelegte Reminder erhalten.
|
||||
|
||||
Die vollständige Herleitung und die Grenzen der Funktion sind unter [Skeds und Sked-Erinnerungen](de-Funktionen#skeds-und-sked-erinnerungen) beschrieben.
|
||||
|
||||
---
|
||||
|
||||
|
||||
+131
-21
@@ -313,19 +313,86 @@ Für ausgewählte Stationen in der Benutzerliste gibt es direkte Buttons, um das
|
||||
|
||||
---
|
||||
|
||||
## Sked-Erinnerungen mit ALERT (ab v1.40)
|
||||
## Skeds und Sked-Erinnerungen
|
||||
|
||||
Für jeden Chatmember kann ein Sked-Erinnerungsdienst mit automatischen Nachrichten aktiviert werden. Konfigurierbare Intervallmuster:
|
||||
> Verfügbar ab v1.40; Band-, Rufzeichen- und Win-Test-Behandlung erweitert in Nightly / v1.42.
|
||||
|
||||
- **2+1 Minuten**: Nachrichten bei 2 min und 1 min vor dem Sked.
|
||||
- **5+2+1 Minuten**: Nachrichten bei 5, 2 und 1 min vor dem Sked.
|
||||
- **10+5+2+1 Minuten**: Nachrichten bei 10, 5, 2 und 1 min vor dem Sked.
|
||||
Ein Sked ist mehr als eine Erinnerung an eine Uhrzeit. Er muss während des laufenden Contestbetriebs rechtzeitig sichtbar werden, die vereinbarte Station priorisieren und – sofern gewünscht – die Gegenstation noch einmal an den Termin erinnern.
|
||||
|
||||
Zusätzlich zu den Nachrichten an die Gegenstation gibt es eine **akustische und optische Benachrichtigung** für den eigenen Operator, sodass kein Sked vergessen wird.
|
||||
KST4Contest behandelt deshalb drei voneinander unabhängige Aufgaben:
|
||||
|
||||
Aktivierung: FurtherInfo-Panel der entsprechenden Station.
|
||||
1. Der Sked wird intern gespeichert und in die Prioritätsberechnung einbezogen.
|
||||
2. Der Termin erscheint in der AP- und Sked-Timeline.
|
||||
3. Optional werden vor dem Termin automatische Privatnachrichten gesendet.
|
||||
|
||||
Ist der Win-Test-Netzwerk-Listener aktiviert, versucht KST4Contest zusätzlich, den Sked an Win-Test zu übergeben. Ein Problem bei dieser Übergabe löscht oder verhindert den internen Sked nicht.
|
||||
|
||||
### Sked anlegen
|
||||
|
||||
Zuerst die gewünschte Station in der Benutzerliste auswählen. Die Bedienelemente befinden sich anschließend unten im Bereich **Further Info**.
|
||||
|
||||
| Bedienelement | Funktion |
|
||||
|---|---|
|
||||
| **Sked in** | Legt fest, in wie vielen Minuten der Sked stattfinden soll. Verfügbar sind 2 bis 15 sowie 20 Minuten. |
|
||||
| **Band** | Wählt das Band des Skeds. Angeboten werden die unter **Station → my station uses …** aktivierten eigenen Bänder. |
|
||||
| **Mode** | Legt den an Win-Test zu übertragenden Mode fest. Verfügbar sind `SSB` und `CW`. Die Auswahl hat keinen Einfluss auf den internen Sked oder die Reminder-PMs. |
|
||||
| **Create sked** | Legt den internen Sked an und versucht bei aktiviertem Win-Test-Netzwerk-Listener zusätzlich die Übergabe an Win-Test. |
|
||||
| **Remind-PM in** | Aktiviert die automatischen Privatnachrichten vor dem Termin. |
|
||||
| **2+1**, **5+2+1**, **10+5+2+1** | Legt fest, wie viele Minuten vor dem Sked die Reminder-PMs gesendet werden. |
|
||||
|
||||
|
||||
|
||||
KST4Contest versucht, ein sinnvolles Band vorzuwählen. Dafür werden nacheinander folgende Informationen verwendet:
|
||||
|
||||
1. eine höchstens 30 Minuten alte QRG der ausgewählten Station auf einem eigenen aktivierten Band,
|
||||
2. eine eindeutige Bandangabe im Namensfeld der Station und
|
||||
3. das erste aktivierte eigene Band.
|
||||
|
||||
Aktive Rufzeichenvarianten desselben Basisrufzeichens werden bei der Suche nach einer aktuellen Bandinformation gemeinsam betrachtet. Eine manuelle NOT-QRV-Markierung wird bei der automatischen Vorauswahl berücksichtigt. Das Band kann trotzdem ausdrücklich geändert werden, wenn der Operator bewusst eine andere Vereinbarung getroffen hat.
|
||||
|
||||
### Auswirkung auf den Priority Score
|
||||
|
||||
Ein eingetragener Sked erhöht den Score des normalisierten Basisrufzeichens:
|
||||
|
||||
| Zeitraum | Sked-Anteil am Score |
|
||||
|---|---:|
|
||||
| mehr als 15 Minuten vor dem Termin | `+40` |
|
||||
| 15 bis 3 Minuten vor dem Termin | kontinuierlicher Anstieg von `+300` bis in Richtung `+1200` |
|
||||
| weniger als 3 Minuten vor bis 1 Minute nach dem Termin | `+5000` |
|
||||
| später als 1 Minute nach dem Termin | kein Sked-Boost mehr |
|
||||
|
||||
Die starke Gewichtung unmittelbar vor dem Termin ist beabsichtigt. Ein vereinbarter Sked soll dann nicht durch eine gerade sehr aktive, aber nicht fest eingeplante Station aus der Prioritätsliste verdrängt werden.
|
||||
|
||||
Der Score wird für das Basisrufzeichen berechnet. Ein Sked mit `DN9APW-2` beeinflusst daher auch den gemeinsamen Score weiterer aktiver Varianten von `DN9APW`. Das konkrete Nachrichtenziel bleibt trotzdem `DN9APW-2` in der beim Anlegen ausgewählten Chat-Kategorie.
|
||||
|
||||
Fünf Minuten nach dem Termin wird der Sked aus der internen Liste entfernt.
|
||||
|
||||
### Reminder-PMs
|
||||
|
||||
Reminder-PMs werden nur angelegt, wenn **Remind-PM in** aktiviert ist. Je nach ausgewähltem Muster sendet KST4Contest beispielsweise zwei und eine Minute vor dem Sked folgende Privatnachricht:
|
||||
|
||||
```text
|
||||
[KST4C Autoreminder] sked in 2 min
|
||||
```
|
||||
|
||||
Die Nachricht geht an das vollständige sichtbare KST-Rufzeichen und in die Chat-Kategorie, in der der Sked angelegt wurde. Ein Sked für `DN9APW-2` wird daher nicht versehentlich an `DN9APW`, `DN9APW-70` oder eine gleichnamige Station in einer anderen Kategorie gesendet.
|
||||
|
||||
Beim tatsächlichen Reminder zeigt KST4Contest zusätzlich den optischen **SKED**-Hinweis an. Ist die einfache Soundausgabe aktiviert, wird außerdem ein Hinweiston abgespielt. Das bloße Aktivieren des Reminders löst noch kein Blinken aus.
|
||||
|
||||
Wird für dasselbe vollständige Rufzeichen ein neuer Satz Reminder aktiviert, ersetzt dieser die zuvor geplanten Reminder dieses Rufzeichens.
|
||||
|
||||
### Speicherung und Grenzen
|
||||
|
||||
Skeds und Reminder-Zeitpläne werden nur im Arbeitsspeicher geführt. Nach einem Neustart von KST4Contest müssen noch benötigte Termine erneut angelegt werden.
|
||||
|
||||
Die automatische Bandvorauswahl ist eine Herleitung aus vorhandenen Chatinformationen. Sie beweist nicht, dass die Station noch auf der zuletzt genannten QRG arbeitet. Band, Uhrzeit und Mode sollten deshalb vor **Create sked** kontrolliert werden.
|
||||
|
||||
Bedienung: [Stationsinfo-Panel](de-Benutzeroberflaeche#stationsinfo-panel-further-info)
|
||||
|
||||
Darstellung: [AP- und Sked-Timeline](#ap-und-sked-timeline)
|
||||
|
||||
Win-Test-Übergabe: [Log-Synchronisation – Win-Test](de-Log-Synchronisation#win-test)
|
||||
|
||||
---
|
||||
|
||||
## QSO-Monitoring (ab v1.31)
|
||||
|
||||
@@ -337,17 +404,23 @@ Konfiguration: [Konfiguration – Sniffer-Einstellungen](de-Konfiguration#sniffe
|
||||
|
||||
---
|
||||
|
||||
## Win-Test-Integration (ab v1.31, vollständig ab v1.40)
|
||||
## Win-Test-Integration
|
||||
|
||||
KST4Contest unterstützt [Win-Test](https://www.win-test.com/) vollständig als Logprogramm:
|
||||
KST4Contest verwendet für Win-Test einen eigenen Listener für das native Win-Test-Netzwerkprotokoll. Darüber werden drei voneinander getrennte Funktionen bereitgestellt:
|
||||
|
||||
- **Log-Synchronisation**: Gearbeitete Stationen werden automatisch aus Win-Test übernommen und in der Benutzerliste markiert.
|
||||
- **Frequenz-Auswertung**: Die aktuelle TRX-Frequenz wird aus Win-Test-UDP-Paketen ausgewertet und befüllt die `MYQRG`-Variable.
|
||||
- **Sked-Übergabe (SKED Push via UDP)**: Vereinbarte Skeds aus KST4Contest können direkt an Win-Test übertragen werden, sodass das Rufzeichen der Gegenstation im Win-Test-Sked-Fenster erscheint.
|
||||
- neue QSOs einschließlich Band- und gegebenenfalls Locatorinformation übernehmen,
|
||||
- die aktuelle QRG aus Win-Test-STATUS-Paketen auswerten und
|
||||
- intern angelegte Skeds als `ADDSKED` an das Win-Test-Netzwerk übergeben.
|
||||
|
||||
Bei der Sked-Übergabe wird die QRG nicht durch eine feste Standardfrequenz ersetzt. KST4Contest sendet nur dann einen Win-Test-Sked, wenn eine zum ausgewählten Band passende QRG ermittelt werden konnte. Der interne Sked, die Timeline und die Reminder-PMs funktionieren unabhängig davon weiter.
|
||||
|
||||
Ein sichtbarer KST-Suffix wie `-2`, `-70` oder `-144` bleibt innerhalb von KST4Contest erhalten, wird für das Win-Test-Logrufzeichen jedoch entfernt. Portable Bestandteile wie `/P`, `/M` oder ein Länderpräfix bleiben bestehen.
|
||||
|
||||
Einrichtung und genaue Datenbehandlung: [Log-Synchronisation – Win-Test](de-Log-Synchronisation#win-test)
|
||||
|
||||
Einstellungen: [Win-Test-Netzwerk-Listener](de-Konfiguration#win-test-netzwerk-listener-ab-v131)
|
||||
|
||||
Details zur Konfiguration: [Konfiguration – Win-Test-Netzwerk-Listener](de-Konfiguration#win-test-netzwerk-listener)
|
||||
|
||||
---
|
||||
|
||||
## PSTRotator-Interface (ab v1.31, vollständig ab v1.40)
|
||||
|
||||
@@ -482,16 +555,53 @@ Zugehörige Einstellungen:
|
||||
|
||||
---
|
||||
|
||||
## AP-Timeline (ab v1.40)
|
||||
## AP- und Sked-Timeline
|
||||
|
||||
Eine visuelle Zeitleiste zeigt für jeden möglichen AP-Ankunftsminuten-Slot bis zu 4 hochbewertete Stationen, die per Aircraft Scatter erreichbar wären. Priorisierungskriterien:
|
||||
Die Timeline stellt bevorstehende Aircraft-Scatter-Gelegenheiten und eingetragene Skeds für die nächsten 30 Minuten gemeinsam dar. Sie beantwortet damit zwei Fragen auf einen Blick:
|
||||
|
||||
- Bevorzugt werden APs mit dem **höchsten Reflexionspotenzial** (nicht unbedingt die schnellste Ankunft).
|
||||
- Stationen, auf die die eigene Antenne nicht zeigt, werden **transparent** dargestellt.
|
||||
- Wann entsteht voraussichtlich eine interessante AP-Gelegenheit?
|
||||
- Welcher bereits vereinbarte Sked nähert sich unabhängig davon?
|
||||
|
||||
So kann der Contest-Operator auf einem Blick sehen, welche Stationen wann und über welche Flugzeuge erreichbar sein werden.
|
||||
Weiter in der Zukunft liegende Ereignisse erscheinen rechts. Mit ablaufender Zeit wandern sie nach links in Richtung des aktuellen Zeitpunkts.
|
||||
|
||||
---
|
||||
|
||||
|
||||
### AP-Kandidaten
|
||||
|
||||
AP-Kandidaten erscheinen in den oberen Spuren. Pro Ankunftsminute können bis zu vier ausgewählte Kandidaten dargestellt werden. Die Auswahl berücksichtigt den Priority Score und das von AirScout gemeldete Reflexionspotenzial.
|
||||
|
||||
Die Farbe des AP-Symbols kennzeichnet das Reflexionspotenzial:
|
||||
|
||||
| Farbe | Reflexionspotenzial |
|
||||
|---|---:|
|
||||
| Magenta | mindestens 95 % |
|
||||
| Rot | mindestens 75 % |
|
||||
| Gelb | mindestens 50 % |
|
||||
| Blau | unter 50 % |
|
||||
|
||||
Die Farbe ist keine QSO-Wahrscheinlichkeit. Sie gibt den von AirScout übernommenen Wert für die berechnete Reflexionsgeometrie wieder.
|
||||
|
||||
Ein Klick auf einen AP-Kandidaten wählt den dazugehörigen aktiven Chatmember einschließlich Rufzeichensuffix und Chat-Kategorie aus. Dadurch kann unmittelbar eine passende Nachricht vorbereitet werden.
|
||||
|
||||
### Skeds
|
||||
|
||||
Skeds erscheinen als Rauten in der unteren Spur. Die Beschriftung verwendet das vollständige KST-Rufzeichen, beispielsweise `SKED: DN9APW-2`. Dadurch bleibt erkennbar, welcher konkrete Login für den Termin ausgewählt wurde.
|
||||
|
||||
Der Tooltip eines Skeds zeigt mindestens:
|
||||
|
||||
- das vollständige KST-Rufzeichen,
|
||||
- das vereinbarte Band und
|
||||
- den QTF zur Gegenstation.
|
||||
|
||||
Sind passende AirScout-Daten vorhanden, werden zusätzlich die aktuelle AP-Erreichbarkeit und die nächste berechnete AP-Gelegenheit angezeigt.
|
||||
|
||||
### Berücksichtigung der Antennenrichtung
|
||||
|
||||
Liegt der QTF eines Ereignisses deutlich außerhalb der aktuellen Antennenrichtung, wird dessen Symbol transparenter dargestellt. Die Beschriftung bleibt lesbar. Liegt das Ziel nahe der Mitte des konfigurierten Antennenbereichs, wird das Symbol zusätzlich hervorgehoben.
|
||||
|
||||
Diese Darstellung verändert weder den Sked noch den Priority Score. Sie ist eine optische Hilfe, um Kandidaten in der aktuellen Antennenrichtung schneller zu erkennen.
|
||||
|
||||
Die Timeline ist eine Vorschau. AirScout-Daten können sich ändern, und ein eingetragener Sked garantiert weder eine freie Frequenz noch eine tatsächlich vorhandene Ausbreitungsverbindung.
|
||||
|
||||
## Intervall-Beacon
|
||||
|
||||
|
||||
@@ -354,20 +354,45 @@ Weitere Hintergründe: [Automatische Antworten auf Privatnachrichten](de-Funktio
|
||||
|
||||
## Win-Test-Netzwerk-Listener (ab v1.31)
|
||||
|
||||
Dedizierter Empfänger für Win-Test-spezifische UDP-Pakete. Ermöglicht:
|
||||
Der Win-Test-Netzwerk-Listener verarbeitet das native Win-Test-UDP-Protokoll. Er ist vom allgemeinen QSO-UDP-Listener auf Port `12060` unabhängig und übernimmt drei Aufgaben:
|
||||
|
||||
- **Log-Synchronisation**: Gearbeitete Stationen werden aus Win-Test übernommen und in der Benutzerliste markiert.
|
||||
- **Frequenz-Auswertung**: Die aktuelle TRX-Frequenz aus Win-Test befüllt die `MYQRG`-Variable.
|
||||
- **Sked-Übergabe (SKED Push)**: Skeds aus KST4Contest werden via UDP direkt an Win-Test übergeben. Der UDP-Broadcast-Standardport von Win-Test (9871) wird verwendet.
|
||||
- QSOs einschließlich Band- und Locatorinformation auswerten,
|
||||
- STATUS-Pakete für die eigene QRG verarbeiten und
|
||||
- Skeds an das Win-Test-Netzwerk übergeben.
|
||||
|
||||
Einstellungen:
|
||||
- **Aktivieren/Deaktivieren**: Checkbox in den Preferences (ab v1.40).
|
||||
- **Port**: Konfigurierbarer UDP-Port für den Win-Test-Listener.
|
||||
- **Sked-UDP-Adresse und Port**: Zieladresse und Port für die SKED-Übergabe an Win-Test.
|
||||
### Einstellungen unter Log sync
|
||||
|
||||
> **Hinweis**: Der Win-Test-Listener ist ein **zusätzlicher** Listener – der Standard-QSO-UDP-Broadcast-Listener auf Port 12060 bleibt davon unabhängig.
|
||||
| Einstellung | Funktion |
|
||||
|---|---|
|
||||
| **Receive Win-Test network based UDP log messages** | Aktiviert den Win-Test-Netzwerk-Listener. Bei aktiviertem Listener wird nach **Create sked** auch die Sked-Übergabe versucht. |
|
||||
| **UDP-Port for Win-Test listener** | Port des Win-Test-Netzwerks. Standard ist `9871`. Der Port wird auch für die Sked-Übergabe verwendet. |
|
||||
| **KST station name in Win-Test network (src of SKED packets)** | Stationsname, unter dem KST4Contest die Sked-Pakete sendet. In einem Netzwerk mit mehreren Clients sollte ein eindeutiger Name verwendet werden. |
|
||||
| **Win-Test network broadcast address** | Zieladresse für ausgehende Win-Test-Netzwerkpakete. Bei lokalem Netzwerkbetrieb muss hier eine vom Win-Test-Rechner erreichbare Broadcast-Adresse eingetragen sein. |
|
||||
|
||||
Die Broadcast-Adresse ist konfigurierbar, weil `255.255.255.255` nicht in jedem Stationsnetz und nicht über jede Netzwerkschnittstelle zuverlässig weitergeleitet wird. Bei mehreren Rechnern kann stattdessen die zum Stationsnetz gehörende gerichtete Broadcast-Adresse erforderlich sein.
|
||||
|
||||
### Einstellungen unter TRX sync
|
||||
|
||||
| Einstellung | Funktion |
|
||||
|---|---|
|
||||
| **Win-Test STATUS QRG Sync** | Übernimmt die aktuelle Frequenz aus Win-Test-STATUS-Paketen als eigene QRG. |
|
||||
| **Use pass frequency from Win-Test STATUS** | Verwendet die übertragene Pass-Frequenz anstelle der normalen TRX-QRG. |
|
||||
| **Win-Test station name filter** | Verarbeitet nur STATUS-Pakete der angegebenen Win-Test-Station. Ein leeres Feld akzeptiert alle Stationsnamen. |
|
||||
|
||||
Der Stationsfilter ist insbesondere bei mehreren Win-Test-Clients sinnvoll. Ohne Filter kann die zuletzt eingegangene STATUS-Meldung eines anderen Arbeitsplatzes die eigene QRG in KST4Contest überschreiben.
|
||||
|
||||
### Sked-Übergabe
|
||||
|
||||
Für die Sked-Übergabe gibt es keinen davon getrennten internen Sked-Modus. Ist der Listener aktiviert, versucht **Create sked** zusätzlich zur internen Anlage die Übertragung an Win-Test.
|
||||
|
||||
KST4Contest sendet nur dann ein `ADDSKED`-Paket, wenn eine QRG ermittelt wurde, die zum ausdrücklich ausgewählten Band gehört. Kann keine passende QRG gefunden werden, bleibt der interne Sked bestehen und die Win-Test-Übergabe wird ausgelassen.
|
||||
|
||||
Die Auswahl `SSB` oder `CW` erfolgt direkt im Further-Info-Bereich beim Anlegen des Skeds. Eine automatische Mode-Ableitung wird nicht verwendet.
|
||||
|
||||
Nach Änderungen **Save Settings** verwenden, damit Port, Stationsname, Broadcast-Adresse und TRX-Optionen beim nächsten Programmstart wiederhergestellt werden.
|
||||
|
||||
Datenbehandlung und QRG-Auswahl: [Log-Synchronisation – Win-Test](de-Log-Synchronisation#win-test)
|
||||
|
||||
---
|
||||
|
||||
## PSTRotator-Einstellungen (ab v1.31)
|
||||
|
||||
|
||||
@@ -86,35 +86,76 @@ Beim Broadcast des vollständigen Logbuchs verwendet DXLog.net `contactreplace`
|
||||
|
||||
### Win-Test
|
||||
|
||||
Win-Test wird mit einem dedizierten UDP-Netzwerk-Listener unterstützt, der das native Win-Test Netzwerkprotokoll versteht.
|
||||
Win-Test wird über einen eigenen UDP-Listener für das native Win-Test-Netzwerkprotokoll angebunden. Dieser Listener ist vom allgemeinen QSO-UDP-Listener auf Port `12060` unabhängig.
|
||||
|
||||
Bei einem neuen QSO übernimmt KST4Contest das Rufzeichen und löst die native Win-Test-Band-ID auf. Dabei werden auch 50 und 70 MHz verarbeitet. Ist im Paket ein gültiger Locator enthalten, wird zusätzlich das gearbeitete Großfeld für das erkannte Band gespeichert.
|
||||
#### QSO- und Worked-Synchronisation
|
||||
|
||||
**Vorteile der Win-Test Integration:**
|
||||
- **Bandbezogene Worked-Daten:** Neue QSOs setzen die Worked-Markierung des von Win-Test gemeldeten Bandes und aktualisieren – sofern vorhanden – den Großfeldstatus.
|
||||
- Automatische QSO-Synchronisation zur Markierung gearbeiteter Stationen.
|
||||
- **Sked-Übergabe (ADDSKED):** Über den Button "Create sked" im Stationsinfo-Panel wird nicht nur in KST4Contest ein Sked angelegt, sondern dieser auch *direkt per UDP an das Win-Test Netzwerk als ADDSKED-Paket gesendet* – automatisch, sobald der Listener aktiv ist.
|
||||
- Es kann zwischen den Sked-Modi "AUTO", "SSB" oder "CW" gewählt werden.
|
||||
- **Automatische QRG-Auflösung für SKEDs:** KST4Contest wählt die Sked-Frequenz intelligent:
|
||||
1. Hat die Gegenstation in einer Chat-Nachricht ihre QRG genannt, wird diese verwendet.
|
||||
2. Sonst wird die eigene aktuelle QRG verwendet (aus Win-Test STATUS oder manueller Eingabe).
|
||||
Bei einem neuen QSO übernimmt KST4Contest:
|
||||
|
||||
**Einstellungen im Reiter „Log-Synchronisation":**
|
||||
- `Receive Win-Test network based UDP log messages` aktivieren.
|
||||
- `UDP-Port for Win-Test listener` (Standard: 9871).
|
||||
- `KST station name in Win-Test network (src of SKED packets)`: Legt fest, unter welchem Stationsnamen KST4Contest im WT-Netzwerk auftritt (z.B. "KST").
|
||||
- `Win-Test network broadcast address`: Wird i.d.R. automatisch erkannt; erforderlich für das Senden von Sked-Paketen.
|
||||
- das geloggte Rufzeichen,
|
||||
- die native Win-Test-Band-ID und
|
||||
- einen gültigen Locator, sofern er im Paket enthalten ist.
|
||||
|
||||
**Einstellungen im Reiter „TRX-Synchronisation":**
|
||||
- `Win-Test STATUS QRG Sync`: Wenn aktiviert, übernimmt KST4Contest die aktuelle Transceiverfrequenz aus dem Win-Test STATUS-Paket als eigene QRG (MYQRG).
|
||||
- `Use pass frequency from Win-Test STATUS`: Statt der eigenen TRX-QRG wird die im STATUS-Paket enthaltene Pass-Frequenz als MYQRG verwendet (für Multi-Op-Setups, bei denen mit einer Pass-QRG gearbeitet wird).
|
||||
- `Win-Test station name filter`: Wird hier ein Name eingetragen (z.B. "STN1"), verarbeitet KST4Contest nur Pakete dieser Win-Test-Instanz. Leer lassen, um alle zu akzeptieren.
|
||||
Die Band-IDs für 50 und 70 MHz werden ebenso verarbeitet wie die VHF-, UHF- und SHF-Bänder. Das Rufzeichen wird global und auf dem erkannten Band als gearbeitet markiert. Liegt zusätzlich ein Locator vor, wird dessen vierstelliges Großfeld für dieses Band gespeichert.
|
||||
|
||||
**Einstellungen in Win-Test:**
|
||||
- Das Netzwerk in Win-Test muss aktiv sein.
|
||||
- Win-Test muss so konfiguriert sein, dass es seine Broadcasts an den entsprechenden Port (Standard 9871) sendet bzw. empfängt.
|
||||
Die Daten werden in derselben internen Datenbank abgelegt wie Worked-Informationen aus den übrigen QSO-UDP-Schnittstellen und nach einem Neustart wiederhergestellt.
|
||||
|
||||
#### Skeds an Win-Test übergeben
|
||||
|
||||
Mit **Create sked** wird zunächst ein interner KST4Contest-Sked angelegt. Ist der Win-Test-Netzwerk-Listener aktiviert, versucht KST4Contest anschließend automatisch, den Sked als `ADDSKED` an das Win-Test-Netzwerk zu übertragen.
|
||||
|
||||
Die QRG wird in folgender Reihenfolge bestimmt:
|
||||
|
||||
1. KST4Contest sucht die neueste, höchstens 30 Minuten alte QRG der Gegenstation auf dem ausdrücklich ausgewählten Band. Dabei werden aktive Varianten desselben Basisrufzeichens gemeinsam ausgewertet.
|
||||
2. Fehlt eine solche QRG, wird die eigene QRG der Chat-Kategorie geprüft, in der der Sked angelegt wurde. Sie wird nur verwendet, wenn sie sich auswerten lässt und tatsächlich zum ausgewählten Band gehört.
|
||||
3. Kann auf keinem dieser Wege eine passende QRG ermittelt werden, wird kein `ADDSKED` gesendet.
|
||||
|
||||
Eine feste Ersatzfrequenz wie `144.300` wird bewusst nicht verwendet. Eine technisch erfolgreiche Übergabe mit falschem Band oder falscher QRG wäre im Contestbetrieb schlechter als eine sichtbar ausgelassene Übergabe.
|
||||
|
||||
Der interne Sked bleibt in jedem Fall erhalten. Das gilt auch bei einer ungültigen Broadcast-Adresse, einem Netzwerkfehler oder einem nicht erreichbaren Win-Test-Client.
|
||||
|
||||
#### Behandlung von KST-Rufzeichensuffixen
|
||||
|
||||
KST-Suffixe kennzeichnen häufig den verwendeten Chat-Login oder ein Band. Sie gehören nicht in jedem Fall zum Logrufzeichen. Für Win-Test entfernt KST4Contest deshalb einen mit `-` abgetrennten KST-Suffix, erhält aber portable und internationale Rufzeichenbestandteile:
|
||||
|
||||
| Rufzeichen im KST-Chat | Übergabe an Win-Test |
|
||||
|---|---|
|
||||
| `DN9APW-2` | `DN9APW` |
|
||||
| `9A0BB-70` | `9A0BB` |
|
||||
| `EA5/G8MBI/P-70` | `EA5/G8MBI/P` |
|
||||
| `DN9APW-2/P` | `DN9APW/P` |
|
||||
|
||||
Innerhalb von KST4Contest bleibt das vollständige Rufzeichen erhalten. Timeline, Reminder-PMs und Chat-Kategorie beziehen sich weiterhin auf den konkret ausgewählten Login.
|
||||
|
||||
#### Mode, Zeitpunkt und Notizen
|
||||
|
||||
Der Mode wird beim Anlegen des Skeds ausdrücklich als `SSB` oder `CW` gewählt. Eine automatische Ableitung aus der QRG findet nicht statt, weil eine begrenzte Liste angenommener Bandsegmente nicht alle unterstützten VHF-, UHF- und SHF-Bänder zuverlässig abbilden kann.
|
||||
|
||||
KST4Contest überträgt den tatsächlichen Sked-Zeitpunkt ohne einen zusätzlichen Minutenversatz. Die Notizen enthalten – soweit bekannt – Locator und QTF sowie den Hinweis, dass der Sked über KST4Contest angelegt wurde.
|
||||
|
||||
Für die Übergabe sendet KST4Contest die Win-Test-Pakete `LOCKSKED`, `ADDSKED` und `UNLOCKSKED`.
|
||||
|
||||
|
||||
|
||||
#### Einstellungen
|
||||
|
||||
Im Reiter **Log sync**:
|
||||
|
||||
- `Receive Win-Test network based UDP log messages`
|
||||
- `UDP-Port for Win-Test listener`, standardmäßig `9871`
|
||||
- `KST station name in Win-Test network (src of SKED packets)`
|
||||
- `Win-Test network broadcast address`
|
||||
|
||||
Im Reiter **TRX sync**:
|
||||
|
||||
- `Win-Test STATUS QRG Sync`
|
||||
- `Use pass frequency from Win-Test STATUS`
|
||||
- `Win-Test station name filter`
|
||||
|
||||
Das Win-Test-Netzwerk muss in Win-Test aktiviert sein. Bei mehreren Computern muss die Broadcast-Adresse das betreffende lokale Netzwerk erreichen. Der Stationsname sollte die sendende KST4Contest-Instanz innerhalb des Win-Test-Netzwerks eindeutig erkennen lassen.
|
||||
|
||||
Ausführliche Beschreibung der Einstellungen: [Win-Test-Netzwerk-Listener](de-Konfiguration#win-test-netzwerk-listener-ab-v131)
|
||||
|
||||
---
|
||||
|
||||
## TRX-Frequenz-Synchronisation
|
||||
|
||||
|
||||
@@ -205,18 +205,44 @@ New settings section with the following options:
|
||||
|
||||
## Win-Test Network Listener (from v1.31)
|
||||
|
||||
A dedicated listener for Win-Test-specific UDP packets. Enables:
|
||||
The Win-Test network listener processes the native Win-Test UDP protocol. It is independent of the general QSO UDP listener on port `12060` and has three separate tasks:
|
||||
|
||||
- **Log synchronisation**: Worked stations are retrieved from Win-Test and marked in the user list.
|
||||
- **Frequency parsing**: The current TRX frequency from Win-Test populates the `MYQRG` variable.
|
||||
- **Sked handover (SKED push)**: Skeds from KST4Contest are passed directly to Win-Test via UDP. Win-Test's default UDP broadcast port (9871) is used.
|
||||
- processing QSOs including band and locator information,
|
||||
- processing STATUS packets for the local QRG, and
|
||||
- handing skeds over to the Win-Test network.
|
||||
|
||||
Settings:
|
||||
- **Enable/Disable**: Checkbox in Preferences (from v1.40).
|
||||
- **Port**: Configurable UDP port for the Win-Test listener.
|
||||
- **Sked UDP address and port**: Target address and port for SKED handover to Win-Test.
|
||||
### Log sync settings
|
||||
|
||||
> **Note**: The Win-Test listener is an **additional** listener – the standard QSO UDP broadcast listener on port 12060 remains independent.
|
||||
| Setting | Function |
|
||||
|---|---|
|
||||
| **Receive Win-Test network based UDP log messages** | Enables the Win-Test network listener. When the listener is enabled, pressing **Create sked** also attempts the Win-Test handover. |
|
||||
| **UDP-Port for Win-Test listener** | Port used by the Win-Test network. The default is `9871`. The same port is used for the sked handover. |
|
||||
| **KST station name in Win-Test network (src of SKED packets)** | Station name used by KST4Contest when sending sked packets. A unique name should be used in a network containing several clients. |
|
||||
| **Win-Test network broadcast address** | Destination address for outgoing Win-Test network packets. In a local network, the address must be reachable by the Win-Test computer. |
|
||||
|
||||
The broadcast address is configurable because `255.255.255.255` is not forwarded reliably through every station network or network interface. In a multi-computer setup, the directed broadcast address belonging to the station network may be required instead.
|
||||
|
||||
### TRX sync settings
|
||||
|
||||
| Setting | Function |
|
||||
|---|---|
|
||||
| **Win-Test STATUS QRG Sync** | Takes the current frequency from Win-Test STATUS packets and uses it as the local QRG. |
|
||||
| **Use pass frequency from Win-Test STATUS** | Uses the transmitted pass frequency instead of the normal TRX QRG. |
|
||||
| **Win-Test station name filter** | Only processes STATUS packets from the specified Win-Test station. An empty field accepts every station name. |
|
||||
|
||||
The station filter is particularly useful when several Win-Test clients are active. Without a filter, the most recently received STATUS packet from another operating position can overwrite the local QRG in KST4Contest.
|
||||
|
||||
### Sked handover
|
||||
|
||||
There is no separate internal sked mode for the Win-Test handover. When the listener is enabled, **Create sked** attempts the Win-Test transfer in addition to creating the internal sked.
|
||||
|
||||
KST4Contest only sends an `ADDSKED` packet when it can determine a QRG which belongs to the explicitly selected band. If no matching QRG is available, the internal sked remains intact and the Win-Test handover is omitted.
|
||||
|
||||
`SSB` or `CW` is selected directly in the Further Info section when the sked is created. No automatic mode inference is used.
|
||||
|
||||
Click **Save Settings** after making changes so that the port, station name, broadcast address and TRX options are restored at the next start.
|
||||
|
||||
Data handling and QRG selection: [Log Synchronisation – Win-Test](en-Log-Sync#win-test)
|
||||
|
||||
---
|
||||
|
||||
|
||||
+132
-21
@@ -211,19 +211,86 @@ For selected stations in the user list, there are direct buttons to open the **Q
|
||||
|
||||
---
|
||||
|
||||
## Sked Reminders with ALERT (from v1.40)
|
||||
## Skeds and Sked Reminders
|
||||
|
||||
A sked reminder service with automatic messages can be activated for each chat member. Configurable interval patterns:
|
||||
> Available from v1.40; band, callsign and Win-Test handling extended in Nightly / v1.42.
|
||||
|
||||
- **2+1 minutes**: Messages at 2 min and 1 min before the sked.
|
||||
- **5+2+1 minutes**: Messages at 5, 2 and 1 min before the sked.
|
||||
- **10+5+2+1 minutes**: Messages at 10, 5, 2 and 1 min before the sked.
|
||||
A sked is more than a reminder tied to a particular time. During a contest, it must become visible early enough, move the agreed station up the priority list and – if required – remind the remote station as well.
|
||||
|
||||
In addition to the automated messages to the remote station, there is an **acoustic and visual notification** for your own operator so no sked is ever missed.
|
||||
KST4Contest therefore treats three tasks separately:
|
||||
|
||||
Activate from the FurtherInfo panel of the corresponding station.
|
||||
1. The sked is stored internally and included in the priority calculation.
|
||||
2. The scheduled contact appears in the AP and sked timeline.
|
||||
3. Automatic private reminder messages can optionally be sent before the agreed time.
|
||||
|
||||
When the Win-Test network listener is enabled, KST4Contest also attempts to hand the sked over to Win-Test. A failed handover neither removes nor prevents the internal sked.
|
||||
|
||||
### Creating a sked
|
||||
|
||||
First select the required station in the user list. The sked controls then appear at the bottom of the **Further Info** section.
|
||||
|
||||
| Control | Function |
|
||||
|---|---|
|
||||
| **Sked in** | Sets the number of minutes until the sked. Available values are 2 through 15 and 20 minutes. |
|
||||
| **Band** | Selects the sked band. The dropdown contains the local bands enabled under **Station → my station uses …**. |
|
||||
| **Mode** | Sets the mode passed to Win-Test. Available values are `SSB` and `CW`. This selection does not affect the internal sked or reminder PMs. |
|
||||
| **Create sked** | Creates the internal sked and, if the Win-Test network listener is enabled, also attempts the Win-Test handover. |
|
||||
| **Remind-PM in** | Enables automatic private reminder messages before the sked. |
|
||||
| **2+1**, **5+2+1**, **10+5+2+1** | Selects how many minutes before the sked the reminder PMs are sent. |
|
||||
|
||||
|
||||
|
||||
KST4Contest attempts to preselect a useful band. It checks the following information in this order:
|
||||
|
||||
1. a QRG of the selected station which is no more than 30 minutes old and belongs to a locally enabled band,
|
||||
2. an unambiguous band designator in the station's name field, and
|
||||
3. the first locally enabled band.
|
||||
|
||||
Active callsign variants belonging to the same base callsign are evaluated together when looking for recent band information. A manual NOT-QRV mark is taken into account by the automatic selection. The operator can still select another band explicitly when a different arrangement has been made.
|
||||
|
||||
### Effect on the Priority Score
|
||||
|
||||
A stored sked raises the score of the normalised base callsign:
|
||||
|
||||
| Time relative to the sked | Contribution to the score |
|
||||
|---|---:|
|
||||
| more than 15 minutes before the sked | `+40` |
|
||||
| 15 to 3 minutes before the sked | continuous increase from `+300` towards `+1200` |
|
||||
| less than 3 minutes before until 1 minute after the sked | `+5000` |
|
||||
| more than 1 minute after the sked | no remaining sked boost |
|
||||
|
||||
The strong weighting immediately around the scheduled time is intentional. An agreed sked should not disappear from the priority list merely because another station is currently very active but has no fixed appointment.
|
||||
|
||||
The score is calculated for the base callsign. A sked created for `DN9APW-2` therefore also affects the shared score of other active `DN9APW` variants. The actual message target nevertheless remains `DN9APW-2` in the chat category selected when the sked was created.
|
||||
|
||||
The sked is removed from the internal list five minutes after its scheduled time.
|
||||
|
||||
### Reminder PMs
|
||||
|
||||
Reminder PMs are only scheduled when **Remind-PM in** is enabled. Depending on the selected pattern, KST4Contest sends a private message such as the following two and one minute before the sked:
|
||||
|
||||
```text
|
||||
[KST4C Autoreminder] sked in 2 min
|
||||
```
|
||||
|
||||
The message is sent to the complete visible KST callsign in the chat category in which the sked was created. A sked for `DN9APW-2` is therefore not accidentally sent to `DN9APW`, `DN9APW-70` or a similarly named station in another category.
|
||||
|
||||
When a reminder is actually triggered, KST4Contest also displays the visual **SKED** indication. If simple notification sounds are enabled, a short sound is played as well. Merely arming a reminder does not start the blinking indication.
|
||||
|
||||
Creating a new set of reminders for the same complete callsign replaces the previously scheduled reminders for that callsign.
|
||||
|
||||
### Storage and limitations
|
||||
|
||||
Skeds and reminder schedules are kept in memory only. Any skeds which are still required must be recreated after restarting KST4Contest.
|
||||
|
||||
The automatic band selection is derived from available chat information. It cannot prove that the station is still operating on the most recently mentioned QRG. Check the band, time and mode before pressing **Create sked**.
|
||||
|
||||
Operation: [Station Info Panel](en-User-Interface#station-info-panel-further-info)
|
||||
|
||||
Display: [AP and Sked Timeline](#ap-and-sked-timeline)
|
||||
|
||||
Win-Test handover: [Log Synchronisation – Win-Test](en-Log-Sync#win-test)
|
||||
|
||||
---
|
||||
|
||||
## QSO Sniffer (from v1.31)
|
||||
|
||||
@@ -233,17 +300,22 @@ Configuration: [Configuration – Sniffer Settings](en-Configuration#sniffer-set
|
||||
|
||||
---
|
||||
|
||||
## Win-Test Integration (from v1.31, fully configurable from v1.40)
|
||||
## Win-Test Integration
|
||||
|
||||
KST4Contest fully supports [Win-Test](https://www.win-test.com/) as a logging programme:
|
||||
KST4Contest uses a dedicated listener for the native Win-Test network protocol. It provides three separate functions:
|
||||
|
||||
- **Log synchronisation**: Worked stations are automatically retrieved from Win-Test and marked in the user list.
|
||||
- **Frequency parsing**: The current TRX frequency is read from Win-Test UDP packets and populates the `MYQRG` variable.
|
||||
- **Sked handover (SKED push via UDP)**: Agreed skeds from KST4Contest can be pushed directly to Win-Test, so the remote callsign appears in Win-Test's sked window.
|
||||
- importing new QSOs including band and, where available, locator information,
|
||||
- reading the current QRG from Win-Test STATUS packets, and
|
||||
- handing internally created skeds over to the Win-Test network as `ADDSKED` packets.
|
||||
|
||||
Details: [Configuration – Win-Test Network Listener](en-Configuration#win-test-network-listener)
|
||||
The sked handover does not replace a missing QRG with a fixed default frequency. KST4Contest only sends a Win-Test sked when it can determine a QRG which belongs to the selected band. The internal sked, timeline and reminder PMs continue to work independently.
|
||||
|
||||
A visible KST suffix such as `-2`, `-70` or `-144` is retained inside KST4Contest but removed from the callsign passed to the Win-Test log. Portable components such as `/P`, `/M` and country prefixes are preserved.
|
||||
|
||||
Setup and data handling: [Log Synchronisation – Win-Test](en-Log-Sync#win-test)
|
||||
|
||||
Settings: [Win-Test Network Listener](en-Configuration#win-test-network-listener-from-v131)
|
||||
|
||||
---
|
||||
|
||||
## PSTRotator Interface (from v1.31, fully configurable from v1.40)
|
||||
|
||||
@@ -379,16 +451,55 @@ Related settings:
|
||||
|
||||
---
|
||||
|
||||
## AP Timeline (from v1.40)
|
||||
## AP and Sked Timeline
|
||||
|
||||
A visual timeline shows up to 4 highly-scored stations per minute slot that should be workable via aircraft scatter. Prioritisation criteria:
|
||||
The timeline combines upcoming aircraft-scatter opportunities and stored skeds for the next 30 minutes. It therefore answers two different questions in the same place:
|
||||
|
||||
- **Highest reflection potential** is preferred (not necessarily the fastest arrival).
|
||||
- Stations towards which your antenna is not pointing are shown **transparently**.
|
||||
- When is an interesting AP opportunity expected?
|
||||
- Which previously agreed sked is approaching independently of that opportunity?
|
||||
|
||||
Events further in the future appear on the right. As time passes, they move left towards the current time.
|
||||
|
||||
|
||||
|
||||
### AP candidates
|
||||
|
||||
AP candidates appear in the upper lanes. Up to four selected candidates can be displayed for each aircraft arrival minute. The selection takes the Priority Score and the reflection potential reported by AirScout into account.
|
||||
|
||||
The colour of an AP marker represents the reflection potential:
|
||||
|
||||
| Colour | Reflection potential |
|
||||
|---|---:|
|
||||
| Magenta | at least 95% |
|
||||
| Red | at least 75% |
|
||||
| Yellow | at least 50% |
|
||||
| Blue | below 50% |
|
||||
|
||||
The colour is not a QSO probability. It represents the AirScout value for the calculated reflection geometry.
|
||||
|
||||
Clicking an AP candidate selects the corresponding active chat member, including its callsign suffix and chat category. A suitable message can then be prepared immediately.
|
||||
|
||||
### Skeds
|
||||
|
||||
Skeds appear as diamonds in the lower lane. Their labels use the complete KST callsign, for example `SKED: DN9APW-2`. This makes it clear which particular login was selected for the scheduled contact.
|
||||
|
||||
A sked tooltip shows at least:
|
||||
|
||||
- the complete KST callsign,
|
||||
- the agreed band, and
|
||||
- the QTF towards the remote station.
|
||||
|
||||
Where suitable AirScout data is available, the tooltip also includes current AP reachability and the next calculated AP opportunity.
|
||||
|
||||
### Antenna direction
|
||||
|
||||
When the QTF of an event is clearly outside the current antenna direction, its marker becomes more transparent. The label remains readable. A target close to the centre of the configured antenna beam is highlighted.
|
||||
|
||||
This visual effect changes neither the sked nor the Priority Score. It is simply a quick way of identifying candidates which fit the current antenna direction.
|
||||
|
||||
The timeline is a preview. AirScout data can change, and a stored sked guarantees neither a clear frequency nor an actual propagation path.
|
||||
|
||||
This gives the contest operator a quick overview of which stations will be reachable via which aircraft and at what time.
|
||||
|
||||
---
|
||||
|
||||
## Interval Beacon
|
||||
|
||||
|
||||
+65
-23
@@ -86,35 +86,77 @@ When broadcasting the complete logbook, DXLog.net uses `contactreplace` instead
|
||||
|
||||
### Win-Test
|
||||
|
||||
Win-Test is supported with a dedicated UDP network listener that understands the native Win-Test network protocol.
|
||||
Win-Test is connected through a dedicated UDP listener for the native Win-Test network protocol. This listener is independent of the general QSO UDP listener on port `12060`.
|
||||
|
||||
For a new QSO, KST4Contest imports the callsign and resolves the native Win-Test band ID. This includes 50 and 70 MHz. If the packet contains a valid locator, the worked grid square is also stored for the detected band.
|
||||
#### QSO and Worked synchronisation
|
||||
|
||||
**Advantages of Win-Test Integration:**
|
||||
- **Per-band Worked data:** New QSOs set the Worked mark for the band reported by Win-Test and update the grid-square status where a locator is available.
|
||||
- Automatic QSO synchronization to mark worked stations.
|
||||
- **Sked Handover (ADDSKED):** Using the "Create sked" button in the station info panel not only creates a sked in KST4Contest but also *sends it directly via UDP to the Win-Test network as an ADDSKED packet* – automatically, as soon as the listener is active. No separate toggle is needed.
|
||||
- You can choose between "AUTO", "SSB", or "CW" sked modes.
|
||||
- **Automatic QRG resolution for SKEDs:** KST4Contest selects the sked frequency intelligently:
|
||||
1. If the other station mentioned their QRG in a recent chat message, that frequency is used.
|
||||
2. Otherwise, your own current QRG is used (from Win-Test STATUS or manual entry).
|
||||
For a new QSO, KST4Contest imports:
|
||||
|
||||
**Settings in the "Log Synchronisation" tab:**
|
||||
- Enable `Receive Win-Test network based UDP log messages`.
|
||||
- `UDP-Port for Win-Test listener` (default: 9871).
|
||||
- `KST station name in Win-Test network (src of SKED packets)`: Defines the station name KST4Contest uses in the WT network (e.g. "KST").
|
||||
- `Win-Test network broadcast address`: Usually detected automatically; required to send sked packets to the network.
|
||||
- the logged callsign,
|
||||
- the native Win-Test band ID, and
|
||||
- a valid locator where one is included in the packet.
|
||||
|
||||
**Settings in the "TRX Synchronisation" tab:**
|
||||
- `Win-Test STATUS QRG Sync`: When enabled, KST4Contest takes the current transceiver frequency from the Win-Test STATUS packet and uses it as your own QRG (MYQRG).
|
||||
- `Use pass frequency from Win-Test STATUS`: 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).
|
||||
- `Win-Test station name filter`: If a name is entered here (e.g. "STN1"), KST4Contest only processes packets from that specific Win-Test instance. Leave empty to accept all.
|
||||
Band IDs for 50 and 70 MHz are processed in the same way as the VHF, UHF and SHF bands. The callsign is marked as worked globally and on the detected band. If a locator is also available, its four-character grid square is stored for that band.
|
||||
|
||||
The information is written to the same internal database as Worked data received through the other QSO UDP interfaces and is restored after a restart.
|
||||
|
||||
#### Handing skeds over to Win-Test
|
||||
|
||||
Pressing **Create sked** first creates an internal KST4Contest sked. If the Win-Test network listener is enabled, KST4Contest then automatically attempts to send the sked to the Win-Test network as an `ADDSKED` packet.
|
||||
|
||||
The QRG is selected in the following order:
|
||||
|
||||
1. KST4Contest looks for the most recent QRG of the remote station on the explicitly selected band. The QRG must be no more than 30 minutes old. Active variants of the same base callsign are evaluated together.
|
||||
2. If no such QRG is available, KST4Contest checks the local QRG of the chat category in which the sked was created. It is only used if it can be parsed and actually belongs to the selected band.
|
||||
3. If neither source provides a matching QRG, no `ADDSKED` packet is sent.
|
||||
|
||||
A fixed replacement frequency such as `144.300` is deliberately not used. During a contest, a technically successful handover containing the wrong band or QRG is worse than a visibly omitted handover.
|
||||
|
||||
The internal sked remains intact in every case. This also applies when the broadcast address is invalid, the network fails or no Win-Test client can be reached.
|
||||
|
||||
#### Handling KST callsign suffixes
|
||||
|
||||
KST suffixes often identify a particular chat login or band. They are not necessarily part of the log callsign. KST4Contest therefore removes a suffix separated by `-` before handing the callsign over to Win-Test, while preserving portable and international callsign components:
|
||||
|
||||
| Callsign in the KST chat | Callsign passed to Win-Test |
|
||||
|---|---|
|
||||
| `DN9APW-2` | `DN9APW` |
|
||||
| `9A0BB-70` | `9A0BB` |
|
||||
| `EA5/G8MBI/P-70` | `EA5/G8MBI/P` |
|
||||
| `DN9APW-2/P` | `DN9APW/P` |
|
||||
|
||||
The complete callsign remains available inside KST4Contest. The timeline, reminder PMs and chat category continue to refer to the login which was actually selected.
|
||||
|
||||
#### Mode, time and notes
|
||||
|
||||
The mode is selected explicitly as `SSB` or `CW` when the sked is created. It is not inferred automatically from the QRG because a limited list of assumed band segments cannot represent every supported VHF, UHF and SHF band reliably.
|
||||
|
||||
KST4Contest sends the actual scheduled time without adding an extra minute. Where available, the notes include the locator and QTF together with an indication that the sked was created through KST4Contest.
|
||||
|
||||
The handover consists of the Win-Test packets `LOCKSKED`, `ADDSKED` and `UNLOCKSKED`.
|
||||
|
||||
|
||||
|
||||
#### Settings
|
||||
|
||||
In the **Log sync** tab:
|
||||
|
||||
- `Receive Win-Test network based UDP log messages`
|
||||
- `UDP-Port for Win-Test listener`, default `9871`
|
||||
- `KST station name in Win-Test network (src of SKED packets)`
|
||||
- `Win-Test network broadcast address`
|
||||
|
||||
In the **TRX sync** tab:
|
||||
|
||||
- `Win-Test STATUS QRG Sync`
|
||||
- `Use pass frequency from Win-Test STATUS`
|
||||
- `Win-Test station name filter`
|
||||
|
||||
The Win-Test network must be enabled in Win-Test. When several computers are used, the broadcast address must reach the relevant local network. The station name should identify the sending KST4Contest instance unambiguously within the Win-Test network.
|
||||
|
||||
Detailed settings: [Win-Test Network Listener](en-Configuration#win-test-network-listener-from-v131)
|
||||
|
||||
**Settings in Win-Test:**
|
||||
- The network in Win-Test must be active.
|
||||
- Win-Test must be configured to send/receive its broadcasts on the corresponding port (default 9871).
|
||||
|
||||
---
|
||||
|
||||
## TRX Frequency Synchronisation
|
||||
|
||||
|
||||
@@ -111,7 +111,24 @@ The current **Priority score** of the selected station is displayed in the same
|
||||
|
||||
**Sked fail** marks an unsuccessful attempt and strongly reduces the score of the normalised base callsign. **Reset fail** removes the mark. It applies to all active suffix and category variants of the station and remains active for the current program session.
|
||||
|
||||
A sked and the corresponding **sked reminders** can be created underneath these controls. An approaching sked raises the Priority Score over time and receives very high priority immediately before the scheduled contact.
|
||||
The controls underneath are used to create a sked:
|
||||
|
||||
| Control | Meaning |
|
||||
|---|---|
|
||||
| **Sked in** | Time remaining until the sked |
|
||||
| **Band** | Agreed band selected from the locally enabled bands |
|
||||
| **Mode** | `SSB` or `CW` for a possible Win-Test handover |
|
||||
| **Create sked** | Create the internal sked |
|
||||
| **Remind-PM in** | Enable automatic reminder PMs |
|
||||
| **2+1**, **5+2+1**, **10+5+2+1** | Times at which reminder PMs are sent before the sked |
|
||||
|
||||
|
||||
|
||||
The proposed band is derived from recent QRG and name information for the station. It can be changed explicitly before creating the sked. The mode selection only affects the Win-Test handover; the internal sked and reminder PMs work independently.
|
||||
|
||||
**Create sked** always creates the appointment inside KST4Contest first. If the Win-Test network listener is active, KST4Contest then attempts an additional handover to Win-Test. If no QRG matching the selected band can be found or Win-Test cannot be reached, the internal sked, its priority contribution and any scheduled reminders remain intact.
|
||||
|
||||
The complete derivation and limitations are described under [Skeds and Sked Reminders](en-Features#skeds-and-sked-reminders).
|
||||
|
||||
---
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
@@ -318,7 +318,6 @@ public class ChatController implements ThreadStatusCallback, PstRotatorEventList
|
||||
}
|
||||
|
||||
|
||||
|
||||
public void stopRotator() {
|
||||
if (rotatorClient != null) {
|
||||
rotatorClient.stop();
|
||||
@@ -773,24 +772,6 @@ public class ChatController implements ThreadStatusCallback, PstRotatorEventList
|
||||
private final Map<String, ChatCategory> lastInboundCategoryByCallSignRaw =
|
||||
new java.util.concurrent.ConcurrentHashMap<>();
|
||||
|
||||
/** Tracks the last time WE sent a message containing a QRG to a specific callsign (UPPERCASE).
|
||||
* Compared against knownActiveBands.timestampEpoch to decide whose QRG to use in a SKED. */
|
||||
private final Map<String, Long> lastSentQRGToCallsign =
|
||||
new java.util.concurrent.ConcurrentHashMap<>();
|
||||
|
||||
/** Call this whenever we send a PM to {@code receiverCallsign} that contains our QRG. */
|
||||
public void recordOutboundQRG(String receiverCallsign) {
|
||||
if (receiverCallsign == null) return;
|
||||
lastSentQRGToCallsign.put(receiverCallsign.trim().toUpperCase(), System.currentTimeMillis());
|
||||
System.out.println("[ChatController] Recorded outbound QRG to: " + receiverCallsign);
|
||||
}
|
||||
|
||||
/** Returns epoch-ms of when we last sent our QRG to this callsign, or 0 if never. */
|
||||
public long getLastSentQRGTimestamp(String callsign) {
|
||||
if (callsign == null) return 0L;
|
||||
return lastSentQRGToCallsign.getOrDefault(callsign.trim().toUpperCase(), 0L);
|
||||
}
|
||||
|
||||
private final ScoreService scoreService = new ScoreService(this, new PriorityCalculator(), 15);
|
||||
private ScheduledExecutorService scoreScheduler;
|
||||
private final StationMetricsService stationMetricsService = new StationMetricsService();
|
||||
@@ -814,158 +795,420 @@ public class ChatController implements ThreadStatusCallback, PstRotatorEventList
|
||||
}
|
||||
|
||||
/**
|
||||
* Pushes a sked to Win-Test via UDP broadcast (LOCKSKED / ADDSKED / UNLOCKSKED).
|
||||
* Runs on a background thread to avoid blocking the UI.
|
||||
* Pushes a sked to Win-Test via UDP broadcast.
|
||||
*
|
||||
* <p>The internal sked is independent from this handover. If no frequency can
|
||||
* be resolved safely for the selected band, the internal sked remains active,
|
||||
* but no misleading Win-Test entry is created.</p>
|
||||
*/
|
||||
private void pushSkedToWinTest(ContestSked sked) {
|
||||
new Thread(() -> {
|
||||
try {
|
||||
InetAddress broadcastAddr = InetAddress.getByName(
|
||||
chatPreferences.getLogsynch_wintestNetworkBroadcastAddress());
|
||||
int port = chatPreferences.getLogsynch_wintestNetworkPort();
|
||||
String stationName = chatPreferences.getLogsynch_wintestNetworkStationNameOfKST();
|
||||
Double frequencyKHz = resolveSkedFrequencyKHz(sked);
|
||||
|
||||
WinTestSkedSender sender = new WinTestSkedSender(stationName, broadcastAddr, port, this);
|
||||
|
||||
// Frequency resolution:
|
||||
// Compare WHO sent a QRG most recently in the PM conversation:
|
||||
// - OM sent their QRG last → use OM's Last Known QRG (ChatMember.frequency)
|
||||
// - WE sent our QRG last → use our own Win-Test QRG (MYQRG)
|
||||
// Fallback chain if no timestamps exist: OM's Last Known QRG → hardcoded default
|
||||
double freqKHz = -1.0;
|
||||
final long SKED_FREQ_MAX_AGE_MS = 60 * 60 * 1000L; // 60 minutes
|
||||
|
||||
ChatMember targetMember = resolveSkedTargetMember(sked.getTargetCallsign());
|
||||
|
||||
// Collect timestamps: when did the OM last mention their QRG? When did WE last send ours?
|
||||
long omLastQRGTimestamp = 0L;
|
||||
double omLastQRGMhz = 0.0;
|
||||
if (targetMember != null && sked.getBand() != null) {
|
||||
ChatMember.ActiveFrequencyInfo fi = targetMember.getKnownActiveBands().get(sked.getBand());
|
||||
if (fi != null && fi.frequency > 0
|
||||
&& (System.currentTimeMillis() - fi.timestampEpoch) <= SKED_FREQ_MAX_AGE_MS) {
|
||||
omLastQRGTimestamp = fi.timestampEpoch;
|
||||
omLastQRGMhz = fi.frequency;
|
||||
}
|
||||
}
|
||||
long ourLastQRGTimestamp = getLastSentQRGTimestamp(sked.getTargetCallsign());
|
||||
|
||||
// Decision: who was more recent?
|
||||
if (omLastQRGTimestamp > 0 && omLastQRGTimestamp >= ourLastQRGTimestamp) {
|
||||
// OM mentioned their QRG MORE RECENTLY (or at same time) → use their QRG
|
||||
freqKHz = omLastQRGMhz * 1000.0;
|
||||
System.out.println("[ChatController] SKED freq: OM sent last → "
|
||||
+ omLastQRGMhz + " MHz → " + freqKHz + " kHz");
|
||||
|
||||
} else if (ourLastQRGTimestamp > 0) {
|
||||
// WE sent our QRG more recently → use our Win-Test QRG
|
||||
try {
|
||||
String qrgStr = chatPreferences.getMYQRGFirstCat().get();
|
||||
if (qrgStr != null && !qrgStr.isBlank()) {
|
||||
String cleaned = qrgStr.trim().replace(".", "");
|
||||
double parsed = Double.parseDouble(cleaned) / 100.0;
|
||||
if (parsed > 50000) {
|
||||
freqKHz = parsed;
|
||||
System.out.println("[ChatController] SKED freq: WE sent last → "
|
||||
+ freqKHz + " kHz (raw: " + qrgStr + ")");
|
||||
}
|
||||
}
|
||||
} catch (NumberFormatException ignored) { }
|
||||
if (frequencyKHz == null) {
|
||||
reportSkippedWinTestSked(
|
||||
sked,
|
||||
"no recent or configured QRG matches "
|
||||
+ sked.getBand().getDisplayLabel()
|
||||
);
|
||||
return;
|
||||
}
|
||||
|
||||
// Fallback A: OM's Last Known QRG from KST field (if no PM QRG exchange found at all)
|
||||
if (freqKHz < 0 && targetMember != null) {
|
||||
try {
|
||||
String memberQrg = targetMember.getFrequency().get();
|
||||
if (memberQrg != null && !memberQrg.isBlank()) {
|
||||
double mhz = Double.parseDouble(memberQrg.trim());
|
||||
freqKHz = mhz * 1000.0;
|
||||
System.out.println("[ChatController] SKED freq: fallback Last Known QRG → "
|
||||
+ mhz + " MHz → " + freqKHz + " kHz");
|
||||
}
|
||||
} catch (NumberFormatException ignored) { }
|
||||
String winTestCallsign =
|
||||
toWinTestSkedCallsign(
|
||||
sked.getTargetChatCallsign()
|
||||
);
|
||||
|
||||
if (winTestCallsign == null || winTestCallsign.isBlank()) {
|
||||
reportSkippedWinTestSked(
|
||||
sked,
|
||||
"the target callsign could not be converted"
|
||||
);
|
||||
return;
|
||||
}
|
||||
|
||||
// Fallback B: hardcoded default
|
||||
if (freqKHz < 0) {
|
||||
freqKHz = 144300.0;
|
||||
}
|
||||
InetAddress broadcastAddress = InetAddress.getByName(
|
||||
chatPreferences
|
||||
.getLogsynch_wintestNetworkBroadcastAddress()
|
||||
);
|
||||
|
||||
int port =
|
||||
chatPreferences.getLogsynch_wintestNetworkPort();
|
||||
|
||||
String stationName =
|
||||
chatPreferences
|
||||
.getLogsynch_wintestNetworkStationNameOfKST();
|
||||
|
||||
WinTestSkedSender sender = new WinTestSkedSender(
|
||||
stationName,
|
||||
broadcastAddress,
|
||||
port,
|
||||
this
|
||||
);
|
||||
|
||||
String targetLocator =
|
||||
resolveSkedTargetLocator(
|
||||
sked.getTargetCallsign()
|
||||
);
|
||||
|
||||
// Build notes string with target locator/azimuth info like reference: [JO02OB - 279°]
|
||||
String targetLocator = resolveSkedTargetLocator(sked.getTargetCallsign());
|
||||
String notes = "sked via KST4Contest";
|
||||
if (targetLocator != null && !targetLocator.isBlank() && sked.getTargetAzimuth() > 0) {
|
||||
notes = String.format("[%s - %.0f°] %s", targetLocator, sked.getTargetAzimuth(), notes);
|
||||
} else if (targetLocator != null && !targetLocator.isBlank()) {
|
||||
notes = String.format("[%s] %s", targetLocator, notes);
|
||||
|
||||
if (targetLocator != null
|
||||
&& !targetLocator.isBlank()
|
||||
&& sked.getTargetAzimuth() > 0) {
|
||||
|
||||
notes = String.format(
|
||||
"[%s - %.0f°] %s",
|
||||
targetLocator,
|
||||
sked.getTargetAzimuth(),
|
||||
notes
|
||||
);
|
||||
|
||||
} else if (targetLocator != null
|
||||
&& !targetLocator.isBlank()) {
|
||||
|
||||
notes = String.format(
|
||||
"[%s] %s",
|
||||
targetLocator,
|
||||
notes
|
||||
);
|
||||
|
||||
} else if (sked.getTargetAzimuth() > 0) {
|
||||
notes = String.format("[%.0f°] %s", sked.getTargetAzimuth(), notes);
|
||||
|
||||
notes = String.format(
|
||||
"[%.0f°] %s",
|
||||
sked.getTargetAzimuth(),
|
||||
notes
|
||||
);
|
||||
}
|
||||
|
||||
// Determine mode: -1 = auto-detect, 0 = CW, 1 = SSB
|
||||
String modeStr = chatPreferences.getLogsynch_wintestSkedMode();
|
||||
int modeOverride = -1; // AUTO
|
||||
if ("CW".equalsIgnoreCase(modeStr)) modeOverride = 0;
|
||||
else if ("SSB".equalsIgnoreCase(modeStr)) modeOverride = 1;
|
||||
String configuredMode =
|
||||
chatPreferences.getLogsynch_wintestSkedMode();
|
||||
|
||||
sender.pushSkedToWinTest(sked, freqKHz, notes, modeOverride);
|
||||
} catch (Exception e) {
|
||||
System.out.println("[ChatController] Error pushing sked to Win-Test: " + e.getMessage());
|
||||
e.printStackTrace();
|
||||
/*
|
||||
* Win-Test mode IDs:
|
||||
* 0 = CW
|
||||
* 1 = SSB
|
||||
*
|
||||
* SSB is the safe fallback for missing or obsolete settings.
|
||||
* The former AUTO mode was frequency-based and could not produce
|
||||
* reliable results on every supported VHF, UHF and SHF band.
|
||||
*/
|
||||
int winTestMode =
|
||||
"CW".equalsIgnoreCase(configuredMode)
|
||||
? 0
|
||||
: 1;
|
||||
|
||||
sender.pushSkedToWinTest(
|
||||
sked,
|
||||
winTestCallsign,
|
||||
frequencyKHz,
|
||||
notes,
|
||||
winTestMode
|
||||
);
|
||||
|
||||
} catch (Exception exception) {
|
||||
String message =
|
||||
"Error pushing sked to Win-Test: "
|
||||
+ exception.getMessage();
|
||||
|
||||
System.out.println(
|
||||
"[ChatController] " + message
|
||||
);
|
||||
|
||||
onThreadStatus(
|
||||
"WT-SkedSend",
|
||||
new ThreadStateMessage(
|
||||
"WT-SkedSend",
|
||||
false,
|
||||
message,
|
||||
true
|
||||
)
|
||||
);
|
||||
|
||||
exception.printStackTrace();
|
||||
}
|
||||
}, "WinTestSkedPush").start();
|
||||
}
|
||||
|
||||
private ChatMember resolveSkedTargetMember(String targetCallsignRaw) {
|
||||
if (targetCallsignRaw == null || targetCallsignRaw.isBlank()) {
|
||||
/**
|
||||
* Resolves the frequency used for the Win-Test sked.
|
||||
*
|
||||
* <ol>
|
||||
* <li>Newest QRG detected for the target station on the selected band</li>
|
||||
* <li>Own QRG belonging to the target's chat category</li>
|
||||
* <li>No result: do not send the Win-Test sked</li>
|
||||
* </ol>
|
||||
*/
|
||||
private Double resolveSkedFrequencyKHz(ContestSked sked) {
|
||||
if (sked == null || sked.getBand() == null) {
|
||||
return null;
|
||||
}
|
||||
|
||||
List<ChatMember> matchingMembers = findActiveChatMembersByRawCall(targetCallsignRaw);
|
||||
return matchingMembers.isEmpty() ? null : matchingMembers.get(0);
|
||||
}
|
||||
Double targetFrequencyKHz =
|
||||
resolveRecentTargetFrequencyKHz(sked);
|
||||
|
||||
private String resolveSkedTargetLocator(String targetCallsignRaw) {
|
||||
if (targetCallsignRaw == null || targetCallsignRaw.isBlank()) {
|
||||
return null;
|
||||
if (targetFrequencyKHz != null) {
|
||||
System.out.println(
|
||||
"[ChatController] SKED frequency from target: "
|
||||
+ targetFrequencyKHz
|
||||
+ " kHz on "
|
||||
+ sked.getBand()
|
||||
);
|
||||
return targetFrequencyKHz;
|
||||
}
|
||||
|
||||
for (ChatMember member : findActiveChatMembersByRawCall(targetCallsignRaw)) {
|
||||
String locator = member.getQra();
|
||||
if (locator != null && !locator.isBlank()) {
|
||||
return locator.trim().toUpperCase(Locale.ROOT);
|
||||
}
|
||||
String ownQrg =
|
||||
resolveOwnQrgForSkedCategory(
|
||||
sked.getTargetChatCategory()
|
||||
);
|
||||
|
||||
Double ownFrequencyKHz =
|
||||
parseSkedFrequencyKHz(
|
||||
ownQrg,
|
||||
sked.getBand()
|
||||
);
|
||||
|
||||
if (ownFrequencyKHz != null) {
|
||||
System.out.println(
|
||||
"[ChatController] SKED frequency from own category QRG: "
|
||||
+ ownFrequencyKHz
|
||||
+ " kHz on "
|
||||
+ sked.getBand()
|
||||
);
|
||||
return ownFrequencyKHz;
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
// private ChatMember resolveSkedTargetMember(String targetCallsignRaw) {
|
||||
// if (targetCallsignRaw == null || targetCallsignRaw.isBlank()) {
|
||||
// return null;
|
||||
// }
|
||||
//
|
||||
// List<ChatMember> matchingMembers = findActiveChatMembersByRawCall(targetCallsignRaw);
|
||||
// return matchingMembers.isEmpty() ? null : matchingMembers.get(0);
|
||||
//
|
||||
// }
|
||||
//
|
||||
// private String resolveSkedTargetLocator(String targetCallsignRaw) {
|
||||
// if (targetCallsignRaw == null || targetCallsignRaw.isBlank()) {
|
||||
// return null;
|
||||
// }
|
||||
//
|
||||
// String normalizedTargetCall = normalizeCallRaw(targetCallsignRaw);
|
||||
//
|
||||
// for (ChatMember member : findActiveChatMembersByRawCall(targetCallsignRaw)) {
|
||||
// String locator = member.getQra();
|
||||
// if (locator != null && !locator.isBlank()) {
|
||||
// return locator.trim().toUpperCase(Locale.ROOT);
|
||||
// }
|
||||
// }
|
||||
//
|
||||
// return null;
|
||||
// }
|
||||
/**
|
||||
* Returns the newest QRG detected on the selected band across all active
|
||||
* suffix and category variants of the base callsign.
|
||||
*/
|
||||
private Double resolveRecentTargetFrequencyKHz(ContestSked sked) {
|
||||
List<ChatMember> variants =
|
||||
findActiveChatMembersByRawCall(
|
||||
sked.getTargetCallsign()
|
||||
);
|
||||
|
||||
long now = System.currentTimeMillis();
|
||||
long newestTimestamp = Long.MIN_VALUE;
|
||||
Double newestFrequencyKHz = null;
|
||||
|
||||
for (ChatMember member : variants) {
|
||||
if (member == null || member.getKnownActiveBands() == null) {
|
||||
continue;
|
||||
}
|
||||
|
||||
ChatMember.ActiveFrequencyInfo frequencyInfo =
|
||||
member.getKnownActiveBands().get(
|
||||
sked.getBand()
|
||||
);
|
||||
|
||||
if (frequencyInfo == null
|
||||
|| frequencyInfo.frequency <= 0.0
|
||||
|| !sked.getBand().isPlausible(
|
||||
frequencyInfo.frequency
|
||||
)) {
|
||||
continue;
|
||||
}
|
||||
|
||||
long ageMs = now - frequencyInfo.timestampEpoch;
|
||||
|
||||
if (ageMs < 0L
|
||||
|| ageMs > BandOpportunityResolver
|
||||
.RECENT_DYNAMIC_EVIDENCE_MAX_AGE_MS) {
|
||||
continue;
|
||||
}
|
||||
|
||||
if (frequencyInfo.timestampEpoch > newestTimestamp) {
|
||||
newestTimestamp = frequencyInfo.timestampEpoch;
|
||||
newestFrequencyKHz =
|
||||
frequencyInfo.frequency * 1000.0;
|
||||
}
|
||||
}
|
||||
|
||||
return newestFrequencyKHz;
|
||||
}
|
||||
|
||||
/**
|
||||
* Returns the own QRG belonging to the chat category in which the target
|
||||
* station was selected.
|
||||
*/
|
||||
private String resolveOwnQrgForSkedCategory(
|
||||
ChatCategory targetCategory) {
|
||||
|
||||
if (sameChatCategory(
|
||||
targetCategory,
|
||||
getChatCategorySecondChat())) {
|
||||
|
||||
return chatPreferences
|
||||
.getMYQRGSecondCat()
|
||||
.get();
|
||||
}
|
||||
|
||||
return chatPreferences
|
||||
.getMYQRGFirstCat()
|
||||
.get();
|
||||
}
|
||||
|
||||
private boolean sameChatCategory(ChatCategory first,
|
||||
ChatCategory second) {
|
||||
|
||||
return first != null
|
||||
&& second != null
|
||||
&& first.getCategoryNumber()
|
||||
== second.getCategoryNumber();
|
||||
}
|
||||
|
||||
/**
|
||||
* Parses the QRG formats used by KST4Contest and Win-Test.
|
||||
*
|
||||
* <p>Examples: 144.300, 144.300.03, 144300 and 144300.0.</p>
|
||||
*/
|
||||
private Double parseSkedFrequencyKHz(String value,
|
||||
Band expectedBand) {
|
||||
|
||||
if (value == null
|
||||
|| value.isBlank()
|
||||
|| expectedBand == null) {
|
||||
return null;
|
||||
}
|
||||
|
||||
String normalized = value
|
||||
.trim()
|
||||
.replace(',', '.')
|
||||
.replaceAll("\\s+", "");
|
||||
|
||||
try {
|
||||
java.util.regex.Matcher groupedFrequency =
|
||||
java.util.regex.Pattern.compile(
|
||||
"^(\\d{2,5})\\.(\\d{3})(?:\\.(\\d{1,2}))?$"
|
||||
).matcher(normalized);
|
||||
|
||||
if (groupedFrequency.matches()) {
|
||||
double frequencyKHz =
|
||||
Integer.parseInt(groupedFrequency.group(1))
|
||||
* 1000.0
|
||||
+ Integer.parseInt(
|
||||
groupedFrequency.group(2)
|
||||
);
|
||||
|
||||
String subKHzPart =
|
||||
groupedFrequency.group(3);
|
||||
|
||||
if (subKHzPart != null) {
|
||||
double subKHz =
|
||||
Integer.parseInt(subKHzPart);
|
||||
|
||||
frequencyKHz +=
|
||||
subKHzPart.length() == 1
|
||||
? subKHz / 10.0
|
||||
: subKHz / 100.0;
|
||||
}
|
||||
|
||||
return expectedBand.isPlausible(
|
||||
frequencyKHz / 1000.0
|
||||
) ? frequencyKHz : null;
|
||||
}
|
||||
|
||||
double numericValue =
|
||||
Double.parseDouble(normalized);
|
||||
|
||||
if (expectedBand.isPlausible(numericValue)) {
|
||||
return numericValue * 1000.0;
|
||||
}
|
||||
|
||||
if (expectedBand.isPlausible(
|
||||
numericValue / 1000.0)) {
|
||||
return numericValue;
|
||||
}
|
||||
|
||||
} catch (NumberFormatException ignored) {
|
||||
// Invalid or unsupported QRG format.
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
/**
|
||||
* Removes KST dash suffixes while retaining ordinary amateur-radio slash
|
||||
* notation such as /P, /M or a country prefix.
|
||||
*
|
||||
* <p>Examples:
|
||||
* DN9APW-2 -> DN9APW
|
||||
* EA5/G8MBI/P-70 -> EA5/G8MBI/P
|
||||
* DN9APW-2/P -> DN9APW/P</p>
|
||||
*/
|
||||
private String toWinTestSkedCallsign(String chatCallsign) {
|
||||
if (chatCallsign == null || chatCallsign.isBlank()) {
|
||||
return null;
|
||||
}
|
||||
|
||||
String normalized =
|
||||
chatCallsign.trim().toUpperCase(Locale.ROOT);
|
||||
|
||||
return normalized.replaceAll(
|
||||
"-[^/]*(?=/|$)",
|
||||
""
|
||||
);
|
||||
}
|
||||
|
||||
private void reportSkippedWinTestSked(ContestSked sked,
|
||||
String reason) {
|
||||
|
||||
String target =
|
||||
sked == null
|
||||
? "unknown station"
|
||||
: sked.getTargetChatCallsign();
|
||||
|
||||
String message =
|
||||
"Win-Test sked not sent for "
|
||||
+ target
|
||||
+ ": "
|
||||
+ reason
|
||||
+ ". The internal KST4Contest sked remains active.";
|
||||
|
||||
System.out.println(
|
||||
"[ChatController] " + message
|
||||
);
|
||||
|
||||
onThreadStatus(
|
||||
"WT-SkedSend",
|
||||
new ThreadStateMessage(
|
||||
"WT-SkedSend",
|
||||
false,
|
||||
message,
|
||||
true
|
||||
)
|
||||
);
|
||||
}
|
||||
|
||||
private String resolveSkedTargetLocator(
|
||||
String targetCallsignRaw) {
|
||||
|
||||
if (targetCallsignRaw == null
|
||||
|| targetCallsignRaw.isBlank()) {
|
||||
return null;
|
||||
}
|
||||
|
||||
for (ChatMember member
|
||||
: findActiveChatMembersByRawCall(
|
||||
targetCallsignRaw)) {
|
||||
|
||||
String locator = member.getQra();
|
||||
|
||||
if (locator != null && !locator.isBlank()) {
|
||||
return locator
|
||||
.trim()
|
||||
.toUpperCase(Locale.ROOT);
|
||||
}
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
public StationMetricsService getStationMetricsService() {
|
||||
return stationMetricsService;
|
||||
|
||||
@@ -1373,9 +1373,12 @@ public class MessageBusManagementThread extends Thread {
|
||||
newDXCListSender3.setQra(splittedMessageLine[5]);
|
||||
|
||||
ChatMember newDXCListReceiver3 = new ChatMember();
|
||||
// newDXCListReceiver3.setFrequency(splittedMessageLine[4]);
|
||||
newDXCListReceiver3.setCallSign(splittedMessageLine[4]);
|
||||
newDXCListReceiver3.setQra(splittedMessageLine[5]);
|
||||
/*
|
||||
* MA format:
|
||||
* MA|0|epoch|sender|receiver|sender locator|receiver locator|
|
||||
*/
|
||||
newDXCListReceiver3.setQra(splittedMessageLine[6]);
|
||||
|
||||
dxcMsg3.setSender(newDXCListSender3);
|
||||
dxcMsg3.setReceiver(newDXCListReceiver3);
|
||||
|
||||
@@ -39,26 +39,63 @@ public class WinTestSkedSender {
|
||||
}
|
||||
|
||||
/**
|
||||
* Pushes a ContestSked into Win-Test by sending the LOCKSKED / ADDSKED / UNLOCKSKED
|
||||
* sequence via UDP broadcast.
|
||||
* Pushes a ContestSked into Win-Test by sending the
|
||||
* LOCKSKED / ADDSKED / UNLOCKSKED sequence.
|
||||
*
|
||||
* @param sked the sked to push
|
||||
* @param frequencyKHz current operating frequency in kHz (e.g. 144321.0)
|
||||
* @param notes free-text notes (e.g. "[JO62QM - 123°] sked via KST")
|
||||
* @param sked sked to push
|
||||
* @param targetCallsign callsign prepared for Win-Test
|
||||
* @param frequencyKHz operating frequency in kHz
|
||||
* @param notes optional notes
|
||||
* @param mode Win-Test mode ID: 0 for CW, 1 for SSB
|
||||
*/
|
||||
public void pushSkedToWinTest(ContestSked sked, double frequencyKHz, String notes, int modeOverride) {
|
||||
public void pushSkedToWinTest(ContestSked sked,
|
||||
String targetCallsign,
|
||||
double frequencyKHz,
|
||||
String notes,
|
||||
int mode) {
|
||||
|
||||
try {
|
||||
sendLockSked();
|
||||
sendAddSked(sked, frequencyKHz, notes, modeOverride);
|
||||
|
||||
sendAddSked(
|
||||
sked,
|
||||
targetCallsign,
|
||||
frequencyKHz,
|
||||
notes,
|
||||
mode
|
||||
);
|
||||
|
||||
sendUnlockSked();
|
||||
|
||||
reportStatus("Sked pushed to WT: " + sked.getTargetCallsign(), false);
|
||||
System.out.println("[WinTestSkedSender] Sked pushed: " + sked.getTargetCallsign()
|
||||
+ " at " + frequencyKHz + " kHz, band=" + sked.getBand());
|
||||
} catch (Exception e) {
|
||||
reportStatus("ERROR pushing sked: " + e.getMessage(), true);
|
||||
System.out.println("[WinTestSkedSender] Error pushing sked: " + e.getMessage());
|
||||
e.printStackTrace();
|
||||
reportStatus(
|
||||
"Sked pushed to WT: " + targetCallsign,
|
||||
false
|
||||
);
|
||||
|
||||
System.out.println(
|
||||
"[WinTestSkedSender] Sked pushed: "
|
||||
+ targetCallsign
|
||||
+ " at "
|
||||
+ frequencyKHz
|
||||
+ " kHz, band="
|
||||
+ sked.getBand()
|
||||
+ ", mode="
|
||||
+ mode
|
||||
);
|
||||
|
||||
} catch (Exception exception) {
|
||||
reportStatus(
|
||||
"ERROR pushing sked: "
|
||||
+ exception.getMessage(),
|
||||
true
|
||||
);
|
||||
|
||||
System.out.println(
|
||||
"[WinTestSkedSender] Error pushing sked: "
|
||||
+ exception.getMessage()
|
||||
);
|
||||
|
||||
exception.printStackTrace();
|
||||
}
|
||||
}
|
||||
|
||||
@@ -86,46 +123,53 @@ public class WinTestSkedSender {
|
||||
|
||||
/**
|
||||
* Sends an ADDSKED message with the sked details.
|
||||
* <p>
|
||||
* Win-Test ADDSKED data format (from wtKST):
|
||||
* <pre>
|
||||
* {epoch_seconds} {freq_in_0.1kHz} {bandId} {mode} "{callsign}" "{notes}"
|
||||
* </pre>
|
||||
* <p>
|
||||
* Win-Test uses a timestamp reference of 1970-01-01 00:01:00 UTC (60s offset from Unix epoch).
|
||||
* The C# code adds 60 seconds to compensate.
|
||||
*
|
||||
* <p>The wtKST implementation subtracts a reference time of
|
||||
* 1970-01-01 00:01:00 UTC and subsequently adds 60 seconds. Both
|
||||
* operations cancel each other out. The transmitted value is therefore
|
||||
* an ordinary Unix timestamp and must not receive another offset here.</p>
|
||||
*/
|
||||
private void sendAddSked(ContestSked sked, double frequencyKHz, String notes, int modeOverride) throws Exception {
|
||||
// Win-Test timestamp: epoch seconds with 60s offset
|
||||
long epochSeconds = sked.getSkedTimeEpoch() / 1000;
|
||||
long wtTimestamp = epochSeconds + 60;
|
||||
private void sendAddSked(ContestSked sked,
|
||||
String targetCallsign,
|
||||
double frequencyKHz,
|
||||
String notes,
|
||||
int mode) throws Exception {
|
||||
|
||||
// Frequency in 0.1 kHz units (Win-Test convention): multiply kHz by 10
|
||||
long freqTenthKHz = Math.round(frequencyKHz * 10.0);
|
||||
long wtTimestamp =
|
||||
sked.getSkedTimeEpoch() / 1000L;
|
||||
|
||||
// Win-Test band ID
|
||||
int bandId = toWinTestBandId(sked.getBand());
|
||||
// Frequency in 0.1 kHz units.
|
||||
long frequencyTenthKHz =
|
||||
Math.round(frequencyKHz * 10.0);
|
||||
|
||||
// Mode: -1 = auto-detect from frequency, 0 = CW, 1 = SSB
|
||||
int mode;
|
||||
if (modeOverride >= 0) {
|
||||
mode = modeOverride;
|
||||
} else {
|
||||
mode = isInSsbSegment(frequencyKHz) ? 1 : 0;
|
||||
}
|
||||
int bandId =
|
||||
toWinTestBandId(sked.getBand());
|
||||
|
||||
String data = wtTimestamp
|
||||
+ " " + freqTenthKHz
|
||||
+ " " + bandId
|
||||
+ " " + mode
|
||||
+ " \"" + sked.getTargetCallsign() + "\""
|
||||
+ " \"" + (notes != null ? notes : "") + "\"";
|
||||
/*
|
||||
* Accept only the mode IDs supported by this UI.
|
||||
* Any unexpected value falls back to SSB.
|
||||
*/
|
||||
int winTestMode =
|
||||
mode == 0
|
||||
? 0
|
||||
: 1;
|
||||
|
||||
WinTestMessage msg = new WinTestMessage(
|
||||
String data =
|
||||
wtTimestamp
|
||||
+ " " + frequencyTenthKHz
|
||||
+ " " + bandId
|
||||
+ " " + winTestMode
|
||||
+ " \"" + targetCallsign + "\""
|
||||
+ " \"" + (notes != null ? notes : "") + "\"";
|
||||
|
||||
WinTestMessage message = new WinTestMessage(
|
||||
WinTestMessage.MessageType.ADDSKED,
|
||||
stationName, "",
|
||||
data);
|
||||
sendUdp(msg);
|
||||
stationName,
|
||||
"",
|
||||
data
|
||||
);
|
||||
|
||||
sendUdp(message);
|
||||
}
|
||||
|
||||
/**
|
||||
@@ -168,18 +212,6 @@ public class WinTestSkedSender {
|
||||
};
|
||||
}
|
||||
|
||||
/**
|
||||
* Very simple SSB segment heuristic.
|
||||
* A more complete implementation would check actual mode from Win-Test STATUS.
|
||||
*/
|
||||
private boolean isInSsbSegment(double frequencyKHz) {
|
||||
// SSB segments (kHz ranges)
|
||||
if (frequencyKHz >= 144300 && frequencyKHz <= 144399) return true; // 2m SSB
|
||||
if (frequencyKHz >= 432200 && frequencyKHz <= 432399) return true; // 70cm SSB
|
||||
if (frequencyKHz >= 1296200 && frequencyKHz <= 1296399) return true; // 23cm SSB
|
||||
return false;
|
||||
}
|
||||
|
||||
private void reportStatus(String text, boolean isError) {
|
||||
if (callback != null) {
|
||||
callback.onThreadStatus(THREAD_NICKNAME,
|
||||
|
||||
@@ -224,7 +224,7 @@ public class ChatPreferences {
|
||||
boolean logsynch_wintestNetworkListenerEnabled = true; // default true = bisheriges Verhalten
|
||||
String logsynch_wintestNetworkBroadcastAddress = "255.255.255.255"; // UDP broadcast address for sending to Win-Test
|
||||
boolean logsynch_wintestNetworkSkedPushEnabled = false; // push SKEDs to Win-Test via UDP
|
||||
String logsynch_wintestSkedMode = "SSB"; // CW, SSB or AUTO
|
||||
String logsynch_wintestSkedMode = "SSB"; // Supported values: SSB or CW
|
||||
boolean logsynch_wintestQrgSyncEnabled = true; // sync QRG from Win-Test STATUS packet
|
||||
boolean logsynch_wintestUsePassQrg = false; // use pass frequency instead of main QRG from STATUS packet
|
||||
|
||||
|
||||
@@ -3,25 +3,58 @@ package kst4contest.model;
|
||||
/**
|
||||
* Represents a scheduled event or an AirScout opportunity in the future.
|
||||
* Used for the Timeline View and Priority Calculation.
|
||||
*
|
||||
* <p>The base callsign remains the grouping key for scoring and worked-state
|
||||
* handling. The exact KST login and its chat category are stored separately
|
||||
* because reminders and external logger handover refer to the selected
|
||||
* ChatMember entity.</p>
|
||||
*/
|
||||
public class ContestSked {
|
||||
|
||||
private String targetCallsign;
|
||||
private double targetAzimuth; // Required for Antenna-Visuals
|
||||
private long skedTimeEpoch; // The peak time (e.g., AP)
|
||||
private String targetChatCallsign;
|
||||
private ChatCategory targetChatCategory;
|
||||
private double targetAzimuth;
|
||||
private long skedTimeEpoch;
|
||||
private Band band;
|
||||
|
||||
// Opportunity potential (0..100). -1 means "unknown".
|
||||
int opportunityPotentialPercent = -1;
|
||||
|
||||
// Status flags to prevent spamming alarms
|
||||
// Status flags to prevent spamming alarms.
|
||||
private boolean warning3MinSent = false;
|
||||
private boolean warningNowSent = false;
|
||||
|
||||
public ContestSked(String call, double azimuth, long time, Band b) {
|
||||
this.targetCallsign = call;
|
||||
/**
|
||||
* Backward-compatible constructor.
|
||||
*/
|
||||
public ContestSked(String call, double azimuth, long time, Band band) {
|
||||
this(call, call, null, azimuth, time, band);
|
||||
}
|
||||
|
||||
/**
|
||||
* Creates a sked for one exact KST login.
|
||||
*
|
||||
* @param callRaw base callsign used for scoring and worked states
|
||||
* @param chatCallsign exact KST login, including an optional dash suffix
|
||||
* @param chatCategory category in which the selected login is active
|
||||
* @param azimuth target azimuth
|
||||
* @param time sked time in epoch milliseconds
|
||||
* @param band selected amateur-radio band
|
||||
*/
|
||||
public ContestSked(String callRaw,
|
||||
String chatCallsign,
|
||||
ChatCategory chatCategory,
|
||||
double azimuth,
|
||||
long time,
|
||||
Band band) {
|
||||
|
||||
this.targetCallsign = callRaw;
|
||||
this.targetChatCallsign = chatCallsign;
|
||||
this.targetChatCategory = chatCategory;
|
||||
this.targetAzimuth = azimuth;
|
||||
this.skedTimeEpoch = time;
|
||||
this.band = b;
|
||||
this.band = band;
|
||||
}
|
||||
|
||||
/**
|
||||
@@ -32,15 +65,54 @@ public class ContestSked {
|
||||
return (skedTimeEpoch - System.currentTimeMillis()) / 1000;
|
||||
}
|
||||
|
||||
// Getters and Setters...
|
||||
public String getTargetCallsign() { return targetCallsign; }
|
||||
public double getTargetAzimuth() { return targetAzimuth; }
|
||||
public long getSkedTimeEpoch() { return skedTimeEpoch; }
|
||||
public Band getBand() { return band; }
|
||||
public boolean isWarning3MinSent() { return warning3MinSent; }
|
||||
public void setWarning3MinSent(boolean b) { this.warning3MinSent = b; }
|
||||
public boolean isWarningNowSent() { return warningNowSent; }
|
||||
public void setWarningNowSent(boolean b) { this.warningNowSent = b; }
|
||||
/**
|
||||
* Returns the base callsign used for scoring and worked-state grouping.
|
||||
*/
|
||||
public String getTargetCallsign() {
|
||||
return targetCallsign;
|
||||
}
|
||||
|
||||
/**
|
||||
* Returns the exact KST login selected when the sked was created.
|
||||
*/
|
||||
public String getTargetChatCallsign() {
|
||||
if (targetChatCallsign == null || targetChatCallsign.isBlank()) {
|
||||
return targetCallsign;
|
||||
}
|
||||
return targetChatCallsign;
|
||||
}
|
||||
|
||||
public ChatCategory getTargetChatCategory() {
|
||||
return targetChatCategory;
|
||||
}
|
||||
|
||||
public double getTargetAzimuth() {
|
||||
return targetAzimuth;
|
||||
}
|
||||
|
||||
public long getSkedTimeEpoch() {
|
||||
return skedTimeEpoch;
|
||||
}
|
||||
|
||||
public Band getBand() {
|
||||
return band;
|
||||
}
|
||||
|
||||
public boolean isWarning3MinSent() {
|
||||
return warning3MinSent;
|
||||
}
|
||||
|
||||
public void setWarning3MinSent(boolean warning3MinSent) {
|
||||
this.warning3MinSent = warning3MinSent;
|
||||
}
|
||||
|
||||
public boolean isWarningNowSent() {
|
||||
return warningNowSent;
|
||||
}
|
||||
|
||||
public void setWarningNowSent(boolean warningNowSent) {
|
||||
this.warningNowSent = warningNowSent;
|
||||
}
|
||||
|
||||
public int getOpportunityPotentialPercent() {
|
||||
return opportunityPotentialPercent;
|
||||
|
||||
@@ -583,6 +583,84 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
};
|
||||
}
|
||||
|
||||
/**
|
||||
* Chooses a useful initial band for a new sked.
|
||||
*
|
||||
* <p>Recent frequency evidence has priority over station-name information.
|
||||
* Manual NOT-QRV exclusions are respected. The operator can still select
|
||||
* another locally enabled band from the dropdown.</p>
|
||||
*/
|
||||
private Band resolveDefaultSkedBand(ChatMember selectedMember,
|
||||
EnumSet<Band> enabledBands) {
|
||||
|
||||
if (selectedMember == null || enabledBands == null || enabledBands.isEmpty()) {
|
||||
return null;
|
||||
}
|
||||
|
||||
List<ChatMember> variants =
|
||||
chatcontroller.findActiveChatMembersByRawCall(
|
||||
selectedMember.getCallSignRaw()
|
||||
);
|
||||
|
||||
if (variants.isEmpty()) {
|
||||
variants = List.of(selectedMember);
|
||||
}
|
||||
|
||||
BandOpportunityResolver.Resolution resolution =
|
||||
BandOpportunityResolver.resolve(
|
||||
variants,
|
||||
System.currentTimeMillis()
|
||||
);
|
||||
|
||||
EnumSet<Band> availableBands = resolution.getAvailableBands();
|
||||
availableBands.retainAll(enabledBands);
|
||||
|
||||
Band newestFrequencyBand = null;
|
||||
long newestTimestamp = Long.MIN_VALUE;
|
||||
long now = System.currentTimeMillis();
|
||||
|
||||
for (ChatMember member : variants) {
|
||||
if (member == null || member.getKnownActiveBands() == null) {
|
||||
continue;
|
||||
}
|
||||
|
||||
for (Map.Entry<Band, ChatMember.ActiveFrequencyInfo> entry
|
||||
: member.getKnownActiveBands().entrySet()) {
|
||||
|
||||
Band band = entry.getKey();
|
||||
ChatMember.ActiveFrequencyInfo info = entry.getValue();
|
||||
|
||||
if (band == null
|
||||
|| info == null
|
||||
|| !availableBands.contains(band)
|
||||
|| !band.isPlausible(info.frequency)) {
|
||||
continue;
|
||||
}
|
||||
|
||||
long ageMs = now - info.timestampEpoch;
|
||||
if (ageMs < 0L
|
||||
|| ageMs > BandOpportunityResolver.RECENT_DYNAMIC_EVIDENCE_MAX_AGE_MS) {
|
||||
continue;
|
||||
}
|
||||
|
||||
if (info.timestampEpoch > newestTimestamp) {
|
||||
newestTimestamp = info.timestampEpoch;
|
||||
newestFrequencyBand = band;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
if (newestFrequencyBand != null) {
|
||||
return newestFrequencyBand;
|
||||
}
|
||||
|
||||
if (!availableBands.isEmpty()) {
|
||||
return availableBands.iterator().next();
|
||||
}
|
||||
|
||||
return enabledBands.iterator().next();
|
||||
}
|
||||
|
||||
|
||||
/**
|
||||
* This method generates a BoderPane which shows some additional information about a callsign which had been
|
||||
@@ -667,56 +745,158 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
|
||||
selectedCallSignDownerSiteGridPane.add(priorityRow, 0, 5, 1, 1);
|
||||
|
||||
ChoiceBox<Integer> cbSkedMinutes = new ChoiceBox<>(FXCollections.observableArrayList(2, 3, 4, 5, 6,7,8,9, 10,11,12,13,14, 15, 20));
|
||||
ChoiceBox<Integer> cbSkedMinutes = new ChoiceBox<>(
|
||||
FXCollections.observableArrayList(
|
||||
2, 3, 4, 5, 6, 7, 8, 9, 10,
|
||||
11, 12, 13, 14, 15, 20
|
||||
)
|
||||
);
|
||||
cbSkedMinutes.getSelectionModel().select(Integer.valueOf(5));
|
||||
|
||||
ChoiceBox<String> cbSkedMode = new ChoiceBox<>(FXCollections.observableArrayList("AUTO", "SSB", "CW"));
|
||||
String configuredSkedMode = this.chatcontroller.getChatPreferences().getLogsynch_wintestSkedMode();
|
||||
if (configuredSkedMode == null || configuredSkedMode.isBlank()) {
|
||||
configuredSkedMode = "AUTO";
|
||||
}
|
||||
String configuredSkedModeUpper = configuredSkedMode.trim().toUpperCase(java.util.Locale.ROOT);
|
||||
if (!"AUTO".equals(configuredSkedModeUpper)
|
||||
&& !"SSB".equals(configuredSkedModeUpper)
|
||||
&& !"CW".equals(configuredSkedModeUpper)) {
|
||||
configuredSkedModeUpper = "AUTO";
|
||||
}
|
||||
cbSkedMode.setValue(configuredSkedModeUpper);
|
||||
cbSkedMode.setTooltip(new Tooltip("Mode for Win-Test ADDSKED packets"));
|
||||
cbSkedMode.setOnAction(e ->
|
||||
chatcontroller.getChatPreferences().setLogsynch_wintestSkedMode(cbSkedMode.getValue()));
|
||||
EnumSet<Band> enabledSkedBands =
|
||||
BandOpportunityResolver.getEnabledStationBands(
|
||||
chatcontroller.getChatPreferences()
|
||||
);
|
||||
|
||||
ChoiceBox<String> cbReminderOffsets = new ChoiceBox<>(FXCollections.observableArrayList("2+1", "5+2+1", "10+5+2+1"));
|
||||
ChoiceBox<Band> cbSkedBand = new ChoiceBox<>(
|
||||
FXCollections.observableArrayList(enabledSkedBands)
|
||||
);
|
||||
|
||||
cbSkedBand.setConverter(new StringConverter<>() {
|
||||
@Override
|
||||
public String toString(Band band) {
|
||||
return band == null ? "" : bandToHumanLabel(band);
|
||||
}
|
||||
|
||||
@Override
|
||||
public Band fromString(String value) {
|
||||
return null;
|
||||
}
|
||||
});
|
||||
|
||||
cbSkedBand.setPrefWidth(75);
|
||||
cbSkedBand.setTooltip(new Tooltip(
|
||||
"Band for this sked. The initial value is derived from recent "
|
||||
+ "QRG information or the station name. Only bands enabled "
|
||||
+ "for your own station are offered."
|
||||
));
|
||||
|
||||
Band defaultSkedBand =
|
||||
resolveDefaultSkedBand(
|
||||
selectedCallSignInfoStageChatMember,
|
||||
enabledSkedBands
|
||||
);
|
||||
|
||||
if (defaultSkedBand != null) {
|
||||
cbSkedBand.setValue(defaultSkedBand);
|
||||
}
|
||||
|
||||
ChoiceBox<String> cbSkedMode = new ChoiceBox<>(
|
||||
FXCollections.observableArrayList("SSB", "CW")
|
||||
);
|
||||
|
||||
String configuredSkedMode =
|
||||
chatcontroller.getChatPreferences()
|
||||
.getLogsynch_wintestSkedMode();
|
||||
|
||||
if (configuredSkedMode == null
|
||||
|| (!"SSB".equalsIgnoreCase(configuredSkedMode)
|
||||
&& !"CW".equalsIgnoreCase(configuredSkedMode))) {
|
||||
|
||||
configuredSkedMode = "SSB";
|
||||
}
|
||||
|
||||
cbSkedMode.setValue(
|
||||
configuredSkedMode.trim().toUpperCase(Locale.ROOT)
|
||||
);
|
||||
|
||||
cbSkedMode.setTooltip(new Tooltip(
|
||||
"Mode transferred to Win-Test with the ADDSKED packet"
|
||||
));
|
||||
|
||||
cbSkedMode.setOnAction(e ->
|
||||
chatcontroller.getChatPreferences()
|
||||
.setLogsynch_wintestSkedMode(
|
||||
cbSkedMode.getValue()
|
||||
)
|
||||
);
|
||||
|
||||
ChoiceBox<String> cbReminderOffsets = new ChoiceBox<>(
|
||||
FXCollections.observableArrayList(
|
||||
"2+1",
|
||||
"5+2+1",
|
||||
"10+5+2+1"
|
||||
)
|
||||
);
|
||||
cbReminderOffsets.getSelectionModel().select("2+1");
|
||||
|
||||
CheckBox chkPmReminders = new CheckBox("Remind-PM in ");
|
||||
|
||||
Button btnCreateSked = new Button("Create sked");
|
||||
btnCreateSked.setTooltip(new Tooltip("Creates a sked entry and boosts priority (ramp-up)."));
|
||||
btnCreateSked.setTooltip(new Tooltip(
|
||||
"Creates a sked entry and boosts priority during the approach."
|
||||
));
|
||||
|
||||
btnCreateSked.setOnAction(e -> {
|
||||
ChatMember sel = chatcontroller.getScoreService().selectedChatMemberProperty().get();
|
||||
if (sel == null) return;
|
||||
ChatMember selectedMember =
|
||||
chatcontroller.getScoreService()
|
||||
.selectedChatMemberProperty()
|
||||
.get();
|
||||
|
||||
if (cbSkedMode.getValue() != null) {
|
||||
chatcontroller.getChatPreferences().setLogsynch_wintestSkedMode(cbSkedMode.getValue());
|
||||
if (selectedMember == null) {
|
||||
return;
|
||||
}
|
||||
|
||||
int minutes = cbSkedMinutes.getValue() == null ? 5 : cbSkedMinutes.getValue();
|
||||
long skedTime = System.currentTimeMillis() + minutes * 60_000L;
|
||||
Band selectedBand = cbSkedBand.getValue();
|
||||
if (selectedBand == null) {
|
||||
showUserInputErrorWindow(
|
||||
"No sked band is available. Enable at least one band "
|
||||
+ "under \"My station uses ...\" before creating a sked."
|
||||
);
|
||||
return;
|
||||
}
|
||||
|
||||
double az = sel.getQTFdirection() != null ? sel.getQTFdirection() : 0.0;
|
||||
if (cbSkedMode.getValue() != null) {
|
||||
chatcontroller.getChatPreferences()
|
||||
.setLogsynch_wintestSkedMode(cbSkedMode.getValue());
|
||||
}
|
||||
|
||||
// band is not strictly required for scoring; keep current category context
|
||||
Band band = Band.B_144; // if you want, replace with a real dropdown later
|
||||
ContestSked sked = new ContestSked(sel.getCallSignRaw(), az, skedTime, band);
|
||||
int minutes =
|
||||
cbSkedMinutes.getValue() == null
|
||||
? 5
|
||||
: cbSkedMinutes.getValue();
|
||||
|
||||
long skedTime =
|
||||
System.currentTimeMillis() + minutes * 60_000L;
|
||||
|
||||
double azimuth =
|
||||
selectedMember.getQTFdirection() != null
|
||||
? selectedMember.getQTFdirection()
|
||||
: 0.0;
|
||||
|
||||
ContestSked sked = new ContestSked(
|
||||
selectedMember.getCallSignRaw(),
|
||||
selectedMember.getCallSign(),
|
||||
selectedMember.getChatCategory(),
|
||||
azimuth,
|
||||
skedTime,
|
||||
selectedBand
|
||||
);
|
||||
|
||||
chatcontroller.addSked(sked);
|
||||
chatcontroller.getScoreService().requestRecompute("sked-created");
|
||||
chatcontroller.getScoreService()
|
||||
.requestRecompute("sked-created");
|
||||
|
||||
if (chkPmReminders.isSelected()) {
|
||||
List<Integer> offsets = parseMinuteOffsets(cbReminderOffsets.getValue());
|
||||
chatcontroller.getSkedReminderService().armReminders(sel.getCallSignRaw(), sel.getChatCategory(), skedTime, offsets);
|
||||
List<Integer> offsets =
|
||||
parseMinuteOffsets(cbReminderOffsets.getValue());
|
||||
|
||||
chatcontroller.getSkedReminderService().armReminders(
|
||||
sked.getTargetChatCallsign(),
|
||||
sked.getTargetChatCategory(),
|
||||
skedTime,
|
||||
offsets
|
||||
);
|
||||
}
|
||||
});
|
||||
|
||||
@@ -728,6 +908,13 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
);
|
||||
skedTimeGroup.setAlignment(Pos.CENTER_LEFT);
|
||||
|
||||
HBox skedBandGroup = new HBox(
|
||||
4,
|
||||
new Label("Band"),
|
||||
cbSkedBand
|
||||
);
|
||||
skedBandGroup.setAlignment(Pos.CENTER_LEFT);
|
||||
|
||||
HBox skedModeGroup = new HBox(
|
||||
4,
|
||||
new Label("Mode"),
|
||||
@@ -750,12 +937,19 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
skedRow.setAlignment(Pos.CENTER_LEFT);
|
||||
skedRow.getChildren().addAll(
|
||||
skedTimeGroup,
|
||||
skedBandGroup,
|
||||
skedModeGroup,
|
||||
btnCreateSked,
|
||||
skedReminderGroup
|
||||
);
|
||||
|
||||
selectedCallSignDownerSiteGridPane.add(skedRow, 0, 6, 2, 1);
|
||||
selectedCallSignDownerSiteGridPane.add(
|
||||
skedRow,
|
||||
0,
|
||||
6,
|
||||
2,
|
||||
1
|
||||
);
|
||||
GridPane.setHgrow(skedRow, Priority.ALWAYS);
|
||||
|
||||
|
||||
@@ -3699,12 +3893,12 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
public ObservableValue<String> call(CellDataFeatures<ClusterMessage, String> cellDataFeatures) {
|
||||
SimpleStringProperty locRX = new SimpleStringProperty();
|
||||
|
||||
if (cellDataFeatures.getValue().getSender() != null) {
|
||||
if (cellDataFeatures.getValue().getReceiver() != null) {
|
||||
|
||||
locRX.setValue(cellDataFeatures.getValue().getReceiver().getQra());
|
||||
} else {
|
||||
|
||||
locRX.setValue("");// TODO: Prevents a bug of not setting all values as a default
|
||||
locRX.setValue("");
|
||||
}
|
||||
return locRX;
|
||||
}
|
||||
@@ -3938,7 +4132,7 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
});
|
||||
|
||||
TableColumn<ChatMessage, String> workedTXCol = new TableColumn<ChatMessage, String>("wkd TX?");
|
||||
workedRXCol.setCellValueFactory(new Callback<CellDataFeatures<ChatMessage, String>, ObservableValue<String>>() {
|
||||
workedTXCol.setCellValueFactory(new Callback<CellDataFeatures<ChatMessage, String>, ObservableValue<String>>() {
|
||||
|
||||
@Override
|
||||
public ObservableValue<String> call(CellDataFeatures<ChatMessage, String> cellDataFeatures) {
|
||||
@@ -5453,23 +5647,7 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
btnSkedWarnIndicator.setTooltip(tipSkedWarnIndicator);
|
||||
}
|
||||
|
||||
private void maybeShowSkedWarnIndicator(String key, ThreadStateMessage msg) {
|
||||
if (msg == null) return;
|
||||
|
||||
String text = msg.getRunningInformationTextDescription();
|
||||
if (text == null || text.isBlank()) text = msg.getRunningInformation();
|
||||
if (text == null || text.isBlank()) return;
|
||||
|
||||
String nick = msg.getThreadNickName() == null ? "" : msg.getThreadNickName().toLowerCase(Locale.ROOT);
|
||||
String k = key == null ? "" : key.toLowerCase(Locale.ROOT);
|
||||
String t = text.toLowerCase(Locale.ROOT);
|
||||
|
||||
boolean isSkedRelated = k.contains("sked") || nick.contains("sked") || t.contains("reminder");
|
||||
if (!isSkedRelated) return;
|
||||
|
||||
final String finalText = text;
|
||||
Platform.runLater(() -> showBlinkingSkedWarnIndicator(finalText + " SKED!"));
|
||||
}
|
||||
|
||||
private void showBlinkingSkedWarnIndicator(String text) {
|
||||
// short text for the button; full text in tooltip
|
||||
@@ -6417,8 +6595,28 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
bPaneChatWindow.setTop(flwpne_StatusBar);
|
||||
|
||||
initSkedWarnIndicatorButton();
|
||||
|
||||
chatcontroller.lastUiReminderEventProperty().addListener(
|
||||
(observable, oldValue, reminderEvent) -> {
|
||||
if (reminderEvent == null) {
|
||||
return;
|
||||
}
|
||||
|
||||
String text = "REMINDER: "
|
||||
+ reminderEvent.getCallSignRaw()
|
||||
+ " T-"
|
||||
+ reminderEvent.getMinutesBefore()
|
||||
+ "m";
|
||||
|
||||
Platform.runLater(
|
||||
() -> showBlinkingSkedWarnIndicator(text)
|
||||
);
|
||||
}
|
||||
);
|
||||
|
||||
flwpne_StatusBar.getChildren().add(btnSkedWarnIndicator);
|
||||
|
||||
|
||||
initBandUpgradeIndicatorButton();
|
||||
flwpne_StatusBar.getChildren().add(btnBandUpgradeIndicator);
|
||||
|
||||
@@ -7233,6 +7431,17 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
// chatMemberTableFilterQTFAndQRBHbox.set
|
||||
|
||||
VBox chatMemberTableFilterVBoxForAllFilters= new VBox();
|
||||
|
||||
Button btnResetChatMemberFilters = new Button("Reset filters");
|
||||
btnResetChatMemberFilters.getStyleClass().clear();
|
||||
btnResetChatMemberFilters.getStyleClass().addAll(
|
||||
"button",
|
||||
"buttonMyQrg1"
|
||||
);
|
||||
btnResetChatMemberFilters.setTooltip(
|
||||
new Tooltip("Disable all station-list filters and show every user")
|
||||
);
|
||||
|
||||
chatMemberTableFilterVBoxForAllFilters.setSpacing(1);
|
||||
|
||||
chatMemberTableFilterVBoxForAllFilters.setMinWidth(0);
|
||||
@@ -7416,20 +7625,12 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
"-fx-border-radius: 1;" +
|
||||
"-fx-border-color: lightgrey;");
|
||||
|
||||
// chatMemberTableFilterQTFAndQRBHbox.setFillHeight(true);
|
||||
// chatMemberTableFilterQTFAndQRBHbox.setAlignment(Pos.CENTER_LEFT);
|
||||
// chatMemberTableFilterQTFAndQRBHbox.getChildren().add(chatMemberTableFilterQRBHBox);
|
||||
chatMemberTableFilterQTFAndQRBHbox
|
||||
.getChildren()
|
||||
.add(chatMemberTableFilterQRBHBox);
|
||||
chatMemberTableFilterQTFAndQRBHbox.getChildren().addAll(
|
||||
btnResetChatMemberFilters,
|
||||
chatMemberTableFilterQRBHBox
|
||||
);
|
||||
|
||||
|
||||
// HBox chatMemberTableFilterQTFHBox = new HBox();
|
||||
// FlowPane chatMemberTableFilterQTFHBox = new FlowPane();
|
||||
// chatMemberTableFilterQTFHBox.setAlignment(Pos.CENTER_LEFT);
|
||||
// chatMemberTableFilterQTFHBox.setPrefWidth(525);
|
||||
// chatMemberTableFilterQTFHBox.setHgap(2);
|
||||
|
||||
FlowPane chatMemberTableFilterQTFHBox = new FlowPane(
|
||||
Orientation.HORIZONTAL,
|
||||
2,
|
||||
@@ -7671,52 +7872,6 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
chatMemberTableFilterTextField.setPromptText("Find...");
|
||||
|
||||
chatMemberTableFilterTextField.setFocusTraversable(false);
|
||||
// chatMemberTableFilterTextField.focusedProperty().addListener(new ChangeListener<Boolean>() {
|
||||
// @Override
|
||||
// public void changed(ObservableValue<? extends Boolean> observableValue, Boolean aBoolean, Boolean t1) {
|
||||
// if (chatMemberTableFilterTextField.focusedProperty().getValue()) {
|
||||
//
|
||||
// chatMemberTableFilterTextField.clear();
|
||||
// } else {
|
||||
// if (!chatMemberTableFilterTextField.focusedProperty().getValue() && chatMemberTableFilterTextField.textProperty().equals("")) {
|
||||
//
|
||||
// chatMemberTableFilterTextField.setText("Find...");
|
||||
// }
|
||||
// }
|
||||
//// System.out.println(chatMemberTableFilterTextField.focusedProperty().getValue());
|
||||
// }
|
||||
// });
|
||||
// chatMemberTableFilterTextField.textProperty().addListener(new ChangeListener<String>() {
|
||||
//
|
||||
// Predicate<ChatMember> searchTextPredicate = new Predicate<ChatMember>() {
|
||||
// @Override
|
||||
// public boolean test(ChatMember chatMember) {
|
||||
// if (chatMember.getCallSign().toUpperCase().contains(chatMemberTableFilterTextField.getText().toUpperCase()) ||
|
||||
// chatMember.getCallSign().toUpperCase().contains(chatMemberTableFilterTextField.getText().toLowerCase())) {
|
||||
// return true;
|
||||
// } else
|
||||
//
|
||||
// return false;
|
||||
// }
|
||||
//
|
||||
// };
|
||||
//
|
||||
// @Override
|
||||
// public void changed(ObservableValue<? extends String> observableValue, String s, String t1) {
|
||||
//
|
||||
// if (chatMemberTableFilterTextField.textProperty().getValue().equals("") && !chatMemberTableFilterTextField.focusedProperty().getValue()) {
|
||||
// chatMemberTableFilterTextField.setText("Find...");
|
||||
// chatcontroller.getLst_chatMemberListFilterPredicates().remove(searchTextPredicate);
|
||||
// }
|
||||
// else {
|
||||
// if (!chatcontroller.getLst_chatMemberListFilterPredicates().contains(searchTextPredicate)) {
|
||||
// chatcontroller.getLst_chatMemberListFilterPredicates().add(searchTextPredicate);
|
||||
// }
|
||||
// }
|
||||
//
|
||||
// System.out.println("KST4CApp " + chatMemberTableFilterTextField.textProperty().getValue().equals("") + " / " + !chatMemberTableFilterTextField.focusedProperty().getValue());
|
||||
// }
|
||||
// });
|
||||
|
||||
chatMemberTableFilterTextField.textProperty().addListener(new ChangeListener<String>() {
|
||||
|
||||
@@ -7757,13 +7912,26 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
}
|
||||
});
|
||||
|
||||
// HBox chatMemberTableFilterWorkedBandFiltersHbx = new HBox();
|
||||
|
||||
FlowPane chatMemberTableFilterWorkedBandFiltersHbx = new FlowPane(
|
||||
Orientation.HORIZONTAL,
|
||||
2,
|
||||
3
|
||||
);
|
||||
|
||||
HBox chatMemberTableReachabilityBox = new HBox(4);
|
||||
chatMemberTableReachabilityBox.setAlignment(Pos.CENTER_LEFT);
|
||||
chatMemberTableReachabilityBox.setMinWidth(0);
|
||||
|
||||
chatMemberTableReachabilityBox.setStyle(
|
||||
"-fx-padding: 1;" +
|
||||
"-fx-border-style: solid inside;" +
|
||||
"-fx-border-width: 1;" +
|
||||
"-fx-border-insets: 1;" +
|
||||
"-fx-border-radius: 1;" +
|
||||
"-fx-border-color: lightgrey;"
|
||||
);
|
||||
|
||||
chatMemberTableFilterWorkedBandFiltersHbx.setAlignment(Pos.CENTER_LEFT);
|
||||
chatMemberTableFilterWorkedBandFiltersHbx.setRowValignment(VPos.CENTER);
|
||||
chatMemberTableFilterWorkedBandFiltersHbx.setMinWidth(0);
|
||||
@@ -7815,9 +7983,11 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
}
|
||||
});
|
||||
|
||||
chatMemberTableFilterWorkedBandFiltersHbx.getChildren().add(new Label("Reachability:"));
|
||||
chatMemberTableFilterWorkedBandFiltersHbx.getChildren().add(cmbReachabilityBand);
|
||||
chatMemberTableFilterWorkedBandFiltersHbx.getChildren().add(btnCalculateSelectedTropo);
|
||||
chatMemberTableReachabilityBox.getChildren().addAll(
|
||||
new Label("Reachability:"),
|
||||
cmbReachabilityBand,
|
||||
btnCalculateSelectedTropo
|
||||
);
|
||||
|
||||
/**
|
||||
* In order to work the filters needs the proper band settings, which should be worked
|
||||
@@ -8159,8 +8329,44 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
btnTglAsNext5Min
|
||||
);
|
||||
|
||||
// chatMemberTableFilterWorkedBandFilters
|
||||
btnResetChatMemberFilters.setOnAction(event -> {
|
||||
|
||||
/*
|
||||
* Reset the visible state of every station-list filter.
|
||||
*
|
||||
* Grid coloring and the selected reachability band are intentionally
|
||||
* preserved because they are display/calculation settings, not filters.
|
||||
*/
|
||||
List.of(
|
||||
btnTglNewLocator,
|
||||
btnTglReachableTropo,
|
||||
btnTglNewBands,
|
||||
btnTglAsNext5Min,
|
||||
tglBtnQRBEnable,
|
||||
btnTglwkd,
|
||||
btnTglwkd50,
|
||||
btnTglwkd70,
|
||||
btnTglwkd144,
|
||||
btnTglwkd432,
|
||||
btnTglwkd23,
|
||||
btnTglwkd13,
|
||||
btnTglwkd9,
|
||||
btnTglwkd6,
|
||||
btnTglwkd3,
|
||||
btnTglInactive
|
||||
).forEach(toggleButton -> toggleButton.setSelected(false));
|
||||
|
||||
tglGrpQTF.selectToggle(null);
|
||||
chatMemberTableFilterQtfEnableChkbx.setSelected(false);
|
||||
chatMemberTableFilterTextField.clear();
|
||||
|
||||
/*
|
||||
* Programmatically changing a ToggleButton does not invoke its action
|
||||
* handler. Clear the predicate list explicitly so no stale predicate
|
||||
* can remain active.
|
||||
*/
|
||||
chatcontroller.getLst_chatMemberListFilterPredicates().clear();
|
||||
});
|
||||
|
||||
chatMemberTableFilterTextFieldBox.getChildren().addAll(chatMemberTableFilterTextField);
|
||||
|
||||
@@ -8176,6 +8382,7 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
|
||||
chatMemberTableFilterTextFieldAndWorkedBandsHbx.getChildren().addAll(
|
||||
chatMemberTableFilterTextFieldBox,
|
||||
chatMemberTableReachabilityBox,
|
||||
chatMemberTableFilterWorkedBandFiltersHbx
|
||||
);
|
||||
|
||||
@@ -11384,13 +11591,7 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
|
||||
settingsStage.show();
|
||||
|
||||
chatcontroller.lastUiReminderEventProperty().addListener((obs, oldVal, ev) -> {
|
||||
if (ev == null) return;
|
||||
|
||||
String text = "REMINDER: " + ev.getCallSignRaw() + " T-" + ev.getMinutesBefore() + "m";
|
||||
Platform.runLater(() -> showBlinkingSkedWarnIndicator(text));
|
||||
|
||||
});
|
||||
|
||||
//initialize the timeline
|
||||
Platform.runLater(this::updateTimelineVisuals);
|
||||
@@ -11651,10 +11852,7 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL
|
||||
updateStatusButton(key, threadStateMessage);
|
||||
});
|
||||
|
||||
maybeShowSkedWarnIndicator(key, threadStateMessage);
|
||||
maybeShowBandUpgradeIndicator(key, threadStateMessage);
|
||||
|
||||
|
||||
//if we receive a threadstatemessage for sked warning, enable the sked warning
|
||||
|
||||
|
||||
|
||||
@@ -208,7 +208,12 @@ public class TimelineView extends Pane {
|
||||
|
||||
diamond.setFill(colorForPotential(sked.getOpportunityPotentialPercent()));
|
||||
|
||||
String baseToolTipFallBack = sked.getTargetCallsign() + " (" + sked.getBand() + ")\nAz: " + sked.getTargetAzimuth();
|
||||
String baseToolTipFallBack =
|
||||
sked.getTargetChatCallsign()
|
||||
+ " ("
|
||||
+ sked.getBand()
|
||||
+ ")\nAz: "
|
||||
+ sked.getTargetAzimuth();
|
||||
|
||||
if (skedTooltipExtraTextProvider != null) {
|
||||
String extra = skedTooltipExtraTextProvider.apply(sked);
|
||||
@@ -220,7 +225,9 @@ public class TimelineView extends Pane {
|
||||
Tooltip t = new Tooltip(baseToolTipFallBack);
|
||||
Tooltip.install(diamond, t);
|
||||
|
||||
Label lbl = new Label("SKED: " + sked.getTargetCallsign());
|
||||
Label lbl = new Label(
|
||||
"SKED: " + sked.getTargetChatCallsign()
|
||||
);
|
||||
// lbl.setFont(new Font(9));
|
||||
// lbl.setTextFill(Color.WHITE);
|
||||
lbl.setLayoutY(14);
|
||||
|
||||
@@ -1,25 +1,59 @@
|
||||
---
|
||||
title: Log Synchronization
|
||||
title: Log Synchronisation
|
||||
icon: 🔄
|
||||
category: Logger Integration
|
||||
since: "1.31"
|
||||
summary: Import worked stations and current frequencies from supported contest loggers so filters and band information follow the log.
|
||||
description: KST4Contest receives worked-station and, where supported, frequency data from UCXLog, N1MM+, QARTest, DXLog.net and Win-Test through file and UDP interfaces.
|
||||
summary: Import callsign, band, locator and QRG information from supported contest loggers at the level provided by each interface.
|
||||
description: KST4Contest connects chat activity with current log state through file-based evaluation, general QSO UDP packets and the native Win-Test network protocol.
|
||||
tagsList:
|
||||
- Win-Test
|
||||
- UCXLog
|
||||
- N1MM+
|
||||
- QARTest
|
||||
- DXLog.net
|
||||
- contest logger
|
||||
related:
|
||||
- priority-score
|
||||
- dual-chat
|
||||
- sked-reminder
|
||||
---
|
||||
|
||||
## Connect chat and logging
|
||||
## Why connect the logger?
|
||||
|
||||
Contest operation is faster when chat information and log state are connected.
|
||||
The chat may still show a station as an interesting candidate after the QSO has already been logged. Without synchronisation, Worked filters, band columns and priority calculations would continue to use an outdated contest state.
|
||||
|
||||
KST4Contest can use logger information to improve workflow awareness.
|
||||
KST4Contest therefore imports the information provided by the logging application and applies it to the active chat entries of the corresponding base callsign.
|
||||
|
||||
## Worked and band awareness
|
||||
## Three interfaces with different levels of detail
|
||||
|
||||
Log synchronization helps the client understand which stations and bands are relevant.
|
||||
The available information depends on the interface:
|
||||
|
||||
| Interface | Callsign | Band | Locator |
|
||||
|---|---:|---:|---:|
|
||||
| Simplelogfile interpreter | yes | no | no |
|
||||
| General QSO UDP listener | yes | when included | when included |
|
||||
| Win-Test network listener | yes | yes | when included |
|
||||
|
||||
The Simplelogfile interpreter is broadly compatible but can only identify worked callsigns. A callsign match in a file does not provide enough information to infer a reliable band or grid square.
|
||||
|
||||
The general UDP listener processes packets from UCXLog, N1MM+, QARTest and DXLog.net. Where the packet contains band and locator data, KST4Contest also updates the per-band Worked state and worked grid square.
|
||||
|
||||
|
||||
|
||||
## Native Win-Test integration
|
||||
|
||||
Win-Test uses a separate listener for its native network protocol. KST4Contest resolves the Win-Test band ID, including 50 and 70 MHz, and stores the resulting Worked information in the same internal database.
|
||||
|
||||
STATUS packets can also update the local QRG. In multi-operator networks, a station-name filter prevents STATUS packets from another operating position from replacing the frequency of the intended radio.
|
||||
|
||||
Win-Test can additionally receive skeds created in KST4Contest. The handover only takes place when a QRG matching the selected band can be determined. No fixed fallback frequency is inserted merely to make the packet technically valid.
|
||||
|
||||
> The band-aware sked handover and explicit `SSB`/`CW` selection are included in Nightly / v1.42.
|
||||
|
||||
## Stored state and limitations
|
||||
|
||||
Worked, NOT-QRV and worked-grid information is stored in the internal SQLite database and restored after a restart. Contest-related records expire automatically after three days.
|
||||
|
||||
KST4Contest can only use the fields supplied by the selected interface. Missing band or locator data is not reconstructed from guesswork. This makes the result less complete in some cases, but also avoids turning an incomplete log packet into incorrect Worked information.
|
||||
|
||||
[Read the complete log synchronisation setup in the manual.](/manual/en/log-sync/)
|
||||
@@ -3,24 +3,70 @@ title: Sked Reminder
|
||||
icon: 🔔
|
||||
category: Sked Management
|
||||
since: "1.40"
|
||||
summary: Store planned contacts and issue configurable chat messages plus local alerts before the agreed time.
|
||||
description: Sked Reminder keeps scheduled contacts visible and provides automatic advance messages together with acoustic and visual operator alerts.
|
||||
summary: Create a timed contact, raise its priority, show it on the timeline and optionally send reminder PMs before the agreed time.
|
||||
description: KST4Contest keeps scheduled contacts in the active workflow, increases their priority as the agreed time approaches and can remind both operators.
|
||||
tagsList:
|
||||
- sked
|
||||
- ON4KST
|
||||
- contest reminder
|
||||
- Win-Test
|
||||
related:
|
||||
- priority-score
|
||||
- airscout
|
||||
- timeline
|
||||
---
|
||||
|
||||
## Never lose important skeds
|
||||
## Why store a sked inside the chat client?
|
||||
|
||||
During active contests, it is easy to miss a planned contact while handling chat traffic, logging and band changes.
|
||||
A contact agreed for five or ten minutes later has to compete with incoming messages, logging, antenna changes and other stations asking for attention. Remembering the time is only part of the problem. The station must also become visible again when the appointment approaches.
|
||||
|
||||
Sked Reminder keeps scheduled contacts visible.
|
||||
KST4Contest therefore treats a sked as an active operating task rather than a simple alarm.
|
||||
|
||||
## Built for real contest pressure
|
||||
## What happens when a sked is created?
|
||||
|
||||
The workflow supports time-critical operation where missing a few minutes can mean missing a QSO.
|
||||
Select the station, the remaining time and one of the locally enabled bands. The mode can be set to `SSB` or `CW` for a possible Win-Test handover.
|
||||
|
||||
After pressing **Create sked**, KST4Contest:
|
||||
|
||||
1. stores the sked internally,
|
||||
2. raises the station's Priority Score as the scheduled time approaches,
|
||||
3. adds the contact to the AP and sked timeline, and
|
||||
4. optionally schedules private reminder messages.
|
||||
|
||||
|
||||
|
||||
The internal sked does not depend on Win-Test. If no logger is connected or the network handover fails, the sked remains available in KST4Contest.
|
||||
|
||||
## Reminding the remote station
|
||||
|
||||
Reminder PMs are optional. The available patterns are:
|
||||
|
||||
- two and one minute before the sked,
|
||||
- five, two and one minute before the sked, or
|
||||
- ten, five, two and one minute before the sked.
|
||||
|
||||
Messages are sent to the complete KST callsign in the selected chat category. A band-specific login such as `CALLSIGN-70` therefore remains a separate message target instead of being silently reduced to the base callsign.
|
||||
|
||||
The local operator receives a visual **SKED** indication and, if simple notification sounds are enabled, an acoustic reminder.
|
||||
|
||||
## Win-Test handover
|
||||
|
||||
When the Win-Test network listener is enabled, KST4Contest also attempts to send the sked to Win-Test.
|
||||
|
||||
The frequency is not guessed. KST4Contest first looks for a recent QRG of the remote station on the selected band. If none is available, it checks whether the local QRG of the selected chat category belongs to that band. Without a matching frequency, the Win-Test handover is omitted while the internal sked remains intact.
|
||||
|
||||
KST-specific suffixes such as `-2`, `-70` or `-144` are removed from the callsign passed to the log. Portable components such as `/P` and `/M` are preserved.
|
||||
|
||||
> Band-aware QRG validation, explicit `SSB`/`CW` selection and the corrected handling of KST suffixes are included in Nightly / v1.42.
|
||||
|
||||
|
||||
|
||||
## What the reminder cannot guarantee
|
||||
|
||||
Skeds and reminder schedules are stored in memory. They must be recreated after restarting KST4Contest.
|
||||
|
||||
The proposed band is derived from recent chat and station-name information. This is useful context, not proof that the station is still operating on the same QRG. Check the band, time and mode before creating the sked.
|
||||
|
||||
In plain terms: the function makes a scheduled contact considerably harder to overlook. It cannot prevent every missed sked.
|
||||
|
||||
[Read the complete sked handling and its limitations in the manual.](/manual/en/features/#skeds-and-sked-reminders)
|
||||
@@ -1,25 +1,54 @@
|
||||
---
|
||||
title: Timeline View
|
||||
title: AP and Sked Timeline
|
||||
icon: ⏱️
|
||||
category: Contest Awareness
|
||||
since: "1.40"
|
||||
summary: Show AP-based priority candidates and scheduled contacts on a shared timeline.
|
||||
description: The Timeline View places upcoming aircraft scatter candidates and planned skeds into a common time-based overview.
|
||||
summary: Show upcoming aircraft-scatter candidates and scheduled contacts together on a 30-minute timeline.
|
||||
description: The timeline relates AirScout opportunities, priority candidates, antenna direction and internal skeds to their expected time.
|
||||
tagsList:
|
||||
- timeline
|
||||
- AP windows
|
||||
- airplane scatter
|
||||
- aircraft scatter
|
||||
- sked
|
||||
related:
|
||||
- airscout
|
||||
- priority-score
|
||||
- sked-reminder
|
||||
---
|
||||
|
||||
## Timing matters
|
||||
## The useful station may only be useful for a minute
|
||||
|
||||
Many VHF/UHF/SHF opportunities are short-lived.
|
||||
Aircraft-scatter opportunities are time-dependent. A candidate which matters in two minutes may be irrelevant now, while an agreed sked must remain visible even when no aircraft is currently available.
|
||||
|
||||
The Timeline View helps operators see upcoming timing windows instead of keeping everything in mind manually.
|
||||
The timeline places both kinds of event into the same 30-minute view.
|
||||
|
||||
## Designed for fast awareness
|
||||
Events further in the future appear on the right. As their time approaches, they move left towards the present.
|
||||
|
||||
The timeline supports quick decisions during busy contest operation.
|
||||
|
||||
|
||||
## AP candidates and scheduled contacts remain distinct
|
||||
|
||||
AP candidates appear in the upper lanes. Up to four selected candidates can be shown for each arrival minute. Their colours represent the reflection potential reported by AirScout:
|
||||
|
||||
- magenta from 95%,
|
||||
- red from 75%,
|
||||
- yellow from 50%, and
|
||||
- blue below 50%.
|
||||
|
||||
Skeds appear as diamonds in the lower lane. Their labels use the complete selected KST callsign so that band-specific or otherwise suffixed logins remain identifiable.
|
||||
|
||||
> Complete KST callsigns in sked labels are included in Nightly / v1.42.
|
||||
|
||||
## Antenna direction remains visible
|
||||
|
||||
A marker becomes more transparent when its QTF is clearly outside the current antenna direction. The callsign remains readable. Targets near the centre of the configured antenna beam receive an additional visual highlight.
|
||||
|
||||
Clicking an AP candidate selects the corresponding active chat member, including the callsign suffix and chat category.
|
||||
|
||||
## A timing aid, not a contact forecast
|
||||
|
||||
The timeline shows when an event is expected to matter. It does not guarantee that the frequency is clear, that the remote station is ready or that the calculated aircraft path will produce a workable signal.
|
||||
|
||||
AirScout data can change. So can the actual operating situation.
|
||||
|
||||
[Read the complete timeline behaviour in the manual.](/manual/en/features/#ap-and-sked-timeline)
|
||||
Reference in New Issue
Block a user