rouggy
99599458ff
Asked for the wiki to catch up, and to be explicit — examples rather than
descriptions. New page and six rewritten sections.
Recent QSOs and Filters, the page named in the request: the right-click menu is
now a table of what every entry does, and the filter builder has five worked
multi-criteria filters written out field by field, each ending in what you then
do with the result. Including the distinction that prompted it — "export
selected" takes the highlighted rows, "export filtered view" takes every QSO the
filter matched, and after building a filter it is the second one you want. Plus
the traps: ADIF date format, and "is empty" not being "equals N".
Connections (new): the page for a settings section that had none. What OpsLog
listens to and sends, which outbound row another logger actually wants — a
logger asking for "WSJT-X UDP" discards a bare ADIF record — the custom-message
triggers with their placeholder lists, three worked examples, and the port-clash
warning that produced this week's CAT-drop report.
Amplifiers and Switches: the generic HTTP relay in full — per-relay URLs, the
pattern form, {relay}, {relay-1} and {value} with what each one sends — relay
automatic control with a four-relay antenna-switch example, and the bench power
supply including why OpsLog writes only its output.
Rotators: the two new native types (SPID with the Rot1Prog/Rot2Prog choice,
DCU-1), two-rotor setups, and that Test only reads the heading on the types
where it does.
Awards: the US county database, and the difference between the automatic fill
(blanks only) and the right-click re-derive (replaces) — with the Connecticut
planning regions, which is the case that needs it.
QSL Management: QSL_VIA against QSL_SENT_VIA/QSL_RCVD_VIA, why an import shows E
on every Log4OM record, and that V counts as confirmed.
Troubleshooting: the three field reports of the last few days, by symptom.
Every [[link]] checked to resolve.
76 lines
2.9 KiB
Markdown
76 lines
2.9 KiB
Markdown
# 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.
|