JTAlert does nothing.


Don Farrar
 

After upgrading both JTAlert and WSJT-X, JTAlert stopped working?
Went back to Ver 2.16.17 and still nothing?
WSJT-X seems to work and still communicates with ACLog?

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line :

Decode alerts and logging will be unavailable until corrected.

What am I missing?

TAlert 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   :
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version               :
WSJT-X Revision              :
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                :
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : 127.0.0.1
WSJT-X UDP MCast on Loopback : False
WSJT-X UDP Max Schema        : 

Don, VA3ZV


Michael Black
 

Does JTAlert work if you don't start ACLog?

Mike W9MDB




On Monday, June 7, 2021, 11:49:10 AM CDT, Don Farrar <va3zedvee@...> wrote:


After upgrading both JTAlert and WSJT-X, JTAlert stopped working?
Went back to Ver 2.16.17 and still nothing?
WSJT-X seems to work and still communicates with ACLog?

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line :

Decode alerts and logging will be unavailable until corrected.

What am I missing?

TAlert 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   :
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version               :
WSJT-X Revision              :
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                :
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : 127.0.0.1
WSJT-X UDP MCast on Loopback : False
WSJT-X UDP Max Schema        : 

Don, VA3ZV


Don Farrar
 

After turning ACLog off it does start to show call signs, but clicking on them does nothing.
Sometimes the call signs are flashing?
Sometimes no calls show at all?

Don VA3ZV

On Mon, Jun 7, 2021 at 12:53 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Does JTAlert work if you don't start ACLog?

Mike W9MDB




On Monday, June 7, 2021, 11:49:10 AM CDT, Don Farrar <va3zedvee@...> wrote:


After upgrading both JTAlert and WSJT-X, JTAlert stopped working?
Went back to Ver 2.16.17 and still nothing?
WSJT-X seems to work and still communicates with ACLog?

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line :

Decode alerts and logging will be unavailable until corrected.

What am I missing?

TAlert 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   :
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version               :
WSJT-X Revision              :
WSJT-X Spec Op Mode          : None
WSJT-X UDP ID                :
WSJT-X UDP Port              : 2237
WSJT-X UDP Server            : 127.0.0.1
WSJT-X UDP MCast on Loopback : False
WSJT-X UDP Max Schema        : 

Don, VA3ZV


Joe Subich, W4TV
 

What am I missing?
IP Address : 127.0.0.1
You are not using a multicast UDP address!

See the Help Topic: "WSJTX UP Setup" availble by clicking
"Help" in the JT-Alert Main Menu.

73,

... Joe, W4TV


On 2021-06-07 12:48 PM, Don Farrar wrote:
After upgrading both JTAlert and WSJT-X, JTAlert stopped working?
Went back to Ver 2.16.17 and still nothing?
WSJT-X seems to work and still communicates with ACLog?
Unable to communicate with the WSJT-X process.
UDP Port : 2237
IP Address : 127.0.0.1
Values read from WSJT-X config file...
C:\Users\VA3ZV Mark II\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Detected Instance...
Process Window Title : WSJT-X v2.4.0 by K1JT, G4WJS, K9AN, and IV3NWV
Process Command Line :
Decode alerts and logging will be unavailable until corrected.
What am I missing?
TAlert 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 :
WSJT-X --rig-name :
WSJT-X Config File : C:\Users\VA3ZV Mark
II\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version :
WSJT-X Revision :
WSJT-X Spec Op Mode : None
WSJT-X UDP ID :
WSJT-X UDP Port : 2237
WSJT-X UDP Server : 127.0.0.1
WSJT-X UDP MCast on Loopback : False
WSJT-X UDP Max Schema :
Don, VA3ZV


HamApps Support (VK3AMA)
 

On 8/06/2021 5:08 am, Joe Subich, W4TV wrote:
You are not using a multicast UDP address!

See the Help Topic:  "WSJTX UP Setup" availble by clicking
"Help" in the JT-Alert Main Menu.

73,

   ... Joe, W4TV

Tnx Joe.

I have now included the WSJT-X UDP setup instructions into the JTAlert 2.50.0 features help file despite it not being 2.50.0 specific. Too many people have been unable to select the correct Help file despite clear instructions as to where to look. Now there should be no excuse.

de Laurie VK3AMA


Wyndell - K5WJF
 

Now there should be no excuse.” - de Laurie VK3AMA

Wanna bet?

 

73 de Wyndell K5WJF

 

 




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com