toggle quoted messageShow quoted text
I’ll try 2.5.0 rc3 after I do the capture with 2.4.0. Getting back to 2.4.0 if no difference or some other anomaly in rc3 I fear will be a “chore” but will give it a try.
73 de Brad, N8GLS
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Michael Black via groups.io
Sent: Tuesday, July 6, 2021 1:04 PM
Subject: Re: [WSJTX] IC-9700/7300 VFO A/B switching #Hamlib
Make that 2.5.0-rc3 since it's the latest.
There is still a problem with rigctld and the Icom rigs.
On Tuesday, July 6, 2021, 12:01:58 PM CDT, Black Michael <mdblack98@...> wrote:
Please try 2.5.0-rc2 -- it should be fixed.
On Tuesday, July 6, 2021, 11:13:51 AM CDT, Brad, N8GLS <n8gls@...> wrote:
Been using v2.4.0 for a while and have noticed the following occurring;
IC-9700: When WSJT-X launches it consistently will switch the 9700’s VFO from A to B. I have to manually switch it back to VFO A. Once back on A, it does stay on A after band/mode changes. Don’t know if anyone else is seeing this but it occurs at every launch.
IC-7300: When WSJT-X launches it will randomly switch the 7300’s VFO from A to B then back again to A. This occurs quickly and usually only occurs every 5 or 6 launches of WSJT-X. Not so much a problem on the 7300 as on the 9700 but noteworthy none-the-less.
I run two rig specific instances of WSJT-X. My hardware/software setup hasn’t changed in a very long time and no recent windows updates or changes have occured. I can only think this is a Hamlib issue but was wondering if others are seeing the same thing. Is there a location/file that logs what’s being sent from WSJT-X to the rig when launched I can look at ?? I may have another way to extract some of what is being sent but was hoping WSJT-X was logging to some system file when launched.
Thanks for any help,
73 de Brad N8GLS