Re: [Hamlib-developer] Rig Control Error
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: Nate B. <n0...@n0...> - 2025-11-10 00:49:10
|
* On 2025 09 Nov 13:33 -0600, prb...@gm... wrote: > Hi Nate, > > Thanks for coming back to me. > I'm sorry, I'm not very good with the technical side, I have spent 2 days > trying to repair and am about to give up and sell my rig. > I have attached the document I have found, it appears to relate to Version > 2.7 which has the button to update Hamlib. I suspect that 2.7 has the old URL either hard coded or in a configuration variable. The old link has gone away and isn't coming back. It was not my decision to break that. > All my set up was working a year ago, before I decided to try to update the > software to V3.0 > I have even completely reset my IC705, but it's made no difference. > I have just rolled back to 2.5.4 but its just the same, although I don't > have the hamlib update buttons, but it still comes up with > > Hamlib error: Communication timed out > serial.c(884):ser_close return(0) > iofunc.c(361):port_close return(0) > rig.c(1083):rig_open return(-5) Communication timed out > serial.c(884):ser_close return(0) > iofunc.c(361):port_close return(0) > iofunc.c(361):port_close return(0) while opening connection to rig > > Timestamp: 2025-11-09T19:27:53.170Z As I stated earlier, the output from rigctl will be considerably more helpful to us. This output is like an outline while the output I am asking for is the entire term paper! > I notice the download web page has changed from princetown to a different > one? I don't know as I don't get the software from there. I use the package provided by the Debian project. > I don't really use the rig for voice, so its useless for me now. > > And in response to your question about when I try to press the update hamlib > button, yes, it fails to update, with the error straight away? > > Should I not stay on 2.5.4? I just don't know what to do now You can ask on the WSJT-X support forum (wherever that is) for guidance on manually installing the updated .DLL but I don't think that is where the problem is, but I cannot guess from the sparse output above. Sorry. 73, Nate -- "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 |