Received information
ON4KST messages, logger packets, Win-Test network data and AirScout responses provide information at different levels of detail. Missing fields are not automatically equivalent to negative information.
Functions
How KST4Contest supports the contest workflow
KST4Contest combines ON4KST messages with station, band, Worked, sked, AirScout and logger information. The individual functions use this shared context instead of treating every message or interface as an isolated event.
Some information is received directly from another program. Other information must be derived from chat messages, station names or the current operating state. The distinction matters: a detected band or a calculated priority is useful context, but not automatically a confirmed fact.
Shared context
Why the functions affect each other
A newly detected frequency can change the known bands of a station. This can affect its Worked state, filters, priority, map path and a later sked handover. The same principle applies to information received from a logger or entered manually.
Derived information
Bands, frequencies, activity and candidate priorities may be derived from several sources. Explicit NOT-QRV information overrules a merely inferred band opportunity.
Operator decision
Scores, filters, AP windows and path assessments reduce the amount of information that must be evaluated manually. They do not guarantee a contact or replace checking the actual operating situation.
Function overview
Functions in their intended order
The pages below explain the operating problem behind each function, the information it uses and the limitations that remain.
KST4Contest Functions
Read how it works →Contest Awareness
AP and Sked Timeline
Show upcoming aircraft-scatter candidates and scheduled contacts together on a 30-minute timeline.
Read how it works →Station Control
PSTRotator Control
Point the antenna at a selected chat station and use the azimuth reported by PSTRotator throughout the KST4Contest operating context.
Read how it works →Aircraft Scatter
AirScout Integration
Request station-specific aircraft-scatter information from AirScout and include the returned AP timing in the user list, timeline and candidate priority.
Read how it works →Contest Workflow
Band Recognition and Opportunities
Automatically recognise active bands and alert the operator immediately after logging when the same station can still be worked on another common band.
Read how it works →Contest Workflow
Priority Score System
Calculate one priority per base callsign, exclude known unusable band combinations and order the remaining active stations by band, distance, direction, activity, AirScout, reply and sked context.
Read how it works →Contest Awareness
Combinable Station Filters
Combine spatial, operating and propagation filters to focus the user list and station map without removing hidden stations from the active chat context.
Read how it works →Contest Awareness
Station Map and Path Analysis
Use the filtered chat-member list as a geographical contest worklist and examine the selected radio path with terrain, Fresnel and link-budget estimates.
Read how it works →Logger Integration
Log Synchronisation
Import callsign, band, locator and QRG information from supported contest loggers at the level provided by each interface.
Read how it works →Operator Speed
Macros and Variables
Insert recurring text through shortcut buttons or snippets and add current QRG, locator, heading, station-name and AirScout information when the message is used.
Read how it works →Sked Management
Sked Reminder
Create a timed contact, raise its priority, show it on the timeline and optionally send reminder PMs before the agreed time.
Read how it works →Contest Workflow
Directional Opportunities
Recognise when a station in a directed ON4KST exchange may be pointing towards the local station and highlight the short-lived opportunity.
Read how it works →Logger Integration
Local DX Cluster Server
Forward detected directional opportunities and their known frequencies as local DX Cluster spots to compatible contest loggers.
Read how it works →ON4KST Chat
Automatic QRG Detection
Recognise complete and relative QRG information in chat messages and retain the sender's recent band context before using a global fallback.
Read how it works →Station Control
TRX/QRG Synchronisation
Keep the primary operating frequency in MYQRG current from RadioInfo or Win-Test STATUS packets while leaving logging and SECONDQRG independent.
Read how it works →ON4KST Chat
Automatic Private Replies
Answer repeated private messages or QRG requests without losing the complete callsign, chat category or protection against automatic reply loops.
Read how it works →ON4KST Chat
Dual Chat Categories
Monitor two ON4KST categories in one interface while preserving the complete callsign and category required for correct message routing.
Read how it works →ON4KST Chat
Global Message Views
Follow public chat, ON4KST DX cluster traffic and directed messages between other stations without tying the overview to the currently selected station.
Read how it works →ON4KST Chat
QSO Monitoring
Follow messages sent or received by one station across its KST suffixes without changing the actual message destination or chat category.
Read how it works →ON4KST Chat
Private Message Handling
Catch mentions of the configured login callsign from public or directed chat traffic and use six green age levels without changing the original message routing.
Read how it works →Technical details
The manual remains the authoritative description
These pages provide a practical overview. Configuration parameters, interface requirements, exact behaviour and version-specific limitations are documented in the manual. Where the short description and the manual differ, the manual should be corrected first. Two competing descriptions of the same function would not improve matters.