Have found that if my Windows 10 box (Win10 Pro 64 bit version 1909 OS build 18363.959 on a Dell Precision Tower 3431 i7-9700 3 GHz with 16 GB Ram) either manually has its screen locked or if it times-out to a locked state that it kills the TX portion of DAX.
Actually all SmartSDR components appear to be fine, but WSJT-X apparently doesn’t like to be behind a locked screen.
It doesn’t happen often, more because I am have been experimenting trying to figure out where the breakdown was occurring. I have to set the WSJT-X to a silly amount of time, and bring the time-to-lock down to a shorter period.
First came to my attention when in a rush I manually locked my machine when I was called away, and my expectation was that I’d find either a watchdog timeout or perhaps a general pause in WSJT-X. My past experience is that SmartSDR & components is pretty forgiving if I would lock the screen when running phone.
WSJT-X continues to run, and continues to decode, but while it “thinks” it is transmitting no oubound data arrives to DAX.
As I’ve not found anything system based in hardware or software that would appear to be the culprit, I’m hoping perhaps a reader might offer a solution.
Actually I don’t mind if WSJT-X acts as if “Halt Tx” was pushed when the screen locks, as I’d like to not be required to terminate WSJT-X completely and restart it to be back in action when I unlock the machine.
As I have a lot of go-to & resource/authority roles at work, I’d like to be able to simply lock/unlock while maintaining functionality.