1. Support@HamApps.groups.io
  2. Messages
   Date   
locked JTAlertX is logging QSO's in log4om, But still receive error message

David W0DHB <dave@...>
 

I just set up JTAlertX (2.10.7) with WSJT-x(1.8.0rc2) to work with Log4OM (1.30.0.0 Running in admin mode) .
The QSO's are being logged in Log4OM properly but JTAlertX reports an error 


Log4OM UDP port 2235
JTAlertX UDP port 2235
WSJT-X UDP port 2237
Log4OM MySQL port 3306 test connection is successful 

No obvious errors noted in Log4OM communicator log.

 using Win 10 Pro , MySQL 5.7
Any ideas ?
locked Re: LOTW and Log4OM

Rich McCabe
 

OK excellent.  Just wanted to be clear 😊

 

Merry Christmas

 

Rich

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jürgen Umstädter
Sent: Saturday, December 23, 2017 6:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Hi Rich,

i´ve understood this when i read your first post. Not a problem for me. I only said i´m still
waiting for the first Beta. B.t.w. i am a member of the L4O beta team ... I don´t need to
have an alpha for testing, HI ....

Have nice x-mas days ... Juergen, DF5WW ;-)8-)


Am 24.12.2017 um 00:12 schrieb Rich McCabe:

Just to be clear this is not an updated version. Just testing the LOTW fixes since I am one having issues so helping them verify the fix.

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jürgen Umstädter
Sent: Saturday, December 23, 2017 5:06 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Hi Rich,

sounds good. Still waiting for the first Beta ;-)8-)

Juergen, DF5WW

Am 23.12.2017 um 23:48 schrieb Rich McCabe:

Yea its not a big deal to do. Thanks for the updates in #3 and #4.


I currently have an alpha release of updated Log4OM that I am testing which is working fine.

 

I cant speak for them as far as timing but I would expect it to be public release shortly.

 

Rich

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, December 23, 2017 11:28 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Every time...and here's a slightly updated sequence

 

 

#0 Back it up!!!
#1 Open QSO Manager/QSO Archive
#2 Click Search Parameters at bottom
#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.  Close the window.
#4 Click Search at the top, then Select All
#5 Click Field Update
#6 Under "Execute custom update query" put this:
update log set state=SUBSTR(state,1,2) WHERE SUBSTR(state,4,2)="//"
#7 Click all 4 warning boxes and then the "I understand..." button underneath.

de Mike W9MDB

 

 

On Saturday, December 23, 2017, 11:16:51 AM CST, Lawrence Godek <LawrenceG94@...> wrote:

 

 

Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry

W0OGH

 

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 

 

 

 
locked Re: LOTW and Log4OM

Jürgen Umstädter
 

Hi Rich,

i´ve understood this when i read your first post. Not a problem for me. I only said i´m still
waiting for the first Beta. B.t.w. i am a member of the L4O beta team ... I don´t need to
have an alpha for testing, HI ....

Have nice x-mas days ... Juergen, DF5WW ;-)8-)



Am 24.12.2017 um 00:12 schrieb Rich McCabe:

Just to be clear this is not an updated version. Just testing the LOTW fixes since I am one having issues so helping them verify the fix.

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jürgen Umstädter
Sent: Saturday, December 23, 2017 5:06 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Hi Rich,

sounds good. Still waiting for the first Beta ;-)8-)

Juergen, DF5WW


Am 23.12.2017 um 23:48 schrieb Rich McCabe:

Yea its not a big deal to do. Thanks for the updates in #3 and #4.


I currently have an alpha release of updated Log4OM that I am testing which is working fine.

 

I cant speak for them as far as timing but I would expect it to be public release shortly.

 

Rich

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, December 23, 2017 11:28 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Every time...and here's a slightly updated sequence

 

 

#0 Back it up!!!
#1 Open QSO Manager/QSO Archive
#2 Click Search Parameters at bottom
#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.  Close the window.
#4 Click Search at the top, then Select All
#5 Click Field Update
#6 Under "Execute custom update query" put this:
update log set state=SUBSTR(state,1,2) WHERE SUBSTR(state,4,2)="//"
#7 Click all 4 warning boxes and then the "I understand..." button underneath.

de Mike W9MDB

 

 

On Saturday, December 23, 2017, 11:16:51 AM CST, Lawrence Godek <LawrenceG94@...> wrote:

 

 

Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry

W0OGH

 

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 

 

 
locked Re: LOTW and Log4OM

Rich McCabe
 

Just to be clear this is not an updated version. Just testing the LOTW fixes since I am one having issues so helping them verify the fix.

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jürgen Umstädter
Sent: Saturday, December 23, 2017 5:06 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Hi Rich,

sounds good. Still waiting for the first Beta ;-)8-)

Juergen, DF5WW


Am 23.12.2017 um 23:48 schrieb Rich McCabe:

Yea its not a big deal to do. Thanks for the updates in #3 and #4.


I currently have an alpha release of updated Log4OM that I am testing which is working fine.

 

I cant speak for them as far as timing but I would expect it to be public release shortly.

 

Rich

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, December 23, 2017 11:28 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Every time...and here's a slightly updated sequence

 

 

#0 Back it up!!!
#1 Open QSO Manager/QSO Archive
#2 Click Search Parameters at bottom
#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.  Close the window.
#4 Click Search at the top, then Select All
#5 Click Field Update
#6 Under "Execute custom update query" put this:
update log set state=SUBSTR(state,1,2) WHERE SUBSTR(state,4,2)="//"
#7 Click all 4 warning boxes and then the "I understand..." button underneath.

de Mike W9MDB

 

 

On Saturday, December 23, 2017, 11:16:51 AM CST, Lawrence Godek <LawrenceG94@...> wrote:

 

 

Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry

W0OGH

 

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 

 

 
locked Re: LOTW and Log4OM

Jürgen Umstädter
 

Hi Rich,

sounds good. Still waiting for the first Beta ;-)8-)

Juergen, DF5WW



Am 23.12.2017 um 23:48 schrieb Rich McCabe:

Yea its not a big deal to do. Thanks for the updates in #3 and #4.


I currently have an alpha release of updated Log4OM that I am testing which is working fine.

 

I cant speak for them as far as timing but I would expect it to be public release shortly.

 

Rich

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, December 23, 2017 11:28 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Every time...and here's a slightly updated sequence

 

 

#0 Back it up!!!
#1 Open QSO Manager/QSO Archive
#2 Click Search Parameters at bottom
#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.  Close the window.
#4 Click Search at the top, then Select All
#5 Click Field Update
#6 Under "Execute custom update query" put this:
update log set state=SUBSTR(state,1,2) WHERE SUBSTR(state,4,2)="//"
#7 Click all 4 warning boxes and then the "I understand..." button underneath.

de Mike W9MDB

 

 

On Saturday, December 23, 2017, 11:16:51 AM CST, Lawrence Godek <LawrenceG94@...> wrote:

 

 

Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry

W0OGH

 

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 

 
locked Re: LOTW and Log4OM

Rich McCabe
 

Yea its not a big deal to do. Thanks for the updates in #3 and #4.


I currently have an alpha release of updated Log4OM that I am testing which is working fine.

 

I cant speak for them as far as timing but I would expect it to be public release shortly.

 

Rich

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, December 23, 2017 11:28 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] LOTW and Log4OM

 

Every time...and here's a slightly updated sequence

 

 

#0 Back it up!!!
#1 Open QSO Manager/QSO Archive
#2 Click Search Parameters at bottom
#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.  Close the window.
#4 Click Search at the top, then Select All
#5 Click Field Update
#6 Under "Execute custom update query" put this:
update log set state=SUBSTR(state,1,2) WHERE SUBSTR(state,4,2)="//"
#7 Click all 4 warning boxes and then the "I understand..." button underneath.

de Mike W9MDB

 

 

On Saturday, December 23, 2017, 11:16:51 AM CST, Lawrence Godek <LawrenceG94@...> wrote:

 

 

Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry

W0OGH

 

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 

 
locked Re: HRD logging with JT-Alert not working

JTAlert Support (VK3AMA)
 

On 23/12/2017 1:16 AM, Brad Rich wrote:

I sent the file.  I had it working on my old machine.  I had to change computers and since has not worked.  I do click the log QSO button before entering the formatted logging screen

 

My call is N6GR

 

Brad

Brad,

You don't have a HRDLogbook.trace file because JTAlert has never logged a QSO to HRD.
JTAlert is not logging to HRD because it never receives a UDP Logged QSO packet from WSJT-X.

In fact JTAlert is not getting any UDP packets from WSJT-X so doesn't know your QRG and that is the reason JTAlert shows "???m" in the titlebar rather than the QRG Band. You would also not be receiving decodes from WSJT-X either so no callsigns displayed in JTAlert. If you had mentioned these other problems a solution would have been identified sooner.

You need to setup WSJT-X to allow the UDP communication between it and JTAlert.

See the JTAlert help file, "Tutorials -> WSJT-X UDP Server" topic.

de Laurie VK3AMA
   

locked Re: Feature Request :: JTAlert and HRD - Worked B4

JTAlert Support (VK3AMA)
 

On 24/12/2017 12:17 AM, Hans Schiessl wrote:
Hello Coder!

I would like to have the option in JTAlert to have the Worked B4 option together with HRD6.

Is it possible to not only store records, but also read records form HRD6 Logbook when using with WSJT-X for example.

Would be nice to have e query filter like:

Show in JTAlert CAPTURED STATIONS=WORKED IN HRD LOGBOOK AND MODE=FT8

Then when there is a Match -> in JTAlert a field like 'B4' after the CALL.


Now, this only works within JTAlert itself and not together with HRD.

Have a nice XMAS and HNY


Best 73,

Hans, PD4RM

Hans,

What your asking for is already available.
All B4 checks are done against the HRD Log when HRD Logging is enabled within JTAlert.

Similarly for the other supported loggers, the B4 checks are done against the log for the enabled logger.

de Laurie VK3AMA
   

locked Feature Request :: JTAlert and HRD - Worked B4

Hans Schiessl <hans@...>
 

Hello Coder!

I would like to have the option in JTAlert to have the Worked B4 option together with HRD6.

Is it possible to not only store records, but also read records form HRD6 Logbook when using with WSJT-X for example.

Would be nice to have e query filter like:

Show in JTAlert CAPTURED STATIONS=WORKED IN HRD LOGBOOK AND MODE=FT8

Then when there is a Match -> in JTAlert a field like 'B4' after the CALL.


Now, this only works within JTAlert itself and not together with HRD.

Have a nice XMAS and HNY


Best 73,

Hans, PD4RM
locked Re: LOTW and Log4OM

Michael Black
 

Every time...and here's a slightly updated sequence


#0 Back it up!!!
#1 Open QSO Manager/QSO Archive
#2 Click Search Parameters at bottom
#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.  Close the window.
#4 Click Search at the top, then Select All
#5 Click Field Update
#6 Under "Execute custom update query" put this:
update log set state=SUBSTR(state,1,2) WHERE SUBSTR(state,4,2)="//"
#7 Click all 4 warning boxes and then the "I understand..." button underneath.
de Mike W9MDB


On Saturday, December 23, 2017, 11:16:51 AM CST, Lawrence Godek <LawrenceG94@...> wrote:


Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry
W0OGH

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 
locked Re: LOTW and Log4OM

Lawrence Godek
 

Is this a "one time fix" or do you have to run this "fix" everytime you download from LoTW?

Larry
W0OGH

On Thu, Dec 21, 2017 at 10:50 AM, Rich McCabe <r.mccabe@...> wrote:

Thanks for this info Mike.


I did not realize this issue was causing me grief until today!

 

 

73,


Rich

 

An bit of an update to this to make it a little more specific to US states (NZ states caused a problem).

 

 

Due to changes in LOTW downloads Log4OM users will need to do the following until Log4OM releases a fix for this or LOTW reverts their change.

 

Here's how to fix your downloads from LOTW in Log4OM.  Before starting back up your log file of course.

 

#1 Open QSO Manager/QSO Archive

#2 Click Search Parameters at bottom

#3 in the Simple pulldown select "State" and then "LIKE".  Then put "%//%" in the box.  Click +.

#4 Click Select All

#5 Click Field Update

#6 Under "Execute custom update query" put "update log set state=SUBSTR(state,1,2)"

#7 Click all 4 warning boxes and then the "I understand..." button underneath.

 

This series of actions corrects the LOTW comments being added to the download.

And it can all be done from within Log4OM.

 

de Mike W9MDB

 

 
locked Re: Different Alert for new country

Rich McCabe
 

 

OK thanks Laurie,


I currently have DXCC on digital alone but there are a lot of countries to work when you are trying to do them on as many of the HF bands as possible.  Now with FT8 there are constantly blue new DX for new bands.  Because of this its easy to miss that rare DX 😊

 

Thanks again.


Rich

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, December 22, 2017 6:27 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Different Alert for new country

 

On 23/12/2017 10:37 AM, Rich McCabe wrote:

I doubt this is possible but going to ask :)

Is there any way to get an alert for un-worked country on any band when you have new country set per band?  In other words I want to continue to pick off countries on all the bands I need them on but I would like to have something that tells me when its a country I have never worked on ANY band so that can take priority.

Rich

Rich,

What your asking for is an ATNO alert. Not possible within the current JTAlert V2 implementation.

An ATNO alert would be of most use to those just starting their DX career where it is common to get multiple DXCC alerts at a time and need to make a decision which to work.

My suggestion is become more active on the bands and work the easy ones and in a short time, you will only be getting the occasional DXCC alert on a band and you will want to work that one regardless of whether it is an ATNO or just a new band/mode.

de Laurie VK3AMA
    

locked Re: Version 2.10.7 Problem Fixed

JTAlert Support (VK3AMA)
 

On 23/12/2017 7:43 AM, W7JHR via Groups.Io wrote:
Hi Laurie,

Thanks for getting back to me so quickly.  Here are the answers to your questions:

1.  I was using the latest version of WSJT-X 1.8 and had not touched it since installing it when it was released.
2. The version of JTAlert that I had been using was the one that was previous to 2.10.7. I don't recall its' release number.
3. All previous versions of WSJT-X and JTAlert had worked seamlessly.
4. I'm very familair with the manual and tutorials.

When my frustration level reached the boiling point, I uninstalled both WSJT-X and JTAlert and re-installed both programs.  Both programs worked worked seamlessly again with the exception of the Band Activity Window which simply didn't show up when the program was running.  After rebooting the program several times it showed up and is working properly.  I hope this helps those who may have experienced similar problems.

Thanks for your software!  I didn't realize how much I relied on it until I couldn't use it.

73
Jim W7JHR
Jim,

Are you running Win10? Unusual and unexpected application behaviour appears to occur more frequently with Win10. Many commentators have attributed this to the Windows "Fast Startup" mode. I have experienced this many times until I read this article The Pros and Cons of Windows 10’s “Fast Startup” Mode.

Win10 by default doesn't unload certain parts of the OS and some application files when a shutdown is performed, a form of hibernation takes place and this provides for a fast startup. The only way to guarantee that the OS and applications are completely unloaded is to perform a "Restart"

All Win10 PCs that I work on now have "Fast Startup" disabled. While it does make startup noticeably slower, the unusual application behaviours I was previously experiencing seem to have been eliminated, except when Windows has an update pending which only becomes apparent when the Restart is performed (typically because an app is misbehaving)

Regarding uninstalling WSJT-X and JTAlert, that will typically have no effect as configuration files for both are not removed by the uninstall process. Rarely is there a problem with the actual application files.

de Laurie VK3AMA
   

locked Re: Different Alert for new country

JTAlert Support (VK3AMA)
 

On 23/12/2017 10:37 AM, Rich McCabe wrote:
I doubt this is possible but going to ask :)

Is there any way to get an alert for un-worked country on any band when you have new country set per band?  In other words I want to continue to pick off countries on all the bands I need them on but I would like to have something that tells me when its a country I have never worked on ANY band so that can take priority.

Rich
Rich,

What your asking for is an ATNO alert. Not possible within the current JTAlert V2 implementation.

An ATNO alert would be of most use to those just starting their DX career where it is common to get multiple DXCC alerts at a time and need to make a decision which to work.

My suggestion is become more active on the bands and work the easy ones and in a short time, you will only be getting the occasional DXCC alert on a band and you will want to work that one regardless of whether it is an ATNO or just a new band/mode.

de Laurie VK3AMA
    

locked Different Alert for new country

Rich McCabe
 

I doubt this is possible but going to ask :)

Is there any way to get an alert for un-worked country on any band when you have new country set per band?  In other words I want to continue to pick off countries on all the bands I need them on but I would like to have something that tells me when its a country I have never worked on ANY band so that can take priority.

Rich
locked Re: Version 2.10.7 Problem Fixed

W7JHR@...
 

Hi Laurie,

Thanks for getting back to me so quickly.  Here are the answers to your questions:

1.  I was using the latest version of WSJT-X 1.8 and had not touched it since installing it when it was released.
2. The version of JTAlert that I had been using was the one that was previous to 2.10.7. I don't recall its' release number.
3. All previous versions of WSJT-X and JTAlert had worked seamlessly.
4. I'm very familair with the manual and tutorials.

When my frustration level reached the boiling point, I uninstalled both WSJT-X and JTAlert and re-installed both programs.  Both programs worked worked seamlessly again with the exception of the Band Activity Window which simply didn't show up when the program was running.  After rebooting the program several times it showed up and is working properly.  I hope this helps those who may have experienced similar problems.

Thanks for your software!  I didn't realize how much I relied on it until I couldn't use it.

73
Jim W7JHR
locked Re: HRD logging with JT-Alert not working

René
 

TNX Laurie,
Now working FB. Merry XMAS
René ve2esu
locked Re: Suggested Additional Capability

Michael Black
 

That's not a bad idea...I'll float it around and see if it sticks.  It would take changes on both JTAlert and WSJT-X to handle non-CQ messages.  Previously this has been assumed to get QSOs automated but this idea wouldn't do that.

A CTRL-Click in JTAlert would simply put the message in the RX window so you don't have to hunt for it.

de Mike W9MDB



From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Larry Banks
Sent: Friday, December 22, 2017 7:55 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Suggested Additional Capability

 

Hi Mike,

 

Yes, I’m not using correct terminology. 

 

I should have said that clicking an alert in JTAlert would bring the (non-CQing) spot from the Band Activity window to the RX Frequency window and do nothing else.  (I had “Menus” turned off and forgot what they are actually called.)  Nothing else would need to be done.  If it was a station that you then wanted to call, you would double click it at the appropriate time, usually after they subsequently call CQ.


73 -- Larry -- W1DYJ
locked Re: Suggested Additional Capability

Rich McCabe
 

Larry, I re read your post and misunderstood it.

 

I think this would be a WSJT limitation and not something JT alert can control.

 

I agree that would be nice.

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Rich McCabe
Sent: Friday, December 22, 2017 8:01 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Suggested Additional Capability

 

That already works and is a setting in WSJT-X itself.

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Larry Banks
Sent: Friday, December 22, 2017 7:55 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Suggested Additional Capability

 

Hi Mike,

 

Yes, I’m not using correct terminology. 

 

I should have said that clicking an alert in JTAlert would bring the (non-CQing) spot from the Band Activity window to the RX Frequency window and do nothing else.  (I had “Menus” turned off and forgot what they are actually called.)  Nothing else would need to be done.  If it was a station that you then wanted to call, you would double click it at the appropriate time, usually after they subsequently call CQ.


73 -- Larry -- W1DYJ

Re: Suggested Additional Capability
From: Michael Black
Date: Thu, 21 Dec 2017 20:43:43 PST

What "transmit window" are you talking about...the "Rx Frequency" window in WSJT-X?

 

I'm trying to think of why this would not be possible.  WSJT-X could simply plunk any non CQ message in the Tx Frequency window.  But I assume you want it to do more than that.  Probably set DX Call, adjust offset, and Generate Std Msgs?  Basically the same as double-click but without Enable being turned on.

 

de Mike W9MDB

 

 

On Thursday, December 21, 2017, 8:48:00 PM CST, Larry Banks <larryb@...> wrote:

 

 

Hi Laurie,

 

I completely agree that nothing should be done to make this automatic, and my request would not do that.  Perhaps I did not describe it very well.  I am simply suggesting that when you click on an alert in JTAlert, it brings the info to the transmit window so it can be seen.  As it functions currently, nothing would start unless the station is calling CQ.  This just moves the “click” from the received side of WSJT-X to JTAlert and saves looking back over the WSJT-X received window for that call.

 

Of course, perhaps I misunderstood your answer.  From what you stated, the WSJT-X UDP protocols themselves prevent you from writing code to do this.  In that case, and I agree with this, preventing automation (which is good) is preventing non-automatic features (which is sort of bad.)

 

Oh well...


73 -- Larry -- W1DYJ
locked Re: HRD logging with JT-Alert not working

Brad Rich <brad.rich@...>
 

I sent the file.  I had it working on my old machine.  I had to change computers and since has not worked.  I do click the log QSO button before entering the formatted logging screen

 

My call is N6GR

 

Brad

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, December 21, 2017 10:29 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] HRD logging with JT-Alert not working

 

On 22/12/2017 7:42 AM, Brad Rich wrote:

My HRDLogboox trace is missing.


If the HRDLogbook.trace is truly missing rather than just being hidden by Windows, that indicates there has never been a HRDLogbook logging command sent by JTAlert. The creation and population of that trace file is automatic when JTAlert receives the logging event from WSJT-X (you must OK the Log QSO window) and subsequently send a suitably formatted logging command, via TCP, to HRDLogbook.

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Make sure you have attempted one HRD logging from JTAlert in the last 24 hours and please reference this message thread in the notes.

Also, you still have not provided your Callsign, it will help in identifying your Support Request if your could provide that.

de Laurie VK3AMA
   

21861 - 21880 of 39839