wsjt-devel@lists.sourceforge.net *Multiple 2.6.0-rc4 Hound bugs* In the past few days, on two different occasions, while working ZL7/K5WE, I experienced a number of anomalies in the Hound mode. I was using WSJT-X version 2.6.0-rc4 in the FT8 mode with the "H" Hound button active (Red background). While on 18.091 MHz, after transmitting a number of Tx1 messages of "ZL7/K5WE K1HTV FM18" the Fox answered me, sending calls and reports at 21:22:15. That's when I noticed what appeared to be the first bug.* Instead of WSJT-X moving my Tx tone frequency to the Fox's transmit frequency, it remained higher in the band at 1736 Hz. *. My first thought was that the DX station may be using a WSJT-X clone.
At 21:22:45 the 2nd bug was experienced. When I received the Fox's Tx2 message of calls and a dB report,* instead of WSJT-X auto sequencing and switching to my Tx3 message of calls and R-Report, I continued to send the Tx1 message of calls and grid.* By the time I noticed this bug, 6 seconds had passed and at 21:22:51 I manually switched to my Tx3 message of calls and R-Report. The ZL7 didn't copy my truncated, short message, so my Tx3 message was transmitted again at 21:23:15. Here is the captured data from the "Rx Frequency" column. 212215 Tx 1736 ~ <ZL7/K5WE> K1HTV FM18 212230 -2 0.3 373 ~ K1HTV <ZL7/K5WE> -14 212245 Tx 1740 ~ <ZL7/K5WE> K1HTV FM18 212251 Tx 1740 ~ <ZL7/K5WE> K1HTV R-15 212300 -1 0.3 373 ~ <PY4AZ> ZL7/K5WE RR73 Chatham Is. 212300 2 0.3 313 ~ K1HTV <ZL7/K5WE> -14 212315 Tx 1740 ~ <ZL7/K5WE> K1HTV R-15 212330 3 0.3 374 ~ CX7BBR <ZL7/K5WE> -19 212330 7 0.3 314 ~ <K1HTV> ZL7/K5WE RR73 Chatham Is. 212400 -3 0.3 373 ~ <PY4AZ> ZL7/K5WE RR73 Chatham Is. When I received the RR73 message at 21:23:30, the third bug occurred. *Instead of the red "Enable Tx" going gray, my transmissions continued and my Tx3 message was resent to the Fox.* I had to manually click the "Halt Tx" button. Finally, a 4th bug occurred. *After receiving the RR73 message from the Fox, the WSJT-X "Log QSO" screen did not pop up.* I had to manually click the "Log QSO" button and hit Enter to log the QSO. I verified that the settings "Prompt me to log QSO" checkbox was checked. This same problem had occurred the day before when I worked ZL7/K5WE on FT8 20 Meters. I wonder if anyone else has experienced these anomalies with 2.6.0-rc4? 73, Rich - K1HTV
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
