Re: [Hamlib-developer] Rig Control Error
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
Re: [Hamlib-developer] Rig Control Error
|
From: Uwe, D. <dg...@gm...> - 2025-11-10 13:45:26
|
Hi Pete, Why do you make everything so complicated? Simply install v3.0.0 251101 <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v3.0.0/wsjtx-3.0.0-win64_improved_PLUS_251101.exe/download>of WSJT-X (Improved) and use the “Diagnostic mode” which you can activate from the Save menu. Follow the instructions (= restart your computer, reproduce the error for a few seconds and close the program again). This will automatically create two debug log files in a new "logs" folder, which will be created on the desktop of your computer. Send them to me or to all of us. The most important file is “WSJT-X_RigControl.log,” because it logs all communication between WSJT-X (Improved) and your rig, so that we can immediately see any errors in Hamlib or elsewhere. Note that the “Diagnostic mode” is not available with earlier versions of WSJT-X. By the way: The “Update Hamlib” function is also working again in the current version 3.0.0 251101 <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v3.0.0/wsjtx-3.0.0-win64_improved_PLUS_251101.exe/download>. In addition, all of our 3.0.0 versions contain the necessary SSL/TLS files, so you no longer need to install OpenSSL yourself on Windows, as was the case with all previous versions of WSJT-X. This is now only necessary if you already have incompatible OpenSSL versions installed on your PC. You're mixing up several things here that have nothing to do with each other. I am happy to provide you with the following information about the general status of the WSJT-X project: Keep in mind that Joe is now over 84 years old. A few years ago, Joe was no longer able to keep the old Princeton URL for the WSJT-X download page. That's why we moved to SourceForge again. (I created the new homepage for him). In addition, for years now, both WSJT-X and the more up-to-date “WSJT-X Improved” version of the source code and all installers have no longer been created by him, but by other people in the core WSJT Develop group. Most of the maintenance work of WSJT-X is nowadays done by me. I also create all Linux and Windows installation packages. And because we younger members of the core WSJT Development group have been responsible for most of the innovations for years now, I am releasing with “WSJT-X Improved” a state-of-the-art edition of “WSJT-X,” where all new features are tested and optimized, and bugs are fixed promptly. IMPORTANT FOR YOU: You must always distinguish between the program itself (i.e., WSJT-X or WSJT-X Improved) and Hamlib. If you have rig control errors, there can be various reasons for this. Often it is because the user has accidentally set some settings incorrectly (COM port, baud rate, etc.) or there is a hardware problem (USB cable, etc.). If you can rule all of that out, then it could be caused by the Hamlib driver. For Windows users, the entire Hamlib driver database is contained in a single DLL file: “libhamlib-4.dll”, which is located in the “bin” folder of your installation (usually c:\WSJT\wsjtx\bin\libhamlib-4.dll). This file is replaced when you use the “Update Hamlib” function. In theory, however, this can also be done manually by the user at any time. As mentioned, you only need to reset the “libhamlib-4.dll” file that came with WSJT-X v2.5.4, and you will then have the same Hamlib version (i.e., also with v3.0.0 251101"). By the way, you can also find this file here <https://sourceforge.net/projects/wsjt-x-improved/files/Additional%20Files/Hamlib/libhamlib-4_WSJTX_v2.5.4_64-bit.dll/download>. If your rig control error persists, then it is obviously due to something else. But again: you just need to use the built-in “Diagnostic mode” in WSJT-X (Improved) and send us the two files in question, then we can say more about it. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 10.11.2025 um 13:05 schrieb Peter Bearne: > Is there anyway you can talk me through how to get the data you need? > Ive also rolled back to 2.5.4 > Is it advisable to put 2.7 back on first? > Is diagnostic mode built into the program, or do you mean Windows > diagnostic? > Regards > > Pete > > On Mon, 10 Nov 2025, 10:51 Peter Bearne, <prb...@gm...> wrote: > > Hi Nate, > > Im not sure how to get the Rigctl data you need? > > Thanks for trying to help me out. > > Regards > > Peter > > On Mon, 10 Nov 2025, 00:35 Nate Bargmann, <n0...@n0...> wrote: > > * 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 > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
