FLRig and rigctld NET

[[e-mail] [linuxham]]

A search of the Goog turned up only an old post to this forum that went unanswered. Hopefully, I'll have better luck than Jose.

I have set myself down and worked out how to get rigctld to run and allow multiple programs to connect to one rig via the USB to Serial device. Unfortunately, FLRig's UI does not seem to be coded the same as FLDigi.

With FLDigi, the transceiver control can be setup under Hamlib by setting the Rig device to Hamlib NET rigctl, and given an ip address as the device, it will connect to the rigctld service and happily do its thing.

FLRig on the other hand, does not have an option for Hamlib NET rigctl, nor will it allow for the direct entry of a device address. In fact, FLRig will not allow the user to connect to any device NOT listed in the drop down box. This means that if a user creates a /dev/radio device which is pointed at a /dev/ttyUSB#, that /dev/radio device cannot be used. Instead, only the direct reference to /dev/ttyUSB# may be used and only if it is present in the drop down.

Would it be possible to align the UI of FLRig's configuration with that of FLDigi, such that FLRig may be used with a rigctld service? Is it possible currently to run FLRig, perhaps with a CLI command, to connect to Hamlib NET rigctl rather than to a specific radio and serial device?

This would allow me to finally be able to run FLRig as my main radio interface, with FLDigi doing its digital work and CQRLog logging the contacts.

Please do not reply with any mention of XMLRPC as that only allows FLRig and FLDigi to run simultaneously, but does not allow any other program to access the USB/Serial device without conflicts.

All the best and Seven-Three,

Michael - K5WRN

[Geoff NW7GM [e-mail] [linuxham]]

Michael,

Each of the supported radios in FLrig are hard coded into the program
itself. There is, however, an alpha version that may do something similar
to what you want. I was starting to play around with said version but life
got in the way and I haven't had a chance to 'play radio' in about a month
now.

Perhaps Dave could provide the details about the version I am referring to
(I can't remember the specific version number of that alpha).

Post by michael.k5wrn-***@public.gmane.org [linuxham]
A search of the Goog turned up only an old post to this forum that went
unanswered. Hopefully, I'll have better luck than Jose.
I have set myself down and worked out how to get rigctld to run and allow
multiple programs to connect to one rig via the USB to Serial device.
Unfortunately, FLRig's UI does not seem to be coded the same as FLDigi.
With FLDigi, the transceiver control can be setup under Hamlib by setting
the Rig device to Hamlib NET rigctl, and given an ip address as the device,
it will connect to the rigctld service and happily do its thing.
FLRig on the other hand, does not have an option for Hamlib NET rigctl,
nor will it allow for the direct entry of a device address. In fact, FLRig
will not allow the user to connect to any device NOT listed in the drop
down box. This means that if a user creates a /dev/radio device which is
pointed at a /dev/ttyUSB#, that /dev/radio device cannot be used. Instead,
only the direct reference to /dev/ttyUSB# may be used and only if it is
present in the drop down.
Would it be possible to align the UI of FLRig's configuration with that of
FLDigi, such that FLRig may be used with a rigctld service? Is it possible
currently to run FLRig, perhaps with a CLI command, to connect to Hamlib
NET rigctl rather than to a specific radio and serial device?
This would allow me to finally be able to run FLRig as my main radio
interface, with FLDigi doing its digital work and CQRLog logging the
contacts.
Please do not reply with any mention of XMLRPC as that only allows FLRig
and FLDigi to run simultaneously, but does not allow any other program to
access the USB/Serial device without conflicts.
All the best and Seven-Three,
Michael - K5WRN