Project

General

Profile

Actions

Feature #50

closed

Interface to hamlib, esp. rigctld

Added by David Hagood almost 13 years ago. Updated almost 13 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/28/2012
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
I read the instructions above:

Description

Usually, I have my radio tied into an instance of Hamlib's rigctld, to allow software such as PSK-31 software to work. However, it would also be nice to be able to modify the radio's memories without shutting down rigctld, so it would be nice if CHIRP could support interfacing to Hamlib, and would allow selecting the Hamlib rig ID and device (including the RPC "rig" and IP address).

Actions #1

Updated by Dan Smith almost 13 years ago

  • Status changed from New to Rejected

Hi David,

I'm not sure which rig you're using that is supported by both CHIRP and hamlib -- perhaps one of the Yaesu HF radios? Hamlib, to my knowledge, does not support the type of operation that CHIRP needs to clone a radio. It is possible that this may work for some of the Icom CI-V radios, but it would be a lot of work.

I spent quite a bit of time trying to get hamlib instrumented in a reasonable way from Python that would be cross-platform. I decided that it was likely a lot more work than it was worth.

Since I don't have any intent to revisit this any time soon, I'd like to close this issue for the time being. However, being a linux user, it's definitely something I'll keep an eye on and maybe decide to work on it sometime later when the time/situation fits.

Thanks!

Actions

Also available in: Atom PDF