locked No Decode & Generate Std Msgs doesn't do anything #decode #windows11


sw@...
 

On latest Windows 11, suddenly Decode fails to work, there are no standard Messages, and Generate Std Msgs button does nothing. I've checked all the settings and they are correct. Any ideas?


Reino Talarmo
 

Hi sw,

You need to type a call sign into the box below DX Call field before the Generate Std Msgs works. If you had a call sign there, then I give up.
73, Reino OH3mA

On latest Windows 11, suddenly Decode fails to work, there are no standard Messages, and Generate Std Msgs button does nothing. I've checked all the settings and they are correct. Any ideas?


sw@...
 

Thanks for the help on Generate Std Message, that works.

It seems that Decode is the only problem. The WSJT-X Wide Graph looks perfect and I can see the stations. I am using a FlexRadio 6600 so I can also hear the audio stream from my computer and it also sounds correct. I can see the Decode button flash 3 times while I’m in Deep decode mode, but nothing gets decoded. Do you have any idea how I could debug this further? The level meter in WSJT-X looks right, too, responding to signals.


Martin G0HDB
 

On Mon, Mar 14, 2022 at 08:53 AM, <sw@...> wrote:

On latest Windows 11, suddenly Decode fails to work, there are no standard
Messages, and Generate Std Msgs button does nothing. I've checked all the
settings and they are correct. Any ideas?
Are you seeing any signals on the waterfall? If you are but you're not getting any decodes then check that your PC's clock is sufficiently close to 'real time'. The best way to ensure the clock is accurate is to install the Meinberg NTP client - don't be tempted by less-capable 'time correction' apps, such as Dimension 4, that use SNTP.

If you're not seeing any signals on the waterfall then I'd suggest checking Win 11's privacy settings to ensure that the WSJT-X app is permitted to access the 'microphone'.

--
Martin G0HDB


sw@...
 

That was it. My time server was changed to Local CMOS so time was way off. This must have happened during a Windows update somehow since I definitely didn't change the settings.

Thanks!