Date   

locked Re: Display distance in Kilometers?

HamApps Support (VK3AMA)
 

On 9/11/2020 7:26 am, Stefan Braun wrote:
By moving the mouse over a shown callsign, a lot of things are shown. Also the distance is shown im Miles.
Is there any possibility to show the distance in kilometers? 
I havn´t found any tickbox ar similar like in JTDX od WSJT to change it.
Thanks for any answer or help.
If not possible I would like to request a change that the distance can be shown in kilometers.

73s de Stefan HB9GFX

JTAlert "Alerts -> Decoded Callsign Data Tooltip" menu and un-tick the "Show distance in Miles" entry.

The default is for Kilometers display so sometime in the past you must have changed that setting.

de Laurie VK3AMA


locked Display distance in Kilometers?

Stefan Braun
 

By moving the mouse over a shown callsign, a lot of things are shown. Also the distance is shown im Miles.
Is there any possibility to show the distance in kilometers? 
I havn´t found any tickbox ar similar like in JTDX od WSJT to change it.
Thanks for any answer or help.
If not possible I would like to request a change that the distance can be shown in kilometers.

73s de Stefan HB9GFX


locked Re: CU5AM showed up as Portugal - QRZ XML Defect

HamApps Support (VK3AMA)
 

On 9/11/2020 1:34 am, Jim Spears wrote:

Even though his sent grid square matched Azores.  His qrz.com page appears to correctly show Azores.  This is with current JTAlert.

 

Jim Spears

N1NK


JTAlert correctly identifies CU5AM as being in the Azores.


The problem is that the data returned from a QRZ XML lookup is wrong. It has the dxcc set as 272 which is Portugal.
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>CU5AM</call>
<dxcc>272</dxcc>
<fname>JOSE MANUEL</fname>
<name>SILVA SILVEIRA</name>
<addr1>RUA DOS FAROLEIROS,5</addr1>
<addr2>VELAS</addr2>
<country>Azores</country>
<grid>HM58vq</grid>
<cqzone>14</cqzone>
<ituzone>36</ituzone>

I note that the HamQTH XML lookup returns the correct dxcc of 149.
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <search>
        <callsign>CU5AM</callsign>
        <nick>Jose Silva</nick>
        <qth>Rua dos Faroleiros,5 Velas</qth>
        <country>Azores Islands</country>
        <adif>149</adif>
        <itu>36</itu>
        <cq>14</cq>
        <grid>HM58VQ</grid>

I suggest you contact CU5AM and get him to correct his QRZ data.

de Laurie VK3AMA


locked Re: Republic of North Macedonia

HamApps Support (VK3AMA)
 

On 8/11/2020 3:32 am, Ron W3RJW via groups.io wrote:
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)

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

Ron,

The use of "North Macedonia" by JTAlert is based the Entity name provided by ClubLog.
I note that the cty.dat file lists "North Macedonia" and the ARRL listing has "North Macedonia (Republic of)".

In the past I relied on the Country name enumeration of the ADIF specs, but that is no longer accurate for a number of Country name changes that have occurred in recent years. I note it has not been updated in this case, still listing as "Macedonia", not "North" or "Republic".

The critical bit of data is the underlying dxcc number. It is immutable, it doesn't change, regardless of the country name changes or spelling.

de Laurie VK3AMA



locked Re: 6-digit Grids in Decodes window - Defect Confirmed

HamApps Support (VK3AMA)
 

On 3/11/2020 3:00 pm, Jim Cooper 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

  


I can confirm this defect.

The cause is the leaking of logged 6 character grids back into JTAlert for Grid alerting. This only occurs for compound callsigns where their grid cannot be included in the standard decode messages and a 6 character grid has been logged, as is the case for the two callsigns shown, 4A50CRH & ZA/IK2RLM.

This has been corrected for the next JTAlert release.

de Laurie VK3AMA


locked Re: CU5AM showed up as Portugal

Jim N6VH
 


On 11/8/2020 6:34 AM, Jim Spears wrote:

Even though his sent grid square matched Azores.  His qrz.com page appears to correctly show Azores.  This is with current JTAlert.

 

Jim Spears

N1NK

_._,_._,_


Jim,

CU5AM shows up in JTAlert as Azores here. I am using 2.16.15.  Do you have the latest Callsign Database installed? It is 2020.10.30.

73,

Jim N6VH


locked CU5AM showed up as Portugal

Jim Spears
 

Even though his sent grid square matched Azores.  His qrz.com page appears to correctly show Azores.  This is with current JTAlert.

 

Jim Spears

N1NK


locked Re: JTAlerts 2.16.15 crashes

Richard Williams
 

Michael,

I have been running 2.16.15 since it was released and have not had any problems.  I leave my computer and radio on pretty much 24/7, and unless I am working CW.SSB or RTTY, WSJT-X and JTAlert runs all the time on 6, 60, or 160M.

SInce this doesn't seem to be a wide spread problem, I would think the issue is a computer issue.

Am sure it is frustrating, so hopefully you can figure out what is causing the program to crash.

Dick, K8ZTT



Flying is the second greatest thrill known to man.
What is first, you ask? Landing, of course.
"A good aviator will always have his take-offs plus landings divisible by 2!"







On Saturday, November 7, 2020, 08:41:28 PM MST, Michael <w7osgarrl@...> wrote:


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


locked 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?


locked 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


locked 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.


locked JTAlerts 2.16.15 crashes

Michael
 

Just started getting this error notice






Thanks

MIke C.


locked 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


locked 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


locked 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


locked 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

--


locked 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
--


locked 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


locked 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.


locked 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

941 - 960 of 32879