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.
64 lines
2.9 KiB
Markdown
64 lines
2.9 KiB
Markdown
# Profiles and Databases
|
|
|
|
## Profiles
|
|
|
|
Every setting in OpsLog is **per-profile**: station identity, CAT, lookup, QSL
|
|
defaults, awards display, antennas, and which logbook to use. Create one profile
|
|
per callsign / station / event.
|
|
|
|
The **callsign in the top bar is the station switcher** — click it and pick a
|
|
profile. Managing profiles is at the bottom of that list (and in Settings).
|
|
|
|
## Two separate databases
|
|
|
|
Since 0.21.0 the settings and the QSOs live in **separate files**:
|
|
|
|
| Store | What | Where |
|
|
|-------|------|-------|
|
|
| **Settings database** (`settings.db`, or `opslog.db` on older installs) | settings, profiles, rigs/antennas, cluster nodes, lookup cache, award lists, QSL templates | always the **local SQLite** file under `data/` |
|
|
| **Logbook** (`logbook.db`) | your QSOs | where the active profile points — a local SQLite file **or** shared MySQL |
|
|
|
|
Keeping the settings local means the UI is instant even when the logbook is a
|
|
far-away MySQL server. Settings → Database shows the two as separate sections,
|
|
with an *Open folder* shortcut; a logbook file can be **renamed or relocated**
|
|
(its QSOs move with it), and the status bar names the **logbook** file — that
|
|
is the one to back up.
|
|
|
|
A profile can point at its **own logbook file** — ideal for a visiting
|
|
operator, whose contacts stay out of your log without touching your settings.
|
|
|
|
**Portable**: paths inside the OpsLog folder are stored relative to it, so
|
|
moving the whole folder to another drive or PC loses nothing.
|
|
|
|
## Shared MySQL logbook (multi-operator)
|
|
|
|
Point a profile's logbook at a **MySQL** database so several operators run **one
|
|
log** — e.g. a multi-op special-event call. Configure the host / database /
|
|
credentials in the profile's database settings.
|
|
|
|
- The database and tables are converted to **utf8mb4** on connect, so Cyrillic
|
|
or Polish characters from a QRZ lookup store correctly even when the hosting
|
|
panel created the database as latin1.
|
|
- An FT8/MSHV QSO that cannot reach a laggy shared database is **parked and
|
|
re-logged automatically** once it recovers — no lost QSOs.
|
|
- Switching to a profile whose MySQL is unreachable shows a clear warning
|
|
instead of silently staying on the previous logbook.
|
|
|
|
This is also what powers [[Multi-Operator Live Status]].
|
|
|
|
## Backups
|
|
|
|
Optional **database + ADIF backup at shutdown** (Settings → Backup). Regardless,
|
|
copying the `data/` folder backs up your settings and local logbook. See
|
|
[[Settings and Data]].
|
|
|
|
## What follows the active profile
|
|
|
|
Every setting is per profile, station hardware included. Switching profile
|
|
reconnects the **CAT link**, the **amplifiers**, the **motorized antenna**, the
|
|
**Antenna Genius** and the **tuner** using the new profile's settings — so an
|
|
operator with, say, an SPE on COM9 for HF and another on COM10 for 6 m gets the
|
|
right one by switching profile, with no visit to Settings.
|
|
|
|
The Winkeyer is deliberately left alone: you connect it explicitly.
|