This page assumes that you know how to use rigctld.
rigctld is a daemon provided by hamlib that allows you to connect your software remotely to your hamlib equipment.
You can get some help from rigctld in the rigctld man page.
Just as an example you can see here how you can connect an IC-7300 to a raspberry pi.
This will open the 4532/TCP port in your server (the raspberry pi in this case) and will wait for connections.
Once you have done that, you need to go to the HamLib tab of the KLog settings.
Selecting NET rigctl as the radio will enable:
- The Server/Address box where you should have to enter the hostname or address of your server (the raspberry pi IP address in this case) and;
- The Port entry, where you should have to enter the port. The default port is 4532.
Once you have configured these information, you can alreadi click on the Red button named Test.
If everything goes well, you will see how the red button becomes Green, showing that the connection has been done.
Once you are here, you can simply click on OK and exit the Settings .
Running rigctld on boot with systemd in linux
If your linux system uses systemd then it is relatively straightforward to use a systemd unit file to start rigctld on boot with all the correct parameters already set for your radio.
Two files are needed:
- A configuration file: /etc/rigctld.conf
- The systemd unit file: /usr/lib/systemd/system/rigctl.service
http://svnweb.mageia.org/packages/cauldron/hamlib/current/SOURCES/rigctld.service?view=co
To configure for your radio edit /etc/rigctld.conf with the radio model ID obtained by using rigctl -l. Comment the OPTIONS= line unless you specifically need extra options. (Add # as the first character on the line to comment it)
To test the service, make sure rigctl or rigctld are stopped. Then as root:
systemctl daemon-reload
systemctl start rigctld.service
systemctl status rigctld.service
If there are no errors the service should be shown as running.
To stop it run: systemctl stop rigctld.service
Assuming all is well you can now make it start on boot by enabling it:
systemctl enable rigctld (note the “.service” can be left off for all these commands)
If you edit the config file or rigctld.service you MUST run 'systemctl daemon-reload' before testing again.
If you have problems and need detailed logging then you can uncomment the VERBOSE AND MILLITIME lines in the conf file.
Output can be viewed using:
journalctl -u rigctld
Work in progress
