Hi Joe, Yes, I just cc'd you on the mail to the dev team. Tried to document the exact conditions when it happens. If they need more info, then only additional data available after it happened is the data from the All.txt file but that does not indicate TX enabled status.
Forgot to include the fact that I have 2 pass decode and deep decode set. Hope that helps. Anyway, thank you for the reply. Hope you had a great weekend. 73, Sam W2JDB -----Original Message----- From: Joe Taylor <j...@princeton.edu> To: Sam W2JDB <w2...@aol.com> Sent: Mon, Mar 6, 2023 11:15 am Subject: Re: Tx being disbabled bug Hi Sam, It's *much* better to send such a report to wsjt-devel, where it will receive due attention. As always, an explicit recipe for reproducing the undesired behavior will guarantee suitable action. -- Joe, K1JT On 3/6/2023 11:08 AM, Sam W2JDB wrote: > Hi, > > > > Finished a contact with K4EAY, and re-enabled TX ready to call another > CQ. KC0JRW called me at offset 1130, and wsjt-x responded with a report. > It then decoded VE1RMR calling 9A1AX at offset 1131. At that point it > seems that TX was disabled. Originally I did not notice that, but when I > did, I manually re-enabled TX. This happened once before and I thought I > had somehow disabled TX by accident. This is time I documented it. It > happened a few more times when I was calling CQ, responding with a > report to a decoded station while other stations were calling me on a > very busy band. > > Running Win/10 Pro (Ver 21H2), PC is AMD 3900X, 3.79GHz 32GB, 1TB SSD. > > 73, > > Sam W2JDB >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
