Hi Team, Change Request: Do not reset an in-progress QSO from TX3 to TX1 when your called station responds to another station on the same RX frequency with RRR or RR73. Stations often interleave multiple QSOs resulting in a situation where you are sending TX3, but the partner is sending TX4 (RRR) to their other party in progress. This results in the sequence resetting to TX1 starting the QSO all over again. Quickly switching the message back to TX3 is now mid transmission or next transmission thus wasting a decode cycle adding 30 seconds to the exchange, perhaps losing a contact in busy and fading conditions.
Example AA1BBB K7MDL EL87 K7MDL AA1BBB -09 AA1BBB K7MDL R-04 -->CC2DDD AA1BBB RR73 - partner sending RR73 to another station on same frequency -->AA1BBB K7MDL EL87 - program switched to TX1 - rush to change to TX3 (AA1BBB K7MDL R-04) mid or late period Here I react as fast as I can to click TX3 back on. Too late, have to wait a another cycle for a clean message to be sent. K7MDL AA1BBB -09 - now redundant message - he received who knows what or TX1. AA1BBB K7MDL R-04 - now redundant message K7MDL AA1BBB RR73 - now can complete AA1BBB K7MDL 73 This scenario and scenarios where the other station did not get a 73 and keeps requesting one after RR73 or was sent ending the sequence on my side results in me needing to turn off Auto Seq, and too often I forget to turn it back on, realizing it after I notice a calling station getting the only my TX1 for several periods. My bad, but happens to often. Thanks! Mike, K7MDL
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
