Info from WA6PHR ALL TXT Log 164045 2 0.1 1304 ~ CQ KF5WCP EM25 164045 -8 0.1 2867 ~ EA3KU N5JS EM12 181116_164100 Transmitting 14.074 MHz FT8: KF5WCP WA6PHR CM94 164115 -5 0.2 1304 ~ CQ KF5WCP EM25 2018-11-16 16:41 21.074 MHz FT8 164130 -9 0.1 1305 ~ KF5WCP K4EGA EM83 164200 0 0.1 2047 ~ CQ AJ6T EM64 164230 -4 0.1 2047 ~ CQ AJ6T EM64 164300 -5 0.1 2047 ~ CQ AJ6T EM64 181116_164315 Transmitting 21.074 MHz FT8: AJ6T WA6PHR CM94 181116_164345 Transmitting 21.074 MHz FT8: AJ6T WA6PHR CM94 164400 -12 0.1 2047 ~ WA6PHR AJ6T -10 181116_164415 Transmitting 21.074 MHz FT8: AJ6T WA6PHR R-12 164430 -4 0.1 2046 ~ WA6PHR AJ6T RR73 181116_164445 Transmitting 21.074 MHz FT8: AJ6T WA6PHR 73 164930 -10 0.1 2136 ~ <...> AJ6T EM64 165000 -12 0.1 2137 ~ <...> AJ6T EM64 165030 -13 0.1 2137 ~ <...> AJ6T EM64 165100 1 0.1 2137 ~ <...> AJ6T EM64 165130 10 0.1 2137 ~ <...> AJ6T EM64 165200 4 0.1 2137 ~ <...> AJ6T EM64 165230 9 0.1 2137 ~ <...> AJ6T EM64 165300 1 0.1 2137 ~ <...> AJ6T EM64 165330 5 0.1 2137 ~ <...> AJ6T EM64 165400 2 0.1 2137 ~ <...> AJ6T EM64
-----Original Message----- From: Walter Miller, AJ6T Sent: Friday, November 16, 2018 10:12 AM To: [email protected] Subject: [wsjt-devel] 5 Minute No-Mouse Timer versus WD Timer 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 [email protected] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cd4a622c6d79e4282f5ee08d64bef8ecd%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636779889609577712&sdata=ds5HRzwx%2BAYdWFnNSbkrdUzDL7kxjzM3jdxC2caQzrI%3D&reserved=0 _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
