This sounds like it is related to the "WSJT-X 2.5.0-rc3 RST_RCVD logging issue" that I reported on this reflector on Fri 7/16/2021 10:45 PM. In the brief JA-to-NA 6m FT8 openings, it is typical for the JA station to start with the Tx2 message.
Ed N4II. -----Original Message----- From: Martin Davies G0HDB via wsjt-devel <[email protected]> Sent: Wednesday, August 4, 2021 9:32 AM To: WSJT software development <[email protected]> Cc: Martin Davies G0HDB <[email protected]> Subject: [wsjt-devel] 'Rpt Rcvd' not being correctly populated I'm running WSJT-X on a PC (i7-9700 CPU @ 3GHz, 16G RAM, 512G SSD, running fully up-to-date 64bit Win 10 Pro). The issue I'll describe below is one that I believe has existed for a while - it's certainly present in v2.3.1 and v2.5.0-rc3. Here's the scenario, which is quite subtle and not easy to explain in straightforward terms...! As far as I've been able to ascertain thus far, the issue exists for both FT4 and FT8 modes; I haven't (yet) been able to confirm if it also exists when using other modes such as MSK144. I'm having a QSO with a station, let's say it's K1JT, and we have exchanged reports and I've received K1JT's RR73 and have sent a 73 in reply; at this point the QSO is complete and the prompt to log the QSO has come up and I've OK'ed the logging of the QSO. Let's say the 'Rpt Rcvd' figure that was received from K1JT and displayed in the appropriate box in the logging prompt window was -10. At some point during the QSO with K1JT I was called by another station, let's say it's N8DX, who sent me his Tx2 message. After I've completed and logged my QSO with K1JT I double-click on the N8DX callsign in the decoded Tx2 message, to start a QSO with him/her. I conduct the QSO with N8DX; we exchange reports and our RR73/73 and eventually the logging prompt pops up again, but at that point I notice that the figure displayed in the 'Rpt Rcvd' box isn't the one that was in N8DX's Tx2 message - the 'Rpt Rcvd' figure is either the same -10 figure that was correct for my previous QSO with K1JT, or on some occasions the 'Rpt Rcvd' box is completely empty. In both of these cases I have to enter the correct 'Rpt Rcvd' figure into the box before OK'ing the logging of the QSO. It would appear that in some circumstances, for example but perhaps not limited to starting a QSO by double-clicking on a received Tx2 message, the report-received figure isn't being picked up correctly from the received Tx2 message and hence isn't being displayed correctly in the 'Rpt Rcvd' box in the logging window, but instead the report-received figure from a previous QSO is being retained or the 'Rpt Rcvd' box is being left blank. On quite a few occasions I've had to amend an entry in my logging app (Logger32) because the report-received figure transferred to the app by WSJT-X has been incorrect. Has anyone else observed these anomalous figures being displayed in the 'Rpt Rcvd' box and hence logged? -- 73, Martin G0HDB -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
