How to launch rigctld without commands: Hamlib Launcher for amateur radio operators

Many times we’ve heard complaints about Hamlib from frustrated users who can’t get their radios to connect to programs that use rigctl.exe. The port isn’t detected, the model doesn’t show up, you have to run commands in a console like it’s the 90s again…
The truth, however, is that Hamlib is an open source gem. It’s the library used by programs as popular among amateur radio operators as WSJT-X, Fldigi or CQRLOG to control radios remotely, robustly and across platforms.
What is Hamlib?
Hamlib is, put simply, a kind of “driver library” for transceivers. It acts as a middle layer that translates generic commands into instructions specific to each radio model.
In more technical terms, Hamlib provides a standard API for radio control. This means a software developer doesn’t have to write a separate driver for every model: they use Hamlib and that’s it. And all you need to do is configure it properly to make it work.
What difficulties does it present?
When developers build a program and decide to integrate Hamlib, they usually only include a handful of drivers. If your radio isn’t among them, you’re stuck using Hamlib on the outside: running rigctld.exe manually, typing parameters by hand… Not exactly pleasant.
What is rigctl.exe?
rigctl.exe lets you send commands directly to the radio. Many programs that use Hamlib offer an option called “Hamlib NET rigctl”, which lets you connect through port 4532 to an external rigctld that you configure yourself.
That way you can use your radio’s real driver even if it’s not listed in the software.
HamLib Launcher
While tinkering with rigctl.exe alongside my friend Alberto, from Riojanos por la Radio, we had the classic “man, this has to be simplifiable” conversation. Between testing and swapping experiences, the idea came up of building a visual launcher so people wouldn’t have to deal with the command line.
I’d recently built a Hamlib driver that lets me use my own interface with CB and 10-metre radios through this library. Since I already had the topic fresh in my mind, I took the chance to turn that knowledge into something useful for more people.
And that’s how this HamLib Launcher was born: a lightweight, no-nonsense tool I’m sharing here in case it’s useful to you. It’s a small program that launches rigctl.exe without you having to type a single command.
As simple as:
- Run the launcher
- Enter your settings in a friendly interface
- And start/stop
rigctl.exewith a single click
Thanks to Alberto’s help, it’s available as a working .exe for 64-bit Windows 7, 10 and 11.
Prerequisites
- Windows 7, 10 or 11 x64.
- Control cable and drivers installed.
- Hamlib with
rigctl.exe,rigctld.exeand therigs/folder.
Step 1: Install Hamlib
- Go to Hamlib’s official releases page: https://github.com/Hamlib/Hamlib/releases/tag/4.6.5
-
Look for the file ending in
win64.exe(for example hamlib-w64-4.6.5.exe) and download it. It’s the installer for 64-bit Windows. -
Run the installer and follow the on-screen steps.
By default, it will install into a folder like:
C:Program Fileshamlib-w64-4.6.5
- Once installed, download the rigs folder from the official source code: https://github.com/Hamlib/Hamlib/tree/master/rigs
-
Extract that folder, rename it to rigs and copy it inside the directory where Hamlib was installed.
It should end up looking like this:
C:Program Fileshamlib-w64-4.6.5 ├─ lib ├─ src └─ rigs ├─ yaesu.c ├─ icom.c ├─ kenwood.c └─ ...
- Folder: where
rigctld.exeis located. - COM port: the one your cable uses.
- Baud rate: 9600, 19200, etc.
- Model: pick yours from the list.
Step 2: Run the launcher
Place HamlibLauncher.exe in C:Programashamlib_launcher and run it.
Step 3: Configure your radio
Step 4: Run rigctld
Click “Run rigctld”. The program connects through localhost:4532. Click again to stop it.
Persistent configuration
The first time you run the program, a config.json file will be created in the .exe’s directory so your settings get saved.
Common issues and fixes
| Issue | Suggested fix |
|---|---|
rigctl.exe not found | Check the Hamlib folder. |
| Models don’t load | Make sure you have the rigs/ folder. |
| COM port doesn’t show up | Check the cable and driver. |
rigctld won’t stop | Restart the program or the system. |