Date   

locked WSJT will not load

Jim Denneny
 

Today.  JTAlert (latest version) will not load.  WSJT running latest Beta.  Reboot does not fix.  WSJT has been running OK until today.  Known issue? - Jim K7EG


locked JT alert / HRD logging issues.

F4HJO Jerome
 

Hello,

I was using WSJT-Z version 2.0.1 with JT ALERT version 2.13.10, the logging on HRD (the last one) was done well.

I wanted to make the updates.
I installed the latest version of WSJT-Z (2.2.1) and JT ALERT (2.16.17).


When I run wsjt-z in auto-cq and jt alert, the first qso (2 or 3) are done and go into the HRD logbook.
And then, the qso do not migrate in the log. The wsjt "log qso" window opens well and closes quickly (as always), but nothing.
I have to restart jtalert to make it work again, but the problem starts again afterwards.

Have you ever encountered this problem ?

regards.

73, Jérôme F4HJO


locked wsjt group

Joe - W9RF
 

Sorry if this is not quite on topic but is WSJT group working?
Since this group has most members in WSJT I just thought I would ask


73,

W9RF - Joe


locked Re: JTALERT - "pre-loading" worked callsigns

Steve Roth - AD4K
 

Thanks for reminding me.  So many choices. 73

Mobile

On Jan 8, 2021, at 17:26, Michael Black via groups.io <mdblack98@...> wrote:


It's up to you....

Inline image
Mike W9MDB






On Friday, January 8, 2021, 04:23:10 PM CST, Steve Roth <ad4k.steven@...> wrote:


Okay, after some monitoring I need to ask an important question - Is JTALERT "smart enough" to differentiate my contacts as to band and mode?  Example, say I worked a station on 40M on FT8.  Later I worked the same station on 40M FT4.  Will it show that station as "B4" or not?

Basically, I tried in my "truth test" to prove that my uploading of the ADI file of previous QSO's would match my logging up for "B4" purposes.  I looked for a contact to prove to myself that JTALERT was NOT going to indicate "B4" if it was on the same band and same mode.  I could not find any.

Okay, I think that I have used enough of your valuable time.  I like JTALERT and it is a great help in filtering through the digital stuff so I can pay attention to what I really need.  Thanks so much for your patience.

Regards, Steve   - AD4K - Central Florida





On Thu, Jan 7, 2021 at 10:32 AM Steve Roth via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
I am doing a "truth test" to determine if my file worked.  So, I will let you know after I monitor the situation.  I really appreciate your quick help.  Regards, Steve  AD4K


On Wed, Jan 6, 2021 at 8:55 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 7/01/2021 12:40 pm, Steve Roth wrote:
> Unfortunately, it did not work. I used my two-month log entries from
> HRD, and used that to create the new "B4" adif per the app, which I
> loaded.  I did several tests to see if old qso's would show up as
> "B4", but they did not.

There will likely be something unusual with the ADIF file you used. Send
it to me direct and I will test it.
Send to  vk3ama.ham.apps [at] gmail.com

Also , 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: Recurring JTAlert crash

gksmith_1
 

On Fri, Jan 8, 2021 at 01:58 PM, gksmith_1 wrote:
On Fri, Jan 8, 2021 at 12:58 PM, HamApps Support (VK3AMA) wrote:
On 9/01/2021 7:27 am, gksmith_1 wrote:
Good afternoon,

I have a bit of a mystery that I have not been able to solve.

This may not be the proper place for this query, but since it is JTAlert that I can no longer make run, I thought that I would start here.

I have used WSJT-X, JTAlert and DX Keeper for a number of years now without any issues at all.

Now, however, I have a situation that I have NOT, using all of the search features of the forum, been able to discover a cure for.

I had been using WSJTX-2.3.0-rc2 along with JTAlert 2.16.17 and things were operating very well.

I updated WSJT-X to version 2.3.0-rc3 and everything stopped working at that point.

By that I mean that I did as normal, and started JTAlert which, though the auto-start feature starts WSJT-X and DX Keeper, as it always has, but this time JTAlert appeared on the screen, and after about 3 seconds, JTAlert vanished off the screen.

I still had the WSJT-X window and waterfall and the JTAlert Decodes window which had opened on my desktop, but without any functionality of JTAlert.

I can shutdown WSJT-X and DX Keeper and the JTAlert Decodes window and try the start process again and again, always failing in the same manner.

Also the computer has been rebooted probably a dozen times during my attempts to get this fixed, including several shutdown, remove power from the computer, hold the power button to drain the capacitors, in other words, everything that I could think to do to remove residual bad information before the next attempt.

I checked Task Manager, and no listing for JTAlert. Only JTAlertV2Manager.exe was listed, and it was in the Background Processes area.

When JTAlert tries to start, the title line of JTAlert shows as follows




Then, for just a split second before it vanishes I get the following title bar:




If I am quick enough on the mouse, and can click on the Settings drop down menu, I can get the Manage Settings dialog to open. At this point the JTAlert window will be locked to my desktop until I close the Settings Window.

If I go, in the Settings Window to the Program Updates, it will say "Error downloading data"  for each of the 3 programs.

After closing the Settings Window, JTAlert vanishes.

I have a much longer description that I could have sent, but figured that I would start with something smaller to see if I could get a solution with less bandwidth.

As a point of information, my radio is on before I start WSJT-X, JTAlert and DX Keeper.

I have a Core i7 computer running at 3.2 GHz with 16 GB of RAM, and a solid state 100 GB drive with 12.5 GB of free space and my operating system is Windows 10 Pro, so I don't believe that it is for lack of horsepower that this is happening.

Thanks in advance for any help that you can give me.

73 de WA3ZSC - Jerry


Jerry,

The WSJT-X update to rc3 should have no effect.

If JTAlert is not presenting an error window, than it is unlikely it is closing due to a code failure, more likely it is being deliberately closed (killed). My guess is your Protection software (what do you use?) may be interfering. With the Decodes.exe and JTAlertV2.Manager.exe still running that indicates that JTAlert is being forcibly closed either due to error or by a 3rd party. Both will need to be killed off before trying to start JTAlert again.

A possibility is that WSJT-X is set to run as Administrator (for which there is no normal need) and your Protection software is killing JTAlert due to its interaction with an elevated process due to a permissions mismatch. Check the properties of the wsjtx.exe file to see if you have set it to run with elevated privileges (set to run as administrator), if it is turn that off.

Worth trying is disabling the auto-starting of WSJT-X by JTAlert and manually starting WSJT-X before starting JTAlert. If you can't get into the JTAlert Settings window before it closes to disable your auto-starts, you can disable the autostart operation by using the "/noautostarts" command line parameter (without the quotes) when starting JTAlert, you will need to create a copy of your JTAlert shortcut and add that parameter. eg.
   

Does JTAlert remain running if it is not auto-starting WSJT-X?

Let us know how you get on with this.

de Laurie VK3AMA

Hi Laurie,

Thank you for the quick reply.

I will try to answer your questions. If I miss something, remind me again to jog my memory.

1.Sometimes JTAlert will present an "Undeclared Variable" error, which I know from other posts that you have replied to is an impossibility, other times, no error message at all, it just vanishes.

2. I tried starting JTAlert without starting WSJT-X and it will sit there waiting for WSJT-X for at least 5 minutes, and does not crash, just patiently waits fore me to start WSJT-X.

3. I did check the Compatibility tab of the Properties of both WSJTX.exe and JTAlert.exe (both the EXE file in File Explorer, and the shortcut on my desktop) and none of them are set for "Run as Administrator"

4. My protection software is ESET Internet Security and I have tried to run WSJT-X and JTAlert with ESET disabled, at least as disabled as I am able to determine from its dashboard controls.

5. Yes, I have disabled the auto-start part of JTAlert and it does not make any difference.

6. I did try to manually start WSJT-X and waited until it had made a connection to my radio so that there was a CAT connection that worked, and this has always been the case.

As a point of interest, the inability of JTAlert to be able to check on program updates when it tries to start would kind of suggest to me that there is a permission problem between JTAlert and the communications (networking) part of my computer. I am sure that this is not the fault of your program, but at the same time it is not something that I would know how to check.

Just about the time that I filed the first request I tried to update my Meinberg software for time keeping and the computer refused to let me do that. So after some internet searching I found something that told me that something was corrupted in my user profile with permissions, so I changed my password for Windows 10 and restarted the computer, after which I was able to update the Meinberg software.  (Lots of computer reboots here again today)

But still, when trying to start JTAlert, I still get about 3 seconds of the JTAlert window, and then Poof, it vanishes.....

And another question, I have almost no experience with replying to the forum, so for this message I highlighted the previous message's text before pressing Reply. Is this the correct way to do it or am I missing something.  I have not found good instructions in this matter.

Thanks for all your help.

73 de WA3ZSC- Jerry


Hi again Laurie,

For what it is worth, here is the listing from the help file About JTAlert

JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X   v2.2.2   by K1JT, G4WJS, and K9AN
WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"
WSJT-X   --rig-name   :
WSJT-X Config File    : C:\Users\gksmi\AppData\Local\WSJT-X\WSJT-X.ini

==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 63575 64553
JTAlertV2.Manager.exe : 54301 54302
JTAlertV2.Decodes.exe :


==================================================
JTAlertV2.Manager (2.16.14.0) status
(2021-01-09 00:52:08 utc)
--------------------------------------------------
NET Framework    : .NET Framework 4.8.4300.0
CLR Version      : 4.0.30319.42000
--------------------------------------------------
UDP Router       : Initialized : NO
Audio            : Initialized : NO
BandData         : Initialized : NO
Text Msgs        : Initialized : NO
HamSpots         : Initialized : NO
QRZ Xml          : Initialized : NO
HamQth Xml       : Initialized : NO
QRZ Log          : Initialized : NO
HamQth Log       : Initialized : NO
ClubLog Log      : Initialized : NO
Eqsl Log         : Initialized : NO
HrdLog Log       : Initialized : NO
DXLab DDE        : Initialized : NO
User Alert       : Initialized : NO
Updates Chk      : Initialized : NO
Maintenance      : Initialized : NO

And also, here is an error that popped up this time:



I know  that the error message is a mistake, probably by Windows, but maybe the About information will give you a hint.

Thanks again,

73 de WA3ZSC - Jerry


locked Re: JTALERT - "pre-loading" worked callsigns

Michael Black
 

It's up to you....

Inline image
Mike W9MDB






On Friday, January 8, 2021, 04:23:10 PM CST, Steve Roth <ad4k.steven@...> wrote:


Okay, after some monitoring I need to ask an important question - Is JTALERT "smart enough" to differentiate my contacts as to band and mode?  Example, say I worked a station on 40M on FT8.  Later I worked the same station on 40M FT4.  Will it show that station as "B4" or not?

Basically, I tried in my "truth test" to prove that my uploading of the ADI file of previous QSO's would match my logging up for "B4" purposes.  I looked for a contact to prove to myself that JTALERT was NOT going to indicate "B4" if it was on the same band and same mode.  I could not find any.

Okay, I think that I have used enough of your valuable time.  I like JTALERT and it is a great help in filtering through the digital stuff so I can pay attention to what I really need.  Thanks so much for your patience.

Regards, Steve   - AD4K - Central Florida





On Thu, Jan 7, 2021 at 10:32 AM Steve Roth via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
I am doing a "truth test" to determine if my file worked.  So, I will let you know after I monitor the situation.  I really appreciate your quick help.  Regards, Steve  AD4K


On Wed, Jan 6, 2021 at 8:55 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 7/01/2021 12:40 pm, Steve Roth wrote:
> Unfortunately, it did not work. I used my two-month log entries from
> HRD, and used that to create the new "B4" adif per the app, which I
> loaded.  I did several tests to see if old qso's would show up as
> "B4", but they did not.

There will likely be something unusual with the ADIF file you used. Send
it to me direct and I will test it.
Send to  vk3ama.ham.apps [at] gmail.com

Also , 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: JTALERT - "pre-loading" worked callsigns

Steve Roth - AD4K
 

Okay, after some monitoring I need to ask an important question - Is JTALERT "smart enough" to differentiate my contacts as to band and mode?  Example, say I worked a station on 40M on FT8.  Later I worked the same station on 40M FT4.  Will it show that station as "B4" or not?

Basically, I tried in my "truth test" to prove that my uploading of the ADI file of previous QSO's would match my logging up for "B4" purposes.  I looked for a contact to prove to myself that JTALERT was NOT going to indicate "B4" if it was on the same band and same mode.  I could not find any.

Okay, I think that I have used enough of your valuable time.  I like JTALERT and it is a great help in filtering through the digital stuff so I can pay attention to what I really need.  Thanks so much for your patience.

Regards, Steve   - AD4K - Central Florida





On Thu, Jan 7, 2021 at 10:32 AM Steve Roth via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
I am doing a "truth test" to determine if my file worked.  So, I will let you know after I monitor the situation.  I really appreciate your quick help.  Regards, Steve  AD4K


On Wed, Jan 6, 2021 at 8:55 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 7/01/2021 12:40 pm, Steve Roth wrote:
> Unfortunately, it did not work. I used my two-month log entries from
> HRD, and used that to create the new "B4" adif per the app, which I
> loaded.  I did several tests to see if old qso's would show up as
> "B4", but they did not.

There will likely be something unusual with the ADIF file you used. Send
it to me direct and I will test it.
Send to  vk3ama.ham.apps [at] gmail.com

Also , 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: Recurring JTAlert crash

gksmith_1
 

On Fri, Jan 8, 2021 at 12:58 PM, HamApps Support (VK3AMA) wrote:
On 9/01/2021 7:27 am, gksmith_1 wrote:
Good afternoon,

I have a bit of a mystery that I have not been able to solve.

This may not be the proper place for this query, but since it is JTAlert that I can no longer make run, I thought that I would start here.

I have used WSJT-X, JTAlert and DX Keeper for a number of years now without any issues at all.

Now, however, I have a situation that I have NOT, using all of the search features of the forum, been able to discover a cure for.

I had been using WSJTX-2.3.0-rc2 along with JTAlert 2.16.17 and things were operating very well.

I updated WSJT-X to version 2.3.0-rc3 and everything stopped working at that point.

By that I mean that I did as normal, and started JTAlert which, though the auto-start feature starts WSJT-X and DX Keeper, as it always has, but this time JTAlert appeared on the screen, and after about 3 seconds, JTAlert vanished off the screen.

I still had the WSJT-X window and waterfall and the JTAlert Decodes window which had opened on my desktop, but without any functionality of JTAlert.

I can shutdown WSJT-X and DX Keeper and the JTAlert Decodes window and try the start process again and again, always failing in the same manner.

Also the computer has been rebooted probably a dozen times during my attempts to get this fixed, including several shutdown, remove power from the computer, hold the power button to drain the capacitors, in other words, everything that I could think to do to remove residual bad information before the next attempt.

I checked Task Manager, and no listing for JTAlert. Only JTAlertV2Manager.exe was listed, and it was in the Background Processes area.

When JTAlert tries to start, the title line of JTAlert shows as follows




Then, for just a split second before it vanishes I get the following title bar:




If I am quick enough on the mouse, and can click on the Settings drop down menu, I can get the Manage Settings dialog to open. At this point the JTAlert window will be locked to my desktop until I close the Settings Window.

If I go, in the Settings Window to the Program Updates, it will say "Error downloading data"  for each of the 3 programs.

After closing the Settings Window, JTAlert vanishes.

I have a much longer description that I could have sent, but figured that I would start with something smaller to see if I could get a solution with less bandwidth.

As a point of information, my radio is on before I start WSJT-X, JTAlert and DX Keeper.

I have a Core i7 computer running at 3.2 GHz with 16 GB of RAM, and a solid state 100 GB drive with 12.5 GB of free space and my operating system is Windows 10 Pro, so I don't believe that it is for lack of horsepower that this is happening.

Thanks in advance for any help that you can give me.

73 de WA3ZSC - Jerry


Jerry,

The WSJT-X update to rc3 should have no effect.

If JTAlert is not presenting an error window, than it is unlikely it is closing due to a code failure, more likely it is being deliberately closed (killed). My guess is your Protection software (what do you use?) may be interfering. With the Decodes.exe and JTAlertV2.Manager.exe still running that indicates that JTAlert is being forcibly closed either due to error or by a 3rd party. Both will need to be killed off before trying to start JTAlert again.

A possibility is that WSJT-X is set to run as Administrator (for which there is no normal need) and your Protection software is killing JTAlert due to its interaction with an elevated process due to a permissions mismatch. Check the properties of the wsjtx.exe file to see if you have set it to run with elevated privileges (set to run as administrator), if it is turn that off.

Worth trying is disabling the auto-starting of WSJT-X by JTAlert and manually starting WSJT-X before starting JTAlert. If you can't get into the JTAlert Settings window before it closes to disable your auto-starts, you can disable the autostart operation by using the "/noautostarts" command line parameter (without the quotes) when starting JTAlert, you will need to create a copy of your JTAlert shortcut and add that parameter. eg.
   

Does JTAlert remain running if it is not auto-starting WSJT-X?

Let us know how you get on with this.

de Laurie VK3AMA

Hi Laurie,

Thank you for the quick reply.

I will try to answer your questions. If I miss something, remind me again to jog my memory.

1.Sometimes JTAlert will present an "Undeclared Variable" error, which I know from other posts that you have replied to is an impossibility, other times, no error message at all, it just vanishes.

2. I tried starting JTAlert without starting WSJT-X and it will sit there waiting for WSJT-X for at least 5 minutes, and does not crash, just patiently waits fore me to start WSJT-X.

3. I did check the Compatibility tab of the Properties of both WSJTX.exe and JTAlert.exe (both the EXE file in File Explorer, and the shortcut on my desktop) and none of them are set for "Run as Administrator"

4. My protection software is ESET Internet Security and I have tried to run WSJT-X and JTAlert with ESET disabled, at least as disabled as I am able to determine from its dashboard controls.

5. Yes, I have disabled the auto-start part of JTAlert and it does not make any difference.

6. I did try to manually start WSJT-X and waited until it had made a connection to my radio so that there was a CAT connection that worked, and this has always been the case.

As a point of interest, the inability of JTAlert to be able to check on program updates when it tries to start would kind of suggest to me that there is a permission problem between JTAlert and the communications (networking) part of my computer. I am sure that this is not the fault of your program, but at the same time it is not something that I would know how to check.

Just about the time that I filed the first request I tried to update my Meinberg software for time keeping and the computer refused to let me do that. So after some internet searching I found something that told me that something was corrupted in my user profile with permissions, so I changed my password for Windows 10 and restarted the computer, after which I was able to update the Meinberg software.  (Lots of computer reboots here again today)

But still, when trying to start JTAlert, I still get about 3 seconds of the JTAlert window, and then Poof, it vanishes.....

And another question, I have almost no experience with replying to the forum, so for this message I highlighted the previous message's text before pressing Reply. Is this the correct way to do it or am I missing something.  I have not found good instructions in this matter.

Thanks for all your help.

73 de WA3ZSC- Jerry


locked Re: Recurring JTAlert crash

gksmith_1
 

Hi Tom,

Thanks for the suggestion. 

I neglected to mention however, that I have already tried that, in fact I uninstalled rc-3 and went back and installed version 2.2.2 of WSJT-X and also backed up to version 2.16.14 of JTAlert, to no avail.

Appreciate the suggestion to send it to the WSJT-X Forum as well,

I will do that.

Thanks,

73 de WA3ZSC - Jerry


locked Re: Recurring JTAlert crash

HamApps Support (VK3AMA)
 

On 9/01/2021 7:27 am, gksmith_1 wrote:
Good afternoon,

I have a bit of a mystery that I have not been able to solve.

This may not be the proper place for this query, but since it is JTAlert that I can no longer make run, I thought that I would start here.

I have used WSJT-X, JTAlert and DX Keeper for a number of years now without any issues at all.

Now, however, I have a situation that I have NOT, using all of the search features of the forum, been able to discover a cure for.

I had been using WSJTX-2.3.0-rc2 along with JTAlert 2.16.17 and things were operating very well.

I updated WSJT-X to version 2.3.0-rc3 and everything stopped working at that point.

By that I mean that I did as normal, and started JTAlert which, though the auto-start feature starts WSJT-X and DX Keeper, as it always has, but this time JTAlert appeared on the screen, and after about 3 seconds, JTAlert vanished off the screen.

I still had the WSJT-X window and waterfall and the JTAlert Decodes window which had opened on my desktop, but without any functionality of JTAlert.

I can shutdown WSJT-X and DX Keeper and the JTAlert Decodes window and try the start process again and again, always failing in the same manner.

Also the computer has been rebooted probably a dozen times during my attempts to get this fixed, including several shutdown, remove power from the computer, hold the power button to drain the capacitors, in other words, everything that I could think to do to remove residual bad information before the next attempt.

I checked Task Manager, and no listing for JTAlert. Only JTAlertV2Manager.exe was listed, and it was in the Background Processes area.

When JTAlert tries to start, the title line of JTAlert shows as follows




Then, for just a split second before it vanishes I get the following title bar:




If I am quick enough on the mouse, and can click on the Settings drop down menu, I can get the Manage Settings dialog to open. At this point the JTAlert window will be locked to my desktop until I close the Settings Window.

If I go, in the Settings Window to the Program Updates, it will say "Error downloading data"  for each of the 3 programs.

After closing the Settings Window, JTAlert vanishes.

I have a much longer description that I could have sent, but figured that I would start with something smaller to see if I could get a solution with less bandwidth.

As a point of information, my radio is on before I start WSJT-X, JTAlert and DX Keeper.

I have a Core i7 computer running at 3.2 GHz with 16 GB of RAM, and a solid state 100 GB drive with 12.5 GB of free space and my operating system is Windows 10 Pro, so I don't believe that it is for lack of horsepower that this is happening.

Thanks in advance for any help that you can give me.

73 de WA3ZSC - Jerry


Jerry,

The WSJT-X update to rc3 should have no effect.

If JTAlert is not presenting an error window, than it is unlikely it is closing due to a code failure, more likely it is being deliberately closed (killed). My guess is your Protection software (what do you use?) may be interfering. With the Decodes.exe and JTAlertV2.Manager.exe still running that indicates that JTAlert is being forcibly closed either due to error or by a 3rd party. Both will need to be killed off before trying to start JTAlert again.

A possibility is that WSJT-X is set to run as Administrator (for which there is no normal need) and your Protection software is killing JTAlert due to its interaction with an elevated process due to a permissions mismatch. Check the properties of the wsjtx.exe file to see if you have set it to run with elevated privileges (set to run as administrator), if it is turn that off.

Worth trying is disabling the auto-starting of WSJT-X by JTAlert and manually starting WSJT-X before starting JTAlert. If you can't get into the JTAlert Settings window before it closes to disable your auto-starts, you can disable the autostart operation by using the "/noautostarts" command line parameter (without the quotes) when starting JTAlert, you will need to create a copy of your JTAlert shortcut and add that parameter. eg.
   

Does JTAlert remain running if it is not auto-starting WSJT-X?

Let us know how you get on with this.

de Laurie VK3AMA


locked Re: Recurring JTAlert crash

Tom Job
 

Just a thought….uninstall the rc-3 and go back to rc-2. There’s obviously some kind of bad interaction between it and JTAlert.  I would also send the same email to the WSJT-X group.  With beta software there are always bound to be problems.  The developer(s) would surely like your report.

 

73….GL

 

Tom VE3II

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of gksmith_1
Sent: January 8, 2021 15:27
To: Support@HamApps.groups.io
Subject: [HamApps] Recurring JTAlert crash

 

Good afternoon,

I have a bit of a mystery that I have not been able to solve.

This may not be the proper place for this query, but since it is JTAlert that I can no longer make run, I thought that I would start here.

I have used WSJT-X, JTAlert and DX Keeper for a number of years now without any issues at all.

Now, however, I have a situation that I have NOT, using all of the search features of the forum, been able to discover a cure for.

I had been using WSJTX-2.3.0-rc2 along with JTAlert 2.16.17 and things were operating very well.

I updated WSJT-X to version 2.3.0-rc3 and everything stopped working at that point.

By that I mean that I did as normal, and started JTAlert which, though the auto-start feature starts WSJT-X and DX Keeper, as it always has, but this time JTAlert appeared on the screen, and after about 3 seconds, JTAlert vanished off the screen.

I still had the WSJT-X window and waterfall and the JTAlert Decodes window which had opened on my desktop, but without any functionality of JTAlert.

I can shutdown WSJT-X and DX Keeper and the JTAlert Decodes window and try the start process again and again, always failing in the same manner.

Also the computer has been rebooted probably a dozen times during my attempts to get this fixed, including several shutdown, remove power from the computer, hold the power button to drain the capacitors, in other words, everything that I could think to do to remove residual bad information before the next attempt.

I checked Task Manager, and no listing for JTAlert. Only JTAlertV2Manager.exe was listed, and it was in the Background Processes area.

When JTAlert tries to start, the title line of JTAlert shows as follows




Then, for just a split second before it vanishes I get the following title bar:




If I am quick enough on the mouse, and can click on the Settings drop down menu, I can get the Manage Settings dialog to open. At this point the JTAlert window will be locked to my desktop until I close the Settings Window.

If I go, in the Settings Window to the Program Updates, it will say "Error downloading data"  for each of the 3 programs.

After closing the Settings Window, JTAlert vanishes.

I have a much longer description that I could have sent, but figured that I would start with something smaller to see if I could get a solution with less bandwidth.

As a point of information, my radio is on before I start WSJT-X, JTAlert and DX Keeper.

I have a Core i7 computer running at 3.2 GHz with 16 GB of RAM, and a solid state 100 GB drive with 12.5 GB of free space and my operating system is Windows 10 Pro, so I don't believe that it is for lack of horsepower that this is happening.

Thanks in advance for any help that you can give me.

73 de WA3ZSC - Jerry




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Recurring JTAlert crash

gksmith_1
 

Good afternoon,

I have a bit of a mystery that I have not been able to solve.

This may not be the proper place for this query, but since it is JTAlert that I can no longer make run, I thought that I would start here.

I have used WSJT-X, JTAlert and DX Keeper for a number of years now without any issues at all.

Now, however, I have a situation that I have NOT, using all of the search features of the forum, been able to discover a cure for.

I had been using WSJTX-2.3.0-rc2 along with JTAlert 2.16.17 and things were operating very well.

I updated WSJT-X to version 2.3.0-rc3 and everything stopped working at that point.

By that I mean that I did as normal, and started JTAlert which, though the auto-start feature starts WSJT-X and DX Keeper, as it always has, but this time JTAlert appeared on the screen, and after about 3 seconds, JTAlert vanished off the screen.

I still had the WSJT-X window and waterfall and the JTAlert Decodes window which had opened on my desktop, but without any functionality of JTAlert.

I can shutdown WSJT-X and DX Keeper and the JTAlert Decodes window and try the start process again and again, always failing in the same manner.

Also the computer has been rebooted probably a dozen times during my attempts to get this fixed, including several shutdown, remove power from the computer, hold the power button to drain the capacitors, in other words, everything that I could think to do to remove residual bad information before the next attempt.

I checked Task Manager, and no listing for JTAlert. Only JTAlertV2Manager.exe was listed, and it was in the Background Processes area.

When JTAlert tries to start, the title line of JTAlert shows as follows




Then, for just a split second before it vanishes I get the following title bar:




If I am quick enough on the mouse, and can click on the Settings drop down menu, I can get the Manage Settings dialog to open. At this point the JTAlert window will be locked to my desktop until I close the Settings Window.

If I go, in the Settings Window to the Program Updates, it will say "Error downloading data"  for each of the 3 programs.

After closing the Settings Window, JTAlert vanishes.

I have a much longer description that I could have sent, but figured that I would start with something smaller to see if I could get a solution with less bandwidth.

As a point of information, my radio is on before I start WSJT-X, JTAlert and DX Keeper.

I have a Core i7 computer running at 3.2 GHz with 16 GB of RAM, and a solid state 100 GB drive with 12.5 GB of free space and my operating system is Windows 10 Pro, so I don't believe that it is for lack of horsepower that this is happening.

Thanks in advance for any help that you can give me.

73 de WA3ZSC - Jerry



locked Re: JTALERT - "pre-loading" worked callsigns

Steve Roth - AD4K
 

I am doing a "truth test" to determine if my file worked.  So, I will let you know after I monitor the situation.  I really appreciate your quick help.  Regards, Steve  AD4K


On Wed, Jan 6, 2021 at 8:55 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 7/01/2021 12:40 pm, Steve Roth wrote:
> Unfortunately, it did not work. I used my two-month log entries from
> HRD, and used that to create the new "B4" adif per the app, which I
> loaded.  I did several tests to see if old qso's would show up as
> "B4", but they did not.

There will likely be something unusual with the ADIF file you used. Send
it to me direct and I will test it.
Send to  vk3ama.ham.apps [at] gmail.com

Also , 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: Can decoded callsigns be sorted by priority?

Jim Reisert AD1C
 

Long answer... Any sort of callsign sorting will require that all decodes have been processed and delivered by WSJT-X before JTAlert can produce a sorted display. That could be several seconds of dead (non-display) time depending on you PC capability and how busy the Band.

Understood.

Using the Decodes window just means another pane of callsigns I have to watch.  Two is more than I want, IMO.  I do have the JT Alert coloring of the WSJT-X callsigns.  That's my primary way of finding those higher-priority calls (scrolling backward in WSJT-X).

--
Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us


locked Re: WSJT-X and JT Alert Conflicting

Michael Black
 

#1 Ensure that there are no green icons on the rig audio device in "Sound Control Panel".
Should look like this:
Inline image
And not like this:
Inline image
If you have green icons on your rig audio device then right-click your computer speaker device and select these two items.
The green icons on your rig audio device will disappear.
Inline image
#2 Do the same for both Playback (the really important one) and Recording (not so important and actually optional or may not be able to be set if you don't have a mic in your computer).

#3 Make sure WSJT-X audio devices are pointing to rig audio (e.g. USB Audio CODEC) and not "Default".  

#4 Get some decent chokes (not from Ebay please) and put them on your USB cable on both sides.  Remember all cables are antennas.

RFI in the shack can be pretty subtle to really ugly.  There can be just enough to mess with the USB protocol or enough to mess with the USB 5V power which will cause device resets.  Either one can affect any program talking to the USB audio or CAT control.


Mike W9MDB




On Thursday, January 7, 2021, 12:44:06 AM CST, Scott Armstrong <aa5am@...> wrote:


FWIW... I have experienced the same thing Dave K5HC is reporting.

WSJT-X keys the radio and there is no audio (tones generated) or RF power output.  The problem is intermittent and occurs infrequently.
The problem does not appear to be frequency dependent as I have had it occur on various bands from 160m to 6m and possibly 2m which is a totally different radio/configuration.

My work around has been to 'Halt' WSJT-X and then 'Enable" again. Then there is audio and RF power output.
The issue is not RFI related as there is no RF being generated because of the lack of tones.

My configuration is totally different from what Dave has:

WSJT-X  v2.2.2 or v2.3.0-rcX and past versions
JTA currently 2.16.17 but has also occurred on past versions
IC-IC756ProII 
MFJ-1275 SCI
ASUS XonarU5 (external USB sound card)

HP xw4400 workstation  dual core 2.13 GHz  6GB RAM
Win7 Pro SP1


I have never considered JTA to be the issue but will try killing it the next time the problem occurs and see what the result is.
My gut feel is that it's a race condition/resource issue with WSJT-X.

73,
Scott AA5AM



On Wed, Jan 6, 2021 at 10:21 PM Jamie GOLLY <k6ngn@...> wrote:
Hi Dave, I have a 991A as well with no issues running WSJT-X and JT Alert. This is my set up on Win 10. 

Best of luck

Jamie
K6NGN 




On Jan 6, 2021, at 8:16 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 7/01/2021 2:18 am, K5HC@... wrote:

I am having a random problem with WSJT-X and JT Alert apparently conflicting somehow.  First, I little information about my setup.  I am using a Yaesu FT-991A which has an internal sound card and is connected to my Windows 10 computer via a USB connection.  When I run WSJT-X all by itself, it seems to work flawlessly.  However when I run it with JT Alert, something happens randomly that on a transmit cycle, my transmitter will key up but there is no output power showing on my wattmeter.  If I close JT Alert, sometimes the problem is solved and other times I have to shut down WSJT-X as well to get things working again.  BTW, I have Sound OFF in JT Alert if that makes a difference.

I am running WSJT-X v.2.2.2 and JT Alert 2.16.17

 

JT Alert is a great program, just wish I could use it with WSJT-X reliably.  Any suggestions for a fix would be greatly appreciated.

 

Thanks and 73,

Dave

K5HC


A fix is hard to suggest as you have provided minimal data about your operating environment.
What are your PC specs, number of CPU cores, CPU speed, installed Ram, Windows version?

It is very unlikely that JTAlert is directly influencing your transmissions.

You indicated that it is random whether you experience loss of TX suggesting to me that it is likely an RFI issue. USB controlled transceivers tend to be susceptible to RF in the shack. Try running into a dummy load, does the loss of TX still occur?

Another possibility is that your PC is under-resourced. What sort of CPU usage numbers is taskmanager showing? How late is WSJT-X in finishing processing period decodes, does it run into the new period?

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

de Laurie VK3AMA


Attachments:


locked Re: WSJT-X and JT Alert Conflicting

Scott Armstrong
 

FWIW... I have experienced the same thing Dave K5HC is reporting.

WSJT-X keys the radio and there is no audio (tones generated) or RF power output.  The problem is intermittent and occurs infrequently.
The problem does not appear to be frequency dependent as I have had it occur on various bands from 160m to 6m and possibly 2m which is a totally different radio/configuration.

My work around has been to 'Halt' WSJT-X and then 'Enable" again. Then there is audio and RF power output.
The issue is not RFI related as there is no RF being generated because of the lack of tones.

My configuration is totally different from what Dave has:

WSJT-X  v2.2.2 or v2.3.0-rcX and past versions
JTA currently 2.16.17 but has also occurred on past versions
IC-IC756ProII 
MFJ-1275 SCI
ASUS XonarU5 (external USB sound card)

HP xw4400 workstation  dual core 2.13 GHz  6GB RAM
Win7 Pro SP1


I have never considered JTA to be the issue but will try killing it the next time the problem occurs and see what the result is.
My gut feel is that it's a race condition/resource issue with WSJT-X.

73,
Scott AA5AM



On Wed, Jan 6, 2021 at 10:21 PM Jamie GOLLY <k6ngn@...> wrote:
Hi Dave, I have a 991A as well with no issues running WSJT-X and JT Alert. This is my set up on Win 10. 

Best of luck

Jamie
K6NGN 




On Jan 6, 2021, at 8:16 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 7/01/2021 2:18 am, K5HC@... wrote:

I am having a random problem with WSJT-X and JT Alert apparently conflicting somehow.  First, I little information about my setup.  I am using a Yaesu FT-991A which has an internal sound card and is connected to my Windows 10 computer via a USB connection.  When I run WSJT-X all by itself, it seems to work flawlessly.  However when I run it with JT Alert, something happens randomly that on a transmit cycle, my transmitter will key up but there is no output power showing on my wattmeter.  If I close JT Alert, sometimes the problem is solved and other times I have to shut down WSJT-X as well to get things working again.  BTW, I have Sound OFF in JT Alert if that makes a difference.

I am running WSJT-X v.2.2.2 and JT Alert 2.16.17

 

JT Alert is a great program, just wish I could use it with WSJT-X reliably.  Any suggestions for a fix would be greatly appreciated.

 

Thanks and 73,

Dave

K5HC


A fix is hard to suggest as you have provided minimal data about your operating environment.
What are your PC specs, number of CPU cores, CPU speed, installed Ram, Windows version?

It is very unlikely that JTAlert is directly influencing your transmissions.

You indicated that it is random whether you experience loss of TX suggesting to me that it is likely an RFI issue. USB controlled transceivers tend to be susceptible to RF in the shack. Try running into a dummy load, does the loss of TX still occur?

Another possibility is that your PC is under-resourced. What sort of CPU usage numbers is taskmanager showing? How late is WSJT-X in finishing processing period decodes, does it run into the new period?

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

de Laurie VK3AMA


Attachments:


locked Re: WSJT-X and JT Alert Conflicting

Jamie GOLLY
 
Edited

Hi Dave, I have a 991A as well with no issues running WSJT-X and JT Alert. This is my set up on Win 10. 
 
Best of luck
 
Jamie
K6NGN 
 
 


 

On Jan 6, 2021, at 8:16 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 7/01/2021 2:18 am, K5HC@... wrote:

I am having a random problem with WSJT-X and JT Alert apparently conflicting somehow.  First, I little information about my setup.  I am using a Yaesu FT-991A which has an internal sound card and is connected to my Windows 10 computer via a USB connection.  When I run WSJT-X all by itself, it seems to work flawlessly.  However when I run it with JT Alert, something happens randomly that on a transmit cycle, my transmitter will key up but there is no output power showing on my wattmeter.  If I close JT Alert, sometimes the problem is solved and other times I have to shut down WSJT-X as well to get things working again.  BTW, I have Sound OFF in JT Alert if that makes a difference.

I am running WSJT-X v.2.2.2 and JT Alert 2.16.17

 

JT Alert is a great program, just wish I could use it with WSJT-X reliably.  Any suggestions for a fix would be greatly appreciated.

 

Thanks and 73,

Dave

K5HC


A fix is hard to suggest as you have provided minimal data about your operating environment.
What are your PC specs, number of CPU cores, CPU speed, installed Ram, Windows version?

It is very unlikely that JTAlert is directly influencing your transmissions.

You indicated that it is random whether you experience loss of TX suggesting to me that it is likely an RFI issue. USB controlled transceivers tend to be susceptible to RF in the shack. Try running into a dummy load, does the loss of TX still occur?

Another possibility is that your PC is under-resourced. What sort of CPU usage numbers is taskmanager showing? How late is WSJT-X in finishing processing period decodes, does it run into the new period?

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

de Laurie VK3AMA



locked Re: WSJT-X and JT Alert Conflicting

HamApps Support (VK3AMA)
 

On 7/01/2021 2:18 am, K5HC@... wrote:

I am having a random problem with WSJT-X and JT Alert apparently conflicting somehow.  First, I little information about my setup.  I am using a Yaesu FT-991A which has an internal sound card and is connected to my Windows 10 computer via a USB connection.  When I run WSJT-X all by itself, it seems to work flawlessly.  However when I run it with JT Alert, something happens randomly that on a transmit cycle, my transmitter will key up but there is no output power showing on my wattmeter.  If I close JT Alert, sometimes the problem is solved and other times I have to shut down WSJT-X as well to get things working again.  BTW, I have Sound OFF in JT Alert if that makes a difference.

I am running WSJT-X v.2.2.2 and JT Alert 2.16.17

 

JT Alert is a great program, just wish I could use it with WSJT-X reliably.  Any suggestions for a fix would be greatly appreciated.

 

Thanks and 73,

Dave

K5HC


A fix is hard to suggest as you have provided minimal data about your operating environment.
What are your PC specs, number of CPU cores, CPU speed, installed Ram, Windows version?

It is very unlikely that JTAlert is directly influencing your transmissions.

You indicated that it is random whether you experience loss of TX suggesting to me that it is likely an RFI issue. USB controlled transceivers tend to be susceptible to RF in the shack. Try running into a dummy load, does the loss of TX still occur?

Another possibility is that your PC is under-resourced. What sort of CPU usage numbers is taskmanager showing? How late is WSJT-X in finishing processing period decodes, does it run into the new period?

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

de Laurie VK3AMA



locked Re: WSJT-X and JT Alert Conflicting

neil_zampella
 

What soundcard do you have JT-Alert pointing to?   I'm not sure that having 'sounds off' stops JT-Alert from accessing the card.

 

Neil, KN3ILZ


locked Re: JTALERT - "pre-loading" worked callsigns

Laurie, VK3AMA
 

On 7/01/2021 12:40 pm, Steve Roth wrote:
Unfortunately, it did not work. I used my two-month log entries from HRD, and used that to create the new "B4" adif per the app, which I loaded.  I did several tests to see if old qso's would show up as "B4", but they did not.
There will likely be something unusual with the ADIF file you used. Send it to me direct and I will test it.
Send to  vk3ama.ham.apps [at] gmail.com

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

de Laurie VK3AMA

4241 - 4260 of 36987