DXCA — DX Cluster Aggregator 2.0
Ground-up Rust rewrite of the DX Cluster Aggregator that runs the whole aggregation stack headless on a Raspberry Pi (equally on macOS/Linux, and since v2.2.0 on Windows) behind a multi-user web GUI. Merges WSJT-X / JTDX / MSHV binary-UDP decoder sources and DX-cluster telnet nodes — honest three-state node status (proven-live vs connected-unproven), login/silence watchdog, reconnect backoff that only resets on proof — into one feed, re-served on a built-in telnet cluster server (port 7575), a UDP fan-out including a verbatim passthrough that keeps RUMlogNG's click-to-fill working, and MQTT publish (structured JSON plus the plain cluster line, on sibling topics) for panadapter overlays. Each account carries its own ClubLog matrix, so different operators see their own highlighting across seventeen alert levels — New DXCC / Band / Mode / Slot for never worked, the matching four for worked-but-unconfirmed, a New and a ? pair each for IOTA, WAS, VUCC and WAZ, and the DX Marathon — and get their own Telegram alerts, with a history of what was actually sent, over the same shared spot stream. A match can be marked on the radio as well as sent to a phone: FlexRadio panadapters over SmartSDR and ExpertSDR3 over TCI, several of each per account.
DXCC Challenge points and band×mode slot totals per station, per-band and per-mode entity breakdowns, LoTW uploaders flagged from ARRL's list, and each account's ClubLog log plus the shared LoTW list re-downloaded on a schedule. Five awards beyond DXCC are opt-in per account and add nothing anywhere until ticked — IOTA from a spot's own comment, checked against the directory; WAS from the FCC licence database; VUCC grids on 50 MHz and up; WAZ's forty zones; and the DX Marathon's score for the current year — and which WAS or WAZ you are chasing (mixed, per band, or each mode) is itself a setting, because it changes what wakes you rather than only what is shown. Confirmations ride an optional LoTW QSL-report download, except zones, which score off the QSL flags ClubLog's export already carries.
Where a cluster comment omits the mode, it is inferred from an IARU Region 3 band plan and marked as inferred rather than asserted — an unknown mode is never quietly filed as digital. Live WebSocket dashboard on a three-tab shell — Spots, Alerts, Stats — with everything you configure behind a gear: sources, nodes, destinations, MQTT, accounts and a server-wide call blacklist, all edited in the browser with hot-apply. Both spot tables share one fixed, measured column grid, so a column lands in the same place on every row while the stream runs, and each screen's narrowing sits in a collapsible rail that still reports how much it is holding back when folded.
An optional band mask recedes bands the sun says are not workable from your Maidenhead square — dim or hide, around a tunable grey-line window, and New DXCC is never masked. Stats shows what the live feed is made of beside your own ClubLog totals, with Club Log's DX Dashboard embedded alongside them and an awards view — WAS endorsements per band and per mode with a Triple Play worklist, zones worked and confirmed, islands, grids and the Marathon year, each with a still needed list. Installs as a systemd service (Pi), a launchd agent (macOS) or — new in v2.2.0 — a boot-started scheduled task on Windows from a prebuilt .exe + installer shipped as a release asset, each through an installer that checks its own prerequisites and then verifies the result is genuinely serving; behavioural parity with the macOS app proven by golden tests against its own artifacts.
Supersedes the macOS DX Cluster Aggregator (final feature release v1.8.4, maintained at v1.8.5, retained as fallback). Original concept and reference implementation by Vinod VU3ESV; the DX-cluster telnet engine and the web GUI's design system are derived from the Meridian project (joint work with Basil Thomas W6BT and Ram VU3RDD).