Locked #Cat_RigControl #Cat_RigControl
|
Jacques Pecourt
On numerous occasions I found that I lost the communication between the radio and my desktop for some unknown reasons, probably another MS update (too many of them). What happened ? Starting WSJT-X (after the radio was turned ON), the screen tab where the frequency appears is RED instead of black. The CAT test button also remains red when checked. Here is the quick way I correct the issue. Step 1: Right click on the taskbar speaker icon which is not responsive. Step 2: From the RUN command, open the task manager and scroll down to the long list of "Processes" until you find "Windows Explorer" (way toward the bottom). Once located, highlight it, then click on "Restart". Step 3: Reboot the computer, then verify by clicking the speaker icon that you can now toggle between several speakers options (Realtek, USB Codec and others if any). Step 4: Be sure to select the USB Codec option. Turn on the radio and re-open WSJT-X. The frequency tab is now back to the black colour with yellow frequency numbers. Issue fixed every time. Using WSJT-X ver. 2.1.2 0068f4 - TX 590gsg - Win 10 pro ver 2004 (os build 19041 804). Jacques W2/F2YS |
|
|
|
Kenneth Williams
Hello Jacques
Maybe you should update your WSJT-X to 2.4 rc1. While you may not like this response, I have had a recent experience where this was indeed the proper solution. I am mentioning this because I have a TS-570S, and while it is not a 590 as you have, these radios may share some of the problem causing behavior. OK, here is some boring detail: I started using FT8 with version 2.2. WSJT-X would frequently report loss of communication with the radio although I did not need to reboot my computer, I did suffer this kind of problem. It was suggested that I update to V2.3. This did not completely resolve the problem. v2.4 solved the problem. The problem: In my case, my radio would occasionally respond to an 'IF' (information query) command with an answer that was one or two bytes shorts. Hamlib, the library that is used to interface with the various radios, would reject the responses that were one byte too short (in v2.3) but responses that were two bytes too short would cause hamlib to report loss of communication. I know this because when validating the problem, mostly for my own curiosity, I instrumented the serial interface to my rig and I could see the short responses come out of the radio. With WSJT-X v2.2, I saw a loss of communication message frequently (once every few hours). With v2.3, the messages were less frequent (once or twice a day). Since running v2.4 for almost a week, I have not seen that problem at all (except when I tripped the circuit breaker to my radio, but I do not think that this event counts) Good luck Ken KC6PUQ |
|
|
|
Jacques Pecourt
Hello Ken, Thank you for sharing this suggestion and describing how you cured your problems. Yes, I should probably upgrade, not in my habit to stay behind. However, I am hesitant since the issues I described never occur while using the program. They only pop up on a day after a shut-off and a start of a new session. I also noticed they coincide after MS installs the so called "Improvements".. I am not addressing the "Security updates". This older WJT-X version 2.1.2 works flawlessly and I hate to start a new venture that obviously has a lot more than what I need. I often think of the saying "if it ain't broken, don't fix it". If things get worse I will certainly change my mind.. .73's Jacques F2YS On Tue, 16 Feb 2021 at 15:38, Kenneth Williams <ken.williams@...> wrote: Hello Jacques |
|
|