Troubleshooting
Vehicle does not connect
Symptom: The indicator stays red even after pressing Connect.
- Make sure the radio link (HM30, MK32, telemetry) is powered on and paired
- Check that the connection profile uses the correct IP and port
- If using MAVProxy, verify the relay is running (
pgrep mavproxy) - Try pinging the link IP:
ping 192.168.144.20
Heartbeat received but no telemetry data
Symptom: Yellow indicator, no HUD data.
- ArduPilot may not be sending streams: use Connection → Request streams to force
REQUEST_DATA_STREAM - Check that
SR0_*orSR1_*are set to values > 0 in the parameters
App crashes on launch on macOS
Error "Harlock" is damaged and can't be opened:
xattr -cr /Applications/Harlock.app
Mission upload fails
- Make sure the vehicle is connected and receiving heartbeats
- Check that the mission does not contain waypoints with
0,0coordinates - Try downloading the existing mission first, then upload again
Parameters do not update
If PARAM_SET receives no response:
- Increase the timeout under Settings → Connection → Timeout
- Make sure the link is not saturated (e.g. high-frequency video streaming)
Logs and diagnostics
Application logs are located at:
| Platform | Path |
|---|---|
| macOS | ~/Library/Logs/harlock/ |
| Windows | %APPDATA%\harlock\logs\ |
| Linux | ~/.local/share/harlock/logs/ |
Enable verbose logging under Settings → Diagnostics → Log level: Debug to get MAVLink details.
Reporting a bug
Open an issue on GitHub with:
- Harlock version (visible under About)
- Operating system and version
- Steps to reproduce the problem
- App logs (see above)