Rsclub2_2/kst4contest
1
0
Fork 0
mirror of https://github.com/praktimarc/kst4contest.git synced 2026-09-11 19:55:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix DX Cluster spot formatting - emit fixed 75-character DXSpider-compatible lines - align callsign, comment, and UTC fields - support frequencies up to 24 GHz - reject overlong callsigns instead of truncating them - add protocol tests and update documentation Fixes #86

Browse Source
This commit is contained in:
Marc Froehlich
2026-09-02 20:03:55 +02:00
parent 6b0d699a98
commit 51aa04bfb5
15 changed files with 422 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files
github_docs/en-Configuration.md
+3 -1
View File
@@ -428,12 +428,14 @@ The following settings and controls belong to the local DX cluster output:
```text
Spotted callsign: DO5AMF
Comment: Testing DXC-Spot: Congrats, you donated $100!
Comment: DXC test: You donated $100!
Frequency: .300 on the selected fallback band
```
With `144 MHz` selected as the fallback band, the resulting frequency is approximately `144.300 MHz`.
All spots use a fixed, DXSpider-compatible 75-character payload line with a 30-character comment field. Longer comments are deliberately truncated at this protocol boundary; the DX callsign is not. A callsign longer than twelve characters causes the affected spot to be rejected and logged.
The comment is a deliberately retained Easter egg. It has no technical meaning and, despite being remarkably specific, does not initiate a payment. Its practical purpose is to make the test spot easy to identify in the logging software.
The test works only if