Date   

locked Re: JTALERT "B4"

Steve Roth - AD4K
 

I tried various things, including a 10 sec delay.  I got the same error.  It does put something in HRD logbook but the date is missing as well as some of the other fields.  It also puts a logbook entry direct from WSJT-X with everything correct.

I am thinking that there are other settings in WSJT-X and JTALERT which may be impacting things working correctly - i.e., JTALERT talking to WSJT-X and both talking to HRD Logbook.  Perhaps not, but that is my feeling after reviewing some YouTube sessions discussing similarities with my setup.  For example, there is a "QSO Forwarding" setup page in HRD Logbook.  My current settings do not match those that I found on several YouTube sessions.  I would like to find a person who is using the same setup I have (WSJT-X and JTALERT and HRD Logbook) so I could get screen shots of their setup.

I am usually pretty good at this stuff but not this time.  The setup I have is working, albeit not the best configuration and lacking in correct B4 data.

Just as an experiment I set my HRD Logging to on, then did a  Rebuild Alert Database.  That messed up the alert data for DXCC worked and wiped out the States Worked data.  I recovered from that as I keep good records of my current stuff before messing with new stuff..

I truly appreciate your help.  But, I regret bothering you.


On Mon, Aug 23, 2021 at 12:05 PM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
Okay, I will keep trying.... Thanks

On Mon, Aug 23, 2021 at 9:40 AM neil_zampella <neilz@...> wrote:

The error just said that JTAlert couldn't verify that the QSO was updated, that could mean that the delay setting in JTAlert was not long enough.   The grayed 'B4' file is not a bad thing, its normal as JTAlert is going to your main log for all the older B4 data which means its updating each time you start the program.

You said that JTAlert showed the QSO as B4, and that's what you want.     As far as it colored red, that's a personal preference, I have mine setup fo show B4 as gray.

None of that (other than the verification) is a 'bad result'.   You can try increasing the time JTAlert pauses before it verifies the QSO was logged, or just turn that verification off.

Neil, KN3ILZ


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Okay, I will keep trying.... Thanks

On Mon, Aug 23, 2021 at 9:40 AM neil_zampella <neilz@...> wrote:

The error just said that JTAlert couldn't verify that the QSO was updated, that could mean that the delay setting in JTAlert was not long enough.   The grayed 'B4' file is not a bad thing, its normal as JTAlert is going to your main log for all the older B4 data which means its updating each time you start the program.

You said that JTAlert showed the QSO as B4, and that's what you want.     As far as it colored red, that's a personal preference, I have mine setup fo show B4 as gray.

None of that (other than the verification) is a 'bad result'.   You can try increasing the time JTAlert pauses before it verifies the QSO was logged, or just turn that verification off.

Neil, KN3ILZ


locked Music note colors

NA2NY - John Hart
 

Are the music note colors to be different on the different windows?  With JTDX they are mixed red and blue, but on WSJT-X they are all red.
I think on my W7 machine the were all the same color for each program.

Running W10  20H2 build 19042.1165    JTAlert 2.50.5

Thanks  John  NA2NY


locked Re: JTALERT "B4"

neil_zampella
 

The error just said that JTAlert couldn't verify that the QSO was updated, that could mean that the delay setting in JTAlert was not long enough.   The grayed 'B4' file is not a bad thing, its normal as JTAlert is going to your main log for all the older B4 data which means its updating each time you start the program.

You said that JTAlert showed the QSO as B4, and that's what you want.     As far as it colored red, that's a personal preference, I have mine setup fo show B4 as gray.

None of that (other than the verification) is a 'bad result'.   You can try increasing the time JTAlert pauses before it verifies the QSO was logged, or just turn that verification off.

Neil, KN3ILZ


locked Re: JTALERT B4 and Wanted call

Jim N6VH
 

On 8/22/2021 9:28 AM, Bob Frostholm wrote:
Thank you Jim,

That worked

73

Bob

Ko6Lu
Bob,

Great! Glad I could help.

73,

Jim N6VH


locked Re: JTALERT B4 and Wanted call

Bob Frostholm
 

Thank you Jim,

That worked

73

Bob

Ko6Lu

On 8/21/2021 11:45 AM, Jim N6VH via groups.io wrote:

On 8/21/2021 8:44 AM, Bob Frostholm wrote:
Hi Laurie,

As many have said, THANKS for the wonderful work you do to enhance our hobby.

I have an observation that may not have a solution.

I chase grids among other things...a fun way is chasing ships at sea as they progress through many unpopulated GRID squares of our oceans. Tonight after working RA0LQ/mm for the umpteenth time, I decided to add his call to the wanted call page. It see though, that since I have worked him before, it overrides my wanted call alert. I don't want to disable worked before as that would create havoc for me while waiting for his precious call to be decoded.

Since Worked B4 does not appear on the alerts priority I don't see a way to possibly  overcome this dilemma.

Is there a solution?

73

Bob

Ko6Lu
Bob,

Go to Settings - Alerts - Miscellaneous Alerts - Wanted Callsign. Under Options, check "Alert when decoded Callsign worked B4".

73,

Jim N6VH




--
Bob
KO6LU


locked Re: Prob Decode Windows

Johan Barre
 

hi 

@laurie the translate is correct, i do the delete and test always same probleme 
@Neil just reinstall .net desktop 64 bits and jtalert64bits my system is also 64 bits last windows reinstallation yesterday without antivirus malware after test probleme always present 
snif 

regards 




Le dim. 22 août 2021 à 00:20, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> a écrit :
On 22/08/2021 7:34 am, Johan Barre wrote:
hi all this day i have install jtalert for wsjt same prob
desktop runtime 5.0.9 installed 
anyone have an idea ?
Regards F4HHL


Le ven. 20 août 2021 à 10:55, Johan Barre <johan.barre@...> a écrit :
Hi all
 just reinstall my radio Pc 
i have apron with JTAlert for JTDX when windows decode is open i ahev this message 
image.png
Uninstall my AV/ reinstall software/reboot install a ols version always the same 
any idea ?

regards F4HHL JOHAN 

Johan,

Google translate says "cessé de fonctionner" translates as "stopped working". Is that correct?

Is it only the Decodes window that is having problems? If so it is likely a problem with the decodes database file. Do the following
  • Stop JTAlert
  • Use Windows file explorer and navigate to %localappdata%\HamApps\JTAlert\F4HHL\Decode\ then delete all files in that directory with names starting with "decodes.sqlite", there may be several.
  • After they have been deleted start JTAlert and try an open the Decodes window.
Let me know if that works for you.

de Laurie VK3AMA


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

I changed the JTALERT and WSJT-X settings back to the way I originally had then and made a successful contact which put it into my HRD logbook correctly, added "B4" to the contact's tile and the tile turned red.  The "Log B4 database was back and it was updated at the time I made the last log entry for my contact.

Regards, Steve


On Sun, Aug 22, 2021 at 9:34 AM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
Oh also, the "Logged B4 Database" in JTALERT is grayed out.

On Sun, Aug 22, 2021 at 9:31 AM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
Okay, I applied the changes you suggested (other than change the MS Access database) with bad results.  I rebooted JTALERT and WSJT-X everything after I made the changes.  Here is what I saw.  KZ9DX had a "B4" added to his call tile on JTALERT and it turned red.

Log Error.jpg
Log w error.jpg
Log Error 2.jpg

On Sun, Aug 22, 2021 at 8:41 AM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
I will make the changes and let you know.

With my current settings I am getting all the audio alerts (new country, wanted callsign, etc.) and the B4 was working for all.  I recently ran into some B4 issues.

Thanks for the help, I want to get this correct.  Will advise.

Regards, Steve Roth  AD4K

On Sun, Aug 22, 2021 at 7:53 AM neil_zampella <neilz@...> wrote:

In your first post you said :

"I am using HRD with with HRD logging system.  I have no boxes checked on the JTALERT "Worked B4" setting.  I let HRD Logbook do my logging direct from WSJT-X.  Under the JTALERT Setting "Logging" I have nothing selected and never have.  I never noticed this issue before.

In which case I'm surprised you were getting any B4 notifications in JTAlert at all.   JTAlert must have access to the log in order to do the B4 checks from prior contacts..   

Turn ON the JTAlert HRD logging by checking ENABLE HRD V5/V6 logging in JTAlert.   Turn OFF the secondary UDP settings in WSJT-X.  

I've also seen threads about issues with the MS Access database in HRD.   I'd convert your log to the other database option, Maria DB.    Do a database backup before you do this.

This allows JTAlert to properly signal all alerts based on real-time data using logbook confirmations etc, from LoTW and eQSL.

 

Neil, KN3iLZ

 

On Sat, Aug 21, 2021 at 07:58 PM, Steve Roth - AD4K wrote:

Okay, I believe you.  The way it works now it gives me B4 data.  Lately I have been having issues with unreliable B4 data.
 
What is the correct way to do it?  I am all ears as having seen your advice in past I believe you can help.
 
Thanks, Steve


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Oh also, the "Logged B4 Database" in JTALERT is grayed out.

On Sun, Aug 22, 2021 at 9:31 AM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
Okay, I applied the changes you suggested (other than change the MS Access database) with bad results.  I rebooted JTALERT and WSJT-X everything after I made the changes.  Here is what I saw.  KZ9DX had a "B4" added to his call tile on JTALERT and it turned red.

Log Error.jpg
Log w error.jpg
Log Error 2.jpg

On Sun, Aug 22, 2021 at 8:41 AM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
I will make the changes and let you know.

With my current settings I am getting all the audio alerts (new country, wanted callsign, etc.) and the B4 was working for all.  I recently ran into some B4 issues.

Thanks for the help, I want to get this correct.  Will advise.

Regards, Steve Roth  AD4K

On Sun, Aug 22, 2021 at 7:53 AM neil_zampella <neilz@...> wrote:

In your first post you said :

"I am using HRD with with HRD logging system.  I have no boxes checked on the JTALERT "Worked B4" setting.  I let HRD Logbook do my logging direct from WSJT-X.  Under the JTALERT Setting "Logging" I have nothing selected and never have.  I never noticed this issue before.

In which case I'm surprised you were getting any B4 notifications in JTAlert at all.   JTAlert must have access to the log in order to do the B4 checks from prior contacts..   

Turn ON the JTAlert HRD logging by checking ENABLE HRD V5/V6 logging in JTAlert.   Turn OFF the secondary UDP settings in WSJT-X.  

I've also seen threads about issues with the MS Access database in HRD.   I'd convert your log to the other database option, Maria DB.    Do a database backup before you do this.

This allows JTAlert to properly signal all alerts based on real-time data using logbook confirmations etc, from LoTW and eQSL.

 

Neil, KN3iLZ

 

On Sat, Aug 21, 2021 at 07:58 PM, Steve Roth - AD4K wrote:

Okay, I believe you.  The way it works now it gives me B4 data.  Lately I have been having issues with unreliable B4 data.
 
What is the correct way to do it?  I am all ears as having seen your advice in past I believe you can help.
 
Thanks, Steve


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Okay, I applied the changes you suggested (other than change the MS Access database) with bad results.  I rebooted JTALERT and WSJT-X everything after I made the changes.  Here is what I saw.  KZ9DX had a "B4" added to his call tile on JTALERT and it turned red.

Log Error.jpg
Log w error.jpg
Log Error 2.jpg


On Sun, Aug 22, 2021 at 8:41 AM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
I will make the changes and let you know.

With my current settings I am getting all the audio alerts (new country, wanted callsign, etc.) and the B4 was working for all.  I recently ran into some B4 issues.

Thanks for the help, I want to get this correct.  Will advise.

Regards, Steve Roth  AD4K

On Sun, Aug 22, 2021 at 7:53 AM neil_zampella <neilz@...> wrote:

In your first post you said :

"I am using HRD with with HRD logging system.  I have no boxes checked on the JTALERT "Worked B4" setting.  I let HRD Logbook do my logging direct from WSJT-X.  Under the JTALERT Setting "Logging" I have nothing selected and never have.  I never noticed this issue before.

In which case I'm surprised you were getting any B4 notifications in JTAlert at all.   JTAlert must have access to the log in order to do the B4 checks from prior contacts..   

Turn ON the JTAlert HRD logging by checking ENABLE HRD V5/V6 logging in JTAlert.   Turn OFF the secondary UDP settings in WSJT-X.  

I've also seen threads about issues with the MS Access database in HRD.   I'd convert your log to the other database option, Maria DB.    Do a database backup before you do this.

This allows JTAlert to properly signal all alerts based on real-time data using logbook confirmations etc, from LoTW and eQSL.

 

Neil, KN3iLZ

 

On Sat, Aug 21, 2021 at 07:58 PM, Steve Roth - AD4K wrote:

Okay, I believe you.  The way it works now it gives me B4 data.  Lately I have been having issues with unreliable B4 data.
 
What is the correct way to do it?  I am all ears as having seen your advice in past I believe you can help.
 
Thanks, Steve


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

I will make the changes and let you know.

With my current settings I am getting all the audio alerts (new country, wanted callsign, etc.) and the B4 was working for all.  I recently ran into some B4 issues.

Thanks for the help, I want to get this correct.  Will advise.

Regards, Steve Roth  AD4K


On Sun, Aug 22, 2021 at 7:53 AM neil_zampella <neilz@...> wrote:

In your first post you said :

"I am using HRD with with HRD logging system.  I have no boxes checked on the JTALERT "Worked B4" setting.  I let HRD Logbook do my logging direct from WSJT-X.  Under the JTALERT Setting "Logging" I have nothing selected and never have.  I never noticed this issue before.

In which case I'm surprised you were getting any B4 notifications in JTAlert at all.   JTAlert must have access to the log in order to do the B4 checks from prior contacts..   

Turn ON the JTAlert HRD logging by checking ENABLE HRD V5/V6 logging in JTAlert.   Turn OFF the secondary UDP settings in WSJT-X.  

I've also seen threads about issues with the MS Access database in HRD.   I'd convert your log to the other database option, Maria DB.    Do a database backup before you do this.

This allows JTAlert to properly signal all alerts based on real-time data using logbook confirmations etc, from LoTW and eQSL.

 

Neil, KN3iLZ

 

On Sat, Aug 21, 2021 at 07:58 PM, Steve Roth - AD4K wrote:

Okay, I believe you.  The way it works now it gives me B4 data.  Lately I have been having issues with unreliable B4 data.
 
What is the correct way to do it?  I am all ears as having seen your advice in past I believe you can help.
 
Thanks, Steve


locked Re: Prob Decode Windows

neil_zampella
 

Joe ...

You're right ... just didn't think someone would install the 32 bit version of JTAlert on a 64 bit Windows system.

Neil, KN3ILZ

 

No, select 64 bit (x64) if you have installed the 64 bit version of
JT-Alert and select 32 (x86) bit if you have installed the 32 bit
version of JT-Alert.


locked Re: JTALERT "B4"

neil_zampella
 

In your first post you said :

"I am using HRD with with HRD logging system.  I have no boxes checked on the JTALERT "Worked B4" setting.  I let HRD Logbook do my logging direct from WSJT-X.  Under the JTALERT Setting "Logging" I have nothing selected and never have.  I never noticed this issue before.

In which case I'm surprised you were getting any B4 notifications in JTAlert at all.   JTAlert must have access to the log in order to do the B4 checks from prior contacts..   

Turn ON the JTAlert HRD logging by checking ENABLE HRD V5/V6 logging in JTAlert.   Turn OFF the secondary UDP settings in WSJT-X.  

I've also seen threads about issues with the MS Access database in HRD.   I'd convert your log to the other database option, Maria DB.    Do a database backup before you do this.

This allows JTAlert to properly signal all alerts based on real-time data using logbook confirmations etc, from LoTW and eQSL.

 

Neil, KN3iLZ

 

On Sat, Aug 21, 2021 at 07:58 PM, Steve Roth - AD4K wrote:

Okay, I believe you.  The way it works now it gives me B4 data.  Lately I have been having issues with unreliable B4 data.
 
What is the correct way to do it?  I am all ears as having seen your advice in past I believe you can help.
 
Thanks, Steve


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Okay, I believe you.  The way it works now it gives me B4 data.  Lately I have been having issues with unreliable B4 data.

What is the correct way to do it?  I am all ears as having seen your advice in past I believe you can help.

Thanks, Steve


On Sat, Aug 21, 2021 at 5:51 PM neil_zampella <neilz@...> wrote:

You do realize that this will not give you any alerts from JTAlert as it has no access to see if you worked anyone before on any mode.

Neil, KN3ILZ


locked Re: Prob Decode Windows

HamApps Support (VK3AMA)
 

On 22/08/2021 7:34 am, Johan Barre wrote:
hi all this day i have install jtalert for wsjt same prob
desktop runtime 5.0.9 installed 
anyone have an idea ?
Regards F4HHL


Le ven. 20 août 2021 à 10:55, Johan Barre <johan.barre@...> a écrit :
Hi all
 just reinstall my radio Pc 
i have apron with JTAlert for JTDX when windows decode is open i ahev this message 
image.png
Uninstall my AV/ reinstall software/reboot install a ols version always the same 
any idea ?

regards F4HHL JOHAN 

Johan,

Google translate says "cessé de fonctionner" translates as "stopped working". Is that correct?

Is it only the Decodes window that is having problems? If so it is likely a problem with the decodes database file. Do the following
  • Stop JTAlert
  • Use Windows file explorer and navigate to %localappdata%\HamApps\JTAlert\F4HHL\Decode\ then delete all files in that directory with names starting with "decodes.sqlite", there may be several.
  • After they have been deleted start JTAlert and try an open the Decodes window.
Let me know if that works for you.

de Laurie VK3AMA


locked Re: Prob Decode Windows

Joe Subich, W4TV
 

On 2021-08-21 5:57 PM, neil_zampella wrote:
and select the x64 version if you have a 64 bit version of WIndows,
and the x86 version for 32 bit.
No, select 64 bit (x64) if you have installed the 64 bit version of
JT-Alert and select 32 (x86) bit if you have installed the 32 bit
version of JT-Alert.

In *BOTH* cases make sure you select the *DESKTOP* (Run Desktop apps)
version of Dot Net 5.0 and *NOT* the "console" (Run Console apps)
version.

73,

... Joe, W4TV


On 2021-08-21 5:57 PM, neil_zampella wrote:
Are you saying you have the runtime 5.0.9 installed?   Are you sure you installed the correct version for your computer?  32 bit or 64 bit??
You download it from here: https://dotnet.microsoft.com/download/dotnet/5.0/runtime <https://dotnet.microsoft.com/download/dotnet/5.0/runtime>
and select the x64 version if you have a 64 bit version of WIndows, and the x86 version for 32 bit.
Neil, KN3ILZ


locked Re: Prob Decode Windows

neil_zampella
 

Are you saying you have the runtime 5.0.9 installed?   Are you sure you installed the correct version for your computer?  32 bit or 64 bit??

You download it from here: https://dotnet.microsoft.com/download/dotnet/5.0/runtime

and select the x64 version if you have a 64 bit version of WIndows, and the x86 version for 32 bit.

 

Neil, KN3ILZ


locked Re: Logger32 +JTAlert+IC-7300

neil_zampella
 

You're directly logging to Logger32, correct?    I suspect its taking control of the UDP port.  Look under HELP for Multicast setup.  If Logger32 can handle Multicasting UDP packets, then setting up WSJT-X for Multicast would allow both JTAlert and the logger to work.

 

Neil, KN3ILZ


locked Re: JTALERT "B4"

neil_zampella
 

You do realize that this will not give you any alerts from JTAlert as it has no access to see if you worked anyone before on any mode.

Neil, KN3ILZ


locked Re: Prob Decode Windows

Johan Barre
 

hi all this day i have install jtalert for wsjt same prob
desktop runtime 5.0.9 installed 
anyone have an idea ?
Regards F4HHL


Le ven. 20 août 2021 à 10:55, Johan Barre <johan.barre@...> a écrit :
Hi all
 just reinstall my radio Pc 
i have apron with JTAlert for JTDX when windows decode is open i ahev this message 
image.png
Uninstall my AV/ reinstall software/reboot install a ols version always the same 
any idea ?

regards F4HHL JOHAN 


1141 - 1160 of 37815