Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process
Please place this file as described below https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location Here's a youtube video showing Windows users howto -- https://www.youtube.com/watch?v=q9tAvhNmSvc For Linux put it in ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X For MacOS put it in /Users/[username]/Library/Preferences Restart WSJT-X and duplicate the problem. Shut down WSJT-X Then send me the WSJT-X_RigControl.log file Mike W9MDB On Wednesday, March 20, 2024 at 06:59:10 PM CDT, Scott Armstrong via wsjt-devel wrote: Hi All, I have encountered a problem running 2.7.0-rc4 with Hamlib version This impacts an Icom IC-756ProII and IC-746. The issue is not observed when running a IC-9700 The problem is also observed running 2.7.0-rc3 with the new Hamlib version The workaround is to roll back to the previous version of Hamlib See below for the problem details. If more information/data is required I'd be glad to provide it. Thanks, Scott AA5AM PROBLEM: CAT failure causes v2.7.0-rc4 to hang, requiring the process to be killed. WSJT: Hamlib: Windows/PC: Rigs impacted: Icom IC-756ProII Icom IC-746 PROBLEM DESCRIPTION If CAT becomes disabled by turning the radio off or other problem that causes a disconnect, the WSJT CAT connection indicator remains green. It never transitions to amber or red. The Rig Control Error pop-up message is not raised. When CAT is restored by turning on the radio or resolving other errors, there is still no connection between the SW and the radio even though the indicator is still green. WSJT-X v2.7.0-rc4 is then closed and relaunched. The pop-up indicating that another instance may be running is observed. Then it becomes necessary to go into Task Manager and kill the wsjt.exe process that is hung from the previous instance of the SW running. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process
Please place this file as described below https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location Here's a youtube video showing Windows users howto -- https://www.youtube.com/watch?v=q9tAvhNmSvc For Linux put it in ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X For MacOS put it in /Users/[username]/Library/Preferences Restart WSJT-X and duplicate the problem. Shut down WSJT-X Then send me the WSJT-X_RigControl.log file Mike W9MDB On Wednesday, March 20, 2024 at 06:59:10 PM CDT, Scott Armstrong via wsjt-devel wrote: Hi All, I have encountered a problem running 2.7.0-rc4 with Hamlib version This impacts an Icom IC-756ProII and IC-746. The issue is not observed when running a IC-9700 The problem is also observed running 2.7.0-rc3 with the new Hamlib version The workaround is to roll back to the previous version of Hamlib See below for the problem details. If more information/data is required I'd be glad to provide it. Thanks, Scott AA5AM PROBLEM: CAT failure causes v2.7.0-rc4 to hang, requiring the process to be killed. WSJT: Hamlib: Windows/PC: Rigs impacted: Icom IC-756ProII Icom IC-746 PROBLEM DESCRIPTION If CAT becomes disabled by turning the radio off or other problem that causes a disconnect, the WSJT CAT connection indicator remains green. It never transitions to amber or red. The Rig Control Error pop-up message is not raised. When CAT is restored by turning on the radio or resolving other errors, there is still no connection between the SW and the radio even though the indicator is still green. WSJT-X v2.7.0-rc4 is then closed and relaunched. The pop-up indicating that another instance may be running is observed. Then it becomes necessary to go into Task Manager and kill the wsjt.exe process that is hung from the previous instance of the SW running. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process
Usually on click ok, the Config pane pops up on radio tab so you can reconfigure , so you don't see that then, ok ? It would be interesting to confirm a program interface like FLrig, Commander or HRD works, or rigctld/Hamlib interface , rather than actual radio choice. 73 vk4tux On 21/3/24 10:25, Scott Armstrong wrote: The Rig Control Error window is never displayed. But to answer your question... going into the settings and doing a 'Test CAT' does not restore the connection. -Scott AA5AM___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process
The Rig Control Error window is never displayed. But to answer your question... going into the settings and doing a 'Test CAT' does not restore the connection. -Scott AA5AM On Wed, Mar 20, 2024 at 7:11 PM Adrian wrote: > Re below ; If you click 'ok', and then are shown the wsjtx radio settings > tab, does 'Test CAT' restore the cat connection ? > > > 73 > > > vk4tux > On 21/3/24 09:52, Scott Armstrong via wsjt-devel wrote: > > The Rig Control Error pop-up message is not raised. > [image: image.png] > > > When CAT is restored by turning on the radio or resolving other errors, > there is still no connection between the SW and the radio even though the > indicator is still green. > WSJT-X v2.7.0-rc4 is then closed and relaunched. > > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process
Re below ; If you click 'ok', and then are shown the wsjtx radio settings tab, does 'Test CAT' restore the cat connection ? 73 vk4tux On 21/3/24 09:52, Scott Armstrong via wsjt-devel wrote: The Rig Control Error pop-up message is not raised. image.png When CAT is restored by turning on the radio or resolving other errors, there is still no connection between the SW and the radio even though the indicator is still green. WSJT-X v2.7.0-rc4 is then closed and relaunched.___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process
Hi All, I have encountered a problem running 2.7.0-rc4 with Hamlib version [image: image.png] This impacts an Icom IC-756ProII and IC-746. The issue is not observed when running a IC-9700 The problem is also observed running 2.7.0-rc3 with the new Hamlib version The workaround is to roll back to the previous version of Hamlib [image: image.png] See below for the problem details. If more information/data is required I'd be glad to provide it. Thanks, Scott AA5AM *PROBLEM: * CAT failure causes v2.7.0-rc4 to hang, requiring the process to be killed. *WSJT:* [image: image.png] *Hamlib:* [image: 9d3168cc-5948-4560-ad51-4e3c9551fccb.png] *Windows/PC:* [image: image.png] *Rigs impacted:* Icom IC-756ProII Icom IC-746 *PROBLEM DESCRIPTION* If CAT becomes disabled by turning the radio off or other problem that causes a disconnect, the WSJT CAT connection indicator remains green. It never transitions to amber or red. [image: image.png] The Rig Control Error pop-up message is not raised. [image: image.png] When CAT is restored by turning on the radio or resolving other errors, there is still no connection between the SW and the radio even though the indicator is still green. WSJT-X v2.7.0-rc4 is then closed and relaunched. The pop-up indicating that another instance may be running is observed. [image: image.png] Then it becomes necessary to go into Task Manager and kill the wsjt.exe process that is hung from the previous instance of the SW running. [image: image.png] ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
