Re: [Hamlib-developer] Python API
Library to control radio transceivers and receivers
Brought to you by:
n0nb
From: Nate B. <n0...@n0...> - 2025-04-03 09:31:11
|
This dropped into my administrator queue on Tuesday but Mailman never gave me a message to approve. 73, Nate ----- Forwarded message from ham...@li... ----- Date: Tue, 1 Apr 2025 14:58:15 +1000 From: Adrian <vk...@gm...> To: Stephen Pattinson <st...@bi...>, Dave Baxter <g8k...@go...>, n0...@n0..., Erik Icket <run...@gm...> Cc: ham...@li... Subject: Re: [Hamlib-developer] Python API User-Agent: Mozilla Thunderbird Just to add, node-red works well <> with hamlib, and it is how I access my windows FTDX101MP serial connected rigctld bat process from the lan with node-red running on Debian ; Then other flows like the SPE amp flow can be linked in/out to auto control drive power, and temperature protection. In node-red settings.js **/ process.env.RIGADDRESS = '192.168.0.2' process.env.RIGPORT = '4532' process.env.RIGADDRESS1 = '192.168.0.32' process.env.RIGPORT1 = '4532' module.exports = { Covers two rigs I have connected using hamlib rigctld. The other is lan connected to macos running rigctld connected to a FT-747GX. 73 vk4tux On 1/4/25 14:36, Stephen Pattinson wrote: > Hi Dave, Erik, Adrian & Nate, > > Thanks for your help guys. I now have my Python app talking to rigctld via > TCP and getting frequency, mode and tx status, which as was pointed out is > probably the preferred way to go. Of course, I could just use rigctl if > all I wanted to do was send the odd command to the radio, but the main > purpose was to have rigctld running so I could get multiple processes to > talk to my radio. > > Dave, your code snippet was most helpful - thanks. > Eric, I am starting rigctld from Popen(). The whole idea was to develop a > little app to start and stop rigctld in a window (tkinter) without having > to resorts to the command line. > > It does expose another issue however in that I seem to have a reliability > problem with the IC7300 USB interface which results in the rigctld daemon > getting into a state where it doesn't respond and using up 25% of the PCs > CPU. I don't have physical access to the system at present, so I'll wait > till I do and maybe ask another question. > > Anyway - thanks guys. > 73 Steve > > PS Sad news about W9MDB - I was very sorry to hear that. > > ----- End forwarded message ----- -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |