Date   

locked Re: JTAlertX 2.12.10

Tim Davis KJ4DHF
 

Laurie,

It working this morning just fine. I did check for JTAlertHamSpots.Plugin in my task manager it was there and yesterday it made no difference if firewall was on/off as I did check that before posting. The gremlin gone for now
thanks for help.

KJ4DHF
Tim


locked Re: JTAlertX 2.12.10

HamApps Support (VK3AMA)
 

On 24/01/2019 10:34 am, kj4dhf via Groups.Io wrote:

Yes I am sure it is ticked. I even went on FT-8 page to make sure I was not on blocked calls list in case I had sent spots wrong. And I used WSJTX to send spots to psk reporter so I could see where I was being heard


Since you have the spotting enabled, the likely cause of no spots is that the "JTAlertHamSpots.Plugin" is not running or it is being interfered with by your Virus/Malware protection. Check taskmanager to see if "JTAlertHamSpots.Plugin" is present. If it isn't check your Virus protection to see if it is blocking the starting of the process.

I might see something in your JTAlert files, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: NULL Country for TO7D

Jim Reisert AD1C
 

On Wed, Jan 23, 2019 at 4:43 PM Jim Reisert AD1C wrote:

There is something wrong with my software. TO7D should have been
added to the country file(s) on January 14, but it was not:
I found the problem! My data file had some unwanted blank space
characters in it. The software was checking for those, and writing
the errors to a log file, but nothing looked for errors in that log
file! I moved the check somewhere else where any such problem will
cause an obvious failure very early on, that must be dealt with
(fixed) before continuing.

I'll be releasing a new country file in the next day or so.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us


locked Re: NULL Country for TO7D

Jim Reisert AD1C
 

There is something wrong with my software. TO7D should have been
added to the country file(s) on January 14, but it was not:

http://www.country-files.com/cty-2901-14-january-2019/

I need to see what's wrong. I plan to do a release soon.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us


locked Re: JTAlertX 2.12.10

Tim Davis KJ4DHF
 

Hi Laurie,

Yes I am sure it is ticked. I even went on FT-8 page to make sure I was not on blocked calls list in case I had sent spots wrong. And I used WSJTX to send spots to psk reporter so I could see where I was being heard.


locked JTAlert 2.12.10 “Not Responding”

Vern NJ8L
 

Equipment lineup. JTAlert 2.12.10, WSJT-X 2.0.0, HRD 6.3.0.524 (no rig control), TS-2000, Signalink USB, Win 7

All works first few QSOs/logging. The JTAlert then fails to display WSJT-X decodes after logging a QSO. Selecting the Alert status bar shows “not responding “. After a few sessions Alert will start displaying correctly while JT-x always decoded while Alert was not responding. Makes no difference if double clicking on the call sign in JT-X or JTAlert when selecting the new QSO partner. 

Any suggestion(s) as to where I can look to point me in the direction to rectify this problem?

Vern - NJ8L


locked Re: Logging incorrect DXCC Country

HamApps Support (VK3AMA)
 

On 24/01/2019 2:37 am, Bill Engel wrote:
It appears that JTAlert is logging PJ4P as Curacao instead of Bonaire.  The XML lookup from qrz.com shows Bonaire.

Bill K5DHY

Bill sorry, but your mistaken.

JTAlert correctly identifies PJ4P as Bonaire (DXCC - 520) for both decoding and logging.
The problem is that the XML data from QRZ.com is incorrect, listing the DXCC as 517, Curacao
There is nothing that JTAlert can do if the QRZ listing maintainer gets it wrong. "Garbage In = Garbage Out".

Decoding...

   

Logging (without XML lookup)...

   

Logging after the QRZ XML Lookup...

   

While the QRZ webpage shows Bonaire, that is only the address field typically used for QSLing, but can be used for other purposes. This is not the XML data.

   

The QRZ XML data contains a dxcc field that identifies the Country. For PJ4P this has been entered wrong.

   

de Laurie VK3AMA


locked Re: Logging incorrect DXCC Country

Bill Engel
 

It appears that JTAlert is logging PJ4P as Curacao instead of Bonaire.  The XML lookup from qrz.com shows Bonaire.

Bill K5DHY


locked Re: JTAlertX 2.12.10

HamApps Support (VK3AMA)
 

On 23/01/2019 10:28 pm, kj4dhf via Groups.Io wrote:
Not sending decoded call signs to hamspots.net.
1) send spots to hamspots.net  is ticked
2) under web services  says tcp connect ok for port 49521

Any ideas ?

Tim
KJ4DHF
Are you sure you have spotting to HamSpots enabled?
I checked the database on HamSpots and all spots from
KJ4DHF are from PSKReporter, none from JTAlert.

   

de Laurie VK3AMA


locked JTAlertX 2.12.10

Tim Davis KJ4DHF
 

Not sending decoded call signs to hamspots.net.
1) send spots to hamspots.net  is ticked
2) under web services  says tcp connect ok for port 49521

Any ideas ?

Tim
KJ4DHF


locked Re: Only seeing call sign display line

John <ve1cdd@...>
 

Hi, I see you are on John Goodwin's emailing list. He passed away on Jan 6th. I am sorry to be the bearer of bad news, but you will not be receiving any more correspondence from him. Liz Goodwin, lizgoodwin@...

On 22/01/2019 3:47 p.m., HamApps Support (VK3AMA) wrote:
On 23/01/2019 5:30 am, w2eck wrote:
 New install of v2.12.10 on windows 10 laptop, When I open JTAlert - all is ee are 2 call sign display lines. am missing the rest of the display. Everything else on laptop display is correctly sized. Any hints on how to fix?

73
Paul
w2ecN
If you can provide a screen-capture (of JTAlert only) that will help diagnose what is not working as you expect. See this topic https://hamapps.groups.io/g/Support/message/20528 for instructions on using the Windows snipping-tool for taking screen-captures.

If your missing the Log Fields area, that can be enabled via the View -> Show Log Fields menu, but only if you have one of the supported Loggers enabled. If "No Log" is shown in the title bar title text, the Log fields will not be displayed.

de Laurie VK3AMA



locked Re: Only seeing call sign display line

John <ve1cdd@...>
 

Hi, I see you are on John Goodwin's emailing list. He passed away on Jan 6th. I am sorry to be the bearer of bad news, but you will not be receiving any more correspondence from him. Liz Goodwin, lizgoodwin@...

On 22/01/2019 3:59 p.m., w2eck wrote:
LLaurie - that was it - Show Log Fields = Guess  I didn't know proper name for what I was missing. All set now.

tnx
Paul
w2eck



locked Re: Only seeing call sign display line

w2eck
 

Laurie - that was it - Show Log Fields = Guess  I didn't know proper name for what I was missing. All set now.

tnx
Paul
w2eck


locked Re: Only seeing call sign display line

HamApps Support (VK3AMA)
 

On 23/01/2019 5:30 am, w2eck wrote:
 New install of v2.12.10 on windows 10 laptop, When I open JTAlert - all is ee are 2 call sign display lines. am missing the rest of the display. Everything else on laptop display is correctly sized. Any hints on how to fix?

73
Paul
w2ecN
If you can provide a screen-capture (of JTAlert only) that will help diagnose what is not working as you expect. See this topic https://hamapps.groups.io/g/Support/message/20528 for instructions on using the Windows snipping-tool for taking screen-captures.

If your missing the Log Fields area, that can be enabled via the View -> Show Log Fields menu, but only if you have one of the supported Loggers enabled. If "No Log" is shown in the title bar title text, the Log fields will not be displayed.

de Laurie VK3AMA


locked Re: Only seeing call sign display line

Michael Black
 

Can you send a screenshot? (use the Snip tool).

de Mike W9MDB


On Tuesday, January 22, 2019, 12:30:39 PM CST, w2eck <eckerpw@...> wrote:


 New install of v2.12.10 on windows 10 laptop, When I open JTAlert - all is ee are 2 call sign display lines. am missing the rest of the display. Everything else on laptop display is correctly sized. Any hints on how to fix?

73
Paul
w2ecN


locked Only seeing call sign display line

w2eck
 

 New install of v2.12.10 on windows 10 laptop, When I open JTAlert - all is ee are 2 call sign display lines. am missing the rest of the display. Everything else on laptop display is correctly sized. Any hints on how to fix?

73
Paul
w2ecN


locked Re: Logging incorrect DXCC Country

Paul W5PF
 

You are correct Laurie, I had forgotten that JTAlert had the capability to do a lookup and can't remember why I turned it on. I found the setting and turned it off and now the logging is correct. Thanks for your patience and the great software.

73, Paul W5PF

On 1/21/2019 9:52 PM, HamApps Support (VK3AMA) wrote:
On 22/01/2019 2:10 pm, Paul W5PF wrote:
I have JTAlerts set up to log my WSJTX qsos to DXKeeper. I have noticed that when I log a portable callsign, such as P4/K3DMG, JTAlerts logs the country as the home country, in this case as USA. I have tried entering several portable calls in the DX Call box of WSJTX and they always appear in JTAlert as the  home country rather than the portable location. I can see this when I enable "Show Log Fields." The incorrect DXCC is then sent to my logging program (DXKeeper). Is this a bug or have I missed a setting somewhere?

Thanks,
Paul W5PF
Paul,

JTAlert correctly identifies
P4/K3DMG as being in Aruba.

   

Very likely, you have an XML Lookup enabled, and it is returning the wrong home call data.
My guess is your using HamQTH, is that correct?

From the QRZ listing for
K3DMG/P4

   

While QRZ XML returns no data for
P4/K3DMG, it does return incorrect US data for K3DMG/P4

HamQTH XML returns incorrect US Home Call data for both
P4/K3DMG & K3DMG/P4

There is nothing JTAlert can do if the XML lookup service your using returns the wrong data.

de Laurie VK3AMA


locked Re: Logging incorrect DXCC Country

HamApps Support (VK3AMA)
 

In addition to my last message.

If you want to examine the data returned from your XML service open the cached xml data file (using notepad or similar) stored at %localappdata%\HamApps\cache\xml\

eg. the HamQTH xml data for P4/K3DMG
<?xml version="1.0"?>
<HamQTH version="2.8" xmlns="http://www.hamqth.com">
    <search>
        <callsign>k3dmg</callsign>
        <nick>Russell</nick>
        <qth>Canton</qth>
        <country>United States</country>
        <adif>291</adif>
        <itu>8</itu>
        <cq>4</cq>
        <grid>EN90</grid>
        <adr_name>Russell L Sholley</adr_name>
        <adr_street1>5117 Beechgrove Ne</adr_street1>
        <adr_city>Canton</adr_city>
        <adr_zip>44705</adr_zip>
        <adr_country>United States</adr_country>
        <adr_adif>291</adr_adif>
        <us_state>OH</us_state>
        <us_county>Stark</us_county>
        <lotw>Y</lotw>
        <qsldirect>?</qsldirect>
        <qsl>?</qsl>
        <eqsl>Y</eqsl>
        <latitude>40.83</latitude>
        <longitude>-81.33</longitude>
        <continent>NA</continent>
        <utc_offset>5</utc_offset>
        <picture>http://www.hamqth.com/images/default/ts-480_with_hair.jpg</picture>
    </search>
</HamQTH>

de Laurie VK3AMA




locked Re: Logging incorrect DXCC Country

HamApps Support (VK3AMA)
 

On 22/01/2019 2:10 pm, Paul W5PF wrote:
I have JTAlerts set up to log my WSJTX qsos to DXKeeper. I have noticed that when I log a portable callsign, such as P4/K3DMG, JTAlerts logs the country as the home country, in this case as USA. I have tried entering several portable calls in the DX Call box of WSJTX and they always appear in JTAlert as the  home country rather than the portable location. I can see this when I enable "Show Log Fields." The incorrect DXCC is then sent to my logging program (DXKeeper). Is this a bug or have I missed a setting somewhere?

Thanks,
Paul W5PF
Paul,

JTAlert correctly identifies
P4/K3DMG as being in Aruba.

   

Very likely, you have an XML Lookup enabled, and it is returning the wrong home call data.
My guess is your using HamQTH, is that correct?

From the QRZ listing for
K3DMG/P4

   

While QRZ XML returns no data for
P4/K3DMG, it does return incorrect US data for K3DMG/P4

HamQTH XML returns incorrect US Home Call data for both
P4/K3DMG & K3DMG/P4

There is nothing JTAlert can do if the XML lookup service your using returns the wrong data.

de Laurie VK3AMA


locked Logging incorrect DXCC Country

Paul W5PF
 

I have JTAlerts set up to log my WSJTX qsos to DXKeeper. I have noticed that when I log a portable callsign, such as P4/K3DMG, JTAlerts logs the country as the home country, in this case as USA. I have tried entering several portable calls in the DX Call box of WSJTX and they always appear in JTAlert as the  home country rather than the portable location. I can see this when I enable "Show Log Fields." The incorrect DXCC is then sent to my logging program (DXKeeper). Is this a bug or have I missed a setting somewhere?

Thanks,
Paul W5PF

14561 - 14580 of 37715