Files
OpsLog/wiki/Troubleshooting.md
2026-07-09 16:51:57 +02:00

59 lines
2.4 KiB
Markdown

# Troubleshooting
## Where's the log file?
OpsLog writes a diagnostic log. The path is shown in Settings (and can be opened
from there). When reporting a problem, include the relevant lines — they're
prefixed by subsystem (`Flex:`, `icom net:`, `icom scope`, `antgenius:`,
`cluster:`, `qslmgr:log`, `audio:`…).
## CAT
- **Radio not connecting** — check the backend fields (COM port + baud for USB;
IP/credentials for network). OpsLog connects non-blocking, so it won't freeze —
watch the CAT status.
- **Icom: no CAT at all over USB** — the CI-V address must match the radio; pick
your **model** from the dropdown (it sets the address) and set *CI-V USB Echo
Back* **OFF** on the rig.
- **Icom scope blank on an IC-7300** — this was a bug where the scope decoder was
chosen from the configured CI-V address; it now uses the model detected from the
CI-V ID, so a single-scope rig run at address `0x98` decodes correctly. Update
to the latest build.
- **Icom attenuator button does nothing** — the dB steps are model-specific; make
sure the right model is selected (IC-7300 = 20 dB, IC-7610 = 6/12/18 dB).
## Remote Icom
- **Login rejected** → wrong Network User1 name/password.
- **Can't bind local port** → the Icom **Remote Utility is still running**
close it.
- **Link drops with the scope on** → receive-side retransmit should hold it; if
not, check network quality and the `icom net:` log lines. See
[[Remote Icom over the Internet]].
## FlexRadio
- **A control reads 0 / stale at startup** — some SmartSDR status fields use short
names (e.g. the TX filter is reported as `lo`/`hi`, not `filter_low/high`). If a
value never populates, capture the `Flex: … status` log line and report it.
- **Antenna wrong band on a spot click** — fixed: `SetFrequency`/`SetMode` update
the slice cache immediately so the panel and the Ultrabeam follow don't chase a
stale frequency.
## Multi-op live status PHP
`Connection refused` from the PHP page is almost always MySQL `bind-address =
127.0.0.1` or a firewall/grant issue — see
[[Multi-Operator Live Status]].
## DVK / PTT
- **Test PTT does nothing on CAT/OmniRig** — the key is held ~1.5 s so the async
OmniRig write is actually sent; if it still doesn't key, the rig's OmniRig
profile may not expose CAT TX keying — use RTS/DTR or VOX.
## Still stuck?
Open an issue with: what you did, what happened, your radio/model, and the
relevant log lines.