diff --git a/.github/workflows/website-build.yml b/.github/workflows/website-build.yml deleted file mode 100644 index 449bf22..0000000 --- a/.github/workflows/website-build.yml +++ /dev/null @@ -1,76 +0,0 @@ -name: Build Website - -on: - push: - branches: - - main - paths: - - website/** - - github_docs/** - - .github/workflows/website-build.yml - pull_request: - branches: - - main - paths: - - website/** - - github_docs/** - - .github/workflows/website-build.yml - workflow_dispatch: - -env: - FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true - -concurrency: - group: website-build-${{ github.ref }} - cancel-in-progress: ${{ github.event_name == 'pull_request' }} - -permissions: - contents: read - -jobs: - build-website: - name: Build 11ty Website - runs-on: ubuntu-latest - - steps: - - name: Checkout - uses: actions/checkout@v4.1.7 - with: - ssh-key: ${{ secrets.WEBSITE_DEPLOY_KEY }} - - - name: Set up Node.js - uses: actions/setup-node@v4 - with: - node-version: "24" - cache: npm - cache-dependency-path: website/package-lock.json - - - name: Install dependencies - working-directory: website - run: npm ci - - - name: Build website - working-directory: website - run: npm run build - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - - - name: Upload website artifact - uses: actions/upload-artifact@v4.3.4 - with: - name: kst4contest-website - path: website/_site/ - retention-days: 7 - - - name: Commit rebuilt site - if: github.event_name == 'push' && github.ref == 'refs/heads/main' - run: | - git config user.name "github-actions[bot]" - git config user.email "github-actions[bot]@users.noreply.github.com" - git add website/_site - if git diff --cached --quiet; then - echo "No changes to commit" - else - git commit -m "chore: rebuild website [skip ci]" - git push - fi \ No newline at end of file diff --git a/.github/workflows/website-roadmap-rebuild.yml b/.github/workflows/website-roadmap-rebuild.yml deleted file mode 100644 index bd16e9d..0000000 --- a/.github/workflows/website-roadmap-rebuild.yml +++ /dev/null @@ -1,59 +0,0 @@ -name: Rebuild Roadmap - -on: - issues: - types: [opened, edited, closed, reopened, labeled, unlabeled, milestoned, demilestoned] - -env: - FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true - -concurrency: - group: website-build-${{ github.ref }} - cancel-in-progress: false - -permissions: - contents: read - -jobs: - rebuild-roadmap: - name: Rebuild website roadmap - runs-on: ubuntu-latest - # Only worth a rebuild if the "enhancement" label is involved: either the - # issue currently carries it, or this event just added/removed it. - if: contains(github.event.issue.labels.*.name, 'enhancement') || github.event.label.name == 'enhancement' - - steps: - - name: Checkout - uses: actions/checkout@v4.1.7 - with: - ref: main - ssh-key: ${{ secrets.WEBSITE_DEPLOY_KEY }} - - - name: Set up Node.js - uses: actions/setup-node@v4 - with: - node-version: "24" - cache: npm - cache-dependency-path: website/package-lock.json - - - name: Install dependencies - working-directory: website - run: npm ci - - - name: Build website - working-directory: website - run: npm run build - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - - - name: Commit rebuilt site - run: | - git config user.name "github-actions[bot]" - git config user.email "github-actions[bot]@users.noreply.github.com" - git add website/_site - if git diff --cached --quiet; then - echo "No changes to commit" - else - git commit -m "chore: rebuild website roadmap [skip ci]" - git push - fi diff --git a/.gitignore b/.gitignore index bfbf6e5..ae13c6e 100644 --- a/.gitignore +++ b/.gitignore @@ -39,5 +39,8 @@ dist/ # node Modules in website website/node_modules/ +# built website output (rebuilt on the server) +website/_site/ + # Local secrets for act testing .secrets diff --git a/website/_site/about/index.html b/website/_site/about/index.html deleted file mode 100644 index 5d780aa..0000000 --- a/website/_site/about/index.html +++ /dev/null @@ -1,137 +0,0 @@ - - - - - About KST4Contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

About

-

Built for real contest operation.

-

- KST4Contest was created to turn ON4KST chat activity into actionable contest workflow. -

-
- -
-
-

Why KST4Contest exists

-

- Generic chat clients display messages. KST4Contest goes further: - it helps operators identify candidates, manage skeds, use AirScout timing, - synchronize with loggers and reduce workload during VHF/UHF/SHF contests. -

- -

Open source and practical

-

- The project is open source and focused on practical contest station workflows. - Features are designed around real operating pressure, not theoretical UI concepts. -

- -

Community supported

- -

- - KST4Contest is developed independently. - - Community support helps finance hosting, - online services, - testing across multiple operating systems - and future contest-oriented features. - -

- -
- -
- - - - - - diff --git a/website/_site/assets/css/main.css b/website/_site/assets/css/main.css deleted file mode 100644 index 4e5d0cb..0000000 --- a/website/_site/assets/css/main.css +++ /dev/null @@ -1,807 +0,0 @@ -:root { - --bg: #050816; - --bg2: #0b1224; - --panel: rgba(15, 23, 42, 0.78); - --panel2: rgba(30, 41, 59, 0.72); - --border: rgba(148, 163, 184, 0.22); - --text: #f8fafc; - --muted: #aab6ca; - --soft: #64748b; - --accent: #38bdf8; - --accent2: #a855f7; - --accent3: #22c55e; - --shadow: 0 24px 80px rgba(0, 0, 0, 0.45); -} - -* { - box-sizing: border-box; -} - -html { - scroll-behavior: smooth; - background: var(--bg); -} - -body { - margin: 0; - min-height: 100vh; - background: - radial-gradient(circle at 14% 12%, rgba(168, 85, 247, 0.30), transparent 28%), - radial-gradient(circle at 82% 16%, rgba(56, 189, 248, 0.24), transparent 30%), - radial-gradient(circle at 50% 85%, rgba(34, 197, 94, 0.11), transparent 35%), - linear-gradient(180deg, #050816 0%, #07111f 100%); - color: var(--text); - font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; - line-height: 1.65; - overflow-x: hidden; -} - -body::before { - content: ""; - position: fixed; - inset: -20%; - z-index: -3; - background: - radial-gradient(circle at 20% 20%, rgba(168, 85, 247, 0.22), transparent 28%), - radial-gradient(circle at 78% 18%, rgba(56, 189, 248, 0.18), transparent 30%), - radial-gradient(circle at 45% 80%, rgba(34, 197, 94, 0.10), transparent 26%); - filter: blur(48px); - transform: translateZ(0); -} - -body::after { - content: ""; - position: fixed; - inset: 0; - z-index: -2; - pointer-events: none; - background-image: - linear-gradient(rgba(255,255,255,0.038) 1px, transparent 1px), - linear-gradient(90deg, rgba(255,255,255,0.038) 1px, transparent 1px); - background-size: 54px 54px; - -webkit-mask-image: radial-gradient(circle at center, black 0%, black 46%, transparent 78%); - mask-image: radial-gradient(circle at center, black 0%, black 46%, transparent 78%); -} - -.site-bg { - position: fixed; - inset: 0; - z-index: -1; - pointer-events: none; - background: - linear-gradient(180deg, rgba(5, 8, 22, 0.10), rgba(5, 8, 22, 0.84)), - radial-gradient(circle at 8% 24%, rgba(168, 85, 247, 0.18), transparent 26%), - radial-gradient(circle at 82% 20%, rgba(56, 189, 248, 0.16), transparent 30%); -} - -.site-bg::before { - content: ""; - position: absolute; - inset: 0; - background: - radial-gradient(circle at top, transparent 0%, rgba(5, 8, 22, 0.42) 72%), - linear-gradient(90deg, rgba(5, 8, 22, 0.25), transparent 50%, rgba(5, 8, 22, 0.25)); -} - -.site-bg::after { - content: ""; - position: absolute; - inset: 0; - background-image: - radial-gradient(circle at 1px 1px, rgba(255,255,255,0.10) 1px, transparent 0); - background-size: 28px 28px; - opacity: 0.11; - -webkit-mask-image: radial-gradient(circle at 50% 22%, black 0%, transparent 68%); - mask-image: radial-gradient(circle at 50% 22%, black 0%, transparent 68%); -} - -a { - color: var(--accent); - text-decoration: none; -} - -a:hover { - color: white; -} - -.site-header { - position: sticky; - top: 0; - z-index: 10; - display: flex; - justify-content: space-between; - gap: 24px; - align-items: center; - padding: 18px 6vw; - background: rgba(5, 8, 22, 0.76); - -webkit-backdrop-filter: blur(18px); - backdrop-filter: blur(18px); - border-bottom: 1px solid var(--border); -} - -.brand { - display: flex; - gap: 12px; - align-items: center; - color: white; -} - -.brand-mark { - display: grid; - place-items: center; - width: 40px; - height: 40px; - border-radius: 14px; - background: - radial-gradient(circle at 30% 20%, white, transparent 22%), - linear-gradient(135deg, var(--accent), var(--accent2)); - box-shadow: - 0 0 26px rgba(168, 85, 247, 0.45), - 0 0 50px rgba(56, 189, 248, 0.18); -} - -.brand strong { - display: block; - font-size: 1.05rem; - letter-spacing: 0.02em; -} - -.brand small { - display: block; - color: var(--muted); - font-size: 0.78rem; - margin-top: -4px; -} - -.site-nav { - display: flex; - align-items: center; - gap: 16px; - flex-wrap: wrap; -} - -.site-nav a { - color: var(--muted); - font-size: 0.95rem; -} - -.site-nav a:hover { - color: white; -} - -.nav-cta { - padding: 9px 14px; - border-radius: 999px; - color: white !important; - background: linear-gradient(135deg, var(--accent), var(--accent2)); - box-shadow: 0 0 22px rgba(56, 189, 248, 0.28); -} - -.hero { - position: relative; - padding: 92px 6vw 62px; - max-width: 1180px; -} - -.hero::before { - content: ""; - position: absolute; - inset: -160px -12vw auto -12vw; - height: 420px; - z-index: -1; - pointer-events: none; - background: - radial-gradient(circle at 24% 40%, rgba(168, 85, 247, 0.20), transparent 36%), - radial-gradient(circle at 62% 30%, rgba(56, 189, 248, 0.14), transparent 40%); - filter: blur(74px); -} - -.hero-split { - display: grid; - grid-template-columns: minmax(0, 1fr) minmax(360px, 0.9fr); - gap: 42px; - align-items: center; - max-width: 1500px; -} - -.hero h1 { - margin: 0 0 22px; - font-size: clamp(3rem, 8vw, 6.5rem); - line-height: 0.95; - letter-spacing: -0.07em; - background: linear-gradient(90deg, #ffffff 0%, #7dd3fc 40%, #a855f7 78%); - -webkit-background-clip: text; - background-clip: text; - color: transparent; -} - -.hero .lead, -.hero > p, -.section-heading p, -.cta-panel p { - color: var(--muted); - font-size: 1.18rem; - max-width: 850px; -} - -.badge, -.eyebrow { - display: inline-flex; - width: fit-content; - align-items: center; - gap: 8px; - color: #e9d5ff; - background: rgba(168, 85, 247, 0.13); - border: 1px solid rgba(168, 85, 247, 0.34); - padding: 6px 12px; - border-radius: 999px; - text-transform: uppercase; - letter-spacing: 0.08em; - font-size: 0.74rem; - font-weight: 800; - box-shadow: 0 0 22px rgba(168, 85, 247, 0.12); -} - -.actions { - display: flex; - gap: 14px; - margin-top: 30px; - flex-wrap: wrap; -} - -.button { - display: inline-flex; - align-items: center; - justify-content: center; - min-height: 46px; - padding: 12px 18px; - border-radius: 14px; - color: #020617; - background: linear-gradient(135deg, var(--accent), var(--accent2)); - font-weight: 800; - box-shadow: - 0 16px 44px rgba(56, 189, 248, 0.25), - inset 0 1px 0 rgba(255, 255, 255, 0.35); -} - -.button:hover { - color: white; - transform: translateY(-1px); -} - -.button.secondary { - color: white; - background: rgba(30, 41, 59, 0.85); - border: 1px solid var(--border); - box-shadow: none; -} - -.button.ghost { - color: white; - background: transparent; - border: 1px solid var(--border); - box-shadow: none; -} - -.hero-panel, -.card, -.cta-panel { - background: - linear-gradient(180deg, rgba(255,255,255,0.045), transparent 42%), - var(--panel); - border: 1px solid var(--border); - border-radius: 26px; - box-shadow: var(--shadow); - -webkit-backdrop-filter: blur(16px); - backdrop-filter: blur(16px); -} - -.hero-panel { - position: relative; - overflow: hidden; - transform: perspective(1200px) rotateY(-5deg) rotateX(2deg); -} - -.hero-panel::before { - content: ""; - position: absolute; - inset: -1px; - pointer-events: none; - background: - linear-gradient(135deg, rgba(56, 189, 248, 0.45), transparent 35%, rgba(168, 85, 247, 0.38)); - opacity: 0.18; -} - -.terminal-bar { - display: flex; - gap: 8px; - align-items: center; - padding: 14px 16px; - border-bottom: 1px solid var(--border); - background: rgba(2, 6, 23, 0.74); -} - -.terminal-bar span { - width: 11px; - height: 11px; - border-radius: 50%; - background: var(--accent2); -} - -.terminal-bar span:nth-child(2) { - background: #f59e0b; -} - -.terminal-bar span:nth-child(3) { - background: var(--accent3); -} - -.terminal-bar strong { - margin-left: 8px; - color: var(--muted); - font-size: 0.85rem; -} - -.mock-grid { - display: grid; - gap: 12px; - padding: 18px; -} - -.mini-card { - padding: 14px; - border-radius: 16px; - background: rgba(15, 23, 42, 0.88); - border: 1px solid rgba(148, 163, 184, 0.16); -} - -.mini-card strong, -.mini-card small { - display: block; -} - -.mini-card small { - color: var(--muted); - margin-top: 4px; -} - -.section { - padding: 52px 6vw; -} - -.section.narrow { - max-width: 1040px; -} - -.section-heading { - margin-bottom: 26px; -} - -.section h2 { - font-size: clamp(2rem, 4vw, 3.4rem); - line-height: 1.05; - margin: 12px 0 14px; - letter-spacing: -0.04em; -} - -.grid { - display: grid; - grid-template-columns: repeat(auto-fit, minmax(260px, 1fr)); - gap: 18px; -} - -.card { - padding: 24px; - transition: transform 180ms ease, border-color 180ms ease, background 180ms ease, box-shadow 180ms ease; -} - -.card:hover { - transform: translateY(-4px); - border-color: rgba(56, 189, 248, 0.45); - background: - linear-gradient(180deg, rgba(255,255,255,0.055), transparent 42%), - rgba(15, 23, 42, 0.92); - box-shadow: - 0 26px 90px rgba(0, 0, 0, 0.50), - 0 0 30px rgba(56, 189, 248, 0.08); -} - -.card h3, -.card h2 { - margin-top: 0; -} - -.card p { - color: var(--muted); -} - -.roadmap-version + .roadmap-version { - margin-top: 24px; -} - -.roadmap-version ul { - padding-left: 20px; -} - -.roadmap-version li { - margin-bottom: 8px; -} - -.roadmap-done a { - color: var(--muted); - text-decoration: line-through; -} - -.feature-icon { - font-size: 2rem; - margin-bottom: 14px; -} - -.feature-icon.large { - font-size: 4rem; -} - -.content-card { - max-width: 980px; -} - -.tag-list { - display: flex; - gap: 10px; - flex-wrap: wrap; -} - -.tag-list span { - padding: 7px 11px; - border-radius: 999px; - color: var(--muted); - background: rgba(15, 23, 42, 0.85); - border: 1px solid var(--border); -} - -.download-card { - min-height: 220px; -} - -.screenshot-placeholder { - display: grid; - place-items: center; - min-height: 180px; - margin-bottom: 16px; - border-radius: 18px; - background: - linear-gradient(135deg, rgba(56, 189, 248, 0.20), rgba(168, 85, 247, 0.20)), - rgba(2, 6, 23, 0.7); - border: 1px solid var(--border); - color: white; - font-weight: 800; -} - -.cta-panel { - padding: clamp(28px, 5vw, 60px); -} - -.manual-content { - max-width: 980px; -} - -.manual-content h1, -.manual-content h2, -.manual-content h3 { - line-height: 1.2; -} - -.manual-content pre { - overflow-x: auto; - padding: 16px; - border-radius: 14px; - background: #020617; -} - -.manual-content code { - color: #bae6fd; -} - -.manual-content table { - width: 100%; - border-collapse: collapse; - overflow-x: auto; -} - -.manual-content th, -.manual-content td { - border-bottom: 1px solid rgba(148, 163, 184, 0.22); - padding: 10px; - text-align: left; -} - -.site-footer { - padding: 42px 6vw; - color: var(--muted); - border-top: 1px solid var(--border); -} - -@media (max-width: 900px) { - .hero-split { - grid-template-columns: 1fr; - } - - .hero-panel { - transform: none; - } - - .site-header { - align-items: flex-start; - flex-direction: column; - } -} - -@media (prefers-reduced-motion: no-preference) { - .button, - .card { - transition: all 180ms ease; - } -} - -.footer-grid { - display: grid; - grid-template-columns: 2fr repeat(3, 1fr); - gap: 24px; -} - -.footer-grid strong { - color: white; -} - -.footer-grid p { - margin: 8px 0; -} - -@media (max-width: 800px) { - .footer-grid { - grid-template-columns: 1fr; - } -} -/* ================================================================ - KST4Contest brand recovery: green operator-console identity - and full-screen interactive hero - ================================================================ */ - -:root { - --bg: #050806; - --bg2: #0b140f; - --panel: rgba(15, 28, 20, 0.82); - --panel2: rgba(24, 43, 31, 0.84); - --border: rgba(125, 178, 134, 0.22); - --text: #f4f7f3; - --muted: #a9b8ad; - --soft: #6e8173; - --accent: #54d63d; - --accent2: #8aef64; - --accent3: #31b54a; - --fx-plane: #79ff73; - --fx-plane-muted: rgba(121, 255, 115, 0.42); - --fx-beam: #52ff65; - --fx-beam-glow: rgba(82, 255, 101, 0.28); - --fx-reflection: #d2ffc8; - --fx-trail: rgba(121, 255, 115, 0.17); - --fx-grid: rgba(121, 255, 115, 0.055); -} - -body { - background: - radial-gradient(circle at 14% 12%, rgba(52, 165, 57, 0.20), transparent 30%), - radial-gradient(circle at 82% 16%, rgba(95, 218, 82, 0.14), transparent 32%), - radial-gradient(circle at 50% 85%, rgba(32, 126, 55, 0.12), transparent 36%), - linear-gradient(180deg, #070b09 0%, #0b1410 100%); -} - -body::before { - background: - radial-gradient(circle at 20% 20%, rgba(60, 173, 61, 0.18), transparent 28%), - radial-gradient(circle at 78% 18%, rgba(97, 222, 80, 0.13), transparent 30%), - radial-gradient(circle at 45% 80%, rgba(34, 122, 53, 0.11), transparent 26%); -} - -body::after { - background-image: - linear-gradient(rgba(160,255,160,0.032) 1px, transparent 1px), - linear-gradient(90deg, rgba(160,255,160,0.032) 1px, transparent 1px); -} - -.site-bg { - background: - linear-gradient(180deg, rgba(5, 8, 6, 0.10), rgba(5, 8, 6, 0.84)), - radial-gradient(circle at 8% 24%, rgba(52, 165, 57, 0.14), transparent 26%), - radial-gradient(circle at 82% 20%, rgba(95, 218, 82, 0.12), transparent 30%); -} - -.site-header { - background: rgba(5, 8, 7, 0.82); -} - -.brand-mark, -.nav-cta, -.button { - background: linear-gradient(135deg, var(--accent), var(--accent2)); -} - -.brand-mark { - box-shadow: - 0 0 26px rgba(84, 214, 61, 0.42), - 0 0 50px rgba(49, 181, 74, 0.16); -} - -.nav-cta { - color: #061008 !important; - box-shadow: 0 0 22px rgba(84, 214, 61, 0.28); -} - -main { - width: 100%; -} - -.hero.hero-split { - position: relative; - width: 100%; - max-width: none; - min-height: calc(100vh - 73px); - display: grid; - grid-template-columns: minmax(420px, 0.9fr) minmax(520px, 1.1fr); - gap: clamp(40px, 5vw, 110px); - align-items: center; - align-content: center; - padding: clamp(56px, 7vh, 100px) clamp(28px, 6vw, 110px); - overflow: hidden; -} - -.hero.hero-split > *:not(.hero-radio-fx):not(.hero-fx-vignette) { - position: relative; - z-index: 3; -} - -.hero-copy { - max-width: 760px; -} - -.hero.hero-split h1 { - font-size: clamp(3.4rem, 8vw, 7rem); - background: linear-gradient(90deg, #ffffff 0%, #c9ffd0 28%, #77ec70 58%, #45bd4d 100%); - -webkit-background-clip: text; - background-clip: text; - color: transparent; -} - -.badge, -.eyebrow { - color: #caffc0; - background: rgba(52, 165, 57, 0.12); - border-color: rgba(105, 232, 88, 0.32); - box-shadow: 0 0 22px rgba(82, 255, 101, 0.08); -} - -.button { - color: #041007; - box-shadow: - 0 16px 44px rgba(84, 214, 61, 0.22), - inset 0 1px 0 rgba(255,255,255,0.35); -} - -.button.secondary { - color: white; - background: rgba(28, 43, 32, 0.90); -} - -.hero-panel { - width: min(100%, 760px); - justify-self: center; - transform: perspective(1200px) rotateY(-4deg) rotateX(1.5deg); -} - -.hero-panel, -.card, -.cta-panel { - background: - linear-gradient(180deg, rgba(255,255,255,0.045), transparent 42%), - rgba(15, 28, 20, 0.82); -} - -.mini-card { - background: rgba(12, 25, 17, 0.88); - border-color: rgba(148, 184, 155, 0.16); -} - -.card:hover { - border-color: rgba(84, 214, 61, 0.42); - background: - linear-gradient(180deg, rgba(255,255,255,0.055), transparent 42%), - rgba(12, 25, 17, 0.94); - box-shadow: - 0 26px 90px rgba(0,0,0,0.50), - 0 0 30px rgba(84,214,61,0.07); -} - -.hero-radio-fx { - position: absolute; - inset: 0; - z-index: 0; - width: 100%; - height: 100%; - pointer-events: none; - opacity: 0.78; -} - -.hero-fx-vignette { - position: absolute; - inset: 0; - z-index: 1; - pointer-events: none; - background: - linear-gradient(90deg, - rgba(7,11,9,0.92) 0%, - rgba(7,11,9,0.70) 32%, - rgba(7,11,9,0.17) 62%, - rgba(7,11,9,0.38) 100%), - linear-gradient(180deg, - rgba(7,11,9,0.08), - rgba(7,11,9,0.58)); -} - -html[data-theme="light"] { - --bg: #f4f4f2; - --bg2: #ffffff; - --panel: rgba(255,255,255,0.90); - --panel2: rgba(242,242,239,0.94); - --border: rgba(91,91,86,0.20); - --text: #252522; - --muted: #656560; - --soft: #888881; - --accent: #d33732; - --accent2: #f25a51; - --accent3: #ae2727; - --fx-plane: #df3732; - --fx-plane-muted: rgba(211,55,50,0.38); - --fx-beam: #ef4039; - --fx-beam-glow: rgba(239,64,57,0.22); - --fx-reflection: #ff8d84; - --fx-trail: rgba(211,55,50,0.15); - --fx-grid: rgba(185,47,43,0.045); -} - -@media (min-width: 1600px) { - .hero.hero-split { - grid-template-columns: minmax(520px, 0.85fr) minmax(620px, 1.15fr); - } - - .hero-panel { - width: min(100%, 820px); - } -} - -@media (max-width: 1000px) { - .hero.hero-split { - min-height: auto; - grid-template-columns: 1fr; - padding-top: 64px; - padding-bottom: 64px; - } - - .hero-panel { - width: min(100%, 760px); - transform: none; - } - - .hero-radio-fx { - opacity: 0.50; - } - - .hero-fx-vignette { - background: linear-gradient(180deg, rgba(7,11,9,0.84), rgba(7,11,9,0.34)); - } -} - -@media (prefers-reduced-motion: reduce) { - .hero-radio-fx { - opacity: 0.28; - } -} diff --git a/website/_site/assets/js/hero-radio-fx.js b/website/_site/assets/js/hero-radio-fx.js deleted file mode 100644 index 61fa498..0000000 --- a/website/_site/assets/js/hero-radio-fx.js +++ /dev/null @@ -1,509 +0,0 @@ -(() => { - "use strict"; - - const canvas = document.querySelector("[data-hero-radio-fx]"); - if (!(canvas instanceof HTMLCanvasElement)) return; - - const hero = canvas.closest(".hero"); - const ctx = canvas.getContext("2d", { alpha: true, desynchronized: true }); - if (!(hero instanceof HTMLElement) || !ctx) return; - - const reducedMotion = matchMedia("(prefers-reduced-motion: reduce)"); - const coarsePointer = matchMedia("(pointer: coarse)"); - - const state = { - width: 0, - height: 0, - dpr: 1, - running: false, - visible: true, - lastFrame: 0, - spawnTime: 0, - beamTime: 0, - frameId: 0, - pointer: { x: 0, y: 0, active: false }, - planes: [], - beams: [], - reflections: [] - }; - - const clamp = (v, min, max) => Math.max(min, Math.min(max, v)); - const random = (min, max) => min + Math.random() * (max - min); - - function css(name, fallback) { - return getComputedStyle(document.documentElement).getPropertyValue(name).trim() || fallback; - } - - function palette() { - return { - plane: css("--fx-plane", "#79ff73"), - planeMuted: css("--fx-plane-muted", "rgba(121,255,115,.42)"), - beam: css("--fx-beam", "#52ff65"), - beamGlow: css("--fx-beam-glow", "rgba(82,255,101,.28)"), - reflection: css("--fx-reflection", "#d2ffc8"), - trail: css("--fx-trail", "rgba(121,255,115,.17)"), - grid: css("--fx-grid", "rgba(121,255,115,.055)") - }; - } - - function roundedRect(x, y, width, height, radius) { - const r = Math.min(radius, width / 2, height / 2); - ctx.beginPath(); - ctx.moveTo(x + r, y); - ctx.arcTo(x + width, y, x + width, y + height, r); - ctx.arcTo(x + width, y + height, x, y + height, r); - ctx.arcTo(x, y + height, x, y, r); - ctx.arcTo(x, y, x + width, y, r); - ctx.closePath(); - } - - function resize() { - const rect = hero.getBoundingClientRect(); - state.width = Math.max(1, Math.round(rect.width)); - state.height = Math.max(1, Math.round(rect.height)); - state.dpr = Math.min(devicePixelRatio || 1, 1.5); - canvas.width = Math.round(state.width * state.dpr); - canvas.height = Math.round(state.height * state.dpr); - canvas.style.width = `${state.width}px`; - canvas.style.height = `${state.height}px`; - ctx.setTransform(state.dpr, 0, 0, state.dpr, 0, 0); - - if (!state.pointer.active) { - state.pointer.x = state.width * 0.55; - state.pointer.y = state.height * 0.42; - } - } - - function stations() { - const targetX = state.width * 0.54; - const targetY = state.height * 0.43; - const left = { x: state.width * 0.075, y: state.height * 0.82, label: "JO51IJ" }; - const right = { x: state.width * 0.925, y: state.height * 0.80, label: "JN49FL" }; - left.angle = Math.atan2(targetY - left.y, targetX - left.x); - right.angle = Math.atan2(targetY - right.y, targetX - right.x); - return [left, right]; - } - - function planeLimit() { - if (coarsePointer.matches) return 5; - return state.width < 900 ? 7 : 12; - } - - function createPlane() { - const margin = 55; - const edge = Math.floor(Math.random() * 4); - let x; - let y; - - if (edge === 0) { - x = random(0, state.width); - y = -margin; - } else if (edge === 1) { - x = state.width + margin; - y = random(0, state.height); - } else if (edge === 2) { - x = random(0, state.width); - y = state.height + margin; - } else { - x = -margin; - y = random(0, state.height); - } - - const tx = state.pointer.active ? state.pointer.x : state.width * random(0.38, 0.72); - const ty = state.pointer.active ? state.pointer.y : state.height * random(0.20, 0.72); - const angle = Math.atan2(ty - y, tx - x); - const speed = random(18, 34); - - return { - x, y, angle, - vx: Math.cos(angle) * speed, - vy: Math.sin(angle) * speed, - size: random(5.5, 9), - age: 0, - maxAge: random(12, 20), - steering: random(0.65, 1.2), - wobble: random(0, Math.PI * 2), - wobbleSpeed: random(0.7, 1.4), - hit: 0 - }; - } - - function updatePlane(plane, dt) { - plane.age += dt; - plane.wobble += dt * plane.wobbleSpeed; - - const tx = state.pointer.active ? state.pointer.x : state.width * 0.56; - const ty = state.pointer.active ? state.pointer.y : state.height * 0.44; - const desired = Math.atan2(ty - plane.y, tx - plane.x); - let diff = desired - plane.angle; - while (diff > Math.PI) diff -= Math.PI * 2; - while (diff < -Math.PI) diff += Math.PI * 2; - plane.angle += diff * plane.steering * dt; - - const speed = Math.hypot(plane.vx, plane.vy); - const wobble = Math.sin(plane.wobble) * 0.14; - plane.vx = Math.cos(plane.angle + wobble) * speed; - plane.vy = Math.sin(plane.angle + wobble) * speed; - plane.x += plane.vx * dt; - plane.y += plane.vy * dt; - plane.hit = Math.max(0, plane.hit - dt * 1.8); - } - - function expired(plane) { - const margin = 180; - return plane.age > plane.maxAge || plane.x < -margin || plane.x > state.width + margin || plane.y < -margin || plane.y > state.height + margin; - } - - function beamTarget() { - if (!state.planes.length) return null; - const tx = state.pointer.active ? state.pointer.x : state.width * 0.56; - const ty = state.pointer.active ? state.pointer.y : state.height * 0.44; - const nearby = state.planes - .map(plane => ({ plane, distance: Math.hypot(plane.x - tx, plane.y - ty) })) - .filter(item => item.distance < 280) - .sort((a, b) => a.distance - b.distance); - return nearby[0]?.plane || state.planes[Math.floor(Math.random() * state.planes.length)]; - } - - function createBeam(target) { - const source = stations() - .map(station => ({ station, distance: Math.hypot(target.x - station.x, target.y - station.y) })) - .sort((a, b) => a.distance - b.distance)[0].station; - - const angle = Math.atan2(target.y - source.y, target.x - source.x); - const tip = 45; - state.beams.push({ - startX: source.x + Math.cos(angle) * tip, - startY: source.y + Math.sin(angle) * tip, - endX: target.x, - endY: target.y, - age: 0, - maxAge: 0.72 - }); - - target.hit = 1; - const values = [50, 75, 100]; - state.reflections.push({ - x: target.x, - y: target.y, - age: 0, - maxAge: 1.25, - radius: random(8, 13), - probability: values[Math.floor(Math.random() * values.length)] - }); - } - - function updateEffects(dt) { - state.beams.forEach(beam => beam.age += dt); - state.beams = state.beams.filter(beam => beam.age < beam.maxAge); - state.reflections.forEach(r => { - r.age += dt; - r.radius += dt * 30; - }); - state.reflections = state.reflections.filter(r => r.age < r.maxAge); - } - - function drawGrid(p) { - ctx.save(); - ctx.strokeStyle = p.grid; - ctx.lineWidth = 1; - const spacing = 54; - for (let x = spacing; x < state.width; x += spacing) { - ctx.beginPath(); - ctx.moveTo(x, 0); - ctx.lineTo(x, state.height); - ctx.stroke(); - } - for (let y = spacing; y < state.height; y += spacing) { - ctx.beginPath(); - ctx.moveTo(0, y); - ctx.lineTo(state.width, y); - ctx.stroke(); - } - ctx.restore(); - } - - function drawRadar(p) { - const x = state.pointer.active ? state.pointer.x : state.width * 0.56; - const y = state.pointer.active ? state.pointer.y : state.height * 0.44; - ctx.save(); - ctx.strokeStyle = p.planeMuted; - ctx.lineWidth = 1; - for (const radius of [24, 48, 82]) { - ctx.globalAlpha = 0.24 - radius / 500; - ctx.beginPath(); - ctx.arc(x, y, radius, 0, Math.PI * 2); - ctx.stroke(); - } - ctx.globalAlpha = 0.2; - ctx.beginPath(); - ctx.moveTo(x - 100, y); - ctx.lineTo(x + 100, y); - ctx.moveTo(x, y - 100); - ctx.lineTo(x, y + 100); - ctx.stroke(); - ctx.restore(); - } - - function drawYagi(station, p) { - ctx.save(); - ctx.translate(station.x, station.y); - ctx.rotate(station.angle); - ctx.strokeStyle = p.plane; - ctx.fillStyle = p.plane; - ctx.lineWidth = 1.5; - ctx.lineCap = "round"; - ctx.shadowColor = p.beamGlow; - ctx.shadowBlur = 9; - - ctx.beginPath(); - ctx.moveTo(-30, 26); - ctx.lineTo(-30, -5); - ctx.stroke(); - - ctx.beginPath(); - ctx.moveTo(-32, 0); - ctx.lineTo(43, 0); - ctx.stroke(); - - for (const element of [ - { x: -27, length: 34 }, - { x: -12, length: 28 }, - { x: 2, length: 22 }, - { x: 14, length: 19 }, - { x: 25, length: 16 }, - { x: 35, length: 13 } - ]) { - ctx.beginPath(); - ctx.moveTo(element.x, -element.length / 2); - ctx.lineTo(element.x, element.length / 2); - ctx.stroke(); - } - - ctx.beginPath(); - ctx.arc(-12, 0, 3.2, 0, Math.PI * 2); - ctx.fill(); - ctx.restore(); - - ctx.save(); - ctx.font = "700 11px Inter, system-ui, sans-serif"; - const width = ctx.measureText(station.label).width + 14; - const x = station.x - width / 2; - const y = station.y + 32; - ctx.fillStyle = "rgba(6,18,10,.86)"; - ctx.strokeStyle = p.planeMuted; - roundedRect(x, y, width, 23, 6); - ctx.fill(); - ctx.stroke(); - ctx.fillStyle = p.plane; - ctx.textAlign = "center"; - ctx.textBaseline = "middle"; - ctx.fillText(station.label, station.x, y + 11.5); - ctx.restore(); - } - - function drawPlane(plane, p) { - ctx.save(); - ctx.translate(plane.x, plane.y); - ctx.rotate(plane.angle); - ctx.globalAlpha = clamp(Math.min(plane.age * 1.8, (plane.maxAge - plane.age) * 1.8), 0, 1); - ctx.strokeStyle = p.trail; - ctx.lineWidth = 1; - ctx.beginPath(); - ctx.moveTo(-plane.size * 4.5, 0); - ctx.lineTo(-plane.size * 1.4, 0); - ctx.stroke(); - - ctx.fillStyle = plane.hit > 0 ? p.reflection : p.plane; - ctx.shadowColor = plane.hit > 0 ? p.reflection : p.beamGlow; - ctx.shadowBlur = plane.hit > 0 ? 16 : 5; - const s = plane.size; - ctx.beginPath(); - ctx.moveTo(s * 1.65, 0); - ctx.lineTo(-s * 0.7, s * 0.34); - ctx.lineTo(-s * 0.15, s * 1.05); - ctx.lineTo(-s * 0.65, s * 1.08); - ctx.lineTo(-s * 1.35, s * 0.3); - ctx.lineTo(-s * 1.7, s * 0.28); - ctx.lineTo(-s * 1.12, 0); - ctx.lineTo(-s * 1.7, -s * 0.28); - ctx.lineTo(-s * 1.35, -s * 0.3); - ctx.lineTo(-s * 0.65, -s * 1.08); - ctx.lineTo(-s * 0.15, -s * 1.05); - ctx.lineTo(-s * 0.7, -s * 0.34); - ctx.closePath(); - ctx.fill(); - ctx.restore(); - } - - function drawBeam(beam, p) { - const progress = beam.age / beam.maxAge; - const alpha = Math.sin(progress * Math.PI); - ctx.save(); - ctx.globalAlpha = alpha; - ctx.strokeStyle = p.beamGlow; - ctx.lineWidth = 8; - ctx.shadowColor = p.beam; - ctx.shadowBlur = 15; - ctx.setLineDash([10, 6]); - ctx.lineDashOffset = -progress * 36; - ctx.beginPath(); - ctx.moveTo(beam.startX, beam.startY); - ctx.lineTo(beam.endX, beam.endY); - ctx.stroke(); - ctx.setLineDash([]); - ctx.strokeStyle = p.beam; - ctx.lineWidth = 1.8; - ctx.shadowBlur = 5; - ctx.beginPath(); - ctx.moveTo(beam.startX, beam.startY); - ctx.lineTo(beam.endX, beam.endY); - ctx.stroke(); - ctx.restore(); - } - - function drawReflection(r, p) { - const progress = r.age / r.maxAge; - const alpha = 1 - progress; - ctx.save(); - ctx.translate(r.x, r.y); - ctx.globalAlpha = alpha; - ctx.strokeStyle = p.reflection; - ctx.lineWidth = 1.6; - ctx.shadowColor = p.beam; - ctx.shadowBlur = 18; - for (const scale of [1, 1.65]) { - ctx.globalAlpha = alpha * (scale === 1 ? 1 : 0.55); - ctx.beginPath(); - ctx.arc(0, 0, r.radius * scale, 0, Math.PI * 2); - ctx.stroke(); - } - ctx.globalAlpha = alpha * 0.8; - const cross = r.radius * 1.25; - ctx.beginPath(); - ctx.moveTo(-cross, 0); - ctx.lineTo(cross, 0); - ctx.moveTo(0, -cross); - ctx.lineTo(0, cross); - ctx.stroke(); - ctx.globalAlpha = alpha; - ctx.fillStyle = p.reflection; - ctx.beginPath(); - ctx.arc(0, 0, 3.8, 0, Math.PI * 2); - ctx.fill(); - ctx.restore(); - - ctx.save(); - const label = `${r.probability}%`; - ctx.font = "800 12px Inter, system-ui, sans-serif"; - const width = ctx.measureText(label).width + 16; - const height = 25; - const x = r.x + r.radius + 12; - const y = r.y - r.radius - 17; - ctx.globalAlpha = clamp(alpha * 1.25, 0, 1); - ctx.fillStyle = "rgba(6,18,10,.91)"; - ctx.strokeStyle = p.plane; - ctx.shadowColor = p.beamGlow; - ctx.shadowBlur = 10; - roundedRect(x, y, width, height, 6); - ctx.fill(); - ctx.stroke(); - ctx.shadowBlur = 0; - ctx.fillStyle = p.reflection; - ctx.textAlign = "center"; - ctx.textBaseline = "middle"; - ctx.fillText(label, x + width / 2, y + height / 2); - ctx.restore(); - } - - function draw(staticOnly = false) { - const p = palette(); - ctx.clearRect(0, 0, state.width, state.height); - drawGrid(p); - drawRadar(p); - stations().forEach(station => drawYagi(station, p)); - if (staticOnly) return; - state.planes.forEach(plane => drawPlane(plane, p)); - state.beams.forEach(beam => drawBeam(beam, p)); - state.reflections.forEach(r => drawReflection(r, p)); - } - - function animate(timestamp) { - if (!state.running) return; - const dt = clamp((timestamp - state.lastFrame) / 1000 || 0, 0, 0.05); - state.lastFrame = timestamp; - - if (!state.visible || document.hidden) { - state.frameId = requestAnimationFrame(animate); - return; - } - - state.spawnTime += dt; - state.beamTime += dt; - const spawnInterval = coarsePointer.matches ? 2.2 : 1.15; - const beamInterval = coarsePointer.matches ? 3.3 : 1.8; - - if (state.spawnTime >= spawnInterval && state.planes.length < planeLimit()) { - state.spawnTime = 0; - state.planes.push(createPlane()); - } - - if (state.beamTime >= beamInterval && state.planes.length) { - state.beamTime = 0; - const target = beamTarget(); - if (target) createBeam(target); - } - - state.planes.forEach(plane => updatePlane(plane, dt)); - state.planes = state.planes.filter(plane => !expired(plane)); - updateEffects(dt); - draw(false); - state.frameId = requestAnimationFrame(animate); - } - - function start() { - cancelAnimationFrame(state.frameId); - resize(); - if (reducedMotion.matches) { - state.running = false; - draw(true); - return; - } - - state.running = true; - state.lastFrame = performance.now(); - if (!state.planes.length) { - const count = coarsePointer.matches ? 2 : 5; - for (let i = 0; i < count; i++) { - const plane = createPlane(); - plane.age = Math.random() * 2; - state.planes.push(plane); - } - } - state.frameId = requestAnimationFrame(animate); - } - - hero.addEventListener("pointermove", event => { - const rect = hero.getBoundingClientRect(); - state.pointer.x = clamp(event.clientX - rect.left, 0, rect.width); - state.pointer.y = clamp(event.clientY - rect.top, 0, rect.height); - state.pointer.active = true; - }, { passive: true }); - - hero.addEventListener("pointerleave", () => state.pointer.active = false); - addEventListener("resize", resize, { passive: true }); - document.addEventListener("visibilitychange", () => state.lastFrame = performance.now()); - reducedMotion.addEventListener("change", start); - - new ResizeObserver(() => { - resize(); - if (reducedMotion.matches) draw(true); - }).observe(hero); - - new IntersectionObserver(entries => { - state.visible = entries[0]?.isIntersecting ?? true; - state.lastFrame = performance.now(); - }, { threshold: 0.05 }).observe(hero); - - start(); -})(); diff --git a/website/_site/assets/social/kst4contest-og.png b/website/_site/assets/social/kst4contest-og.png deleted file mode 100644 index 17dd092..0000000 Binary files a/website/_site/assets/social/kst4contest-og.png and /dev/null differ diff --git a/website/_site/contact/index.html b/website/_site/contact/index.html deleted file mode 100644 index 6ed8adf..0000000 --- a/website/_site/contact/index.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - Contact | KST4Contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Contact

-

Contact

-

Get in touch, report issues or contribute to KST4Contest.

-
- -
-
-
-

GitHub Issues

-

Report bugs, request features or discuss technical problems.

- Open issues → -
- -
-

GitHub Repository

-

Browse source code, releases and documentation.

- Open repository → -
- - -
-
- - - - - - diff --git a/website/_site/download/index.html b/website/_site/download/index.html deleted file mode 100644 index b7de096..0000000 --- a/website/_site/download/index.html +++ /dev/null @@ -1,282 +0,0 @@ - - - - - Download KST4Contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Stable release

-

Download KST4Contest

-

- Choose the package for your operating system. Official builds are published through GitHub Releases, - and the required Java runtime is already included. -

- -
- Latest release on GitHub - All releases -
-
- -
-
-

Packages by platform

-

Choose the format that fits your system

-
- -
- -
-
🪟
- - -

Default choice

- - -

Windows

-

ZIP x64

-

Extract the complete archive, then start praktiKST.exe. No separate Java installation is required.

- - Download → -
- -
-
🐧
- - -

Default choice

- - -

Linux

-

Flatpak (.flatpakref)

-

Installs through Flatpak and can be updated through Flatpak or the desktop software centre.

- - Download → -
- -
-
🐧
- - - -

Linux

-

AppImage x86_64

-

Portable build without package installation. Make the downloaded file executable before the first launch.

- - Download → -
- -
-
📦
- - - -

Debian / Ubuntu

-

DEB amd64

-

Native package for Debian, Ubuntu and distributions based on them.

- - Download → -
- -
-
📦
- - - -

Fedora

-

RPM x86_64

-

Native package built for Fedora and compatible RPM-based systems.

- - Download → -
- -
-
📦
- - - -

Arch Linux

-

pkg.tar.zst

-

Release package for direct installation with pacman. AUR alternatives are described in the installation guide.

- - Download → -
- -
-
🍎
- - - -

macOS Apple Silicon

-

DMG arm64

-

Best-effort build for Apple Silicon Macs. The application is not currently notarized by Apple.

- - Download → -
- -
-
🍎
- - - -

macOS Intel

-

DMG x86_64

-

Best-effort build for Intel Macs. The application is not currently notarized by Apple.

- - Download → -
- -
-
📘
- - - -

Manual English

-

PDF

-

English PDF manual included with the Stable release.

- - Download → -
- -
-
📘
- - - -

Manual German

-

PDF

-

German PDF manual included with the Stable release.

- - Download → -
- -
-
- -
-
-

Choosing a package

-

Which file should I use?

-

- Windows users normally need the x64 ZIP package. On Linux, Flatpak is the practical choice when - updates should be managed through the desktop software centre or the Flatpak command line. The - AppImage is useful when a portable file is preferred, while DEB, RPM and Arch packages integrate - with their respective package managers. -

-

- macOS packages are provided for Apple Silicon and Intel systems on a best-effort basis. They are - not currently notarized by Apple. The installation guide covers the first launch, updates, the - Stable, Beta and Nightly channels, and the location of the settings directory. -

-
- Read the installation guide - Open the FAQ -
-
-
- -
-
-

Development and infrastructure

-

- KST4Contest is developed independently. If it is useful in your contest workflow and you want to - help cover continued development, testing and infrastructure costs, the support page explains - what project contributions are used for. -

-
- Support the project -
-
-
- - - - - - diff --git a/website/_site/faq/index.html b/website/_site/faq/index.html deleted file mode 100644 index 561fdb5..0000000 --- a/website/_site/faq/index.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - KST4Contest FAQ - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Frequently asked questions

-

- Answers about KST4Contest, ON4KST contest operation, downloads, - AirScout integration and supported platforms. -

-
- -
-
-

What is KST4Contest?

-

- KST4Contest is a contest-optimized ON4KST chat client for VHF, UHF and SHF ham radio contest operation. -

- -

Is KST4Contest a replacement for wtKST, KST2Me or KSTChat?

-

- KST4Contest follows a different approach. It is focused on contest workflow, priority candidates, - sked handling, AirScout support, log synchronization and operator decision support. -

- -

Which platforms are supported?

-

- KST4Contest provides release artifacts for Windows, Linux and macOS through GitHub Releases. -

- -

Does KST4Contest support AirScout?

-

- Yes. KST4Contest is designed to integrate AirScout-related workflow information into contest operation. -

- -

Where can I download KST4Contest?

-

- Official builds are available on the GitHub Releases page. -

-
-
- -
- - - - - - diff --git a/website/_site/features/airscout/index.html b/website/_site/features/airscout/index.html deleted file mode 100644 index 7c3fc96..0000000 --- a/website/_site/features/airscout/index.html +++ /dev/null @@ -1,223 +0,0 @@ - - - - - AirScout Integration - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Aircraft Scatter · since 1.26

-

AirScout Integration

-

Use AirScout AP predictions in candidate evaluation, the timeline and sked planning.

-
- -
-
-
✈️
- -

Airplane scatter in the operator workflow

-

Aircraft reflections can create short but valuable contact opportunities.

-

KST4Contest helps combine ON4KST chat activity with AirScout-based propagation awareness.

-

From candidate to sked decision

-

AirScout information can support the decision whether a candidate station should be called immediately, scheduled later or monitored for a better window.

- - - -

Keywords

-
- - AirScout - - airplane scatter - - aircraft scatter - - VHF contest - -
- - - -

Related features

-
- - - - - - - - - - - - - - - - - - - - Timeline View - - - - - - - - - - - - - - - - - - Priority Score System - - - - - - - - - - - - - - - - - - - - - - - - Sked Reminder - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/dual-chat/index.html b/website/_site/features/dual-chat/index.html deleted file mode 100644 index b536f97..0000000 --- a/website/_site/features/dual-chat/index.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - Dual Chat Categories - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

ON4KST Chat · since 1.26

-

Dual Chat Categories

-

Log in to two ON4KST categories and handle both message streams in one station list and interface.

-
- -
-
-
💬
- -

Two categories, one workflow

-

KST4Contest can operate with two ON4KST chat categories at once.

-

This is useful when contest activity spans VHF/UHF and microwave operation.

-

Less window switching

-

The operator can keep more information visible without constantly changing tools.

- - - -

Keywords

-
- - ON4KST - - dual chat - - microwave contest - -
- - - -

Related features

-
- - - - - - - - - - - - - - - - Priority Score System - - - - - - - - - - - - - - - - - - Log Synchronization - - - - - - - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/dx-cluster/index.html b/website/_site/features/dx-cluster/index.html deleted file mode 100644 index d8fa5ac..0000000 --- a/website/_site/features/dx-cluster/index.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - - DXCluster Server - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Radio Workflow · since 1.23

-

DXCluster Server

-

Send direction warnings as DX Cluster spots to compatible logging software when a usable QRG is known.

-
- -
-
-
📡
- -

More situational awareness

-

DXCluster information can support contest operators by adding another source of activity information.

-

Integrated workflow

-

The goal is not to open another isolated tool, but to connect activity information with the wider KST4Contest workflow.

- - - -

Keywords

-
- - DXCluster - - ham radio - - contest - -
- - - -

Related features

-
- - - - - - - - - - - - Log Synchronization - - - - - - - - - - - - - - - - - - - - - - - - - - Priority Score System - - - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/index.html b/website/_site/features/index.html deleted file mode 100644 index 3642f2f..0000000 --- a/website/_site/features/index.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - KST4Contest Features - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Features

-

Contest tools, not just chat windows.

-

- KST4Contest combines ON4KST chat, candidate scoring, AirScout workflow, - sked handling, log synchronization and operator decision support. -

-
- -
-
- - - - - -
-
📡
-

Radio Workflow

-

DXCluster Server

-

Send direction warnings as DX Cluster spots to compatible logging software when a usable QRG is known.

- Learn more → -
- - - -
-
🔄
-

Logger Integration

-

Log Synchronization

-

Import worked stations and current frequencies from supported contest loggers so filters and band information follow the log.

- Learn more → -
- -
-
⚡
-

Operator Speed

-

Macros and Variables

-

Build recurring chat messages from configurable text blocks and variables such as the current QRG or locator.

- Learn more → -
- -
-
🎯
-

Contest Workflow

-

Priority Score System

-

Rank active stations from known context such as direction, activity, band, QRG, AP and sked information.

- Learn more → -
- -
-
🔔
-

Sked Management

-

Sked Reminder

-

Store planned contacts and issue configurable chat messages plus local alerts before the agreed time.

- Learn more → -
- -
-
⏱️
-

Contest Awareness

-

Timeline View

-

Show AP-based priority candidates and scheduled contacts on a shared timeline.

- Learn more → -
- -
-
- - - - - - diff --git a/website/_site/features/log-sync/index.html b/website/_site/features/log-sync/index.html deleted file mode 100644 index 4e1e001..0000000 --- a/website/_site/features/log-sync/index.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - Log Synchronization - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Logger Integration · since 1.31

-

Log Synchronization

-

Import worked stations and current frequencies from supported contest loggers so filters and band information follow the log.

-
- -
-
-
🔄
- -

Connect chat and logging

-

Contest operation is faster when chat information and log state are connected.

-

KST4Contest can use logger information to improve workflow awareness.

-

Worked and band awareness

-

Log synchronization helps the client understand which stations and bands are relevant.

- - - -

Keywords

-
- - Win-Test - - UCXLog - - contest logger - -
- - - -

Related features

-
- - - - - - - - - - - - - - - - Priority Score System - - - - - - - - - - - - Dual Chat Categories - - - - - - - - - - - - - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/macros/index.html b/website/_site/features/macros/index.html deleted file mode 100644 index a2820d7..0000000 --- a/website/_site/features/macros/index.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - - Macros and Variables - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Operator Speed · since 1.0

-

Macros and Variables

-

Build recurring chat messages from configurable text blocks and variables such as the current QRG or locator.

-
- -
-
-
⚡
- -

Faster messages

-

Macros reduce repetitive typing during active contest operation.

-

More consistent operation

-

Variables help keep messages structured and reduce manual errors.

- - - -

Keywords

-
- - macros - - ON4KST - - operator workflow - -
- - - -

Related features

-
- - - - - - - - - - - - - - - - - - Sked Reminder - - - - - - - - - - Dual Chat Categories - - - - - - - - - - - - - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/priority-score/index.html b/website/_site/features/priority-score/index.html deleted file mode 100644 index 6deb04b..0000000 --- a/website/_site/features/priority-score/index.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - Priority Score System - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Contest Workflow · since 1.40

-

Priority Score System

-

Rank active stations from known context such as direction, activity, band, QRG, AP and sked information.

-
- -
-
-
🎯
- -

Why it matters

-

During active VHF, UHF and microwave contests, relevant stations can disappear quickly in busy ON4KST chat traffic.

-

The Priority Score System helps operators focus on stations that are more likely to be useful during contest operation.

-

Built for contest decisions

-

KST4Contest is not just a chat viewer. It evaluates contest-relevant context and helps turn chat activity into better operating decisions.

- - - -

Keywords

-
- - ON4KST - - VHF - - UHF - - SHF - - contest - - priority candidates - -
- - - -

Related features

-
- - - - - - - - - - - - - - - - - - - - Timeline View - - - - - - AirScout Integration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Sked Reminder - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/sked-reminder/index.html b/website/_site/features/sked-reminder/index.html deleted file mode 100644 index d5d63ed..0000000 --- a/website/_site/features/sked-reminder/index.html +++ /dev/null @@ -1,221 +0,0 @@ - - - - - Sked Reminder - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Sked Management · since 1.40

-

Sked Reminder

-

Store planned contacts and issue configurable chat messages plus local alerts before the agreed time.

-
- -
-
-
🔔
- -

Never lose important skeds

-

During active contests, it is easy to miss a planned contact while handling chat traffic, logging and band changes.

-

Sked Reminder keeps scheduled contacts visible.

-

Built for real contest pressure

-

The workflow supports time-critical operation where missing a few minutes can mean missing a QSO.

- - - -

Keywords

-
- - sked - - ON4KST - - contest reminder - -
- - - -

Related features

-
- - - - - - - - - - - - - - - - Priority Score System - - - - - - - - - - AirScout Integration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Timeline View - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/features/timeline/index.html b/website/_site/features/timeline/index.html deleted file mode 100644 index 4a7ca19..0000000 --- a/website/_site/features/timeline/index.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - Timeline View - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Contest Awareness · since 1.40

-

Timeline View

-

Show AP-based priority candidates and scheduled contacts on a shared timeline.

-
- -
-
-
⏱️
- -

Timing matters

-

Many VHF/UHF/SHF opportunities are short-lived.

-

The Timeline View helps operators see upcoming timing windows instead of keeping everything in mind manually.

-

Designed for fast awareness

-

The timeline supports quick decisions during busy contest operation.

- - - -

Keywords

-
- - timeline - - AP windows - - airplane scatter - -
- - - -

Related features

-
- - - - AirScout Integration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Priority Score System - - - - - - - -
- -
-
- -
- - - - - - diff --git a/website/_site/feed.xml b/website/_site/feed.xml deleted file mode 100644 index f722e70..0000000 --- a/website/_site/feed.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - KST4Contest News - https://kst4contest.hamradioonline.de/ - News and release updates for KST4Contest. - en - - - - AUR Packages now live of kst4contest - https://kst4contest.hamradioonline.de/news/2026-07-15-AUR-Packages/ - https://kst4contest.hamradioonline.de/news/2026-07-15-AUR-Packages/ - Wed, 15 Jul 2026 00:00:00 GMT - We now uploaded the packages of kst4contest to the AUR - - - - Hotfix Version 1.41.1 - https://kst4contest.hamradioonline.de/news/2026-07-08-hotfix-version-1-41-1/ - https://kst4contest.hamradioonline.de/news/2026-07-08-hotfix-version-1-41-1/ - Wed, 08 Jul 2026 00:00:00 GMT - Hotfix of a bug in Version 1.41 - - - - KST4Contest Website Launch - https://kst4contest.hamradioonline.de/news/2026-07-website-launch/ - https://kst4contest.hamradioonline.de/news/2026-07-website-launch/ - Tue, 07 Jul 2026 00:00:00 GMT - The new KST4Contest website is being built as a static, SEO-friendly product portal with GitHub-based documentation. - - - - \ No newline at end of file diff --git a/website/_site/index.html b/website/_site/index.html deleted file mode 100644 index 41e3f77..0000000 --- a/website/_site/index.html +++ /dev/null @@ -1,366 +0,0 @@ - - - - - KST4Contest – ON4KST Contest Client for VHF, UHF and SHF - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
- - - -
-

ON4KST contest workflow for 144 MHz and above

-

KST4Contest

- -

- ON4KST shows you the traffic. KST4Contest helps turn it into an operating - decision by combining chat, candidate prioritisation, sked planning, - AirScout data and logger integration in one desktop client. -

- -

- The available information is filtered, related to active stations and - presented in a contest-oriented workflow. The final decision still - belongs to the operator. -

- -
- Download KST4Contest - Read the manual - View source code -
-
- -
-
- - Functions sharing the same station context -
- -
- - -
- ✈️ AirScout Integration - Use AirScout AP predictions in candidate evaluation, the timeline and sked planning. -
- - - -
- 💬 Dual Chat Categories - Log in to two ON4KST categories and handle both message streams in one station list and interface. -
- - - -
- 📡 DXCluster Server - Send direction warnings as DX Cluster spots to compatible logging software when a usable QRG is known. -
- - - -
- KST4Contest Features - -
- - - -
- 🔄 Log Synchronization - Import worked stations and current frequencies from supported contest loggers so filters and band information follow the log. -
- - - -
- ⚡ Macros and Variables - Build recurring chat messages from configurable text blocks and variables such as the current QRG or locator. -
- - - - - - - - -
-
-
- -
-
-

The operating problem

-

The useful station is rarely the only station in the chat

-

- During an active contest, messages, sked requests, frequency information - and band changes arrive continuously. The task is to identify which part - of that traffic matters now, which candidate should be monitored and - which contact is better scheduled for later. -

-
- -
-
-

Observe

-

- Messages, locators, detected frequencies and known band activity are - assigned to stations across as many as two ON4KST chat categories. -

-
- -
-

Evaluate

-

- Direction, distance, worked status, NOT-QRV information, chat activity, - sked context and aircraft scatter data feed filters and candidate scores. -

-
- -
-

Act

-

- Candidates can be contacted, scheduled or monitored. Skeds remain - visible, while supported loggers and station interfaces receive the - information required for the next operating step. -

-
-
-
- -
-
-

Functions

-

One workflow, shared context

-

- The individual functions are not isolated tools. They use the same - station, message, band and timing information, so that a change in one - part of the workflow can also affect filters, priorities and reminders. -

-
- -
- - - - - - - - - -
-
🔄
-

Logger Integration

-

Log Synchronization

-

Import worked stations and current frequencies from supported contest loggers so filters and band information follow the log.

- Read how it works → -
- - - - - -
-
🔔
-

Sked Management

-

Sked Reminder

-

Store planned contacts and issue configurable chat messages plus local alerts before the agreed time.

- Read how it works → -
- - - -
-
- -
-
-

Limits

-

A priority score is not a propagation forecast

-

- KST4Contest can only evaluate the information it knows. Scores, AP - windows, filters and path profiles support the operator's decision; they - do not guarantee a contact. If the input data is incomplete or outdated, - the result can be incomplete or outdated as well. -

- -
- Explore the functions - Read the technical details -
-
-
- -
-
-

Project status

-

Stable for operation, Nightly for testing

-

- KST4Contest is open-source software. The current stable release is the - normal choice for contest operation. Nightly builds follow ongoing - development and are useful when a particular fix or feature needs - testing. A few minutes before a contest is not the ideal time to discover - what changed. -

- -
- Download the stable release - Development status - Support development -
-
-
- -
- - - - - - - - diff --git a/website/_site/kst4ContestVersionInfo.xml b/website/_site/kst4ContestVersionInfo.xml deleted file mode 100644 index 4f9304f..0000000 --- a/website/_site/kst4ContestVersionInfo.xml +++ /dev/null @@ -1,538 +0,0 @@ - - - - 1.411 - 1.41.1 - - - Score of Top-Priority Candidates in the user section -- Broadcast Messages (To ALL Station in Contest) in seperate Window - https://github.com/praktimarc/kst4contest/releases/tag/v1.41.1 - - - nothing - - - - Cyclic update of own name in chat to actual QRG - 2024-02 - open - - - Acoustic warnings - 2023-12 - added - - - Airscout support - 2023-03 - added - - - cyclic beacon messages in public chat - 2023-03 - added - - - - - -stations like ol7c-7 and ol7c-2 will not be marked as worked if only "ol7c" -is in the log. Need to interprete that. May ignore suffix starting with "-" - solved - - - -worked callsigns table is updated only once after connected to chat -Should be available directly after program started. -But Reset works all time - open - - - feature request: language-specific strings, maybe based to an xml file - - open - - - feature request: Macros - - added - - - feature request: - Automatic elimination of calls already connected from the log - - added - - - feature request: - Limitation of users beyond a certain QRB - - added - - - feature request: - User division for QTF perhaps settable based on the antenna lobe - - added - - - feature request: - Notification of new incoming users - added - - - feature request: - Evidence of a call which was written but not responded to. - - added - - - feature request: - direction based reachable-warnings: - if the chatclient detects a realised qso between two stations which both must have - directed their beams to my station, there should be an instant warning to me for - working at least one of the stations at the detected qrg - open - - - feature request: - implement ASShowpath message to airacout; - by doubleclicking a callsign in the chatmember list, the path and plane state should be - provided by airscout - open - - - feature request: - make chatlines copyable to the clipboard... - open - - - feature request: - adding an activity detection for sensing if another chatmembers alive-state - added - - - On sql error close the connection to make a clean exit - open - - - SETNAME /MYQRG in options menu doesnt work - solved - - - Disconnect button does not work (DL5ZK) - solved - - - Password-wrong error not displayed (DO5SA) - solved - - - /CQ isnt written on own PMs - solved - - - rightclick-textsnippets arent available in cq-table - solved - - - - 1.41.1 - 2026-07-08 - Release v1.41.1 - - Hotfix of Bug #56 - - - - - 1.41.0 - 2026-07-01 - Release v1.41.0 - - Score of Top-Priority Candidates in the user section -- Broadcast Messages (To ALL Station in Contest) in seperate Window - Migration to Github -- Band and Frequency Detection per Chatmember — KST4Contest identifies which bands or frequencies a station appears active or reachable on based on chat data. This information is integrated into the display and prioritization. -- Band Alert — If a logged station could be of interest on other locally active bands, KST14Contest can alert the user. -- Sked Reminder ALERT — New reminder function for planned Skeds to ensure that agreed contacts are not forgotten during contest operation. -- Skedfail Button — Failed Skeds can be marked; this allows the station to be handled differently in terms of score and workflow. -- Win-Test SKED Push via UDP — Skeds can be passed to Win-Test via a LOCKSKED/ADDSKED/UNLOCKSKED sequence. This feature is configurable in the preferences and disabled by default. -- Win-Test Broadcast Defaults and SKed Workflow — Improved broadcast addresses, frequency formats, mode selection, and notes including locator/azimuth. -- PSTRotator Interface — KST4Contest received an interface to PSTRoter to better integrate antenna direction and rotator workflow. -- QSO /-Callsign Sniffer — Callsigns or QSO-relevant information can be detected and utilized for further workflow. -- Chat History at Startup — Historical chat data can be loaded upon startup, allowing the client to quickly gain relevant context for scoring, activity, and station identification. -- Station Map / Map View — New map view with station markers, your own location, locator/Maidenhead reference, connection line, and antenna/beam representation. -- Local Leaflet /-TileProxy Backend — The map function utilizes embedded Leaflet resources and a local TileProxy approach, making the map more portable and independent. -- Maidenhead /-Grid Overlay — The map can display locator/grid information; recently added Grid-Square coloring. -- Path /-Terrain /-Horizon Profile — Map documentation describes a path profile with terrain, Fresnel, and horizon information for the selected link. -- Tropo /-AS Reachability Filters — New filters and sorting were added for Tropospheric reachability, AirScoop availability, large locator fields, and priority. -- Reachability Band Selector — Added a band selection for range/Troposphere calculations. -- 4-Char Locator Filter — Locator evaluations can be reduced to 4-character fields; this improves overview and performance. -- KST Testserver Support — A KST server test server was added into the Source. -@praktimarc and @Rsclub22 - - [BUG] -- [BUG] Programmstart kann ohne selektieren keine Nachrichten senden -- KST4Contest crashes after to many messages or to much RAM Usage -- Scaling Problem at 1280x800 screen resolution - - - - 1.40 - 2026-02-16 - Much changes and fixes - -- win-test support (not deactivable yet, beta) -- QSO sniffer which filters changable callsigns lists messages to your pm window -- Chatmember Score system. Each chatmember gets a score depending to antenna direction, activity time, - activity msgcount, positive signals, active bands, active frequencies, his sked direction (degrees), - self handed rate, sked-made-rate and some others -- Chatmember Band and frequency recognition: now we list all active bands of each other chatmember -- Band alert for logged stations -- Sked reminder ALERT with automatic messages in 2+1 / 5+2+1 / 10+5+2+1 minutes -- PSTRotator interface -- AirPlane Timeline -- Skedfail button in furtherinfo panel -- Wintest logsynch interface can now be activated and deactivated in the preferences -- load chat history on startup - - -- added save option: ServerDNS / Port -- added save option: activate/deactivate pstRotator interface -- added save option: activate/deactivate wintest interface -- added save option: callsign sniffer -- added save option: boolean GUI_darkModeActiveByDefault = false -- added AP notes at the internal DX cluster spots -- Generic Autoanswer fires maximum once in 45 seconds per rx callsign - - -- Userlist sort automatically on new member signon -- Posonpill-messages now kills only exactly one Client instance (bugreport 9A2HM) -- Crash of wtkst by disconnection of kst4Contest -- wtKST crashes when kst4contest is running (many reporters) -- wintest: logged per band excludes pre worked band (bugreport SM6VTZ) -- PSTRotator SOCKET Close on DISCONNECT BUTTON works now -- AirScout Map had not been updated (bugreport SM0RJV) -- QTFDefault had been not saved correctly (bugreport SM0RJV) -- Show path in AS button worked only with fixed server Strings (bugreport 9A2HM) -- Version number had been displayed wrong -- suffixes like /p, -2, etc. problem now fixed everywhere -- Dark mode: passing for qrg fields fix - - -- No more date display. Not needed. Saving space, only time is important - - - - 1.31 - 2025-12-13 - Much changes and a hotfix - -- win-test support (not deactivable yet, beta) -- pstRotator support (not deactivable yet, beta) -- airScout fix (calculations depends to cpu load now) -- QSO sniffer - - -- DNS from www.on4kst.info to www.on4kst.org (hotfix, now configurable in preferences) - - -- Endless loop in error case lets freeze the client -- PSTRotator SOCKET Close on DISCONNECT BUTTON -- Dark mode: passing for qrg fields fix - - - - - 1.266 - 2025-10-03 - Airscout interface did not work with multi-signons - nothing - nothing - -Fixed by using raw callsign (without -2 suffix etc.) when communicating with AirScout. -Thank you very much for testing this, Kreso 9A2HM! - - - - - 1.265 - 2025-09-28 - Direction buttons stay now colored, if activated - nothing - nothing - The buttons stay now colored, if activated - - - - 1.264 - 2025-08-02 - Changed the callsign recognition pattern for Simplelogfile - nothing - nothing - -Callsigns like S53CC, S51A etc. are now correctly marked as worked in SimpleLogFile.txt. -(bugreport Boris, S53CC) - - - - - 1.263 - 2025-06-08 - Airscout communication and Loginname - nothing - -Only entries with QRB lower than max-QRB are sent to AirScout in 60s intervals (was 12s for all). - - -- AS communication message count hugely reduced -- Name in chat is now saveable -- Fixed AS client name (was hard-wired to "KST") -73 / DO5AMF - - - - - 1.262 - 2025-05-21 - Freezes caused by getting messages before user login should be fixed now - nothing - nothing - -ON4KST delivers messages of stations not yet logged in. That caused a freeze at the message -processing engine which is now fixed. - - - - - 1.26 - 2025-05 - Login to multiple Channels via single signon / spend some colors - -1. UI: Dark mode. Switch in "Window -> use dark mode" -2. Usage of two Chatcategories at the same time -3. opposite station multi-callsign login-tagging -73 / DO5AMF - - -- Coloring mechanic of the software. Modify colors via css by yourself... - - -- Station tagging fixed completely - - - - - 1.251 - 2025-02 - BUGFIX of 1.25, tnx Steve Clements! - -- Steve spotted a problem in udp broadcast spot info reading, its now fixed! -73 / DO5AMF - - - - Station tagging - - - - 1.25 - 2025-02 - Wishlist-time - -- New configuration Tab: Messagehandling (auto-answering, CQ qrg auto-answer) -- Coloured lines: new pm rows appear in red, fade rainbow-like to white over 30s (tnx Gianluca) -73 / DO5AMF - - - -- Users with suffixes like "-2 and -70" are now correctly marked as worked - - - - - 1.24 - 2024-11 - Wishlist-time - -- Button to show qrz.com profile of a selected station -- Button to show qrzcq.com profile of a selected station - - - - - - - 1.23 - 2024-10 - DXCluster Server is now implemented - -- DXCluster Server (tnx OMAAO): KST4Contest now provides a DXCluster server to feed - your log client with station-reachable warnings. - - - - - - - 1.22 - 2024-05 - Increase usability, fixed AS button - - Variables (tnx OMAAO): MYLOCATORSHORT, MYQRGSHORT, QRZNAME - - Sendtext-field focus on callsign click - -- Worked-station-filter (tnx Gianluca): filter is now live -- Chatters list sorting by QRB (tnx Alessandro): fixed to numeric sort -- Airscout showpath button now maximizes AS and shows the path - - - - - 1.21 - 2024-04 - Increase usability - - -- Window sizes and divider positions are now stored and restored on next startup -- Filters section is now a flowpane for lower resolutions - - - - - - 1.2 - 2024-04 - Increase usability - -- Selectable bands -- Unworkable tags for each callsign per band -- QTF-Arrow on the "show path in AS" button - - - - - - - 1.1 - 2024-03 - Increased workflow - -- Reachable warning function -- Variables FIRSTAP and SECONDAP for predefined texts -- Marking new connected stations (bold) and away-state (brackets) -- Activity-timer since last message of a chatter - - - QRB/QTF info in pm-window - -- Behaviour of messagefilter-radiobutton corrected (tnx Gian) -- Error sending macros on selected stations in pm window (tnx Gian) - - - boot sound - - - 1.0 - 2024-02 - First stable release - -- audio notification support -- update-available warning -- changelog displaying -- known-bugs displaying -- message filters for selected station -- stationlist-filters (show by qtf / textstring, hide by qrb, qtf, workedstate) -- 10 macros (textsnippets available by hitting strg+numberkey) - - - - - - - 0.9 - 2024-02 - Now the chat is disconnectable without closing it - - - disconnect-button, Textsnippets in CQ Window, "/CQ" at click on own sendtexts, -setname "qrg" works now - - - - 0.8 - 2023-10 - savesettings function and disconnect function added. MYCALL-Highlighting fixed - savesettings function, disconnect function - - MYCALL-Highlighting - - - - 0.7 - 2023-07 - Internal database for worked stations, shortcut and textsnippet editor - database, shortcut-editor, textsnipped-editor - - - - - - 0.6 - 2023-07 - Added periodically sent beacon function - beacon to public channel - - - - - - 0.5 - 2023-02 - Airscout interface, UDP interfaces for worked-station data and TRX info, shortcuts - Airscout-interface, packetreceiver for ucxlog, n1mm, qartest - - - - - - 0.4 - 2022-12 - Worked info by logfile via universal pattern matching logfile interpreter - simple-logfile - - - - - - 0.3 - 2022-10 - Added a GUI, chat was text based only - Graphical user interface - - - - - - 0.2 - 2022-10 - Pattern matching system for frequency information, frequency collection per chatmember - frequency-extraction for every callsign - - - - - - 0.15 - 2022-09 - Researched the Chatprotocol and developed the base communication with the chatserver - - - - - - - 0.1 - 2022-09 - Primary architecture of the chat, message bus system for handling the message queues - - - - - - diff --git a/website/_site/legal-notice/index.html b/website/_site/legal-notice/index.html deleted file mode 100644 index b5d1703..0000000 --- a/website/_site/legal-notice/index.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - Legal Notice | KST4Contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Legal Notice

-

Legal Notice

-

Information according to § 5 DDG.

-
- -
-
-

Provider

-

- Marc Fröhlich
- Rheingoldstr. 6
- 68199 Mannheim
- Germany -

- -

Contact

-

- Email: praktimarc+kst4contest@gmail.com -

- -

Responsible for content

-

- Marc Fröhlich
- Rheingoldstr. 6
- 68199 Mannheim
- Germany -

- -

Project

-

- KST4Contest is an open-source ON4KST contest client. - Source code and releases are available on - GitHub. -

-
-
- - - - - - diff --git a/website/_site/manual/assets/as_plane_feed_1.png b/website/_site/manual/assets/as_plane_feed_1.png deleted file mode 100644 index 08e28e5..0000000 Binary files a/website/_site/manual/assets/as_plane_feed_1.png and /dev/null differ diff --git a/website/_site/manual/assets/as_plane_feed_2.png b/website/_site/manual/assets/as_plane_feed_2.png deleted file mode 100644 index be35ea1..0000000 Binary files a/website/_site/manual/assets/as_plane_feed_2.png and /dev/null differ diff --git a/website/_site/manual/assets/as_plane_feed_3.png b/website/_site/manual/assets/as_plane_feed_3.png deleted file mode 100644 index 65f47d5..0000000 Binary files a/website/_site/manual/assets/as_plane_feed_3.png and /dev/null differ diff --git a/website/_site/manual/assets/as_plane_feed_4.png b/website/_site/manual/assets/as_plane_feed_4.png deleted file mode 100644 index 74ffa8f..0000000 Binary files a/website/_site/manual/assets/as_plane_feed_4.png and /dev/null differ diff --git a/website/_site/manual/assets/client_settings_window_logsync.png b/website/_site/manual/assets/client_settings_window_logsync.png deleted file mode 100644 index 41e782e..0000000 Binary files a/website/_site/manual/assets/client_settings_window_logsync.png and /dev/null differ diff --git a/website/_site/manual/assets/client_settings_window_station.png b/website/_site/manual/assets/client_settings_window_station.png deleted file mode 100644 index 312fa19..0000000 Binary files a/website/_site/manual/assets/client_settings_window_station.png and /dev/null differ diff --git a/website/_site/manual/assets/dxlog_net_logsync.png b/website/_site/manual/assets/dxlog_net_logsync.png deleted file mode 100644 index feba0ef..0000000 Binary files a/website/_site/manual/assets/dxlog_net_logsync.png and /dev/null differ diff --git a/website/_site/manual/assets/qartest_logsync.png b/website/_site/manual/assets/qartest_logsync.png deleted file mode 100644 index 8da59bd..0000000 Binary files a/website/_site/manual/assets/qartest_logsync.png and /dev/null differ diff --git a/website/_site/manual/assets/qrg_buttons.png b/website/_site/manual/assets/qrg_buttons.png deleted file mode 100644 index 5e5ea1d..0000000 Binary files a/website/_site/manual/assets/qrg_buttons.png and /dev/null differ diff --git a/website/_site/manual/assets/ucxlog_logsync.png b/website/_site/manual/assets/ucxlog_logsync.png deleted file mode 100644 index 93c34b3..0000000 Binary files a/website/_site/manual/assets/ucxlog_logsync.png and /dev/null differ diff --git a/website/_site/manual/assets/update_window.png b/website/_site/manual/assets/update_window.png deleted file mode 100644 index 49b693f..0000000 Binary files a/website/_site/manual/assets/update_window.png and /dev/null differ diff --git a/website/_site/manual/de/airscout-integration/index.html b/website/_site/manual/de/airscout-integration/index.html deleted file mode 100644 index 30d7bf2..0000000 --- a/website/_site/manual/de/airscout-integration/index.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

AirScout-Integration

-

AirScout-Integration

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

AirScout (von DL2ALF) ist ein Programm zur Erkennung von Flugzeugen für den Aircraft-Scatter-Betrieb. KST4Contest ist eng mit AirScout integriert und zeigt reflektierbare Flugzeuge direkt in der Benutzerliste an.

-
-

Aircraft Scatter ermöglicht sehr weitreichende Verbindungen auf VHF und höher – auch für Stationen mit geringer Höhe über NN oder ungünstigen topografischen Verhältnissen.

-
-
-

AirScout herunterladen

-

Download von AirScout:

- -
-

Flugzeugdaten-Feeds (ADSB)

-

Öffentliche Flugzeugdaten-Feeds im Internet sind oft unzuverlässig und begrenzt nutzbar. Eine empfohlene Alternative bietet OV3T (Thomas) mit einem dedizierten ADSB-Feed-Dienst:

- -

Für diesen Dienst ist ein Account erforderlich. Bitte eine Spende für Thomas in Betracht ziehen – der Server-Betrieb ist nicht kostenlos!

-
-

AirScout einrichten

-

Schritt 1: ADSB-Feed in AirScout konfigurieren

-
    -
  1. AirScout starten.
    2. -
  2. In den AirScout-Einstellungen den OV3T-Feed-Account eintragen (Benutzername, Passwort, URL).
    3. -
-

AirscoutSchritt1 -AirscoutSchritt2

-
    -
  1. Verbindung testen.
    2. -
-

Schritt 2: UDP-Kommunikation für KST4Contest aktivieren

-

In AirScout die UDP-Schnittstelle aktivieren:

-
    -
  • In den AirScout-Einstellungen die entsprechende Checkbox aktivieren (nur eine Checkbox notwendig).
    • -
  • Standard-Ports nicht ändern, wenn kein besonderer Grund vorliegt.
    • -
-

Schritt 3: KST4Contest-Einstellungen

-

In den KST4Contest-Preferences → AirScout Settings:

-
    -
  • AirScout-Kommunikation aktivieren
    • -
  • IP und Port auf Standardwerte lassen (sofern nicht geändert)
    • -
-

AirscoutSchritt3{ width=85% }

-
-

Kommunikation zwischen KST4Contest und AirScout (ab v1.263)

-

Verbesserung in v1.263: KST4Contest sendet nur noch Stationen an AirScout, deren QRB (Entfernung) kleiner als das eingestellte Maximum-QRB ist. Das Abfrageintervall wurde von 12 Sekunden auf 60 Sekunden verlängert.

-

Vorteile:

-
    -
  • Deutlich weniger Berechnungsaufwand für AirScout
    • -
  • Deutlich weniger Nachrichtenverkehr
    • -
  • Das Tracking-Problem mit dem „Show Path in AirScout"-Button wurde dadurch deutlich verbessert
    • -
  • Weniger Rechenleistung insgesamt
    • -
-

Außerdem: Der Name des KST4Contest-Clients und des AirScout-Servers war früher hartcodiert (KST und AS). Ab v1.263 werden die in den Preferences eingetragenen Namen verwendet.

-
-

Mehrere KST4Contest-Instanzen und AirScout

-
-

Achtung: Wenn mehrere KST4Contest-Instanzen gleichzeitig betrieben werden und bei beiden die AirScout-Kommunikation aktiviert ist, antwortet AirScout an beide Instanzen.

-
-

Das ist unproblematisch, wenn:

-
    -
  • Beide Instanzen denselben Locator verwenden, oder
    • -
  • Beide Instanzen unterschiedliche Login-Rufzeichen haben.
    • -
-

Andernfalls kann es zu fehlerhaften AP-Daten kommen.

-
-

AP-Spalte in der Benutzerliste

-

Nach der Einrichtung erscheint in der Benutzerliste eine AP-Spalte mit bis zu zwei reflektierbaren Flugzeugen pro Station.

-

Beispiel-Darstellung:

- - - - - - - - - - - - - - - - - -
StationAP-Info
DF9QX2 Planes: 0 min / 0 min, je 100%
F5DYD2 Planes: 14 min / 31 min, je 50%
-

Die AP-Informationen sind auch im Privatnachrichten-Fenster verfügbar.

-

Die Prozentzahl gibt das Reflexionspotenzial an (Größe des Flugzeugs, Höhe, Entfernung).

-
-

AP-Variablen in Nachrichten

-

Die Flugzeugdaten können direkt in Nachrichten eingefügt werden:

-
    -
  • FIRSTAP → z. B. a very big AP in 1 min
    • -
  • SECONDAP → z. B. Next big AP in 9 min
    • -
-

Details: Makros und Variablen

-
-

„Show Path in AirScout"-Button

-

In der Benutzerliste gibt es einen Button mit einem Pfeil, der die Richtung (QTF) zur ausgewählten Station anzeigt. Ein Klick maximiert AirScout und zeigt den Pfad mit reflektierbaren Flugzeugen zum ausgewählten Gesprächspartner.

- -
-
- - - - - - diff --git a/website/_site/manual/de/benutzeroberflaeche/index.html b/website/_site/manual/de/benutzeroberflaeche/index.html deleted file mode 100644 index edaec1e..0000000 --- a/website/_site/manual/de/benutzeroberflaeche/index.html +++ /dev/null @@ -1,211 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Benutzeroberfläche

-

Benutzeroberfläche

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

Verbinden mit dem Chat

-
    -
  1. Im Einstellungsfenster eine Chat-Kategorie auswählen (z. B. 144 MHz VHF, 432 MHz UHF, …).
    2. -
  2. Connect-Button klicken.
    3. -
  3. Warten bis die Verbindung aufgebaut ist.
    4. -
-
-

Trennen und Neu-Verbinden ist nur über das Einstellungsfenster möglich. Es empfiehlt sich daher, das Einstellungsfenster geöffnet zu lassen.

-
-
-

Hauptfenster-Überblick

-

Das Hauptfenster besteht aus mehreren Bereichen:

-

PM-Fenster (oben links)

-

Zeigt alle empfangenen Privatnachrichten sowie abgefangene öffentliche Nachrichten, die das eigene Rufzeichen enthalten. Neue Nachrichten erscheinen in Rot und faden alle 30 Sekunden über Gelb bis Weiß ab.

-

Benutzerliste (Chat Members)

-

Die zentrale Tabelle aller aktuell aktiven Chat-Nutzer. Spalten (je nach Konfiguration):

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SpalteInhalt
CallRufzeichen der Station
NameName aus dem Chat-Namenfeld
LocMaidenhead-Locator
QRBEntfernung in km
QTFRichtung in Grad
QRGAutomatisch erkannte Frequenz
APAirScout-Flugzeugdaten (wenn aktiv)
Band-FarbenWorked/NOT-QRV-Status pro Band
-

Sortierung: Klick auf Spaltenköpfe. QRB-Sortierung arbeitet numerisch (ab v1.22 korrigiert).

-

Sendfeld

-

Texteingabe für ausgehende Nachrichten. Nach Klick auf ein Rufzeichen in der Benutzerliste erhält das Sendfeld automatisch den Fokus – sofort tippen ohne Doppelklick (ab v1.22).

-

MYQRG-Feld

-

Rechts neben dem Sendbutton. Zeigt die aktuelle eigene QRG an, kann auch manuell eingetragen werden.

-

MYQTF-Feld (für v1.3)

-

Eingabefeld für die aktuelle Antennenrichtung. Wird für die geplante MYQTF-Variable verwendet.

-
-

Filter

-

Die Filter-Leiste (ab v1.21 als Flowpane für kleine Bildschirme):

-
    -
  • Show only QTF: Richtungsfilter aktivieren (Buttons N/NE/E/… oder Grad-Eingabe)
    • -
  • Show only QRB [km] <=: Entfernungsfilter aktivieren (Toggle-Button)
    • -
  • Hide Worked [Band]: Gearbeitete Stationen pro Band ausblenden (je ein Toggle pro Band)
    • -
  • Hide NOT-QRV [Band]: NOT-QRV-markierte Stationen pro Band ausblenden
    • -
-
-

Stationsinfo-Panel (Further Info)

-

Rechts unten: Zeigt alle Nachrichten einer ausgewählten Station (CQ-Nachrichten und PMs in einem Panel). Ein Nachrichtenfilter lässt sich über den Standard-Filter in den Preferences vorbelegen.

-

Hier können auch Sked-Erinnerungen aktiviert werden.

-
-

Prioritätsliste

-

Zeigt die vom Score-Service berechneten Top-Kandidaten. Aktualisiert sich automatisch im Hintergrund basierend auf Richtung, Entfernung und AP-Verfügbarkeit.

-
-

Cluster & QSO der anderen

-

Separates Fenster (kann miniaturisiert werden). Zeigt den Kommunikationsfluss zwischen anderen Stationen – interessant in ruhigeren Phasen.

-
-

Menü

-

Window

-
    -
  • Use Dark Mode (ab v1.26): Dunkles Farbschema aktivieren/deaktivieren.
    • -
-
-

Fenstergrößen und Divider

-

Ab v1.21 werden beim Klick auf „Save Settings" auch Fenstergrößen und Divider-Positionen aller Panels in der Konfigurationsdatei gespeichert und beim nächsten Start wiederhergestellt.

-

Bei Problemen mit der Darstellung: Konfigurationsdatei löschen → KST4Contest erstellt neue Standardwerte.

-
-

Tipps zur Bedienung

-
    -
  • Einstellungsfenster geöffnet lassen: Schneller Zugriff auf Beacon-Aktivierung/Deaktivierung.
    • -
  • Rechtsklick in der Benutzerliste: Öffnet das Snippet-Menü und weitere Aktionen (QRZ.com-Profil, NOT-QRV-Tags setzen).
    • -
  • Enter aus dem Chat heraus: Wenn im Sendfeld Text steht, sendet Enter direkt – auch wenn der Fokus woanders liegt.
    • -
  • Beacon stoppen: Beim Scannen von Frequenzen den Beacon ausschalten, damit der Chat nicht mit Meldungen überflutet wird.
    • -
- -
-
- - - - - - diff --git a/website/_site/manual/de/changelog/index.html b/website/_site/manual/de/changelog/index.html deleted file mode 100644 index f68ca0e..0000000 --- a/website/_site/manual/de/changelog/index.html +++ /dev/null @@ -1,346 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Changelog

-

Changelog

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

Versionsverlauf von KST4Contest / PraktiKST.

-
-

letzter Changelog bitte aus GitHub entnehmen. Der bisherige Changelog

-

v1.41

-

Stationskarte, Performance, Reaktionsfähiges UI

-

Neu:

-
    -
  • Stationskarte: Interaktive OpenStreetMap-Karte zeigt die geografische Position aller aktiven Chatmember. Enthält Stationsmarker, Antennen-Kegel, Verbindungslinie zur ausgewählten Station, Maidenhead-Raster-Overlay und ein Wegprofil-Diagramm mit Geländehöhen-Analyse (Fresnel-Zonen, Horizonterkennung). Geländedaten aus Copernicus GLO-30, Open-Meteo API oder Offline-DEM-Import. Aircraft-Scatter-Weganalyse integriert. Funktioniert in AppImage und Flatpak ohne externe CDN-Verbindung (lokaler Tile-Proxy, eingebettetes Leaflet.js).
    • -
-

Geändert:

-
    -
  • Nachrichten-Tabellen-Limit auf 30.000 erhöht: Chat- und Nachrichtentabellen sind auf 30.000 Einträge begrenzt. Ältere Nachrichten werden automatisch verworfen, was die Performance bei mehrtägigem Contest-Betrieb stabil hält.
    • -
  • Bildschirmgerechte Fenstergröße: Beim Start wird das Hauptfenster auf den aktuellen Bildschirm angepasst. Wenn KST4Contest zuletzt auf einem größeren Monitor betrieben wurde, wird das Fenster automatisch verkleinert. Das UI-Layout ist kompakter und reaktionsfähiger auf kleineren Bildschirmen.
    • -
-
-

v1.40 (2026-02-16)

-

Großes Feature-Release: Score-System, AP-Timeline, Win-Test, PSTRotator

-

Neu:

-
    -
  • Chatmember Score-System: Jeder Chatmember erhält automatisch eine Prioritätsbewertung anhand von Antennenrichtung, Aktivitätszeit, Nachrichtenanzahl, aktiven Bändern, Frequenzen, Sked-Richtung und anderen Faktoren. Die Top-Kandidaten werden in einer eigenen Liste hervorgehoben.
    • -
  • AP-Timeline: Für jeden möglichen AP-Ankunftsminuten-Slot werden bis zu 4 hochbewertete Stationen angezeigt, die erreichbar wären. Bevorzugt werden APs mit dem höchsten Potenzial, nicht die schnellste Ankunft. Stationen, auf die die eigene Antenne nicht zeigt, werden transparent dargestellt.
    • -
  • Win-Test-Unterstützung (ab v1.31 als Beta, jetzt vollständig konfigurierbar): Log-Synchronisation, Frequenzauswertung und Sked-Übergabe via UDP vollständig integriert. In den Preferences aktivier-/deaktivierbar.
    • -
  • PSTRotator-Interface (ab v1.31 als Beta, jetzt vollständig konfigurierbar): Aktualisierung der Rotatorposition direkt aus KST4Contest. In den Preferences aktivier-/deaktivierbar.
    • -
  • QSO-Sniffer: Nachrichten von konfigurierbaren Rufzeichen-Listen werden automatisch in das PM-Fenster weitergeleitet.
    • -
  • Band-Alert bei gearbeiteten Stationen: Wenn eine Station geloggt wird, erscheint ein Hinweis, wenn diese Station ein weiteres Band aktiv hat, auf dem man selbst ebenfalls QRV ist.
    • -
  • Sked-Erinnerungs-ALERT: Pro Chatmember kann ein Sked-Alarm mit automatischen Nachrichten in konfigurierbaren Intervallen (2+1 / 5+2+1 / 10+5+2+1 Minuten vor dem Sked) eingerichtet werden, plus akustische und optische Benachrichtigung.
    • -
  • Chat-Historie beim Start laden: Beim Verbindungsaufbau wird die Serverhistorie geladen, um aktive Chatmember und letzte Nachrichten sofort sichtbar zu machen.
    • -
  • Skedfail-Button: Im FurtherInfo-Panel kann ein Sked-Misserfolg für einen Chatmember markiert werden, was dessen Score senkt.
    • -
-

Geändert:

-
    -
  • AP-Notizen in DX-Cluster-Spots integriert.
    • -
  • Scrolling der Chatmember-Tabelle folgt automatisch der aktuellen Nachrichtenauswahl.
    • -
  • Generic Auto-Antwort und QRG-Auto-Antwort senden max. einmal pro 45 Sekunden pro Rufzeichen (verhindert Spam-Schleifen).
    • -
  • Speicherbare Einstellungen erweitert: ServerDNS/Port, PSTRotator-Interface, Win-Test-Interface, Callsign-Sniffer, Dark-Mode-Standard.
    • -
  • Datum in der Chat-Tabelle entfernt (nur Uhrzeit verbleibt – spart Platz).
    • -
-

Behoben:

-
    -
  • Benutzerliste wird jetzt bei jedem Neu-Login automatisch sortiert.
    • -
  • Posonpill-Nachrichten beenden jetzt nur genau eine Client-Instanz (nicht alle und nicht wtKST).
    • -
  • wtKST: Absturz bei KST4Contest-Trennung behoben.
    • -
  • Mehrere Probleme mit Rufzeichen-Suffixen wie /p, -2 etc. behoben.
    • -
  • QTFDefault wurde nicht korrekt gespeichert → behoben.
    • -
  • AirScout-Watchlist (ASWATCHLIST) wurde nicht korrekt aktualisiert → behoben.
    • -
  • Dark Mode: QRG-Felder wurden nicht vollständig angezeigt → behoben.
    • -
  • Versionsnummer-Anzeige korrigiert.
    • -
-
-

v1.31 (2025-12-13)

-

Win-Test + PSTRotator Beta, QSO-Sniffer, DNS-Hotfix

-

Neu:

-
    -
  • Win-Test-Unterstützung (Beta, noch nicht deaktivierbar): Log-Synchronisation und Frequenzauswertung.
    • -
  • PSTRotator-Unterstützung (Beta, noch nicht deaktivierbar).
    • -
  • QSO-Sniffer: Nachrichten von konfigurierbaren Rufzeichen werden ins PM-Fenster weitergeleitet.
    • -
-

Geändert:

-
    -
  • DNS-Server geändert: Von www.on4kst.info auf www.on4kst.org (Hotfix). Der DNS-Server ist ab sofort in den Preferences änderbar.
    • -
-

Behoben:

-
    -
  • Endlosschleife im Fehlerfall friert den Client ein → behoben.
    • -
-
-

v1.266 (2025-10-03)

-

AirScout-Fix für Rufzeichen mit Suffix

-

Behoben:

-
    -
  • AirScout-Interface funktionierte nicht, wenn das Login-Rufzeichen einen Suffix enthielt (z. B. 9A1W-2). AirScout kann mit diesem Format nicht umgehen – es wird jetzt nur noch das Basis-Rufzeichen ohne Suffix an AirScout übergeben.
    • -
-

(Fehler gemeldet und getestet von 9A2HM / Kreso – herzlichen Dank!)

-
-

v1.265 (2025-09-28)

-

Richtungs-Buttons bleiben aktiviert eingefärbt

-

Behoben:

-
    -
  • Richtungs-Buttons (N / NE / E usw.) behalten jetzt ihre Farbe, wenn sie aktiviert sind, sodass der Aktivierungsstatus auf einen Blick erkennbar ist.
    • -
-
-

v1.264 (2025-08-02)

-

Simplelogfile: Rufzeichen-Erkennung verbessert

-

Behoben:

-
    -
  • Rufzeichen wie S53CC, S51A usw. wurden in der SimpleLogFile-Auswertung nicht als gearbeitet markiert → Erkennungsmuster verbessert.
    • -
-

(Fehler gemeldet von Boris, S53CC – danke!)

-
-

v1.263 (2025-06-08)

-

AirScout-Kommunikation und Login-Name

-

Geändert:

-
    -
  • AirScout-Kommunikation grundlegend überarbeitet: Nur noch Stationen mit QRB < max-QRB werden an AirScout gesendet.
    • -
  • Abfrage-Intervall von 12 Sekunden auf 60 Sekunden erhöht.
    • -
  • Deutlich weniger Berechnungsaufwand und Nachrichtenverkehr → Stabileres AirScout-Tracking.
    • -
  • Name des AS-Clients und AS-Servers ist jetzt aus den Preferences konfigurierbar (war vorher hartcodiert auf „KST" / „AS").
    • -
-

Behoben:

-
    -
  • „Track in AirScout"-Button war sehr träge → durch neue Kommunikationslogik deutlich verbessert.
    • -
  • Name im Chat ist jetzt speicherbar (Fehler behoben).
    • -
  • Visuelle Korrekturen vor und nach dem Login.
    • -
  • Fehler behoben, der von 9A2HM (Kreso) gemeldet wurde.
    • -
-
-

v1.262 (2025-05-21)

-

Freeze-Fix bei vorzeitiger Nachrichtenlieferung

-

Behoben:

-
    -
  • ON4KST liefert manchmal Nachrichten, bevor der Login abgeschlossen ist. Das verursachte Fehler in der Nachrichtenverarbeitung → jetzt behoben.
    • -
-
-

v1.26 (2025-05)

-

Multi-Channel-Login und Dark Mode

-

Neu:

-
    -
  • Dark Mode: Umschaltbar über Window → Use Dark Mode.
    • -
  • Multi-Channel-Login: Gleichzeitiger Login in zwei Chat-Kategorien.
    • -
  • Opposite Station Multi-Callsign Login-Tagging: Unterstützung für Stationen mit mehreren Rufzeichen.
    • -
-

Geändert:

-
    -
  • Farbgebungs-Mechanismus überarbeitet: Farben können jetzt über CSS angepasst werden.
    • -
-

Behoben:

-
    -
  • Stationsmarkierung komplett überarbeitet und korrekt gestellt.
    • -
-
-

v1.251 (2025-02)

-

Bugfix für UDP-Broadcast-Spot-Info

-

Behoben:

-
    -
  • Problem beim Lesen von UDP-Broadcast-Spot-Informationen behoben (gemeldet von Steve Clements – danke!).
    • -
  • Stationsmarkierung (erneut verbessert).
    • -
-
-

v1.25 (2025-02)

-

Wunschliste umgesetzt

-

Neu:

-
    -
  • Neuer Einstellungs-Tab: Messagehandling -
      -
    • Auto-Antwort auf eingehende Nachrichten konfigurierbar.
      • -
    • Automatische Antwort mit eigener CQ-QRG, wenn jemand danach fragt.
      • -
    • Konfigurierbarer Standard-Filter für das Userinfo-Fenster (für Gianluca :-) ).
      • -
    -
    • -
  • Farbige PM-Zeilen: Neue Privatnachrichten erscheinen rot und faden alle 30 Sekunden über Gelb bis Weiß ab (Idee von IU3OAR, Gianluca).
    • -
-

Behoben:

-
    -
  • Stationen mit Suffixen wie „-2" und „-70" wurden nicht als gearbeitet markiert → werden jetzt ignoriert, Station wird korrekt markiert.
    • -
-
-

v1.24 (2024-11)

-

Wunschliste + DX-Cluster-Spots

-

Neu:

-
    -
  • Button zum Öffnen des QRZ.com-Profils der ausgewählten Station.
    • -
  • Button zum Öffnen des QRZ-CQ-Profils der ausgewählten Station.
    • -
  • DX-Cluster-Server-Integration: Richtungs-Warnungen werden als Spots an das Logprogramm gesendet (wenn QRG bekannt).
    • -
-

(Zusätzlich wurden Farbgebungen der PM-Zeilen hinzugefügt – tnx Gianluca)

-
-

v1.23 (2024-10)

-

Integrierter DX-Cluster-Server

-

Neu:

-
    -
  • KST4Contest enthält jetzt einen integrierten DX-Cluster-Server.
    • -
  • Generiert DX-Cluster-Spots und sendet sie an das Logprogramm, wenn eine Richtungs-Warnung ausgelöst und eine QRG bekannt ist.
    • -
  • Spotter-Rufzeichen muss sich vom Contest-Rufzeichen unterscheiden (für korrekte Filterung im Logprogramm).
    • -
-

(Idee von OM0AAO, Viliam Petrik – danke!)

-
-

v1.22 (2024-05)

-

Usability-Verbesserungen und AirScout-Button-Fix

-

Neu:

-
    -
  • Neue Variablen (tnx OM0AAO, Viliam Petrik): -
      -
    • MYLOCATORSHORT
      • -
    • MYQRGSHORT
      • -
    • QRZNAME
      • -
    -
    • -
-

Geändert:

-
    -
  • Sendfeld-Fokus: Nach Klick auf Rufzeichen in der Benutzerliste erhält das Sendfeld sofort den Fokus – kein Doppelklick notwendig (tnx Gianluca).
    • -
-

Behoben:

-
    -
  • Worked-Station-Filter ist jetzt live-aktiv: Gearbeitete Stationen verschwinden sofort nach Aktivierung des Filters (tnx Gianluca).
    • -
  • QRB-Sortierung war lexikografisch → jetzt numerisch (tnx Alessandro Murador).
    • -
  • AirScout-„Show Path"-Button: Klick maximiert AirScout und zeigt den Pfad korrekt an.
    • -
-
-

v1.21 (2024-04)

-

Usability-Verbesserungen

-

Geändert:

-
    -
  • Fenstergrößen und Divider-Positionen werden beim Klick auf „Save Settings" in der Konfigurationsdatei gespeichert und beim Start wiederhergestellt.
    • -
  • Filter-Bereich als Flowpane → bessere Darstellung auf kleineren Bildschirmen.
    • -
-
-

v1.2 (2024-04)

-

Bandselektion und NOT-QRV-Tags

-

Neu:

-
    -
  • Bandselektion: In den Preferences auswählbar, welche Bänder aktiv sind. Nur für gewählte Bänder erscheinen Buttons und Felder in der UI. Speichern und Neustart erforderlich.
    • -
  • NOT-QRV-Tags pro Station und Band: Stationen können für jedes Band als „nicht QRV" markiert werden. Kombinierbar mit dem Userlist-Filter.
    • -
  • QTF-Pfeil: Der „Show path in AS"-Button zeigt jetzt einen Pfeil mit dem QTF der ausgewählten Station an.
    • -
-
-

Frühere Versionen

-

v1.1

-

Erste öffentlich veröffentlichte Version. Grundfunktionen:

-
    -
  • Worked-Markierung via Simplelogfile und UDP
    • -
  • Sked-Richtungs-Hervorhebung
    • -
  • QRG-Erkennung
    • -
  • Text-Snippets und Shortcuts
    • -
  • AirScout-Interface (erste Version)
    • -
  • Intervall-Beacon
    • -
  • PM-Abfang für öffentliche Nachrichten mit eigenem Rufzeichen
    • -
  • Update-Hinweis-Dienst
    • -
-
-

Geplante Features

-
    -
  • MYQTF-Variable (eigene Antennenrichtung als Text)
    • -
  • Lebensdauer für den Worked-Status (automatisches Zurücksetzen) ✅ Umgesetzt in v1.40 (3-Tage-Lebensdauer, kein manuelles Zurücksetzen mehr nötig)
    • -
  • Filterung des „Cluster & QSO der anderen"-Fensters auf eigenes QTF
    • -
  • Weitere Topografie-basierte Berechnungen für die Richtungswarnung
    • -
- -
-
- - - - - - diff --git a/website/_site/manual/de/dx-cluster-server/index.html b/website/_site/manual/de/dx-cluster-server/index.html deleted file mode 100644 index 4b7f709..0000000 --- a/website/_site/manual/de/dx-cluster-server/index.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Integrierter DX-Cluster-Server

-

Integrierter DX-Cluster-Server

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

Ab Version 1.23 enthält KST4Contest einen integrierten DX-Cluster-Server. Dieser sendet Spots direkt an das Logprogramm, wenn eine Richtungs-Warnung ausgelöst wird.

-

(Idee von OM0AAO, Viliam Petrik – danke!)

-
-

Wozu dient der integrierte DX-Cluster-Server?

-

Wenn KST4Contest erkennt, dass eine Station aus der eigenen Richtung ein Sked anfragt und gleichzeitig eine QRG bekannt ist, wird automatisch ein DX-Cluster-Spot generiert und an den Cluster-Client des Logprogramms gesendet.

-

Das Logprogramm zeigt den Spot in der Bandkarte an. Ein Klick auf den Spot stellt Frequenz und Mode des Transceivers direkt ein – ohne manuelles Eintippen.

-
-

Einrichtung

-

In KST4Contest

-

In den Preferences → DX-Cluster-Server-Einstellungen:

-
    -
  1. Port des internen Servers eintragen (z. B. 7300 oder 8000 – muss mit dem Logprogramm übereinstimmen).
    2. -
  2. Spotter-Rufzeichen eintragen – unbedingt ein anderes Rufzeichen als das Contest-Rufzeichen verwenden! -
      -
    • Grund: Logprogramme filtern Spots, die vom eigenen Rufzeichen stammen, als „gearbeitet" heraus. Wenn der Spotter dasselbe Rufzeichen hat, werden die Spots nicht angezeigt.
      • -
    -
    3. -
  3. Angenommene MHz eintragen: Bei Frequenzangaben wie „.205" im Chat muss KST4Contest entscheiden, ob 144.205, 432.205 oder 1296.205 gemeint ist. Bei Einband-Contests einfach die entsprechende Bandmitte eintragen. Vollständige Frequenzangaben wie „144.205" oder „1296.338" im Chat werden immer korrekt erkannt.
    4. -
-

In UCXLog

-
    -
  • Verbindung zu einem DX-Cluster-Server konfigurieren: -
      -
    • Host: 127.0.0.1 (oder IP des KST4Contest-Computers)
      • -
    • Port: Wie in KST4Contest konfiguriert
      • -
    • Passwort: kann leer bleiben
      • -
    -
    • -
  • Über die Schaltfläche „Send a test message to your log" kann die Verbindung getestet werden.
    • -
-

In N1MM+

-

Ähnliche Einstellungen:

-
    -
  • Host: 127.0.0.1 (oder IP des KST4Contest-Computers)
    • -
  • Port: Wie in KST4Contest konfiguriert
    • -
-
-

Funktionsweise

-

Ein Spot wird generiert, wenn beide Bedingungen erfüllt sind:

-
    -
  1. Eine Richtungs-Warnung wurde ausgelöst (Station macht ein Sked in die eigene Richtung).
    2. -
  2. QRG der Station ist bekannt (aus dem Chat ausgelesen oder manuell eingetragen).
    3. -
-

Der generierte Spot enthält:

-
    -
  • Rufzeichen der Station
    • -
  • Frequenz
    • -
  • Spotterzeit
    • -
-

Das Logprogramm kann den Spot dann in der Bandkarte anzeigen und den TRX per Mausklick auf die Frequenz abstimmen.

-
-

Multi-Computer-Setup

-

Wenn KST4Contest auf einem separaten Computer läuft (nicht auf dem Log-Computer):

-
    -
  • Host im Logprogramm: IP des KST4Contest-Computers (nicht 127.0.0.1)
    • -
  • Entspricht der Konfiguration der QSO-UDP-Broadcast-Pakete (siehe Log-Synchronisation)
    • -
-
-

Getestete Logprogramme

-
    -
  • UCXLog ✓
    • -
  • N1MM+ ✓
    • -
-

Weitere Testergebnisse sind willkommen – bitte per E-Mail an DO5AMF melden.

- -
-
- - - - - - diff --git a/website/_site/manual/de/funktionen/index.html b/website/_site/manual/de/funktionen/index.html deleted file mode 100644 index 57f8456..0000000 --- a/website/_site/manual/de/funktionen/index.html +++ /dev/null @@ -1,295 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Funktionen

-

Funktionen

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

Übersicht aller Hauptfunktionen von KST4Contest.

-
-

Sked-Richtungs-Hervorhebung

-

Eine der Kernfunktionen: Wenn eine Station ein Sked in die eigene Richtung sendet, wird sie in der Benutzerliste grün und fett hervorgehoben.

-

Wie funktioniert das?

-

Die Berechnung basiert auf folgender Logik:

-
    -
  • Wenn Station A eine Sked-Anfrage an Station B sendet, wird angenommen, dass A ihre Antenne auf B ausrichtet.
    • -
  • Wenn die daraus resultierende Richtung von A zur eigenen Station innerhalb des halben Öffnungswinkels der eigenen Antenne liegt, wird A hervorgehoben.
    • -
-

Beispiel (Öffnungswinkel 69°, Halbwinkel 34,5°):

- - - - - - - - - - - - - - - - - - - - - - - - - -
SituationErgebnis für DO5AMF in JN49
Sked von F5FEN → DM5M✅ Hervorhebung (F5FEN zeigt Richtung DM5M, das liegt nahe JN49)
Sked von DM5M → F5FEN✅ Hervorhebung (DM5M antwortet in Richtung F5FEN)
F1DBN ist unbeteiligt❌ Keine Hervorhebung
DO5AMF/P (anderer Standort)❌ Keine Hervorhebung für Sked-Antwort
-

Die Berechnung berücksichtigt keine topografischen Wegberechnungen – das ist eine bewusste Vereinfachung. Möglicherweise wird das in einer späteren Version ergänzt.

-
-

Konfiguration: Konfiguration – Antennen-Öffnungswinkel

-
-
-

Sked-Richtungs-Spots (Integrierter DX-Cluster)

-

Ab v1.23: Richtungs-Warnungen werden als DX-Cluster-Spots an das Logprogramm weitergeleitet, wenn eine QRG bekannt ist. Details: DX-Cluster-Server.

-
-

QRG-Erkennung (QRG Reading)

-

KST4Contest verarbeitet jede Chat-Nachricht und extrahiert automatisch Frequenzangaben. Diese werden in der Benutzerliste in der QRG-Spalte angezeigt.

-

Erkannte Formate: 144.205, 432.088, .205 (mit konfigurierter Bandannahme), etc.

-

Nutzen: Ohne nachzufragen kann man direkt auf die QRG einer Station schauen und entscheiden, ob eine Verbindung möglich ist.

-
-

Worked-Markierung

-

Gearbeitete Stationen werden in der Benutzerliste visuell markiert – pro Band. Grundlage ist die Log-Synchronisation via UDP oder Simplelogfile.

-

Vor jedem Contest die Datenbank zurücksetzen: Konfiguration – Worked Station Database Settings.

-
-

NOT-QRV-Tags (ab v1.2)

-

Wenn eine Station mitteilt, dass sie auf einem bestimmten Band nicht QRV ist, kann dies manuell markiert werden:

-
    -
  1. Station in der Benutzerliste auswählen.
    2. -
  2. Rechtsklick → NOT-QRV für das entsprechende Band setzen.
    3. -
-

Diese Tags werden in der internen Datenbank gespeichert und bleiben nach einem Neustart von KST4Contest erhalten. Zurücksetzen über die Einstellungen möglich.

-

Nutzen: Verhindert wiederholte Sked-Anfragen auf Bändern, auf denen die Station nicht QRV ist – schont sowohl die eigenen Nerven als auch die der Gegenstation.

-
-

Richtungsfilter (Direction Filter)

-

Zeigt in der Benutzerliste nur Stationen an, die sich in einer bestimmten Richtung befinden. Aktivierbar über die Buttons N / NE / E / SE / S / SW / W / NW oder durch manuelle Eingabe von Grad.

-

Sinnvoll: Während man CQ in eine bestimmte Richtung ruft, nur Stationen in dieser Richtung anzeigen.

-
-

Entfernungsfilter (Distance Filter)

-

Stationen jenseits einer maximalen Entfernung ausblenden. Schaltfläche „Show only QRB [km] <=" ist ein Toggle-Button.

-
-

Worked- und NOT-QRV-Filter

-

Toggle-Buttons (einer pro Band) zum Ausblenden bereits gearbeiteter Stationen und/oder NOT-QRV-markierter Stationen. Der Filter wirkt sofort ohne manuelles Neu-Aktivieren (ab v1.22 live).

-
-

Farbige PM-Zeilen (ab v1.25)

-

Neue Privatnachrichten erscheinen in Rot. Die Farbe wechselt alle 30 Sekunden über Gelb bis Weiß – wie ein Regenbogen-Fade. So ist auf einen Blick erkennbar, wie aktuell eine Nachricht ist.

-

(Idee von IU3OAR, Gianluca Costantino – danke!)

-
-

PM-Abfang (Catching Personal Messages)

-

Manche Nutzer senden Direktnachrichten versehentlich öffentlich, z. B.:

-
(DM5M) pse ur qrg
-
-

KST4Contest erkennt solche Nachrichten, die das eigene Rufzeichen enthalten, und sortiert sie automatisch in die Privatnachrichten-Tabelle ein. So gehen keine Nachrichten verloren.

-
-

Multi-Channel-Login (ab v1.26)

-

Gleichzeitiger Login in zwei Chat-Kategorien (z. B. 144 MHz und 432 MHz). Beide Chats werden parallel überwacht.

-
-

Dark Mode (ab v1.26)

-

Aktivierbar über: Window → Use Dark Mode

-

Für individuelle Farbanpassungen: CSS-Datei bearbeiten (Pfad in den Programmunterlagen).

-
-

Opposite Station Multi-Callsign Login-Tagging (ab v1.26)

-

Unterstützung für Stationen, die mit mehreren Rufzeichen gleichzeitig im Chat aktiv sind (z. B. Expedition-Setups).

-
-

QRZ.com und QRZ-CQ Profil-Buttons (ab v1.24)

-

Für ausgewählte Stationen in der Benutzerliste gibt es direkte Buttons, um das QRZ.com-Profil und das QRZ-CQ-Profil im Browser zu öffnen.

-
-

Sked-Erinnerungen mit ALERT (ab v1.40)

-

Für jeden Chatmember kann ein Sked-Erinnerungsdienst mit automatischen Nachrichten aktiviert werden. Konfigurierbare Intervallmuster:

-
    -
  • 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.
    • -
-

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.

-

Aktivierung: FurtherInfo-Panel der entsprechenden Station.

-
-

QSO-Sniffer (ab v1.31)

-

Der QSO-Sniffer überwacht den Chat auf Nachrichten von einer konfigurierbaren Rufzeichen-Liste und leitet diese automatisch in das PM-Fenster weiter. So gehen keine relevanten Nachrichten im allgemeinen Chat-Rauschen unter.

-

Konfiguration: Konfiguration – Sniffer-Einstellungen

-
-

Win-Test-Integration (ab v1.31, vollständig ab v1.40)

-

KST4Contest unterstützt Win-Test vollständig als Logprogramm:

-
    -
  • 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.
    • -
-

Details zur Konfiguration: Konfiguration – Win-Test-Netzwerk-Listener

-
-

PSTRotator-Interface (ab v1.31, vollständig ab v1.40)

-

KST4Contest kann die Antennenrichtung direkt über PSTRotator steuern. Wenn in der Benutzerliste eine Station ausgewählt wird, kann der Rotator automatisch auf den QTF zur ausgewählten Station gedreht werden.

-

Konfiguration: Konfiguration – PSTRotator-Einstellungen

-
-

Band-Alert bei neuen QSOs (ab v1.40)

-

Wenn eine Station geloggt wird, prüft KST4Contest automatisch, ob diese Station im Chat weitere aktive Bänder angezeigt hat, auf denen man selbst ebenfalls QRV ist. Falls ja, erscheint ein Hinweis-Alert, damit keine Multi-Band-Möglichkeit übersehen wird.

-
-

Worked-Tag-Lebensdauer (ab v1.40)

-

Gearbeitete Stationen werden nach 3 Tagen automatisch aus der Datenbank entfernt. Ein manuelles Zurücksetzen der Worked-Datenbank vor jedem Contest ist damit nicht mehr zwingend notwendig – die Datenbank hält sich selbst aktuell.

-
-

Chatmember Score-System / Prioritätsliste (ab v1.40)

-

KST4Contest berechnet automatisch eine Prioritätsbewertung für jeden aktiven Chatmember. Der Score setzt sich zusammen aus:

-
    -
  • Antennenrichtung der Gegenstation (zeigt sie auf mich?)
    • -
  • QRB (Entfernung)
    • -
  • Aktivitätszeit und Nachrichtenanzahl
    • -
  • Aktive Bänder und Frequenzen
    • -
  • AP-Verfügbarkeit (AirScout)
    • -
  • Sked-Richtung
    • -
  • Sked-Erfolgsrate und Skedfail-Markierungen
    • -
-

Die Top-Kandidaten werden in einer eigenen Prioritätsliste hervorgehoben und helfen, im Contest-Stress die wichtigsten Stationen nicht zu übersehen.

-

Stationen, bei denen ein Sked gescheitert ist, können über den Skedfail-Button im FurtherInfo-Panel markiert werden – das senkt ihren Score vorübergehend.

-
-

AP-Timeline (ab v1.40)

-

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:

-
    -
  • Bevorzugt werden APs mit dem höchsten Reflexionspotenzial (nicht unbedingt die schnellste Ankunft).
    • -
  • Stationen, auf die die eigene Antenne nicht zeigt, werden transparent dargestellt.
    • -
-

So kann der Contest-Operator auf einem Blick sehen, welche Stationen wann und über welche Flugzeuge erreichbar sein werden.

-
-

Intervall-Beacon

-

Automatische CQ-Meldungen im öffentlichen Kanal in konfigurierbarem Intervall. Empfohlene Verwendung mit der Variable MYQRG für aktuelle Frequenzangabe. Details: Konfiguration – Beacon Settings.

-
-

Simplelogfile

-

Dateibasierte Log-Auswertung per Regex. Details: Log-Synchronisation.

-
-

Cluster & QSO der anderen

-

Ein separates Fenster zeigt den QSO-Fluss zwischen anderen Stationen. Besonders interessant in ruhigeren Nacht-Stunden während des Contests, wenn weniger Verkehr herrscht.

-

Dieses Fenster kann miniaturisiert werden, wenn es nicht benötigt wird. Zukünftig geplant: Filterung auf Stationen im ausgewählten QTF.

-
-

Stationskarte (ab v1.41)

-

Eine interaktive OpenStreetMap-Karte zeigt die geografische Position aller aktiven Chatmember.

-

Funktionen:

-
    -
  • Stationsmarker mit Rufzeichen-Labels, farblich nach Aktivität und Sked-Status
    • -
  • Antennen-Kegel für die eigene Station
    • -
  • Verbindungslinie zur aktuell ausgewählten Station
    • -
  • Maidenhead-Raster (QRA-Locator-Gitter als Overlay)
    • -
  • Wegprofil-Diagramm: Geländehöhen-Querschnitt zwischen eigener und ausgewählter Station, inklusive Fresnel-Zonen-Analyse und Horizonterkennung
    • -
  • Mehrere Terrainquellen: Copernicus GLO-30 (hochauflösendes DEM), Open-Meteo API, synthetischer Fallback und Offline-DEM-Import für den Betrieb ohne Internetverbindung
    • -
  • Aircraft-Scatter-Weganalyse verknüpft mit den Geländedaten
    • -
-

Die Karte funktioniert in gepackten Umgebungen (AppImage, Flatpak) ohne Zugriff auf externe CDNs: Die Kartenkacheln werden über einen lokalen Tile-Proxy abgerufen, die Leaflet.js-Bibliothek ist in der Anwendung eingebettet.

-
-

Optimierte Nachrichtenverarbeitung / 30.000-Nachrichten-Limit (ab v1.41)

-

Die internen Chat- und Nachrichtentabellen sind auf 30.000 Einträge begrenzt. Ältere Nachrichten werden automatisch verworfen, sobald das Limit erreicht wird. Damit bleiben Speicherverbrauch und Darstellungsperformance auch bei mehrtägigen Contest-Betrieb stabil.

-
-

Bildschirmgerechte Fenstergröße (ab v1.41)

-

Beim Programmstart berechnet KST4Contest eine bildschirmgerechte Startgröße für das Hauptfenster:

-
    -
  • Die gespeicherte Fenstergröße aus der letzten Session wird verwendet – aber niemals größer als der aktuelle Bildschirm.
    • -
  • Wenn KST4Contest zuletzt auf einem größeren Monitor betrieben wurde, wird das Fenster automatisch auf die aktuelle Anzeige verkleinert.
    • -
  • Das UI-Layout ist kompakter und reaktionsfähiger auf kleineren Bildschirmen.
    • -
-

Damit werden unbrauchbare, abgeschnittene Fenster beim Wechsel zwischen Geräten oder Monitoren verhindert.

- -
-
- - - - - - diff --git a/website/_site/manual/de/home/index.html b/website/_site/manual/de/home/index.html deleted file mode 100644 index d01c0fe..0000000 --- a/website/_site/manual/de/home/index.html +++ /dev/null @@ -1,249 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

KST4Contest – Handbuch

-

KST4Contest – Handbuch

-
-

English version | Du liest gerade die deutsche Version

-
-

KST4Contest ist ein Desktop-Client für den ON4KST-Chat, der für den Contest-Betrieb auf den VHF-, UHF- und SHF-Bändern entwickelt wurde. Er verbindet Chat, Stationsauswahl, Sked-Planung, Aircraft-Scatter-Daten und die Anbindung an weitere Programme in einer gemeinsamen Arbeitsoberfläche.

-

Entwickelt wird KST4Contest von DO5AMF (Marc Fröhlich), Operator bei DM5M und (seit Mai 2025) DN9APW (Philipp Wagner). Der Quellcode ist öffentlich auf GitHub verfügbar.

-
-

Wozu braucht man einen eigenen ON4KST-Client?

-

Der ON4KST-Chat liefert während eines Contests eine große Menge an Informationen: aktive Stationen, Locator, Frequenzen, Sked-Anfragen und Hinweise auf aktuelle Aktivität. Das eigentliche Problem besteht nicht darin, diese Daten zu sehen. Man muss daraus rechtzeitig die nächste sinnvolle Verbindung ableiten.

-

KST4Contest wertet die verfügbaren Informationen aus, ordnet sie und stellt sie in einem contestgerechten Arbeitsablauf dar. Dabei werden unter anderem Antennenrichtung, Entfernung, bekannte Bänder und Frequenzen, bereits gearbeitete Stationen, Chat-Aktivität und Aircraft-Scatter-Zeiten berücksichtigt.

-

Das Programm entscheidet jedoch nicht, welches QSO tatsächlich möglich ist. Der Prioritätsscore, die AP-Timeline und die verschiedenen Hervorhebungen sind Entscheidungshilfen. Die endgültige Beurteilung bleibt beim Operator – schon deshalb, weil auch ein recht überzeugender Computerbildschirm noch keine Funkverbindung herstellt.

-
-

Was KST4Contest im Contest unterstützt

-
    -
  • -

    Chat beobachten und einordnen: KST4Contest kann zwei ON4KST-Chat-Kategorien gleichzeitig darstellen. Nachrichten, Frequenzangaben und bekannte Bandaktivitäten werden den jeweiligen Stationen zugeordnet.

    -
    • -
  • -

    Relevante Stationen herausfiltern: Richtungs-, Entfernungs-, Worked- und NOT-QRV-Filter reduzieren die Benutzerliste auf die Stationen, die für den aktuellen Betriebszustand tatsächlich interessant sind.

    -
    • -
  • -

    Kandidaten priorisieren: Das Score-System bewertet aktive Chatmember anhand mehrerer bekannter Kriterien. Die derzeit relevantesten Kandidaten erscheinen zusätzlich in einer eigenen Prioritätsliste.

    -
    • -
  • -

    Skeds vorbereiten und im Blick behalten: Sked-Erinnerungen, automatische Vorwarnungen und die AP-Timeline helfen dabei, vereinbarte Verbindungen nicht zwischen Chat, Log und laufendem CQ-Betrieb zu verlieren.

    -
    • -
  • -

    Aircraft Scatter einbeziehen: Über die AirScout-Schnittstelle werden geeignete Flugzeuge und erwartete Reflexionszeiten in die Stationsbewertung und Zeitplanung übernommen.

    -
    • -
  • -

    Log und Funkstation anbinden: KST4Contest synchronisiert gearbeitete Stationen und Frequenzinformationen mit unterstützten Logprogrammen. Zusätzlich stehen Schnittstellen zu Win-Test, PSTRotator und ein integrierter DX-Cluster-Server zur Verfügung.

    -
    • -
  • -

    Stationen und Funkwege darstellen: Die Stationskarte zeigt aktive Chatmember, Locator-Felder, Antennenrichtungen und den Weg zur ausgewählten Station. Für ausgewählte Verbindungen kann außerdem ein Geländeprofil berechnet werden.

    -
    • -
-

Die Funktionen greifen ineinander. Eine erkannte Frequenz kann beispielsweise einem aktiven Band zugeordnet werden, der Worked-Status stammt aus dem Log, Aircraft-Scatter-Daten ergänzen die zeitliche Bewertung und der daraus berechnete Score beeinflusst die Prioritätsliste. Fehlende oder veraltete Eingangsdaten können deshalb auch das Ergebnis beeinflussen.

-
-

Voraussetzungen

-

Für die Anmeldung ist ein registrierter ON4KST-Account erforderlich. Registrierung und Login sind über die offizielle ON4KST-Anmeldeseite erreichbar.

-

Die offizielle Sprache im ON4KST-Chat ist Englisch. Das gilt auch für Nachrichten an Stationen aus dem eigenen Land. Übliche Amateurfunk-Abkürzungen wie pse, agn, qrg, dir, rrr, tnx oder 73 sind dabei normal und meistens erheblich schneller als ausformulierte Prosa.

-

Download, unterstützte Betriebssysteme und Installationswege sind im Kapitel Installation beschrieben.

-
-

Versionsstand dieses Handbuchs

-

Dieses Handbuch beschreibt die stabile Version v1.41.1.

-

Funktionen oder Änderungen, die nur im aktuellen Entwicklungsstand enthalten sind, werden ausdrücklich als Nightly / v1.42 gekennzeichnet. Fehlt eine solche Kennzeichnung, bezieht sich die Beschreibung auf die stabile Version.

- -

Für einen Contest ist grundsätzlich die stabile Version zu empfehlen. Nightly-Builds enthalten neuere Korrekturen und Funktionen, können sich aber zwischen zwei Builds verändern. Sie sind sinnvoll, wenn eine bestimmte Änderung getestet werden soll – weniger sinnvoll ist der erste Versuch zehn Minuten vor Contestbeginn.

-
-

Schnellnavigation

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SeiteInhalt
InstallationON4KST-Account, Download, Installation und Updates
KonfigurationLogin, Station, Bänder, Benutzeroberfläche und externe Schnittstellen
Log-SynchronisationSimplelogfile, UCXLog, N1MM+, QARTest, DXLog.net und Win-Test
AirScout-IntegrationVerbindung zu AirScout und Auswertung von Aircraft-Scatter-Zeiten
DX-Cluster-ServerÜbergabe erkannter Möglichkeiten an das Logprogramm
FunktionenArbeitsweise, Herleitung und Grenzen der einzelnen Funktionen
Makros und VariablenWiederverwendbare Texte, Shortcuts und automatisch ersetzte Werte
BenutzeroberflächeAufbau der Oberfläche und Bedienung im Contest
ChangelogReleases, Nightly-Änderungen und behobene Fehler
-
-

Kontakt und Support

- -

Einen Fehler melden

-

Ein Fehler lässt sich wesentlich schneller nachvollziehen, wenn die Meldung mindestens folgende Angaben enthält:

-
    -
  1. verwendete KST4Contest-Version,
    2. -
  2. Betriebssystem und Installationsart,
    3. -
  3. genaue Schritte bis zum Fehler,
    4. -
  4. erwartetes und tatsächlich beobachtetes Verhalten,
    5. -
  5. gegebenenfalls einen Screenshot,
    6. -
  6. die Fehler-Logdatei.
    7. -
-

Die Fehler-Logdatei wird hier gespeichert:

- - - - - - - - - - - - - - - - - -
BetriebssystemPfad
Linux / macOS~/.praktiKST/kst4contest-errors.log
WindowsC:\Users\<Benutzername>\.praktiKST\kst4contest-errors.log
-

Vor dem Hochladen sollte die Datei kurz geprüft werden. Ein Fehlerprotokoll enthält überwiegend technische Informationen, kann abhängig vom Fehler aber beispielsweise lokale Dateipfade oder weitere Kontextdaten enthalten.

-

In Datei- und Verzeichnisnamen wird teilweise noch der technische Name praktiKST verwendet. Gemeint ist dasselbe Programm.

-
-

Danksagungen

-

KST4Contest wurde durch Rückmeldungen aus dem praktischen Contest-Betrieb wesentlich verbessert.

-

Besonderer Dank gilt Gianluca Costantino (IU3OAR), Alessandro Murador (IZ3VTH), Reczetár István (HA1FV), Viliam Petrik (OM0AAO, Idee zum DX-Cluster), Konrad Neitzel (DC9DJ, Projektstruktur), Andreas (DO5ALF, Webmaster von funkerportal.de), Franz van Velzen (PE0WGA, Tester), DN9APW als neuem Entwickler im Team und Master über die CI/CD pipelines sowie allen weiteren Testern und Ideengebern.

- -
-
- - - - - - diff --git a/website/_site/manual/de/index.html b/website/_site/manual/de/index.html deleted file mode 100644 index bfb69e4..0000000 --- a/website/_site/manual/de/index.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - KST4Contest Deutsches Handbuch - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Deutsches Handbuch

-

Das Handbuch wird zentral in GitHub gepflegt und als Wiki, PDF und Online-Dokumentation veröffentlicht.

-
- -
-
- - -
-

KST4Contest – Handbuch

- -

KST4Contest ist ein Desktop-Client für den ON4KST-Chat, der für den Contest-Betrieb auf den VHF-, UHF- und SHF-Bändern entwickelt wurde. Er verbindet Chat, Stationsauswahl, Sked-Planung, Aircraft-Scatter-Daten und die Anbindung an weitere Programme in einer gemeinsamen Arbeitsoberfläche.

- -
- - - -
-

Installation

- -

KST4Contest wird für Windows, Linux und macOS als fertiges Programmpaket bereitgestellt. Für die offiziellen Release-Pakete muss Java nicht separat installiert werden: Die benötigte Java-Laufzeitumgebung ist bereits enthalten.

- -
- - - -
-

Konfiguration

- -

Nach dem ersten Start öffnet sich das Einstellungsfenster – dieses ist der zentrale Ausgangspunkt für alle Konfigurationen. Es empfiehlt sich, das Einstellungsfenster während des Betriebs geöffnet zu lassen (z. B. um den Beacon schnell ein- und auszuschalten).

- -
- - - -
-

Log-Synchronisation

- -

KST4Contest markiert gearbeitete Stationen automatisch in der Chat-Benutzerliste. Dafür gibt es zwei grundlegende Methoden:

- -
- - - -
-

AirScout-Integration

- -

AirScout (von DL2ALF) ist ein Programm zur Erkennung von Flugzeugen für den Aircraft-Scatter-Betrieb. KST4Contest ist eng mit AirScout integriert und zeigt reflektierbare Flugzeuge direkt in der Benutzerliste an.

- -
- - - -
-

Integrierter DX-Cluster-Server

- -

Ab Version 1.23 enthält KST4Contest einen integrierten DX-Cluster-Server. Dieser sendet Spots direkt an das Logprogramm, wenn eine Richtungs-Warnung ausgelöst wird.

- -
- - - -
-

Funktionen

- -

Übersicht aller Hauptfunktionen von KST4Contest.

- -
- - - -
-

Makros und Variablen

- -

KST4Contest bietet ein flexibles System aus Text-Snippets, Shortcuts und eingebauten Variablen, die den Chat-Workflow im Contest erheblich beschleunigen.

- -
- - - -
-

Benutzeroberfläche

- -

Das Hauptfenster besteht aus mehreren Bereichen:

- -
- - - -
-

Changelog

- -

Versionsverlauf von KST4Contest / PraktiKST.

- -
- - - - - - - - - - - - - - - - - - - - - - -
-
- - - - - - diff --git a/website/_site/manual/de/installation/index.html b/website/_site/manual/de/installation/index.html deleted file mode 100644 index 8a53228..0000000 --- a/website/_site/manual/de/installation/index.html +++ /dev/null @@ -1,503 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Installation

-

Installation

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

KST4Contest wird für Windows, Linux und macOS als fertiges Programmpaket bereitgestellt. Für die offiziellen Release-Pakete muss Java nicht separat installiert werden: Die benötigte Java-Laufzeitumgebung ist bereits enthalten.

-

Benötigt werden damit im Wesentlichen ein unterstütztes Betriebssystem, eine Internetverbindung und ein ON4KST-Account. Das klingt zunächst überschaubar – und ist es normalerweise auch.

-

Voraussetzungen

-

ON4KST-Account

-

KST4Contest ist ein eigenständiger Client für den ON4KST-Chat, ersetzt aber nicht den dazugehörigen Benutzeraccount.

-

Falls noch kein Account vorhanden ist, kann er über die offizielle ON4KST-Seite angelegt werden:

- -

ON4KST gibt Englisch als gemeinsame Sprache im Chat vor. Das gilt auch dann, wenn beide beteiligten Stationen dieselbe Muttersprache sprechen. Im Contestbetrieb werden häufig die üblichen Amateurfunk-Abkürzungen wie pse, agn, qrg, dir, rrr, tnx oder 73 verwendet.

-

Die eigentliche Bedienung des Chats und das Senden persönlicher Nachrichten werden im Kapitel zur Benutzeroberfläche beschrieben. Für die Installation ist zunächst nur wichtig, dass der Account funktioniert.

-

Bildschirmgröße

-

Eine nutzbare Bildschirmfläche von ungefähr 1200 × 720 Pixeln oder mehr wird empfohlen.

-

KST4Contest passt das Hauptfenster automatisch an die verfügbare Fläche des primären Bildschirms an. Das Programm kann deshalb auch auf kleineren Bildschirmen gestartet werden. Weniger Platz bleibt allerdings weniger Platz: In diesem Fall können nicht alle Tabellen, Filter und Zusatzinformationen gleichzeitig in sinnvoller Größe dargestellt werden.

-

Java

-

Für die fertigen Pakete aus den GitHub Releases ist keine separate Java-Installation erforderlich. Die benötigte Laufzeitumgebung wird zusammen mit KST4Contest ausgeliefert.

-

Eine Java-Entwicklungsumgebung wird nur benötigt, wenn KST4Contest selbst aus dem Quellcode gebaut werden soll. Bei den AUR-Paketen kst4contest und kst4contest-git werden Java 21 und Maven als Build-Abhängigkeiten durch den Paketmanager berücksichtigt.

-
-

Stable, Beta oder Nightly?

-

KST4Contest wird in drei Entwicklungsständen bereitgestellt:

- - - - - - - - - - - - - - - - - - - - - - - - - -
KanalGeeignet fürEinordnung
StableNormaler ContestbetriebVeröffentlichte und für den regulären Einsatz vorgesehene Version
BetaGezielte Tests vor einem Stable-ReleaseVorabversion mit weitgehend festgelegtem Funktionsumfang
NightlyFrühe Tests neuer FunktionenAktueller Entwicklungsstand aus dem main-Branch
-

Für den normalen Einsatz wird die Stable-Version empfohlen.

-

Beta- und Nightly-Versionen können Funktionen enthalten, die im Stable-Release noch nicht verfügbar sind. Sie können aber ebenso unfertige Bedienabläufe, geänderte Einstellungen oder neue Fehler enthalten. Das ist kein ungewöhnlicher Defekt im Veröffentlichungsverfahren, sondern der Zweck eines Entwicklungskanals.

-

Wenn in diesem Manual eine Funktion ausdrücklich mit Nightly gekennzeichnet ist, gehört sie noch nicht zwingend zum aktuellen Stable-Release.

-
-

Download

-

Die aktuelle Stable-Version ist hier verfügbar:

- -

Die Release-Seite enthält die Programmpakete sowie die deutschen und englischen PDF-Handbücher.

-

Welches Paket wird benötigt?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
BetriebssystemPaketTypischer Dateiname
Windows x64ZIP-PaketpraktiKST-v<Version>-windows-x64.zip
Linux x86_64AppImageKST4Contest-v<Version>-linux-x86_64.AppImage
Debian/Ubuntu amd64DEB-PaketKST4Contest-v<Version>-debian-amd64.deb
Fedora/RPM x86_64RPM-PaketKST4Contest-v<Version>-fedora-x86_64.rpm
Arch Linux x86_64Arch-PaketKST4Contest-v<Version>-archlinux-x86_64.pkg.tar.zst
Linux mit FlatpakFlatpak-Referenzde.x08.KST4Contest.flatpakref
macOS Apple SiliconDMG für ARM64KST4Contest-v<Version>-macos-arm64.dmg
macOS IntelDMG für x86_64KST4Contest-v<Version>-macos-x86_64.dmg
-

Lade Programmpakete nur aus den offiziellen GitHub Releases, dem KST4Contest-Flatpak-Repository oder den verlinkten AUR-Paketen herunter. Dateien aus anderen Quellen können anders gebaut, veraltet oder verändert worden sein.

-
-

Installation unter Windows

-

KST4Contest wird unter Windows als ZIP-Paket bereitgestellt. Ein klassischer Installer ist nicht erforderlich.

-
    -
  1. Lade praktiKST-v<Version>-windows-x64.zip aus dem aktuellen Release herunter.
    2. -
  2. Entpacke die ZIP-Datei vollständig in einen eigenen Ordner.
    3. -
  3. Öffne den entpackten Ordner.
    4. -
  4. Starte praktiKST.exe.
    5. -
-

Starte das Programm nicht direkt aus der noch komprimierten ZIP-Datei. KST4Contest besteht aus mehreren Dateien und einer mitgelieferten Laufzeitumgebung. Windows kann diese Struktur nur zuverlässig verwenden, wenn das Archiv vorher vollständig entpackt wurde.

-

Die Programmeinstellungen befinden sich nicht im entpackten Programmordner, sondern im Benutzerverzeichnis:

-
%USERPROFILE%\.praktiKST\preferences.xml
-
-

Dadurch können neue Programmversionen in einen anderen Ordner entpackt werden, ohne dass die vorhandenen Einstellungen verloren gehen.

-
-

Installation unter Linux

-

Unter Linux stehen mehrere Paketformate zur Verfügung. Welches davon sinnvoll ist, hängt weniger von KST4Contest als von der verwendeten Distribution und der gewünschten Update-Methode ab.

- - - - - - - - - - - - - - - - - - - - - - - - - -
InstallationsartSinnvoll, wenn …
FlatpakUpdates zentral verwaltet werden sollen und Flatpak bereits verwendet wird
AppImageKST4Contest ohne Installation als einzelne portable Datei gestartet werden soll
DEB/RPMdie Paketverwaltung der Distribution verwendet werden soll
Arch-Paket/AURArch Linux, Manjaro oder EndeavourOS eingesetzt wird
-

Flatpak

-

Flatpak ist für die meisten Linux-Anwender der einfachste Weg, KST4Contest installiert und aktualisierbar zu halten. Das KST4Contest-Repository ist GPG-signiert und enthält die Kanäle Stable, Beta und Nightly.

-

Stable über die Release-Datei installieren

-

Lade de.x08.KST4Contest.flatpakref aus dem aktuellen Release herunter und öffne die Datei mit der Softwareverwaltung der verwendeten Desktop-Umgebung.

-

Alternativ kann sie im Terminal installiert werden:

-
flatpak install ./de.x08.KST4Contest.flatpakref
-
-

KST4Contest-Repository hinzufügen

-

Das Repository muss nur einmal hinzugefügt werden:

-
flatpak remote-add --if-not-exists kst4contest \
-https://praktimarc.github.io/kst4contest/kst4contest.flatpakrepo
-
-

Anschließend kann die Stable-Version installiert werden:

-
flatpak install kst4contest de.x08.KST4Contest//stable
-
-

Beta installieren

-
flatpak install kst4contest de.x08.KST4Contest//beta
-
-

Nightly installieren

-
flatpak install kst4contest de.x08.KST4Contest//nightly
-
-

KST4Contest verwendet für alle drei Kanäle dieselbe App-ID. Eine parallele Installation mehrerer KST4Contest-Kanäle ist deshalb nicht vorgesehen.

-

Zum Wechsel von Stable auf Nightly beispielsweise:

-
flatpak uninstall de.x08.KST4Contest//stable
-flatpak install kst4contest de.x08.KST4Contest//nightly
-
-

Die persönlichen Einstellungen im Verzeichnis ~/.praktiKST werden dabei nicht automatisch gelöscht.

-

Installierte Flatpak-Anwendungen können mit folgendem Befehl aktualisiert werden:

-
flatpak update de.x08.KST4Contest
-
-

Je nach Desktop-Umgebung kann die grafische Softwareverwaltung verfügbare Flatpak-Updates ebenfalls anzeigen oder automatisch installieren. Der Befehl flatpak update selbst führt das Update aus; er verspricht nicht, irgendwann von allein vorbeizukommen.

-

AppImage

-

Das AppImage benötigt keine klassische Installation.

-
    -
  1. Lade KST4Contest-v<Version>-linux-x86_64.AppImage herunter.
    2. -
  2. Öffne ein Terminal im Download-Verzeichnis.
    3. -
  3. Mache die Datei ausführbar:
    4. -
-
chmod +x KST4Contest-v<Version>-linux-x86_64.AppImage
-
-
    -
  1. Starte KST4Contest:
    2. -
-
./KST4Contest-v<Version>-linux-x86_64.AppImage
-
-

Das AppImage kann anschließend an einen anderen Ort verschoben werden, beispielsweise nach ~/Applications.

-

Debian und Ubuntu

-

Installiere das DEB-Paket mit:

-
sudo apt install ./KST4Contest-v<Version>-debian-amd64.deb
-
-

Alternativ kann die Datei in einer grafischen Paketverwaltung geöffnet werden.

-

Fedora und kompatible RPM-Systeme

-

Installiere das RPM-Paket mit:

-
sudo dnf install ./KST4Contest-v<Version>-fedora-x86_64.rpm
-
-

Arch Linux: fertiges Release-Paket

-

Das aus dem GitHub Release heruntergeladene Arch-Paket kann direkt installiert werden:

-
sudo pacman -U KST4Contest-v<Version>-archlinux-x86_64.pkg.tar.zst
-
-

Arch Linux: Installation über den AUR

-

Im AUR stehen drei Varianten bereit:

- - - - - - - - - - - - - - - - - - - - - -
PaketInhalt
kst4contest-binVorgefertigtes Paket des aktuellen Stable-Releases
kst4contestStable-Release, das lokal aus dem Quellcode gebaut wird
kst4contest-gitAktueller Entwicklungsstand aus dem main-Branch
-

Für die meisten Anwender ist kst4contest-bin die naheliegende Variante:

-
yay -S kst4contest-bin
-
-

Stable aus dem Quellcode bauen:

-
yay -S kst4contest
-
-

Aktuellen Entwicklungsstand bauen:

-
yay -S kst4contest-git
-
-

Die drei Pakete stellen dieselbe Anwendung bereit und sind deshalb als gegenseitige Konflikte definiert. Installiere nur eine Variante gleichzeitig.

-

AUR-Updates werden berücksichtigt, wenn der verwendete AUR-Helper nach Paketaktualisierungen sucht, beispielsweise mit:

-
yay -Syu
-
-

Sie erfolgen nicht allein deshalb automatisch, weil das Paket aus dem AUR stammt.

-
-

Installation unter macOS

-
-

Best-Effort-Support: Die macOS-Pakete werden zusammen mit den übrigen Releases gebaut, aber nicht in demselben Umfang getestet wie die Windows- und Linux-Versionen. Rückmeldungen sind willkommen; eine vollständig geprüfte Unterstützung aller macOS-Versionen und Hardwarevarianten kann derzeit jedoch nicht zugesagt werden.

-
-

Für Apple-Silicon-Macs wird das Paket mit arm64 benötigt. Für Intel-Macs ist das Paket mit x86_64 vorgesehen.

-
    -
  1. Lade die passende DMG-Datei herunter.
    2. -
  2. Öffne die DMG-Datei.
    3. -
  3. Ziehe KST4Contest.app in den Ordner Programme.
    4. -
  4. Starte KST4Contest aus dem Programme-Ordner oder über das Launchpad.
    5. -
-

Die Anwendung ist derzeit nicht von Apple notarisiert. macOS kann den ersten Start deshalb blockieren.

-

Falls die Anwendung aus dem offiziellen GitHub Release stammt:

-
    -
  1. Öffne den Programme-Ordner im Finder.
    2. -
  2. Klicke mit der rechten Maustaste oder mit gedrückter Ctrl-Taste auf KST4Contest.app.
    3. -
  3. Wähle Öffnen.
    4. -
  4. Bestätige den Start im angezeigten Dialog.
    5. -
-

Alternativ kann macOS unter Systemeinstellungen → Datenschutz & Sicherheit die Schaltfläche Trotzdem öffnen anbieten.

-
-

Wo werden die Einstellungen gespeichert?

-

KST4Contest speichert seine Einstellungen und weitere lokale Arbeitsdateien im Benutzerverzeichnis. Der Programmordner und das Datenverzeichnis sind voneinander getrennt.

- - - - - - - - - - - - - - - - - - - - - - - - - -
BetriebssystemDatenverzeichnisEinstellungsdatei
Windows%USERPROFILE%\.praktiKST\%USERPROFILE%\.praktiKST\preferences.xml
Linux~/.praktiKST/~/.praktiKST/preferences.xml
macOS~/.praktiKST/~/.praktiKST/preferences.xml
-

Beachte die Schreibweise .praktiKST mit großem KST. Unter Linux und macOS wird zwischen Groß- und Kleinschreibung unterschieden. .praktikst wäre dort schlicht ein anderes Verzeichnis.

-

Ein Programmupdate entfernt dieses Verzeichnis nicht. Trotzdem ist es sinnvoll, vor größeren Versionswechseln oder umfangreichen Änderungen an der Konfiguration eine Sicherung davon anzulegen.

-
-

Updates

-

KST4Contest prüft beim Start, ob ein neueres Stable-Release verfügbar ist. Wenn eine neuere Version gefunden wird, erscheint ein Informationsfenster mit:

-
    -
  • der installierten Version,
    • -
  • der aktuellen Stable-Version,
    • -
  • einer kurzen Übersicht wesentlicher Änderungen,
    • -
  • dem Changelog,
    • -
  • bekannten Problemen,
    • -
  • einem Link zur passenden GitHub-Release-Seite.
    • -
-

Update-Hinweis von KST4Contest

-

Der Update-Checker installiert nichts selbst. Er informiert über die neue Version und öffnet die plattformneutrale Release-Seite. Dort muss das passende Paket für Windows, Linux oder macOS ausgewählt werden.

-

Windows aktualisieren

-
    -
  1. Beende KST4Contest.
    2. -
  2. Lade das neue Windows-ZIP herunter.
    3. -
  3. Entpacke es in einen neuen oder leeren Ordner.
    4. -
  4. Starte die neue Version.
    5. -
  5. Prüfe, ob die bisherigen Einstellungen geladen wurden.
    6. -
  6. Entferne den alten Programmordner erst danach.
    7. -
-

Die Einstellungen bleiben erhalten, weil sie unter %USERPROFILE%\.praktiKST und nicht im Programmordner gespeichert werden.

-

AppImage aktualisieren

-
    -
  1. Lade das neue AppImage herunter.
    2. -
  2. Mache es ausführbar.
    3. -
  3. Starte die neue Datei.
    4. -
  4. Entferne das bisherige AppImage erst, wenn die neue Version funktioniert.
    5. -
-

Debian und Ubuntu aktualisieren

-
sudo apt install ./KST4Contest-v<Version>-debian-amd64.deb
-
-

Fedora aktualisieren

-
sudo dnf upgrade ./KST4Contest-v<Version>-fedora-x86_64.rpm
-
-

Arch-Paket aktualisieren

-
sudo pacman -U KST4Contest-v<Version>-archlinux-x86_64.pkg.tar.zst
-
-

AUR-Paket aktualisieren

-

Aktualisiere das installierte Paket über den verwendeten AUR-Helper, beispielsweise:

-
yay -Syu
-
-

Flatpak aktualisieren

-
flatpak update de.x08.KST4Contest
-
-

macOS aktualisieren

-
    -
  1. Lade die neue DMG-Datei für die vorhandene Architektur herunter.
    2. -
  2. Beende KST4Contest.
    3. -
  3. Öffne die DMG-Datei.
    4. -
  4. Ersetze KST4Contest.app im Programme-Ordner.
    5. -
  5. Starte die neue Version und prüfe die vorhandenen Einstellungen.
    6. -
-

Die Konfiguration unter ~/.praktiKST bleibt davon unberührt.

-
-

Probleme beim ersten Start

-

Windows meldet eine unbekannte Anwendung

-

KST4Contest ist derzeit nicht mit einem kommerziellen Windows-Code-Signing-Zertifikat signiert. Windows oder ein zusätzlich installiertes Sicherheitsprodukt kann deshalb vor einer unbekannten oder selten heruntergeladenen Anwendung warnen.

-

Prüfe in diesem Fall zuerst:

-
    -
  • Stammt die Datei aus dem offiziellen KST4Contest-Release?
    • -
  • Passt der Dateiname zum veröffentlichten Release?
    • -
  • Wurde die Datei vollständig heruntergeladen?
    • -
  • Nennt das Sicherheitsprogramm einen konkreten Erkennungsnamen oder nur eine allgemeine Reputationswarnung?
    • -
-

Ein Warnhinweis ist allein weder ein sicherer Beweis für Schadsoftware noch automatisch ein Fehlalarm. Wenn die Herkunft der Datei unklar ist, sollte sie nicht gestartet oder aus der Quarantäne wiederhergestellt werden.

-

Einige Anwender haben insbesondere Quarantäne-Meldungen von Norton 360 gemeldet. Wenn sich eine Meldung reproduzieren lässt, erstelle bitte einen GitHub-Issue und nenne:

-
    -
  • die KST4Contest-Version,
    • -
  • den vollständigen Dateinamen,
    • -
  • das verwendete Sicherheitsprodukt und dessen Version,
    • -
  • den angezeigten Erkennungsnamen,
    • -
  • möglichst einen Screenshot der Meldung.
    • -
-

Das AppImage startet nicht

-

Prüfe zuerst das Ausführungsrecht:

-
chmod +x KST4Contest-v<Version>-linux-x86_64.AppImage
-
-

Starte die Datei anschließend aus einem Terminal. Fehlermeldungen sind dort meist aussagekräftiger als ein Doppelklick, der lediglich nichts Sichtbares tut.

-

macOS blockiert die Anwendung

-

Verwende die unter Installation unter macOS beschriebene Funktion Öffnen im Kontextmenü. Prüfe vorher, ob die DMG-Datei aus dem offiziellen GitHub Release stammt.

-

Das Problem bleibt bestehen

-

Prüfe zunächst, ob das Problem bereits unter GitHub Issues beschrieben wurde. Falls nicht, erstelle einen neuen Issue mit:

-
    -
  • Betriebssystem und Version,
    • -
  • verwendeter KST4Contest-Version,
    • -
  • Installationsart,
    • -
  • genauer Fehlermeldung,
    • -
  • den Schritten, mit denen sich das Problem reproduzieren lässt.
    • -
-

„Geht nicht“ beschreibt den Zustand meistens korrekt, hilft bei der Fehlersuche aber nur begrenzt.

- -
-
- - - - - - diff --git a/website/_site/manual/de/konfiguration/index.html b/website/_site/manual/de/konfiguration/index.html deleted file mode 100644 index a1656c5..0000000 --- a/website/_site/manual/de/konfiguration/index.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Konfiguration

-

Konfiguration

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

Nach dem ersten Start öffnet sich das Einstellungsfenster – dieses ist der zentrale Ausgangspunkt für alle Konfigurationen. Es empfiehlt sich, das Einstellungsfenster während des Betriebs geöffnet zu lassen (z. B. um den Beacon schnell ein- und auszuschalten).

-
-

Wichtig: Nach jeder Änderung unbedingt „Save Settings" klicken! Die Einstellungen werden unter Linux in ~/.praktikst/preferences.xml und unter Windows in %USERPROFILE%\.praktikst\preferences.xml (bzw. C:\Users\<Benutzername>\.praktikst\preferences.xml) gespeichert. Ab v1.21 werden auch Fenstergrößen und Divider-Positionen beim Speichern gesichert.

-
-
-

Station Settings (Stationseinstellungen)

-

Stationseinstellungen

-

Login und Chat-Kategorien

-

Hier werden die Zugangsdaten für den ON4KST-Chat eingetragen (Rufzeichen und Passwort). -Zudem wird die primäre Chat-Kategorie (z. B. IARU Region 1 VHF/Microwave) ausgewählt.

-

Mit der Option für einen zweiten Chat (Multi-Channel-Login) kann man sich gleichzeitig in eine weitere Kategorie (z. B. UHF/SHF) einloggen. Beide Chats werden dann parallel überwacht. Hier kann optional auch ein abweichender Login-Name für den zweiten Chat vergeben werden (nützlich für Opposite Station Multi-Callsign Logging).

-

Rufzeichen und Locator

-

Eigenes Rufzeichen und Maidenhead-Locator (6-stellig, z. B. JN49IJ) eintragen. Diese Werte werden für Distanz- und Richtungsberechnungen benötigt.

-

Aktivierte Bänder

-

Über die „my station uses band"-Checkboxen werden die aktiven Bänder ausgewählt. Nur für ausgewählte Bänder erscheinen Schaltflächen und Tabellenzeilen in der Benutzeroberfläche. Nach Änderungen muss die Software neu gestartet werden.

-

Antennen-Öffnungswinkel (Antenna Beamwidth)

-

Einen realistischen Wert für den Öffnungswinkel der eigenen Antenne eintragen (in Grad). Dieser Wert wird für die Sked-Richtungs-Hervorhebung verwendet. Ein Testwert von 50° hat sich bewährt; DM5M nutzt Quads mit 69°.

-
-

Keinesfalls Fantasy-Werte eintragen – die Richtungsberechnungen werden sonst unbrauchbar.

-
-

Standard-Maximum-QRB

-

Maximale Entfernung (in km), für die Richtungs-Warnungen ausgelöst werden sollen. Realistischer Wert für DM5M: 900 km. Stationen, die weiter entfernt sind, werden für Highlighting-Zwecke ignoriert.

-
-

Server-Einstellungen (ab v1.31)

-

Der Chat-Server-DNS und -Port sind in den Preferences konfigurierbar:

-
    -
  • Server-DNS: Standard www.on4kst.org (ab v1.31 geändert von www.on4kst.info).
    • -
  • Port: Standardport des ON4KST-Servers.
    • -
-

Eine Änderung ist nur notwendig, wenn der Server umzieht oder ein alternativer Endpunkt genutzt wird.

-
-

Log-Sync-Einstellungen

-

Drei Methoden stehen zur Verfügung, um gearbeitete Stationen automatisch zu markieren. Details: Log-Synchronisation.

-

Universal File Based Callsign Interpreter (Simplelogfile)

-

Interpretiert beliebige Log-Dateien per Regex nach Rufzeichen-Mustern. Keine Bandinformation möglich. Geeignet als Fallback oder für nicht direkt unterstützte Logprogramme.

-

Netzwerk-Listener für QSO-UDP-Broadcast

-

Empfohlene Methode. KST4Contest hört auf UDP-Pakete, die das Logprogramm beim Speichern eines QSOs an die Broadcast-Adresse sendet. Die Stationen werden mit Bandinformation markiert. UDP-Port: Standard 12060. (Wird z. B. von UCXLog, N1MM+, QARTest, DXLog.net genutzt).

-

Win-Test Network-Listener (Zusätzlicher UDP-Listener)

-

Dedizierter Netzwerk-Erkenner für Win-Test. KST4Contest empfängt und verarbeitet Win-Test-spezifische UDP-Pakete (inkl. Sked-Übergabe) auf dem dafür konfigurierten Port.

-
-

TRX-Sync-Einstellungen

-

Empfängt die aktuelle Frequenz des Transceivers vom Logprogramm via UDP. Ermöglicht die automatische Befüllung der Variable MYQRG. Nützlich für:

-
    -
  • Schnelles Einfügen der eigenen QRG in Chat-Nachrichten.
    • -
  • Automatische CQ-Baken mit aktueller Frequenz.
    • -
-
-

Hinweis für Multi-Setup: Wenn zwei Logprogramme an zwei Computern betrieben werden, aber nur eine KST4Contest-Instanz, darf nur ein Logprogramm die Frequenzpakete senden. KST4Contest kann nicht zwischen den Quellen unterscheiden.

-
-
-

AirScout-Einstellungen

-

Konfiguration der Schnittstelle zu AirScout für die Flugzeug-Scatter-Erkennung. Details: AirScout-Integration.

-
-

Notification Settings (Benachrichtigungen)

-

Drei Benachrichtigungstypen stehen zur Wahl:

-
    -
  1. Einfache Sounds: TADA-Sound für eingehende Nachrichten, Tick für Sked-Richtungserkennung usw.
    2. -
  2. CW-Ansage: Das Rufzeichen einer Station, die eine Privatnachricht sendet, wird als CW-Signal ausgegeben.
    3. -
  3. Phonetische Ansage: Das Rufzeichen wird phonetisch ausgesprochen.
    4. -
-
-

Shortcut Settings (Schnellzugriff-Schaltflächen)

-

Konfiguration von Schnellzugriff-Schaltflächen, die direkt im Hauptfenster erscheinen. Ein Klick auf eine Schaltfläche fügt den konfigurierten Text in das Sendfeld ein. Alle Variablen können verwendet werden.

-
-

Snippet Settings (Text-Snippets)

-

Text-Snippets sind über folgende Wege abrufbar:

-
    -
  • Rechtsklick auf ein Rufzeichen in der Benutzerliste
    • -
  • Rechtsklick in der CQ-Nachrichtentabelle
    • -
  • Rechtsklick in der PM-Nachrichtentabelle
    • -
  • Tastenkombinationen: Ctrl+1 bis Ctrl+0 für die ersten 10 Snippets
    • -
-

Wenn in der Benutzerliste ein Rufzeichen ausgewählt ist, wird der Snippet als Direktnachricht adressiert: -/CQ RUFZEICHEN <Snippet-Text>

-
-

Beacon Settings (Automatischer Beacon)

-

Konfiguration eines automatischen Intervall-Beacons im öffentlichen Chat-Kanal. Empfohlen: Variable MYQRG im Text verwenden, damit die aktuelle Frequenz immer aktuell ist. Intervall und Text sind frei konfigurierbar.

-
-

Tipp: Beacon beim CQ-Rufen aktivieren und im Einstellungsfenster schnell deaktivieren, wenn kein CQ gerufen wird.

-
-
-

Messagehandling Settings (ab v1.25)

-

Neuer Einstellungsbereich mit folgenden Optionen:

-
    -
  • Auto-Antwort auf alle eingehenden Nachrichten: Automatische Antwort auf Privatnachrichten konfigurierbar.
    • -
  • Auto-Antwort mit eigener CQ-QRG: Wenn jemand nach der eigenen QRG fragt, antwortet KST4Contest automatisch mit dem Inhalt der MYQRG-Variable.
    • -
  • Standard-Filter für das Userinfo-Fenster: Voreingestellter Nachrichtenfilter für das Stationsinfo-Fenster konfigurierbar (für Gianluca :-) ).
    • -
-
-

Win-Test-Netzwerk-Listener (ab v1.31)

-

Dedizierter Empfänger für Win-Test-spezifische UDP-Pakete. Ermöglicht:

-
    -
  • 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.
    • -
-

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.
    • -
-
-

Hinweis: Der Win-Test-Listener ist ein zusätzlicher Listener – der Standard-QSO-UDP-Broadcast-Listener auf Port 12060 bleibt davon unabhängig.

-
-
-

PSTRotator-Einstellungen (ab v1.31)

-

KST4Contest kann die Antennenrichtung über PSTRotator steuern.

-

Einstellungen:

-
    -
  • Aktivieren/Deaktivieren: Checkbox in den Preferences (ab v1.40).
    • -
  • IP-Adresse: IP-Adresse des PSTRotator-Rechners (Standard: 127.0.0.1 bei Betrieb auf demselben PC).
    • -
  • Port: Kommunikationsport von PSTRotator.
    • -
-
-

Hinweis: Nach einem Klick auf den Richtungs-Button wartet KST4Contest kurz auf die Rotatorantwort. Bei langsamen Rotoren (z. B. SPID) kann es zu einer kleinen Verzögerung kommen.

-
-
-

Sniffer-Einstellungen (ab v1.31)

-

Der QSO-Sniffer filtert Chat-Nachrichten von konfigurierbaren Rufzeichen und leitet sie ins PM-Fenster weiter.

-

Einstellungen:

-
    -
  • Rufzeichen-Liste: Kommagetrennte Liste von Rufzeichen, deren Nachrichten immer in das PM-Fenster weitergeleitet werden sollen.
    • -
-

Anwendungsfall: Wichtige Stationen (z. B. DX-Peditionen oder feste Verbündete im Contest) im Auge behalten, ohne den Haupt-Chat ständig zu beobachten.

-
-

Worked Station Database Settings (Gearbeitete-Stationen-Datenbank)

-

Die interne Worked-Datenbank enthält:

-
    -
  • Worked-Status aller Stationen (pro Band)
    • -
  • NOT-QRV-Tags (seit v1.2)
    • -
-

Ab v1.40: Einträge haben eine automatische Lebensdauer von 3 Tagen – ein manuelles Zurücksetzen vor jedem Contest ist nicht mehr zwingend notwendig. Für ein vollständiges Reset kann trotzdem die Schaltfläche „Reinitialize" verwendet werden.

-
-

Dark Mode (ab v1.26)

-

Umschaltbar über das Menü: Window → Use Dark Mode. Die Farben können über CSS individuell angepasst werden.

-
-

Einstellungen speichern

-

Nach jeder Änderung „Save Settings" klicken! Ohne Speichern gehen alle Änderungen beim nächsten Start verloren.

-
    -
  • Speicherort: unter Linux ~/.praktikst/preferences.xml und unter Windows %USERPROFILE%\.praktikst\preferences.xml (bzw. C:\Users\<Benutzername>\.praktikst\preferences.xml)
    • -
  • Ab v1.21: Fenstergrößen und Divider-Positionen werden ebenfalls gespeichert.
    • -
  • Bei Problemen: Konfigurationsdatei löschen → KST4Contest erstellt eine neue mit Standardwerten.
    • -
- -
-
- - - - - - diff --git a/website/_site/manual/de/log-synchronisation/index.html b/website/_site/manual/de/log-synchronisation/index.html deleted file mode 100644 index 55aa56b..0000000 --- a/website/_site/manual/de/log-synchronisation/index.html +++ /dev/null @@ -1,231 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Log-Synchronisation

-

Log-Synchronisation

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

KST4Contest markiert gearbeitete Stationen automatisch in der Chat-Benutzerliste. Dafür gibt es zwei grundlegende Methoden:

-
-

Log-Synchronisation Einstellungsfenster

-

Methode 1: Universal File Based Callsign Interpreter (Simplelogfile)

-

KST4Contest liest eine Log-Datei und sucht mittels regulärem Ausdruck nach Rufzeichen-Mustern. Dabei werden auch binäre Logdateien unterstützt – unlesbarer Binärinhalt wird einfach ignoriert.

-

Vorteil: Funktioniert mit nahezu jedem Logprogramm, das eine Datei schreibt. -Nachteil: Keine Bandinformation möglich – es wird nur „gearbeitet" markiert, nicht auf welchem Band.

-

Pfad der Log-Datei in den Preferences eintragen. Die Datei wird nur gelesen, nie verändert (read-only).

-
-

Tipp: Die Simplelogfile-Funktion kann auch genutzt werden, um Stationen zu markieren, die definitiv nicht erreichbar sind (z. B. eigene Notizen). Das wird in einer späteren Version durch ein besseres Tagging-System ersetzt.

-
-
-

Methode 2: Netzwerk-Listener (UDP-Broadcast) – Empfohlen

-

Das Logprogramm sendet beim Speichern eines QSOs ein UDP-Paket an die Broadcast-Adresse des Heimnetzwerks. KST4Contest empfängt dieses Paket und markiert die Station inklusive Bandinformation in der internen SQLite-Datenbank.

-
-

Wichtig: KST4Contest muss parallel zum Logprogramm laufen. QSOs, die während einer Abwesenheit von KST4Contest geloggt werden, werden nicht erfasst – außer bei QARTest (kann das komplette Log senden).

-
-

Standard UDP-Port: 12060 (entspricht dem Standard der meisten Logprogramme)

-
-

Unterstützte Logprogramme

-

UCXLog (DL7UCX)

-

UCXLog Konfiguration

-

UCXLog sendet QSO-UDP-Pakete und Transceiver-Frequenzpakete.

-

Einstellungen in UCXLog:

-
    -
  • UDP-Broadcast aktivieren
    • -
  • IP-Adresse des KST4Contest-Computers eintragen (bei lokalem Betrieb: 127.0.0.1)
    • -
  • Port: 12060 (Standard)
    • -
-

Grün markierte Felder in den UCXLog-Einstellungen beachten: IP und Port müssen eingetragen werden.

-

Hinweis für Multi-Setup (2 Computer, 2 Radios, eine KST4Contest-Instanz): Beide Logprogramme müssen die QSO-Pakete an die IP des KST4Contest-Computers senden. Dann ist mindestens eine IP nicht 127.0.0.1.

-

QARTest (IK3QAR)

-

QARTest Konfiguration

-

Besonderheit: QARTest kann das vollständige Log an KST4Contest senden (Schaltfläche „Invia log completo" in den QARTest-Einstellungen). Damit werden auch QSOs erfasst, die vor dem Start von KST4Contest geloggt wurden.

-

Einstellungen in QARTest:

-
    -
  • UDP-Broadcast und IP/Port wie UCXLog konfigurieren
    • -
  • „Invia log completo" für den vollständigen Log-Upload verwenden
    • -
-

(„Buona funzionalità caro IK3QAR!" – DO5AMF)

-

N1MM+

-

Einstellungen in N1MM+:

-

In N1MM+ unter Config → Configure Ports, Mode Control, Winkey, etc. → Broadcast Data:

-
    -
  • Radio Info aktivieren (für TRX-Sync/QRG)
    • -
  • Contact Info aktivieren (für QSO-Sync)
    • -
  • IP: 127.0.0.1 (oder IP des KST4Contest-Computers)
    • -
  • Port: 12060
    • -
-

Für den integrierten DX-Cluster-Server: N1MM+ als DX-Cluster-Client konfigurieren (Server: 127.0.0.1, Port wie in KST4Contest eingestellt).

-

DXLog.net

-

DXLog.net Konfiguration

-

Einstellungen in DXLog.net:

-
    -
  • UDP-Broadcast aktivieren
    • -
  • IP des KST4Contest-Computers eintragen (grün markierte Felder)
    • -
  • Port: 12060
    • -
-

Win-Test

-

Win-Test wird mit einem dedizierten UDP-Netzwerk-Listener unterstützt, der das native Win-Test Netzwerkprotokoll versteht.

-

Vorteile der Win-Test Integration:

-
    -
  • 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. -
    2. Sonst wird die eigene aktuelle QRG verwendet (aus Win-Test STATUS oder manueller Eingabe).
      3. -
    -
    • -
-

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.
    • -
-

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.
    • -
-

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.
    • -
-
-

TRX-Frequenz-Synchronisation

-

Neben der QSO-Synchronisation übertragen UCXLog und andere Programme auch die aktuelle Transceiverfrequenz via UDP. KST4Contest verarbeitet diese Information und stellt sie als Variable MYQRG bereit.

-

FrequenzButtons

-

Ergebnis: Die eigene QRG muss im Chat nie mehr manuell eingegeben werden – ein Klick auf den MYQRG-Button oder die Verwendung der Variable im Beacon genügt.

-

Quellen für die eigene QRG (MYQRG):

-
    -
  • UCXLog, N1MM+, DXLog.net, QARTest via UDP-Port 12060
    • -
  • Win-Test STATUS-Paket (optional, konfigurierbar im Reiter „TRX-Synchronisation" unter „Win-Test STATUS QRG Sync")
    • -
  • Manuelle Eingabe im QRG-Feld
    • -
-
-

Hinweis für Multi-Setup: Bei zwei Logprogrammen an zwei Computern sollte nur eines die Frequenzpakete senden. KST4Contest kann nicht zwischen den Quellen unterscheiden und verarbeitet alle eingehenden Pakete.

-
-
-

Multi-Setup: 2 Radios, 2 Computer

-

Für DM5M-typische Setups (2 Radios, 2 Computer, eine KST4Contest-Instanz oder zwei separate):

-

Variante A – Eine gemeinsame KST4Contest-Instanz:

-
    -
  • Beide Logprogramme senden QSO-Pakete an die IP des KST4Contest-Computers
    • -
  • Nur ein Logprogramm sendet Frequenzpakete (empfohlen: das VHF-Logprogramm)
    • -
-

Variante B – Zwei separate KST4Contest-Instanzen (empfohlen):

-
    -
  • Jedes Logprogramm kommuniziert mit seiner eigenen KST4Contest-Instanz via 127.0.0.1
    • -
  • Zwei separate Chat-Logins
    • -
  • Bessere Trennung und weniger Konflikte
    • -
-
-

Interne Datenbank

-

KST4Contest speichert die Worked-Information in einer internen SQLite-Datenbank. Diese ist von der Logprogramm-Datenbank unabhängig und wird nur über den UDP-Broadcast befüllt.

-

Vor jedem neuen Contest: Datenbank zurücksetzen! → Konfiguration – Worked Station Database Settings

- -
-
- - - - - - diff --git a/website/_site/manual/de/makros-und-variablen/index.html b/website/_site/manual/de/makros-und-variablen/index.html deleted file mode 100644 index 4fa85f1..0000000 --- a/website/_site/manual/de/makros-und-variablen/index.html +++ /dev/null @@ -1,242 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Makros und Variablen

-

Makros und Variablen

-
-

🇬🇧 English version | 🇩🇪 Du liest gerade die deutsche Version

-
-

KST4Contest bietet ein flexibles System aus Text-Snippets, Shortcuts und eingebauten Variablen, die den Chat-Workflow im Contest erheblich beschleunigen.

-
-

Überblick

- - - - - - - - - - - - - - - - - - - - - - - - - -
TypAufrufZweck
ShortcutsButton in der ToolbarSchneller Text-Insert ins Sendfeld
SnippetsRechtsklick / Ctrl+1…0Text-Bausteine, optionaler PM-Versand
VariablenIn allen Text-Feldern verwendbarDynamische Werte (QRG, Locator, AP-Daten)
-
-

Shortcuts (Schnellzugriff-Schaltflächen)

-

Konfigurierbar in den Preferences → Shortcut Settings.

-
    -
  • Jeder konfigurierte Text erzeugt einen Button in der Benutzeroberfläche.
    • -
  • Ein Klick fügt den Text in das Sendfeld ein.
    • -
  • Alle Variablen können in Shortcuts verwendet werden und werden beim Einfügen sofort aufgelöst.
    • -
  • Auch längere Texte möglich.
    • -
-

Tipp: Häufig verwendete Abkürzungen wie „pse", „rrr", „tnx", „73" als Shortcuts anlegen.

-
-

Snippets (Text-Bausteine)

-

Konfigurierbar in den Preferences → Snippet Settings.

-

Aufruf

-
    -
  • Rechtsklick auf ein Rufzeichen in der Benutzerliste
    • -
  • Rechtsklick in der CQ-Nachrichtentabelle
    • -
  • Rechtsklick in der PM-Nachrichtentabelle
    • -
  • Tastaturkürzel: Ctrl+1 bis Ctrl+0 für die ersten 10 Snippets
    • -
-

Verhalten mit ausgewähltem Rufzeichen

-

Wenn in der Benutzerliste ein Rufzeichen ausgewählt ist, wird der Snippet als Privatnachricht adressiert:

-
/CQ RUFZEICHEN <Snippet-Text>
-
-

Anschließend kann mit Enter direkt gesendet werden – auch wenn das Sendfeld nicht den Fokus hat.

-

Hardware-Makro-Tastatur

-

(Idee von IU3OAR, Gianluca Costantino)

-

Die Tastenkombinationen Ctrl+1 bis Ctrl+0 können auf einer programmierbaren Makro-Tastatur belegt werden. Ein weiterer Tastendruck (auf eine „Enter"-Taste) sendet den Text sofort. Im Contest-Betrieb spart das erheblich Zeit.

-

Vordefinierte Standard-Snippets

-

Beim ersten Start werden einige Snippets vorbelegt, z. B.:

-
    -
  • Hi OM, try sked?
    • -
  • I am calling cq ur dir, pse lsn to me at MYQRG
    • -
  • pse ur qrg?
    • -
  • rrr, I move to your qrg nw, pse ant dir me
    • -
-

Diese können in den Preferences angepasst oder gelöscht werden.

-
-

Variablen

-

Variablen werden in geschriebenen Texten (Snippets, Shortcuts, Beacon, Sendfeld) durch ihre aktuellen Werte ersetzt. Einfach den Variablennamen großgeschrieben in den Text einfügen.

-

MYQRG

-

Wird durch die aktuelle Transceiverfrequenz ersetzt.

-
    -
  • Quelle: TRX-Sync via UDP vom Logprogramm (wenn aktiviert)
    • -
  • Fallback: Manuell eingetragener Wert im MYQRG-Textfeld rechts neben dem Sendbutton
    • -
  • Format: 144.388.03
    • -
-

Beispiel: calling cq at MYQRG → calling cq at 144.388.03

-

MYQRGSHORT

-

Wie MYQRG, aber nur die ersten 7 Zeichen.

-
    -
  • Format: 144.388
    • -
-

Beispiel: qrg: MYQRGSHORT → qrg: 144.388

-

MYLOCATOR

-

Wird durch den eigenen Maidenhead-Locator (6-stellig) ersetzt.

-
    -
  • Format: JO51IJ
    • -
-

Beispiel: my loc: MYLOCATOR → my loc: JO51IJ

-

MYLOCATORSHORT

-

Wie MYLOCATOR, aber nur die ersten 4 Zeichen.

-
    -
  • Format: JO51
    • -
-

Beispiel: loc: MYLOCATORSHORT → loc: JO51

-

QRZNAME

-

Wird durch den Namen der aktuell ausgewählten Station aus dem Chat-Namenfeld ersetzt.

-

Beispiel: Hi QRZNAME, sked? → Hi Gianluca, sked?

-

FIRSTAP

-

Wird durch Daten des ersten reflektierbaren Flugzeugs zur ausgewählten Station ersetzt (sofern vorhanden).

-
    -
  • Bedingung: AirScout ist aktiv und ein Flugzeug ist verfügbar.
    • -
  • Format-Beispiel: a very big AP in 1 min
    • -
-

Beispiel: AP info: FIRSTAP → AP info: a very big AP in 1 min

-

SECONDAP

-

Wie FIRSTAP, aber für das zweite verfügbare Flugzeug.

-
    -
  • Format-Beispiel: Next big AP in 9 min
    • -
-

Beispiel: also: SECONDAP → also: Next big AP in 9 min

-

MYQTF (geplant für v1.3)

-

Wird durch die aktuelle Antennenrichtung in Worten ersetzt (z. B. north, north east, east, …).

-
    -
  • Quelle: Winkelwert im MYQTF-Eingabefeld (rechts neben dem MYQRG-Feld)
    • -
-
-

Variablen im Beacon

-

Alle Variablen können auch im automatischen Beacon (Intervall-Nachrichten) verwendet werden. Empfohlene Beacon-Konfiguration:

-
calling cq at MYQRG, loc MYLOCATOR, GL all!
-
-

Da KST4Contest QRG-Daten automatisch aus Chat-Nachrichten ausliest: Wenn andere Stationen ebenfalls KST4Contest nutzen, sehen sie die eigene QRG sofort in der QRG-Spalte der Benutzerliste.

-
-

Beispiel-Workflow mit Makros im Contest

-
    -
  1. Station in der Benutzerliste auswählen → Rufzeichen ist nun vorausgewählt.
    2. -
  2. Ctrl+1 drücken → Snippet „Hi OM, try sked?" wird als PM adressiert.
    3. -
  3. Enter drücken → Nachricht wird gesendet.
    4. -
  4. Station antwortet mit Frequenz → QRG-Spalte wird automatisch befüllt.
    5. -
  5. Ctrl+2 → Snippet „I am calling cq ur dir, pse lsn to me at 144.388" (MYQRG aufgelöst).
    6. -
  6. Enter → Gesendet.
    7. -
-

Ohne manuelle Tipparbeit, ohne Fehler, ohne Unterbrechung des CQ-Rufens.

- -
-
- - - - - - diff --git a/website/_site/manual/en/airscout-integration/index.html b/website/_site/manual/en/airscout-integration/index.html deleted file mode 100644 index dbab128..0000000 --- a/website/_site/manual/en/airscout-integration/index.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

AirScout Integration

-

AirScout Integration

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

AirScout (by DL2ALF) is a program for detecting aircraft for aircraft scatter operation. KST4Contest is tightly integrated with AirScout and shows reflectable aircraft directly in the user list.

-
-

Aircraft Scatter enables very long-distance communication on VHF and higher – even for stations with low altitude above sea level or unfavourable topographic conditions.

-
-
-

Downloading AirScout

-

Download AirScout from:

- -
-

Aircraft Data Feeds (ADSB)

-

Public aircraft data feeds on the internet are often unreliable and limited in use. A recommended alternative is the dedicated ADSB feed service provided by OV3T (Thomas):

- -

An account is required for this service. Please consider donating to Thomas – the server costs are not free!

-
-

Setting Up AirScout

-

Step 1: Configure the ADSB Feed in AirScout

-
    -
  1. Start AirScout.
    2. -
  2. Enter your OV3T feed account details (username, password, URL) in the AirScout settings.
    3. -
-

AirscoutStep1 -AirscoutStep2

-
    -
  1. Test the connection.
    2. -
-

Step 2: Enable UDP Communication for KST4Contest

-

In AirScout, enable the UDP interface:

-
    -
  • Activate the corresponding checkbox in the AirScout settings (only one checkbox needed).
    • -
  • Do not change the default ports unless there is a specific reason.
    • -
-

Step 3: KST4Contest Settings

-

In KST4Contest Preferences → AirScout Settings:

-
    -
  • Enable AirScout communication
    • -
  • Leave IP and port at their default values (unless changed)
    • -
-

AirscoutStep3{ width=85% }

-
-

Communication Between KST4Contest and AirScout (from v1.263)

-

Improvement in v1.263: KST4Contest now only sends stations to AirScout whose QRB (distance) is less than the configured maximum QRB. The query interval has been extended from 12 seconds to 60 seconds.

-

Benefits:

-
    -
  • Significantly less computation load for AirScout
    • -
  • Significantly less message traffic
    • -
  • The tracking issue with the “Show Path in AirScout” button is greatly improved
    • -
  • Less overall CPU usage
    • -
-

Additionally: The name of the KST4Contest client and AirScout server was previously hardcoded (KST and AS). From v1.263, the names configured in the Preferences are used.

-
-

Multiple KST4Contest Instances and AirScout

-
-

Note: If multiple KST4Contest instances are running simultaneously and AirScout communication is enabled on both, AirScout will respond to both instances.

-
-

This is not a problem if:

-
    -
  • Both instances use the same locator, or
    • -
  • Both instances have different login callsigns.
    • -
-

Otherwise, it may result in incorrect AP data.

-
-

AP Column in the User List

-

After setup, an AP column appears in the user list showing up to two reflectable aircraft per station.

-

Example display:

- - - - - - - - - - - - - - - - - -
StationAP Info
DF9QX2 Planes: 0 min / 0 min, 100% each
F5DYD2 Planes: 14 min / 31 min, 50% each
-

AP information is also available in the private messages window.

-

The percentage indicates the reflection potential (aircraft size, altitude, distance).

-
-

AP Variables in Messages

-

Aircraft data can be inserted directly into messages:

-
    -
  • FIRSTAP → e.g. a very big AP in 1 min
    • -
  • SECONDAP → e.g. Next big AP in 9 min
    • -
-

Details: Macros and Variables

-
-

“Show Path in AirScout” Button

-

In the user list there is a button with an arrow showing the direction (QTF) to the selected station. Clicking it maximises AirScout and shows the path with reflectable aircraft to the selected contact.

- -
-
- - - - - - diff --git a/website/_site/manual/en/changelog/index.html b/website/_site/manual/en/changelog/index.html deleted file mode 100644 index fa0cbf1..0000000 --- a/website/_site/manual/en/changelog/index.html +++ /dev/null @@ -1,346 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Changelog

-

Changelog

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

Version history of KST4Contest / PraktiKST.

-
-

For the latest changelog, please refer to GitHub. The previous changelog is below.

-

v1.41

-

Station Map, Performance, Responsive UI

-

New:

-
    -
  • Station Map: Interactive OpenStreetMap-based map showing the geographic position of all active chat members. Includes station markers, antenna beam cone, connection line to the selected station, Maidenhead grid overlay, and a path profile chart with terrain elevation analysis (Fresnel zones, horizon detection). Terrain data from Copernicus GLO-30, Open-Meteo API, or offline DEM import. Aircraft scatter path analysis integrated. Works in AppImage and Flatpak without external CDN access (local tile proxy, bundled Leaflet.js).
    • -
-

Changed:

-
    -
  • Message table limit raised to 30,000: Chat and message tables are capped at 30,000 entries. Older messages are automatically discarded, keeping performance stable during multi-day contest operations.
    • -
  • Screen-aware window sizing: On startup, the main window is sized to fit the current screen. If KST4Contest was last used on a larger monitor, the window is automatically scaled down. The UI layout is more compact and responsive on smaller screens.
    • -
-
-

v1.40 (2026-02-16)

-

Major Feature Release: Score System, AP Timeline, Win-Test, PSTRotator

-

New:

-
    -
  • Chatmember Score System: Every chat member is automatically scored based on antenna direction, activity time, message count, active bands, frequencies, sked direction (degrees), and other factors. Top candidates are highlighted in a dedicated list.
    • -
  • AP Timeline: For each minute of possible aircraft arrival, up to 4 highly-scored stations are shown that should be workable. Aircraft with the highest potential are preferred over the fastest arrival. Chat members whose antenna is not pointing towards you are shown transparently.
    • -
  • Win-Test Support (Beta since v1.31, now fully configurable): Log synchronisation, frequency parsing and sked handover via UDP fully integrated. Can be enabled/disabled in Preferences.
    • -
  • PSTRotator Interface (Beta since v1.31, now fully configurable): Rotator position updates directly from KST4Contest. Can be enabled/disabled in Preferences.
    • -
  • QSO Sniffer: Messages from configurable callsign lists are automatically forwarded to the PM window.
    • -
  • Band Alert for logged stations: When a station is logged, a hint appears if that station has another active band that you are also QRV on.
    • -
  • Sked Reminder ALERT: A sked alarm with automatic messages in configurable intervals (2+1 / 5+2+1 / 10+5+2+1 minutes before the sked) can be set up for each chat member, plus acoustic and visual notification.
    • -
  • Load chat history on startup: Chat server history is loaded on connect to immediately see active members and recent messages.
    • -
  • Skedfail button: In the FurtherInfo panel, a sked failure can be marked for a chat member, which lowers their priority score.
    • -
-

Changed:

-
    -
  • AP notes added to internal DX cluster spots.
    • -
  • Chat member table scrolling follows the current message selection automatically.
    • -
  • Generic auto-reply and QRG auto-reply now fire a maximum of once every 45 seconds per callsign (prevents spam and message ping-pong).
    • -
  • New saveable settings: ServerDNS/Port, PSTRotator interface, Win-Test interface, callsign sniffer, Dark Mode on by default.
    • -
  • Date column removed from chat table (time only – saves space).
    • -
-

Fixed:

-
    -
  • User list now automatically sorted on every new member sign-on.
    • -
  • Posonpill messages now terminate exactly one client instance (no longer affects all instances or wtKST).
    • -
  • wtKST: crash on KST4Contest disconnection fixed.
    • -
  • Multiple issues with callsign suffixes like /p, -2, etc. fixed throughout.
    • -
  • QTFDefault was not saved correctly → fixed.
    • -
  • AirScout watchlist (ASWATCHLIST) was not being updated → fixed.
    • -
  • Dark Mode: QRG fields not displayed at full size → fixed.
    • -
  • Version number display corrected.
    • -
-
-

v1.31 (2025-12-13)

-

Win-Test + PSTRotator Beta, QSO Sniffer, DNS Hotfix

-

New:

-
    -
  • Win-Test support (Beta, not yet deactivatable): Log synchronisation and frequency parsing.
    • -
  • PSTRotator support (Beta, not yet deactivatable).
    • -
  • QSO Sniffer: Messages from configurable callsigns are forwarded to the PM window.
    • -
-

Changed:

-
    -
  • DNS server changed: From www.on4kst.info to www.on4kst.org (hotfix). The DNS server is now configurable in Preferences.
    • -
-

Fixed:

-
    -
  • Endless loop in error case freezes the client → fixed.
    • -
-
-

v1.266 (2025-10-03)

-

AirScout Fix for Callsigns with Suffix

-

Fixed:

-
    -
  • AirScout interface did not work when the login callsign contained a suffix (e.g. 9A1W-2). AirScout cannot handle this format – only the base callsign without suffix is now passed to AirScout.
    • -
-

(Bug reported and tested by 9A2HM / Kreso – many thanks!)

-
-

v1.265 (2025-09-28)

-

Direction Buttons Stay Coloured When Active

-

Fixed:

-
    -
  • Direction buttons (N / NE / E etc.) now keep their highlight colour when activated, making the active state immediately visible.
    • -
-
-

v1.264 (2025-08-02)

-

Simplelogfile: Improved Callsign Recognition

-

Fixed:

-
    -
  • Callsigns like S53CC, S51A, etc. were not being marked as worked in the SimpleLogFile interpreter → recognition pattern improved.
    • -
-

(Bug reported by Boris, S53CC – thank you!)

-
-

v1.263 (2025-06-08)

-

AirScout Communication and Login Name

-

Changed:

-
    -
  • AirScout communication fundamentally revised: Only stations with QRB < max-QRB are now sent to AirScout.
    • -
  • Query interval extended from 12 seconds to 60 seconds.
    • -
  • Significantly less computation load and message traffic → more stable AirScout tracking.
    • -
  • Name of the AS client and AS server is now configurable from the Preferences (was previously hardcoded to “KST” / “AS”).
    • -
-

Fixed:

-
    -
  • “Track in AirScout” button was very sluggish → greatly improved by new communication logic.
    • -
  • Name in chat is now saveable (bug fixed).
    • -
  • Visual corrections before and after login.
    • -
  • Bug fixed that was reported by 9A2HM (Kreso).
    • -
-
-

v1.262 (2025-05-21)

-

Freeze Fix for Early Message Delivery

-

Fixed:

-
    -
  • ON4KST sometimes delivers messages before login is complete. This caused errors in the message processing engine → now fixed.
    • -
-
-

v1.26 (2025-05)

-

Multi-Channel Login and Dark Mode

-

New:

-
    -
  • Dark Mode: Toggle via Window → Use Dark Mode.
    • -
  • Multi-channel login: Simultaneous login to two chat categories.
    • -
  • Opposite station multi-callsign login tagging: Support for stations with multiple callsigns.
    • -
-

Changed:

-
    -
  • Colouring mechanism revised: Colours can now be customised via CSS.
    • -
-

Fixed:

-
    -
  • Station tagging completely revised and corrected.
    • -
-
-

v1.251 (2025-02)

-

Bugfix for UDP Broadcast Spot Info

-

Fixed:

-
    -
  • Problem reading UDP broadcast spot information fixed (reported by Steve Clements – thank you!).
    • -
  • Station tagging (further improved).
    • -
-
-

v1.25 (2025-02)

-

Wishlist Time

-

New:

-
    -
  • New settings tab: Messagehandling -
      -
    • Auto-reply to incoming messages configurable.
      • -
    • Automatic reply with own CQ QRG when someone asks for it.
      • -
    • Configurable default filter for the userinfo window (for Gianluca :-) ).
      • -
    -
    • -
  • Coloured PM rows: New private messages appear red and fade every 30 seconds from yellow to white (idea by IU3OAR, Gianluca).
    • -
-

Fixed:

-
    -
  • Stations with suffixes like “-2” and “-70” were not being marked as worked → now ignored, station is correctly marked.
    • -
-
-

v1.24 (2024-11)

-

Wishlist + DX Cluster Spots

-

New:

-
    -
  • Button to open the QRZ.com profile of the selected station.
    • -
  • Button to open the QRZ-CQ profile of the selected station.
    • -
  • DX Cluster Server integration: Direction warnings are sent as spots to the logging software (when QRG is known).
    • -
-

(Coloured PM row feature also added – tnx Gianluca)

-
-

v1.23 (2024-10)

-

Built-in DX Cluster Server

-

New:

-
    -
  • KST4Contest now contains a built-in DX cluster server.
    • -
  • Generates DX cluster spots and sends them to the logging software when a direction warning is triggered and a QRG is known.
    • -
  • Spotter callsign must differ from the contest callsign (for correct filtering in the logging software).
    • -
-

(Idea by OM0AAO, Viliam Petrik – thank you!)

-
-

v1.22 (2024-05)

-

Usability Improvements and AirScout Button Fix

-

New:

-
    -
  • New variables (tnx OM0AAO, Viliam Petrik): -
      -
    • MYLOCATORSHORT
      • -
    • MYQRGSHORT
      • -
    • QRZNAME
      • -
    -
    • -
-

Changed:

-
    -
  • Send field focus: After clicking a callsign in the user list, the send field immediately receives focus – no double-click needed (tnx Gianluca).
    • -
-

Fixed:

-
    -
  • Worked-station filter is now live: Worked stations disappear immediately when the filter is activated (tnx Gianluca).
    • -
  • QRB sorting was lexicographic → now numeric (tnx Alessandro Murador).
    • -
  • AirScout “Show Path” button: Click now maximises AirScout and correctly shows the path.
    • -
-
-

v1.21 (2024-04)

-

Usability Improvements

-

Changed:

-
    -
  • Window sizes and divider positions are saved in the configuration file when clicking “Save Settings” and restored on startup.
    • -
  • Filter section as flowpane → better display on smaller screens.
    • -
-
-

v1.2 (2024-04)

-

Band Selection and NOT-QRV Tags

-

New:

-
    -
  • Band selection: Selectable in Preferences which bands are active. Only buttons and fields for selected bands appear in the UI. Save and restart required.
    • -
  • NOT-QRV tags per station and band: Stations can be marked as “not QRV” for each band. Combinable with the user list filter.
    • -
  • QTF arrow: The “Show path in AS” button now shows an arrow with the QTF of the selected station.
    • -
-
-

Earlier Versions

-

v1.1

-

First publicly released version. Core features:

-
    -
  • Worked marking via Simplelogfile and UDP
    • -
  • Sked direction highlighting
    • -
  • QRG detection
    • -
  • Text snippets and shortcuts
    • -
  • AirScout interface (first version)
    • -
  • Interval beacon
    • -
  • PM catching for public messages containing your own callsign
    • -
  • Update notification service
    • -
-
-

Planned Features

-
    -
  • MYQTF variable (own antenna direction as text)
    • -
  • Lifetime for worked status (automatic reset) ✅ Implemented in v1.40 (3-day lifetime, no manual reset needed anymore)
    • -
  • Filtering the “Cluster & QSO of others” window to own QTF
    • -
  • Further topography-based calculations for direction warnings
    • -
- -
-
- - - - - - diff --git a/website/_site/manual/en/configuration/index.html b/website/_site/manual/en/configuration/index.html deleted file mode 100644 index 6515c3b..0000000 --- a/website/_site/manual/en/configuration/index.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Configuration

-

Configuration

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

After the first start, the settings window opens – this is the central starting point for all configuration. It is recommended to keep the settings window open during operation (e.g. to quickly toggle the beacon on and off).

-
-

Important: Always click “Save Settings” after any change! Settings are stored in ~/.praktikst/preferences.xml on Linux and in %USERPROFILE%\.praktikst\preferences.xml (or C:\Users\<Username>\.praktikst\preferences.xml) on Windows. From v1.21 onwards, window sizes and divider positions are also saved when you click Save.

-
-
-

Station Settings

-

Station Settings

-

Login and Chat Categories

-

Enter your ON4KST chat credentials here (callsign and password). -Also, select the primary chat category (e.g., IARU Region 1 VHF/Microwave).

-

With the option for a second chat (Multi-Channel Login), you can log in to another category simultaneously (e.g., UHF/SHF). Both chats will then be monitored in parallel. You can optionally specify a different login name for the second chat (useful for Opposite Station Multi-Callsign Logging).

-

Callsign and Locator

-

Enter your own callsign and Maidenhead locator (6 characters, e.g., JN49IJ). These values are needed for distance and direction calculations.

-

Active Bands

-

Use the “my station uses band” checkboxes to select the active bands. Buttons and table rows will only appear in the user interface for selected bands. The software must be restarted after making changes.

-

Antenna Beamwidth

-

Enter a realistic value for your antenna’s beamwidth (in degrees). This value is used for the Sked Direction Highlighting. A test value of 50° has proven effective; DM5M uses quads with 69°.

-
-

Do not enter fantasy values – the direction calculations will become useless.

-
-

Default Maximum QRB

-

Maximum distance (in km) for which direction warnings should be triggered. A realistic value for DM5M is 900 km. Stations farther away are ignored for highlighting purposes.

-
-

Server Settings (from v1.31)

-

The chat server DNS and port are configurable in the Preferences:

-
    -
  • Server DNS: Default www.on4kst.org (changed from www.on4kst.info in v1.31 hotfix).
    • -
  • Port: Default port of the ON4KST server.
    • -
-

A change is only needed if the server moves or an alternative endpoint is used.

-
-

Log Sync Settings

-

Three methods are available for automatically marking worked stations. Details: Log Synchronisation.

-

Universal File Based Callsign Interpreter (Simplelogfile)

-

Interprets any log file using regex for callsign patterns. No band information is available. Suitable as a fallback or for log programs that are not directly supported.

-

Network Listener for Logger’s QSO UDP Broadcast

-

Recommended method. KST4Contest listens for UDP packets sent by the logging software to the broadcast address when a QSO is saved. Stations are marked with band information. UDP port: default 12060. (Used by UCXLog, N1MM+, QARTest, DXLog.net, etc.).

-

Win-Test Network Listener (Additional UDP Listener)

-

A dedicated network listener for Win-Test. KST4Contest receives and processes Win-Test-specific UDP packets (including sked handovers) on the configured port.

-
-

TRX Sync Settings

-

Receives the current transceiver frequency from the logging software via UDP. This enables the automatic population of the MYQRG variable. Useful for:

-
    -
  • Quickly inserting your own QRG into chat messages.
    • -
  • Automatic CQ beacon with current frequency.
    • -
-
-

Note for multi-setup: When running two logging programs on two computers but only one KST4Contest instance, only one logging program should send frequency packets. KST4Contest cannot distinguish between sources.

-
-
-

AirScout Settings

-

Configuration of the interface to AirScout for aircraft scatter detection. Details: AirScout Integration.

-
-

Notification Settings

-

Three notification types are available:

-
    -
  1. Simple sounds: TADA sound for incoming messages, tick for sked direction detection, etc.
    2. -
  2. CW announcement: The callsign of a station sending a private message is output as a CW signal.
    3. -
  3. Phonetic announcement: The callsign is pronounced phonetically.
    4. -
-
-

Shortcut Settings

-

Configuration of quick-access buttons that appear directly in the main window. Clicking a button inserts the configured text into the send field. All variables can be used.

-
-

Snippet Settings

-

Text snippets are accessible via:

-
    -
  • Right-click on a callsign in the user list
    • -
  • Right-click in the CQ message table
    • -
  • Right-click in the PM message table
    • -
  • Keyboard shortcuts: Ctrl+1 to Ctrl+0 for the first 10 snippets
    • -
-

If a callsign is selected in the user list, the snippet is addressed as a direct message: -/CQ CALLSIGN <snippet text>

-
-

Beacon Settings

-

Configuration of an automatic interval beacon in the public chat channel. Recommended: use the MYQRG variable in the text so the current frequency is always up to date. Interval and text are freely configurable.

-
-

Tip: Enable the beacon when calling CQ and quickly disable it in the settings window when not calling.

-
-
-

Messagehandling Settings (from v1.25)

-

New settings section with the following options:

-
    -
  • Auto-reply to all incoming messages: Configurable automatic reply to private messages.
    • -
  • Auto-reply with own CQ QRG: When someone asks for your QRG, KST4Contest automatically replies with the content of the MYQRG variable.
    • -
  • Default filter for the userinfo window: Pre-configured message filter for the station info window (for Gianluca :-) ).
    • -
-
-

Win-Test Network Listener (from v1.31)

-

A dedicated listener for Win-Test-specific UDP packets. Enables:

-
    -
  • 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.
    • -
-

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.
    • -
-
-

Note: The Win-Test listener is an additional listener – the standard QSO UDP broadcast listener on port 12060 remains independent.

-
-
-

PSTRotator Settings (from v1.31)

-

KST4Contest can control antenna direction via PSTRotator.

-

Settings:

-
    -
  • Enable/Disable: Checkbox in Preferences (from v1.40).
    • -
  • IP address: IP address of the PSTRotator computer (default: 127.0.0.1 when running on the same PC).
    • -
  • Port: Communication port of PSTRotator.
    • -
-
-

Note: After clicking a direction button, KST4Contest waits briefly for the rotator response. With slow rotors (e.g. SPID) there may be a small delay.

-
-
-

Sniffer Settings (from v1.31)

-

The QSO sniffer filters chat messages from configurable callsigns and forwards them to the PM window.

-

Settings:

-
    -
  • Callsign list: Comma-separated list of callsigns whose messages are always forwarded to the PM window.
    • -
-

Use case: Keep track of important stations (e.g. DX expeditions or trusted contest allies) without constantly monitoring the main chat.

-
-

Worked Station Database Settings

-

The internal worked database contains:

-
    -
  • Worked status of all stations (per band)
    • -
  • NOT-QRV tags (since v1.2)
    • -
-

From v1.40: Entries have an automatic lifetime of 3 days – manually resetting before each contest is no longer strictly necessary. For a full reset, the “Reinitialize” button is still available.

-
-

Dark Mode (from v1.26)

-

Toggle via the menu: Window → Use Dark Mode. The colors can be individually customized via CSS.

-
-

Saving Settings

-

Click “Save Settings” after every change! Without saving, all changes will be lost on the next start.

-
    -
  • Storage location: ~/.praktikst/preferences.xml on Linux and %USERPROFILE%\.praktikst\preferences.xml (or C:\Users\<Username>\.praktikst\preferences.xml) on Windows
    • -
  • From v1.21: Window sizes and divider positions are also saved.
    • -
  • If you encounter problems: delete the configuration file → KST4Contest will create a new one with default values.
    • -
- -
-
- - - - - - diff --git a/website/_site/manual/en/dx-cluster-server/index.html b/website/_site/manual/en/dx-cluster-server/index.html deleted file mode 100644 index 31c4d12..0000000 --- a/website/_site/manual/en/dx-cluster-server/index.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Built-in DX Cluster Server

-

Built-in DX Cluster Server

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

From version 1.23, KST4Contest includes a built-in DX cluster server. It sends spots directly to the logging software whenever a direction warning is triggered.

-

(Idea by OM0AAO, Viliam Petrik – thank you!)

-
-

What is the Built-in DX Cluster Server For?

-

When KST4Contest detects that a station is requesting a sked from your direction and a QRG is known, it automatically generates a DX cluster spot and feeds it directly to the logging software’s cluster client / band map.

-

The logging software then displays the spot in the band map. Clicking the spot sets the transceiver’s frequency and mode directly – without any manual typing.

-
-

Setup

-

In KST4Contest

-

In Preferences → DX Cluster Server Settings:

-
    -
  1. Enter the port of the internal server (e.g. 7300 or 8000 – must match the logging software).
    2. -
  2. Enter a spotter callsign – this must be a different callsign than your contest callsign! -
      -
    • Reason: Logging programs filter spots from your own callsign as “already worked”. If the spotter uses the same callsign, the spots will not be displayed.
      • -
    -
    3. -
  3. Enter the assumed MHz: For frequency references like “.205” in the chat, KST4Contest needs to decide whether 144.205, 432.205 or 1296.205 is meant. For single-band contests, simply enter the corresponding band centre. Full frequency references like “144.205” or “1296.338” in the chat are always correctly identified.
    4. -
-

In UCXLog

-
    -
  • Configure a DX cluster server connection: -
      -
    • Host: 127.0.0.1 (or IP of the KST4Contest computer)
      • -
    • Port: As configured in KST4Contest
      • -
    • Password: can be left empty
      • -
    -
    • -
  • Use the “Send a test message to your log” button to test the connection.
    • -
-

In N1MM+

-

Similar settings:

-
    -
  • Host: 127.0.0.1 (or IP of the KST4Contest computer)
    • -
  • Port: As configured in KST4Contest
    • -
-
-

How It Works

-

A spot is generated when both conditions are met:

-
    -
  1. A direction warning has been triggered (station is making a sked in your direction).
    2. -
  2. The station’s QRG is known (read from the chat or manually entered).
    3. -
-

The generated spot contains:

-
    -
  • Station’s callsign
    • -
  • Frequency
    • -
  • Spot time
    • -
-

The logging software can then display the spot in the band map and tune the TRX to that frequency with a mouse click.

-
-

Multi-Computer Setup

-

If KST4Contest runs on a separate computer (not the logging computer):

-
    -
  • Host in the logging software: IP of the KST4Contest computer (not 127.0.0.1)
    • -
  • Same configuration as for the QSO UDP broadcast packets (see Log Synchronisation)
    • -
-
-

Tested Logging Software

-
    -
  • UCXLog ✓
    • -
  • N1MM+ ✓
    • -
-

Further test reports are welcome – please send by email to DO5AMF.

- -
-
- - - - - - diff --git a/website/_site/manual/en/features/index.html b/website/_site/manual/en/features/index.html deleted file mode 100644 index 67bef5d..0000000 --- a/website/_site/manual/en/features/index.html +++ /dev/null @@ -1,294 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Features

-

Features

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

Overview of all main features of KST4Contest.

-
-

Sked Direction Highlighting

-

One of the core features: when a station makes a sked request towards your direction, it is highlighted green and bold in the user list.

-

How does it work?

-

The calculation is based on the following logic:

-
    -
  • When station A sends a sked request to station B, it is assumed that A is pointing its antenna towards B.
    • -
  • If the resulting direction from A to your own station is within half the beamwidth of your own antenna, A is highlighted.
    • -
-

Example (beamwidth 69°, half-angle 34.5°):

- - - - - - - - - - - - - - - - - - - - - - - - - -
SituationResult for DO5AMF in JN49
Sked from F5FEN → DM5M✅ Highlighted (F5FEN points towards DM5M, close to JN49)
Sked from DM5M → F5FEN✅ Highlighted (DM5M replies towards F5FEN)
F1DBN is uninvolved❌ No highlighting
DO5AMF/P (different location)❌ No highlighting for sked reply
-

The calculation does not include topographic path calculations – this is a deliberate simplification. It may be added in a future version.

-
-

Configuration: Configuration – Antenna Beamwidth

-
-
-

Sked Direction Spots (Built-in DX Cluster)

-

From v1.23: Direction warnings are forwarded as DX cluster spots to the logging software when a QRG is known. Details: DX Cluster Server.

-
-

QRG Detection (QRG Reading)

-

KST4Contest processes every line of text flowing through the channel and automatically extracts frequency references. These are displayed in the user list in the QRG column.

-

Recognised formats: 144.205, 432.088, .205 (with configured band assumption), etc.

-

Benefit: Without asking, you can directly look up a station’s calling frequency and decide whether a contact is possible.

-
-

Worked Marking

-

Worked stations are visually marked in the user list – per band. Based on Log Synchronisation via UDP or Simplelogfile.

-

Reset the database before each contest: Configuration – Worked Station Database Settings.

-
-

NOT-QRV Tags (from v1.2)

-

When a station indicates it is not QRV on a specific band, this can be manually marked:

-
    -
  1. Select the station in the user list.
    2. -
  2. Right-click → Set NOT-QRV for the appropriate band.
    3. -
-

These tags are stored in the internal database and persist after a KST4Contest restart. Can be reset via the settings.

-

Benefit: Prevents repeated sked requests on bands where the station is not active – saves time for both sides.

-
-

Direction Filter

-

Shows only stations in the user list that are located in a specific direction. Toggle using the N / NE / E / SE / S / SW / W / NW buttons or by entering degrees manually.

-

Useful: While calling CQ in a specific direction, only show stations in that direction.

-
-

Distance Filter

-

Hide stations beyond a maximum distance. The “Show only QRB [km] <=” button is a toggle.

-
-

Worked and NOT-QRV Filter

-

Toggle buttons (one per band) to hide already-worked stations and/or NOT-QRV-tagged stations. The filter takes effect immediately without manually reactivating (live since v1.22).

-
-

Coloured PM Rows (from v1.25)

-

New private messages appear in red. The colour fades every 30 seconds from yellow to white – like a rainbow fade. This makes it immediately clear how recent a message is.

-

(Idea by IU3OAR, Gianluca Costantino – thank you!)

-
-

PM Catching

-

Some users accidentally post direct messages publicly, e.g.:

-
(DM5M) pse ur qrg
-
-

KST4Contest detects such messages that contain your own callsign and automatically sorts them into the private messages table. No messages are missed this way.

-
-

Multi-Channel Login (from v1.26)

-

Simultaneous login to two chat categories (e.g. 144 MHz and 432 MHz). Both chats are monitored in parallel.

-
-

Dark Mode (from v1.26)

-

Toggle via: Window → Use Dark Mode

-

For individual colour adjustments: edit the CSS file (path in the program settings).

-
-

Opposite Station Multi-Callsign Login Tagging (from v1.26)

-

Support for stations that are active in the chat with multiple callsigns simultaneously (e.g. expedition setups).

-
-

QRZ.com and QRZ-CQ Profile Buttons (from v1.24)

-

For selected stations in the user list, there are direct buttons to open the QRZ.com profile and the QRZ-CQ profile in the browser.

-
-

Sked Reminders with ALERT (from v1.40)

-

A sked reminder service with automatic messages can be activated for each chat member. Configurable interval patterns:

-
    -
  • 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.
    • -
-

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.

-

Activate from the FurtherInfo panel of the corresponding station.

-
-

QSO Sniffer (from v1.31)

-

The QSO sniffer monitors the chat for messages from a configurable callsign list and automatically forwards them to the PM window. This prevents relevant messages from being lost in the general chat traffic.

-

Configuration: Configuration – Sniffer Settings

-
-

Win-Test Integration (from v1.31, fully configurable from v1.40)

-

KST4Contest fully supports Win-Test as a logging programme:

-
    -
  • 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.
    • -
-

Details: Configuration – Win-Test Network Listener

-
-

PSTRotator Interface (from v1.31, fully configurable from v1.40)

-

KST4Contest can control antenna direction directly via PSTRotator. When a station is selected in the user list, the rotator can automatically be turned to the QTF of the selected station.

-

Configuration: Configuration – PSTRotator Settings

-
-

Band Alert for New QSOs (from v1.40)

-

When a station is logged, KST4Contest automatically checks whether that station has shown any other active bands in the chat that you are also QRV on. If so, a hint alert appears so no multi-band opportunity is missed.

-
-

Worked Tag Lifetime (from v1.40)

-

Worked stations are automatically removed from the database after 3 days. Manually resetting the worked database before each contest is therefore no longer strictly necessary – the database keeps itself up to date.

-
-

Chatmember Score System / Priority List (from v1.40)

-

KST4Contest automatically calculates a priority score for each active chat member. The score is derived from:

-
    -
  • Antenna direction of the remote station (is it pointing towards me?)
    • -
  • QRB (distance)
    • -
  • Activity time and message count
    • -
  • Active bands and frequencies
    • -
  • AP availability (AirScout)
    • -
  • Sked direction (degrees)
    • -
  • Sked success rate and skedfail markings
    • -
-

The top candidates are highlighted in a dedicated priority list, helping you not to miss the most important contacts during contest stress.

-

Stations with a failed sked can be marked using the Skedfail button in the FurtherInfo panel – this temporarily lowers their score.

-
-

AP Timeline (from v1.40)

-

A visual timeline shows up to 4 highly-scored stations per minute slot that should be workable via aircraft scatter. Prioritisation criteria:

-
    -
  • Highest reflection potential is preferred (not necessarily the fastest arrival).
    • -
  • Stations towards which your antenna is not pointing are shown transparently.
    • -
-

This gives the contest operator a quick overview of which stations will be reachable via which aircraft and at what time.

-
-

Interval Beacon

-

Automatic CQ messages in the public channel at a configurable interval. Recommended: use the MYQRG variable so the current frequency is always accurate. Details: Configuration – Beacon Settings.

-
-

Simplelogfile

-

File-based log evaluation using regex. Details: Log Synchronisation.

-
-

Cluster & QSO of Others

-

A separate window showing the QSO flow between other stations. Particularly interesting during quieter night-time hours of a contest. This window can be minimised when not needed. Future plan: filtering to stations in your selected QTF.

-
-

Station Map (from v1.41)

-

An interactive OpenStreetMap-based map showing the geographic position of all active chat members.

-

Features:

-
    -
  • Station markers with callsign labels, coloured by activity and sked state
    • -
  • Antenna beam cone visualisation for the own station
    • -
  • Connection line to the currently selected station
    • -
  • Maidenhead grid overlay (QRA locator grid)
    • -
  • Path profile chart: Terrain elevation cross-section between own station and the selected station, including Fresnel zone analysis and obstruction/horizon detection
    • -
  • Multiple terrain data sources: Copernicus GLO-30 (high-resolution DEM), Open-Meteo API, synthetic fallback, and offline DEM import for air-gapped use
    • -
  • Aircraft scatter path analysis integrated with the terrain data
    • -
-

The map works in packaged environments (AppImage, Flatpak) without internet access to external CDNs: map tiles are fetched via a local tile proxy, and the Leaflet.js library is bundled inside the application.

-
-

Optimised Message Handling / 30,000 Message Limit (from v1.41)

-

The internal chat and message tables are capped at 30,000 entries. Older messages are automatically discarded when the limit is reached. This keeps memory usage and rendering performance stable during multi-day contest operations.

-
-

Screen-Aware Window Sizing (from v1.41)

-

On startup, KST4Contest calculates a screen-aware size for the main window:

-
    -
  • The stored window size from the previous session is used – but never larger than the current screen.
    • -
  • If KST4Contest was last used on a larger monitor, the window is automatically scaled down to fit the current display without clipping.
    • -
  • The UI layout is more compact and responsive on smaller screens, showing the same information in less space.
    • -
-

This prevents unusable oversized windows when switching between machines or monitors.

- -
-
- - - - - - diff --git a/website/_site/manual/en/home/index.html b/website/_site/manual/en/home/index.html deleted file mode 100644 index 7116a82..0000000 --- a/website/_site/manual/en/home/index.html +++ /dev/null @@ -1,249 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

KST4Contest – User Manual

-

KST4Contest – User Manual

-
-

You are reading the English version | Deutsche Version

-
-

KST4Contest is a desktop client for the ON4KST Chat, developed for VHF, UHF and SHF contest operation. It brings chat, candidate selection, sked planning, aircraft scatter data and external station software together in a single operating interface.

-

KST4Contest is developed by DO5AMF (Marc Fröhlich), operator at DM5M and (since May 2025) DN9APW (Philipp Wagner). The source code is publicly available on GitHub.

-
-

Why use a dedicated ON4KST client?

-

During a contest, the ON4KST Chat provides a considerable amount of information: active stations, locators, frequencies, sked requests and indications of current activity. The actual problem is not seeing this data. It is turning it into the next useful contact in time.

-

KST4Contest evaluates the available information, puts it into context and presents it as part of a contest-oriented workflow. This includes antenna direction, distance, known bands and frequencies, worked status, chat activity and aircraft scatter timing.

-

The program does not decide which QSO is actually possible. Priority scores, the AP timeline and visual highlights are decision aids. The final judgement remains with the operator – not least because even a very convincing computer screen cannot complete a radio contact.

-
-

How KST4Contest supports contest operation

-
    -
  • -

    Observe and organise chat activity: KST4Contest can display two ON4KST chat categories at the same time. Messages, frequency information and known band activity are assigned to the corresponding stations.

    -
    • -
  • -

    Reduce the station list: Direction, distance, worked and NOT-QRV filters help limit the user list to stations that are relevant to the current operating situation.

    -
    • -
  • -

    Prioritise candidates: The score system evaluates active chat members using several known criteria. The currently most relevant candidates are also shown in a separate priority list.

    -
    • -
  • -

    Prepare skeds and keep them visible: Sked reminders, automatic advance messages and the AP timeline help prevent scheduled contacts from disappearing somewhere between chat, logging and ongoing CQ operation.

    -
    • -
  • -

    Include aircraft scatter information: The AirScout interface brings suitable aircraft and expected reflection times into candidate evaluation and sked planning.

    -
    • -
  • -

    Connect the logger and station equipment: KST4Contest synchronises worked stations and frequency information with supported logging software. It also provides interfaces for Win-Test, PSTRotator and a built-in DX Cluster server.

    -
    • -
  • -

    Display stations and radio paths: The station map shows active chat members, locator squares, antenna directions and the path to the selected station. A terrain profile can also be calculated for selected paths.

    -
    • -
-

These functions share information. A detected frequency can indicate an active band, worked status comes from the logger, aircraft scatter data adds timing information and the resulting score affects the priority list. Missing or outdated input data can therefore affect the result as well.

-
-

Requirements

-

A registered ON4KST account is required. Registration and login are available from the official ON4KST login page.

-

English is the official language of the ON4KST Chat. This also applies when communicating with stations from your own country. Common amateur radio abbreviations such as pse, agn, qrg, dir, rrr, tnx and 73 are normal and usually considerably faster than carefully written prose.

-

Downloads, supported operating systems and installation methods are described in Installation.

-
-

Manual version

-

This manual describes the stable release v1.41.1.

-

Features or changes that are only available in the current development version are explicitly marked as Nightly / v1.42. If no such label is present, the description refers to the stable release.

- -

For contest operation, the stable release is generally the appropriate choice. Nightly builds contain newer fixes and features, but may change between builds. They are useful when a particular change needs testing. Trying one for the first time ten minutes before a contest is less useful.

-
-

Quick navigation

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PageContents
InstallationON4KST account, downloads, installation and updates
ConfigurationLogin, station, bands, user interface and external connections
Log SynchronisationSimplelogfile, UCXLog, N1MM+, QARTest, DXLog.net and Win-Test
AirScout IntegrationConnecting AirScout and evaluating aircraft scatter timing
DX Cluster ServerPassing detected opportunities to logging software
FeaturesOperation, reasoning and limitations of individual functions
Macros and VariablesReusable messages, shortcuts and automatically substituted values
User InterfaceInterface layout and operation during a contest
ChangelogReleases, Nightly changes and resolved issues
-
-

Contact and support

- -

Reporting a bug

-

A problem is considerably easier to reproduce when the report contains at least:

-
    -
  1. the KST4Contest version,
    2. -
  2. the operating system and installation method,
    3. -
  3. the exact steps leading to the problem,
    4. -
  4. the expected and observed behaviour,
    5. -
  5. a screenshot where appropriate,
    6. -
  6. the error log file.
    7. -
-

The error log is stored at:

- - - - - - - - - - - - - - - - - -
Operating systemPath
Linux / macOS~/.praktiKST/kst4contest-errors.log
WindowsC:\Users\<YourName>\.praktiKST\kst4contest-errors.log
-

Please inspect the file briefly before uploading it. An error log mainly contains technical information, but depending on the problem it may also include local file paths or other contextual data.

-

Some file and directory names still use the technical name praktiKST. They refer to the same program.

-
-

Acknowledgements

-

KST4Contest has benefited considerably from feedback gathered during actual contest operation.

-

Special thanks go to Gianluca Costantino (IU3OAR), Alessandro Murador (IZ3VTH), Reczetár István (HA1FV), Viliam Petrik (OM0AAO, DX Cluster idea), Konrad Neitzel (DC9DJ, project structure), Andreas (DO5ALF, webmaster of funkerportal.de), Franz van Velzen (PE0WGA, testing), and all other testers and contributors.

- -
-
- - - - - - diff --git a/website/_site/manual/en/index.html b/website/_site/manual/en/index.html deleted file mode 100644 index 87580b2..0000000 --- a/website/_site/manual/en/index.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - KST4Contest English Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

English Manual

-

The manual is maintained centrally in GitHub and published as Wiki, PDF and online documentation.

-
- -
-
- - - - - - - - - - - - - - - - - - - - - - -
-

KST4Contest – User Manual

- -

KST4Contest is a desktop client for the ON4KST Chat, developed for VHF, UHF and SHF contest operation. It brings chat, candidate selection, sked planning, aircraft scatter data and external station software together in a single operating interface.

- -
- - - -
-

Installation

- -

KST4Contest is distributed as a ready-to-run application package for Windows, Linux and macOS. The official release packages do not require a separate Java installation: the required Java runtime is already included.

- -
- - - -
-

Configuration

- -

After the first start, the settings window opens – this is the central starting point for all configuration. It is recommended to keep the settings window open during operation (e.g. to quickly toggle the beacon on and off).

- -
- - - -
-

Log Synchronisation

- -

KST4Contest automatically marks worked stations in the chat user list. Two basic methods are available:

- -
- - - -
-

AirScout Integration

- -

AirScout (by DL2ALF) is a program for detecting aircraft for aircraft scatter operation. KST4Contest is tightly integrated with AirScout and shows reflectable aircraft directly in the user list.

- -
- - - -
-

Built-in DX Cluster Server

- -

From version 1.23, KST4Contest includes a built-in DX cluster server. It sends spots directly to the logging software whenever a direction warning is triggered.

- -
- - - -
-

Features

- -

Overview of all main features of KST4Contest.

- -
- - - -
-

Macros and Variables

- -

KST4Contest offers a flexible system of text snippets, shortcuts and built-in variables that significantly speed up the chat workflow during contests.

- -
- - - -
-

User Interface

- -

The main window consists of several areas:

- -
- - - -
-

Changelog

- -

Version history of KST4Contest / PraktiKST.

- -
- - -
-
- - - - - - diff --git a/website/_site/manual/en/installation/index.html b/website/_site/manual/en/installation/index.html deleted file mode 100644 index 5874165..0000000 --- a/website/_site/manual/en/installation/index.html +++ /dev/null @@ -1,503 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Installation

-

Installation

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

KST4Contest is distributed as a ready-to-run application package for Windows, Linux and macOS. The official release packages do not require a separate Java installation: the required Java runtime is already included.

-

In practical terms, you need a supported operating system, an internet connection and an ON4KST account. That sounds manageable—and usually it is.

-

Requirements

-

ON4KST account

-

KST4Contest is an independent client for the ON4KST chat, but it does not replace the corresponding user account.

-

If you do not have an account yet, you can create one on the official ON4KST website:

- -

ON4KST specifies English as the common language for the chat. This also applies when both stations happen to share another language. During contests, the usual amateur radio abbreviations such as pse, agn, qrg, dir, rrr, tnx and 73 are widely used.

-

Using the chat and sending personal messages are covered in the user interface chapter. For the installation, the only thing that matters at this point is that the account works.

-

Screen size

-

A usable screen area of approximately 1200 × 720 pixels or more is recommended.

-

KST4Contest automatically adapts the main window to the available area of the primary screen. The application can therefore also be started on smaller displays. Less space is still less space, however: not all tables, filters and additional information can then be displayed at a useful size at the same time.

-

Java

-

The ready-made packages from the GitHub Releases do not require a separate Java installation. The required runtime is distributed with KST4Contest.

-

A Java development environment is only required if you want to build KST4Contest from source. For the AUR packages kst4contest and kst4contest-git, Java 21 and Maven are handled as build dependencies by the package manager.

-
-

Stable, Beta or Nightly?

-

KST4Contest is distributed through three development channels:

- - - - - - - - - - - - - - - - - - - - - - - - - -
ChannelIntended useClassification
StableNormal contest operationPublished version intended for regular use
BetaFocused testing before a Stable releasePre-release version with a largely defined feature set
NightlyEarly testing of new featuresCurrent development state from the main branch
-

The Stable version is recommended for normal operation.

-

Beta and Nightly builds may contain features that are not yet available in the Stable release. They may also contain unfinished workflows, changed settings or new defects. That is not an unusual failure of the release process; it is the purpose of a development channel.

-

If a function in this manual is explicitly marked as Nightly, it is not necessarily part of the current Stable release yet.

-
-

Download

-

The current Stable version is available here:

- -

The release page contains the application packages as well as the English and German PDF manuals.

-

Which package do I need?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Operating systemPackageTypical filename
Windows x64ZIP packagepraktiKST-v<version>-windows-x64.zip
Linux x86_64AppImageKST4Contest-v<version>-linux-x86_64.AppImage
Debian/Ubuntu amd64DEB packageKST4Contest-v<version>-debian-amd64.deb
Fedora/RPM x86_64RPM packageKST4Contest-v<version>-fedora-x86_64.rpm
Arch Linux x86_64Arch packageKST4Contest-v<version>-archlinux-x86_64.pkg.tar.zst
Linux with FlatpakFlatpak referencede.x08.KST4Contest.flatpakref
macOS Apple SiliconDMG for ARM64KST4Contest-v<version>-macos-arm64.dmg
macOS IntelDMG for x86_64KST4Contest-v<version>-macos-x86_64.dmg
-

Only download application packages from the official GitHub Releases, the KST4Contest Flatpak repository or the linked AUR packages. Files from other sources may have been built differently, may be outdated or may have been modified.

-
-

Installing on Windows

-

KST4Contest is distributed as a ZIP package for Windows. A conventional installer is not required.

-
    -
  1. Download praktiKST-v<version>-windows-x64.zip from the latest release.
    2. -
  2. Extract the ZIP file completely into a dedicated folder.
    3. -
  3. Open the extracted folder.
    4. -
  4. Start praktiKST.exe.
    5. -
-

Do not start the application directly from the compressed ZIP file. KST4Contest consists of several files and a bundled runtime. Windows can only use this structure reliably after the archive has been extracted completely.

-

The application settings are not stored in the extracted program directory. They are stored in your user profile:

-
%USERPROFILE%\.praktiKST\preferences.xml
-
-

This allows a new application version to be extracted into a different directory without losing the existing settings.

-
-

Installing on Linux

-

Several Linux package formats are available. The appropriate choice depends less on KST4Contest itself than on your distribution and the way you prefer to manage updates.

- - - - - - - - - - - - - - - - - - - - - - - - - -
Installation methodUseful when …
Flatpakupdates should be managed centrally and Flatpak is already in use
AppImageKST4Contest should run as a portable file without package installation
DEB/RPMthe distribution’s native package manager should be used
Arch package/AURArch Linux, Manjaro or EndeavourOS is being used
-

Flatpak

-

For most Linux users, Flatpak is the simplest way to keep KST4Contest installed and manageable through the system’s update tools. The KST4Contest repository is GPG-signed and contains the Stable, Beta and Nightly channels.

-

Installing Stable from the release file

-

Download de.x08.KST4Contest.flatpakref from the latest release and open it with the software manager provided by your desktop environment.

-

Alternatively, install it from a terminal:

-
flatpak install ./de.x08.KST4Contest.flatpakref
-
-

Adding the KST4Contest repository

-

The repository only needs to be added once:

-
flatpak remote-add --if-not-exists kst4contest \
-https://praktimarc.github.io/kst4contest/kst4contest.flatpakrepo
-
-

You can then install the Stable version:

-
flatpak install kst4contest de.x08.KST4Contest//stable
-
-

Installing Beta

-
flatpak install kst4contest de.x08.KST4Contest//beta
-
-

Installing Nightly

-
flatpak install kst4contest de.x08.KST4Contest//nightly
-
-

All three KST4Contest channels use the same application ID. Installing multiple KST4Contest channels in parallel is therefore not supported.

-

For example, to switch from Stable to Nightly:

-
flatpak uninstall de.x08.KST4Contest//stable
-flatpak install kst4contest de.x08.KST4Contest//nightly
-
-

This does not automatically remove the personal settings stored in ~/.praktiKST.

-

Installed Flatpak applications can be updated with:

-
flatpak update de.x08.KST4Contest
-
-

Depending on the desktop environment, the graphical software manager may also display or automatically install available Flatpak updates. The flatpak update command itself performs an update; it does not promise to turn up and run by itself one day.

-

AppImage

-

The AppImage does not require a conventional installation.

-
    -
  1. Download KST4Contest-v<version>-linux-x86_64.AppImage.
    2. -
  2. Open a terminal in the download directory.
    3. -
  3. Make the file executable:
    4. -
-
chmod +x KST4Contest-v<version>-linux-x86_64.AppImage
-
-
    -
  1. Start KST4Contest:
    2. -
-
./KST4Contest-v<version>-linux-x86_64.AppImage
-
-

The AppImage can then be moved to another location, such as ~/Applications.

-

Debian and Ubuntu

-

Install the DEB package with:

-
sudo apt install ./KST4Contest-v<version>-debian-amd64.deb
-
-

Alternatively, open the file with a graphical package manager.

-

Fedora and compatible RPM systems

-

Install the RPM package with:

-
sudo dnf install ./KST4Contest-v<version>-fedora-x86_64.rpm
-
-

Arch Linux: installing the release package

-

The Arch package downloaded from the GitHub Release can be installed directly:

-
sudo pacman -U KST4Contest-v<version>-archlinux-x86_64.pkg.tar.zst
-
-

Arch Linux: installing from the AUR

-

Three variants are available in the AUR:

- - - - - - - - - - - - - - - - - - - - - -
PackageContent
kst4contest-binPre-built package from the current Stable release
kst4contestStable release built locally from source
kst4contest-gitCurrent development state from the main branch
-

For most users, kst4contest-bin is the straightforward option:

-
yay -S kst4contest-bin
-
-

To build the Stable release from source:

-
yay -S kst4contest
-
-

To build the current development state:

-
yay -S kst4contest-git
-
-

All three packages provide the same application and are therefore defined as conflicting with one another. Install only one variant at a time.

-

AUR updates are included when the selected AUR helper checks for package updates, for example:

-
yay -Syu
-
-

They do not happen automatically merely because the package came from the AUR.

-
-

Installing on macOS

-
-

Best-effort support: The macOS packages are built together with the other releases, but they are not tested to the same extent as the Windows and Linux versions. Feedback is welcome; fully tested support for every macOS version and hardware variant cannot currently be guaranteed.

-
-

Apple Silicon Macs require the package marked arm64. Intel Macs require the package marked x86_64.

-
    -
  1. Download the appropriate DMG file.
    2. -
  2. Open the DMG file.
    3. -
  3. Drag KST4Contest.app into the Applications folder.
    4. -
  4. Start KST4Contest from the Applications folder or Launchpad.
    5. -
-

The application is not currently notarized by Apple. macOS may therefore block the first launch.

-

If the application came from the official GitHub Release:

-
    -
  1. Open the Applications folder in Finder.
    2. -
  2. Right-click or Control-click KST4Contest.app.
    3. -
  3. Select Open.
    4. -
  4. Confirm the launch in the dialog that appears.
    5. -
-

Alternatively, macOS may provide an Open Anyway button under System Settings → Privacy & Security.

-
-

Where are the settings stored?

-

KST4Contest stores its settings and other local working files in the user’s home directory. The application directory and the data directory are separate.

- - - - - - - - - - - - - - - - - - - - - - - - - -
Operating systemData directorySettings file
Windows%USERPROFILE%\.praktiKST\%USERPROFILE%\.praktiKST\preferences.xml
Linux~/.praktiKST/~/.praktiKST/preferences.xml
macOS~/.praktiKST/~/.praktiKST/preferences.xml
-

Note the spelling .praktiKST with an uppercase KST. Linux and macOS distinguish between uppercase and lowercase letters. .praktikst would simply be a different directory.

-

An application update does not remove this directory. Even so, creating a backup before a major version change or extensive configuration work is sensible.

-
-

Updates

-

When KST4Contest starts, it checks whether a newer Stable release is available. If it finds one, it displays an information window containing:

-
    -
  • the installed version,
    • -
  • the latest Stable version,
    • -
  • a short overview of the main changes,
    • -
  • the changelog,
    • -
  • known issues,
    • -
  • a link to the corresponding GitHub Release page.
    • -
-

KST4Contest update notification

-

The update checker does not install anything. It reports the new version and opens the platform-neutral release page. From there, you must select the appropriate package for Windows, Linux or macOS.

-

Updating Windows

-
    -
  1. Close KST4Contest.
    2. -
  2. Download the new Windows ZIP package.
    3. -
  3. Extract it into a new or empty directory.
    4. -
  4. Start the new version.
    5. -
  5. Check that the existing settings have been loaded.
    6. -
  6. Remove the old application directory only after that.
    7. -
-

The settings are preserved because they are stored under %USERPROFILE%\.praktiKST, not in the application directory.

-

Updating an AppImage

-
    -
  1. Download the new AppImage.
    2. -
  2. Make it executable.
    3. -
  3. Start the new file.
    4. -
  4. Remove the previous AppImage only after the new version works.
    5. -
-

Updating Debian and Ubuntu

-
sudo apt install ./KST4Contest-v<version>-debian-amd64.deb
-
-

Updating Fedora

-
sudo dnf upgrade ./KST4Contest-v<version>-fedora-x86_64.rpm
-
-

Updating the Arch package

-
sudo pacman -U KST4Contest-v<version>-archlinux-x86_64.pkg.tar.zst
-
-

Updating an AUR package

-

Update the installed package through the selected AUR helper, for example:

-
yay -Syu
-
-

Updating Flatpak

-
flatpak update de.x08.KST4Contest
-
-

Updating macOS

-
    -
  1. Download the new DMG file for the appropriate architecture.
    2. -
  2. Close KST4Contest.
    3. -
  3. Open the DMG file.
    4. -
  4. Replace KST4Contest.app in the Applications folder.
    5. -
  5. Start the new version and check the existing settings.
    6. -
-

The configuration under ~/.praktiKST is not affected.

-
-

Problems during the first launch

-

Windows reports an unknown application

-

KST4Contest is not currently signed with a commercial Windows code-signing certificate. Windows or an additional security product may therefore warn about an unknown or rarely downloaded application.

-

Check the following first:

-
    -
  • Did the file come from the official KST4Contest release?
    • -
  • Does the filename match the published release?
    • -
  • Was the file downloaded completely?
    • -
  • Does the security product report a specific detection name or only a general reputation warning?
    • -
-

A warning alone is neither reliable proof of malware nor automatically a false positive. If the origin of the file is unclear, do not run it or restore it from quarantine.

-

Some users have reported quarantine messages from Norton 360 in particular. If the warning can be reproduced, please create a GitHub issue and include:

-
    -
  • the KST4Contest version,
    • -
  • the complete filename,
    • -
  • the security product and its version,
    • -
  • the reported detection name,
    • -
  • a screenshot of the warning, if possible.
    • -
-

The AppImage does not start

-

Check the executable permission first:

-
chmod +x KST4Contest-v<version>-linux-x86_64.AppImage
-
-

Then start the file from a terminal. Error messages shown there are usually more useful than a double-click that simply produces no visible result.

-

macOS blocks the application

-

Use the Open function described under Installing on macOS. Before doing so, verify that the DMG file came from the official GitHub Release.

-

The problem remains

-

First check whether the problem has already been reported under GitHub Issues. If it has not, create a new issue containing:

-
    -
  • the operating system and version,
    • -
  • the KST4Contest version,
    • -
  • the installation method,
    • -
  • the exact error message,
    • -
  • the steps required to reproduce the problem.
    • -
-

“It does not work” usually describes the situation accurately, but it is of limited value during diagnosis.

- -
-
- - - - - - diff --git a/website/_site/manual/en/log-sync/index.html b/website/_site/manual/en/log-sync/index.html deleted file mode 100644 index 78bb00f..0000000 --- a/website/_site/manual/en/log-sync/index.html +++ /dev/null @@ -1,231 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Log Synchronisation

-

Log Synchronisation

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

KST4Contest automatically marks worked stations in the chat user list. Two basic methods are available:

-
-

Log Sync Settings Window

-

Method 1: Universal File Based Callsign Interpreter (Simplelogfile)

-

KST4Contest reads a log file and searches for callsign patterns using a regular expression. Binary log files are also supported – unreadable binary content is simply ignored.

-

Advantage: Works with almost any logging program that writes a file. -Disadvantage: No band information available – stations are only marked as “worked”, not on which band.

-

Enter the path to the log file in the Preferences. The file is only read, never modified (read-only).

-
-

Tip: The Simplelogfile function can also be used to mark stations that are definitely unreachable (e.g. personal notes). This will be replaced in a later version by a better tagging system.

-
-
- -

When saving a QSO, the logging software sends a UDP packet to the broadcast address of the home network. KST4Contest receives this packet and marks the station including band information in its internal SQLite database.

-
-

Important: KST4Contest must be running in parallel with the logging software. QSOs logged while KST4Contest is not running will not be captured – except with QARTest (which can send the complete log).

-
-

Default UDP port: 12060 (matches the default of most logging programs)

-
-

Supported Logging Software

-

UCXLog (DL7UCX)

-

UCXLog Configuration

-

UCXLog sends QSO UDP packets and transceiver frequency packets.

-

Settings in UCXLog:

-
    -
  • Enable UDP broadcast
    • -
  • Enter the IP address of the KST4Contest computer (for local operation: 127.0.0.1)
    • -
  • Port: 12060 (default)
    • -
-

Note the green-highlighted fields in the UCXLog settings: IP and port must be filled in.

-

Note for multi-setup (2 computers, 2 radios, one KST4Contest instance): Both logging programs must send QSO packets to the IP of the KST4Contest computer. In this case, at least one IP is not 127.0.0.1.

-

QARTest (IK3QAR)

-

QARTest Configuration

-

Special feature: QARTest can send the complete log to KST4Contest (button “Invia log completo” in the QARTest settings). This means QSOs logged before KST4Contest was started are also captured.

-

Settings in QARTest:

-
    -
  • Configure UDP broadcast and IP/port as with UCXLog
    • -
  • Use “Invia log completo” for a full log upload
    • -
-

(„Buona funzionalità caro IK3QAR!" – DO5AMF)

-

N1MM+

-

Settings in N1MM+:

-

In N1MM+ under Config → Configure Ports, Mode Control, Winkey, etc. → Broadcast Data:

-
    -
  • Enable Radio Info (for TRX sync / QRG)
    • -
  • Enable Contact Info (for QSO sync)
    • -
  • IP: 127.0.0.1 (or IP of the KST4Contest computer)
    • -
  • Port: 12060
    • -
-

For the built-in DX cluster server: configure N1MM+ as a DX cluster client (server: 127.0.0.1, port as set in KST4Contest).

-

DXLog.net

-

DXLog.net Configuration

-

Settings in DXLog.net:

-
    -
  • Enable UDP broadcast
    • -
  • Enter the IP of the KST4Contest computer (green-highlighted fields)
    • -
  • Port: 12060
    • -
-

Win-Test

-

Win-Test is supported with a dedicated UDP network listener that understands the native Win-Test network protocol.

-

Advantages of Win-Test Integration:

-
    -
  • 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. -
    2. Otherwise, your own current QRG is used (from Win-Test STATUS or manual entry).
      3. -
    -
    • -
-

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.
    • -
-

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.
    • -
-

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

-

In addition to QSO synchronisation, UCXLog and other programs also transmit the current transceiver frequency via UDP. KST4Contest processes this information and makes it available as the MYQRG variable.

-

Frequency Buttons

-

Result: Your own QRG never needs to be typed manually in the chat – clicking the MYQRG button or using the variable in the beacon is sufficient.

-

Sources for your own QRG (MYQRG):

-
    -
  • UCXLog, N1MM+, DXLog.net, QARTest via UDP port 12060
    • -
  • Win-Test STATUS packet (optional, configurable in the “TRX Synchronisation” tab under “Win-Test STATUS QRG Sync”)
    • -
  • Manual entry in the QRG field
    • -
-
-

Note for multi-setup: With two logging programs on two computers, only one should send frequency packets. KST4Contest cannot distinguish between sources and processes all incoming packets.

-
-
-

Multi-Setup: 2 Radios, 2 Computers

-

For DM5M-style setups (2 radios, 2 computers, one KST4Contest instance or two separate):

-

Option A – One shared KST4Contest instance:

-
    -
  • Both logging programs send QSO packets to the IP of the KST4Contest computer
    • -
  • Only one logging program sends frequency packets (recommended: the VHF logging program)
    • -
-

Option B – Two separate KST4Contest instances (recommended):

-
    -
  • Each logging program communicates with its own KST4Contest instance via 127.0.0.1
    • -
  • Two separate chat logins
    • -
  • Better separation and fewer conflicts
    • -
-
-

Internal Database

-

KST4Contest stores worked information in an internal SQLite database. This is independent of the logging program’s database and is only populated via the UDP broadcast.

-

Before each new contest: reset the database! → Configuration – Worked Station Database Settings

- -
-
- - - - - - diff --git a/website/_site/manual/en/macros-and-variables/index.html b/website/_site/manual/en/macros-and-variables/index.html deleted file mode 100644 index ece07ba..0000000 --- a/website/_site/manual/en/macros-and-variables/index.html +++ /dev/null @@ -1,242 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

Macros and Variables

-

Macros and Variables

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

KST4Contest offers a flexible system of text snippets, shortcuts and built-in variables that significantly speed up the chat workflow during contests.

-
-

Overview

- - - - - - - - - - - - - - - - - - - - - - - - - -
TypeAccessPurpose
ShortcutsButton in the toolbarQuick text insert into the send field
SnippetsRight-click / Ctrl+1…0Text building blocks, optional PM sending
VariablesUsable in all text fieldsDynamic values (QRG, locator, AP data)
-
-

Shortcuts (Quick-Access Buttons)

-

Configurable in Preferences → Shortcut Settings.

-
    -
  • Each configured text creates one button in the user interface.
    • -
  • Clicking a button inserts the text into the send field.
    • -
  • All variables can be used in shortcuts and are resolved immediately when inserted.
    • -
  • Longer texts are also possible.
    • -
-

Tip: Set up frequently used abbreviations like “pse”, “rrr”, “tnx”, “73” as shortcuts.

-
-

Snippets (Text Building Blocks)

-

Configurable in Preferences → Snippet Settings.

-

Access

-
    -
  • Right-click on a callsign in the user list
    • -
  • Right-click in the CQ message table
    • -
  • Right-click in the PM message table
    • -
  • Keyboard shortcuts: Ctrl+1 to Ctrl+0 for the first 10 snippets
    • -
-

Behaviour with a Selected Callsign

-

When a callsign is selected in the user list, the snippet is addressed as a private message:

-
/CQ CALLSIGN <snippet text>
-
-

Then Enter can be pressed to send directly – even if the send field does not have focus.

-

Hardware Macro Keyboard

-

(Idea by IU3OAR, Gianluca Costantino)

-

The key combinations Ctrl+1 to Ctrl+0 can be assigned to a programmable macro keyboard. One key press triggers the snippet, another press (mapped to Enter) sends it immediately. In contest operation this saves considerable time.

-

Predefined Default Snippets

-

On first start, some snippets are pre-configured, e.g.:

-
    -
  • Hi OM, try sked?
    • -
  • I am calling cq ur dir, pse lsn to me at MYQRG
    • -
  • pse ur qrg?
    • -
  • rrr, I move to your qrg nw, pse ant dir me
    • -
-

These can be customised or deleted in the Preferences.

-
-

Variables

-

Variables in written texts (snippets, shortcuts, beacon, send field) are replaced by their current values at runtime. Simply type the variable name in uppercase in the text.

-

MYQRG

-

Replaced by the current transceiver frequency.

-
    -
  • Source: TRX sync via UDP from the logging software (if enabled)
    • -
  • Fallback: Manually entered value in the MYQRG text field to the right of the send button
    • -
  • Format: 144.388.03
    • -
-

Example: calling cq at MYQRG → calling cq at 144.388.03

-

MYQRGSHORT

-

Like MYQRG, but only the first 7 characters.

-
    -
  • Format: 144.388
    • -
-

Example: qrg: MYQRGSHORT → qrg: 144.388

-

MYLOCATOR

-

Replaced by your own Maidenhead locator (6 characters).

-
    -
  • Format: JO51IJ
    • -
-

Example: my loc: MYLOCATOR → my loc: JO51IJ

-

MYLOCATORSHORT

-

Like MYLOCATOR, but only the first 4 characters.

-
    -
  • Format: JO51
    • -
-

Example: loc: MYLOCATORSHORT → loc: JO51

-

QRZNAME

-

Replaced by the name of the currently selected station from the chat name field.

-

Example: Hi QRZNAME, sked? → Hi Gianluca, sked?

-

FIRSTAP

-

Replaced by data of the first reflectable aircraft to the selected station (if available).

-
    -
  • Condition: AirScout is active and an aircraft is available.
    • -
  • Example format: a very big AP in 1 min
    • -
-

Example: AP info: FIRSTAP → AP info: a very big AP in 1 min

-

SECONDAP

-

Like FIRSTAP, but for the second available aircraft.

-
    -
  • Example format: Next big AP in 9 min
    • -
-

Example: also: SECONDAP → also: Next big AP in 9 min

-

MYQTF (planned for v1.3)

-

Replaced by the current antenna direction in words (e.g. north, north east, east, …).

-
    -
  • Source: Degree value in the MYQTF input field (to the right of the MYQRG field)
    • -
-
-

Variables in the Beacon

-

All variables can also be used in the automatic beacon (interval messages). Recommended beacon configuration:

-
calling cq at MYQRG, loc MYLOCATOR, GL all!
-
-

Since KST4Contest automatically reads QRG data from chat messages: if other stations also use KST4Contest, they will immediately see your QRG in the QRG column of their user list.

-
-

Example Contest Workflow with Macros

-
    -
  1. Select a station in the user list → callsign is now pre-selected.
    2. -
  2. Press Ctrl+1 → Snippet “Hi OM, try sked?” is addressed as a PM.
    3. -
  3. Press Enter → Message sent.
    4. -
  4. Station replies with frequency → QRG column is automatically filled.
    5. -
  5. Press Ctrl+2 → Snippet “I am calling cq ur dir, pse lsn to me at 144.388” (MYQRG resolved).
    6. -
  6. Press Enter → Sent.
    7. -
-

No manual typing, no errors, no interruption to CQ calling.

- -
-
- - - - - - diff --git a/website/_site/manual/en/user-interface/index.html b/website/_site/manual/en/user-interface/index.html deleted file mode 100644 index 2e9d5da..0000000 --- a/website/_site/manual/en/user-interface/index.html +++ /dev/null @@ -1,211 +0,0 @@ - - - - - {{ manual.title }} | KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-
-

← Back to manual overview

-

User Interface

-

User Interface

-
-

🇬🇧 You are reading the English version | 🇩🇪 Deutsche Version

-
-

Connecting to the Chat

-
    -
  1. Select a chat category in the settings window (e.g. 144 MHz VHF, 432 MHz UHF, …).
    2. -
  2. Click the Connect button.
    3. -
  3. Wait for the connection to be established.
    4. -
-
-

Disconnecting and reconnecting is only possible via the settings window. It is therefore recommended to keep the settings window open.

-
-
-

Main Window Overview

-

The main window consists of several areas:

-

PM Window (top left)

-

Shows all received private messages as well as intercepted public messages containing your own callsign. New messages appear in red and fade every 30 seconds from yellow to white.

-

User List (Chat Members)

-

The central table of all currently active chat users. Columns (depending on configuration):

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ColumnContent
CallStation’s callsign
NameName from the chat name field
LocMaidenhead locator
QRBDistance in km
QTFDirection in degrees
QRGAutomatically detected frequency
APAirScout aircraft data (when active)
Band coloursWorked / NOT-QRV status per band
-

Sorting: Click column headers. QRB sorting is numerical (corrected in v1.22).

-

Send Field

-

Text input for outgoing messages. After clicking a callsign in the user list, the send field automatically receives focus – start typing immediately without double-clicking (from v1.22).

-

MYQRG Field

-

To the right of the send button. Shows the current own QRG, can also be entered manually.

-

MYQTF Field (for v1.3)

-

Input field for the current antenna direction. Used for the planned MYQTF variable.

-
-

Filters

-

The filter bar (from v1.21 as a flowpane for small screens):

-
    -
  • Show only QTF: Activate direction filter (N/NE/E/… buttons or degree input)
    • -
  • Show only QRB [km] <=: Activate distance filter (toggle button)
    • -
  • Hide Worked [Band]: Hide worked stations per band (one toggle per band)
    • -
  • Hide NOT-QRV [Band]: Hide NOT-QRV-tagged stations per band
    • -
-
-

Station Info Panel (Further Info)

-

Bottom right: Shows all messages of a selected station (CQ messages and PMs in one panel). A message filter can be pre-configured via the default filter in the Preferences.

-

Sked reminders can also be activated here.

-
-

Priority List

-

Shows the top candidates calculated by the Score Service. Updates automatically in the background based on direction, distance and AP availability.

-
-

Cluster & QSO of Others

-

Separate window (can be minimised). Shows the communication flow between other stations – interesting during quieter contest periods.

-
- -

Window

-
    -
  • Use Dark Mode (from v1.26): Toggle dark colour scheme on/off.
    • -
-
-

Window Sizes and Dividers

-

From v1.21, clicking “Save Settings” also saves window sizes and divider positions of all panels in the configuration file, which are restored on the next start.

-

If you encounter display problems: delete the configuration file → KST4Contest creates new default values.

-
-

Operating Tips

-
    -
  • Keep the settings window open: Quick access to enable/disable the beacon.
    • -
  • Right-click in the user list: Opens the snippet menu and further actions (QRZ.com profile, set NOT-QRV tags).
    • -
  • Enter from anywhere: When text is in the send field, Enter sends directly – even if the focus is elsewhere.
    • -
  • Stop the beacon: Switch off the beacon while scanning frequencies to avoid flooding the chat with messages.
    • -
- -
-
- - - - - - diff --git a/website/_site/manual/index.html b/website/_site/manual/index.html deleted file mode 100644 index d16cd46..0000000 --- a/website/_site/manual/index.html +++ /dev/null @@ -1,110 +0,0 @@ - - - - - KST4Contest Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

KST4Contest Manual

-

- User documentation for installation, configuration, features, - AirScout integration, log synchronization and contest workflow. -

- -
- English Manual - Deutsches Handbuch -
-
- - - - - - diff --git a/website/_site/news/2026-07-08-hotfix-version-1-41-1/index.html b/website/_site/news/2026-07-08-hotfix-version-1-41-1/index.html deleted file mode 100644 index 910573f..0000000 --- a/website/_site/news/2026-07-08-hotfix-version-1-41-1/index.html +++ /dev/null @@ -1,111 +0,0 @@ - - - - - Hotfix Version 1.41.1 - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

News · July 8, 2026

-

Hotfix Version 1.41.1

-

Hotfix of a bug in Version 1.41

-
- -
-
-

Version 1.41.1

-

We had a bug, where KST4Contest would clear out the text field, where you would send your messages after a period. It also happend to set your Cursor back to the Sending Field, when you were filtering for a station. We fixed this bug today. The new release is here. You can also download the artifacts as always via the Downloads-Page.

- -
-
- - - - - - diff --git a/website/_site/news/2026-07-15-AUR-Packages/index.html b/website/_site/news/2026-07-15-AUR-Packages/index.html deleted file mode 100644 index 5def279..0000000 --- a/website/_site/news/2026-07-15-AUR-Packages/index.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - AUR Packages now live of kst4contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

News · July 15, 2026

-

AUR Packages now live of kst4contest

-

We now uploaded the packages of kst4contest to the AUR

-
- -
-
-

AUR Packages now live of KST4Contest

-

We now have uploaded kst4contest as multiple Arch User Repository Packages. This allows yet another integration into Package Managers for easier updating toall Archlinux Users of our software. This one of many more repositories for our linux users to come. It is an continous effort. You can see the progress of making updating KST4Contest for our users easier here.

-

AUR DISCLAIMER

-

Before you use the AUR (if you did not use the AUR before) please read this entry in the Arch wiki and the disclaimer about security in the AUR.

-

Packages provided to the AUR:

-
    -
  • kst4contest: This is the latest Release Build. If you install this package, you will compile the source code on your own machine. We recommend an JDK21 Enviroment for doing this
    • -
  • kst4contest-bin: This is the precompiled Binary, which is the same as the binary on the Github release page.
    • -
  • kstcontest-git: This is the latest devolopment state of kst4contest. This is recommend for testers only, as things might break.
    • -
-

Have fun with these packages. 73

- -
-
- - - - - - diff --git a/website/_site/news/2026-07-website-launch/index.html b/website/_site/news/2026-07-website-launch/index.html deleted file mode 100644 index cf77e3b..0000000 --- a/website/_site/news/2026-07-website-launch/index.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - - KST4Contest Website Launch - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

News · July 7, 2026

-

KST4Contest Website Launch

-

The new KST4Contest website is being built as a static, SEO-friendly product portal with GitHub-based documentation.

-
- -
-
-

A new home for KST4Contest

-

KST4Contest now has its own website at kst4contest.hamradioonline.de.

-

The site is built with Eleventy, generated from version-controlled Markdown and deployed as a fast static website.

-

Why this matters

-

The goal is to make KST4Contest easier to discover, easier to document and easier to maintain.

-

Documentation, release information, feature pages and future updates can now grow from a shared content model.

- -
-
- - - - - - diff --git a/website/_site/news/index.html b/website/_site/news/index.html deleted file mode 100644 index 4b708dd..0000000 --- a/website/_site/news/index.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - KST4Contest News - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

News

-

Development updates and release notes.

-

- Updates about KST4Contest releases, website improvements and contest workflow development. -

-
- -
-
- - - - - - - -
-
- - - - - - diff --git a/website/_site/privacy/index.html b/website/_site/privacy/index.html deleted file mode 100644 index c07693d..0000000 --- a/website/_site/privacy/index.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - Privacy Policy | KST4Contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Privacy

-

Privacy Policy

-

Information about data processing on this static website.

-
- -
-
-

Controller

-

- Marc Fröhlich
- Rheingoldstr. 6
- 68199 Mannheim
- Germany -

- -

Access logs

-

- When this website is accessed, the web server may process technical access data such as - IP address, requested URL, date and time, user agent and referrer. - This processing is used to provide the website, maintain security and investigate technical issues. -

- -

Legal basis

-

- The legal basis is Art. 6(1)(f) GDPR: legitimate interest in secure and reliable operation - of the website. -

- -

Cookies and tracking

-

- This website currently does not use cookies, analytics tracking, advertising pixels or user profiling. -

- -

External links

-

- This website links to GitHub for source code, releases and downloads. When you follow these links, - GitHub is responsible for its own data processing. -

- -

- - Support via Ko-fi - -

- -

- - This website links to Ko-fi for voluntary financial support. - - Payments are processed entirely by Ko-fi and its payment providers. - - KST4Contest itself never receives or processes payment information. - -

- -

Your rights

-

- You may have the right to access, rectification, erasure, restriction of processing, - data portability and objection under the GDPR. -

- -

Supervisory authority

-

- You have the right to lodge a complaint with a competent data protection supervisory authority. -

-
-
- - - - - - diff --git a/website/_site/roadmap/index.html b/website/_site/roadmap/index.html deleted file mode 100644 index 0165cbe..0000000 --- a/website/_site/roadmap/index.html +++ /dev/null @@ -1,270 +0,0 @@ - - - - - KST4Contest Roadmap - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Roadmap

-

What's planned next.

-

- Generated automatically from the "enhancement" issues in our - GitHub repository, - grouped by their target version milestone. -

-
- -
- - - - - - - - - - - -
- -
- -
- -

- -Community - -

- -

- -Development is driven by the community. - -

- -

- -Many roadmap items require -time, -online services -and infrastructure. - -Community support helps accelerate development. - -

- -
- - - -❤️ Support Development - - - -
- -
- -
- - - - - - diff --git a/website/_site/screenshots/index.html b/website/_site/screenshots/index.html deleted file mode 100644 index 7c5ebd6..0000000 --- a/website/_site/screenshots/index.html +++ /dev/null @@ -1,136 +0,0 @@ - - - - - KST4Contest Screenshots - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Screenshots

-

See the contest workflow.

-

- Visual impressions of KST4Contest: ON4KST chat workflow, priority candidates, - sked handling, AirScout integration and contest-focused operator tools. -

-
- -
-
- -
-
- Main Window -
-

Main Window

-

Contest-oriented ON4KST chat workflow with candidate awareness.

-
- -
-
- Priority Candidates -
-

Priority Candidates

-

Score-based candidate ranking for faster operator decisions.

-
- -
-
- Timeline View -
-

Timeline View

-

Timeline support for AP windows and candidate timing.

-
- -
-
- - - - - - diff --git a/website/_site/sitemap.xml b/website/_site/sitemap.xml deleted file mode 100644 index f721b23..0000000 --- a/website/_site/sitemap.xml +++ /dev/null @@ -1,107 +0,0 @@ - - - - https://kst4contest.hamradioonline.de/news/2026-07-website-launch/ - 2026-07-07 - - - https://kst4contest.hamradioonline.de/news/2026-07-08-hotfix-version-1-41-1/ - 2026-07-08 - - - https://kst4contest.hamradioonline.de/news/2026-07-15-AUR-Packages/ - 2026-07-15 - - - https://kst4contest.hamradioonline.de/about/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/contact/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/download/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/faq/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/airscout/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/dual-chat/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/dx-cluster/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/log-sync/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/macros/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/priority-score/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/sked-reminder/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/features/timeline/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/legal-notice/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/manual/de/home/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/manual/de/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/manual/en/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/manual/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/privacy/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/roadmap/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/screenshots/ - 2026-07-21 - - - https://kst4contest.hamradioonline.de/support/ - 2026-07-21 - - \ No newline at end of file diff --git a/website/_site/support/index.html b/website/_site/support/index.html deleted file mode 100644 index 1b2deb8..0000000 --- a/website/_site/support/index.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - Support KST4Contest - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - KST4Contest - ON4KST Contest Client - - - - -
- -
-
-

Support Development

- -

Help shape the future of KST4Contest.

- -

- KST4Contest is an independent open-source project developed in my free time. - Your support helps cover infrastructure costs and enables new contest-oriented - features that would otherwise be difficult to implement. -

- -
- - ❤️ Support on Ko-fi - - - - View Source Code - -
-
- - -
- -
-

What previous support has enabled

- -

Real improvements funded by the community.

-
- -
- -
- -

🛰 PSTRotator Integration

- -

- -Support helped justify the investment into rotor hardware and the required -PSTRotator license. Today KST4Contest can automatically control antennas -during contest operation. - -

- -
- -
- -

🗺 Interactive Map

- -

- -The interactive station map required commercial map API usage. -Community support helped cover those API costs and made the feature possible. - -

- -
- -
- -
- - -
- -
- -

Future goals

- -

What future support will fund

- -
- -
- -
- -

☁ Map API

- -

- -Keeping the online map service available requires ongoing API usage. - -

- -
- -
- -

📡 Tropo Server

- -

- -Future propagation prediction services and server-side calculations -will require dedicated hosting infrastructure. - -

- -
- -
- -

🔌 New Integrations

- -

- -Development of additional interfaces, logging software integrations, -contest tools and automation features. - -

- -
- -
- -

🚀 Faster Development

- -

- -More development time means more contest-oriented features, -better testing and better documentation. - -

- -
- -
- -
- - -
- -
- -

Every contribution helps

- -

Whether it's one coffee or ongoing support.

- -

- -Your support directly improves KST4Contest. - -Unlike commercial software, every new feature is driven by real contest -experience and community feedback. - -

- -
- - - -❤️ Support KST4Contest - - - -
- -
- -
- - - - - -