RC4 on Win10
I called VP8LP on 15 meters this morning, and (no surprise) he came back
to a couple of other callers and then resumed CQing before finally
coming back to me. I was not paying close attention to the screen, and
when I looked at the screen again there were two red lines with my
exchange with VP8LP ending with his RR73 sent to me. My station did not
send anything further to him. As always, I had "Auto Seq" and "Call
1st" and "Hold Tx Freq" checked. By that time time there were others
calling VP8LP, and he resumed CQing and made more contacts. See the
decodes and my transmissions in the "Rx Frequency" below. The strange
part was that there was no log window popup despite the fact that I have
checked "Prompt me to log QSO" in the Settings. VP8LP was still in the
"DX Call" box, and I was able to log the QSO manually by selecting the
"Log QSO" button.
I'm not sure, but I think I ran afoul of the new 5 minute "No-Mouse
Movement" feature. It appears that WSJT-X simply stopped completing the
contact and failed to pop up the log window.
144000 Tx 2339 ~ VP8LP AJ6T EM64
144015 -14 0.3 2256 ~ IW1AYD VP8LP -08
144030 Tx 2339 ~ VP8LP AJ6T EM64
144045 -13 0.3 2256 ~ IW1AYD VP8LP -08
144100 Tx 2339 ~ VP8LP AJ6T EM64
144115 -14 0.3 2256 ~ IW1AYD VP8LP RR73
144130 Tx 2339 ~ VP8LP AJ6T EM64
144145 -8 0.3 2256 ~ CQ VP8LP GD18 CQ Zone 13
144200 Tx 2339 ~ VP8LP AJ6T EM64
144215 -12 0.3 2256 ~ HA5LV VP8LP +08
144230 Tx 2339 ~ VP8LP AJ6T EM64
144245 -11 0.3 2256 ~ HA5LV VP8LP +08
144300 Tx 2339 ~ VP8LP AJ6T EM64
144315 -11 0.3 2256 ~ HA5LV VP8LP +08
144330 Tx 2339 ~ VP8LP AJ6T EM64
144345 -13 0.3 2256 ~ HA5LV VP8LP RR73
144400 Tx 2339 ~ VP8LP AJ6T EM64
144415 -12 0.3 2256 ~ CQ VP8LP GD18 CQ Zone 13
144430 Tx 2339 ~ VP8LP AJ6T EM64
144445 -11 0.3 2256 ~ CQ VP8LP GD18 CQ Zone 13
144500 Tx 2339 ~ VP8LP AJ6T EM64
144515 -14 0.3 2256 ~ AJ6T VP8LP -13
144530 Tx 2339 ~ VP8LP AJ6T R-14
144545 -13 0.3 2256 ~ AJ6T VP8LP RR73
144700 -21 0.4 2255 ~ <VP8LP> EA7/DL8FCL
144730 -19 0.4 2255 ~ <VP8LP> EA7/DL8FCL
144815 -14 0.6 2256 ~ CQ VP8LP GD18 CQ Zone 13
In any event, I decided to try to test that theory by calling CQ and
seeing when my transmissions stopped. I unexpectedly got a reply from
WA6PHR just at the expiration of 5 minutes, so that test did not run to
completion exactly as I had planned. However, the expected "Call 1st"
option did not activate, and I had to click on WA6PHR (after his second
call to me) in order to initiate the QSO. See the "Rx Frequency" window
transcript below.
163800 Tx 2056 ~ CQ AJ6T EM64
163830 Tx 2056 ~ CQ AJ6T EM64
163900 Tx 2056 ~ CQ AJ6T EM64
163930 Tx 2056 ~ CQ AJ6T EM64
164000 Tx 2056 ~ CQ AJ6T EM64
164030 Tx 2056 ~ CQ AJ6T EM64
164100 Tx 2056 ~ CQ AJ6T EM64
164130 Tx 2056 ~ CQ AJ6T EM64
164200 Tx 2056 ~ CQ AJ6T EM64
164230 Tx 2056 ~ CQ AJ6T EM64
164300 Tx 2056 ~ CQ AJ6T EM64
164315 -9 0.1 2056 ~ AJ6T WA6PHR CM94
164345 -10 0.1 2057 ~ AJ6T WA6PHR CM94
164402 Tx 2056 ~ WA6PHR AJ6T -10
164415 -10 0.1 2057 ~ AJ6T WA6PHR R-12
164430 Tx 2056 ~ WA6PHR AJ6T RR73
164445 -5 0.1 2057 ~ AJ6T WA6PHR 73
As a final test, I initiated another CQ and did not get an answer this
time. Sure enough, the CQ stopped after 5 minutes without any
indication of a timeout. The ten minute WatchDog timer continued to
count down for another 5 minutes, and when it expired there was no
indication of that fact either. In previous versions there was a red
box in the lower left indicating the WD timeout.
Is this information useful to the development team?
73, Walt, AJ6T
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
