Date   

locked JTAlert Shortcut Issue

W7JHR@...
 

I just downloaded the latest version.  During the download process I only checked the shortcut box for WSJT-X and left the others blank.  The red icon showed up on my computer screen as usual.  When I clicked on the icon, I received a message that stated "Problem with shortcut.  The item JTAlert .eve that this shortcut refers has been changed or moved, so the shortcut will no longer work properly.  Do you want to delete this shortcut?"  I clicked yes.  Any ideas why  this is happening and how do I fix it?

Thanks,
Jim W7JHR


locked Are you using WSJT-X / JTAlert / ACLog / QRZ XML database.

Paul-N5DUP
 

If so, and you have ACLog auto populating Name, County, and Comments fields with data from QRZ XML data, I would really appreciate a comparison of settings in the 3 apps. 

Thanks,
Paul
N5DUP


locked Re: JTAlert and Comments field of logfile

Jim N6VH
 

Paul,

I replied to your earlier message before I saw this one. Yes, in your case you would not want WSJT-X to populate any fields. In logging to ACLog from JTAlert, things like QTH, etc, are sent to "Other" fields, as you have probably already seen under the ACLog section of JTAlert. Maybe Laurie will have an answer that works for you.

73,

Jim N6VH

On 2/12/2020 12:36 PM, Paul-N5DUP wrote:
Jim,

There were several fields in the JTAlerx Logging Options box that pertain to data displayed from XML lookups and I checked all of them but that didn’t seem to work, still nothing in the Comments field.  And just FYI, for ACLog to populate the Comments field with XML data,  WSJT-X CANNOT be putting dB signal reports (or anything else for that matter) into the Comments field.

Paul
N5DUP


On Feb 12, 2020, at 1:45 PM, Paul B. <paul@...> wrote:

Jim, 

First, thank you for your response! I use ACLog as my logging program. I also subscribe to QRZ’s XML call database. ACLog queries that database and populates several fields in its log like Name and County, which is being populated. But the Address is supposed to be in the Comments field and it is not. Thanks to you I have found several XML check boxes in the Logging Options Box that I think need to be checked. Waiting to make a contact to test it now. Thanks

73,
Paul
N5DUP



On Feb 12, 2020, at 1:21 PM, Jim N6VH <N6VH@...> wrote:



Paul,

Go to Settings/Manage Settings/Logging. In the Logging Options Box, scroll down until you see "Log WSJT-X Comments to QSL Message Field", and check that box.

In WSJT-X, go to Settings/Reporting. Check the box that says "dB reports to comments".

Is that what you are looking for?

73,

Jim N6VH

On 2/12/2020 7:39 AM, Paul-N5DUP wrote:
Does JTAlert have to be configured to pass Comments field data?

Paul
N5DUP


locked Re: JTAlert and Comments field of logfile

Paul-N5DUP
 

Jim,

There were several fields in the JTAlerx Logging Options box that pertain to data displayed from XML lookups and I checked all of them but that didn’t seem to work, still nothing in the Comments field.  And just FYI, for ACLog to populate the Comments field with XML data,  WSJT-X CANNOT be putting dB signal reports (or anything else for that matter) into the Comments field.

Paul
N5DUP


On Feb 12, 2020, at 1:45 PM, Paul B. <paul@...> wrote:

Jim, 

First, thank you for your response! I use ACLog as my logging program. I also subscribe to QRZ’s XML call database. ACLog queries that database and populates several fields in its log like Name and County, which is being populated. But the Address is supposed to be in the Comments field and it is not. Thanks to you I have found several XML check boxes in the Logging Options Box that I think need to be checked. Waiting to make a contact to test it now. Thanks

73,
Paul
N5DUP



On Feb 12, 2020, at 1:21 PM, Jim N6VH <N6VH@...> wrote:



Paul,

Go to Settings/Manage Settings/Logging. In the Logging Options Box, scroll down until you see "Log WSJT-X Comments to QSL Message Field", and check that box.

In WSJT-X, go to Settings/Reporting. Check the box that says "dB reports to comments".

Is that what you are looking for?

73,

Jim N6VH

On 2/12/2020 7:39 AM, Paul-N5DUP wrote:
Does JTAlert have to be configured to pass Comments field data?

Paul
N5DUP


locked Re: JTAlert and Comments field of logfile

Jim N6VH
 

Paul,

Very good. I wasn't sure which comments you wanted logged. Hope this works for you.

73,

Jim N6VH

On 2/12/2020 11:45 AM, Paul-N5DUP wrote:
Jim, 

First, thank you for your response! I use ACLog as my logging program. I also subscribe to QRZ’s XML call database. ACLog queries that database and populates several fields in its log like Name and County, which is being populated. But the Address is supposed to be in the Comments field and it is not. Thanks to you I have found several XML check boxes in the Logging Options Box that I think need to be checked. Waiting to make a contact to test it now. Thanks

73,
Paul
N5DUP



On Feb 12, 2020, at 1:21 PM, Jim N6VH <N6VH@...> wrote:



Paul,

Go to Settings/Manage Settings/Logging. In the Logging Options Box, scroll down until you see "Log WSJT-X Comments to QSL Message Field", and check that box.

In WSJT-X, go to Settings/Reporting. Check the box that says "dB reports to comments".

Is that what you are looking for?

73,

Jim N6VH

On 2/12/2020 7:39 AM, Paul-N5DUP wrote:
Does JTAlert have to be configured to pass Comments field data?

Paul
N5DUP


locked Re: JTAlert and Comments field of logfile

Paul-N5DUP
 

Jim, 

First, thank you for your response! I use ACLog as my logging program. I also subscribe to QRZ’s XML call database. ACLog queries that database and populates several fields in its log like Name and County, which is being populated. But the Address is supposed to be in the Comments field and it is not. Thanks to you I have found several XML check boxes in the Logging Options Box that I think need to be checked. Waiting to make a contact to test it now. Thanks

73,
Paul
N5DUP



On Feb 12, 2020, at 1:21 PM, Jim N6VH <N6VH@...> wrote:



Paul,

Go to Settings/Manage Settings/Logging. In the Logging Options Box, scroll down until you see "Log WSJT-X Comments to QSL Message Field", and check that box.

In WSJT-X, go to Settings/Reporting. Check the box that says "dB reports to comments".

Is that what you are looking for?

73,

Jim N6VH

On 2/12/2020 7:39 AM, Paul-N5DUP wrote:
Does JTAlert have to be configured to pass Comments field data?

Paul
N5DUP


locked Re: JTAlert and Comments field of logfile

Jim N6VH
 

Paul,

Go to Settings/Manage Settings/Logging. In the Logging Options Box, scroll down until you see "Log WSJT-X Comments to QSL Message Field", and check that box.

In WSJT-X, go to Settings/Reporting. Check the box that says "dB reports to comments".

Is that what you are looking for?

73,

Jim N6VH

On 2/12/2020 7:39 AM, Paul-N5DUP wrote:
Does JTAlert have to be configured to pass Comments field data?

Paul
N5DUP


locked JTAlert and Comments field of logfile

Paul-N5DUP
 

Does JTAlert have to be configured to pass Comments field data?

Paul
N5DUP


locked Re: audio

lozere15@...
 

Thank you for your advice
73 friendship


locked Re: JTAlert New error message

HamApps Support (VK3AMA)
 

On 12/02/2020 12:13 pm, Ian Turner via Groups.Io wrote:
I noticed the CQ Zone is now omitted when using QRZ XML on HRD all versions. This has only occurred since the JT Alert version 2.15.9

Does anyone have any ideas on how to fix this?

I returned to version 2.15.7 and all is well but am concerned about the update

Ian
km4cqg
This was corrected a couple of days ago.
See https://hamapps.groups.io/g/Support/message/27731

de Laurie VK3AMA


locked Re: JTAlert New error message

Ian Turner <flyjets01@...>
 

I noticed the CQ Zone is now omitted when using QRZ XML on HRD all versions. This has only occurred since the JT Alert version 2.15.9

Does anyone have any ideas on how to fix this?

I returned to version 2.15.7 and all is well but am concerned about the update

Ian
km4cqg


locked Re: Callsign Database V2020.02.06

Jim N6VH
 

I also use Norton 360. I tested this with the latest versions of Firefox, Edge and Chrome. I didn't get any error messages with any browser. Everything worked fine here. It might be something in your settings, either in your browsers, or in Norton.

73,

Jim N6VH

On 2/11/2020 8:38 AM, bmorris106@... wrote:
Try running the Database on both Firefox and Edge.  PC security software is Norton 360. 
on Edge I get this message

Can’t connect securely to this page

This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

On Firefox I get this;
Secure Connection Failed

An error occurred during a connection to dnl.hamapps.com. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

_._,_._,_



locked Re: Callsign Database V2020.02.06

bmorris106@...
 

Try running the Database on both Firefox and Edge.  PC security software is Norton 360. 
on Edge I get this message

Can’t connect securely to this page

This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

On Firefox I get this;
Secure Connection Failed

An error occurred during a connection to dnl.hamapps.com. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.


locked Re: JTAlert New error message

Paul-N5DUP
 

Laurie,

Thank you for your reply and answer.  I sincerely apologize for having to ask for help. I had read about the QSO confirmation time and in fact had already stretched it from 5 sec. to 10 sec. which did not help. I think maybe the ACLog .mdb log file got corrupted somehow because I overwrote the backup to it and no more problems confirming the QSO. Thank you and sorry for the trouble.

Paul
N5DUP


On Feb 10, 2020, at 8:19 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 11/02/2020 11:42 am, Paul-N5DUP wrote:

So I have WSJT-X prompting me when it is ready to log a contact. Until now JTAlerts confirms that it is logging to ACLog and all was well. Now I am getting this message from JTAlert that says.

Failure: QSO not logged

Error Message: ACLOG File unable to confirm QSO logged 

Not sure what has changed but any ideas what I should look for?

I’m not sure what to look for. Any help appreciated.

Thank you,
Paul
N5DUP

This has been discussed many times.

This error message indicates that JTAlert was unable to confirm that the QSO was successfully logged. It does this by performing a direct read of your Loggers log file/database. JTAlert doesn't rely on the logging status produced by some loggers which have shown to incorrectly indicate successful logging even when failing to log the QSO. Also some loggers don't provide any feedback at all when logging via their API, so JTAlert always tries to confirm success/failure via a direct log/database read.

If the QSOs are indeed getting logged you will need to increase the "Check QSO Log Record" time. See the Logging section of the JTAlert Settings window.

Very likely the post logging activities being performed by your logger are being impacted by Internet access speeds resulting in later than normal logging. Typical examples are post logging XML lookups or posting the QSO to online logs.

de Laurie VK3AMA


locked Re: JTAlert New error message

HamApps Support (VK3AMA)
 

On 11/02/2020 11:42 am, Paul-N5DUP wrote:

So I have WSJT-X prompting me when it is ready to log a contact. Until now JTAlerts confirms that it is logging to ACLog and all was well. Now I am getting this message from JTAlert that says.

Failure: QSO not logged

Error Message: ACLOG File unable to confirm QSO logged 

Not sure what has changed but any ideas what I should look for?

I’m not sure what to look for. Any help appreciated.

Thank you,
Paul
N5DUP

This has been discussed many times.

This error message indicates that JTAlert was unable to confirm that the QSO was successfully logged. It does this by performing a direct read of your Loggers log file/database. JTAlert doesn't rely on the logging status produced by some loggers which have shown to incorrectly indicate successful logging even when failing to log the QSO. Also some loggers don't provide any feedback at all when logging via their API, so JTAlert always tries to confirm success/failure via a direct log/database read.

If the QSOs are indeed getting logged you will need to increase the "Check QSO Log Record" time. See the Logging section of the JTAlert Settings window.

Very likely the post logging activities being performed by your logger are being impacted by Internet access speeds resulting in later than normal logging. Typical examples are post logging XML lookups or posting the QSO to online logs.

de Laurie VK3AMA


locked Re: Callsign Database V2020.02.06

HamApps Support (VK3AMA)
 

On 11/02/2020 12:51 pm, bmorris106@... wrote:

 

Can’t connect securely to this page

This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

There is nothing wrong with or outdated about the HamApps SSL certificates.

The error your getting is likely coming from your Protection software or your browser. Try an different browser.

de Laurie VK3AMA


locked Re: Callsign Database V2020.02.06

bmorris106@...
 

No, that didn't work either

 

Can’t connect securely to this page

This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.


locked JTAlert New error message

Paul-N5DUP
 

So I have WSJT-X prompting me when it is ready to log a contact. Until now JTAlerts confirms that it is logging to ACLog and all was well. Now I am getting this message from JTAlert that says.

Failure: QSO not logged

Error Message: ACLOG File unable to confirm QSO logged 

Not sure what has changed but any ideas what I should look for?

I’m not sure what to look for. Any help appreciated.

Thank you,
Paul
N5DUP


locked Re: Callsign Database V2020.02.06

Dave Morton
 


locked Callsign Database V2020.02.06

bmorris106@...
 

Can not download the database, getting this error;

Secure Connection Failed
An error occurred during a connection to dnl.hamapps.com. SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

Is there a fix, never had this problem before.

Thanks  Bob  WA3THL