FreeDV Hamlib support

[Joel Stanley]

Hello list,

I've been watching the list these past few months, and have noticed a
large demand for enhanced rig control in FreeDV. I decided to take a
look at what was involved, and from there got stuck right into it.

I've written a hamlib class that provides an interface to the hamlib
library. Currently it queries hamlib for the list of rigs to populate
the dropdown for the config window. Eventually it may need to spawn a
thread to do the hamlib serial port stuff - this is how fldigi handles
hamlib, I presume to make sure it doesn't slow the UI down while doing
serial comms.

I've also got the settings all hooked up, getting saved when the
screen is opened and closed, and persisted to disk. Next step is to
have it talk to the rig, which means I need to build a rig interface
cable for the FT-817 I have at home.

I've attached a screenshot of the current work in progress. It's
modeled on the hamlib interface window in fldigi. As you can see, the
previous libctb based controls are still there for now.

I'm happy to take on board feedback from those who have experience
with rig control to make it easier to use, but keep in mind that it's
a work in progress at this stage.

Cheers,

Joel
VK5FJMS

[Bruce Perens]

Hi Joel,

Joel,

Obviously this is important. I suggest you work with Richard Shaw to get
Hamlib into his cmake configuration as an optional feature (for now).

Hamlib should not put another thread to sleep by doing blocking I/O to
the serial port. Having its own thread is the conceptually simplest way
to handle this and perhaps the most portable. If you can write with
#ifdef around it, using that cmake option to turn it on, that might be
best. That way we can test one source code version with both control
methods, until we are sure hamlib works and can retire libctb.

Thanks

Bruce

[Tony Langdon]

On 20/05/13 11:58 AM, Bruce Perens wrote:
> Hi Joel,
>
> Joel,
>
> Obviously this is important. I suggest you work with Richard Shaw to
> get Hamlib into his cmake configuration as an optional feature (for now).
>
> Hamlib should not put another thread to sleep by doing blocking I/O to
> the serial port. Having its own thread is the conceptually simplest
> way to handle this and perhaps the most portable. If you can write
> with #ifdef around it, using that cmake option to turn it on, that
> might be best. That way we can test one source code version with both
> control methods, until we are sure hamlib works and can retire libctb.

Hmm, looks like I will have to get my station back on the air. Off air
due to moving house, and haven't had a chance to put any antennas up
yet. I have an IC-7000 and FT-736R (with a hardware converter that
makes it look like an FT-847 to software) to test with. Both radios
have been successfully used with Ham Radio Deluxe and other rig control
software in the past.

--
73 de Tony VK3JED
http://vkradio.com

[jdow]

Joel, it would be better to make FreeDV into a tool that communicates
with a real rig control program rather than provide crippled rig
control in the name of a fancier TR interface.

Let FreeDV concentrate on what it does well and let a real rig control
program concentrate on doing what it does well plus provide a good and
flexible plugin interface.

{^_^} Joanne/W6MKU

> freedv-hamlib-wip.png
>
>

[John Hays]

Hamlib also provides PTT via CAT, a sorely needed feature, which argues for integration / inclusion.

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "digitalvoice" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
> To post to this group, send email to digita...@googlegroups.com.
> Visit this group at http://groups.google.com/group/digitalvoice?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[jdow]

If FreeDV uses it then you've locked out other remote control programs.

That is unacceptable. The programs should work together.

{^_^}

[Berndt Josef Wulf]

G'day,

Not really, as this can be implemented as a plugin where users decide
which plugin to run, if any.

Hamlib has gained a wide acceptance in other HAM Software. I've been
using Hamlib successfully to control Yaesu, Icom and TenTec radio
equipment and can only speak highly about it.

Agreed, FreeDV is about digital communication, but since its open source
it doesn't preclude anyone from adding new features.

My 2 cents

73, Berndt
VK5ABN

[aa777888]

Not true where HRD is concerned. Simply use the "third party serial port" feature of HRD to accept the Hamlib CAT commands from a Hamlib capable version of FreeDV. Indeed, this is how I normally run, with Fldigi interfaced to HRD and HRD controlling the radio.

Setup for Flex systems is similar to HRD.

If Flrig is preferred then FreeDV will have to implement the xmlrpc feature in FreeDV used with Flrig. Again, completely within the realm of possibility.

What other remote control programs would need to be supported?

[Bruce Perens]

There must be someone out there who wants to write a good open H R D clone

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[Nate Bargmann]

* On 2013 20 May 19:36 -0500, Bruce Perens wrote:
> There must be someone out there who wants to write a good open H R D clone

Dunno about it being a clone, but CQRlog does a quite fine job for me as
an everyday logger. It integrated well enough with LoTW that I
transcribed my paper logs into it a couple of years ago. But then I
don't worry about the DX tracking and such as I look that up on LoTW
when I care to.

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us