# DX Cluster and Spots

## Servers

Add multiple cluster servers (Settings). They auto-reconnect; one is the
**master** used for sending commands. A quiet node is not treated as a dead one
— silence keeps its session, login and filters. The Cluster tab and the
Main-view cluster pane share the same live feed.

## Filter sidebar

A show/hide **filter sidebar** (shared by the Cluster tab and the Main pane):

- **Callsign** search, **hide worked**, **group duplicates**.
- Filter by **band / mode / status / source**, plus **NEW POTA** and
  **NEW COUNTY** chips.

## Per-spot status and tuning

Each spot is coloured by **status** relative to your log:

- **new** (entity never worked), **new-band**, **new-mode**, **new-slot**,
  **worked**.
- Settings → General → **Group digital modes as one (DXCC-style)** makes
  FT8/FT4/RTTY/PSK count as a single Digital mode for the colouring and the
  matrix badges, matching how DXCC counts.

Click a spot to **tune the rig** (fills the callsign into the entry strip). A
multi-band **Band Map** shows panadapter-style strips per band — its CW / data
/ phone sub-bands use their own colour-blind-checked hues, and **Ctrl+↑ /
Ctrl+↓** jumps to the next spot above/below the current frequency and tunes it.

**POTA** spots are tagged with their park reference (via `api.pota.app`).

The entry strip's band matrix can also show the **ClubLog Most Wanted rank**
(Settings → General): an `MW #rank` pill next to the entity name, personalised
to your callsign, refreshed daily.

## Sending a spot

Use the **Send Spot** window to announce a DX spot on the master cluster:
callsign + frequency + a message. The frequency defaults to the **live CAT
frequency** (full resolution, including sub-kHz).

## Spot alerts

**Tools → Alert management** — Log4OM-style alert rules on **call / country /
band / mode / spotter**, with **sound**, **visual** and **e-mail** notification.
Active alerts appear as a discreet bell in the entry strip; click it for the
list.

## External spot sources

A **DXHunter** remote-call UDP packet fills the callsign, and when it carries
`<FREQ>` and `<MODE>` it also tunes whichever CAT backend is active. See
[[Settings and Data]] for the UDP configuration.

See also: [[Maps and Antennas]] for turning the beam to a spot.

## When the list looks empty

If spots are arriving and none are shown, the panel says so, names the filters
responsible and offers a button to clear them all. The two easiest to forget are
the **band and mode locks** (🔒), because they follow the radio rather than a
click — with the rig on 20 m SSB and both locked, a hundred spots on other bands
show nothing.

Filter selections are remembered between sessions; a fresh installation starts
with none set.

## Spotting

When you send a spot, the comment carries the mode and then the **award
references you have assigned** to that contact — the ones on the QSO, not the
ones OpsLog would compute for it.
