# Remote Icom over the Internet

OpsLog speaks the Icom radio's **built-in network protocol** directly, so it
**replaces both the Icom Remote Utility and RS-BA1**. Radios with a LAN server —
**IC-7610, IC-9700, IC-705, IC-7760, IC-905** — can be operated over the
LAN/internet with the full [[Icom]] console.

> The **IC-9100 has no LAN server** — it is USB-only.

## On the radio (one-time)

In the radio's **Network** menu:

1. Enable the network / *Remote settings*.
2. Set a **Network User1** name and password.
3. Note the radio's **IP address** and its **CI-V address**.
4. Make sure the Icom **Remote Utility is closed** on every PC — OpsLog binds the
   same local UDP ports, so they can't both run.

## In OpsLog

Settings → CAT → backend **Icom CI-V (network / remote)**:

- **Host** — the radio's IP or hostname.
- **User / Password** — the Network User1 credentials.
- **Rig model / CI-V address** — pick the model.

Save. OpsLog logs in, obtains a session **token** (auto-renewed so control never
drops after ~2 minutes), opens the **CI-V tunnel**, and the whole console works
over the net — freq / mode / DSP / TX / RIT / CW / scope.

## How it stays solid

- **Token renewal** every ~45 s keeps the session alive.
- **Receive-side retransmit**: under the heavy panadapter stream, lost UDP
  packets are re-requested, so the link doesn't drop when the scope is on.
- **Standby-tolerant**: the radio's server answers pings even when the radio is
  off, so the session doesn't flap — the console + power ON button stay reachable.
- **Manual power** ON / OFF (the app never wakes the rig on connect).

## Audio

Network **audio** is a work in progress. For now, use the radio in **USB + a
voice link** (e.g. Mumble) alongside the network CAT, or run OpsLog on the
station PC via remote desktop. See [[Audio and Keyers]] for the USB-monitor
option.

## Troubleshooting

- **"Login rejected"** → wrong Network User1 name/password.
- **Can't bind local port / dial fails** → the Icom **Remote Utility** is still
  running; close it.
- **Link drops when the scope turns on** → should be fixed by receive-side
  retransmit; if it persists, check the log (`icom net:` lines) and network
  quality. See [[Troubleshooting]].