Date   

locked Re: JTAlert for JTDX and WSJT-X - ver. 2.50

EDMUNDO CAMPUSANO
 

Hi John

Do you work with more monitors? Maybe it's on the other monitor.-

Greetings

73 Edmundo CE2EC

El mar, 13 de abr. de 2021 a la(s) 11:23, Jim N6VH (N6VH@...) escribió:

On 4/13/2021 8:13 AM, John Profita wrote:
> I downloaded the 5.0.5-win-64 Framework being it was not on my Win 10 computer. Then I downloaded the JTALERT for both JTDX and WSJT-X. But all I see is the decodes window, see attached. There is no JTALERT that I can get into settings etc. I deleted from program files (x86) the unins000.exe and that went well? I tried again to download both from HamApps  and still does the same thing.
>
> Tnx John
> ND1X

John,

It is possible that the Callsigns window is on top of the main JTAlert
window. Try moving the Callsigns window. If the window won't move, click
on the cog to open the settings. Go to "Window", and make sure "Position
locked" is not checked.

73,

Jim N6VH








--
Edmundo 73, CE2EC
La Serena


locked dB vs Grid?

Bill - AA4M
 

I just downloaded 2.50.0 and spent about 2 hours working with it.  All I can say is FLAWLESS, WOW!

I did have one request for an enhancement.  Anybody who's ever worked DX knows that they often start a QSO with the dB report rather than a grid.  I like this, especially in marginal conditions.  What I'd like to see in JTAlert is an option to make my response to a CQ or tailgate (by double clicking in the callsign window) begin with my sending dB rather than grid location.  Can such a feature ever be implemented?

Thanks for the great software Laurie!

73, Bill  AA4M


locked icon messaging #FT8

f8nhf
 

Hello

the new version is great I had no problem. Great work thank you Laurie and your team of testers
question anyway hi hi hi

in the old version we could see which station had activated the messaging, the callsign was underlined. with version 2.50.0 apparently  
would it be possible to enlarge the star or put another icon more visible (like CQ, DX, 73 alerts)

73 Denis  F8NHF


locked Re: 2.5.0 -- AutoIt Error

David - AK2L
 

You don't turn off virtual screens -- they are a part of Windows 10.  But I did as you asked anyway and moved everything to what I will call "desktop 0".  I then re-enabled HRD6 logging.  JTAlert silently quit within 60 seconds.

Clearly, JTAlert doesn't like being connected to my HRD installation.  This is not a new problem; it existing in earlier versions of JTAlert as well.  But with the earlier versions, it would usually happen only once when I changed a setting.  I would then restart JTAlert and all would be well until I changed another setting.  With v2.50, it happens every time.

I would be interested to hear from other HRD6 users to see if they have seen any problems.

For now, I will look at logging directly from WSJT-X or perhaps changing my logging program altogether.


locked Re: Slow ADIF import

Michael Black
 

For Laurie....

Sometimes this can be sped up dramatically by wrapping the entire import in a transaction.  Are you already doing that?
And it appears you do postpone the index creation until it's done which is good too.

Mike W9MDB






On Tuesday, April 13, 2021, 10:35:19 AM CDT, John Holmes W9ILY <w9ily@...> wrote:


Laurie,

As you may recall my ADI fie is over 85 MB for over 249,000 records and the load time took over 116,000 ms to complete. Can this be improved? Thanks for all of your latest enhancements!

 

John W9ILY


locked Re: JT Alert

Greg Yates <gyates@...>
 

Thanks,

 

I found it

 

Greg, WB2BIN

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Greg Yates via groups.io
Sent: Tuesday, April 13, 2021 11:35 AM
To: Support@HamApps.groups.io
Subject: [HamApps] JT Alert

 

I know I am missing something but I have read the release notes and played with the new version which is great.

 

Where am I overlooking how to get the signal strength back….like -5 ect.

 

Thanks

 

Greg, WB2BIN


locked Re: JT Alert

Michael Black
 

Click the gear in the lower right corner then turn on dB

Inline image
Mike W9MDB




On Tuesday, April 13, 2021, 10:34:45 AM CDT, Greg Yates via groups.io <gyates@...> wrote:


I know I am missing something but I have read the release notes and played with the new version which is great.

 

Where am I overlooking how to get the signal strength back….like -5 ect.

 

Thanks

 

Greg, WB2BIN


locked Slow ADIF import

John Holmes W9ILY
 

Laurie,

As you may recall my ADI fie is over 85 MB for over 249,000 records and the load time took over 116,000 ms to complete. Can this be improved? Thanks for all of your latest enhancements!

 

John W9ILY


locked JT Alert

Greg Yates <gyates@...>
 

I know I am missing something but I have read the release notes and played with the new version which is great.

 

Where am I overlooking how to get the signal strength back….like -5 ect.

 

Thanks

 

Greg, WB2BIN


locked Re: JTAlert for JTDX and WSJT-X - ver. 2.50

Jim N6VH
 

On 4/13/2021 8:13 AM, John Profita wrote:
I downloaded the 5.0.5-win-64 Framework being it was not on my Win 10 computer. Then I downloaded the JTALERT for both JTDX and WSJT-X. But all I see is the decodes window, see attached. There is no JTALERT that I can get into settings etc. I deleted from program files (x86) the unins000.exe and that went well? I tried again to download both from HamApps and still does the same thing.

Tnx John
ND1X
John,

It is possible that the Callsigns window is on top of the main JTAlert window. Try moving the Callsigns window. If the window won't move, click on the cog to open the settings. Go to "Window", and make sure "Position locked" is not checked.

73,

Jim N6VH


locked JTAlert for JTDX and WSJT-X - ver. 2.50

John Profita
 

I downloaded the 5.0.5-win-64 Framework being it was not on my Win 10 computer. Then I downloaded the JTALERT for both JTDX and WSJT-X. But all I see is the decodes window, see attached. There is no JTALERT that I can get into settings etc. I deleted from program files (x86) the unins000.exe and that went well? I tried again to download both from HamApps and still does the same thing.

Tnx John
ND1X


locked 2.50.0 with WSJT-X 2.3.1 crashes

John, DK9JC / AK9JC
 

After some hours JTAlert 2.50.0 freezes.

WSJT-X 2.3.1 with Log4OM.
WSJT-X decode is fine, but nothing showing on JTAlert Callsign window and after a QSO, it's logged the WSJT-X adif, but QSO does not move into the Log4OM Log.

After a restart of JTAlert it works for some time until it crashed agn.

Win 10 Pro latest build and latest net installed.


locked Re: Alerts/spots

Joe Subich, W4TV
 

On 2021-04-13 10:00 AM, Neil Foster wrote:
How can I limit the number of spots?
I use the Filters ... Alerts -> Filters

Typically, I select "Show only callsigns generating Alerts"

73,

... Joe, W4TV


On 2021-04-13 10:00 AM, Neil Foster wrote:
WOW...the new 2.50 format is nice. I see too many spots in JT Alert. I have searched the help file and can not find the answer. How can I limit the number of spots? Sometimes there are too many for this old geezer to see. Before I had it limited to 9 I think??
Many thanks
Neil   N4FN


locked Alerts/spots

Neil Foster
 

WOW...the new 2.50 format is nice. I see too many spots in JT Alert. I have searched the help file and can not find the answer. How can I limit the number of spots? Sometimes there are too many for this old geezer to see. Before I had it limited to 9 I think??
Many thanks
Neil   N4FN


locked No problem!

W1UU
 

No problem for me to install 2.50.0

Like anything, one has to get use to software changes to match operating styles.

I just need to pick and choose some of the optional settings. Part of the fun of JT Alert is choosing!

Peter W1UU



--
Peter Butler
W1UU


locked Re: Ver 2.50.0 issues

Fred Roberts
 

Laurie.....
       Good news! The answer to my question....should I have chosen the x64 version is YES!!!!....no problem uninstalling the x86 version, I just sorted by date installed, followed the link you provided in your install instructions, choose the CORRECT version, and 2.50.0 is up and running!
Tnx es 73,
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 8:26 AM Fred Roberts via groups.io <fred5352=gmail.com@groups.io> wrote:
Good morning Laurie.....
      A bit of help needed. Installed 2.50.0 and after a minute or two wait I get the following pop up window:
     I am running Windows 10 Home. I did get the warning that . Net 5 wasn't installed, and I installed it (I choose the x86 version - should I have used x64?)  
I've also included a shot of the WSJT-x settings.
     Thanks for your help, and a great program!
73,
Fred
WB4QOC



On Tue, Apr 13, 2021, 7:59 AM Bill Barrett <billbarrett174@...> wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA

Attachments:


locked Re: 2.50.0 Display priority callsigns/callers

Andy k3wyc
 

On Tue, Apr 13, 2021 at 05:35 AM, Andy k3wyc wrote:
Is there any way to inhibit the display of callers?
I found the "disable" option in the display position list.

73,
Andy, k3wyc


locked 2.50.0 Display priority callsigns/callers

Andy k3wyc
 

First of all thanks for this feature rich update to JtAlert.  As I became familiar with it I found several things I would like to change and, sure enough, there was an option that allowed me to configure the way I wanted.

So far I have not found no way to change the relative priority for displaying callsigns vs callers.   I have set a fixed size for the callers and adjusted the window size and position but not locked size or position.  My chosen settings allow 4 rows of 8 callsigns.   When someone calls me the auto-open callers display blocks the bottom line of my callsign display.  Since I usually consider these callers to be low priority I'd prefer they did not block the callsigns.

Is there any way to make callsigns have priority over callers  i.e. only display callers if there is space available?
is there a way to have the window size automatically increase to add callers?
Is there any way to inhibit the display of callers?

Thanks and 73,
Andy, k3wyc



locked Re: independent windows #JTDX

sv1hep@...
 

I fount it !! False alarm.


locked Re: Ver 2.50.0 issues

Fred Roberts
 
Edited

Good morning Laurie.....
      A bit of help needed. Installed 2.50.0 and after a minute or two wait I get the following pop up window:
     I am running Windows 10 Home. I did get the warning that . Net 5 wasn't installed, and I installed it (I choose the x86 version - should I have used x64?)  
I've also included a shot of the WSJT-x settings.
     Thanks for your help, and a great program!
73,
Fred
WB4QOC
 
 

On Tue, Apr 13, 2021, 7:59 AM Bill Barrett <billbarrett174@...> wrote:
Hello Laurie-
 
Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:
 
1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.
 
2.) Instance #1 does not always display the Band and Mode.
 
3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.
 
The new call window is very flexible.
 
Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA

 

 

 

 

3861 - 3880 of 37666