locked Re: World-wide Digi DX Contest Problem

Jim Shorney

I also noticed the decode button staying on during the contest. Investigating, I found that one CPU core was hitting 100% for periods roughly coinciding with the decode button behavior.

I'm using WSJT-X in Kubuntu 18 Linux, compiled from source. I have WSJT-X connected via LAN to DXLabs SpotCollector on a very busy Windows box for the extra highlighting of calls. After I tried a couple of other things I found that clearing the band activity pane with right-CLICK-Erase helped. Periodically erasing the band activity or erasing when the monitor button started to act up seemed to settle things down.

I can't say if I was missing any decodes or not, I was usually getting plenty so how would I know? :)



On Mon, 31 Aug 2020 16:27:19 -0700
"Tony Collett via groups.io" <tony.nbs@...> wrote:


More basic system here v2.2.2 W10 Pro 64bit v2004 on a 3GHz Intel Core2 Duo CPU and just WSJT running alongside N1MM with a K3 over the weekend.
Out of contests I run JTALert and DXLab suite (Commander/Log and Spot) so much more going on on the PC.

I've never noticed the decode light stay on before but it was doing it over the weekend during the Digi DX Contest. Didn't appear to lose me any decodes, other than them appearing after the next period had started from time to time.

I did have WSJT crash out on me twice though which it has never done before. Both times I had just logged a QSO and clicked on a decode of a wanted station - not his CQ but one containing reports. Think one of the decodes included a hashed call but not sure of the other occasion.

Tony G4NBS

Join main@WSJTX.groups.io to automatically receive all group messages.