Date   

Re: JTAlerts 2.16.15 crashes

Michael
 

seems to have only happen since upgrading to 2.16.15. Maybe I ought to go back to 2.16.14?


Republic of North Macedonia

Ron W3RJW
 
Edited

Republic of North Macedonia  ...   Comes up as "N." in my JTA callsign display (i.e. Z34K). The official name of Macedonia.is now Republic of North Macedonia (result of political dispute over the name)

Everything gets logged correctly,

No big deal   When you get around to it.
--
73
Ron, W3RJW


Re: JTAlerts 2.16.15 crashes

Michael Black
 


Nothing can be done...there's no fix for it....and nobody seems to know what causes it either...it's some compiler bug.  This will go away when the new JTAlert is released -- maybe next year?

Generally it seems a reboot helps.

Mike W9MDB

On Friday, November 6, 2020, 12:14:54 PM CST, Michael <w7osgarrl@...> wrote:


Just started getting this error notice






Thanks

MIke C.


JTAlerts 2.16.15 crashes

Michael
 

Just started getting this error notice






Thanks

MIke C.


Re: JT Alert crashes

Michael Black
 

First thing to try is run a new configuration.

You can temporarily rename C:\Users\[username]\AppData\Local\HamApps
Then JTALert will recreate it.

If that fixes your problem then zip up the old directory and send it in.


Mike W9MDB




On Thursday, November 5, 2020, 10:16:41 AM CST, <tomloock@...> wrote:


For some reason JT Alert crashes.  I start WSJT-X and then JT Alert and I am decoding signals but after 1 or 2 cycles JT Alert shuts down.  It does show the stations that I have not contacted but after the 2nd decode cycle the program closes. Not sure what might have changed.  I have tried versions 2.16.6,  2.16.14 and 2.16.15 and all do the same thing.  ???

TIA
73 Tom K9VER


JT Alert crashes

tomloock@...
 

For some reason JT Alert crashes.  I start WSJT-X and then JT Alert and I am decoding signals but after 1 or 2 cycles JT Alert shuts down.  It does show the stations that I have not contacted but after the 2nd decode cycle the program closes. Not sure what might have changed.  I have tried versions 2.16.6,  2.16.14 and 2.16.15 and all do the same thing.  ???

TIA
73 Tom K9VER


Re: Odd happenings

Dave Garber
 

i thought lookups were done via a qrz key, within jtalert

Dave Garber
VE3WEJ / VE3IE


On Wed, Nov 4, 2020 at 10:37 AM Phil Cooper via groups.io <pcooper=suremail.gg@groups.io> wrote:
Hi Laurie and the group,

Since updating to the latest version of JTAlert (2.16.15) I've noticed one small oddity in the behavior of JTA when working a previously worked call.
It used to bring up the name, QTH and grid of a call worked on other bands, but with this latest version, if that call was worked on - say RTTY - since the previous FT8 contact, it does not automatically fill in the name and QTH, but sometimes does bring up the grid, if it was matched on LoTW.

For example, I had worked Chad WE9V on many bands in FT8 previously (80/40/30/20/17, but not 15m) and when I saw him on 15m today, I gave him a call, but since I worked him on RTTY the last time, it failed to bring up his name and QTH, even though we had previously worked on FT8.

I don't see any mention of this in the release notes, so maybe it is a bug, or is it me?

I'm running the latest version of DXKeeper, and logging is working fine, as is the lookup of previous contacts.

73 de Phil GU0SUP


Re: db display

scot
 

David,

 

Thanks for the info.

 

Scott

N2SAB

 

From: David Ross [mailto:drossm@...]
Sent: Wednesday, November 4, 2020 2:35 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] db display

 

Settings....Window....Extended Display...Show db (DXCC Name)

David VA3MJR

On 2020-11-04 12:57 p.m., scot wrote:

Laurie,

i know this was posted recently but i can not find it... How to show RX Db level in the text boxes. I just went to another computer and can not figure it out....

Scott
N2 SAB

--


Re: db display

David Ross
 

Settings....Window....Extended Display...Show db (DXCC Name)

David VA3MJR

On 2020-11-04 12:57 p.m., scot wrote:
Laurie,

i know this was posted recently but i can not find it... How to show RX Db level in the text boxes. I just went to another computer and can not figure it out....

Scott
N2 SAB
--


db display

scot
 

Laurie,

i know this was posted recently but i can not find it... How to show RX Db level in the text boxes. I just went to another computer and can not figure it out....

Scott
N2 SAB


Re: Odd happenings

Paul
 

Hi, 
     I am also running JTAlert 2.16.15 and DXKeeper 15.8.9.
On checking JTAlert Settings> Manager Settings > Logging---Logging options "Do not lookup previous qso data from logbook"
 is UN TICKED.The same problem of QRZ information not being file in from previous QSO"S Is happening.
Paul G4YKQ.


Odd happenings

Phil Cooper
 

Hi Laurie and the group,

Since updating to the latest version of JTAlert (2.16.15) I've noticed one small oddity in the behavior of JTA when working a previously worked call.
It used to bring up the name, QTH and grid of a call worked on other bands, but with this latest version, if that call was worked on - say RTTY - since the previous FT8 contact, it does not automatically fill in the name and QTH, but sometimes does bring up the grid, if it was matched on LoTW.

For example, I had worked Chad WE9V on many bands in FT8 previously (80/40/30/20/17, but not 15m) and when I saw him on 15m today, I gave him a call, but since I worked him on RTTY the last time, it failed to bring up his name and QTH, even though we had previously worked on FT8.

I don't see any mention of this in the release notes, so maybe it is a bug, or is it me?

I'm running the latest version of DXKeeper, and logging is working fine, as is the lookup of previous contacts.

73 de Phil GU0SUP


Re: {SPAMFILTER} Re: [HamApps] 6-digit Grids in Decodes window

Anthony W. DePrato
 

yes i know there are NOW Grid awards outside of VHF/UHF with FT8 in the HF bands.
i see awards now for working 50 grid sq's in Africe ect.
for those it is great . like i said to each his own
73

, FT8 only sends 4 places no ma
As for grids, are you not aware that there are at
least a few awards (HF, worldwide) based on grids
worked ... ?? Why do you supposed Laurie spent a
good chunk of his life creating the grids-worked
database and alerts for unworked grids? not just
for VHF.

http://www.arrl.org/ffma

https://www.qrz.com/awards/GSA/










--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: {SPAMFILTER} Re: [HamApps] 6-digit Grids in Decodes window

Anthony W. DePrato
 

like i said each to his own.Larry. i have worked DX for 60 yrs and really never needed a gird to tell me where Poland or Turkoman was.
was located in EU or Asia.or in case of a /MM Their Reigon told me where they were in the world.
73 Tony wa4jqs



At 10:49 AM 11/3/2020, you wrote:
States don’t work in many countries outside of the USA, and grids give a much better indication of location world-wide.

73 -- Larry -- W1DYJ

 
From: Anthony W. DePrato
Sent: Tuesday, November 03, 2020 9:59
To: Support@HamApps.groups.io
Subject: Re: [HamApps] 6-digit Grids in Decodes window
 



I would think it is because some enter the entire Grid Sq locator which is 6 numbers. others just enter 4.
really does not matter if it is 4 or 6. IMHO Grids are for use on VHF freqs not HT . i think WSJT-X used on HF should list state instead of Grids.
but to each his own.
73 Tony WA4JQS








At 11:00 PM 11/2/2020, you wrote:
I don't know where JTalert gets the 6-digit
grid locators that occaisionally show in the
Decodes window, but apparently when one
rebuilds the Alert database they don't register
with the first four characters ... 

Example below ... these two stations are B4
but when I ran the rebuild alert db they did
not clear but remain as wanted grids.

graphic  

 

[]  Virus-free. www.avg.com


Re: 6-digit Grids in Decodes window

Jim Cooper
 

On 3 Nov 2020 at 9:59, Anthony W. DePrato wrote:

I would think it is because some
enter the entire Grid Sq locator
which is 6 numbers. others just
enter 4. really does not matter if it
is 4 or 6. IMHO Grids are for use on
VHF freqs not HT . i think WSJT-X
used on HF should list state instead
of Grids. but to each his own. 73 Tony
WA4JQS
Well, FT8 only sends 4 places no matter what is put in.

So the 6 places must come from some lookup somewhere.

As for grids, are you not aware that there are at
least a few awards (HF, worldwide) based on grids
worked ... ?? Why do you supposed Laurie spent a
good chunk of his life creating the grids-worked
database and alerts for unworked grids? not just
for VHF.

http://www.arrl.org/ffma

https://www.qrz.com/awards/GSA/


Re: 6-digit Grids in Decodes window

Larry Banks
 

States don’t work in many countries outside of the USA, and grids give a much better indication of location world-wide.

73 -- Larry -- W1DYJ

 

Sent: Tuesday, November 03, 2020 9:59
Subject: Re: [HamApps] 6-digit Grids in Decodes window
 



I would think it is because some enter the entire Grid Sq locator which is 6 numbers. others just enter 4.
really does not matter if it is 4 or 6. IMHO Grids are for use on VHF freqs not HT . i think WSJT-X used on HF should list state instead of Grids.
but to each his own.
73 Tony WA4JQS








At 11:00 PM 11/2/2020, you wrote:
I don't know where JTalert gets the 6-digit
grid locators that occaisionally show in the
Decodes window, but apparently when one
rebuilds the Alert database they don't register
with the first four characters ... 

Example below ... these two stations are B4
but when I ran the rebuild alert db they did
not clear but remain as wanted grids.

graphic

 

[] Virus-free. www.avg.com


Re: 6-digit Grids in Decodes window

Anthony W. DePrato
 




I would think it is because some enter the entire Grid Sq locator which is 6 numbers. others just enter 4.
really does not matter if it is 4 or 6. IMHO Grids are for use on VHF freqs not HT . i think WSJT-X used on HF should list state instead of Grids.
but to each his own.
73 Tony WA4JQS








At 11:00 PM 11/2/2020, you wrote:
I don't know where JTalert gets the 6-digit
grid locators that occaisionally show in the
Decodes window, but apparently when one
rebuilds the Alert database they don't register
with the first four characters ... 

Example below ... these two stations are B4
but when I ran the rebuild alert db they did
not clear but remain as wanted grids.

graphic

 

[]  Virus-free. www.avg.com


Re: V2.6.14 Crash

TomK
 

FWIT: I run my DRW (digital radio workstation) 20/7/365. 

When not at the keyboard, I let apps idle by disabling WSJT monitoring.

However, that is NOT without issues.

A little forensics tells me most pop digital apps trigger memory issues.

That is common with heavy use of internal arrays and caches that eat memory.

 

So, I take it in stride and do the simple routines of:

  1. Daily:                     Restart all my DRW apps (WSJT, JTA, GT, ACLog, Excel).
  2. Weekly:                Do a Soft PC Restart (Windows option)
  3. Monthly:              Do a Hard Restart (via power switch)

It’s even easier with the habit of starting them when breaking to eat, make coffee, etc.

My actual schedule varies madly 😊

TomK 73

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of David
Sent: Monday, November 2, 2020 10:02 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] V2.6.14 Crash

 

Michael,

The computer was rebooted the day before, to install multiple Windows patches.
And, the unit has 64GB.
I could get in the habit of restarting JTAlert at least once per day if it would help.

David, AK2L


6-digit Grids in Decodes window

Jim Cooper
 

I don't know where JTalert gets the 6-digit
grid locators that occaisionally show in the
Decodes window, but apparently when one
rebuilds the Alert database they don't register
with the first four characters ... 

Example below ... these two stations are B4
but when I ran the rebuild alert db they did
not clear but remain as wanted grids.

graphic

  


Re: delay in decode is causing the calls in JTA to change in mid cycle

Jim Cooper
 

On 2 Nov 2020 at 16:13, Dave Garber wrote:

not sure how to show this in a clip,
so I am hoping you understand Laurie,
et al.    I decoded a station, and
was ready to pounce when 2 more call
decoded during that cycle, and the
first box emtied
I used to have the problem before I moved
my FT8 stuff onto a modern, "powerful" PC ...
it really DOES make a difference with this
stuff, which requires so much processing in
the mere last couple of seconds.

On the new PC, everything just pops up where
it should be ... no missed cycles, no stutters
posting the calls ...

w2jc