Settings and Data

Settings and Data

Where everything lives

A data/ folder is created next to OpsLog.exe:

• Settings database (SQLite): settings, profiles, rigs/antennas, cluster nodes, lookup cache, award lists, QSL templates. Always local.
• Logbook (logbook.db, SQLite): QSOs, when the profile logs locally.
• data/qsl/templates/… — QSL card templates and their photos.
• data/qsl/outbox/… — sent QSL card JPEGs.
• Recordings folder (configurable) — per-QSO WAV/MP3.
• Backups, diagnostic logs.

Paths are stored relative to the folder, so the whole OpsLog directory can move to another drive or PC. Back up your setup by copying data/. See Profiles and Databases for local-vs-MySQL logbooks.

Settings map

Section	What
General	language, theme, date format (US / FR / Standard), Main-view panes, digital-modes grouping, Super Check Partial, ClubLog exceptions & Most Wanted
Station	your callsign, grid, name, address (my-station ADIF) — hand-corrected CQ/ITU zones stay corrected
CAT	radio backend + connection, CAT sharing (rigctld), protocol trace (CAT Control)
Lookup	QRZ.com / HamQTH credentials
Audio	DVK / recorder devices, PTT, gains and levels, RX monitor
CW Keyer	engine (WinKeyer / Serial / Icom / Flex CWX / Yaesu / TCI), macros, ESM
External services	LoTW (TQSL), QRZ, eQSL, ClubLog, HRDLog, POTA, Cloudlog/Wavelog
Email	SMTP for eQSL-by-email and Send log to F4BPO
Amplifier / Tuner Genius / Antenna Genius / Rotator / Antenna	station hardware (Amplifiers and Switches · Maps and Antennas)
Database	settings DB + this profile's logbook, rename/relocate
Backup	database + ADIF backup at shutdown

Appearance & language

Four themes (Warm light, Warm dark, Graphite dark, High contrast) plus Auto (follows the OS); fresh installs start dark. Full English / French UI with a first-run flag chooser and a switcher in Settings → General. Ctrl + wheel zooms the whole UI (remembered; Ctrl+0 resets). The window title bar is drawn by OpsLog — drag the top bar to move, double-click to maximise — and the window reopens on the screen it was closed on.

UDP integrations

• Inbound: WSJT-X / MSHV / JTDX QSO logging and status (unicast or multicast), and DXHunter remote-call packets (fills the callsign, tunes the rig when the packet carries <FREQ>/<MODE>).
• Outbound: the current frequency to PstRotator, radio info in N1MM RadioInfo format, or an ADIF record on each logged QSO.

Other

• Autostart external programs (WSJT-X, JTAlert, rotator control…) at launch, skipping any already running.
• Update check at startup, when opening Help → About, and every 5 minutes. A "What's new" summary appears on the first launch after each update.
• Help → Send log to F4BPO (shown when SMTP is configured) e-mails the diagnostic logs straight to the developer.
• Anonymous usage telemetry — a once-a-day heartbeat (random install ID + version + OS; no callsign or QSO data). Opt out in Preferences.
• LoTW user list — downloads ARRL's public list of LoTW users and their last-upload date, which is what puts the colour-coded LoTW badge beside a callsign: green under a week, amber one to four weeks, red over thirty days.
• Web publish — writes your log as a file for a website: a standalone HTML page or a CSV, kept locally and optionally uploaded by FTP. It is refreshed when you log a QSO and, if you set an interval, on a timer.
• Folder sync — point every OpsLog at the same folder, one your PCs already synchronise (Seafile, OneDrive, Dropbox, a NAS share). Each machine writes what it logs there and reads the others'. The databases themselves are never shared, so this is not a substitute for the MySQL logbook (Profiles and Databases).
• QSL sent via — older OpsLog versions, and many ADIF imports, stored the sending method (bureau, direct, electronic) in the field where the QSL manager belongs. OpsLog offers once to move those to the proper QSL_SENT_VIA field.

Bands and modes: your lists, everywhere

Two list editors decide what the rest of the interface offers.

• Bands — pick the ones you actually use. The entry strip, the band-slot grid and the band-map switcher only show what is in the right-hand column, and the order there is the display order.
• Modes — the same, and anywhere the interface shows a mode picker it iterates that column. Selecting a mode in the entry form also fills RST sent/received from the defaults set here, unless you have already typed something.
• RST lists — the choices offered in the entry form's RST dropdowns, per mode family. One value per line (or space-separated); the first is the top of the list.

Default confirmation statuses

The QSL / eQSL / LoTW / upload status every QSO starts with — for one typed in by hand and for one auto-logged over UDP from WSJT-X, JTDX or MSHV alike. Leave a field blank to keep that column empty on the QSO. See QSL Management, which explains why sent = Yes means a QSO is never uploaded.