Silicon Labs has updated drivers for Big Sur 11.x. https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers -- Thanks & 73, Jeff K3JRZ https://www.qrz.com/db/K3JRZ 100WAAW #404

Icom radios use Silicon Labs VCP Driver packages. and now that package (after a recent uprgade of my mac to macOS Catalina Version 10.15.7) shows this message

Crash also happens on Linux Ubuntu 18.04.5 LTS Running: /home/karza/ham/wsjtx/wsjtx240-rc1/bin/jt9 -s "WSJT-X - eirikia" -w 1 -m 3 -e /home/karza/ham/wsjtx/wsjtx240-rc1/bin -a

Thanks Bill, It installs on the Pi os 64 fine. I am wondering if they are working on the 64 bit version at all. It still runs very slowly compared to the 32 bit version.

JT4 decodes crash v2.4.0-rc1(-win64). Happens repeatedly, often on first decode. Does not happen Q65/FT4/FT8/JT65/JT9 modes. ---- error message ---- Subprocess failed with exit code 2: Running:

Working as designed! The internal and external plug-in sound cards are not supposed to appear in WSJTX if they are set to either DEFAULT or COMM DEFAULT devices. Adjust your Windows 10 sound

A few details... Running 2.2.2 on RPi. Radio is a Yaesu 857D. RigBlaster Advantage. (I believe I have also seen this when running 2.2.2 on Windows - same radio). -- Jim KM6GUO

I see my own CQ on the activity window. Is that a good thing? Something I am doing wrong? It happens after the watchdog terminates transmit - and the timestamp corresponds to when it was transmitted.

Dave, that decoding takes many millions of CPU cycles, it cannot be instant. There will surely be some optimizations that speed things up but this is just the first release candidate and there are

I've used the hastag "BugReport" as there didn't seem to be anything else that would cover this. Using Q65 today someone, on one of the KST Chat rooms, mentioned that it was taking a long time from

Hi Alex, see this post from the wsjt-devel Source Forge list: https://sourceforge.net/p/wsjt/mailman/message/37212133/ 73 Bill G4WJS.

Hi Dave, that is not necessary when using multicast IP, but some servers, notably JTAlert, do not handle multicast quite right and require each WSJT-X instance to send to a different service port

I get the exact same error running 2.4.0-rc1-win64 at the end of first JT4 decode period. Does not happen in Q65/FT8/FT4 modes, will try some others

Thanks Bill (& Dave) I realised this was expected behaviour, as you say 3 periods then moved into what I called "no mans land" . Good to know that if propagation or QRM allowed it would probably have

What was the idea behind the box?

I just installed 2.4.0 RC1 next to 2.3.0 on MacOS Big Sur The previous version runs OK, but the RC crashes after about 1 minute of monitoring FT8. During the first period all stations are decoded

Hi Karza, Thanks.. 73 Dave G8LIY

Hi Amos.. Thanks... I plan to use.? GRIDTRACKER if I can 73 Dave G8LIY

Hi Bill, Many Thanks... Another Q.? I assume I will therefore need a UDP Port Nos# per instance. 73 Dave G8LIY

HIHIHI I find the freq box handy! :-) I have a few FST4W skeds with DX stations and we use the freq to help ID traces of the participating stations if operating "random". I don't know how to turn it