The problem I am having however bill perhaps I may be miss communicating or just misunderstanding
I know that the qso is considered final on my end once RR73 is sent and the log box appears if I select Ok to log the qso and my qso partner does not receive my RR73 he responds with my report let’s say R-21 and the message is repeated in V2 it then automatically responds Again with RR73 and then automatically disables after 2 attempts then enable tx has to be pressed and then have to goto tab 1 and click message TX4 to resend the RR73 until he receives it In version 1.9.1 Reports are exchanged and when I send my RRR if he does not receive it wsjt-x continues to send RRR until either he responds with a 73 and then the qso is complete in 1.9.1 the message continues to get sent UNTIL the watchdog is tripped this is not the case in V2 Is there a way to setup v2 to follow the same call flow as 1.9.1 and have it retain that between each call ? I’m not asking to be difficult it’s just that it’s different and I spent a considerable amount of time creating a AutoIT macro to support some other programs external to wsjt-x that depends on this call flow Sent from my iPhone > On Dec 11, 2018, at 9:14 AM, Bill Somerville <[email protected]> wrote: > >> 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 _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
