Date   

locked Re: Data base update

HamApps Support (VK3AMA)
 

On 17/05/2021 12:50 am, VE3JI wrote:

I am running JTAlert version 2.16.14 with an older 2020 data base.  Can I update the callsign database to 

v2021.05.01 without updating to the new JTAlert release ?

Ian VE3JI

Yes the Callsigns database is compatible with your old JTAlert version.

Please note this will change in the future. There are database schema changes needed to accommodate some future alerting options. Those changes will break old JTAlert versions. When that database change happens, I will start releasing two versions of the database so old JTAlert versions will continue to have access to updated data. Eventually, after a number of subsequent JTAlert releases, I will stop publishing the older style database. How long that will be is unknown at this time, probably 6 months. Users who persist in running old JTAlert versions will have to accept that the QSL membership, US State & VE Province reporting will become inaccurate over time due to a non-updated database.

de Laurie VK3AMA


locked Re: Data base update

neil_zampella
 

I'm fairly sure you can, I don't think the database is tied to any specific release.   That said, why haven't you tried updating to 2.50.1 ??

 

Neil, KN3ILZ


locked Re: Log deleted by accident

chas cartmel
 

Missed earlier post so may be off track here, but is not the deleted file in the recycle bin?

73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of randybuckner via groups.io
Sent: 16 May 2021 14:31
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Log deleted by accident

 

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.


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Data base update

VE3JI
 

Hi All

I am running JTAlert version 2.16.14 with an older 2020 data base.  Can I update the callsign database to 

v2021.05.01 without updating to the new JTAlert release ?

Ian VE3JI


locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Ronald Ford
 

OK this may be operator error but this is what I found...

If I use the X on JTAlert to close the program the 2nd instance of JTAlert does not close.  If I go to the task bar and right click and select Close Window the program will close as expected.  So I guess I have been closing the window incorrectly....at least I know what is going on now.  Phil and Dave thanks for the comments....

73, Ronnie


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

3681 - 3700 of 38526