rouggy
9f384402fa
Note that entering address/city/state and per-band rig & antenna, then ticking "Fill my station fields from my profile" on ADIF import, backfills the MY_* fields automatically for a fully-described log.
74 lines
3.0 KiB
Markdown
74 lines
3.0 KiB
Markdown
# Getting Started
|
|
|
|
This walks you from a fresh install to your first logged QSO.
|
|
|
|
## 1. Set your station
|
|
|
|
**Settings → Station Information**: enter your **callsign**, **grid locator** and
|
|
**name**. These feed callsign lookups, the map, awards, the QSL card and the
|
|
"my station" ADIF fields on every QSO.
|
|
|
|
For a **complete ADIF**, also fill your **address / city / state / county** here,
|
|
and set your **per-band rig and antenna** in **Settings → Operating conditions**
|
|
(tick the default antenna for each band). These populate the `MY_*` fields
|
|
(`MY_RIG`, `MY_ANTENNA`, `MY_CITY`, `MY_STREET`, `MY_STATE`…) on your QSOs.
|
|
|
|
> **Importing an existing log?** Fill the station info **and** your operating
|
|
> conditions **before** you import. In the ADIF import dialog, tick **"Fill my
|
|
> station fields from my profile"** — OpsLog then backfills the *empty* `MY_*`
|
|
> fields (grid, rig, antenna, address, city, state, county, SOTA/POTA…) plus
|
|
> **Operator** and **Owner callsign** from your active profile, so even a bare
|
|
> ADIF comes in fully described. Existing values are kept; only
|
|
> `STATION_CALLSIGN` is left untouched (so a mixed-call log isn't re-routed).
|
|
> See [[Import and Export ADIF]].
|
|
|
|
## 2. (Optional) Connect a radio
|
|
|
|
**Settings → CAT**, pick a backend and fill its fields — see [[CAT Control]].
|
|
Once connected, the frequency, band and mode fill in automatically as you tune,
|
|
and clicking a cluster spot tunes the rig.
|
|
|
|
You can log perfectly well **without** a radio — just type the band, mode and
|
|
frequency.
|
|
|
|
## 3. The entry strip
|
|
|
|
The strip across the top is the heart of OpsLog (Log4OM-style):
|
|
|
|
- **Callsign** — type it and the contacted entity's **flag** appears next to the
|
|
RST fields; the country, CQ/ITU zones and continent resolve offline from
|
|
`cty.dat`. If QRZ/HamQTH lookup is configured, name / QTH / grid auto-fill and
|
|
a photo shows in the F2 tab.
|
|
- **RST sent / rcvd**, **Name**, **QTH**, **Grid**.
|
|
- **Band / Mode / Frequency** (TX and, for split, RX).
|
|
- **Start / End time**, **Comment / Note**.
|
|
|
|
Press **Enter** in any text field to **log** the QSO. The contact drops into
|
|
**Recent QSOs** below.
|
|
|
|
> Mode comes from the radio; the digital sub-mode (FT4 vs FT8) is inferred from
|
|
> the frequency.
|
|
|
|
## 4. Look around
|
|
|
|
- **Recent QSOs** — your log; double-click a row to edit every field.
|
|
See [[Recent QSOs and Filters]].
|
|
- **Worked-before matrix** — as you type a call, see if/when you worked that
|
|
entity, per band/mode slot.
|
|
- **Main view** — two configurable panes (Settings → General → *Main view*): a
|
|
great-circle map, the cluster, the FlexRadio or Icom console, Net control, and
|
|
more. See [[Maps and Antennas]].
|
|
|
|
## 5. Profiles
|
|
|
|
Every setting is **per-profile**. A profile can log to the local SQLite file or
|
|
a shared **MySQL** database (multi-operator). Create one per call / station /
|
|
event. See [[Profiles and Databases]].
|
|
|
|
## Next steps
|
|
|
|
- Chase spots → [[DX Cluster and Spots]]
|
|
- Track awards → [[Awards]]
|
|
- Send confirmations → [[QSL Management]]
|
|
- Design a card → [[QSL Card Designer]]
|