Date   

locked Re: JTAlert works fine but no colored calls in WSJT

JTAlert Support (VK3AMA)
 

On 24/12/2020 10:15 am, N2TK, Tony via groups.io wrote:

Never mind. I have to use the red musical note shortcut to see the colored callouts in WSJT. Not sure what the colors mean but it is working fine.

N2TK, Tony

  Red icon  -> JTAlert for WSJT-X
  Blue icon -> JTAlert for JTDX

Don't bother trying to get the JTDX decodes colored by JTAlert, it is not supported. The relevant code in the original WSJT-X source was stripped by the JTDX people for some reason.

de Laurie VK3AMA


locked Re: JTAlert works fine but no colored calls in WSJT

N2TK, Tony
 

Never mind. I have to use the red musical note shortcut to see the colored callouts in WSJT. Not sure what the colors mean but it is working fine.

N2TK, Tony

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of N2TK, Tony via groups.io
Sent: Wednesday, December 23, 2020 5:52 PM
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert works fine but no colored calls in WSJT

 

Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change?
I used the blue musical note shortcut. Do I need to use a different color and/or the "X" instead of the musical symbol?
Tnx
N2TK, Tony


locked JTAlert works fine but no colored calls in WSJT

N2TK, Tony
 

Updated JTAlert. Seems to be working fine. But none of the highlighted calls appear highlighted in WSJT. What did I forget to change?
I used the blue musical note shortcut. Do I need to use a different color and/or the "X" instead of the musical symbol?
Tnx
N2TK, Tony


locked Re: JT Alert & WSJT-X interactions

JTAlert Support (VK3AMA)
 

On 22/12/2020 4:56 am, Mike Turner wrote:
I was trying to discover why I no longer get the "worked before" alert on JTAlert.

If you're not getting B4's than likely the log your using with JTAlert has changed or no longer contains your previous QSOs.

What log type are you using, does it still contain all your past QSOs?

de Laurie VK3AMA


locked Re: NO JTALERT call sign download/fill-in

JTAlert Support (VK3AMA)
 

On 21/12/2020 9:57 pm, k6vib@q.com wrote:
The 2 x 7 areas I use to fill in are ok, but the area for a selected call sign to be worked does not fill in the Name, QTH, or Grid. Seems to have the State and/or Country though. It does fill in if it is a call that I have worked on another band or B4. Do I have a setting wrong?
The WSJT grid info shows up OK. This just started about 2 days ago. I have been manually filling in the info via QRZ. Any suggestions? Thanks Bob K6VIB

The JTAlert log fields area gets populated with Name & QTH data from any previous QSOs in your log for that station or from an XML lookup. Since this was working previously, the likely cause is that your xml subscription has expired.

de Laurie VK3AMA


locked Re: JT Alert not displaying all decodes

JTAlert Support (VK3AMA)
 

On 18/12/2020 11:45 am, Dave LeDuc wrote:

I’m sure this topic has come up before but I can’t seem to find the answer.

Is there anything I can do to display all of the WSTJ-X band activity in the JT-Alert decodes window?

I am only able to see the first 25 or so decodes in the JT-Alert decodes window.

Is my computer too slow?

 

Thanks

Dave N1IX


Since you don't mention your PC specs, it's a guessing game as to whether your PC is the cause of missing decodes. How many cores, installed RAM, speed?

How late is WSJT-X showing all the decodes for a period, that is how far into the new period is WSJT-X still presenting decodes from the last period?

Do you have any JTAlert Alert filters enabled?

de Laurie VK3AMA


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

JTAlert Support (VK3AMA)
 

On 24/12/2020 7:38 am, Dick Bingham wrote:
- IF I click "OK"in the "Confirm QSO Window" while my "73" is being transmitted, the entire system freezes for tens-of-seconds before recovering - being careful to click 
 "OK"  after the transmission is completed solves this problem


That indicates that JTAlert is stuck waiting to verify the QSO was actually written to the DXKeeper log. 10's of seconds is excessive, on a moderate PC I would expect that to be under 5 secs depending on what online activities DXKeeper is performing post logging. How reliable/fast is your internet connection? If you have DXKeeper auto-uploading to LoTW or eQSL and those services are down or slow, than delays in DXKeeper writing the QSO to the log file are normal and JTAlert will hang (as will DXKeeper) while it retries reading the log file to confirm the QSO was written.

Does JTAlert present you with a success or failure message after the logging?

de Laurie VK3AMA


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

JTAlert Support (VK3AMA)
 

On 24/12/2020 7:38 am, Dick Bingham wrote:
- A decoded directed CQ (like "CQ DX W1AW FN##") is not indicated in a 2X8 JTAlert display Cell forcing me to still examine the WSJT-X screen to minimize interfering 
  with the CQer's real interest

You're missing decoded callsigns because your limiting the JTAlert display. The display can go to 4 lines x 9 callsigns. See the View menu.

If 36 callsign slots is not enough, you can try restricting the number displayed by using one or more Alert filters. Alternatively, use the Decodes window which will display all the callsigns in a period.

de Laurie VK3AMA


locked Re: JTAlert shortcuts on desktop

JTAlert Support (VK3AMA)
 

On 24/12/2020 8:54 am, N2TK, Tony via groups.io wrote:
Just installed the update to 2.16.17. Seems to be working fine.
But what about the different colored shortcuts? Did I miss somewhere what they mean?
Musical not and also "X" in blue, red, purple. Used to have a green but no longer since I upgraded. Using the blue musical note right now
Tnx and Merry Christmas
N2TK, Tony

How old was the JTAlert version you upgraded from?

From the release notes...
2.16.5 (08-May-2020)

  ******************************************************************************
  *** Important: JTAlert build type changes
  ***
  *** The Original JTAlert (menus in titlebar) is no longer available.
  *** The Alt Layout JTAlert (menus placed below the titlebar) is now simply
  *** called JTAlert and is the only build type now produced.
  *** The executable file name has changed from JTAlert_AL.exe to JTAlert.exe
  *** The old Alt Layout build icon colors for JTAlert and shortcuts (green
  *** and purple) are no longer used. The icon colors used are ...
  ***   Red icon  -> JTAlert for WSJT-X
  ***   Blue icon -> JTAlert for JTDX
  ******************************************************************************


de Laurie VK3AMA



locked JTAlert shortcuts on desktop

N2TK, Tony
 

Just installed the update to 2.16.17. Seems to be working fine.
But what about the different colored shortcuts? Did I miss somewhere what they mean?
Musical not and also "X" in blue, red, purple. Used to have a green but no longer since I upgraded. Using the blue musical note right now
Tnx and Merry Christmas
N2TK, Tony


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Dick Bingham
 

Greeting ALL - Jim and Neil in particular

I will respond "Inside" Jim's text space to ensure nothing is left out...  Dick/w7wkr
==========================================================
Sounds to me like you JTAlert is not linked to DXKeeper, and you are only seeing the contacts in your WSJT-X log.
 
To check this, in DXKeeper banner, you should see how many contacts you have logged. Mine says DXKeeper 15.8.9 [CC,PF] - AF5FH.mdb: 5571 QSOs. Your number of QSOs will be different, of course.
On my DXKeeper Banner , I see 900-plus QSOs indicated AND I only see QSO logged in the DXKeeper ..\..\databases\W7WKR.mdb LOG going back to August, 2020.
LotW shows I have over 9000 QSO in their database.

In a file at c:\DXLab\DXKeeper\Databases\LotW_QSOs_ADI I see 9074 QSOs logged. Is logging being sent to the wrong file ?

THEN after some messing-around (unfortunately I did not paper-record each step for later review) the DXKeeper banner displayed (DXKeeper 15.7.2 - w7wkr.mdb : 9883 QSO) 
 
 Now JTAlert seems to be working much better indicating many CQ's as being worked previously (B4)

Next, in JTAlert, click Settings, Rebuild Alert Database, and then click Rebuild All (enabled). A Log Scan - DXLab DXKeeper window should appear, and it will quickly at the top flash Loading xxxx of 5571 QSOs, followed by a series of Scanning Log: Band - xxx messages. The number of QSOs in the Log Scan windows has to exactly match the number of QSOs that DXKeeper has logged.
After performing the above steps many times, I now get a match between JTAlert and DXKeeper numbers.

Let us know if the numbers of QSOs match. If they do not, verify that Enable DXLab DXKeeper logging is enabled in Settings, Logging, DXLab DXKeeper.
Yes, "Enable DXkeeper ...." IS enabled.

An important step/steps was/were correctly stumbled upon and now JTAlert works like it was designed to function !

Some issues:
- A decoded directed CQ (like "CQ DX W1AW FN##") is not indicated in a 2X8 JTAlert display Cell forcing me to still examine the WSJT-X screen to minimize interfering 
  with the CQer's real interest
- Do not know what the difference is between an UNDERLINED callsign (in a 2X8 cell) and one NOT underlined. Multiple reading-passes thru the SETUP selections has not
  revealed what is implied
- IF I click "OK"in the "Confirm QSO Window" while my "73" is being transmitted, the entire system freezes for tens-of-seconds before recovering - being careful to click 
 "OK"  after the transmission is completed solves this problem

Thank you ALL who responded to my request for assistance. I can live with what is working now and, with more experience, probably refine some settings.

73  Dick/w7wkr at CN97uj


73, Jim AF5FH


On Wed, Dec 23, 2020 at 7:09 AM Jim AF5FH <jkajder@...> wrote:
Sounds to me like you JTAlert is not linked to DXKeeper, and you are only seeing the contacts in your WSJT-X log.
 
To check this, in DXKeeper banner, you should see how many contacts you have logged. Mine says DXKeeper 15.8.9 [CC,PF] - AF5FH.mdb: 5571 QSOs. Your number of QSOs will be different, of course.

Next, in JTAlert, click Settings, Rebuild Alert Database, and then click Rebuild All (enabled). A Log Scan - DXLab DXKeeper window should appear, and it will quickly at the top flash Loading xxxx of 5571 QSOs, followed by a series of Scanning Log: Band - xxx messages. The number of QSOs in the Log Scan windows has to exactly match the number of QSOs that DXKeeper has logged.

Let us know if the numbers of QSOs match. If they do not, verify that Enable DXLab DXKeeper logging is enabled in Settings, Logging, DXLab DXKeeper.

73, Jim AF5FH


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Jim AC9ZL
 

Sounds to me like you JTAlert is not linked to DXKeeper, and you are only seeing the contacts in your WSJT-X log.
 
To check this, in DXKeeper banner, you should see how many contacts you have logged. Mine says DXKeeper 15.8.9 [CC,PF] - AF5FH.mdb: 5571 QSOs. Your number of QSOs will be different, of course.

Next, in JTAlert, click Settings, Rebuild Alert Database, and then click Rebuild All (enabled). A Log Scan - DXLab DXKeeper window should appear, and it will quickly at the top flash Loading xxxx of 5571 QSOs, followed by a series of Scanning Log: Band - xxx messages. The number of QSOs in the Log Scan windows has to exactly match the number of QSOs that DXKeeper has logged.

Let us know if the numbers of QSOs match. If they do not, verify that Enable DXLab DXKeeper logging is enabled in Settings, Logging, DXLab DXKeeper.

73, Jim AF5FH


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

neil_zampella
 

OK ... I trust that you adjusted the GRID tracking filters properly, and ran the 'rescan' log to update the JT-Alert data?

 

Neil, KN3ILZ


locked Re: JTAlert 'worked before' flag missing

Mike Turner <kl7x@...>
 

My 'Worked B4' issue is resolved.

best 73.

Mike   KL7X


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of Mike Turner <kl7x@...>
Sent: Monday, December 21, 2020 7:43 AM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: [HamApps] JTAlert 'worked before' flag missing
 
Trying to 'get worked' alert working.  I see that the wsjt_log.adi file was last modified 12/26/2019.  contacts since that time are not showing
up as 'worked before',  Logged qsos are seen in the wsjt_log ADI fuke and the wsjt Text document.

Is there a way to move my  latest qsos into the wsjt_log.adi file


locked Re: JTAlert does crash again /Final

asobel@...
 

Laurie

 

I want to report that the problem was solved:

 

On early Sep 2020, HRD support did replace the database of it’s Logbook from MsAccess  to MariaDB which made the logbook run quicker.

As an unexpected result, JtAlert did stop to crash since then.

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, September 3, 2020 1:18 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert does crash again

 

On 2/09/2020 4:59 am, asobel@... wrote:

JTAlert did ceash again few times today.

 

The news is about the new message in the above snip

 

Amos 4X4MF


Amos,

Sorry, I can't provide any further insight into what may be causing the crash on your PC. I have not received similar reports from other users, the problem appears to be specific to your PC environment.

de Laurie VK3AMA


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

Dick Bingham
 

Good Morning Neil

OK, I finally recognize the TRACKING word in the Grid section - Duh !

I just did not see that word (tracking) in any of the HELP or the settings main window.

What I now find puzzling are the displays in the "Grid Squares NOT Wanted"
BIG window:

- ANY BAND selected in the tracking window displays 267 G-S NOT needed

- BY INDIVIDUAL BAND selected I see ===>
-- 160M ==> "0 of 32400 GS NOT Needed"
-- 80M ===> "0 of 32400 GS NOT Needed
-- 60M ===> "0 of 32400 GS NOT Needed
-- 40M ===> "0 of 32400 GS NOT Needed
-- 30M ===> "0 of 32400 GS NOT Needed
-- 20M ===> "125 of 32400 GS NOT Needed
-- 17M ===> "0 of 32400 GS NOT Needed
-- 15M ===> "0 of 32400 GS NOT Needed
and the same for the other higher freq bands

Where are the missing 142 (267 - 125)  Grids ?
Is this a BUG ?

Little-by-little, I am getting better at understanding
this SW. Still seeing decoded CQ's as new contacts but
seeing "B4" when I call them.

73  Dick/w7wkr

On Tue, Dec 22, 2020 at 8:22 AM neil_zampella <neilz@...> wrote:

Dick,

the options are located on the Enable Grid -> BANDS setting under the Tracking box, there are TWO pull down selections, The first shows how to track grids, any band or by individual band, and the next pull down will have four selections, any mode, by individual mode (JT9, JT65, FT8, FT4), any digital mode, and Any WSJT-X Mode.

If you have non-digital, and/or non-WSJT-X mode QSOs, and don't have any mode, or any digital mode selected, you may have filtered out those QSOs.

FWIW ... the JT-Alert help system is a work in-progress.  If Laurie ever finds the time from adding requested additions, or assisting users, he may be able to update that.

 

Neil, KN3ILZ

 



On Mon, Dec 21, 2020 at 03:05 PM, Dick Bingham wrote:

GM Neil
 
Thanks for the follow-up.
 
I just finished going thru the JTAlert "HELP" file stuff and can find
ZERO info about the "Tracking" box you mentioned.
 
In the Settings ===> "Wanted US States" window
- Enable Wanted State Alert checked
- All States checked
- By State Code checked
- By Individual Bands selected
- Any WSJT-X mode selected
- Band Enable and Select  all checked In settings ===> "Wanted State" window
=========================================================
- Enable Wanted Grid Alert checked
and the ONLY band window that has any worked grids displayed is 20-meters.
All other bands (I have many Q's in the database) have empty windows when
selected to see progress.
 
73 Dick/w7wkr at CN97uj
Hide quoted text

 

On Mon, Dec 21, 2020 at 6:20 AM neil_zampella <neilz@...> wrote:

What do you have set in the TRACKING box?   Any digital mode?  Any mode?   There are a few options that may be filtering out those grids.

 

Neil, KN3ILZ


On Mon, Dec 21, 2020 at 02:44 AM, Dick Bingham wrote:

Hello Pete
 
I performed a "Sync LotW QSOs" and "Sync LotW QSLs"
accessed via the DXKeeper QSL-tab ===> LotW Operations
section of the SW AND then rebuilt the Alert Database.
 
After completing these tasks I see a message in the 
20-meter Grids Wanted section of 125 Grids NOT needed.
 
ALL of the other bands indicate EMPTY screens for Grids.
 
Puzzling to say the least! Also, way too many CQing stations
are highlighted as Wanted states even though I've already
worked them on the band in use. Again - puzzling.
 
73 and thanks for the reply.
 
Dick/w7wkr at CN97uj


locked Re: Logging to DXKeeper

David Bunte
 

My problem is solved. Mike Black - W9MDB contacted me this morning, and talked me through my setup. The problem was that the 'PROMPT ME TO LOG QSO' box was unchecked on the reporting tab of the WSJT-X settings. Even as I looked at that tab, I missed the fact that the box was not checked.

Simple problem, but I guess I was too simple to catch it on my own. Mike's assistance was spot on and much appreciated.

73 to all de Dave - K9FN

On Tue, Dec 22, 2020 at 12:30 PM Dave Garber <ve3wej@...> wrote:
make sure DXK is indeed selected as your logging program in jtalert ( look at top tine of jtalert) DXK should be there.

then check to confirm the correct log file is selected in jtalert

DXK should tell you which it is using

also check for udp forwarding is done correctly

hope this helps
Dave Garber
VE3WEJ / VE3IE


On Tue, Dec 22, 2020 at 2:04 AM David Bunte <dpbunte@...> wrote:
JTAlert has successfully logged all my FT8 QSOs directly to DXKeeper, until about 7 or 8 days ago. I have not intentionally changed any of the settings in JTAlert, but did review them to see if something had been changed unknowingly.

I can find no such issues.

I have shut down all applications, be started my PC. Started DXLab applications including DXKeeper. I then started WSJT-X followed by JTAlert. I made an FT8 QSO but it did not log to DXKeeper. There is no error log in DXKeeper which makes me believe it was not a matter of JTAlert trying to log to DXK and failing, but rather, JTAlert did not attempt to log to DXK.

I don't know what to check, or try next.

Dave - K9FN


locked Line 39605 Error

asobel@...
 

Laurie

My first instance of  JTALERT 2.16.7 does repeatedly show the following 
And shutdown.
Please offer a solution.

Amos 4X4MF


locked Re: Logging to DXKeeper

Dave Garber
 

make sure DXK is indeed selected as your logging program in jtalert ( look at top tine of jtalert) DXK should be there.

then check to confirm the correct log file is selected in jtalert

DXK should tell you which it is using

also check for udp forwarding is done correctly

hope this helps
Dave Garber
VE3WEJ / VE3IE


On Tue, Dec 22, 2020 at 2:04 AM David Bunte <dpbunte@...> wrote:
JTAlert has successfully logged all my FT8 QSOs directly to DXKeeper, until about 7 or 8 days ago. I have not intentionally changed any of the settings in JTAlert, but did review them to see if something had been changed unknowingly.

I can find no such issues.

I have shut down all applications, be started my PC. Started DXLab applications including DXKeeper. I then started WSJT-X followed by JTAlert. I made an FT8 QSO but it did not log to DXKeeper. There is no error log in DXKeeper which makes me believe it was not a matter of JTAlert trying to log to DXK and failing, but rather, JTAlert did not attempt to log to DXK.

I don't know what to check, or try next.

Dave - K9FN


locked Re: New User of JTAlert v2.16.17 (and WSJT-X v2.2.2 and DXKeeper Logging)

neil_zampella
 

Dick,

the options are located on the Enable Grid -> BANDS setting under the Tracking box, there are TWO pull down selections, The first shows how to track grids, any band or by individual band, and the next pull down will have four selections, any mode, by individual mode (JT9, JT65, FT8, FT4), any digital mode, and Any WSJT-X Mode.

If you have non-digital, and/or non-WSJT-X mode QSOs, and don't have any mode, or any digital mode selected, you may have filtered out those QSOs.

FWIW ... the JT-Alert help system is a work in-progress.  If Laurie ever finds the time from adding requested additions, or assisting users, he may be able to update that.

 

Neil, KN3ILZ

 



On Mon, Dec 21, 2020 at 03:05 PM, Dick Bingham wrote:

GM Neil
 
Thanks for the follow-up.
 
I just finished going thru the JTAlert "HELP" file stuff and can find
ZERO info about the "Tracking" box you mentioned.
 
In the Settings ===> "Wanted US States" window
- Enable Wanted State Alert checked
- All States checked
- By State Code checked
- By Individual Bands selected
- Any WSJT-X mode selected
- Band Enable and Select  all checked In settings ===> "Wanted State" window
=========================================================
- Enable Wanted Grid Alert checked
and the ONLY band window that has any worked grids displayed is 20-meters.
All other bands (I have many Q's in the database) have empty windows when
selected to see progress.
 
73 Dick/w7wkr at CN97uj
Hide quoted text

 

On Mon, Dec 21, 2020 at 6:20 AM neil_zampella <neilz@...> wrote:

What do you have set in the TRACKING box?   Any digital mode?  Any mode?   There are a few options that may be filtering out those grids.

 

Neil, KN3ILZ


On Mon, Dec 21, 2020 at 02:44 AM, Dick Bingham wrote:

Hello Pete
 
I performed a "Sync LotW QSOs" and "Sync LotW QSLs"
accessed via the DXKeeper QSL-tab ===> LotW Operations
section of the SW AND then rebuilt the Alert Database.
 
After completing these tasks I see a message in the 
20-meter Grids Wanted section of 125 Grids NOT needed.
 
ALL of the other bands indicate EMPTY screens for Grids.
 
Puzzling to say the least! Also, way too many CQing stations
are highlighted as Wanted states even though I've already
worked them on the band in use. Again - puzzling.
 
73 and thanks for the reply.
 
Dick/w7wkr at CN97uj

7221 - 7240 of 39821