WSJT-X multicasts it's status packets from multiple instances as with Flex Radio systems. JTAlert can then see those status packets too.

#Beta

JTAlert shouldn't be using that much CPU power. Most should be in PowerSDR and WSJT-X decoding. JTAlert will be looking up callsigns during decoding so with 5 decodes going on things could get pretty

What rig have you chosen in WSJT-X? There are 3 options for you. Can you test each one? The FlexRadio PowerSDR is relatively new. #1 TS-2000 #2 FlexRadio 6xxx #3 FlexRadio PowerSDR Mike W9MDB

Maybe this? https://www.herdprotect.com/netfilter64.sys-9ca71c727934861e9351af97cc28cea38811b07c.aspx Mike W9MDB

I think you'll find the FT-897 has been fixed in the next version. Mike W9MDB

Try real-time -- if that makes no difference than it would appear that it's not related to any processing delay. This is a known, unfixable problem with JTAlert V2 that will go away with V3....yet to

You need to shut down JTAlert first. And yes..you can delete all of those if they still hang around. Mike W9MDB

Seems like that should be OK. Just for experimentations sake try raising the priority of JTAlert and see if it makes any difference. I've been using ProcessHacker which allows things like CPU affinity

Type this address in your search bar -- you should see your callsign, click on it, then click on Decodes, then right-click decodes.sqlite and select Delete. %localappdata%\HamApps\JTAlert Mike W9MDB

What kind of computer/memory/cpu/speed do you have? This seems to be more common in slower computers. I haven't seen this error at all on my new computer and saw it a few times on the older one I had.

See if you have JTAlertV2 Manger running in your task manager. You should also see it in the About box ================================ UDP Ports used -------------------------------- JTAlert_AL.exe :

Laurie hasn't announce a date yet. A bit hard to predict me thinkst. Mike W9MDB

JTAlert V2 does not do multicast. V3 will when released. Mike W9MDB

I sent this out earlier if you didn't see it. Just have to change the model # for the 746Pro. You can easily find your model # using Windows: "rigctl-wsjtx -l | find "746" Unix: "rigctl-wsjtx -l | gre

Wrong list really as this isn't JTAlert related. But...there are two solutions. One uses two copies of hamlib utilities and the other uses one copy of hamlib utilities and FLRig. You will need virtual

Because the SignaLink does not do CAT control. You must have another cable hooked up for a serial port. Assuming you do have CAT control then you are likely experiencing RF causing the USB serial port

You have to open Windows Defender quarantine and "Allow" the JTAlert download. Then you can download it again and install it. I assume you added a folder exception for the directory Programs (x86)\Ham

See if this helps. https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/ Mike W9MDB

It's in WSJT-X and it adds the timestamp of the current decode if it has enough room to display it. Nothing to do with JTAlert. Why do you ask? Mike W9MDB

I assume you mean multiple monitors? What connection do you have for your monitors? SVGA, HDMI, DPI? What video card? Are your video card drivers up-to-date? And I guess you have the "extended" deskto