Re: jtalert v 2.50.6 broke


HamApps Support (VK3AMA)
 

On 15/09/2021 8:50 am, Mike Wilson wrote:

Installed 2.50.6 and now no display of calls, decode in wsjt-x ok. Went back to 2.50.5 and now it also will not displace the decodes from wsjt-x

73 de KE5WCT

Mike Wilson


There were no UDP changes in the code with 2.50.6. There haven't been any for several versions now, so it is unlikely that something is fundamental broken in JTAlert. What other changes have you made to your PC other than the 2.50.6 update?

As a first step, perform a Windows restart. Pending Windows updates or long-running installations can often produce unexpected application behavior, especially with Win10.

Do you have any other applications trying to work with WSJT-X? If so, they may be taking exclusive control of the WSJT-X UDP port locking JTAlert out, especially if they are not set for multicast UDP.

Have a look in the JTAlert help, "Help -> WSJTX UDP Setup" menu, and setup WSJT-X and JTAlert to use multicast UDP. If you are already running multicast UDP, make sure you have the "Multicast on Loopback" menu enabled in JTAlert, see the before mentioned help article.

de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.