On 11/12/2018 16:00, James Fowler wrote:
What I’m trying to indicate bill is that regardless if I press the ok button in
the log qso popup after RR73 is sent twice TX is automatically disabled if I
reenable it it automatically goes to CQ at which point I need to click the last
call the try and re send the RR73
The call flow has changed in v2 from v1.9.1 it used to be in 1.9.1 the qso was
not final until I received there RRR the log qso would come up as I replied 73
Now in V2 it comes up soon as I send RR73 with no confirmation from them that
they received my report with a RRR
Is there a way I can revert the call flow back to RRR then 73 ? And have wsjt-x
retain it ? I know I can change it manually for every call but it does not
retain between calls
Hi James,
firstly, sending RR73 is saying that the QSO is complete, you should not
expect any reply and certainly not an RRR reply. In conditions where
repeats are likely it is unwise to use RR73 messages, regardless of that
if you look at the actual outgoing message content on Tab 1 you should
see that after logging a QSO the Tx5 message does not get reset so if
you get a repeated R-report message from your QSO partner then you can
click the button to select Tx5 and "Enable Tx" again to repeat your
final QSO message. This should work from Tab 2 although it is not as
clear since the actual messages are not visible.
If you really don't want the messages to be reset after sending a final
QSO message then uncheck the "Settings->Reporting->Clear DX call and
grid after logging" option and you might also want to uncheck the
"Settings->General->Disable Tx after sending 73" option. Then you have
full control of when a QSO ends and must use "Enable Tx" or "Halt Tx" to
end your transmissions.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
