Date   

locked JTAlert 2.50.1 No Alert Colors

Dan Bathker
 

I am new to this Group so excuse my possible ignorant question.

I am now running WSJT-X 2.4.0 with JTAlert 2.50.1 and now have no JTAlert color alerts.
In WSJT-X I have 2 colors selected:
Green for any "CQ in message"
and Yellow for any "Transmitted message".
And those work fine.
In JTAlert I have enabled and selected colors for "Wanted Callsign", "Wanted Continent" and "Ignored Callsign" and one or two others.
But those colors do not work.

Prior to installing the latest JTAlert version I did have colors from both WSJT-X (2 colors) and from JTAlert (4 or 5 selected alerts).

I have tried and tried to get JTAlert 2.50.1 colors to work but no luck

Of course having colors is a great Operating Aid so I would like to regain colors working from JTAlert 2.50.1.

Is there some setting or whatever that I am missing?
In JTAlert or in WSJT-X?

Thanks and 73
Dan K6BLG


locked Re: JTAlert doesn't recognize WSJT is running

HamApps Support (VK3AMA)
 

On 6/06/2021 2:44 am, James Wolf wrote:
JTAlert is complaining that WSJT is not running.  I just upgraded to the latest version of JTAlert.  When the installation is done, it complains that the .NET version needed isn't installed.  I did install it when it complained at the initial installation.  It repairs it when I try to install it again.   I have uninstalled it and reinstalled it 
I have looked through the messages about this and have confirmed that neither JTAlert or WSJTx is running in the  Admin mode. 
In WSJT, in the Network section, the UDP and port number have not changed.
The Does JTAlert look for the UDP packets to know if WSJT is running?  

Jim - KR9U

Before JTAlert can look for WSJT-X UDP packets, it needs to know on what port they are being sent and whether unicast or multicast UDP is being used. JTAlert determines the necessary WSJT-X settings by looking for running wsjtx.exe processes running on your PC and then examining their config file.

Is JTAlert indicating it is waiting for wsjtx instance #2 to start? If so that indicates that JTAlert is already running and your trying to start a second instance of JTAlert. If this is not your intention, simply restart your PC to cleanup any old zombie processes and file locks.

If you're not getting an instance #2 waiting message., the likely causes for JTAlert to not find any wsjtx.exe processes running are...
  1. WSJT-X is being run with elevated (Run as administrator) privileges. Check BOTH the wsjtx.exe file AND the shortcut used to start WSJT-X doesn't have the "Run as administrator" setting enabled. If your using another application to start WSJT-X, it too needs to be checked to ensure it is not running elevated  as that will automatically cause any applications it starts to be elevated.

  2. Your PC Protection software is actively interfering, preventing JTAlert from determining what wsjtx processes are running on your PC.

  3. The WSJT-X executable file has been renamed. It needs to stay unchanged as "wsjtx.exe"

de Laurie VK3AMA


locked Re: JTAlert v2.50.1 - Readability of Callsign Boxes

HamApps Support (VK3AMA)
 

On 6/06/2021 3:39 am, Ken K0KV wrote:
The new 2.50.1 release of JTAlert has a lot of interesting new features, but the readability of the individual callsign boxes simply isn't adequate for my eyeballs.  In particular, for callsigns that aren't alerted in some way, the boxes now use a smallish gray font on a gray background.  This isn't very readable, and it makes a quick visual scan of band activity much more difficult.   Changing the fonts to bold has helped a little, and I've widened the boxes as much as I have room for.  Is there a font setting that I've missed in the menus?   Without this, I'll have to revert back to the previous release.   

All Alert colors, including non-alerting, are adjustable. That hasn't changed and neither has the location of the settings. See the Settings windows of the main JTAlert window. Specifically, the non-alert colors are defined under the "Alerts -> Miscellaneous Alerts -> No Alert" section.

If the text of the new callsigns is too small, simply increase their size by zooming the window. Text can been adjusted up to 300%. All the new 2.50.x series windows support zooming of the text. See the "JTAlert 2.50 features" help file, "Standard Window Functionality" topic.

de Laurie VK3AMA


locked Re: JTAlert doesn't recognize WSJT is running

Joe Subich, W4TV
 

On 2021-06-05 12:44 PM, James Wolf wrote:
JTAlert is complaining that WSJT is not running. I just upgraded to the latest version of JTAlert. When the installation is done, it complains that the .NET version needed isn't installed. I did install it when it complained at the initial installation. It repairs it when I try to install it again. I have uninstalled it
and reinstalled it
Did you install the *correct version* of .NET 5.0x? If you are using
the 32 bit version of JT Alert, you *must be* using the 32 bit version
of .NET 5. If you are using the 64 bit version of JT Alert, you
*MUST BE* using the 64 bit version of .NET 5.

In WSJT, in the Network section, the UDP and port number have not
changed.
What about the server address? Are you using a multicast address
(224.0.0.1 through 224.0.0.255 or 239.0.0.1 through 239.255.255.255)
the local loopback (127.0.0.1) address? See the "WSJT-X UDP Setup"
topic in JT ALERT HELP.

73,

... Joe, W4TV


On 2021-06-05 12:44 PM, James Wolf wrote:
JTAlert is complaining that WSJT is not running.  I just upgraded to the latest version of JTAlert.  When the installation is done, it complains that the .NET version needed isn't installed.  I did install it when it complained at the initial installation.  It repairs it when I try to install it again.   I have uninstalled it and reinstalled it
I have looked through the messages about this and have confirmed that neither JTAlert or WSJTx is running in the  Admin mode.
In WSJT, in the Network section, the UDP and port number have not changed.
The Does JTAlert look for the UDP packets to know if WSJT is running?
Jim - KR9U


locked JTAlert doesn't recognize WSJT is running

James Wolf
 

JTAlert is complaining that WSJT is not running.  I just upgraded to the latest version of JTAlert.  When the installation is done, it complains that the .NET version needed isn't installed.  I did install it when it complained at the initial installation.  It repairs it when I try to install it again.   I have uninstalled it and reinstalled it 
I have looked through the messages about this and have confirmed that neither JTAlert or WSJTx is running in the  Admin mode. 
In WSJT, in the Network section, the UDP and port number have not changed.
The Does JTAlert look for the UDP packets to know if WSJT is running?  

Jim - KR9U


locked Re: scan/rebuild

Michael Black
 

It doesn't...mainly because that process disables JTAlert's monitoring of incoming decodes.

I would think that JTAlert 3.0 would allow it though since it should be able to do that in the background.

Would be nice if JTAlert could trigger an auto-download from LOTW too....not that any loggers provide that capability that I know of.

Mike W9MDB




On Saturday, June 5, 2021, 06:25:20 AM CDT, Dev Null <aptget@...> wrote:


When, if ever, does a "scan log/rebuild" take place automatically?


locked Re: scan/rebuild

Larry Banks
 

It doesn’t.

73 -- Larry -- W1DYJ

 

From: Dev Null
Sent: Saturday, June 05, 2021 7:25
Subject: [HamApps] scan/rebuild
 
When, if ever, does a "scan log/rebuild" take place automatically?


locked scan/rebuild

Dev Null
 

When, if ever, does a "scan log/rebuild" take place automatically?


locked WSJT-x, JTAlert 2.50.1

Jon Baker
 

These two programs suddenly stopped working with each other
WSJT-X does not  populate JTAlert as it did in the last 24 hours
I am not aware of any changes to the system  i.e. updates to Windows 10 etc.
Checked the UDP setup as per the help file but they are still not talking
any ideas?
73 Stan  N1ZX

 


locked Re: Settings V 2.50.1

Joe Subich, W4TV
 

What I am looking for, is a window similar to the picure below.
The window you show is available by pressing F2 on the *MAIN*
JTAlert Window.

73,

... Joe, W4TV


On 2021-06-04 5:17 PM, Fernando Pereira wrote:
Joe, many thanks for your comment.
What I am looking for is the settings and not  the options .
I have the icon visible on bottom right side,  same result as F2, but is Options
Perhaps I am missing something.
What I am looking for, is a window similar to the picure below.
73 de Manuel Fernando, ct1bxx
*De: *Joe Subich, W4TV <mailto:lists@subich.com>
*Enviado: *4 de junho de 2021 21:14
*Para: *Support@HamApps.groups.io <mailto:Support@HamApps.groups.io>
*Assunto: *Re: [HamApps] Settings V 2.50.1
If the settings icon is not visible for the 2.5.x windows,
select the window, then strike F2.  F2 summons the Settings
dialog for *any* JT Alert window (just as it does in WSJTX).
73,
    ... Joe, W4TV
On 2021-06-04 11:16 AM, Fernando Pereira wrote:

> Hi,

>

> I am sure is my fault, however I can´t imagine how to solve my problem.

>

> So, I come to ask for your help.

> I installed the latest version 2.50.1, but I can't, nor see how to
access the settings as we had in previous versions.

> To avoid possible errors, I did a second installation and  nothing.
Options appear but settings do not.

> I have installed .NET 5.06

> Thanks so much for your help.

> 73 ct1bxx, Manuel Fernando


locked Re: Settings V 2.50.1

Fernando Pereira
 

Joe, many thanks for your comment.

What I am looking for is the settings and not  the options .

I have the icon visible on bottom right side,  same result as F2, but is Options

Perhaps I am missing something.

 

What I am looking for, is a window similar to the picure below.

 

 

 

73 de Manuel Fernando, ct1bxx

 

De: Joe Subich, W4TV
Enviado: 4 de junho de 2021 21:14
Para: Support@HamApps.groups.io
Assunto: Re: [HamApps] Settings V 2.50.1

 

 

If the settings icon is not visible for the 2.5.x windows,

select the window, then strike F2.  F2 summons the Settings

dialog for *any* JT Alert window (just as it does in WSJTX).

 

73,

 

    ... Joe, W4TV

 

 

On 2021-06-04 11:16 AM, Fernando Pereira wrote:

> Hi,

>

> I am sure is my fault, however I can´t imagine how to solve my problem.

>

> So, I come to ask for your help.

> I installed the latest version 2.50.1, but I can't, nor see how to access the settings as we had in previous versions.

> To avoid possible errors, I did a second installation and  nothing. Options appear but settings do not.

> I have installed .NET 5.06

> Thanks so much for your help.

> 73 ct1bxx, Manuel Fernando

>

>

 

 

 

 

 


locked Re: Settings V 2.50.1

Joe Subich, W4TV
 

If the settings icon is not visible for the 2.5.x windows,
select the window, then strike F2. F2 summons the Settings
dialog for *any* JT Alert window (just as it does in WSJTX).

73,

... Joe, W4TV

On 2021-06-04 11:16 AM, Fernando Pereira wrote:
Hi,
I am sure is my fault, however I can´t imagine how to solve my problem.
So, I come to ask for your help.
I installed the latest version 2.50.1, but I can't, nor see how to access the settings as we had in previous versions.
To avoid possible errors, I did a second installation and nothing. Options appear but settings do not.
I have installed .NET 5.06
Thanks so much for your help.
73 ct1bxx, Manuel Fernando


locked Settings V 2.50.1

Fernando Pereira
 

Hi,

 

I am sure is my fault, however I can´t imagine how to solve my problem.

 

So, I come to ask for your help.

I installed the latest version 2.50.1, but I can't, nor see how to access the settings as we had in previous versions.

To avoid possible errors, I did a second installation and  nothing. Options appear but settings do not.

I have installed .NET 5.06

Thanks so much for your help.

73 ct1bxx, Manuel Fernando

 

 

 


locked Re: Clicking on callsign does nothing

Don Melcher
 

 Specifically the "Accept UDP requests" needs to be enabled. 

Yep! That was it   Tnx  


--
Don
W6CZ
DM07


locked Re: Multiple callsign registrations

Wayne
 

Thanks Laurie 
I will check the settings.


On 4 Jun 2021, at 8:05 pm, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 4/06/2021 1:58 pm, Wayne wrote:
Since upgrading to version 2.50.1 of JTALERT I am getting multiple callsign listings, up to 20 of the same calls and repeated calling of CQ for those calls. I have uninstalled this version and reinstalled but the problem persists. Any help appreciated

This will not be caused by the JTAlert upgrade. It is caused by someone enabling the "Resend WSJT-X UDP packets..." setting and having it incorrectly set to use the same port as the WSJT-X Primary UDP server setting (typically 2237). The JTAlert upgrade did not make those changes. This resend port should NEVER be set to match WSJT-X.

This setting is off by default with a default port of 2334. Someone has incorrectly changed the port and enabled the setting causing incoming UDP messages to be resent back to the input port causing them to be reprocessed again and again in a feedback loop. 

   
<Image 13.png>


de Laurie VK3AMA


locked Re: Multiple callsign registrations

HamApps Support (VK3AMA)
 

On 4/06/2021 1:58 pm, Wayne wrote:
Since upgrading to version 2.50.1 of JTALERT I am getting multiple callsign listings, up to 20 of the same calls and repeated calling of CQ for those calls. I have uninstalled this version and reinstalled but the problem persists. Any help appreciated

This will not be caused by the JTAlert upgrade. It is caused by someone enabling the "Resend WSJT-X UDP packets..." setting and having it incorrectly set to use the same port as the WSJT-X Primary UDP server setting (typically 2237). The JTAlert upgrade did not make those changes. This resend port should NEVER be set to match WSJT-X.

This setting is off by default with a default port of 2334. Someone has incorrectly changed the port and enabled the setting causing incoming UDP messages to be resent back to the input port causing them to be reprocessed again and again in a feedback loop. 

   

de Laurie VK3AMA


locked Multiple callsign registrations

Wayne
 

Since upgrading to version 2.50.1 of JTALERT I am getting multiple callsign listings, up to 20 of the same calls and repeated calling of CQ for those calls. I have uninstalled this version and reinstalled but the problem persists. Any help appreciated


locked Re: Clicking on callsign does nothing

HamApps Support (VK3AMA)
 

On 4/06/2021 8:45 am, Don Melcher wrote:
Should something happen when I click on a calsign of a station calling CQ in the WSJT-X JTalert window? Nothing happens despite the setting of single or double click. 
--
Don
W6CZ
DM07

If you don't see the DXCall in WSJT-X changing in response to a click event in JTAlert that is a good indication that you haven't fully set the Primary UDP server settings in WSJT-X. Specifically the "Accept UDP requests" needs to be enabled.

de Laurie VK3AMA



locked Re: Clicking on callsign does nothing

Michael Black
 

Check that you have  "Double-click on call sets TX enable" in WSJT-X's General settings.

Mike W9MDB



On Thursday, June 3, 2021, 05:52:18 PM CDT, Don Melcher <don@...> wrote:


Should something happen when I click on a calsign of a station calling CQ in the WSJT-X JTalert window? Nothing happens despite the setting of single or double click. 
--
Don
W6CZ
DM07


locked Clicking on callsign does nothing

Don Melcher
 

Should something happen when I click on a calsign of a station calling CQ in the WSJT-X JTalert window? Nothing happens despite the setting of single or double click. 
--
Don
W6CZ
DM07

2021 - 2040 of 37152