locked JTAlert Never shows any callsigns.


Ken Finke
 

I just installed version 2.50.6 of JTAlert, and upgraded to version 2.4.0 c19d62 of WSJT-X.  Now JTAlert does NOTHING.  I see no callsigns in the call window.  I do see in the main window at the top: [15m,FT8,HRD6+,#1].

Also in the Callsigns window is see 15m FT8 and the callsign of the last station called.  But changes made in WSJT-X are not updated. 

 

Earlier versions worked great.

Disappointed!

 

In JTAlert:

WSJT-X UDP Multicast on Loopback is checked.

JTAlert Instance       : #1

JTAlert Start Params   : /wsjtx

WSJT-X Window Title    : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV

WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe"

WSJT-X   --rig-name    :

WSJT-X Config File     : C:\Users\kefin\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version         : 2.4.0

WSJT-X Revision        : c19d62

WSJT-X Spec Op Mode    : None

WSJT-X UDP ID          : WSJT-X

WSJT-X UDP Port        : 2237

WSJT-X UDP Server      : 239.255.0.1

WSJT-X UDP MCast on LB : True

WSJT-X UDP Max Schema  : 3

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 61371 57169

JTAlertV2.Manager.exe : 63990 63991 63992

JTAlertV2.Decodes.exe :

 

 

==================================================

Audio output devices

--------------------------------------------------

[1] Speakers (Realtek(R) Audio)

[2] Speakers (USB Audio CODEC )

[3] CABLE Input (VB-Audio Virtual Cable)

 

 

==================================================

JTAlertV2.Manager (2.50.6.0) status

(2021-09-22 20:11:25 utc)

--------------------------------------------------

CLR Version       : 5.0.1

NET Framework     : .NET 5.0.1-servicing.20575.16

Architecture      : x64 64bit

--------------------------------------------------

UDP Router        : Initialized * : YES (WSJT-X)

Audio             : Initialized * : YES (3 output devices)

Activity Service  : Initialized * : YES (started : 58)

Messaging Service : Initialized * : YES (started : 17)

HamSpots Service  : Initialized * : YES

QRZ Xml           : Initialized * : YES

HamQth Xml        : Initialized * : YES

QRZ Log           : Initialized * : YES

HamQth Log        : Initialized * : YES

ClubLog Log       : Initialized * : YES

Eqsl Log          : Initialized * : YES

HrdLog Log        : Initialized * : YES

DXLab DDE         : Initialized * : YES

User Alert        : Initialized * : YES

Updates Check     : Initialized * : YES (started : 3600)

Environment Check : Initialized * : YES (started : 3600)

Maintenance       : Initialized * : YES (started : 3600)

--------------------------------------------------


HamApps Support (VK3AMA)
 

On 23/09/2021 6:24 am, Ken Finke wrote:

I just installed version 2.50.6 of JTAlert, and upgraded to version 2.4.0 c19d62 of WSJT-X.  Now JTAlert does NOTHING.  I see no callsigns in the call window.  I do see in the main window at the top: [15m,FT8,HRD6+,#1].

Also in the Callsigns window is see 15m FT8 and the callsign of the last station called.  But changes made in WSJT-X are not updated. 

 



What version of JTAlert did you upgrade from?

Since The Callsigns window is reporting the WSJTX Band/Mode/DXCall in the statusbar and the main JTAlert window is also reporting the Band/Mode, that indicates that the UDP comms with WSJTX is working correctly so that is not the reason for no callsigns being displayed.

Please post an image of your Callsigns window, not the entire desktop, just that window.

de Laurie VK3AMA