Hi Herb, it was not supposed to be possible to have the "Outgoing interfaces" field in "Settings->Reporting" as blank, it was meant to have the local loopback network interface as the

Found the answer to my problem over on the HamApps Group. Seems 2.3.0 has a couple new additional fields since 2.2.2. In Settings>Reporting under the UDP Server setup, the new field "Outgoing

Hi Mark, that is as expected, although the WSJT-X restart is not relevant. The Hamlib library now does band changes on modern Yaesu rigs in the same way you would from the rig front panel. Until this

I have had "SAVE" set to NONE set for a long time. Was looking over the PC (Win10), and saw that AGAIN my C: drive was nearly 2/3 full ! (this is my system drive and it normally only has about 31 GB

Found my delay issues. I found I was only decoding 1 or 2 datagrams each second. I was letting the FLTK event scheduler get a look-in in between each datagram. So of course with the large number

Thanks Gary, I'm getting used to not having the old Tab2. Jim, AF6O

Bill, Thank you for responding. I was actually able to resolve it : - Select a band (starting at 160 meters) - go to VFO A and set IPO / Mode (USB), Split, Width, etc. - go to VFO B and set IPO / Mode

RC3 has expired and you should be downloading 2.3.0 from the WSJT-X website. All anti-virus software will block new and unknown software. If you trust the software, you can tell defender to install it

Hi Steve, Tab 2 has been removed as it was not well maintained and was the source of many defects and support requests. The Tx5 message has the equivalent

Why is that? How does one now send "free" txt?

Why did you just install RC3? The General Availability version has been released, and any previous RC version will no longer run. Neil, KN3ILZ

I just installed RC3 and of course I got the message that it is not often downloaded and so was blocked. Defender blocks it. I said to let it go anyhow and also AND THIS IS THE POINT If every

The bottom part didn’t need fixing. The old Tab2 has been removed. Gary - AG0N

Great! That fixed the top part. Thank you Reino.

OK—- thanks. Noob growing pains. Hopefully the frequency hopping is fixed in the new version, I’m having fun exploring this new mode and a Pixel loop that’s been hanging out looking for a job in

Answers to your questions below... 73 - John - N7GHZ (Suggestion: I think it would help if the team set up the log to highlight in BOLD & RED [thick outlines around the data boxes] those info boxes

Ahh, Thanks Bill. Your comments forced me to take a closer look at the docs and I discovered that I was reading the v2.0.0 docs! I've now read the correct docs, installed the 64 bit versions and it is

Mark, I tried to help you before with this but you replied by saying you were working with the developer. So I can see what is happening please put the attached file into your WSJT-X configuration

Matt, you are getting that error because you have known LoTW user decode highlighting enabled and you have not installed the required OpenSSL libraries for WSJT-X to be able to

Same issue as rig control on 2.3.0 rc4 WSJT-x does not control the rig properly: - does not band switch VFOA - Changes IPO mode randomly - Does not split properly. - Changes VFOA to LSB - Rig