User guide and setup — VHF/UHF contest logger with aircraft scatter
When you open the logger for the first time, Settings opens automatically. Fill in these fields:
| Field | Example | Description |
|---|---|---|
| Callsign | OZ7Z | Your own callsign (upper case) |
| Locator | JO44VW | Your Maidenhead locator, 4 or 6 characters |
| Band | 144 MHz | Active contest band |
| Category | 3L | NAC section code — updates automatically when you change band (3L/3H = SO Low/High, 4L/4H = MO Low/High on 144 MHz) |
| Name / Email | — | Used in the EDI file submitted to the contest organiser |
Use the entry fields in the bottom-left panel:
HHMM).Press Enter to move to the next field. The QSO is saved automatically when the locator is entered.
Enable under Entry mode → One-liner in Settings. Type everything on one line and press Enter.
Important convention: the RST you send (your report to the other station) is marked with an apostrophe ' after it. The RST you receive is written without an apostrophe.
| Example | Meaning |
|---|---|
G3YDY 59' 57 JO01FQ | Sent 59, received 57, locator JO01FQ |
G3YDY 57 JO01FQ | Sent 59 (default), received 57 |
G3YDY JO01FQ | Both RST = 59 (default) |
G3YDY 59' 57 001 JO01FQ | With received serial number 001 |
Full format: CALL [SND-RST'] [RCV-RST] [NR] LOCATOR
Locator and callsign are the only required fields — everything else is optional and falls back to defaults (RST 59).
The score is shown continuously in the bar below the top menu:
| Band | Multiplier |
|---|---|
| 50–1296 MHz | ×1 |
| 2.3 GHz | ×2 |
| 3.4 GHz | ×3 |
| 5.7 GHz | ×4 |
| 10 GHz | ×5 |
| 24 GHz+ | ×6–×10 |
Click ↓ EDI to download your contest log in REG1TEST format (Tucnak-compatible). The file can be uploaded directly to vushf.dk.
Filename: CALL_144MHz_DATE.edi
Import a text file with known stations for callsign autocomplete:
G3YDY;JO01FQ;Don
G4SWX;JO02RF
Format: CALL;LOCATOR or CALL;LOCATOR;NAME — one station per line.
Click 📂 Load locator file in Settings. The database is stored in the browser.
Aircraft scatter allows VHF/UHF QSOs over long distances via reflection from aircraft. Flight data is fetched via vushf.dk as a proxy — it tries airscatter.dk first and automatically falls back to OpenSky Network if airscatter.dk is unavailable. The active source is shown in the info bar below the map: 42 aircraft · airscatter.dk or 42 aircraft · OpenSky.
aircraft_proxy.php to be installed on a PHP server. See section 8.| Display | Meaning |
|---|---|
| G3YDY ✈ (12) | Aircraft in scatter position now — approx. 12 minutes remaining |
| G4SWX (5) | Next aircraft arrives in approximately 5 minutes |
| G4KUX | No scatter or incoming aircraft detected |
| (faded) | Station already logged as a QSO |
The scatter corridor angle and minimum aircraft distance are set automatically based on the selected band. You can adjust them manually in Settings:
| Parameter | Description |
|---|---|
| Scatter angle (°) | Width of the scatter corridor. Narrower at higher frequencies. |
| Plane range (km) | Maximum search radius for aircraft |
| Min plane dist (km) | Aircraft closer than this are ignored (within line-of-sight) |
The logger has a built-in client for the ON4KST VHF chat network. Use it to arrange skeds with other operators during a contest.
When a station in the Watchlist tab is also online on KST it shows a ·KST badge next to its callsign. Right-click the callsign to open a context menu with a pre-filled scatter sked message:
CALL pls sked on 144.300 AP in 8 min
The frequency is taken from your active band and the time is the current scatter ETA. Edit the message if needed and press Enter to send it.
The Online tab (tab 4) shows all stations currently logged into the KST channel. Click Fetch active users to refresh the list. The list is filtered by distance — only stations within the configured maximum (default 1000 km) are shown.
| Badge | Meaning |
|---|---|
| ·WL | Station is in your Watchlist |
| ·ME | Your own callsign |
Right-click any callsign in the Online list to send a CQ message pre-filled as /cq CALL.
| Key | Action |
|---|---|
| Enter | Move to next field / save QSO |
| Esc | Close autocomplete |
The log is saved automatically in the browser's localStorage after every QSO — it survives browser restarts. Data is not deleted when the page is refreshed.
To move your log to another computer: use the browser DevTools (F12 → Application → Local Storage) and copy the keys zlog_log and zlog_settings.