Re: [wsjt-devel] "Invalid QSO Data" when trying to log during mock contest - RC7

[Bill S. <g4...@cl...>]

OM,

my guess is that the message from another QSO on your Rx offset has 
reset the QSO when it should not have do so. The QSO sequencer has 
picked up again when the RR73 message is received but by then the prior 
exchange details have been discarded, hence the missing information. You 
could have worked around it by completing the missing fields "Rpt Sent", 
"Rpt Rcvd", "Exch sent", and "Exch rcvd" with "559", "549", "559 NJ", 
and "549 AB" respectively.

73
Bill
G4WJS.

On 06/06/2019 14:50, K2DBK-WSJT wrote:
>
> I didn’t see any comments from anyone on the development team about 
> this. I checked the Known Issues and it’s not marked there either. I 
> read Joe’s note that issues identified are being corrected for the GA 
> release and I wanted to know if this issue had been addressed?
>
> *From:* K2DBK-WSJT <k2d...@k2...>
> *Sent:* Tuesday, June 4, 2019 7:52 PM
> *To:* 'WSJT software development' <wsj...@li...>
> *Subject:* [wsjt-devel] "Invalid QSO Data" when trying to log during 
> mock contest - RC7
>
> I was making a few contacts in the mock contest this afternoon and ran 
> in a problem where to an issue where the QSO completed but when I 
> tried to log it a dialog popped up that said “Invalid QSO Data  Check 
> exchange sent and received”. I’ve attached a screenshot of what was 
> going on at the time. The Rpt Sent & Rcvd fields were initially 
> populated corrected but  are blank now as I think this was my 2^nd or 
> 3^rd attempt to fill in and log. To finally get it to log I hit Cancel 
> on the logging window then clicked on Log QSO, filled in the same 
> information as before, and it went through.
>
> This happened a second time in the exact same way, and one thing that 
> I noticed that was the same (although unfortunately I don’t have a 
> screenshot) is that there was another signal decoded in the Rx 
> Frequency window between my report to the other station and his RR73 
> to me. I don’t know if that’s related but I wanted to mention it.
>
> I do have Save All decodes checked so I can provide those if it will 
> help. I’ll continue to see if I can see this again. This is on Window 
> 10 Pro 64-bit running the 64-bit version of WSJT-X.
>