Date   

locked Re: dB vs Grid?

Joe Subich, W4TV
 

That would require a change in WSJTX.

73,

... Joe, W4TV

On 2021-04-13 12:27 PM, Glenn Jensen wrote:
I too like the new version – would be ideal to ‘sort’ by db….
Hey, version 2.6 …
Good stuff – Kudos – 73’s Glenn
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Bill - AA4M
Sent: Tuesday, April 13, 2021 8:55 AM
To: Support@HamApps.groups.io
Subject: [HamApps] dB vs Grid?
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 Re: Callsign window in V2.50 opens independently from applications scheduled to open when starting

HamApps Support (VK3AMA)
 

On 14/04/2021 1:05 am, WU9D wrote:
That being said, the callsign window opens BEFORE any applications I have specified to open FIRST. The callsign window needs to open AFTER any applications specified, just like the JT Alert main window.

That is not the case. The Callsigns window is directly controlled by the JTAlert process. If JTAlert is not started, the Callsigns window will not start. It is impossible to open the Callsigns window without starting JTAlert first.

Regardless of how quickly the Callsigns window is displayed, it will not display and decoded/alerted Callsigns until the main JTAlert process has finished its start-up and established comms with WSJT-X.

What is the problem with the Callsigns window showing early, it still takes up the same amount of screen-space and in the same location as when it was last used. I honestly don't understand the complaint, unless I am missing something in your message.

What is the issue with the window showing a second or two early? Please explain.

de Laurie VK3AMA


locked Re: dB vs Grid?

Bill - AA4M
 

Hello Scott,

Thanks for the tip Scott.  That worked, the only (minor) problem is that it loses the setting when I close WSJT-X and start it up again.  I can easily live with this!  :)

BTW - you have a nice callsign!  See you in the pileups

73, Bill  AA4M


On 04/13/2021 10:06:25, Scott Armstrong wrote:
Bill,

That function/feature already exists in WSJT-X.
Double right click on the Tx1 button. The Tx1 message box will grey out and all QSO will start with the  Tx2 message.

-Scott AA5AM



On Tue, Apr 13, 2021 at 10:54 AM Bill - AA4M <MrBill@...> wrote:
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 Re: 2.5.0 -- AutoIt Error

HamApps Support (VK3AMA)
 

On 14/04/2021 1:49 am, David - AK2L wrote:
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.

There are several members of the JTAlert Test Team that use HRD logging. None have reported this issue.

What Log type are you using in HRD? Is it MSAccess? There have been numerous problems with HRD MSAccess logs in recent months that have affected JTAlert. They didn't crash JTAlert but typically caused significant slowdown. The fix in all cases was to create a new Log in HRDLogbook and then set the new log in JTAlert. The problem appears to be tied into the ODBC DSN that HRD uses for its logs. Creating a new DSN, which happens when creating a new log seems to clear the problem. Some MSAccess log users have converted to MariaDB which solved the problem for them.

de Laurie VK3AMA


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

John Profita
 

Edmundo, I do have 2 monitors but I have on 1 monitor my log program (LOG4OM) and the other window I run the JTDX or WSJT-X with JTAlert. Knowing that JTAlert is different for each. Because is the same for both. No JTAlert. I am decoding around 40 to 50 and sometimes even 60 plus. Not sure what to do at this point. Its frustrating for sure.

Tnx, John ND1X


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

John Profita
 

Jim, I checked and and the JTAlert window is not behind the callsign window. Its no where to be found for some reason. I am sure its something simple but for the life of me I can't find it. Its frustrating! I like the callsign window.

John ND1X


locked Re: km vs miles

HamApps Support (VK3AMA)
 

On 14/04/2021 2:35 am, Fred Roberts wrote:
I've spent the last 30 minutes trying to find the setting to change km to miles when I hover over a station in the decodes window. 
I have 'display distance in miles' checked in WSJT-x 2.2.2.
I must be blind because I can't find the option in JTalert.
Thanks,
Fred
WB4QOC

Fred, I think your mean the "Callsigns" window, not the "Decodes" window. They are two different beasts. See the titlebar.

Most of what gets displayed in the new Callsigns window is coming from the old JTAlert, it is still performing the Alerting checks on the incoming decodes. Have a look ate the "Settings -> Decoded Callsign Data Tooltip" menu of the main JTAlert (the old JTAlert) window.

   

de Laurie VK3AMA


locked Re: dB vs Grid?

HamApps Support (VK3AMA)
 

On 14/04/2021 1:54 am, Bill - AA4M wrote:
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?

73, Bill  AA4M
Bill,

JTAlert cannot control the message sent by WSJT-X after a callsign is clicked/double-clicked. The WSJT-X interface protocol doesn't support selecting message type.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 Upgrade help needed

HamApps Support (VK3AMA)
 

On 14/04/2021 1:10 am, Bill Rogers wrote:
I upgraded JTAlert to 2.50.0 from 2.16.10 (I think) for use with WSJT-X.  After the install the Callsign Window and others like "About" don't come up when selected. I am also getting an Unable to communicate with the WSJT-X process: UDP Port 2237 IP Address 127.0.0.1. 

I did not modify my setup after the installation and it appears WSJT-X is still set up to use port 2237.

Is there a remedy or something to try?

Is there a way to go back to the older version safely?

Thanks,
Bill K2TER

All those symptoms indicate that the JTAlertV2.Manager.exe process is not running.

That process requires the .NET 5 Desktop Runtime to be installed. Make sure it is installed and of the correct architecture  (32bit or 64bit), The Runtime needs to match your Windows architecture.

If your running Windows 64bit install the X64 runtime, if 32bit install the X86 runtime.

de Laurie VK3AMA


locked Re: 2.50.0 with WSJT-X 2.3.1 crashes

John, DK9JC / AK9JC
 

Are you configured for a "multicast" address from WSJT-X to your clients?

Hello Ray,

here are the settings in WSJT-X:



Log4OM Settings in JTAlert 2.50.0:


locked Re: JTAlert Will Not Install

HamApps Support (VK3AMA)
 

On 14/04/2021 3:52 am, Ed Wilson via groups.io wrote:
I have been unable to install the latest version of JTAlert under Windows 10 with the latest update. I have attached screen shots of the errors that I encounter


Ed, K0KC

Have you installed the .NET 5 Desktop Runtime?

de Laurie VK3AMA


locked Re: icon messaging #FT8

HamApps Support (VK3AMA)
 

On 14/04/2021 1:54 am, f8nhf wrote:
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

The "Online for messaging" icon (star) size is tied to the size of the Lotw/Eqsl flags. They share the same size selector.

   
 
If increasing the flag size to increase the online Star icon is undesirable, that is the flags become too large in order to produce a suitable Star size, let me know I will look inyo adding an independent size control.

de Laurie VK3AMA


locked Re: Same problem as K5VP Kevin

HamApps Support (VK3AMA)
 

On 14/04/2021 2:59 am, WA9WYI Neal wrote:
have the same issue as Kevin, K5VP.  I installed the 32 bit version of .NET5 and have the same errors.  I excluded this file in Windows Defender, but there was no change in operaton.

What windows version? Is it 32bit or 64bit?

Check task manager and see if JTAlertV2.Manager.exe is running. Is it constantly stopping & restarting?

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Slow ADIF import

HamApps Support (VK3AMA)
 

On 14/04/2021 1:41 am, Michael Black via groups.io wrote:
Sometimes this can be sped up dramatically by wrapping the entire import in a transaction

That is already happening.

de Laurie VK3AMA


locked Re: Slow ADIF import

HamApps Support (VK3AMA)
 

On 14/04/2021 1:35 am, John Holmes W9ILY wrote:

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

John,

I neglected to ask in my last message, what sort of import times were you getting with the old JTAlert?

de Laurie VK3AMA


locked Re: Slow ADIF import

HamApps Support (VK3AMA)
 

On 14/04/2021 1:35 am, John Holmes W9ILY wrote:

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


John,

I am very surprised. This new version should be faster.

Please send me direct your FULL04012021.ADI file and I will test and compare my results with your published results.

de Laurie VK3AMA


locked JTAlert Will Not Install

Ed Wilson
 

I have been unable to install the latest version of JTAlert under Windows 10 with the latest update. I have attached screen shots of the errors that I encounter


Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: JTAlert 2.50.0 Upgrade help needed

Fred Roberts
 

Bill.....
      As I did, you may have installed the wrong version of .Net. The problems you described are exactly what I experienced. I had to go to remove programs, search by date, and remove .Net, then go back to the JTalert installation website, click the link provided, and then install the correct version of .Net. The x86 version is for 32 bit versions of Windows, the x64 is for 64 bit versions of Windows.
Hope this helps.
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 1:09 PM Bill Rogers <k2ter@...> wrote:
I upgraded JTAlert to 2.50.0 from 2.16.10 (I think) for use with WSJT-X.  After the install the Callsign Window and others like "About" don't come up when selected. I am also getting an Unable to communicate with the WSJT-X process: UDP Port 2237 IP Address 127.0.0.1. 

I did not modify my setup after the installation and it appears WSJT-X is still set up to use port 2237.

Is there a remedy or something to try?

Is there a way to go back to the older version safely?

Thanks,
Bill K2TER


locked Re: 2.50.0 with WSJT-X 2.3.1 crashes

Ray, W4BYG <w4byg@...>
 

Are you configured for a "multicast" address from WSJT-X to your clients?
Ray, W4BYG

On 4/13/2021 14:56, John, DK9JC / AK9JC wrote:

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.


-- 
They say a smart person learns from their mistakes.  A
wise person learns from the mistakes of others.

Virus-free. www.avg.com


locked JTAlert 2.50.0 Upgrade help needed

Bill Rogers
 

I upgraded JTAlert to 2.50.0 from 2.16.10 (I think) for use with WSJT-X.  After the install the Callsign Window and others like "About" don't come up when selected. I am also getting an Unable to communicate with the WSJT-X process: UDP Port 2237 IP Address 127.0.0.1. 

I did not modify my setup after the installation and it appears WSJT-X is still set up to use port 2237.

Is there a remedy or something to try?

Is there a way to go back to the older version safely?

Thanks,
Bill K2TER

3481 - 3500 of 37312