Diagnostics (ports and processes)
The program checks what is going on in the computer: which RigAndLog programs are running, who holds the COM port of the radio and which network ports (UDP, TCP) are in use. It helps when the radio “does not want to connect” because another program holds its port, or when a program stayed in the background after it was closed.
The most common use: the radio port is busy - Diagnostics shows which program holds it.
How to start it
- RigAndLog: Configure LogBook and program (the F11 key) → the LogBook tab → System Diagnostics.
- HamlibStarter: menu button → System diagnostics (ports, processes).
- By hand: the
SystemDiagnostics.exefile in the RigAndLog program folder.
The window has four tabs: Processes, COM Ports, UDP Ports, TCP Ports. The Refresh List button in each of them checks everything again.
The “Processes” tab
A list of RigAndLog programs and their helpers: RigAndLog, OmniRig, Hamlib rigctl, Hamlib Starter, the camera module, the NTP time sync module, UDP Hub - with the number of running copies.
- Select a program and click Kill selected processes - useful when a program has “hung” or stayed in the background after it was closed.
- A warning appears before the program is ended. The Cancel button is active by default, so Enter does not close anything by accident.
Ending a process closes the program at once - without saving settings and data. Ending OmniRig or rigctld
also disconnects other programs that use them (e.g. WSJT-X). Try to close the program normally first.
The “COM Ports” tab
All COM ports in the computer and their state. The program briefly tries to open each port to check whether it is free.
| State | What it means |
|---|---|
| Available | The port exists and nobody uses it - a middleman (OmniRig, rigctld) can open it. |
| In Use | The port is held by another program. If it is the radio port and the radio does not work - check who it is (below). |
| Not Found | There is no such port in the system (the radio is switched off or the cable is disconnected). |
| Device Error | The port is there, but the device or its driver reports an error (e.g. USB disconnected). |
| No Response | The port did not answer in time (it happens with Bluetooth ports). |
| Invalid Port Name, Unknown Error | Rare - the port has an unusual name or Windows reported another error. |
Who holds the port? - “More Info”
Click More Info in the port row. The details window shows the process name, PID and path of the program that holds the port. There are also the Copy to Clipboard, Show in Explorer and Release COM port buttons (it ends the program that holds the port - the same warning as above).
Finding the port owner is an experimental feature. It works best when you start Diagnostics as administrator (right-click the file → Run as administrator) - otherwise some programs may be invisible.
The “UDP Ports” and “TCP Ports” tabs
They show the network ports used in the computer: IP address, port number, PID and program name. For TCP also the connection state (e.g. Listening - the program waits for connections, Connected - a connection is open). More Info in a row opens the process details with the Kill this process button.
The ports you will see most often:
| Port | Type | Who usually uses it |
|---|---|---|
| 2237 | UDP | WSJT-X / JTDX send data here - UDP Hub or a program receiving data from WSJT-X listens |
| 2238-2242 | UDP | UDP Hub outputs: GridTracker, HamClock, RigAndLog etc. |
| 4532 | TCP | Rig 0 of HamlibStarter (or a single rigctld) |
| 4533-4536 | TCP | Rig 1-4 of HamlibStarter (the rigctld of each radio) |
Typical situations
The radio does not connect - a “port busy” / “Access denied” message
The COM Ports tab → the radio port has the In Use state → More Info. You will see which program holds it. Close it normally (e.g. the radio manufacturer's software, a second logger). If that does not work - Release COM port.
UDP Hub does not start - the port is busy
The UDP Ports tab → find the hub port (usually 2237) and check which program uses it. Often it is a second program set to the same port. UDP Hub also has its own diagnostics - see UDP Hub.
HamlibStarter reports a port conflict
The TCP Ports tab → check who listens on the port of the Rig (e.g. 4533). It may be an old rigctld started by hand
or another program.
The program is closed, but it “does not want” to start again
The Processes tab → if the program still has a running process, select it and Kill selected processes.