locked Re: JTAlert 2.12.3 Updated and is not working properly at all..

HamApps Support (VK3AMA)

On 4/08/2018 2:15 PM, kw7m07 via Groups.Io wrote:
Hi all, here we go.. I just made the update on JTAlert from 2.11.? to the latest 2.12.3. Let me tell you, I sure did not expect this.. All fields are fully populated with call signs from all over the country. The program will not respond to WSJT - X 1.9.1 when decode is complete. JTAlert continuously populates the call signs about every 8 seconds. And none of the calls are what is showing on WSJT screen after a decode. I also cannot get any of the highlight selections from WSJT to appear in the JTAlert Call selection for Name, QTH, GRID,  ect…  I am running Windows 10, with Signalink to an FT-890 Yaesu, I have match all the setting to the previouse and have triple checked!!  Have not had any issues what so ever since the first of the year with this program. It has been flawless, so, You can imagine my surprise and confusion. I have rebooted after each download, I have uninstalled  and reinstalled about a half a dozen times the whole program and still to this point no success. Hoping for a directional pointer at this point.. Help!!


If JTAlert appears to be in a loop repeatedly displaying the same old decodes, the likely cause is having the UDP received packets rebroadcast enabled and the port incorrectly set to the same port JTAlert is receiving UDP data from WSJT-X.

Open the JTAlert Settings, Applications->WSJT-X section. Is the UDP rebroadcast enabled? If so what port is being used, is it 2237?

Unless your using the rebroadcast for applications like GridTracker, turn it off. If you need it on, change the port to a port different from what WSJT-X has set for the UDP Server port.

Let me know what you discover.

de Laurie VK3AMA

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