Re: [Hamlib-developer] [SPAM] Re: rig-multicast?

[Chris R. <chr...@ch...>]

I wasn't aware that Log4OM uses rigctld but indeed it does, I can 
connect to my rig using Log4OM and connect WSJT-X to it using the 
"Hamlib NET rigctl" option.  I can also see rigctld in the background 
process list.

I've had a lot of experience with connecting hardware to multiple 
software applications both in my day job, where it was electron 
microscopes and for amateur astronomy using the ASCOM platform.  What 
made it challenging was unhelpful applications which will poll the 
hardware as fast as they can which can overwhelm the hardware or put the 
hardware control in their UI process so when the hardware takes time to 
respond the UI gets unresponsive.  Hardware that's slow to respond - and 
if you are using a 9600 baud serial port - response times can be in the 
10s of milliseconds was also a problem.  It also doesn't help when a 
command doesn't send any response, how do you know when it's safe to 
send the next command?

I found that the best way was to set up a separate serial control 
process with a concurrent queue of transactions. Each App control 
instance would put a transaction on the queue and block until the serial 
control process had processed the transaction.  The serial control 
process would read the queue at a rate that suited the hardware. Status 
properties would use a throttled control process where the previous 
value would be returned until it was more than a reasonable age to keep 
polling commands at a reasonable rate.

I'm sure that Hamlib will have the same issues.  I was using C# and .NET 
to handle this but I'm sure there are similar solutions in Linux.

Hope this helps,

Chris, G5CTH

On 04/11/2025 22:39, David Balharrie wrote:
>
> Log4OM uses rigctld, it does not use the api library.
>
> This is its config panel
>
> 73 de David M0DGB/G8FKH
>
> *From:*Michael Morgan <cmo...@gm...>
> *Sent:* 04 November 2025 20:22
> *To:* Uwe, DG2YCB <dg...@gm...>
> *Cc:* ham...@li...
> *Subject:* [Hamlib-developer] [SPAM] Re: rig-multicast?
>
> It just passes through the capabilities of the rig so if PWR and SWR 
> is available it still would be available.
>
> I could try and type up some notes on how to launch it.  And it should 
> work with any application that works with HamLib - so Log4OM would be 
> good.
>
> Michael
>
>
>
>     On Nov 4, 2025, at 10:45 AM, Uwe, DG2YCB <dg...@gm...> wrote:
>
>     Hi Michael and George,
>
>     Thanks for your replies. Would this approach also work with
>     Log4OM? And an additional question: Is the Read PWR and SWR
>     feature supported by rigctld? Because there were actually a few
>     requests about this some time ago (especially from OMs who use
>     Log4OM but would like to continue using the Read PWR and SWR
>     feature, which is not possible with OmniRig).
>
>     If the approach with rigctld would solve this problem for and with
>     Log4OM and WSJT-X (Improved): Could one of you two perhaps be so
>     kind as to briefly explain the setup in a PDF (preferably with a
>     few screenshots)? Then we could make it available to these OMs (or
>     I could put it on my SourceForge page). Thanks.
>
>
>     73 de DG2YCB,
>     Uwe
>     ________________________________________
>     German Amateur Radio Station DG2YCB
>     Dr. Uwe Risse
>     eMail: dg...@gm...
>     Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB>
>
>     Am 04.11.2025 um 16:58 schrieb George Baltz:
>
>         As AA5SH wrote, the current way to handle multiple users is to
>         use rigctld.  My setup is to have cqrlog configured to start
>         rigctld, and then I tell cqrlog(via ctrl-J) to fire up WSJT-X
>         (Improved), configured to use 'Hamlib dummy' as the rig on
>         127.0.0.1:4532
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer