Hamlib - the “address:port” client
Hamlib knows several hundred radio models. The radio is controlled by a small program, rigctld: it holds the radio cable
and waits for questions from programs at a given address and port. RigAndLog connects to it the way a web browser
connects to a website.
Address and port - in plain words
- The address says which computer
rigctldruns on.127.0.0.1means “this same computer”. A radio at another computer has the address of that computer in your home network, e.g.192.168.1.20. - The port is the number of the “door” where
rigctldwaits, e.g.4532. Each radio has a different door.
0.0.0.0 means “accept connections from other computers too”. The arrow shows who connects to whom.
When to choose the classic client
- you have your own rigctld - started by a script, by another program, on a Raspberry Pi or on another computer;
- RigAndLog should be together with WSJT-X on Rig 0 of HamlibStarter - always on the radio you choose in HamlibStarter (see HamlibStarter);
- you work under Linux (Wine).
If the radios are started by HamlibStarter, the HamlibStarter client (Rig 1-4) is usually more convenient - then the ≡ menu shows all Rigs with a coloured status LED.
Setup
- Rig window → Menu → RIG (TRX) configuration → tick Hamlib and choose Hamlib client (address:port).
- Click Configure. In the Hamlib Configuration window enter the
IP address (e.g.
127.0.0.1) and the Port (e.g.4532). In IP alias you can enter the radio name - the window then shows “FTDX101D” instead of the address. - OK in both windows. In the Rig window: ≡ on the row → Hamlib.
After the address or port is changed, the channel reconnects by itself - there is no need to restart the program.
Other options of the “Hamlib Configuration” window
| Option | What it does |
|---|---|
| Run Hamlib Starter to start the server if necessary | At startup RigAndLog starts HamlibStarter by itself (if it is not running yet). |
| Close Hamlib Starter with RigAndLog | When RigAndLog exits, it closes HamlibStarter - only if RigAndLog was the one that started it. |
| Extended rigctld responses (command echo) | An option for unusual servers - change it only when something does not work. |
| Advanced options | SWR reading while transmitting (Check SWR) and an alarm when a limit is exceeded. Detailed CAT log (off by default) writes every command sent to rigctld and every radio response to the program log (LOGS\LOG_RigAndLog). Turn it on only when reporting a radio problem: repeat the situation, note the time and send the log file of that day. Then turn it off - the log grows quickly. |
When HamlibStarter is running, the window also shows the state of its Rigs and of the port for programs (Refresh status).
Modes and bands
Through Hamlib RigAndLog knows the full list of modes (also RTTY, PSK, DATA-FM, C4FM, DV) and handles frequencies above 2 GHz (e.g. IC-905). From 1 GHz the display of the Rig window switches to a longer format by itself.
Why is there only one “Hamlib” item in the ≡ menu?
The classic client is one address and one port, so one radio. Two radios through Hamlib - use HamlibStarter (Rig 1-4), or one radio through Hamlib and the other one through OmniRig.
Where do I get rigctld?
It is part of the Hamlib library, which you download from the Hamlib project page (GitHub, a file like hamlib-w64-4.7.2.zip).
Unpack it to any folder - rigctld.exe is in the bin subfolder. HamlibStarter asks for this file
in the Hamlib library window and from then on starts rigctld for each radio by itself.
Under Linux you point to the Linux rigctld (e.g. /usr/bin/rigctld).