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-11 16:54:09
|
Well, theoretically yes. At the time, I programmed the “Diagnostic mode” in a way that it simply automates all the steps that would otherwise have to be performed manually, i.e., writing a wsjtx_log_config.ini file with the correct content, copying it to the right location, and so on. It is also programmed so that this file is automatically reset to its default content afterwards, as many OMs forgot to do this when performing the manual procedure, which then quickly led to huge amounts of data accumulating on the hard drive. What we could possibly do is query and log the available COM ports and audio sources/sinks in the second debug log file (i.e., in wsjtx_syslog.log). The question is always how user-friendly (or perhaps better, how foolproof) we want to make our programs. Joe's concept for WSJT-X (or QMAP or MAP65) has always been that it's all intended for experts. Specifically, that OMs (or YLs) should be encouraged to take the time to learn how it all works, because that's the only way operators can truly understand what they're doing. And basically, I agree with Joe. However, experience has shown that many users are not even capable of operating their computers properly. Frankly, I have never understood why even OMs who have spent a lot of money and time on highly complex equipment for EME operation sometimes have difficulty installing a new version of WSJT-X (Improved). But that's just the way it is. I think this may also be due to the fact that many OMs have now reached a certain God-blessed age. That's why I had already incorporated a whole host of features into my “improved PLUS edition” that make everything more user-friendly. I will continue along this path. But everything has its limits. A basic understanding of hardware and software is essential if someone wants to engage in digital modes. I mean, fishing is also a nice hobby, hi. However, FT8 has now become something of a mass market. This has also attracted many “plug-in radio amateurs” (= "Steckdosen-Amateure") as we say here in DL. But what often makes things very difficult for users are those annoying Windows updates. There, serious changes (drivers no longer accepted, etc.) are often made without informing the user accordingly. But let's be honest, it's not much better with Linux and macOS. Just think of the new hurdles that Tahoe has brought. And on my various Linux systems, I've often had to completely restore the system because yet another update had messed something. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 11.11.2025 um 17:10 schrieb Michael Morgan: > Hey Uwe - would it make sense for the diagnostic mode when it starts > to maybe iterate the available serial ports. So instances like this > would be easy for us to know what ports are available? > > 73, Michael, AA5SH > > On Tue, Nov 11, 2025 at 9:35 AM Dave Baxter via Hamlib-developer > <ham...@li...> wrote: > > Just a thought. > > Does COM3 actually exist, and is it actually the rig? > > (Windows can re-enumerate ports as things are connected/removed, > or when coming out of a sleep state, so sometimes what was on > "COMx" is now on "COMy" ! There are ways to nail things down to > stop that, but you then have to be very careful to reconnect > things to the same physical USB port on the PC. Put a Hub in the > mix, and it gets very complicated very fast!) > > Is the rig connected by native USB, or via a common USB-Serial / > CI-V adapter? Many of such will have their drivers blocked by > Windows, as there are hoards of fake chipsets out there used for > such things, even FTDI look-alikes! > > If a native USB connection, what does Windows Device Manager say > about it? > > Does any other software (Icom specific for the rig for example?) > work OK with the radio? If not, are the correct drivers installed? > > Also, does the rig have CI-V "Trancieve" enabled? If so, try > with that disabled. (Though I think later Hamlib instances would > disable that automagically if it was detected.) > > Just idle thoughts, based on experiences with that OS and COM > ports in the past work life, where we often had multiple USB and > serial connected instrumentation "things" at the same time. > Sometimes, Windows going to sleep, and then coming out of that, > the Universe would implode, as various pieces of software suddenly > lost sight of what they expected. > > That was true from Windows XP through Windows 10. Glad I have > nothing to do with that OS any more!. > > 73. > > Dave G8KBV. > > > On 11/11/2025 14:09, prb...@gm... wrote: >> >> Hi Uwe >> >> Thanks for your help, I apologise if I appear to be making it >> complicated. >> >> I have downloaded V3.0 as you said and this time the Hamlib >> update button worked, but still the same error with no comms to >> the rig. >> >> I have set the diagnose mode and shut the program, then restarted >> it and closed it again. >> >> I have found the attached 2 log files from the desktop, is this >> what you required ? >> >> Thanks again >> >> Regards >> >> Peter >> >> 73 >> >> M7PTS >> >> *From:*Uwe, DG2YCB <dg...@gm...> <mailto:dg...@gm...> >> *Sent:* 10 November 2025 13:49 >> *To:* Peter Bearne <prb...@gm...> >> <mailto:prb...@gm...>; Hamlib Developers >> <ham...@li...> >> <mailto:ham...@li...> >> *Subject:* Re: [Hamlib-developer] Rig Control Error >> >> Sorry, I meant, of course: Follow the instructions (= restart >> *the program*, reproduce the error for a few seconds and close >> the program again) >> >> >> 73 de DG2YCB, >> Uwe >> ________________________________________ >> German Amateur Radio Station DG2YCB >> Dr. Uwe Risse >> eMail: dg...@gm... >> Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> >> >> Am 10.11.2025 um 14:45 schrieb Uwe, DG2YCB via Hamlib-developer: >> >> Follow the instructions (= restart your computer, reproduce >> the error for a few seconds and close the program again) >> >> >> >> _______________________________________________ >> Hamlib-developer mailing list >> Ham...@li... >> https://lists.sourceforge.net/lists/listinfo/hamlib-developer > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
