Date   

locked Re: Any plans to add more RX squares ?

HamApps Support (VK3AMA)
 

On 25/09/2020 10:15 am, ed.n5dg@... wrote:
36 RX squares is fine on most bands . 20m and 40m being the busy bands an extra 16 squares would be about right . instead of 4 x 9 squares 4 X 13 would make the width about the same as WSJTX.
Thanks for the great SW , Ed N5DG

Ed,

This has been discussed many time. See https://hamapps.groups.io/g/Support/message/29940

IMHO, 36 displayed Callsigns is TOO many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed. Try filtering out B4s and non-alerting callsigns.

A JTAlert window with few callsigns displayed due to filtering makes for a more enjoyable (IMO) experience in the shack. It is less stressful time without trying to decide every 15 seconds which Callsign could be a possible QSO candidate. It is a far less chaotic experience.

The beauty with filtering is that a Callsign that is displayed in JTAlert (has passed the filtering) is likely a good candidate for a QSO. But this approach wont appeal to those more interested in racking up a high QSO count, that is qso "quantity" rather than qso "quality".

Currently, there is code with the Test Team (not yet available for public release) that removes the limit on the number of displayed Callsigns. While this new code allows for more than 36 callsigns, its primary focus is providing a flexible display window without any size restriction (width or height) with flexible sizing comes the additional benefit of increased callsigns displayed. Sorry, there is no ETA on when this will be available publicly.

de Laurie VK3AMA


locked Any plans to add more RX squares ?

ed.n5dg@...
 

36 RX squares is fine on most bands . 20m and 40m being the busy bands an extra 16 squares would be about right . instead of 4 x 9 squares 4 X 13 would make the width about the same as WSJTX.
Thanks for the great SW , Ed N5DG


locked Re: 23 second JTAlert startup time

KD7YZ Bob
 

On 9/23/2020 16:52, HamApps Support (VK3AMA) wrote:
On 23/09/2020 7:41 pm, KD7YZ Bob wrote:
How long does it take for the "Reading Settings Data" window to display?
It should appear within 1 second or less.
   
Thanks to Mike W9MDB for logging onto my computer and doing some sleuthing.

It seems, a while back, I'd played around with JTAlert "Auto-Start"
features.

They were still active.

In a way...

Unbeknownst to me, the "Programs" I had JTAlert attempt to launch, were
.LNK's (AKA shortcuts) or they were .bat's

well it seems JTAlert AutoStart quietly skipped over the shortcuts
without saying a peep then dutifully executed the 20 or 30 second
intervals I had put in.

Ida never suspected this since all I saw was 'nothing' until JTAlert
finally started.

So there y'all go. My bad !

5 or 6 seconds now is the norm.


--
73
Bob KD7YZ
AMSAT LM #901


locked Re: JTAlert (JTDX Version) Reporting QSO Logging Error on HRD FT4 Contacts

John K7KB
 

Opps!! Nevermind :) I was running a earlier version of JTAlert and this problem was apparently corrected in recent versions as I just installed 2.16.13 and the error no longer appears. This also shows the importance of keeping your applications updated :)

John K7KB


locked JTAlert (JTDX Version) Reporting QSO Logging Error on HRD FT4 Contacts

John K7KB
 

Today I made some changes to my HRD Logging software so that it would log FT4 contacts as a Mode MFSK and Submode of FT4 as specified in this video:

https://youtu.be/v90ylxfn1Cg

One of the changes in the video has you set JTAlert in the Logging Options for "Log FT4 as ADIF 3.1.0 compliant Mode=MFSK, SUBMODE=FT4".

However, when I do this and the QSO is logged, I get the following error:



The thing of it is that the QSO does get logged, and it seems that it's in the proper format as a mode of MFSK and submode of FT4. So in the mean time I have the logging option turned off in JTAlert and will make manual changes in my HRD Log as necessary until this gets fixed, or someone tells me what I'm doing wrong :)


locked Re: JTAlert question

Tim
 

Ok. Sorry for intruding in on the satire.


Tim - N8NEU
FN00ah



-------- Original message --------
From: "Barry via groups.io" <boat.anchor@...>
Date: 9/24/20 09:33 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert question

Tim
I am one of those neighbors to the north and therefore
did not hesitate to poke fun at ourselves. That also seems
to be traditional north of 48deg.
cheers
Barry
VA7GEM
On Wed, Sep 23, 2020 at 06:46 PM, Tim wrote:
That was not very nice to say about our neighbors to the north.
 
 
 
Tim - N8NEU
FN00ah
 
 
 
-------- Original message --------
From: "Barry via groups.io" <boat.anchor@...>
Date: 9/23/20 10:29 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert question
 
On Tue, Sep 22, 2020 at 05:16 PM, Bob Willey wrote:
I noticed something showing up recently, mostly Canada stations
shows their Callsign as RED in WSJT-X and JTAlert & Decodes
 
Don't remember seeing that before, unless I clicked on something.
 



 
photo  
Bob Willey
K3RLW

(410) 251-8960 | K3RLW@...

http://qrz.com/db/K3RLW

5161 Ocean Gateway, Trappe Maryland 21673-2023 USA
 

Bob

Bob
This is due to the fact Canadians have a red flag and are somewhat socialist.
cheers
Barry

 


locked Re: JTAlert question

Barry <boat.anchor@...>
 

Tim
I am one of those neighbors to the north and therefore
did not hesitate to poke fun at ourselves. That also seems
to be traditional north of 48deg.
cheers
Barry
VA7GEM

On Wed, Sep 23, 2020 at 06:46 PM, Tim wrote:
That was not very nice to say about our neighbors to the north.
 
 
 
Tim - N8NEU
FN00ah
 
 
 
-------- Original message --------
From: "Barry via groups.io" <boat.anchor@...>
Date: 9/23/20 10:29 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert question
 
On Tue, Sep 22, 2020 at 05:16 PM, Bob Willey wrote:
I noticed something showing up recently, mostly Canada stations
shows their Callsign as RED in WSJT-X and JTAlert & Decodes
 
Don't remember seeing that before, unless I clicked on something.
 



 
photo  
Bob Willey
K3RLW

(410) 251-8960 | K3RLW@...

http://qrz.com/db/K3RLW

5161 Ocean Gateway, Trappe Maryland 21673-2023 USA
 

Bob

Bob
This is due to the fact Canadians have a red flag and are somewhat socialist.
cheers
Barry

 


locked Re: 23 second JTAlert startup time

KD7YZ Bob
 

On 9/23/2020 16:52, HamApps Support (VK3AMA) wrote:

This sounds like PC protection interference to me.
Does your protection software go online to perform an analysis of
suspect files? If so that would account for such a lengthy startup delay.
As best as I am able to verify, I manually shut off system wide
protection(s). In-so-much as I get a 'Nag" from windows Defender for a
day telling me that NO protection is activated would I like to turn
Defender back on.


How long does it take for the "Reading Settings Data" window to display?
It should appear within 1 second or less.
   
I started 'process explorer" as seen in screenshot ...JtAlert then
JTalertmanager begins the well within a second, 'reading settings... "
appears ... then there's the 20 second delay


--
73
Bob KD7YZ
AMSAT LM #901


locked Re: 23 second JTAlert startup time

KD7YZ Bob
 

On 9/23/2020 16:52, HamApps Support (VK3AMA) wrote:


Sorry, while the log caching mechanism you describe exists within
JTAlert and is core to its operation, it is not part of the JTAlert
Oy. Just when I was resigned to accept the strange delay.
Thanks Laurie for clarifying.

--
73
Bob KD7YZ
AMSAT LM #901


locked Re: JTAlert question

Tim
 

That was not very nice to say about our neighbors to the north.



Tim - N8NEU
FN00ah



-------- Original message --------
From: "Barry via groups.io" <boat.anchor@...>
Date: 9/23/20 10:29 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert question

On Tue, Sep 22, 2020 at 05:16 PM, Bob Willey wrote:
I noticed something showing up recently, mostly Canada stations
shows their Callsign as RED in WSJT-X and JTAlert & Decodes
 
Don't remember seeing that before, unless I clicked on something.
 



 
photo  
Bob Willey
K3RLW

(410) 251-8960 | K3RLW@...

http://qrz.com/db/K3RLW

5161 Ocean Gateway, Trappe Maryland 21673-2023 USA
 

Bob

Bob
This is due to the fact Canadians have a red flag and are somewhat socialist.
cheers
Barry

 


locked Re: Click on spots

HamApps Support (VK3AMA)
 

On 23/09/2020 3:44 am, Neil wrote:
It had been working and somehow Windoze decided to uncheck the boxes when it did a recent update. MS thinks they are smarter than the users and think it knows what is best for us.
I appreciate and use ur program
73 and stay well.....Neil   N4FN

Windows won't have unchecked those check-boxes. That will have been due to either your WSJTX config (.ini) file being renamed/deleted or starting WSJTX with a new (previously unused) --rig-name parameter. All three check-boxes unchecked is the default setting.

de Laurie VK3AMA


locked Re: JTAlert question

HamApps Support (VK3AMA)
 

On 24/09/2020 12:29 am, Barry via groups.io wrote:
I noticed something showing up recently, mostly Canada stations
shows their Callsign as RED in WSJT-X and JTAlert & Decodes
 
Don't remember seeing that before, unless I clicked on something.

FYI,

Red text on a white background is the default coloring for the Wanted VE Province Alert.

de Laurie VK3AMA


locked Re: settings - JT-Alert

HamApps Support (VK3AMA)
 

On 22/09/2020 11:14 pm, dbushinsky wrote:

My computer will not allow me to install a newer version of JTAlert - it says I do not have permission to run the program.

thank you - 73 - David W2PD

What is the exact error message? Please post an image of the offending window (not your entire desktop).

de Laurie VK3AMA


locked Re: Jtalert2.16.13 is not logging with jtdx and HRD (latest version) #HRD

HamApps Support (VK3AMA)
 

On 24/09/2020 1:11 am, Gerard de Veer wrote:
I using now version 2.16.10 because when I Install 2.16.13 the qso's I make are not logged in HRD.

PD0GIP
OM,

When QSOs are not logged to HRD does JTAlert show an error message?

Provided you use the "OK" button on the WSJTX/JTDX "Log QSO" window JTAlert will log the QSO to HRD.

de Laurie VK3AMA


locked Re: JTalert "First QSO" permanently

HamApps Support (VK3AMA)
 

On 24/09/2020 12:24 am, Michael Black via groups.io wrote:
Have you done a scan & rebuild of the JTAlert database?


FYI,

A Rebuild Database operation does not affect the QSO History data of a Callsign. It is used for updating the needed entities for the Alerts.

Status messages like "First QSO" don't involve the Alert Database, they come from a direct read of the users Log.

de Laurie VK3AMA
 


locked Re: JTalert "First QSO" permanently

HamApps Support (VK3AMA)
 

On 24/09/2020 12:20 am, Jean-Claude F1DSZ wrote:
I am using JTalert version 2.16.13, and I've noticed for some time that when I contact a station, JTDX tells me
B4 signal but JTalert always announces "First QSO" permanently....view attachment.
A parameter would be at fault.
Thank you for your answer J. Claude F1DSZ


What you describe will occur if your logbook is empty or missing.
Do you have JTAlert set to use the correct (current active) HRD logbook. You may have it set to an old logbook.

de Laurie VK3AMA


locked Re: 23 second JTAlert startup time

HamApps Support (VK3AMA)
 

On 23/09/2020 10:02 pm, Bill Barrett wrote:
The first instance is reading the database from your log. The second
and additional instances get the data from cache.
Bill,

Sorry, while the log caching mechanism you describe exists within JTAlert and is core to its operation, it is not part of the JTAlert startup. There are no log lookups performed at startup.

de Laurie VK3AMA


locked Re: 23 second JTAlert startup time

HamApps Support (VK3AMA)
 

On 23/09/2020 7:41 pm, KD7YZ Bob wrote:
Windows 10-Pro x64
JTAlert 2.16.13 WSJTx 2.2.2

I run three instances of both.
The first instance of JTAlert ALWAYS takes circa 23 seconds to start.
The remaining two roughly 4-6 seconds individually.

I start JtAlert manually, waiting for the first one to finish. Then the
next and then the last.

It doesn't matter if I stop ALL and any A/V or other malware scanners.
HAMAPPS folder is listed as don't scan; JtAlert is the same.

If I stop all three JTAlert ... then begin the three again, the first
one takes 23 or so seconds to get started.

It doesn't matter time time of day or night.

So, since it's quite obviously NOT JTAlert, then someone gimme a hint
what computer setting I have messed up. This has been going on for at
least a month or so ... I've lost track of when I noticed it.


tnx

-- 73 Bob KD7YZ

Bob,

This sounds like PC protection interference to me.
Does your protection software go online to perform an analysis of suspect files? If so that would account for such a lengthy startup delay.

How long does it take for the "Reading Settings Data" window to display? It should appear within 1 second or less.
   

de Laurie VK3AMA


locked Re: Keyboard latency with multiple JTAlert processes running.

HamApps Support (VK3AMA)
 

On 23/09/2020 6:54 am:

Hey folks,

Sorry I'm sure this is an edge case, but I am a Flexradio user and I typically operate WSJT-X with at least 4 bands running simultaneously. I will feed each slice of the Flex to a different WSJT-X process, and then I will run an equal number of JTAlert instances, each capturing the UDP stream of the individual WSJT-X process.

I have noticed that as I add more JTAlert instances, my Keyboard latency will decrease linearly. By the time I have reached 4 processes, the latency is to the point where typing is very difficult.

My system is not taxed at all with all these programs running, I have a 12-core 4.0Ghz processor, and 32GB ram with a very fast GPU, and NVME storage. CPU usage while decoding 4 bands is 10- 20% & memory consumption is about 50%.

I have tried debugging for most of the day, and can confirm that the latency only happens with multiple JTalert instances running. I do not feel any keyboard sluggishness when I add more WSJT-x or Flexradio slices.


Has anyone encountered this before?

I am running version 2.16.13 of jtalert, 2.2.2 of WSJT-x and 15.8.0 of Dxkeeper.

Attached are some screenshots of my setup + a view of my system utilization when this is all running.

Thanks.

W9PDS
OM,

Try temporarily turning off monitor on all your WSJTX instances so there is no new decodes processing in WSJTX and by extension no new decodes processing in JTAlert. Do you still get the keyboard latency?

de Laurie VK3AMA


locked Re: JTalert "First QSO" permanently

Dave Garber
 

double check that the station is using the same grid as you had worked him before.  I have had a few times where this happens, especially if they use multi qth's...


Dave Garber
VE3WEJ / VE3IE


On Wed, Sep 23, 2020 at 10:47 AM Jean-Claude F1DSZ <f1dsz@...> wrote:
Yes I made a reconstruction of the database.
but how to make an analysis ?
  Thank you J. Cl. F1DSZ

3221 - 3240 of 34751