Date   

locked Address Change

Bill Snyder
 

Hello, Bill Snyder here, K3ABE I have been receiving complaints that my address is showing PA, I have moved to FL in June of this year I have change my address every I can think of but JTALERT still shows PA can you help with this?

 

73,

Bill – K3ABE

 


locked Re: JTAlert setup problem

jerry andersson
 

Hi Laurie

I've been away to the summerhouse and compared the settings - identical.
the conclusion drawn was that there's something wrong with the programs, removed all pieces of jtdx, wsjt-x and JTAlert. Degragmented disk... installed fresh copies of the programs, voila! all OK !!
Thanks for a very good companion to WSJT-X and JTDX

73 Jerry


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Wednesday, October 27, 2021 01:18
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] JTAlert setup problem
 
On 26/10/2021 2:18 am, jerry andersson wrote:
I have two QTH's where I'm active 
 
"summerhouse" installed JT Alert 2-50.7- JTDX, on a win10pro - running FB.
 
Home QTH win7pro , 6GB,x64, net5.0 desktop
JT Alert working OK with JTDX, but can't get JT Alert to show anything in Callsign, QSO history, Macros...
 the Messaging window functions !
Tried to revert back to a version pre 2.50 where the macros window functioned - lost that communication too.
Evidently I have managed to do something that I shouldn't. Any suggestions are welcome
73 Jerry
SM7BZV / SM6BZV / SI6V

What does the non-working PC report in the JTAlert "Help -> About" menu window? Open the About window then copy the "Current Operating State" section of the window and past it into your reply. You can quickly copy to the clipboard by using the icon top-right of that section of the About window.



Also check that you have WSJTX and JTAlert UDP comms setup correctly. Open the help file via the "Help -> WSJT-X UDP Setup" menu and check that you have set both correctly.

de Laurie VK3AMA


locked Worked B4 - call marked as a new one

sq3rx
 

Hi, 
Today, I've noticed problem with QSO B4 label (based on 7P8RU call, but this in not the only one). You can take a look at attached screens. What I did to solve this:

1. Rebuilded Alert Database
2. Deleted Decodes Records Database
3. Restarted all aplications (DXKeeper, JTalert)

Unfortunately, the problem still ocures. Any suggestions are welcome
If this can help, I can also find this QSO in JTDX ALL file.

73! Mek sq3rx


locked Re: ACLog interface #FT8

James Tills W7JWT Stevens County DEM
 

Thank you for your help. I will try to look at this closer. I hope I can figure this out. Any idea why JTAlerts is not automatically loading the correct address?

On Oct 29, 2021 12:17 PM, "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:
On 30/10/2021 1:55 am, James Tills W7JWT Stevens County DEM wrote:
I am using JTAlerts with ACLog and FT-8. I have two issues:

1) Under the ACLog menu item in JTAlerts settings, you can select to use ACLog. However, the file address that JTAlerts is supposed to load automatically, is not loading. I would like to get the program to load this info. I don't think I missed a setting, but any help would be appreciated.

2) I was able to load the file address in the Manual section on the same JTAlerts menu page. An FT-8 contact is now transferring to ACLog, but it always brings up the popup box that essentially says it could not verify the contact was successfully logged. Any help in delaying the popup until it can verify it successfully, or speeding up the process so I get the "successful" popup box would be appreciated.

Thanks much for any help. If there is help topic info out there that addresses this, please send me a link.  CUL & 73s  Jim  W7JWT

If the QSOs are getting logged that indicates you have the network component of the settings correct.

JTAlert reporting that it was unable to confirm the QSO was logged indicates that JTAlert was unable to find the newly logged QSO in the log file. The likely cause is that you have not selected the location of the currently enabled log file. Make sure you have selected the correct log type and the log file location/name.

   

de Laurie VK3AMA



locked Re: How Does "Rebuild Alert DB" Work?

Joe Subich, W4TV
 

Can someone explain how the Rebuild Alert DB function works? Does it
scan my HRD logbook or a log that WSJTX and/or JT Alert maintains?
Yes, it scans the specified logbook.

Does it just look to determine if the country has been worked, or
can it be set up to also look if there is a QSL confirmation?
It looks at the status recorded in your log - ie, confirmation by card, confirmation by LotW, "confirmation" by eQSL. It will determine the
"confirmed" status of each QSO based on the settings for each "Wanted"
category in "Rebuild Alert Database." For example, I have "Wanted US
State" set to LotW only (I don't want to mess with those cards), for
DXCC I select "Cards" and "LotW" since ARRL will not accept eQSL.
For WAZ, I select eQSL, Cards and LotW since CQ accepts all three and
for Marathon, I don't select any since Marathon does not require QSLs.

73,

... Joe, W4TV


On 2021-10-29 2:35 PM, Paul N3PS via groups.io wrote:
Until now, I have the Wanted DX alert set up for Any Band, Any Mode . . .  I have been manually updating the Wanted / Not Wanted settings in JT Alert as I work a new country and subsequently receive a QSL card or LoTW confirmation.
Now that I have hit the DXCC 200, I want to move into working for the 5 Band DXCC and DXCC Challenge.  To do this, I will need to change the Wanted DX alert from Any Band, to the By Individual Band setting.
In moving to the By Individual Band setting, I don't want to have to manually update the Wanted / Not Wanted countries if I don't have to . .
Can someone explain how the Rebuild Alert DB function works?  Does it scan my HRD logbook or a log that WSJTX and/or JT Alert maintains?  Does it just look to determine if the country has been worked, or can it be set up to also look if there is a QSL confirmation?
--
Paul / N3PS


locked Re: ACLog interface #FT8

HamApps Support (VK3AMA)
 

On 30/10/2021 1:55 am, James Tills W7JWT Stevens County DEM wrote:
I am using JTAlerts with ACLog and FT-8. I have two issues:

1) Under the ACLog menu item in JTAlerts settings, you can select to use ACLog. However, the file address that JTAlerts is supposed to load automatically, is not loading. I would like to get the program to load this info. I don't think I missed a setting, but any help would be appreciated.

2) I was able to load the file address in the Manual section on the same JTAlerts menu page. An FT-8 contact is now transferring to ACLog, but it always brings up the popup box that essentially says it could not verify the contact was successfully logged. Any help in delaying the popup until it can verify it successfully, or speeding up the process so I get the "successful" popup box would be appreciated.

Thanks much for any help. If there is help topic info out there that addresses this, please send me a link.  CUL & 73s  Jim  W7JWT

If the QSOs are getting logged that indicates you have the network component of the settings correct.

JTAlert reporting that it was unable to confirm the QSO was logged indicates that JTAlert was unable to find the newly logged QSO in the log file. The likely cause is that you have not selected the location of the currently enabled log file. Make sure you have selected the correct log type and the log file location/name.

   

de Laurie VK3AMA


locked How Does "Rebuild Alert DB" Work?

Paul N3PS
 

Until now, I have the Wanted DX alert set up for Any Band, Any Mode . . .  I have been manually updating the Wanted / Not Wanted settings in JT Alert as I work a new country and subsequently receive a QSL card or LoTW confirmation.

Now that I have hit the DXCC 200, I want to move into working for the 5 Band DXCC and DXCC Challenge.  To do this, I will need to change the Wanted DX alert from Any Band, to the By Individual Band setting.

In moving to the By Individual Band setting, I don't want to have to manually update the Wanted / Not Wanted countries if I don't have to . . 

Can someone explain how the Rebuild Alert DB function works?  Does it scan my HRD logbook or a log that WSJTX and/or JT Alert maintains?  Does it just look to determine if the country has been worked, or can it be set up to also look if there is a QSL confirmation?

--
Paul / N3PS


locked Worked but unconfirmed countries are showing up as "unwanted"

Jim Cary
 

Worked but unconfirmed countries are showing up as "unwanted" in the band alert table even though the criteria for "unwanted" is a LoTW confirmation, which does not exist..  This started once I downloaded the current version.

I had this problem when I first installed JTAlert on this computer and with a long conversation with Mike Black we he was able to figure out that it was a registry problem and he was able to fix it.  I'm afraid the same situation might have happened again.   While I obviously need help to fix the current situation, the more important one is to make sure this doesn't happen with future software updates.

I did uninstall and reinstall the current version but with the same results.

Any help would be appreciated.

Jim, W2SM
JimLCary@...


locked ACLog interface #FT8

James Tills W7JWT Stevens County DEM
 

I am using JTAlerts with ACLog and FT-8. I have two issues:

1) Under the ACLog menu item in JTAlerts settings, you can select to use ACLog. However, the file address that JTAlerts is supposed to load automatically, is not loading. I would like to get the program to load this info. I don't think I missed a setting, but any help would be appreciated.

2) I was able to load the file address in the Manual section on the same JTAlerts menu page. An FT-8 contact is now transferring to ACLog, but it always brings up the popup box that essentially says it could not verify the contact was successfully logged. Any help in delaying the popup until it can verify it successfully, or speeding up the process so I get the "successful" popup box would be appreciated.

Thanks much for any help. If there is help topic info out there that addresses this, please send me a link.  CUL & 73s  Jim  W7JWT


locked Re: Dark Mode

KB9HGI <kb9hgi@...>
 

Thanks Laurie for the update sounds cool!

 

Steve KB9HGI

 

Sent from Mail for Windows

 

From: HamApps Support (VK3AMA)
Sent: Thursday, October 28, 2021 9:42 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Dark Mode

 

On 29/10/2021 3:17 am, KB9HGI wrote:

Any plans for Dark mode on JT Alert? I run dark mode on wsjt-x  and everything else and JT-alert looks strange. Dark mode easier on the eyes to me


Yes there are plans.

Currently, color theming is in transition as I move the old code-base over to the new NET 5 code base.
The old code, the main JTAlert window will not change as eventually it will be gone completely. The new 2.50.x introduced windows already support custom coloring. There is no "Dark Mode" but you can adjust the colors of the different elements of a window to produce a dark effect.

The user-defined coloring as it currently exists, defined on a per-window basis, will be getting changed to a centralized theme coloring operation in the future when the remaining old JTAlert code is migrated. That theme/coloring will support saving & restoring custom user coloring along with predefined light & dark themes. That however is still some time away.

de Laurie VK3AMA

 


locked Re: Dark Mode

HamApps Support (VK3AMA)
 

On 29/10/2021 3:17 am, KB9HGI wrote:
Any plans for Dark mode on JT Alert? I run dark mode on wsjt-x  and everything else and JT-alert looks strange. Dark mode easier on the eyes to me

Yes there are plans.

Currently, color theming is in transition as I move the old code-base over to the new NET 5 code base.
The old code, the main JTAlert window will not change as eventually it will be gone completely. The new 2.50.x introduced windows already support custom coloring. There is no "Dark Mode" but you can adjust the colors of the different elements of a window to produce a dark effect.

The user-defined coloring as it currently exists, defined on a per-window basis, will be getting changed to a centralized theme coloring operation in the future when the remaining old JTAlert code is migrated. That theme/coloring will support saving & restoring custom user coloring along with predefined light & dark themes. That however is still some time away.

de Laurie VK3AMA


locked Re: Can not click on the call sign.

W8BBX John
 

Mike and Joe,

No I had not checked Settings/WSJT-X UDP Multicast on Loopback .
But I did. and now the operating state shows


UDP MCast on LB is now True, it was not before, but JTAlert was working before I did this.

Then I went to the WSJT Settings |Reporting and changed the server to 224.0.0.1.  That did not work, no CQ's showing on the Callsigns screen.
Then I went to the WSJT Settings |Reporting and changed the server back to 127.0.0.1.  That did  work, CQ's are showing on the Callsigns screen.

I left the checked, the Settings/WSJT-X UDP Multicast on Loopback .

And it still works.

Thank you
, folks.

W8BBX   John


locked Dark Mode

KB9HGI <kb9hgi@...>
 

Any plans for Dark mode on JT Alert? I run dark mode on wsjt-x  and everything else and JT-alert looks strange. Dark mode easier on the eyes to me


locked Re: Can not click on the call sign.

Joe Subich, W4TV
 

JTAlert Main Window Settings Menu ... top item. Check it.

See item 4 in Help -> WSJT-X UDP Setup

73,

... Joe, W4TV

On 2021-10-28 8:34 AM, John via groups.io wrote:
Still does not work.
I set the Wsjtx reply to Single click, it was set on Double click.
Photo WSJT-X Reporting.
.
Photo showing current screen on 224.0.0.1
File is from  About JTAlert  224.
How do I change the  JTAlert "Multicast on loopback"?
73  W8BBX


locked Re: Can not click on the call sign.

Michael Black
 


On the multicast setup did you check Settings/WSJT-X UDP Multicast on Loopback ?


Mike W9MDB


locked Re: Can not click on the call sign.

W8BBX John
 

IT Works.

I changed WSJT reporting to 127 AND checked the boxes.





File is from About  had to end JTAlert, then restart before it showed changes to WSJT-X reporting ( I think).


THANK YOU

W8BBX   John


locked Re: Can not click on the call sign.

W8BBX John
 

Still does not work.
I set the Wsjtx reply to Single click, it was set on Double click.
Photo WSJT-X Reporting. 
.

 Photo showing current screen on 224.0.0.1


File is from  About JTAlert  224.

How do I change the  JTAlert "Multicast on loopback"?

73  W8BBX


locked Re: New Release

Ken Bills
 

Thank for the update and great product.

73
Ken-W9KB


locked Re: New Release

HamApps Support (VK3AMA)
 

On 28/10/2021 4:29 am, Ken Bills via groups.io wrote:
Senior moment? I thought I read a post this past week about an upcoming new release with extensive changes. I can not seem to find the post. User files written to different directories etc.

73
Ken-W9KB

There have been no announcements of any upcoming release. I do make comment in some messages about fixes and changes that will be part of the next release, but there is never a date published ahead of time.

The HamApps.com website is the official source of JTAlert release downloads. The latest is 2.50.7

The only discussion about files in different directories was a brief comment by me in the Beta Group. I don't believe you're a member of that restricted group so if that was the source of your information it must have been passed on by one of the group members. Discussions in that group can often be wide-ranging about possible future functionality changes/enhancements/additions and don't necessarily reflect imminent changes.

Custom file-storage locations is on my todo-list, but not imminent, and definitely not for the next public release.

de Laurie VK3AMA
 


locked Re: Can not click on the call sign.

HamApps Support (VK3AMA)
 

On 28/10/2021 11:40 am, John via groups.io wrote:
I am new to JTAlert, but it works fine, except I can not click on the call sign and get WSJT_X to transmit the call sign.  I have to go to the WSJT screen and click on the call.
Did  |Help |UDP Setup, but I get nothing on the call screen, after the first one.
First time I tried the setup, click on the CQ on the Callsign and WSJT transmitted.

A photo of no call signs, WSJT_X revisions, JTAlert About.
 There is no WSJT-X UDP ID.


The attachment comes from  JTAlert About.
I changed back to 127.0.0.1, took out the checkmarks, and it works, except I still have to click on WSJT-X
Can anyone help.

John W8BBX

The About window not showing a UDP ID in the "Current Operating State" section indicates that JTAlert has never received a UDP message from WSJT-X. Unfortunately your image doesn't show all the status, so I am guessing that the "WSJT-X UDP MCast on LB" was showing false. While your WSJT-X UDP settings look fine, it is likely not having the JTAlert "Multicast on loopback" setting enabled is the cause of no UDP comms from WSJTX.

As for WSJTX not going into TX when a callsign is clicked or double-clicked (depending on how JTAlert is set) in JTAlert, that is controlled by WSJTX. JTAlert cannot direct WSJTX to go into transmit. If the DXCall is getting populated in WSJTX after a click event in JTAlert than JTAlert is behaving correctly in sending the appropriate instruction to WSJTX.

How do you have the JTAlert Callsigns window "Wsjtx reply" option set? Is it set to single or double click and is that how you're interacting with the callsigns? Perhaps you have it set to "Disabled"



de Laurie VK3AMA


1121 - 1140 of 38444