Date   

locked Re: DXCC entity OA

Björn SM7IUN
 

Thanks Laurie,

I thought JTAlert maintained it's own DXCC entity table and did not rely on external data for this.

The reason I found the issue was that I worked him a few minutes before the screen shot was taken.

When logging the contact DXKeeper showed a popup with a response from ClubLog saying that Austria was
not correct and it would use Peru instead. DXKeeper logged it as Austria and I of course manually updated it to Peru. 

The screen shot is taken after this update, meaning that the QSO in DXKeeper is set to Peru with CQ Zone 12, ITU Zone 12 and grid FH43. All correct.

But if JTAlert makes it's display decision based on its internal QSO data base it would still be wrong. Until the next log scan.

I will check with Dave if a callbook lookup can override a call signs DXCC entity in DXKeeper. 

If it can, and DXKeeper overrides JTAlert's own conclusion on DXCC entity, I think we have identified the reason.

And this post should had been in the DXLab group...

73,

Björn SM7IUN









2017-10-23 21:19 GMT+02:00 HamApps Support (VK3AMA) <vk3ama.ham.apps@...>:

On 24/10/2017 2:39 AM, Björn Ekelund wrote:
I thought that was obvious from the title of the post?

OA6Q is flagged as Austria in the screen shot...

Björn SM7IUN


2017-10-23 17:21 GMT+02:00 Mike Anderson <mike@...>:


you did not explain the defect  Bjorn and how to duplicate it?


On 10/23/2017 9:27 AM, Björn Ekelund wrote:

I think I may have found a defect. 

Infogad bild 1

73

Björn SM7IUN


Björn,

Sorry, It wasn't obvious to me what the problem was from your original post. To me as a non-European, I didn't immediately notice that an OA call was incorrect for Austria, (OE primary prefix).

Regarding OA6Q being shown as Austria (dxcc=206) rather than the correct Peru (dxcc=136), I cannot replicate what you observed. JTAlert is correctly identifying OA6Q as being in Peru.

I note from you image that his was a B4 from a previous QSO. I suggest that you examine your DXKeeper log closely and check that any entries for OA6Q have the correct Country, Continent and Zone data recorded. It is likely one or more entries will be incorrect.

If you log contains incorrect Country data for OA6Q entries, the only explanation I have is that the incorrect data entered your log somehow due to bad XML data returned from a QRZ XML lookup. The QRZ XML data is incorrect (see end of this message) and incorrectly identifies the dxcc as 206 (Austria).
The owner of the OA6Q callsign has set it as an alias for his primary callsign OE3NHW, rather than a callsign managed by OE3NHW

de Laurie VK3AMA
   
XML Lookup data fro OA6Q returned from QRZ.com...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>OE3NHW</call>
<xref>OA6Q</xref>
<aliases>OA6/OE3NHW,OA4/OE3NHW,OA6Q</aliases>
<dxcc>206</dxcc>
<fname>Hans Georg</fname>
<name>Hartl</name>
<addr1>Am Berg 4</addr1>
<addr2>3423 St. Andrä/ Wördern</addr2>
<country>Austria</country>
<lat>-16.396667</lat>
<lon>-71.543333</lon>
<grid>FH43fo</grid>
<ccode>19</ccode>
<land>Austria</land>
<codes>ETP</codes>
<qslmgr>EQSL, LOTW, VIA OE-BUREAU OR DIRECT</qslmgr>
<email>oe3nhw@...</email>
<u_views>90620</u_views>
<bio>5660</bio>
<biodate>2017-07-29 12:36:08</biodate>
<image>https://s3.amazonaws.com/files.qrz.com/w/oe3nhw/P1030220.jpg</image>
<imageinfo>768:1024:332681</imageinfo>
<moddate>2015-11-17 16:26:26</moddate>
<eqsl>1</eqsl>
<mqsl>1</mqsl>
<cqzone>10</cqzone>
<ituzone>12</ituzone>
<born>1946</born>
<lotw>1</lotw>
<user>OE3NHW</user>
<geoloc>user</geoloc>
</Callsign>
<Session>
<Key>e66c3d771737e44bb3dc8107cc3e1d14</Key>
<Count>9963</Count>
<SubExp>Sat Nov 11 00:00:00 2017</SubExp>
<GMTime>Mon Oct 23 18:48:06 2017</GMTime>
<Remark>cpu: 0.041s</Remark>
</Session>
</QRZDatabase>




locked Re: DXCC entity OA

Steve Case <artcase@...>
 

Thank you Laurie, I really appreciate the help, I'm just not to smart.
Steve
WA7ETE
 
 
 


From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...>
Sent: Monday, October 23, 2017 12:30 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] DXCC entity OA
 
On 24/10/2017 2:27 AM, Steve Case wrote:

This pic makes me ask the question, how do you get the alert to display sig strength ?

 

Thanks I know this off topic, but could not find it.

WA7ETE

Open the JTAlert Settings, "Window" section. Under the "Extended Display" group enable the "Show dB (DXCC Name)" setting.

de Laurie VK3AMA
   


locked Re: DXCC entity OA

HamApps Support (VK3AMA)
 

On 24/10/2017 2:39 AM, Björn Ekelund wrote:
I thought that was obvious from the title of the post?

OA6Q is flagged as Austria in the screen shot...

Björn SM7IUN


2017-10-23 17:21 GMT+02:00 Mike Anderson <mike@...>:


you did not explain the defect  Bjorn and how to duplicate it?


On 10/23/2017 9:27 AM, Björn Ekelund wrote:

I think I may have found a defect. 

Infogad bild 1

73

Björn SM7IUN


Björn,

Sorry, It wasn't obvious to me what the problem was from your original post. To me as a non-European, I didn't immediately notice that an OA call was incorrect for Austria, (OE primary prefix).

Regarding OA6Q being shown as Austria (dxcc=206) rather than the correct Peru (dxcc=136), I cannot replicate what you observed. JTAlert is correctly identifying OA6Q as being in Peru.

I note from you image that his was a B4 from a previous QSO. I suggest that you examine your DXKeeper log closely and check that any entries for OA6Q have the correct Country, Continent and Zone data recorded. It is likely one or more entries will be incorrect.

If you log contains incorrect Country data for OA6Q entries, the only explanation I have is that the incorrect data entered your log somehow due to bad XML data returned from a QRZ XML lookup. The QRZ XML data is incorrect (see end of this message) and incorrectly identifies the dxcc as 206 (Austria).
The owner of the OA6Q callsign has set it as an alias for his primary callsign OE3NHW, rather than a callsign managed by OE3NHW

de Laurie VK3AMA
   
XML Lookup data fro OA6Q returned from QRZ.com...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.33" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>OE3NHW</call>
<xref>OA6Q</xref>
<aliases>OA6/OE3NHW,OA4/OE3NHW,OA6Q</aliases>
<dxcc>206</dxcc>
<fname>Hans Georg</fname>
<name>Hartl</name>
<addr1>Am Berg 4</addr1>
<addr2>3423 St. Andrä/ Wördern</addr2>
<country>Austria</country>
<lat>-16.396667</lat>
<lon>-71.543333</lon>
<grid>FH43fo</grid>
<ccode>19</ccode>
<land>Austria</land>
<codes>ETP</codes>
<qslmgr>EQSL, LOTW, VIA OE-BUREAU OR DIRECT</qslmgr>
<email>oe3nhw@...</email>
<u_views>90620</u_views>
<bio>5660</bio>
<biodate>2017-07-29 12:36:08</biodate>
<image>https://s3.amazonaws.com/files.qrz.com/w/oe3nhw/P1030220.jpg</image>
<imageinfo>768:1024:332681</imageinfo>
<moddate>2015-11-17 16:26:26</moddate>
<eqsl>1</eqsl>
<mqsl>1</mqsl>
<cqzone>10</cqzone>
<ituzone>12</ituzone>
<born>1946</born>
<lotw>1</lotw>
<user>OE3NHW</user>
<geoloc>user</geoloc>
</Callsign>
<Session>
<Key>e66c3d771737e44bb3dc8107cc3e1d14</Key>
<Count>9963</Count>
<SubExp>Sat Nov 11 00:00:00 2017</SubExp>
<GMTime>Mon Oct 23 18:48:06 2017</GMTime>
<Remark>cpu: 0.041s</Remark>
</Session>
</QRZDatabase>



locked Re: DXCC entity OA

HamApps Support (VK3AMA)
 

On 24/10/2017 2:27 AM, Steve Case wrote:

This pic makes me ask the question, how do you get the alert to display sig strength ?

 

Thanks I know this off topic, but could not find it.

WA7ETE

Open the JTAlert Settings, "Window" section. Under the "Extended Display" group enable the "Show dB (DXCC Name)" setting.

de Laurie VK3AMA
   


locked Re: DXCC entity OA

Mike Anderson
 

Steve  Click on the  View Menu and then select  Show DXCC Names   That should do it.

K5NAN

On 10/23/2017 10:27 AM, Steve Case wrote:

This pic makes me ask the question, how do you get the alert to display sig strength ?

 

Thanks I know this off topic, but could not find it.

WA7ETE

 

 

 



locked Re: DXCC entity OA

artcase@...
 

This pic makes me ask the question, how do you get the alert to display sig strength ?

 

Thanks I know this off topic, but could not find it.

WA7ETE

 

 

 


locked Re: DXCC entity OA

Arnolds Preiss
 

OA6Q operator is from Austria and in QRZ.com ishis Austrian address…

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Björn Ekelund
Sent: Monday, October 23, 2017 6:40 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] DXCC entity OA

 

I thought that was obvious from the title of the post?

 

OA6Q is flagged as Austria in the screen shot...

 

Björn SM7IUN

 

 

2017-10-23 17:21 GMT+02:00 Mike Anderson <mike@...>:

 

you did not explain the defect  Bjorn and how to duplicate it?

 

On 10/23/2017 9:27 AM, Björn Ekelund wrote:

I think I may have found a defect. 

 

Infogad bild 1

 

73

 

Björn SM7IUN

 

 

 


locked Re: DXCC entity OA

Mike Anderson
 

I did not read the  title closely    Bjorn   I was focused on the   image  

tnx



On 10/23/2017 10:39 AM, Björn Ekelund wrote:

I thought that was obvious from the title of the post?

OA6Q is flagged as Austria in the screen shot...

Björn SM7IUN


2017-10-23 17:21 GMT+02:00 Mike Anderson <mike@...>:


you did not explain the defect  Bjorn and how to duplicate it?


On 10/23/2017 9:27 AM, Björn Ekelund wrote:

I think I may have found a defect. 

Infogad bild 1

73

Björn SM7IUN





locked Re: DXCC entity OA

Björn SM7IUN
 

I thought that was obvious from the title of the post?

OA6Q is flagged as Austria in the screen shot...

Björn SM7IUN


2017-10-23 17:21 GMT+02:00 Mike Anderson <mike@...>:


you did not explain the defect  Bjorn and how to duplicate it?


On 10/23/2017 9:27 AM, Björn Ekelund wrote:

I think I may have found a defect. 

Infogad bild 1

73

Björn SM7IUN




locked Re: DXCC entity OA

Mike Anderson
 


you did not explain the defect  Bjorn and how to duplicate it?


On 10/23/2017 9:27 AM, Björn Ekelund wrote:

I think I may have found a defect. 

Infogad bild 1

73

Björn SM7IUN



locked DXCC entity OA

Björn SM7IUN
 

I think I may have found a defect. 

Infogad bild 1

73

Björn SM7IUN


locked Re: FT 8 ???

N7AED <signalhz@...>
 

I don’t have a Pro 3 any more but it does work with WSJT-X,JT65-HF and all the other ham programs

73 Eddy N7AED

Sent from my iPhone

On Oct 22, 2017, at 9:49 PM, Jim - N4ST <newsgroup@...> wrote:

Apples and oranges.
Actually, Joe Large did JT65-HF using Joe Taylors algorithms.
JT-Alert is a third-party sidekick program originally for JT65-HF, but now covers many variations including the dominant WSJT-X.

_________
73,
Jim - N4ST

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of James Hertel
Sent: Sunday, October 22, 2017 23:01
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FT 8 ???

I appreciate all that have responded... your info help greatly.
By the way.. this support group originally started when Joe Large was writing his programs for jt65. When he got out JT-AlERT took over.
Also !!
HAS Anyone tried to connect a Icom 756 III to JT8 program??? Havin a bit of difficulty in makin it all work.
Jim





locked Re: FT 8 ???

Jim - N4ST
 

Apples and oranges.
Actually, Joe Large did JT65-HF using Joe Taylors algorithms.
JT-Alert is a third-party sidekick program originally for JT65-HF, but now covers many variations including the dominant WSJT-X.

_________
73,
Jim - N4ST

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of James Hertel
Sent: Sunday, October 22, 2017 23:01
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FT 8 ???

I appreciate all that have responded... your info help greatly.
By the way.. this support group originally started when Joe Large was writing his programs for jt65. When he got out JT-AlERT took over.
Also !!
HAS Anyone tried to connect a Icom 756 III to JT8 program??? Havin a bit of difficulty in makin it all work.
Jim


locked Re: FT 8 ???

James Hertel <n6kmr@...>
 

I appreciate all that have responded... your info help greatly.

By the way.. this support group originally started when Joe Large was writing his programs for jt65. When he got out JT-AlERT took over.

Also !!

HAS Anyone tried to connect a Icom 756 III to JT8 program??? Havin a bit of difficulty in makin it all work.

Jim


On 10/20/2017 5:43 PM, neil_zampella wrote:

A few things:

1.   This is the JT-Alert support group.  It is for support of the JT-Alert program which is a third-party program that provides support for the WSJT-X program.

2.   The WSJT-X support group is called wsjtgroup and its on Groups.Yahoo.com

3.   As has been pointed out, you downloaded the wrong program.  GO TO THE BOTTOM of K1JT's WSJT-X page to find the v1.8.0-RC3 release candidate that has FT8.

4.   After you install, READ the Readme file, and then the built-in USERS GUIDE, and do the tutorials that are included.   They will literally HOURS of messing around with settings.

73,

Neil, KN3ILZ



locked Re: Issue with Call Sign Display Lines #3 & #4 - Defect Confirmed.

Stephen - K6SJT
 

Thank you Laurie -

And, as others have mentioned, we're grateful for the time, energy, and enthusiasm you are constantly investing in JTAlert for the benefit of us all. 

73,
Stephen - K6SJT


locked Re: Issue with Call Sign Display Lines #3 & #4

Stephen - K6SJT
 

This occurs when starting JTAlert with two lines (my normal mode for operation), then when traffic increases, I open three lines, and if necessary the forth line..


locked Re: JTAlertX

Ed
 

Dah!!!!!!!!!!

 

Tank you Laurie, I see it in the settings and understand now.

 

Have a nice day and thanks for a great program.

 

Regards Ed WA6WGS

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, October 22, 2017 11:14 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlertX

 

On 23/10/2017 4:35 AM, Ed wrote:

Good morning,

Have been using JTAlert for a couple of months, and it is great.

Been a ham for a long long time, but can not figure out in the Decodes History window, what the columns "L" and "E" with check marks represent?

Can someone please bring me up to speed?

Thanks ED WA6WGS


Ed,

"L" and "E" are shorthand (to keep the column width to a minimum) for "LoTW" and "eQSL(AG)" respectively.

de Laurie VK3AMA
   


locked Re: Waiting for JTDX to start (wsjtx.exe)

HamApps Support (VK3AMA)
 

On 22/10/2017 8:09 PM, HamApps Support (VK3AMA) wrote:
or if you have WSJT-X installed, start WSJT-X and JTDX and then open the Settings

That should read "or if you have WSJT-X installed, start WSJT-X and JTAlert and then open the Settings"

de Laurie VK3AMA
   


locked Re: JTAlertX

HamApps Support (VK3AMA)
 

On 23/10/2017 4:35 AM, Ed wrote:
Good morning,

Have been using JTAlert for a couple of months, and it is great.

Been a ham for a long long time, but can not figure out in the Decodes History window, what the columns "L" and "E" with check marks represent?

Can someone please bring me up to speed?

Thanks ED WA6WGS

Ed,

"L" and "E" are shorthand (to keep the column width to a minimum) for "LoTW" and "eQSL(AG)" respectively.

de Laurie VK3AMA
   


locked JTAlertX

Ed
 

Good morning,

Have been using JTAlert for a couple of months, and it is great.

Been a ham for a long long time, but can not figure out in the Decodes History window, what the columns "L" and "E" with check marks represent?

Can someone please bring me up to speed?

Thanks ED WA6WGS