locked Re: Single/double click within callsigns window not working


HamApps Support (VK3AMA)
 

On 8/05/2021 8:35 pm, BOB K5HX via groups.io wrote:
Laurie,

I changed the UDP Port number to 2237 and still am having no luck.  As before, every so often when clicking on a callsign in the callsigns window it works.  

The JTAlert title bar does follow WSJT-X band/mode changes.  I also use Grid Tracker which is set up to use multicast (now port 2237).  However, I am not running Grid Tracker while troubleshooting this issue.

Below is the requested "Current Operating State" information:

JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.3.1   by K1JT, G4WJS, and K9AN
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\Bob\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.3.1
WSJT-X Revision        : 0e7224
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           : 53839 53639
JTAlertV2.Manager.exe : 53587 53588 53589
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Dell AC511 USB SoundBar)
[2] DELL U2414H (Intel(R) Display Audio)
[3] Navigator Transmit (2- USB Audio CODEC )
[4] DELL U2417H-4 (NVIDIA High Definition Audio)
 
 
==================================================
JTAlertV2.Manager (2.50.1.0) status
(2021-05-08 10:33:16 utc)
--------------------------------------------------
CLR Version      : 5.0.5
NET Framework    : .NET 5.0.5
Architecture     : x64 64bit
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X)
Audio            : Initialized : YES (4 output devices)
BandData         : Initialized : YES (stopped)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (K5HX)
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 (stopped)
Environment      : Initialized : YES (started : 3600)
Maintenance      : Initialized : YES (started : 3600)
--------------------------------------------------


Thanks again for your help.

de Bob K5HX

That all looks normal, and your confirmation that the Callsigns window is correctly reporting Mode and Band changes indicates that JTAlert <-> WSJT-X comms is working correctly.

The intermittent nature of the Callsign click responses is the issue, we can rule out loss of comms to WSJT-X. Where in the Callsigns window are your clicking the Callsigns, is it in the main display (displays all decodes) or the "Callers" display (the stations calling you) or is it in both?

de Laurie VK3AMA

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