Re: [Hamlib-developer] Difference in caps.has_get_level between Windows and Debian.

[<gm...@bt...>]

Thanks Mike, comments in-line.

________________________________
From: Black Michael <mdb...@ya...>
Sent: 09 September 2024 1:36 PM
To: ham...@li... <ham...@li...>; gm3zza <gm...@bt...>
Subject: Re: [Hamlib-developer] Difference in caps.has_get_level between Windows and Debian.

WFView implemented their own rigctld server which is not fully capable.  You will not be able to get the caps data from it unless they implement it.

And it appears it is supported in the Linux version but not in the windows version. So I've raised a query on the wfview support forum.

What does work (seems there are some timing problems between WFView for serial I/O but the TCP server works well)

Use the External Control in WFView and set up a TCP Server Port (e.g. 4534) than hook up the real rigctld to it.

Find your rig's model# "rigctl -l | find "7300""

Then run rigctld

rigctld -m 3073 -r 127.0.0.1:4534 -vvv -Z

Now you'll be able to connect to rigctld normally (port 4532) and the caps query should work.

I'm trying it with the IC-705 to avoid a double hop through wfview.

I get a whole lot of messages from rigctld when I start it after starting wfview, and then when I try and connect my app to it, it thinks for a while then reports that the power is off and eventually disconnects. Wfview is still displaying the spectrum so it's obviously not powered off. I've captured another attempt. This time it just stayed at powered-off.

I'll put this to one side for now as it's not a big loss of functionality - I just won't know if the logged power is correct but it will show 0W so it's obviously not valid.


      Mike W9MDB

Phil GM3ZZA








On Monday, September 9, 2024 at 02:15:33 AM CDT, gm3zza via Hamlib-developer <ham...@li...> wrote:





The reason I recently updated hamlib on my Windows machine was that for rig 'NET rigctl' the Windows version had all ones whereas the Debian version had a value in it. These are both connecting to wfview.

This is still the case with the latest version dated 20240902.

I had a quick look at the code, but it appears dynamically allocated so couldn't work it out. If you get the info from the partner app, then it may be that at fault.

Phil GM3ZZA
_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer