locked JTAlert Main Window not Visible SOLVED


Robie - AJ4F
 

The JTalert main screen issue was resolved by deleting the ini file and letting JTAlert regenerate it,


The issue of no communication between WSJT-X and JTAlert was intermittent an has not recurred after switching JTAlert & WSJT-X to multicast.


Thanks for all the assistance!

Robie - AJ4F 

On Tue, Aug 31, 2021, 9:46 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 1/09/2021 11:50 am, Robie - AJ4F wrote:
> Both WSJT-X and JTAlert are set up for unicast.

If you're using Unicast then it is likely that ACLog is seizing
exclusive control of the UDP port and preventing JTAlert from receiving
the UDP messages. Either turn off ACLog integration with WSJTX or switch
both WSJTX and ACLog to multicast, JTAlert automatically detects if
multicast is being used, but you need to ensure that the "Settings ->
WSJT-X UDP Multicast on loopback" menu is ticked. See the JTAlert "Help
-WSJTX UDP Setup" menu.

de Laurie VK3AMA









HamApps Support (VK3AMA)
 

On 6/09/2021 5:04 am, Robie - AJ4F wrote:
The JTalert main screen issue was resolved by deleting the ini file and letting JTAlert regenerate it,


The issue of no communication between WSJT-X and JTAlert was intermittent an has not recurred after switching JTAlert & WSJT-X to multicast.


Thanks for all the assistance!

Robie - AJ4F 
Thanks for the update.

I don't know what ini file you are referring to, JTAlert doesn't use ini files.

de Laurie VK3AMA