I run a number of different rigs, and have a number of instances of rigctld that I have configured for each (further complicated by my FTX-1 requires a non mainsteam build at the moment). IT appears in CAT control I should be able to configure it to use network control to connect to my running daemon, but it never allows a complete config. As it stands any attempt to run CAT control kills my running instance.
Am I missing something or are there any plans to allow network connect to an instance of rigctld?
If I may add to this request or add a bit of flavor. I noticed that when I’m using the WRL CAT Control I can set my WSJT-X rig to ‘Hamlib NET rigctl’ and set the Network Server to ‘127.0.0.1:4532’ and it works perfectly to control my rig for changing the frequency, mode and PTT control. I can telnet to 127.0.0.1 with port 4532 and issue reads and writes successfully. So it should be fairly trivial to add this to the CAT Control app or a companion application. Since CAT Control is using rigctrld it can read the capabilities of the rig selected to present the functional interface to the user. I’m going to just build a simple front end to play around. I’m using an IC-705. Joe - KK7PZE
Just finished a prototype application utilizing a telnet session to the WRL CAT Control application and passing commands. It works perfectly. I wanted a way to quickly change bands and modes on my IC-705 from the Computer. I tested a few other features that worked, but some didn’t that were listed in the rigctrld documentation so I’m not sure if you’ve utilized the complete library of commands and I couldn’t even send raw CI-V data to do them. But this works great for what i want as I also have WFView to do most of the other things from the desktop.
