I and others reported this same situation after the FT Roundup, although
nothing ever came of it. It seems to happen randomly, and it's always
the received report that doesn't get captured. Fixing it ruins any run
you might have going.
73
Dave AB7E
On 1/4/2020 4:47 PM, John Pelham wrote:
Hello all,
Today in the RTTY Roundup I’ve been operating only FT8 and only S&P. I
followed Joe’s article in January QST, in that I set the Special
Operating Activity to RTTY Roundup, entered my state MA, made sure
Auto Seq is checked, renamed wsjt_log.adi to wsjt_log.bak, and erased
Cabrillo.log. The WSJT Contest Log window appeared at some point.
I did not set up any N1MM+ integration, although my DXLab DXKeeper log
is up and running. When each contest QSO is completed, the “WSJT-X
v2.1.2 by K1JT – Log QSO” dialog box appears, I click the OK button
and the QSO is logged to the WSJT Contest Log, and to DXKeeper.
The issue is that about 10% of the time when I click the OK button in
the Log QSO dialog box, I get an error message that the exchange is
not valid. After a couple of these errors, I took the time to study
the dialog box, and found that in the bottom row that contains the
‘Exch sent’ and ‘Rcvd’ fields, the Rcvd field is empty. For DX, the
info needed to fill this in is right above, in the Rpt Rcvd field, and
for non-DX I have to look at the WSJT main window to determine the
state or province. This takes a bit of time and keeps me busy while
making QSOs, but it would be nice if it was filled in automatically
like it is on the other 90% of the QSOs. I am unable to discern
anything special about the failed QSOs vs. ones that worked automatically.
73, John W1JA
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
