Just to add my recent experiences to this thread... In late October 2020 I commissioned a new PC for my 'radio' apps - the PC is a Dell 3070 with an i7-9500 CPU, 16G RAM and a 512GB SSD, running

Louis, WSJT-X continues to poll the rig via CAT. As I said turning off monitor disables *active* CAT control, that means it should make no changes to rig settings in that state. 73 Bill G4WJS.

Bill, 2 things here. My Yaesu FTDX5000 has a CAT lite that is enabled when its com port is being used by WSJX and anytime CAT is on the lite stays on and second I am using Virtual Serial Port

Hi Louis, what makes you think active CAT control is not relinquished when "Monitor" is not enabled? 73 Bill G4WJS.

For some reason or another that does not release the CAT, it just stops the software from receiving. The way the older software worked for me was that if the frequency you shifted to was not in the

Dave, you will end up with 2 wsjtx_log.adi and wsjtx.log files. 73's de Kari, oh2gqc

Dave I am using a instance of JtAlet with each instance of WSJT-X. JtAlert does log into common Log4OM. Amos 4X4MF

You've given a very good description of how Dxpedition mode works. Three strikes and you're out, as we say in the US. If the Fox doesn't complete with you, you get kicked into the weeds where you

Hi Bill 2.2.2

Hi Ken, Thanks for pointing that out, about the 0 to 4 change in the adi, I forgot to mention that! By the way, it happens on straightforward (no interruptions) qso's too! The manual correction is

Thanks Laurie, Neil, KN3ILZ got be running again. Now I can move on to getting JTAPPS and HRD logbook talking to each other again. Cheers…. Monty, NR0A

I have also experienced the gridsquare problem. Here is a pointer to the info that I received about it: https://wsjtx.groups.io/g/main/topic/79467242#20294 Basically, it says that if a QSO is not a

I have had this done to me too, and believe it to be normal operation Dave Garber VE3WEJ / VE3IE

That (plug in USB dongle or the onboard sound card) does not even show up! The ONLY inputs and outputs listed is my Microsoft USB boom headphone/mic. No other options appear now. And

Hi Louis, if you want WSJT-X to relinquish active CAT control click the "Monitor" button, to re-enable click it again. 73 Bill G4WJS.

Hey Bill, well sometimes when I am sitting here monitoring 630 meters or other frequencies I occasionally want to monitor another frequency. In the older versions such as 2.2 or 1.8, this was allowed

Pat, I am having a very similar issue with situations like this. Go to your .log file and search for your target station, as you reported... - K4TY Once you find it; check that ALL of the needed QSO

Hi Pat, which WSJT-X version are you using? 73 Bill G4WJS.

Looks like you have been playing with your WSJT-X UDP settings. Port 2333 is the default for the secondary UDP Server (depreciated). JTAlert uses the primary settings, and according to

Hi Group I had an intriguing experience yesterday calling a Fox on 30m When my call was selected my Tx was correctly moved to the Fox frequency but he was not seeing my report so he kept sending his