From b3ca684f04c1fc1a5d6ea1ed73f28f889d214ca0 Mon Sep 17 00:00:00 2001 From: Marc Froehlich Date: Fri, 7 Aug 2026 23:38:13 +0200 Subject: [PATCH] updated website for sked and timeline features --- website/src/features/log-sync.md | 50 ++++++++++++++++++---- website/src/features/sked-reminder.md | 60 +++++++++++++++++++++++---- website/src/features/timeline.md | 47 +++++++++++++++++---- 3 files changed, 133 insertions(+), 24 deletions(-) diff --git a/website/src/features/log-sync.md b/website/src/features/log-sync.md index 7a53515..66d5bec 100644 --- a/website/src/features/log-sync.md +++ b/website/src/features/log-sync.md @@ -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. \ No newline at end of file +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. + +![Log synchronisation settings](/manual/assets/client_settings_window_logsync.png) + +## 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/) \ No newline at end of file diff --git a/website/src/features/sked-reminder.md b/website/src/features/sked-reminder.md index a32dac3..c32d1ee 100644 --- a/website/src/features/sked-reminder.md +++ b/website/src/features/sked-reminder.md @@ -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. \ No newline at end of file +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. + +![Sked controls in the Further Info section](/manual/assets/sked_controls.png) + +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. + +![Sked handed over from KST4Contest to Win-Test](/manual/assets/wintest_sked_handover.png) + +## 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) \ No newline at end of file diff --git a/website/src/features/timeline.md b/website/src/features/timeline.md index 1444714..d20755d 100644 --- a/website/src/features/timeline.md +++ b/website/src/features/timeline.md @@ -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. \ No newline at end of file +![AP candidates and skeds in the timeline](/manual/assets/sked_timeline.png) + +## 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) \ No newline at end of file