Date   

locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Phil Cooper
 

Hi all,

My thoughts too....
You should be closing the main JTAlert window (the one where you add name, QTH etc).
You should have no need to close any other windows, assuming you have JTAlert set to open what you need.

73 de Phil GU0SUP

-----Original Message-----
From: "Dave Garber" <ve3wej@gmail.com>
Sent: Sunday, 16 May, 2021 15:15
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Closing JTAlert On Windows 10 Pro 64 Bit

must be something which jtalert window are you closing first the
callsigns window, or the main log window ( do this first) maybe you are
closing the wrong one?

Dave Garber
VE3WEJ / VE3IE


On Sun, May 16, 2021 at 9:51 AM Ronald Ford <rjf802@gmail.com> wrote:

Thanks Dave...I did have it checked but for some reason the second window
will not close when I close JT Alert.

Ronnie



locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Dave Garber
 

must be something    which jtalert window are you closing first   the callsigns window, or the main log window ( do this first)   maybe you are closing the wrong one?

Dave Garber
VE3WEJ / VE3IE


On Sun, May 16, 2021 at 9:51 AM Ronald Ford <rjf802@...> wrote:
Thanks Dave...I did have it checked but for some reason the second window will not close when I close JT Alert.  

Ronnie


locked Re: JTAlert 2.50.1 does not receive from WSJT-X - Callsigns, Activity and Band heat windows don't open

Frode Igland
 

UPDATE. ALL OK with v 2.50.1 NOW. 😊
I have now uninstalled JTAlert for the n-th time. Further, I manually cleaned out everything anywhere in the PC named JTalert or HamApps something , including everything in AppData/Local (configuration, logs, session data, etc.). 

Then I power cycled the PC, downloaded and installed JTAlert v2.50.1 and now everything loooks OK. Only the call signs from the latest decoding sequence appear in the Callsigns window and they arrive fast and in an orderly fashion identical to the sequence in the WSJT-X Band Activity window.. The same applies to the Decodes window, with the latest decodes arriving on top of the list.

All is well with v2.50.1. However, I still wonder what in v2.50.1 caused the problems where the Callsigns and Decodes windows showed old and new decodes and repetitions of same in a completely random order and way before and after the end of the decoding sequence.

73, Frode LA6VQ

fre. 14. mai 2021 kl. 13:49 skrev Frode Igland <frodeigland2@...>:

I am sorry for my slow response in a very busy period. I now reply to Laurie's reply in Digest #1460 dated 3 May 2021.

The only thing I did to have v2.50.0 and v2.50.1 installed at the same time, was to install v.2.50.1 in a folder under Program Files, whilst v2.50.0 was installed under Program Files (x86). When opening v2.50.1 I had to select to use  JTAlert with WSJT-X, with JTDX as the alternative. When I first installed v2.50.1, I made a standard installation with default settings, installing it in the Program Files (x86)/Hamapps folder, so the double installation was a very special case just to see if I could notice any differences between the versions, which I didn't.

I followed Laurie's advice to uninstall both versions. All files were deleted by the uninstall, but some folders stuck, so I deleted the remaining folders, as well, leaving no trace of Hamapps or JTALert in the Program Files or the Program Files (x86) folders. The settings under Localappdata were kept. I then made a new installation of JTAlert v2.50.1 with default settings, opened JTAlert v2.50.1,  scanned the logbook to have everything updated. 

The Callsigns window and the Decodes window opened, but regrettably they were just as chaotic as before.

I attach an example with 7 decodes in the WSJT-X Band Activity window, whilst the Callsigns window produced 75 call signs in no particular order, some of which are repetitions from the latest decoded period, whilst others are decoded call signs from random previous periods (identified by different SNR for the same call sign). The Decodes window shows the same lack of order and system, listing old and new decodes in no particlular order.

However, what is listed last in the Callsigns window is listed on the top of the Decodes list, so between the windows the call sign sequence is identical, but it is not linked to the sequence in what has been received form WSJT-X.

The lack of consistency between the latest WSJT-X decodes and JTAlert 2.50.1 makes the Callsigns and Decodes windows useless for selecting calls to work, as the stations.

Everything worked without problems with JTAlert 2.50.0. The problem appeared when I installed v2.50.1, and going back to v2.50.0 did not correct the issue.

The configuration and latest session files have been sent by separate e-mail.

Frode, LA6VQ


locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Ronald Ford
 

I realize the icon is indicating a second instance of JT Alert...but I only use on instance of JT Alert at any given time.  It seems there should be a setting that would prohibit a second instance from starting.

73, Ronald


locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Ronald Ford
 

Thanks Dave...I did have it checked but for some reason the second window will not close when I close JT Alert.  

Ronnie


locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Dave Garber
 

Make sure folllow jtalert is checked.  I beleive it will make the second window close at the same time


On Sun., May 16, 2021, 9:33 a.m. Ronald Ford, <rjf802@...> wrote:
First thank you for the update.  I have been using the new version for some time and the new call display is great.  I do have an issue I'm not sure how to resolve.  When I close JT Alert the program closes like it has in the past...however the Icon shows it is still open in the Task Bar.  I can right click on the icon and close select close and it closes.  It seems like there is a second something opening when I start JT Alert and when I close it it does not close. In previous versions of the software I have not had this issue occur.  

If this has been discussed in the past please forgive my post.  I checked previous posting and saw some post that may have the same issue as me but I was not sure.  I have checked all of the setting on the gear icon and have tried several settings but nothing I tried resolved my issue of the icon not closing on exit.

73, Ronald - W4RJF  


locked Closing JTAlert On Windows 10 Pro 64 Bit

Ronald Ford
 

First thank you for the update.  I have been using the new version for some time and the new call display is great.  I do have an issue I'm not sure how to resolve.  When I close JT Alert the program closes like it has in the past...however the Icon shows it is still open in the Task Bar.  I can right click on the icon and close select close and it closes.  It seems like there is a second something opening when I start JT Alert and when I close it it does not close. In previous versions of the software I have not had this issue occur.  

If this has been discussed in the past please forgive my post.  I checked previous posting and saw some post that may have the same issue as me but I was not sure.  I have checked all of the setting on the gear icon and have tried several settings but nothing I tried resolved my issue of the icon not closing on exit.

73, Ronald - W4RJF  


locked Re: Log deleted by accident

randybuckner
 

No, it is an adi extension. Not changing the header causes WSJT to make another log. Changing the header, WSJT put any new calls in the log, but it won't recognize the other entries when rescanning.

It shouldn't be so hard.


locked Re: CQ for stations not CQing

Dave Garber
 

sounds like filters in jtdx.  I would check in their forum for answer as well.  it may be in jtdx, not jtalert

Dave Garber
VE3WEJ / VE3IE


On Sat, May 15, 2021 at 9:14 AM Steve <steve@...> wrote:
Laurie,

I didn't explain real well.  Callsigns show up green with CQ being announced in JTAlert.  There is no corresponding CQ in JTDX so when clicking on the callsign in JTAlert, nothing happens.  If JTDX is hiding some of its decodes but JTAlert still sees them, any idea why JTDX  doesn't show them?

Thanks for your help.

Steve NA6G


locked Re: Log deleted by accident

Tom Melvin
 

Randy

I suspect its this step


4 - I changed the name of the adi file to wsjtx_log. For instance, the QRZ file exported was kc5rr.166144.20210515191035.adi. I changed the name to wsjtx_log.


Changing the name MAY have renamed the file:  wsjtx_log.166144.20210515191035.adi

When you look at the listing in Open Log Directory does it show the extension?

In the folder there is (in Win 10 anyway) a view option, select it, tick box ‘File Name Extension’ make sure it is ticked - it should then show the FULL name and extension.

Double check the file is wsjtx_log.adi

The header should not matter.

Tom
GM8MJV




On 15 May 2021, at 20:20, randybuckner via groups.io <randybuckner@...> wrote:

Tom, thanks for trying to help. I'll explain step by step what I have tried, so there is no confusion:

1 - I downloaded my QRZ, eQSL, LOTW, and ACLog programs as adi files.

2 - I opened the WSJT File ---> Open Log Directory.

3 - I placed my adi files (one at a time) in the directory.

4 - I changed the name of the adi file to wsjtx_log. For instance, the QRZ file exported was kc5rr.166144.20210515191035.adi. I changed the name to wsjtx_log.

5 - WSJT Settings ----> Colors ----> Rescan ADIF Log

Nothing happens. I'm lost at this point. Do I need to change the header? The header is:
QRZLogbook download for kc5rr
Date: Sat May 15 19:10:35 2021
Bookid: 166144
Records: 17055
<ADIF_VER:5>3.1.1
<PROGRAMID:10>QRZLogbook
<PROGRAMVERSION:3>2.0
<eoh>


locked Re: Log deleted by accident

randybuckner
 

Tom, thanks for trying to help. I'll explain step by step what I have tried, so there is no confusion:

1 - I downloaded my QRZ, eQSL, LOTW, and ACLog programs as adi files.

2 - I opened the WSJT File ---> Open Log Directory.

3 - I placed my adi files (one at a time) in the directory.

4 - I changed the name of the adi file to wsjtx_log. For instance, the QRZ file exported was kc5rr.166144.20210515191035.adi. I changed the name to wsjtx_log.

5 - WSJT Settings ----> Colors ----> Rescan ADIF Log

Nothing happens. I'm lost at this point. Do I need to change the header? The header is:
QRZLogbook download for kc5rr
Date: Sat May 15 19:10:35 2021
Bookid: 166144
Records: 17055
<ADIF_VER:5>3.1.1
<PROGRAMID:10>QRZLogbook
<PROGRAMVERSION:3>2.0
<eoh>


locked Re: Logging

Knud-Erik Kaadner
 

Well, that was it. So letting JTAlert doing the logging solved the problem.
Thanks.


locked Re: CQ for stations not CQing

Steve
 

Laurie,

I didn't explain real well.  Callsigns show up green with CQ being announced in JTAlert.  There is no corresponding CQ in JTDX so when clicking on the callsign in JTAlert, nothing happens.  If JTDX is hiding some of its decodes but JTAlert still sees them, any idea why JTDX  doesn't show them?

Thanks for your help.

Steve NA6G


locked Re: Logging

Ronald Panetta, WB2WGH
 

Knud-Erik

Check out https://hamapps.groups.io/g/Support/topic/80976078#33513. I had similar issue. Laurie's suggestion solved my problem.

Ron, WB2WGH 

On Sat, May 15, 2021, 6:00 AM Knud-Erik Kaadner <ke@...> wrote:
I have got a problem with loggin. Please see the attached pictures.
Picture no. 1 shows a QSO with DF6JF, and picture no. 2  the logging window from WSTJ for that QSO.
So far so good.
When I click the OK button this window closes, and a new one pops up briefly, telling that JTAlert logged the QSO to HRD V5/V6 with succes.
Picture no. 3 is showing the HRD log with 3 entries for that QSO. One with the Time on at 16:20:30, and two with the Time on at 16:20:00, which is the time I started calliing CQ
The next QSO with DL8YBL is the same, and the QSO with DL1MFT I added manualy.
I am using JTAlert v. 2.50.1, WSJT-X v. 2.3.0 and HRD v. 6.7.0357


locked Re: Logging

Ron W3RJW
 

Make sure you are not logging each QSO from both WSJT-x and JTAlert to HRD  You don't need/want both.  I think JTAlert to HRD is the better option.
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Logging

Knud-Erik Kaadner
 

I have got a problem with loggin. Please see the attached pictures.
Picture no. 1 shows a QSO with DF6JF, and picture no. 2  the logging window from WSTJ for that QSO.
So far so good.
When I click the OK button this window closes, and a new one pops up briefly, telling that JTAlert logged the QSO to HRD V5/V6 with succes.
Picture no. 3 is showing the HRD log with 3 entries for that QSO. One with the Time on at 16:20:30, and two with the Time on at 16:20:00, which is the time I started calliing CQ
The next QSO with DL8YBL is the same, and the QSO with DL1MFT I added manualy.
I am using JTAlert v. 2.50.1, WSJT-X v. 2.3.0 and HRD v. 6.7.0357


locked Re: CQ for stations not CQing

HamApps Support (VK3AMA)
 

On 15/05/2021 7:43 am, Steve wrote:
I am not sure where the call info comes from that say CQ with JTAlert 2.50.0.  I am using JTDX v2.2.0-rc152 with JTAlert.

I keep getting CQ with call signs that don't show in JTDX.  I can't click on them in JTAlert to make a contact.  Where is the CQ contact info coming from that is used in JTAlert?

Thanks.

Steve NA6G

All CQ alerting is based on the real-time decodes coming from WSJT-X/JTDX.
If a decode starts with a "CQ " then it is deemed a CQ decode and alerted accordingly.

What does "I keep getting CQ with call signs" mean? Does it mean that the callsigns are colored with the CQ colors with no sound or does it mean that the "CQ" audio file is played with no coloring or both?

JTAlert will only Alert on the actual decodes it receives.

Sounds to me like JTDX is hiding some of its decodes if JTAlert is getting decodes that are not visible in JTDX.

de Laurie VK3AMA


locked Re: JTAlert Autostart

Joe Subich, W4TV
 

The only window that does not close automatically is the Google Earth
Pro window.
In DXLab Launcher -> Config -> Apps Started Before/After DXLab Apps,
click on he "Show Captions" button and enter the caption ("Google Earth
Pro" ?) from the Window Frame (top) of Google Earth. That lets Launcher
know which window to send the "terminate" message when it closes.

73,

... Joe, W4TV


On 2021-05-14 4:51 PM, Craig wrote:
Hi Jim - decided to make the new changes and all works just fine using
JTAlert (launch / close) only. The only window that does not close
automatically is the Google Earth Pro window. That window was not closing
when terminating apps using Launcher. Not sure how that is managed. Best, C
On Fri, May 14, 2021 at 3:41 PM Craig Willison <nz4cwcraig@gmail.com> wrote:

Hi Jim - thanks much for your thoughts on shutdown options. I understand
your thinking / approach and how it would work not using the bat file.
Some thoughts on operating implications:

1 - If I am going to run digital, everything (launching / terminating) is
then controlled by launching / stopping JTAlert
2 - If I am going to mostly run a different mode, I can launch / terminate
DXLab apps via the Launcher (as designed) without WSJT-X / JTAlert
running. Issue would be then starting JTAlert and having the DXLab apps
launched again - likely easier to terminate with Launcher and restart via
JTAlert.
3 - For mixed mode, option 1 still works fine.

So maybe it's best to always run option 1 given the issue noted under 2.
I wonder if there are implications for operating/logging with JTAlert
starting before the DXLab apps?

Could work Jim. Appreciate you noodling on this for me. I will swing
back to you and let you know what I experience.

73, Craig


On Fri, May 14, 2021 at 2:26 PM Jim N6VH <N6VH@outlook.com> wrote:


On 5/13/2021 5:58 PM, Craig wrote:

Hello Jim - thanks so much for taking the time to put together the coding
and the description of the process. All works just great making the entire
startup process a single click!

Question, as Launcher takes care of starting and terminating the DXLab
applications and other applications that start direct (before or after the
DXLab apps), is there a way to have Launcher terminate the apps started
using the above process that you put together for me? Not a big item but
would take care of everything at shutdown. Thanks again Jim.

73, Craig

Craig,

I'm glad my solution worked fro you.

I don't see any easy way of shutting down JTAlert form DXLab Launcher. It
has been many years since I worked with batch files, so I am pretty rusty
with them. Here's a thought about a different approach. Would it work for
you to have JTAlert autostart DXLab, and NOT use the batch file? In
JTAlert settings, under Auto-Start, set DXLab Launcher to Start after
JTAlert, and then Close when JTAlert is closed.

In DXLab Launcher configuration, select the DXLab Apps you want to start,
and at the top, check Auto Start. Also, check Terminate On Shutdown. See if
that works for you.

Ignore any of the ACLog autostart you see in my JTAlert example. It is
just there for testing (as is DXLab Launcher).

73,

Jim N6VH



locked CQ for stations not CQing

Steve
 

I am not sure where the call info comes from that say CQ with JTAlert 2.50.0.  I am using JTDX v2.2.0-rc152 with JTAlert.

I keep getting CQ with call signs that don't show in JTDX.  I can't click on them in JTAlert to make a contact.  Where is the CQ contact info coming from that is used in JTAlert?

Thanks.

Steve NA6G


locked Re: JTAlert Issue

HamApps Support (VK3AMA)
 

On 12/05/2021 11:52 am, rob neff via groups.io wrote:
Okay, I tried running the shortcut on the desktop as Admin and it runs now. I will make that permanent. 

Sorry for the trouble. 

Rob KW2E

NO! There should be no need to run JTAlert elevated if installed correctly.

On the affected Windows account, did you install JTAlert or are you relying on the JTAlert install under the other (working) account. If the later, that explains why you need to elevate JTAlert as it is trying to access the %localappdata% area of another Windows account which is normally prevented due to Windows security permissions

For each Windows account you need to install JTAlert.

If your reason for using a secondary Windows account is so that you can use a different Callsign with JTAlert. That is easily accomplished by creating a new JTAlert shortcut with an appropriate callsign command parameter. See the "Station Callsign" section of the Settings window.

   

de Laurie VK3AMA

2901 - 2920 of 37741