Date   

locked Re: Decodes History window will not load all of a sudden

WB8ASI Herb
 

Hi John,   Sounds like it is just off your screen.  Try holding down the "shift" key then drag it back onto the screen with the mouse or arrow keys.  73, Herb WB8ASI

On February 5, 2020 at 10:45 AM "John, K2ZJ" <jvc7388@...> wrote:

I have been using V2.15.7 successfully for the past few months, the Decodes History Window is especially useful because of the filters by Continent.  However today, quite randomly the window would not load.  I select it from the menu, and I can see the spinning disc for a few seconds but nothing appears on the screen.

This window has always worked for me over the past 6 months. All of the other windows work, like Text box etc.

I have rebooted the PC, rebooted JTAlert, reinstalled JTAlert etc with no success.

In the Task Manager of windows I see that the Decodes function is there- but nothing shows on the screen.

Any help with troubleshooting?  

Thanks John K2ZJ

 


locked Decodes History window will not load all of a sudden

John, K2ZJ
 

I have been using V2.15.7 successfully for the past few months, the Decodes History Window is especially useful because of the filters by Continent.  However today, quite randomly the window would not load.  I select it from the menu, and I can see the spinning disc for a few seconds but nothing appears on the screen.

This window has always worked for me over the past 6 months. All of the other windows work, like Text box etc.

I have rebooted the PC, rebooted JTAlert, reinstalled JTAlert etc with no success.

In the Task Manager of windows I see that the Decodes function is there- but nothing shows on the screen.

Any help with troubleshooting?  

Thanks John K2ZJ


locked JAlert stopped displaying calls from WSJT-X

Charlie Rubenstein
 

I didn't change any settings, but I no longer get the calls from WSJT-X. I checked the settings, but all three boxes are checked, and the IP and port settings are correct. So, I updated to the newest versions of both JAlert and WSJT-X in case there was something missing.....still no joy.

I rebooted the computer but it didn't help. 

Any suggestions?

Charlie KB8CCR


locked JTAlert does give some false "Not Wanted" DXCC report.

asobel@...
 

Laurie

 

This morning I did work VK9NK on Norfolk Is. 17m. This was my first QSO. I did upload it to LoTW and download LoTW  on Log4OMV2. I did later Scan the log on JTAlert and was surprised to find that Norfolk Is. Is reported as "Not wanted" on DXCC 17m. I did later find that Log4OMV2 does report all entries as LoTW confirmation Received as "Yes" and Received Date of some entries, not including VK9NK 17m of today, with the reporting received date.

So why did my JTAlert report 17m Norfolk Is. as "not wanted" and how does JTAlert find "Not Wanted" DXCC/LoTW in general?

 

Amos 4X4MF

 


locked Re: #fixed

Michael Black
 

Install the latest vc_redist.x86.exe runtime from here


Not the 64-bit version as JTAlert is a 32-bit application.

de Mike W9MDB



On Wednesday, February 5, 2020, 05:53:49 AM CST, jp.f5ghp@... <jp.f5ghp@...> wrote:


Hello , I can't  open the "Setting" menu. I have an SQL error
Pse Help


locked #fixed

F5GHP
 

Hello , I can't  open the "Setting" menu. I have an SQL error
Pse Help


locked Re: TI9A coming up as Cocos-Keeling instead of Cocos

HamApps Support (VK3AMA)
 

On 5/02/2020 5:00 pm, Graham Alston wrote:
TI9A is correct on qrz.com but comes up as Cocos-Keeling in JTAlert 2.15.8.

73 Graham VK3GA
Cosmetic defect only, see https://hamapps.groups.io/g/Support/message/27624

de Laurie VK3AMA


locked Re: Double entries on JTAlert Decodes window with instances / Clue

asobel@...
 

Laurie

 

Mistake See below

 

Laurie

 

I am using 4 instances

My filter is using "Show only alerts" and "JTAlerts enabled Alerts only" What is the difference?

Maximum records is 2000

Slice B 60m does now duplicate

Slice A 80m does not duplicate

Slice C and D are not active this morning. No alerts.

Did change to 100 records and restart.

Slice B 60m does not duplicate most of the time (one duplication)/ Mistake:  All activity moved to slice A 80m.

Slice A 80m does not duplicate

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ד 05 פברואר 2020 05:47
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Double entries on JTAlert Decodes window with instances / Clue

 

On 5/02/2020 8:58 am, asobel@... wrote:

It shows:

 

DH Filter Status

Active Filters

Show only Alerts

Hide worked B4

Hide Ignored

 

Amos 4X4MF

OK,

That didn't help. Using the same filtering settings I am not seeing any duplication of records.

How many JTAlert instances are you running?
What is the size of the Decodes database as shown in the status bar, number of records and size in brackets?

de Laurie VK3AMA


locked Re: Double entries on JTAlert Decodes window with instances / Clue

asobel@...
 

Laurie

 

I am using 4 instances

My filter is using "Show only alerts" and "JTAlerts enabled Alerts only" What is the difference?

Maximum records is 2000

Slice B 60m does now duplicate

Slice A 80m does not duplicate

Slice C and D are not active this morning. No alerts.

Did change to 100 records and restart.

Slice B 60m does not duplicate most of the time (one duplication)

Slice A 80m does not duplicate

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ד 05 פברואר 2020 05:47
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Double entries on JTAlert Decodes window with instances / Clue

 

On 5/02/2020 8:58 am, asobel@... wrote:

It shows:

 

DH Filter Status

Active Filters

Show only Alerts

Hide worked B4

Hide Ignored

 

Amos 4X4MF

OK,

That didn't help. Using the same filtering settings I am not seeing any duplication of records.

How many JTAlert instances are you running?
What is the size of the Decodes database as shown in the status bar, number of records and size in brackets?

de Laurie VK3AMA


locked Re: country conflict

Michael Black
 

Duh...that's what I get for reading too fast....

I'll have to contact them and see what's up.  Interesting that their FM5BH call has the dxcc right.

Mike


On Tuesday, February 4, 2020, 10:35:09 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 5/02/2020 3:25 pm, Michael Black via Groups.Io wrote:
Hmmm..looks like it's been corrected already...

<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
<ccode>166</ccode>
<land>France</land>
<email>ab2rf@...</email>
<u_views>4634</u_views>
<moddate>2019-11-15 05:51:39</moddate>
<eqsl>1</eqsl>
<mqsl>1</mqsl>
<locref>0</locref>
<lotw>1</lotw>
<user>AB2RF</user>
</Callsign>

Nope, that is still wrong. The bad line is "<dxcc>227</dxcc>".
227 = France, the correct code for Martinique is 84

de Laurie VK3AMA


locked Re: country conflict

HamApps Support (VK3AMA)
 

On 5/02/2020 3:25 pm, Michael Black via Groups.Io wrote:
Hmmm..looks like it's been corrected already...

<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
<ccode>166</ccode>
<land>France</land>
<email>ab2rf@...</email>
<u_views>4634</u_views>
<moddate>2019-11-15 05:51:39</moddate>
<eqsl>1</eqsl>
<mqsl>1</mqsl>
<locref>0</locref>
<lotw>1</lotw>
<user>AB2RF</user>
</Callsign>




Nope, that is still wrong. The bad line is "<dxcc>227</dxcc>".
227 = France, the correct code for Martinique is 84

Also, the line "<moddate>2019-11-15 05:51:39</moddate>" tells us this record hasn't been updated since November 2019.


de Laurie VK3AMA


locked Re: country conflict

HamApps Support (VK3AMA)
 

On 5/02/2020 3:25 pm, Michael Black via Groups.Io wrote:
Hmmm..looks like it's been corrected already...

<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
<ccode>166</ccode>
<land>France</land>
<email>ab2rf@...</email>
<u_views>4634</u_views>
<moddate>2019-11-15 05:51:39</moddate>
<eqsl>1</eqsl>
<mqsl>1</mqsl>
<locref>0</locref>
<lotw>1</lotw>
<user>AB2RF</user>
</Callsign>

Nope, that is still wrong. The bad line is "<dxcc>227</dxcc>".
227 = France, the correct code for Martinique is 84

de Laurie VK3AMA


locked Re: country conflict

Michael Black
 

Hmmm..looks like it's been corrected already...

<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
<ccode>166</ccode>
<land>France</land>
<email>ab2rf@...</email>
<u_views>4634</u_views>
<moddate>2019-11-15 05:51:39</moddate>
<eqsl>1</eqsl>
<mqsl>1</mqsl>
<locref>0</locref>
<lotw>1</lotw>
<user>AB2RF</user>
</Callsign>





On Tuesday, February 4, 2020, 08:25:45 PM CST, Dave Garber <ve3wej@...> wrote:


chalk it up to another error using QRZ...   ok, I have seen this many times... cant blame qrz though, most errors are user input, i think


Dave Garber
VE3WEJ / VE3IE


On Tue, Feb 4, 2020 at 8:45 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 5/02/2020 12:33 pm, Dave Garber wrote:
please see attachment, the TO on the air now from Martinique, seen in the little box, but the log line shows france....

is this a bug??

running jtalert 2.15.8.0

The only bug is with the user who maintains the TO3FM data on QRZ.com.
The XML data returned from a QRZ XML lookup uses a dxcc code of 227, which is France.

part of the XML data...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
When TO3FM is first entered as the WSJT-X DXCall JTAlert will correctly show "Martinique" in the log fields area and then a short time later when the XML data is returned will automatically change to "France" because of the incorrect dxcc number in the data.

de Laurie VK3AMA


locked Re: Double entries on JTAlert Decodes window with instances / Clue

HamApps Support (VK3AMA)
 

On 5/02/2020 8:58 am, asobel@... wrote:

It shows:

 

DH Filter Status

Active Filters

Show only Alerts

Hide worked B4

Hide Ignored

 

Amos 4X4MF

OK,

That didn't help. Using the same filtering settings I am not seeing any duplication of records.

How many JTAlert instances are you running?
What is the size of the Decodes database as shown in the status bar, number of records and size in brackets?

de Laurie VK3AMA


locked Re: country conflict

Dave Garber
 

chalk it up to another error using QRZ...   ok, I have seen this many times... cant blame qrz though, most errors are user input, i think


Dave Garber
VE3WEJ / VE3IE


On Tue, Feb 4, 2020 at 8:45 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 5/02/2020 12:33 pm, Dave Garber wrote:
please see attachment, the TO on the air now from Martinique, seen in the little box, but the log line shows france....

is this a bug??

running jtalert 2.15.8.0

The only bug is with the user who maintains the TO3FM data on QRZ.com.
The XML data returned from a QRZ XML lookup uses a dxcc code of 227, which is France.

part of the XML data...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
When TO3FM is first entered as the WSJT-X DXCall JTAlert will correctly show "Martinique" in the log fields area and then a short time later when the XML data is returned will automatically change to "France" because of the incorrect dxcc number in the data.

de Laurie VK3AMA


locked Re: country conflict

HamApps Support (VK3AMA)
 

On 5/02/2020 12:33 pm, Dave Garber wrote:
please see attachment, the TO on the air now from Martinique, seen in the little box, but the log line shows france....

is this a bug??

running jtalert 2.15.8.0

The only bug is with the user who maintains the TO3FM data on QRZ.com.
The XML data returned from a QRZ XML lookup uses a dxcc code of 227, which is France.

part of the XML data...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>TO3FM</call>
<dxcc>227</dxcc>
<fname>Kan</fname>
<name>Yokota</name>
<addr2>Ducos</addr2>
<country>Martinique</country>
When TO3FM is first entered as the WSJT-X DXCall JTAlert will correctly show "Martinique" in the log fields area and then a short time later when the XML data is returned will automatically change to "France" because of the incorrect dxcc number in the data.

de Laurie VK3AMA


locked country conflict

Dave Garber
 

please see attachment, the TO on the air now from Martinique, seen in the little box, but the log line shows france....

is this a bug??

running jtalert 2.15.8.0


locked Re: Double entries on JTAlert Decodes window with instances / Clue

asobel@...
 

Laurie

 

It shows:

 

DH Filter Status

Active Filters

Show only Alerts

Hide worked B4

Hide Ignored

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ג 04 פברואר 2020 22:37
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Double entries on JTAlert Decodes window with instances / Clue

 

On 4/02/2020 4:52 pm, asobel@... wrote:

Here is your clue. See the attached files. It's just the filter.

Amos 4X4MF


Amos,

Please post an image of your Decodes Filter status when your getting the doubled decodes display. Use the "Filter -> View detailed Filter status" menu.

de Laurie VK3AMA


locked Re: False alert for P29ZL

Phil Cooper
 

Uwe and Laurie,

 

I’ve just had a look at the data from this, and it looks like I saw the 3Z90IARU calling T6AA, as T6AA had been shown in the JTAlert box. As it happened, HF90IARU had indeed called him and because there were so many calls, I only noticed 3Z90IARU.

 

Anyway, I am pleased you have identified the problem, and it is now fixed.

 

73 de Phil GU0SUP

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Uwe
Sent: 03 February 2020 10:16
To: Support@HamApps.groups.io
Subject: [HamApps] False alert for P29ZL

 

Hi Laurie,
I don't know if this has already been reported. This morning I got a false alert for P29ZL. OL725PLZ was calling that station. Looks like that two special callsigns were trying to call each other. Maybe a hash code collision? Anyway, JTAlert shouldn't have alerted me because P29ZL was not calling but getting called. (And likely due to this I've falsly posted P29ZL to Hamspots.net.)
73 de Uwe, DG2YCB


locked Re: Double entries on JTAlert Decodes window with instances / Clue

HamApps Support (VK3AMA)
 

On 4/02/2020 4:52 pm, asobel@... wrote:

Here is your clue. See the attached files. It's just the filter.

Amos 4X4MF


Amos,

Please post an image of your Decodes Filter status when your getting the doubled decodes display. Use the "Filter -> View detailed Filter status" menu.

de Laurie VK3AMA