rouggyandClaude Opus 5
82cd5c5d0b
HAMLOG.online was added after most profiles were configured, so it had no entry in the shipped defaults and no stored value either: it came back blank, and blank is not a status anybody chose. Every service now starts the same way — the sent side at R, the received side at N — and a blank left by a service that did not exist when the operator last saved is filled in from that. A status they chose themselves is untouched. Two tests hold the line: no sent side may default to Y, and no field may be left without a default. Y means "already sent", so it makes the uploader skip the contact for ever — an operator with eQSL Sent at Y had a logbook that never reached eQSL, and the only trace was one line in the application log. Wiki, both from operator reports: QSL Management opens with Confirmations — what the page actually is (the status stamped on every new QSO, not an action), what each status does, and the warning about Y in the plainest words available, because it fails silently and by design. Digital Modes and GridTracker is new. Unicast and multicast explained from the operating problem rather than the networking: one letterbox that two programs watch, against a broadcast everyone can tune to. It carries the real evidence — two starts of one station an hour apart, decodes in the second and none in the first, the only difference being whether GridTracker or OpsLog reached port 2237 first — then the settings for WSJT-X, JTDX, MSHV, GridTracker and OpsLog, the 127.0.0.1-in-the-group-box mistake, what to do if unicast is unavoidable, and how to check it from the log. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
2.2 KiB
OpsLog
A modern, fast ham-radio logger for Windows — Log4OM-style entry, real-time CAT for OmniRig, native FlexRadio/SmartSDR, Icom CI-V (USB and remote-over-internet, replacing RS-BA1), Yaesu, Kenwood, Xiegu and TCI (SunSDR / Expert Electronics) — with CAT sharing so WSJT-X & co use the same rig link — a DX cluster with spot alerts, awards tracking, maps, contest logging, QSL management and a QSL-card designer.
Built with Wails v2 (Go backend + React/TypeScript frontend), pure Go (no CGO). SQLite holds the configuration; the logbook can be the local SQLite file or a shared MySQL database so several operators run one log. Fully themeable and bilingual (English / French).
Developed by F4BPO.
New here? Read these first
- Installation — download / build and first launch.
- Getting Started — the entry strip, logging your first QSO, choosing a profile.
- CAT Control — connect your radio (OmniRig, FlexRadio, Icom, Yaesu, Kenwood, Xiegu, TCI).
What OpsLog does
| Area | Pages |
|---|---|
| Enter and manage QSOs | Logging Basics · Recent QSOs and Filters · Import and Export ADIF |
| Control your radio | CAT Control · FlexRadio · Icom · Remote Icom over the Internet · Yaesu · Kenwood and Xiegu |
| Chase DX | DX Cluster and Spots · Maps and Antennas |
| Digital modes | Digital Modes and GridTracker · Connections |
| Station hardware | Amplifiers and Switches · Audio and Keyers |
| Events & contests | Contest Logging · Net Control · Multi-Operator Live Status |
| Confirmations | Awards · QSL Management · QSL Card Designer |
| Configuration | Settings and Data · Security · Profiles and Databases |
| Something wrong? | Troubleshooting |
Design in one line
Everything you configure (settings, profiles, rigs, cluster nodes, award lists, QSL templates, lookup cache) lives in a local SQLite file so the UI is instant. Only the QSOs live where the active profile points them — local SQLite or a shared MySQL. See Profiles and Databases.