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 

HI Brad,

put the attached file in your WSJT-X configuration files directory (that is the same as the log files directory "Menu->File->Open log directory" on Windows), then restart WSJT-X. The log go to your Desktop - WSJT-X_RigControl.log .

Delete the config file when you want to return to normal logging.

Please send me (g4wjs <at> classdesign <dot> com) a log from a minimal session that demonstrates the issue(s)?

73
Bill
G4WJS.

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,

I am running version 2.5.0-rc3 in combination with an Icom IC-9100 in Windows 11 beta.
The problem above is the same here as the above mentioned, also in Windows 10 since i updated to Win 11 beta only last week.
However, i can switch between VFO A and B without a problem, but the TX switches immediately from VFO A to B and manually backwards to A again and remains there until i change to another app. I am running a desktop computer with an Intel I7-2600 and 16GB mem just for HAM purposes with all drivers updated to the latest version.
It is the only app what causes this phenomenon in my situation.

Dirk, PE1KWE.

I did and the issue still exists on my IC-7800 and has since V2.5 I went back to 2.31 until loading the latest. It still happens when I move the VFO. Most recently moving it from 50313 to 50323 for a DXPedition...A & B begin swapping and the only way to stop it, is turn the radio power off or close WSJT-x and reopen. So to change frequencies such as that, I put the DX frequency in the bank and switch it manually. I use HRD and JTAlert but do not use any rig control.
Bill W2CQ

Hi Bill,
In "settings", Radio, split operating, set is "fake it". At present i changed it to "none" now. Everything stable now, but i was recommended to go either to "rig" and then the behaviour, is as you said, normal. But in the "fake it" situation the VFO shouldn't change it, it is "fake" right? But for now, it's in the "none" position.

Thanks for your swift reply.

73, Dirk PE1KWE.