Calling CQ now!

Thanks for your comment. I doubt that many external auto tuners these days would fail in the early years by being used intermittently for a month or so 24/7 every once in a while. There are several

The thing is that there have been sequencing errors creeping in. Here's another where I should have been going to CQ but a 73 was sent.

Ignore, just worked it out, cluster. 73.

Hi Kevin. I highlighted the wrong error... if you see the line below the RR73, my system sent a CQ.. I had to hit the 73 manually. I posted it after having saved the screen and looked at it crossed

Hi Group. There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's

I suspect you've gone from the 32 bit version to the 64 bit version (or vice versa). The answer is you need to install the proper Open SSL library for the program type you're using. The

Hi Bill, I had a similar problem, I did report the text below but received no reply but I think it is related.:- I found that in FST4W mode, if I select Tx Enable and Tx Next, although the PTT is

Hi Tony, The only problem with your theory is that it (wsjtx) calls on you respond & log as it starts sending out the RR73 (TX4) message. What you are suggesting can only be done manually, and this

Error Loading LoTW User Data Network Error - SSL/TLS support not installed, cannot fetch: ‘https://lotw.arrl.org/lotw-user-activity.csv’ Not an issue when loading 2.2.2. KC4AIF Cliff

I think Reino explanation is correct but not worded so that you understood? The program only sent CQ because you had logged the QSO and cleared the fields. If you had waited and not logged the QSO

Silicon Labs are working on their own drivers for Big Sur.

Ror NA, 160 just starts to open at 2200z. Could you please run later? I thank you in advance. Bruce, W8HW in Florida, USA

Hi Folks! Join me in FST4 160m. This evening 19:00-22:00 UTC I will call CQ and listen: 1. Using WSJT-X v2.3.0 rc2 2. Mode=FST4 Single Decode 3. Frequency=1839.00 KHz 4. Tx=Rx=1500 Hz 5. F Tol=100

Mattia, This is a common error message about the ADIF log file. Locate the ADIF log file and do this, Find the first line where it says: WSJT-X ADIF Export<eh> change it to: WSJT-X ADIF

Right in the example below, he sent RRR and when I sent 73, the logging box popped up and I clicked ok and rearmed enable Tx. My point is that previously the program would resend 73 not CQ.

Hi Mattia, thanks for reporting the issue. It is a known issue with WSJT-X v2.2.2 which writes an invalid ADIF header when it first creates its own ADIF log file. You can fix the header by editing

oops : wsjtx-log.adi should have been wsjtx_log.adi Sam W2JDB

Hi, Check the WSJTX-Log.adi file. the first line should look like this : WSJT-X ADIF Export <eoh> There was a bug that left out the <eoh> in the first line. That should fix it. 73, Sam W2JDB

Sequencing errors are easily induced in v2.2.2 od9b96 as follows: While in a QSO with contact one, double-click in the left window on another contact then immediately double-click on the last received