Date   

locked Re: Wrong lookup data

Robert <Robert@...>
 

I will, stand by please.

Thanks,

Robert AC2MM


On 2/11/2019 4:39 PM, Robert wrote:
OK, so if I can't depend on the QRZ info, how do I find the DXCC of the call sign?
So why is QRZ listing all these as mistakes, when the fact is that JTAlertX is the one installing this information, not me.

Thanks,

Robert AC2MM


On 2/11/2019 4:26 PM, HamApps Support (VK3AMA) wrote:
On 12/02/2019 8:05 am, Robert wrote:
I've been spending a lot of time on QRZ with awards and the Logbook, and was surprised to see that I have about 15 or so QSO's that JTAlertX has installed into my HRD logbook with incorrect information.
This current group of 12 has the wrong Grid information, and most likely, more than that.
It's a lot of work to look all these QSO's up, and make the necessary changes, then upload again to LOTW the correct information, as well as go back and correct this in QRZ.
As an example, your system says that V31YN is located in Belize, around Mexico, where in fact it's in Germany.  It got the City right, but botched the country, no small thing.

So why is this happening and how can it be corrected.

-- 

Thanks,

Robert AC2MM
Robert,

Using your one provided example, V31YN, I find no fault.

JTAlert correctly identifies V31YN as being in Belize.

The only botched data is your changing of the logged country from Belize to Germany. Germany is what is botched.

Your assertion that V31YN is in Germany is incorrect. You examined the QRZ listing which provides a German QSL address, but this is not the DXCC of the Callsign, only the QSL address.

The QRZ Bio for the Callsign includes "Location "Smugglers' Den" Consejo Shores, Corozal Belize (CentralAmerica)"

A QRZ XML lookup if enabled in JTAlert also correctly returns Belize.

Part of the QRZ XML results, showing that the DXCC is Belize (# 66)...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>V31YN</call>
<aliases>DJ4KW,DJ4KWA,AC6YM</aliases>
<dxcc>66</dxcc>
<fname>Gerd R.</fname>
<name>Sapper</name>
<addr1>Gumbinner Str. 5 a</addr1>
<addr2>Lueneburg</addr2>
<zip>21337</zip>
<country>Germany</country>
<lat>18.465510</lat>
<lon>-88.302420</lon>
<grid>EK58ul</grid>
<ccode>104</ccode>
<land>Belize</land>


de Laurie VK3AMA




locked Re: Wrong lookup data

Robert <Robert@...>
 

OK, so if I can't depend on the QRZ info, how do I find the DXCC of the call sign?
So why is QRZ listing all these as mistakes, when the fact is that JTAlertX is the one installing this information, not me.

Thanks,

Robert AC2MM


On 2/11/2019 4:26 PM, HamApps Support (VK3AMA) wrote:
On 12/02/2019 8:05 am, Robert wrote:
I've been spending a lot of time on QRZ with awards and the Logbook, and was surprised to see that I have about 15 or so QSO's that JTAlertX has installed into my HRD logbook with incorrect information.
This current group of 12 has the wrong Grid information, and most likely, more than that.
It's a lot of work to look all these QSO's up, and make the necessary changes, then upload again to LOTW the correct information, as well as go back and correct this in QRZ.
As an example, your system says that V31YN is located in Belize, around Mexico, where in fact it's in Germany.  It got the City right, but botched the country, no small thing.

So why is this happening and how can it be corrected.

-- 

Thanks,

Robert AC2MM
Robert,

Using your one provided example, V31YN, I find no fault.

JTAlert correctly identifies V31YN as being in Belize.

The only botched data is your changing of the logged country from Belize to Germany. Germany is what is botched.

Your assertion that V31YN is in Germany is incorrect. You examined the QRZ listing which provides a German QSL address, but this is not the DXCC of the Callsign, only the QSL address.

The QRZ Bio for the Callsign includes "Location "Smugglers' Den" Consejo Shores, Corozal Belize (CentralAmerica)"

A QRZ XML lookup if enabled in JTAlert also correctly returns Belize.

Part of the QRZ XML results, showing that the DXCC is Belize (# 66)...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>V31YN</call>
<aliases>DJ4KW,DJ4KWA,AC6YM</aliases>
<dxcc>66</dxcc>
<fname>Gerd R.</fname>
<name>Sapper</name>
<addr1>Gumbinner Str. 5 a</addr1>
<addr2>Lueneburg</addr2>
<zip>21337</zip>
<country>Germany</country>
<lat>18.465510</lat>
<lon>-88.302420</lon>
<grid>EK58ul</grid>
<ccode>104</ccode>
<land>Belize</land>


de Laurie VK3AMA



locked Re: Wrong lookup data

HamApps Support (VK3AMA)
 

On 12/02/2019 8:05 am, Robert wrote:
This current group of 12 has the wrong Grid information

Do you have examples of these wrongly logged Grids?

Provide a couple of examples. The Callsign, the logged Grid and the Grid you feel is correct.

de Laurie VK3AMA


locked Re: Wrong lookup data

HamApps Support (VK3AMA)
 

On 12/02/2019 8:05 am, Robert wrote:
I've been spending a lot of time on QRZ with awards and the Logbook, and was surprised to see that I have about 15 or so QSO's that JTAlertX has installed into my HRD logbook with incorrect information.
This current group of 12 has the wrong Grid information, and most likely, more than that.
It's a lot of work to look all these QSO's up, and make the necessary changes, then upload again to LOTW the correct information, as well as go back and correct this in QRZ.
As an example, your system says that V31YN is located in Belize, around Mexico, where in fact it's in Germany.  It got the City right, but botched the country, no small thing.

So why is this happening and how can it be corrected.

-- 

Thanks,

Robert AC2MM
Robert,

Using your one provided example, V31YN, I find no fault.

JTAlert correctly identifies V31YN as being in Belize.

The only botched data is your changing of the logged country from Belize to Germany. Germany is what is botched.

Your assertion that V31YN is in Germany is incorrect. You examined the QRZ listing which provides a German QSL address, but this is not the DXCC of the Callsign, only the QSL address.

The QRZ Bio for the Callsign includes "Location "Smugglers' Den" Consejo Shores, Corozal Belize (CentralAmerica)"

A QRZ XML lookup if enabled in JTAlert also correctly returns Belize.

Part of the QRZ XML results, showing that the DXCC is Belize (# 66)...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>V31YN</call>
<aliases>DJ4KW,DJ4KWA,AC6YM</aliases>
<dxcc>66</dxcc>
<fname>Gerd R.</fname>
<name>Sapper</name>
<addr1>Gumbinner Str. 5 a</addr1>
<addr2>Lueneburg</addr2>
<zip>21337</zip>
<country>Germany</country>
<lat>18.465510</lat>
<lon>-88.302420</lon>
<grid>EK58ul</grid>
<ccode>104</ccode>
<land>Belize</land>


de Laurie VK3AMA


locked Wrong lookup data

Robert <Robert@...>
 

Hello,
I've been spending a lot of time on QRZ with awards and the Logbook, and was surprised to see that I have about 15 or so QSO's that JTAlertX has installed into my HRD logbook with incorrect information.
This current group of 12 has the wrong Grid information, and most likely, more than that.
It's a lot of work to look all these QSO's up, and make the necessary changes, then upload again to LOTW the correct information, as well as go back and correct this in QRZ.
As an example, your system says that V31YN is located in Belize, around Mexico, where in fact it's in Germany.  It got the City right, but botched the country, no small thing.

So why is this happening and how can it be corrected.

--

Thanks,

Robert AC2MM


locked Re: how to launch JTAlert for a specific profile

HamApps Support (VK3AMA)
 

On 11/02/2019 1:18 pm, groupio@... wrote:
Hi.  My son just upgraded to his general class license.  We share the same rig.  So now we need a way to quickly and easily swap profiles, especially if one of us finds some rare DX (so switching Windows accounts is not an option).  I use JTAlert and have configured it to launch Log4OM.  I would like to configure a Windows shortcut to launch JTAlert but have it read my son's "profile" not mine (including the wanted lists and log file) as well as launch Log4OM to point to a separate logbook for my son.  Is this possible?  I've looked through the JTAlert command line parameters but there seems to be no option to select a profile (only control operator callsign override and ADI file name).  Any suggestions?

Thanks!

73, Mike KK7ER
Mike,

Start JTAlert with a "/callsign=" parameter using your Son's Callsign. You can either manually create a new shortcut or visit the JTAlert Settings, "Station Callsign" section and create new shortcuts from there (you will need to delete any unnecessary shortcuts created, like for HB9HQX, JTDX, etc).

When fist starting JTAlert with this new shortcut, a new, default config will be created and you will need to setup the logging and run a Scan to update the Wanted Lists.

   

de Laurie VK3AMA




locked Push Notifications

WB8ASI Herb
 

Any help to point me in the right direction to set up push notifications from JTAlert????   Assuming I start at User Defined Alerts, but where to send them.  Using Growl with Log4OM, but seems that is no longer supported. Should I figure out Snarl???   Need advice where to start. Tnx 73, Herb WB8ASI


locked how to launch JTAlert for a specific profile

Mike KK7ER
 

Hi.  My son just upgraded to his general class license.  We share the same rig.  So now we need a way to quickly and easily swap profiles, especially if one of us finds some rare DX (so switching Windows accounts is not an option).  I use JTAlert and have configured it to launch Log4OM.  I would like to configure a Windows shortcut to launch JTAlert but have it read my son's "profile" not mine (including the wanted lists and log file) as well as launch Log4OM to point to a separate logbook for my son.  Is this possible?  I've looked through the JTAlert command line parameters but there seems to be no option to select a profile (only control operator callsign override and ADI file name).  Any suggestions?

Thanks!

73, Mike KK7ER


locked Re: with portrait mode.

WB5JJJ - George
 

Art

I find the number of cells already available to be extremely over the limit of what JTAlert should be showing me.  Simply put, if you ask JTA to show ONLY those stations calling CQ, and of those that are a new contact on the current band and, for me, only LoTW users, I see a max of about 8-10 on even a very busy band, typically its none to 4.  Worked b4's, and those in a QSO as well as non-LoTW users are not displayed.  Much easier to digest in a few seconds instead of everything going on. 

Ever other call is shown in the WSJTx Band Activity window as expected with the proper colors. 
--
73's
George - WB5JJJ


locked Re: with portrait mode.

HamApps Support (VK3AMA)
 

On 11/02/2019 6:50 am, afa1yy wrote:
With the increased popularity of FT8, the number of decodes  has surpassed my display's ability to show them all.  To remedy this, I am using a monitor in portrait mode.  Fine, I can display several times as many decodes than before.  But the JT Alert matrix is now not nearly wide enough to be constrained by my screen.  It shows maybe 60 - 70% of the decode matrix.  Any suggestions please,
--
Art  K0AY
Art,

If you want a user-sizable JTAlert window, unfortunately that is not possible with the current V2 series of JTAlert. The under development JTAlert V3 has no restrictions on window size, but is still many months from release. :(

de Laurie VK3AMA


locked Re: with portrait mode.

Carey, WB4HXE
 

Filter down the decodes to show less on JTAlertX.

On Sun, Feb 10, 2019 at 3:02 PM afa1yy <arthur@...> wrote:
With the increased popularity of FT8, the number of decodes  has surpassed my display's ability to show them all.  To remedy this, I am using a monitor in portrait mode.  Fine, I can display several times as many decodes than before.  But the JT Alert matrix is now not nearly wide enough to be constrained by my screen.  It shows maybe 60 - 70% of the decode matrix.  Any suggestions please,
--
Art  K0AY



--
Carey Fisher


locked with portrait mode.

afa1yy
 

With the increased popularity of FT8, the number of decodes  has surpassed my display's ability to show them all.  To remedy this, I am using a monitor in portrait mode.  Fine, I can display several times as many decodes than before.  But the JT Alert matrix is now not nearly wide enough to be constrained by my screen.  It shows maybe 60 - 70% of the decode matrix.  Any suggestions please,
--
Art  K0AY


locked Re: Updates thought

Tom Melvin
 

Jim

No it wouldn’t be a wsjt-x issue - the question was mooted that could a pop-up be helpful when starting JTAlert to identify an upgrade was available. This would be completely separate to wsjt-x.


73’s

Tom
GM8MJV (IO85)

On 9 Feb 2019, at 22:47, Jim - N4ST <newsgroup@jimpricejr.com> wrote:

Yeah, well that would be a WSJT-X issue, not a JT-Alert issue.
And the pop-up will be removed in the next update.

________
73,
Jim - N4ST

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Tom
Melvin
Sent: Saturday, February 9, 2019 17:12
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Updates thought

Mike

Not too keen on a pop-up on start up - even more things to click to just get
started.

May be ok if you start WSJT + jtalert once a week etc but my PC does do
other things and can end up starting multiple wsjt (and corresponding
jtalerts) quite a few times in an ‘operating session’ - Depending on
mode/propagation may be running the older wsjt and switching to new - so
less ‘clicking’ is a big plus.


--

73’s

Tom
GM8MJV (IO85)




locked Re: Updates thought

HamApps Support (VK3AMA)
 

On 10/02/2019 1:14 pm, HamApps Support (VK3AMA) via Groups.Io wrote:
Likely I will show a popup as JTAlert is closing.

In addition, a popup at shutdown wont delay the JTAlert shutdown with a slow or broken Internet check as the update check has already been performed earlier in the session.

de Laurie VK3AMA


locked Re: Updates thought

HamApps Support (VK3AMA)
 

On 10/02/2019 8:33 am, Michael Black via Groups.Io wrote:
Laurie -- the new "!" for updates isn't very noticeable.

Any reason we can't have a popup when you load the program to tell you what updates are available with a weblink built in?

Mike
Mike,

I am not very keen on application popups during startup.

A check on an update requires an Internet lookup and depending on the user environment or the state of the update hosting server at the time, this can cause unwanted delays to the startup. or hangs if the Server is down. JTAlert works around the possible slow or failed internet access by performing the update check in a separate process, that runs while JTAlert is doing its thing. I would rather not have a popup show sometime after JTAlert has started and potentially while processing decodes.

A popup that is shown once every X times JTAlert has been started (to avoid user annoyance with a popup every startup, like WSJT-X and its ver 2.0 warning) is likely where I will go, but it will need to be such that it doesn't interfere with normal JTAlert operation and doesn't slow or hang the startup. Likely I will show a popup as JTAlert is closing.

de Laurie VK3AMA



locked Re: JTAlert wont start

HamApps Support (VK3AMA)
 

On 10/02/2019 10:31 am, Michael Black via Groups.Io wrote:
You will find a config.sqlite that you can rename and probably that will fix the problem.

If you do get JTAlert started send in a debug report via Help/Contact Support which should send that file into Laurie so he can perhaps see why it's blocking startup.

de MIke W9MDB
Mike,

Very unlikely a corrupt or damaged config file will cause this behaviour. Typical symptoms of a bad config are setting changes not being remembered across JTAlert restarts.

de Laurie VK3AMA


locked Re: JTAlert wont start

HamApps Support (VK3AMA)
 

On 10/02/2019 4:46 am, Rick Boswell wrote:
I have been using JTAlert 2.12.10 with WSJT-X 2.0.0 for many weeks with and without DX Lab apps with no difficulty of any kind. This AM I discovered that JTAlert will not start when double clicking the red X icon. The spinning blue cursor circle appears for a few seconds and then nothing. I have uninstalled and reinstalled but no change in symptoms and no error messages of any kind. Any guidance on this one?

Thanks,
Rick
K8EZB
Rick,

Since JTAlert hasn't changed in the last few weeks, the cause is likely elsewhere. Repeated uninstalls/install operations are not likely to achieve anything except user frustration.

Likely culprits are Win10 needing a restart or Virus/Malware protection interference.
I suggest performing a Windows restart as a first step. If still no joy, start looking into your Virus protection event logs.

de Laurie VK3AMA


locked Re: JTAlert wont start

Rick Boswell
 

Mike,

On Sat, Feb 9, 2019 at 03:31 PM, Michael Black wrote:
You will find a config.sqlite that you can rename and probably that will fix the problem.

Looking … no joy. Can you be a bit more specific?

Thanks,
RB


locked Re: JTAlert wont start

Michael Black
 

You will find a config.sqlite that you can rename and probably that will fix the problem.

If you do get JTAlert started send in a debug report via Help/Contact Support which should send that file into Laurie so he can perhaps see why it's blocking startup.

de MIke W9MDB




On Saturday, February 9, 2019, 11:46:21 AM CST, Rick Boswell <frboswell@...> wrote:


I have been using JTAlert 2.12.10 with WSJT-X 2.0.0 for many weeks with and without DX Lab apps with no difficulty of any kind. This AM I discovered that JTAlert will not start when double clicking the red X icon. The spinning blue cursor circle appears for a few seconds and then nothing. I have uninstalled and reinstalled but no change in symptoms and no error messages of any kind. Any guidance on this one?

Thanks,
Rick
K8EZB


locked Re: Updates thought

Jim - N4ST
 

Yeah, well that would be a WSJT-X issue, not a JT-Alert issue.
And the pop-up will be removed in the next update.

________
73,
Jim - N4ST

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Tom
Melvin
Sent: Saturday, February 9, 2019 17:12
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Updates thought

Mike

Not too keen on a pop-up on start up - even more things to click to just get
started.

May be ok if you start WSJT + jtalert once a week etc but my PC does  do
other things and can end up starting multiple wsjt (and corresponding
jtalerts)  quite a few times in an ‘operating session’ -  Depending on
mode/propagation may be running the older wsjt and switching to new - so
less ‘clicking’ is a big plus.

 
--

73’s

Tom
GM8MJV (IO85)

14481 - 14500 of 37778