Yes, I have experienced receiving my own cq calls decoded as though they were another station, complete with waterfall trace. Every instance, 100% associated with watchdog timeout, which occurs part way through a TX period.
I appreciate a watchdog timeout needs to be far removed from normal communication activity of WSJT but surely, with such a time based system, there should be a way to synchronise start of watchdog to start of the communication TX sequence, so that a watchdog shutdown occurs at the end of a RX period, not part way through a TX period. Thanks for all the work guys, looking forward to upgrading to the new release. Paul Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Christoph Berg<mailto:m...@debian.org> Sent: 26 May 2020 17:07 To: WSJT software development<mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Seeing calls from myself Re: Chris Sullivan > I've seen this a couple of times before on RC1, Windows 10-64. > > I responded to a CQ from VE3VN (Hold TX set, also auto seq & call 1st). Just > after my transmission began I halted tx because I noticed he had called CQ > WC, which I guess isn't me. Then I saw, in red in the band activity window, > VE3VN VE3NRT FN03. I think WSJT-X must have received my signal through from > the monitor (K3 here) while I was transmitting. I've seen it a few times during the final cycle when the tx timeout timer was hitting. It's not reproducible, though. Is there a way to run wsjtx in full-duplex mode? That would be awesome for QO-100 satellite operation where operators are actually supposed to be listening to their own signals. Christoph _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
