Date   

locked Re: Feature request - More Callsign display slots.

HamApps Support (VK3AMA)
 

On 31/08/2020 3:47 pm, Chuck Adams wrote:
Or you can use Settings > Manage Settings > Miscellaneous Alerts > Filters > Show only Callsigns generating alerts.  That will certainly reduce the number of decodes displayed in JTAlert.

73,

Chuck Adams
KV4VT

Chuck,

A quicker method to achieve the same result without the delay in opening the Settings window is to use the "Alerts -> Filters" menu.

de Laurie VK3AMA


locked Re: Feature request - More Callsign display slots.

Chuck Adams
 

Or you can use Settings > Manage Settings > Miscellaneous Alerts > Filters > Show only Callsigns generating alerts.  That will certainly reduce the number of decodes displayed in JTAlert.

73,

Chuck Adams
KV4VT

Sent from my T-Mobile 5G Device


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of Chuck Adams <cfadams@...>
Sent: Monday, August 31, 2020 1:31:14 AM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] Feature request - More Callsign display slots.
 
If you need more relevant decodes displayed, choose the CQ Only option in WSJT-X.  Only CQs will show up.



Sent from my T-Mobile 5G Device



-------- Original message --------
From: Alfred Reeves <areeves18@...>
Date: 8/31/20 1:09 AM (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Feature request - More Callsign display slots.

Why do you need more than 36 decodes displayed?  In the 15 sec decode interval is difficult to examine 36.  What if Laurie gives you 56, 72 etc. your not fast enough to examine them. IMHO it's a waste of programming time and resources.  Just my thoughts.
Al, W1JHU


locked Re: Feature request - More Callsign display slots.

Chuck Adams
 

If you need more relevant decodes displayed, choose the CQ Only option in WSJT-X.  Only CQs will show up.



Sent from my T-Mobile 5G Device



-------- Original message --------
From: Alfred Reeves <areeves18@...>
Date: 8/31/20 1:09 AM (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Feature request - More Callsign display slots.

Why do you need more than 36 decodes displayed?  In the 15 sec decode interval is difficult to examine 36.  What if Laurie gives you 56, 72 etc. your not fast enough to examine them. IMHO it's a waste of programming time and resources.  Just my thoughts.
Al, W1JHU


locked Re: Feature request - More Callsign display slots.

Alfred Reeves
 

Why do you need more than 36 decodes displayed?  In the 15 sec decode interval is difficult to examine 36.  What if Laurie gives you 56, 72 etc. your not fast enough to examine them. IMHO it's a waste of programming time and resources.  Just my thoughts.
Al, W1JHU


locked Re: Problem with JTAlert 2.16.12 and 2.16.13

HamApps Support (VK3AMA)
 

On 31/08/2020 3:24 am, Gerard de Veer wrote:
I have a problem with installing JTAlert 2.16.12 and JTAlert 2,16.13.
See the pictures.
Question is How can I fixe this????
Please give me an Ansher

Best 73

PD0GIP

The two most common causes of JTAlert to not receive UDP traffic from WSJTX and thus producing the error shown is
  1. WSJTX is set to run with elevated privileges. That is either the shortcut used to start the program or the executable itself (check both) is set to "Run as Administrator". There is never any legitimate reason to run WSJTX elevated.

  2. Some other WSJTX interacting application has taken exclusive control of the UDP Server port (2237 in your case)t. Try starting WSJTX and JTAlert only.

I strongly advise that you abandon the use of the 127.0.0.1 port 2237 UDP server settings and utilize a multicast IP address, like 239.255.0.0 on port 2237. Other WSJTX interaction applications like DX Aggregator and Grid Tracker will need to be set to use that multicast IP/Port. There is no setting needed for JTAlert as it will automatically adjust to the new multicast address.

Using multicast will allow multiple applications that interact directly with WSJTX/JTDX to run concurrently, provided they support multicast without adversely affecting the other applications, something that is not possible if using the unicast 127.0.0.1 address..

de Laurie VK3AMA


locked Re: deouble-click in JTAlert not working #FT8

HamApps Support (VK3AMA)
 

On 30/08/2020 10:50 am, ildarin@... wrote:
I see numerous posts on this topic, but no solutions. Unchecking "Color Band Activity" had no effect.
I have the same problem.
Double-clicking in the WSJT-X window works as expected.
.
Tested on Win 7.

OM (name? Callsign?)

What version of WSJT-X?
What version of JTAlert?
Be specific, quote the actual version numbers don't just say "the latest".

BTW, JTAlert changed from using a double-click to single-click for setting up WSJT-X back in version 2.11.4 (Jun 2018)

de Laurie VK3AMA


locked Re: Gray colored CQ - additional information

HamApps Support (VK3AMA)
 

On 31/08/2020 2:55 am, Rich - K1HTV wrote:
I forgot to mention that in addition to the previously worked 8P and 6E prefix stations calling CQ not having a gray background in the WSJT-X Band activity column, I also have noticed that they also Do NOT APPEAR in the JTAlert matrix of displayed callsigns for the 15 second sequence when they appear in WSJT-X.

73,
Rich - K1HTV

Keep in mind that WSJT-X applied coloring to its decodes are independant of the coloring applied (or not) by JTAlert.

If the entire decode row in WSJT-X is colored, that is done by WSJT-X itself based on the log file it maintains and has nothing to do with JTAlert.

JTAlert coloring of WSJT-X decodes involves discrete coloring (not the entire row) of Callsigns and Grids based on the contents of the log used with JTAlert, in your case DXKeeper and the state of the current Alert database.

WSJT-X has no knowledge of what your DXKeeper log contains and it is very unlikely that the WSJT-X maintained log file is not in sync with your DXKeeper log.

IMO, your best to ignore the WSJT-X applied coloring and focus on the JTAlert applied coloring which matches the Alerts generated by JTAlert based on your DXKeeper log.

de Laurie VK3AMA


locked Re: COMMENT

HamApps Support (VK3AMA)
 

On 30/08/2020 10:17 am, Kyle K7KE wrote:
Your post lacked specifics. Here's my take. I've used HRD since 2014. I've found it to be solid and the couple of times I have needed support, the support provided was excellent. I use a pristine ham radio-only PC and Windows updates have never been a problem. And lastly, Laurie is not a 'she'.

Just me 2 cents.

Kyle
K7KE

FWIW, the original poster (OP) had an issue with their HRD log which I quickly identified (took all or ~10 seconds), was due to a corrupt ODBC DSN entry. It was very obvious due to the non-ascii characters shown for the DSN entry.

With HRD logbooks being dependent on ODBC DSNs, I would have expected that HRD Support should have quickly identified the issue due to the critical nature of ODBC in their product. I suspect that is the source of the OP expressed frustrations.

de Laurie VK3AMA


locked Re: 2.16.13 setup files are corrupt

HamApps Support (VK3AMA)
 

On 30/08/2020 9:58 pm, Eliot - KE0N via groups.io wrote:
Attempting to download the 2.16.13 latest rev and met with setup files are corrupt. Anyone else having this issue?

How do you know the files are corrupt?

If you suspect the files are corrupt, the easiest check is to compare the downloaded file size with the size reported on the HamApps JTAlert download webpage. I would also check the sha256 hash for the downloaded file against the published hash.

If the downloaded file size and hash match the published values, then look at your PC protection software which is likely interfering with executing the file.

de Laurie VK3AMA




locked Re: JTA voice alerts but no colored calls

HamApps Support (VK3AMA)
 

On 31/08/2020 3:11 am, Rich - K1HTV wrote:
Using JTA version 13, I am getting "New Grid" and "New Prefix" announcements OK, but no colored callsigns in either JTA or WSJT-X to identify which call is the wanted grids or prefix. When a "Wanted Callsign" is announced, the call is properly colored in both JTA and WSJT-X. I've checked the settings and can't find what might be causing the problem. Any ideas as to why no colored calls for new grids or prefixes?

73,
Rich - K1HTV

When a Callsign generates 2 or more Alerts, audio for each of the Alerts will be played, but only the highest priority Alert will directly control what colors are applied in JTAlert and WSJT-X.

For example, if a Callsign generates a Dxcc, Prefix & Grid alert, with the Dxcc Alert being the highest priority (the default setting), The callsign will have the dxcc coloring applied while at the same time playing the Dxcc, Prefix and Grid audio, but there will be no prefix or Grid coloring applied.

Grid and Prefix coloring will be applied if the Callsign does not generate any other higher-priority alerts.

de Laurie VK3AMA


locked Re: Feature request - More Callsign display slots.

HamApps Support (VK3AMA)
 

On 30/08/2020 12:59 pm, John C wrote:

Hello Laurie, I hope all is well up there.   I have had a request from a mate who is not a forum member to ask for this, and I also think its might be handy.

FT8 is soooooo popular now that jtalert cannot at times, display all of the decoded calls that are on air, so, would it be possible to increase the current maximum number of callsign lines from the present 4 and also increase the maximum 'per line' from the current 9 ?????

 

regards

John
VK7XX


John,

Your friend is welcome to join this group, there are no restrictions.

More Callsign slots is on the "currently being worked on" list (in fact unlimited callsign display), but I cannot provide an ETA.

I respectfully suggest that wanting more Callsigns displayed is the wrong approach. You should be looking at making your operating easier and less chaotic by reducing the number of Callsigns displayed. Engaging one or more Alert filters to remove callsigns that you're likely not interested in working, especially on very busy bands like 20m & 40m where potential QSO partners are many, is the better approach IMO. I would be looking at not displaying worked B4 callsigns as a start.

If you want to see every decoded callsign beyond the hard 36 limit of the main JTAlert window, you will need to have the Decodes window open. There is no limit with that window plus it has it retains past period decodes unlike the main window.

de Laurie VK3AMA


locked Re: Distorted audio on receive

HamApps Support (VK3AMA)
 

On 31/08/2020 4:42 am, Bill Howard wrote:
Thank you Laurie. Very much appreciate your software. I am running a refurbished Dell Optiplex 3010 on Win 10 latest version, with 4gb memory. Only running WSJT-X and JTA lert. Tried everything you suggested with no joy. Switched to an earlier version on WSJT-X and the problem is gone!  Live and learn.
73 - Bill WB3V

Bill, What version of WSJT-X did you downgrade to?

How many CPU cores does the "Dell Optiplex 3010" have?  What model is the cpu (i5 ????).

de Laurie VK3AMA


locked Re: The JTAlert test team is looking for some additional members.

HamApps Support (VK3AMA)
 

On 30/08/2020 5:19 pm, Tom Schaefer NY4I wrote:
If your (sic) interested, please email me direct

Tom NY4I 

Tom,

You're (not your) correct in pointing out the grammatical error.

In my defense, I proof read all my emails, sometimes multiple times, and the pronunciation of "your" & "you're" sound exactly the same in my head, so the incorrect word use goes unnoticed as I focus on misspelling or obvious grammar errors.

de Laurie VK3AMA


locked Re: JTAlert 2.16.12 setup questions

Dave Garber
 

you have GT set to 239.0.0.1, but it does show that you have wsjt or wsjt or log4om on that ip #.   also I think the port should be at 2237 for all. if I understand all this multicast.

I dont use multicast, and JTA, GT, wsjt are all working together.  have not tried n1mm yet

Dave Garber
VE3WEJ / VE3IE


On Sun, Aug 30, 2020 at 2:56 PM Jeff - G4IUA <g4iua@...> wrote:
I'm still having problems with configuring this.  Changing WSJT-X (v2.2.2) UDP server to 239.0.0.1 and selecting GT to Multicast and 239.0.0.1 port 2333 works OK.  However then JTA (v2.16.13) doesn't.  

    
  



I'm afraid this is over my head...I get lost in how all 4 apps talk to each other.  However hopefully the above screen captures will indicate what changes I need to make.  I'm not sure where I should post this question as it is relevant to all apps used but as others seem to have successfully configured exactly the same setup I'd appreciate some help please!

Jeff - G4IUA


locked Re: Feature request

John Kjos
 

Ill second that.

73 John W9RPM

On 8/29/2020 9:59 PM, John C wrote:

Hello Laurie, I hope all is well up there.   I have had a request from a mate who is not a forum member to ask for this, and I also think its might be handy.

FT8 is soooooo popular now that jtalert cannot at times, display all of the decoded calls that are on air, so, would it be possible to increase the current maximum number of callsign lines from the present 4 and also increase the maximum 'per line' from the current 9 ?????

 

regards

John
VK7XX

-- 
EMAIL: john@...
WEBPAGE: http://www.w9rpm.com/
DX CLUB: http://www.tcdxa.org/


locked Re: JTAlert 2.16.12 setup questions

Jeff - G4IUA
 

I'm still having problems with configuring this.  Changing WSJT-X (v2.2.2) UDP server to 239.0.0.1 and selecting GT to Multicast and 239.0.0.1 port 2333 works OK.  However then JTA (v2.16.13) doesn't.  

    
  



I'm afraid this is over my head...I get lost in how all 4 apps talk to each other.  However hopefully the above screen captures will indicate what changes I need to make.  I'm not sure where I should post this question as it is relevant to all apps used but as others seem to have successfully configured exactly the same setup I'd appreciate some help please!

Jeff - G4IUA


locked Re: Distorted audio on receive

Bill Howard
 

Thank you Laurie. Very much appreciate your software. I am running a refurbished Dell Optiplex 3010 on Win 10 latest version, with 4gb memory. Only running WSJT-X and JTA lert. Tried everything you suggested with no joy. Switched to an earlier version on WSJT-X and the problem is gone!  Live and learn.
73 - Bill WB3V


locked Problem with JTAlert 2.16.12 and 2.16.13

Gerard de Veer
 

I have a problem with installing JTAlert 2.16.12 and JTAlert 2,16.13.
See the pictures.
Question is How can I fixe this????
Please give me an Ansher

Best 73

PD0GIP


locked JTA voice alerts but no colored calls

Rich - K1HTV
 

Using JTA version 13, I am getting "New Grid" and "New Prefix" announcements OK, but no colored callsigns in either JTA or WSJT-X to identify which call is the wanted grids or prefix. When a "Wanted Callsign" is announced, the call is properly colored in both JTA and WSJT-X. I've checked the settings and can't find what might be causing the problem. Any ideas as to why no colored calls for new grids or prefixes?

73,
Rich - K1HTV


locked Re: 2.16.13 setup files are corrupt

Rich - K1HTV
 

Eliot,
I also had to temporarily turn off virus protection, then create an exception for the setup file before turning the protection back on. If I didn't, the setup file got quarantined before I could even run it.

73,
Rich - K1HTV