FWIW .. someone sending an RR73 does not expect a reply, the last 73 is a courtesy from you the answering station. If someone keeps sending RR73, they don't understand the use of that response.
Neil, KN3ILZ On 5/19/2020 10:06 AM, Black Michael wrote:
What he's describing has happened to me numerous times... You send 73 and move on to another QSO...then the last QSO sends RR73 again so you have to double-click it. Seems to me double-clicking an RR73 that has your callsign in it should automatically go to Tx 5 instead of TX3. de Mike W9MDB On Tuesday, May 19, 2020, 09:02:07 AM CDT, Joe Taylor <j...@princeton.edu> wrote: Hi Rich, On 5/18/2020 20:16, Rich Zwirko - K1HTV wrote: > *Using 2.2.0-rc1, when completing an FT8 QSO and an RR73 is received I > send a 73. However if the station doesn't receive my '73' message, he > re-sends his TX4 RR73 message. When I double click on his first RR73 > line, instead of sending me sending the correct Tx5 '73' message, > WSJT-X sends the incorrect response of a 'Tx3' message of calls and > roger report. * > * > *Is this a bug or a 'feature' to keep us on our toes?* Think of it as a 'feature'. The program's logic is that you sent 73, so the QSO is over as far as you're concerned. If you want the program to send 73 again upon receipt of another RR73 from the same QSO partner, toggle *Enable Tx* to red, again, during the Rx interval after you send 73. -- Joe, K1JT _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
-- This email has been checked for viruses by AVG. https://www.avg.com
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
