This has been reported before ... Maybe you've already fixed it;
If WSJT-X is configured to use the FlexRadio 6xxx rig interface method
then at random intervals WSJT-X will cease to function correctly.
Various different features cease to work each time and the CPU usage
will increase to about 10 times normal.
I have discovered a method of causing the same symptoms to occur on
demand which should assist in debugging this condition. If the Flex has
TX inhibit set to inhibit then toggling WSJT-X into transmit ( Tune
off>on>off ) will duplicate the symptoms resulting from of the random
event. The random event appears to likely be the result of a delayed
handshake (ID;) response from the radio.
This is from the SSDR CAT log for the TCP port leading up to the event
with TX inhibited..
19-02-06 14:28:05.123 TCP 26001 [sent]: ZZFI01;
2019-02-06 14:28:05.123 TCP 26001 [rcvd]: IF;
2019-02-06 14:28:05.125 TCP 26001 [sent]:
IF000070740000010+0000000000090000000;
2019-02-06 14:28:35.788 TCP 26001 [rcvd]: TX;
2019-02-06 14:28:35.790 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:35.791 TCP 26001 [sent]: ID909;
2019-02-06 14:28:36.646 TCP 26001 [rcvd]: RX;
2019-02-06 14:28:36.647 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:37.246 TCP 26001 [rcvd]: RX;
2019-02-06 14:28:37.246 TCP 26001 [rcvd]: ID;
2019-02-06 14:28:37.717 TCP 26001 [sent]: ID909;
2019-02-06 14:28:37.718 TCP 26001 [sent]: ID909;
At this point the only recourse is to kill WSJT-X with the task manager
and restart. I a normal situation the ID; following the first RX,
receives an ID909; response in 100msec and the second RX is not sent.
AL, K0VM
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
