Date   

locked Re: Wanted VE Provinces not working #FT8

g4wjs
 

Mike,

so are you saying the OPs's issue was that he had entered a port number in WSJT-X that was not available?

As an aside, Amateur Radio is  technical hobby and many enjoy the challenge of getting complex systems working to their satisfaction. IMHO attempts to dumb down the setup of complex things leads to more issues than exposing the real details does.

73
Bill
G4WJS.

On 27/08/2021 05:09, Michael Black via groups.io wrote:
No...not the incorrect NET....he'd gotten JTAlert working before we connected and just had to tweak his setup.
Was using noise reduction which needed to turn off.

All the setup required is a bit daunting for new users.  There's not much software out there which has 3 separate components to set up before things work the way one wants

It seems to me we need a "JTAlert" setup button in WSJTX and the loggers.  Asking people to enter port numbers and such when don't understand what a port number is can be more than confusing for many.

The Help in JTAlert does help for those who understand what it means or who are willing to blindly follow direction without understanding what it means.  But if you have a questioning mind you look at the directions and go "what does that mean?".  Not sure there's a good way to explain it for everybody -- even trying to draw a communication diagram assumes people understand a communication path.

For operators who grew up twiddling knobs the new rigs with all the options and the myriad options in all the software is a bit much.   Usually new information takes a while to sink in for most people and you can only fill it up so much at once.

Mike W9MDB




On Thursday, August 26, 2021, 10:54:19 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/08/2021 1:43 pm, Michael Black via groups.io wrote:
I did get with Dan and he's operating just fine now.

Things can get a little complicated and people get themselves wrapped around the axle and frustration bubbles up to the surface.  

Mike W9MDB

Tnx Mike,

Any chance you can say what was wrong or will it bee too embarrassing for the OP? Was it an incorrect NET install?

de Laurie VK3AMA



--
73
Bill
G4WJS.


locked Re: JTAlert 2.50.0 Not Working

Tom Melvin
 

Morning

Ok you downloaded 2.50. - did that resolve the problem?

Tom
GM8MJV


On 27 Aug 2021, at 02:06, Harry Hall via groups.io <hhallcosd@...> wrote:

Well perhaps I am using the wrong wording I download the new version 2.50 etc 
 
Sent from Mail for Windows
 
From: Tom Melvin
Sent: Friday, August 20, 2021 3:12 AM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working
 
Harry
 
What ‘Crashes’ - first time seen the word crash mentioned in your posts.
 
Is it the install of Net 5.0.8 ? If so that is a Microsoft issue.
 
If it installed and JTAlert crashes pretty sure there will be an error message somewhere on the screen with crash details.
 
If you are seeing ????m in the main window   it is definitely an issue with JTAlert not getting any info from WSJT-X. The port is being blocked by OS, Anti-Malware, Anti Virus, incorrect settings WSJT-X.  Is there any heading in the box with ???? in it - may be worth posting a screen shot showing that box - not the whole desktop - cut/snip the window.
 
To rule out the Net issue can you confirm that it installs ok, no errors and PC is OK BEFORE you start to play with HRD, JTAlert, WSJT-X etc.
 
Regards
TOM
GM8MJV
 


On 20 Aug 2021, at 06:17, Harry Hall via groups.io <hhallcosd@...> wrote:
 
Yes twice and each time its crashes and JT Alert will not see anything???
 
Sent from Mail for Windows
 
From: Joe Subich, W4TV
Sent: Friday, August 13, 2021 7:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working
 
 
Have you installed the *CORRECT VERSION* of NET 5.0.8?
 
You must install the *DESKTOP* version and match 64 or 32 bit
to the version of JTAlert you have installed.
 
THIS IS ALL IN THE DOCUMENTATION.
 
73,
 
    ... Joe, W4TV
 
 
On 2021-08-13 9:32 PM, Harry Hall via groups.io wrote:
> Outstanding done logging back on track.  A friend ham down the road has 
> an old win7 computer of mine he says he uploaded to 2.50.0 with no 
> problems I am going to hold off trying it again because nothing works on 
> jtalert after install, no sound, no logging, no way to open any of the 
> windows to show the call signs decoding.  You just get one box full of 
> ????? near the top on 2.50.0.
> 
> Hers what we are using JTAlert 2.16.17 K5HLH {17M, ft8,hrd6+,Filter, #1} 
> (Updates)
> 
> WSJT-X v2.40 by K1JT, G4WJS, K9AN, and IV3NWV
> 
> Device name      HarryHall-PC
> 
> Processor            AMD Phenom(tm) II X4 945 Processor   3.00 GHz
> 
> Installed RAM    8.00 GB
> 
> Device ID             C2DB017D-2A54-403B-B1A4-84D693AD8A5B
> 
> Product ID          00330-50000-00000-AAOEM
> 
> System type        64-bit operating system, x64-based processor
> 
> Pen and touch   No pen or touch input is available for this display
> 
> Edition  Windows 10 Pro
> 
> Version 20H2
> 
> Installed on        ‎6/‎19/‎2020
> 
> OS build               19042.1165
> 
> Experience          Windows Feature Experience Pack 120.2212.3530.0
> 
> Thanks for your time I am good on QRZ K5HLH 73’s
> 
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
> 
> *From: *HamApps Support (VK3AMA) <mailto:vk3ama.ham.apps@...>
> *Sent: *Friday, August 13, 2021 4:20 PM
> *Subject: *Re: [HamApps] JTAlert 2.50.0 Not Working
> 
> On 14/08/2021 8:08 am wrote:
> 
>     Up graded from 2.16.17 to 2.50.0 nothing worked.  Reloaded back down
>     to 2.16.17 took several days to start working again now it doubles
>     the log entry back to HRD.
> 
>     Device name HarryHall-PC
> 
>     Processor AMD Phenom(tm) II X4 945 Processor   3.00 GHz
> 
>     Installed RAM 8.00 GB
> 
>     Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B
> 
>     Product ID 00330-50000-00000-AAOEM
> 
>     System type 64-bit operating system, x64-based processor
> 
>     Pen and touch No pen or touch input is available for this display
> 
>     Edition Windows 10 Pro
> 
>     Version 20H2
> 
>     Installed on ‎6/‎19/‎2020
> 
>     OS build 19042.1165
> 
>     Experience Windows Feature Experience Pack 120.2212.3530.0
> 
> 
> OM,
> 
> "Nothing Works" is a very broad statement. You will need to be more 
> specific about what is not working.
> 
> As for Double-logging in HRD, that will be due to HRD listening for 
> logging events from WSJT-X and also the logging instruction sent by 
> JTAlert. You will need to turn off the "Enable logged contact ADIF 
> broadcast" setting in WSJTX, under the "Secondary UDP Server 
> (depreciated)" area of Reporting Tab of its Settings.
> 
> If that was not enabled, the extra logging will be coming via the 
> JTAlert "UDP Resend" option being enabled, you need to turn that off 
> under the "Applications -> WSJT-X/JTDX" section of the JTAlert Settings 
> window.
> 
> de Laurie VK3AMA
> 
 
 
 
 
 
 
 

 


locked Re: Wanted VE Provinces not working #FT8

Michael Black
 

No...not the incorrect NET....he'd gotten JTAlert working before we connected and just had to tweak his setup.
Was using noise reduction which needed to turn off.

All the setup required is a bit daunting for new users.  There's not much software out there which has 3 separate components to set up before things work the way one wants

It seems to me we need a "JTAlert" setup button in WSJTX and the loggers.  Asking people to enter port numbers and such when don't understand what a port number is can be more than confusing for many.

The Help in JTAlert does help for those who understand what it means or who are willing to blindly follow direction without understanding what it means.  But if you have a questioning mind you look at the directions and go "what does that mean?".  Not sure there's a good way to explain it for everybody -- even trying to draw a communication diagram assumes people understand a communication path.

For operators who grew up twiddling knobs the new rigs with all the options and the myriad options in all the software is a bit much.   Usually new information takes a while to sink in for most people and you can only fill it up so much at once.

Mike W9MDB




On Thursday, August 26, 2021, 10:54:19 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/08/2021 1:43 pm, Michael Black via groups.io wrote:
I did get with Dan and he's operating just fine now.

Things can get a little complicated and people get themselves wrapped around the axle and frustration bubbles up to the surface.  

Mike W9MDB

Tnx Mike,

Any chance you can say what was wrong or will it bee too embarrassing for the OP? Was it an incorrect NET install?

de Laurie VK3AMA


locked Re: Wanted VE Provinces not working #FT8

JTAlert Support (VK3AMA)
 

On 27/08/2021 1:43 pm, Michael Black via groups.io wrote:
I did get with Dan and he's operating just fine now.

Things can get a little complicated and people get themselves wrapped around the axle and frustration bubbles up to the surface.  

Mike W9MDB

Tnx Mike,

Any chance you can say what was wrong or will it bee too embarrassing for the OP? Was it an incorrect NET install?

de Laurie VK3AMA


locked Re: Wanted VE Provinces not working #FT8

Michael Black
 

I did get with Dan and he's operating just fine now.

Things can get a little complicated and people get themselves wrapped around the axle and frustration bubbles up to the surface.  

Mike W9MDB




On Thursday, August 26, 2021, 08:57:02 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/08/2021 11:34 am, Dan Bathker wrote:

Fighting overly complicated computer software that even talks to users in male Or female voice is just plain not worth the struggle.
Which is my Considered Opinion.


Bottom Line: Use valuable time for Radio, not so much for Computer Software.

Dan K6BLG

Hijacking other threads to push your dislike of JTAlert agenda is not cool. Your past postings indicate a dislike of Computer automation. If you dislike JTAlert so much, don't use it, a simple solution. Why are you bothering being a member of this group if all you going to do is complain and paint JTAlert as overly complicated. It is not, your the one, in my opinion, who is making it overly complicated. Help has been offered by Mike W9MDB, did you take that offer up? If not than what is the point of you being a member of this Support group.

de Laurie VK3AMA


locked Re: Wanted VE Provinces not working #FT8

John
 

Maybe the oop should  "Try a 3x5 inch (75x125 mm) paper card on which" he writes " I will not be a Jackass, I will not be a Jackass" and mount multiple copies throughout his house at eye level.

John
VE7KKQ

On Thu, Aug 26, 2021 at 6:57 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 27/08/2021 11:34 am, Dan Bathker wrote:

Fighting overly complicated computer software that even talks to users in male Or female voice is just plain not worth the struggle.
Which is my Considered Opinion.


Bottom Line: Use valuable time for Radio, not so much for Computer Software.

Dan K6BLG

Hijacking other threads to push your dislike of JTAlert agenda is not cool. Your past postings indicate a dislike of Computer automation. If you dislike JTAlert so much, don't use it, a simple solution. Why are you bothering being a member of this group if all you going to do is complain and paint JTAlert as overly complicated. It is not, your the one, in my opinion, who is making it overly complicated. Help has been offered by Mike W9MDB, did you take that offer up? If not than what is the point of you being a member of this Support group.

de Laurie VK3AMA


locked Re: Wanted VE Provinces not working #FT8

JTAlert Support (VK3AMA)
 

On 27/08/2021 11:34 am, Dan Bathker wrote:

Fighting overly complicated computer software that even talks to users in male Or female voice is just plain not worth the struggle.
Which is my Considered Opinion.


Bottom Line: Use valuable time for Radio, not so much for Computer Software.

Dan K6BLG

Hijacking other threads to push your dislike of JTAlert agenda is not cool. Your past postings indicate a dislike of Computer automation. If you dislike JTAlert so much, don't use it, a simple solution. Why are you bothering being a member of this group if all you going to do is complain and paint JTAlert as overly complicated. It is not, your the one, in my opinion, who is making it overly complicated. Help has been offered by Mike W9MDB, did you take that offer up? If not than what is the point of you being a member of this Support group.

de Laurie VK3AMA


locked Re: Wanted VE Provinces not working #FT8

Dan Bathker
 



Adrian VE7NZ wrote:
" ... works perfectly for all alerts except the Wanted VE Provinces Alert."
" ...
Any ideas?"

Suggestion:
Try a 3x5 inch (75x125 mm) paper card on which you write the VE Province callsign areas you still want.
Using transparent tape, attach over your op position.
Refer to from time to time and with pencil or pen check off those as worked.

As I do for VE VK DL and J callsign areas that I'm still looking for.

Fighting overly complicated computer software that even talks to users in male Or female voice is just plain not worth the struggle.
Which is my Considered Opinion.

Definition of considered opinion:


Bottom Line: Use valuable time for Radio, not so much for Computer Software.

Dan K6BLG
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

On 8/26/2021 1:28 PM, ve7nz wrote:
I recently updated JT-Alert. Love the idea of a Wanted VE Provinces Alert.  I rebuild my database regularly from HRD Logbook which confirms QSOs with LoTW.  This works perfectly for all alerts except the Wanted VE Provinces Alert.  Even though I can see which provinces I have worked in JT Alert, I get alerts for those provinces indicating they are ones I need - when I don't.

The setting look the same for WAS, DXCC, and VE Provinces but the results are different.

Any ideas?

Thx. Adrian VE7NZ

--
Dan Bathker
PO Box 23
La Canada CA 91012

d.bathker@...

Virus-free. www.avast.com


locked Re: JTAlert 2.50.0 Not Working

Harry Hall
 

Well perhaps I am using the wrong wording I download the new version 2.50 etc

 

Sent from Mail for Windows

 

From: Tom Melvin
Sent: Friday, August 20, 2021 3:12 AM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working

 

Harry

 

What ‘Crashes’ - first time seen the word crash mentioned in your posts.

 

Is it the install of Net 5.0.8 ? If so that is a Microsoft issue.

 

If it installed and JTAlert crashes pretty sure there will be an error message somewhere on the screen with crash details.

 

If you are seeing ????m in the main window   it is definitely an issue with JTAlert not getting any info from WSJT-X. The port is being blocked by OS, Anti-Malware, Anti Virus, incorrect settings WSJT-X.  Is there any heading in the box with ???? in it - may be worth posting a screen shot showing that box - not the whole desktop - cut/snip the window.

 

To rule out the Net issue can you confirm that it installs ok, no errors and PC is OK BEFORE you start to play with HRD, JTAlert, WSJT-X etc.

 

Regards

TOM

GM8MJV

 



On 20 Aug 2021, at 06:17, Harry Hall via groups.io <hhallcosd@...> wrote:

 

Yes twice and each time its crashes and JT Alert will not see anything???

 

Sent from Mail for Windows

 

From: Joe Subich, W4TV
Sent: Friday, August 13, 2021 7:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 Not Working

 

 

Have you installed the *CORRECT VERSION* of NET 5.0.8?

 

You must install the *DESKTOP* version and match 64 or 32 bit

to the version of JTAlert you have installed.

 

THIS IS ALL IN THE DOCUMENTATION.

 

73,

 

    ... Joe, W4TV

 

 

On 2021-08-13 9:32 PM, Harry Hall via groups.io wrote:

> Outstanding done logging back on track.  A friend ham down the road has 

> an old win7 computer of mine he says he uploaded to 2.50.0 with no 

> problems I am going to hold off trying it again because nothing works on 

> jtalert after install, no sound, no logging, no way to open any of the 

> windows to show the call signs decoding.  You just get one box full of 

> ????? near the top on 2.50.0.

> 

> Hers what we are using JTAlert 2.16.17 K5HLH {17M, ft8,hrd6+,Filter, #1} 

> (Updates)

> 

> WSJT-X v2.40 by K1JT, G4WJS, K9AN, and IV3NWV

> 

> Device name      HarryHall-PC

> 

> Processor            AMD Phenom(tm) II X4 945 Processor   3.00 GHz

> 

> Installed RAM    8.00 GB

> 

> Device ID             C2DB017D-2A54-403B-B1A4-84D693AD8A5B

> 

> Product ID          00330-50000-00000-AAOEM

> 

> System type        64-bit operating system, x64-based processor

> 

> Pen and touch   No pen or touch input is available for this display

> 

> Edition  Windows 10 Pro

> 

> Version 20H2

> 

> Installed on        ‎6/‎19/‎2020

> 

> OS build               19042.1165

> 

> Experience          Windows Feature Experience Pack 120.2212.3530.0

> 

> Thanks for your time I am good on QRZ K5HLH 73’s

> 

> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

> 

> *From: *HamApps Support (VK3AMA) <mailto:vk3ama.ham.apps@...>

> *Sent: *Friday, August 13, 2021 4:20 PM

> *Subject: *Re: [HamApps] JTAlert 2.50.0 Not Working

> 

> On 14/08/2021 8:08 am wrote:

> 

>     Up graded from 2.16.17 to 2.50.0 nothing worked.  Reloaded back down

>     to 2.16.17 took several days to start working again now it doubles

>     the log entry back to HRD.

> 

>     Device name HarryHall-PC

> 

>     Processor AMD Phenom(tm) II X4 945 Processor   3.00 GHz

> 

>     Installed RAM 8.00 GB

> 

>     Device ID C2DB017D-2A54-403B-B1A4-84D693AD8A5B

> 

>     Product ID 00330-50000-00000-AAOEM

> 

>     System type 64-bit operating system, x64-based processor

> 

>     Pen and touch No pen or touch input is available for this display

> 

>     Edition Windows 10 Pro

> 

>     Version 20H2

> 

>     Installed on ‎6/‎19/‎2020

> 

>     OS build 19042.1165

> 

>     Experience Windows Feature Experience Pack 120.2212.3530.0

> 

> 

> OM,

> 

> "Nothing Works" is a very broad statement. You will need to be more 

> specific about what is not working.

> 

> As for Double-logging in HRD, that will be due to HRD listening for 

> logging events from WSJT-X and also the logging instruction sent by 

> JTAlert. You will need to turn off the "Enable logged contact ADIF 

> broadcast" setting in WSJTX, under the "Secondary UDP Server 

> (depreciated)" area of Reporting Tab of its Settings.

> 

> If that was not enabled, the extra logging will be coming via the 

> JTAlert "UDP Resend" option being enabled, you need to turn that off 

> under the "Applications -> WSJT-X/JTDX" section of the JTAlert Settings 

> window.

> 

> de Laurie VK3AMA

> 

 

 

 

 

 

 

 

 


locked Re: Wanted VE Provinces not working #FT8

Monty Wilson, NR0A
 

The Wanted VE Provinces Alert works fine on my system.  It is a relatively new addition to the program.  Are you running the latest version?  I am running 2.50.5.  If so, then check the settings under Wanted VE Provence under the settings menu.  Make sure the Enable Wanted VE Provence Alert is checked.  I also checked the Use individual Province Name announcements  rather than the singular alert.

 

Hope this helps. 

 

Monty, NR0A

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of ve7nz
Sent: Thursday, August 26, 2021 03:28 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Wanted VE Provinces not working #FT8

 

I recently updated JT-Alert. Love the idea of a Wanted VE Provinces Alert.  I rebuild my database regularly from HRD Logbook which confirms QSOs with LoTW.  This works perfectly for all alerts except the Wanted VE Provinces Alert.  Even though I can see which provinces I have worked in JT Alert, I get alerts for those provinces indicating they are ones I need - when I don't.

The setting look the same for WAS, DXCC, and VE Provinces but the results are different.

Any ideas?

Thx. Adrian VE7NZ


locked Re: messaging not working

Tom Melvin
 

Hi

It’s a known issue - check the posts from last couple of days - ends with:


Tom
GM8MJV



On 26 Aug 2021, at 14:23, ke1ab <ke1ab@...> wrote:

Hello to the  Group

Noticed I wasn't getting messages, so tried sending a couple and no response. did an online  self test and no reply was received. checked JTAlert setting and windows messages all checked off, UDP loopback checked  off.  Messaging was working last week as I Rx a couple. Sorry wasn't paying attention to when it stopped working as I was not using it that much.

Everything else has been working great, so I'm wonder what I did to messed that up.  I reviewed  the group messages for ideas, so any further suggestions  would be appreciated   

Sean KE1AB


Here is the info dump
JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.5.0-rc5   by K1JT, G4WJS, K9AN, and IV3NWV
WSJT-X Command Line    : C:\WSJT\wsjtx\bin\wsjtx.exe
WSJT-X   --rig-name    :
WSJT-X Config File     : C:\Users\User\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.5.0-rc5
WSJT-X Revision        : 4030b0
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : WSJT-X
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 224.0.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema  : 3

==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 57931 57378
JTAlertV2.Manager.exe : 56004 56005 56006
JTAlertV2.Decodes.exe :


==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (2- High Definition Audio Device)
[2] Speakers (USB Audio CODEC )


==================================================
JTAlertV2.Manager (2.50.5.0) status
(2021-08-26 12:59:43 utc)
--------------------------------------------------
CLR Version       : 5.0.9
NET Framework     : .NET 5.0.9
Architecture      : x64 64bit
--------------------------------------------------
UDP Router        : Initialized : YES (WSJT-X)
Audio             : Initialized : YES (2 output devices)
Activity Service  : Initialized : YES (started : 58)
Messaging Service : Initialized : YES (started : 17)
HamSpots Service  : Initialized : YES
QRZ Xml           : Initialized : YES
HamQth Xml        : Initialized : YES
QRZ Log           : Initialized : YES
HamQth Log        : Initialized : YES
ClubLog Log       : Initialized : YES
Eqsl Log          : Initialized : YES
HrdLog Log        : Initialized : YES
DXLab DDE         : Initialized : YES
User Alert        : Initialized : YES
Updates Check     : Initialized : YES (started : 3600)
Environment Check : Initialized : YES (started : 3600)
Maintenance       : Initialized : YES (started : 3600)
--------------------------------------------------


locked Wanted VE Provinces not working #FT8

ve7nz
 

I recently updated JT-Alert. Love the idea of a Wanted VE Provinces Alert.  I rebuild my database regularly from HRD Logbook which confirms QSOs with LoTW.  This works perfectly for all alerts except the Wanted VE Provinces Alert.  Even though I can see which provinces I have worked in JT Alert, I get alerts for those provinces indicating they are ones I need - when I don't.

The setting look the same for WAS, DXCC, and VE Provinces but the results are different.

Any ideas?

Thx. Adrian VE7NZ


locked messaging not working

ke1ab
 

Hello to the  Group

Noticed I wasn't getting messages, so tried sending a couple and no response. did an online  self test and no reply was received. checked JTAlert setting and windows messages all checked off, UDP loopback checked  off.  Messaging was working last week as I Rx a couple. Sorry wasn't paying attention to when it stopped working as I was not using it that much.

Everything else has been working great, so I'm wonder what I did to messed that up.  I reviewed  the group messages for ideas, so any further suggestions  would be appreciated   

Sean KE1AB


Here is the info dump
JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.5.0-rc5   by K1JT, G4WJS, K9AN, and IV3NWV
WSJT-X Command Line    : C:\WSJT\wsjtx\bin\wsjtx.exe
WSJT-X   --rig-name    :
WSJT-X Config File     : C:\Users\User\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.5.0-rc5
WSJT-X Revision        : 4030b0
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : WSJT-X
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 224.0.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema  : 3

==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 57931 57378
JTAlertV2.Manager.exe : 56004 56005 56006
JTAlertV2.Decodes.exe :


==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (2- High Definition Audio Device)
[2] Speakers (USB Audio CODEC )


==================================================
JTAlertV2.Manager (2.50.5.0) status
(2021-08-26 12:59:43 utc)
--------------------------------------------------
CLR Version       : 5.0.9
NET Framework     : .NET 5.0.9
Architecture      : x64 64bit
--------------------------------------------------
UDP Router        : Initialized : YES (WSJT-X)
Audio             : Initialized : YES (2 output devices)
Activity Service  : Initialized : YES (started : 58)
Messaging Service : Initialized : YES (started : 17)
HamSpots Service  : Initialized : YES
QRZ Xml           : Initialized : YES
HamQth Xml        : Initialized : YES
QRZ Log           : Initialized : YES
HamQth Log        : Initialized : YES
ClubLog Log       : Initialized : YES
Eqsl Log          : Initialized : YES
HrdLog Log        : Initialized : YES
DXLab DDE         : Initialized : YES
User Alert        : Initialized : YES
Updates Check     : Initialized : YES (started : 3600)
Environment Check : Initialized : YES (started : 3600)
Maintenance       : Initialized : YES (started : 3600)
--------------------------------------------------


locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

Gia Fra
 

Buon giorno 
scusate  il problema forse questo

Install the .NET 5 Desktop Runtime choosing the bit version that matches your Windows bit version determined .
 
It is Important to choose the ".NET Desktop Runtime" NOT the non-desktop ".NET Runtime".




locked Re: Rebuild Alert Database

g4wjs
 

On 26/08/2021 13:55, Steve Roth - AD4K wrote:
So, the "aromatic system" should gather information from my connected logging system (HRD Logbook) and QSO's in session.  There is no "manually worked before tables", I only doing the manual corrections because they are missing when doing the JTALERT "Rebuild Alert Database". Perhaps I am missing your point.

Steve AD4K
Steve,

perhaps you need to review the settings you have for the "Rebuild Alert Database" categories, and also the alert settings. I suspect there is a discrepency between your expectations of what should be alerted and what you have asked JTAlert to track as confirmed. For example if you have unique alerts set for each digital mode JTAlert tracks, yet your expectation is that once worked in any digital mode a goal is satisfied.



--
73
Bill
G4WJS.


locked Re: Rebuild Alert Database

Steve Roth - AD4K
 

So, the "aromatic system" should gather information from my connected logging system (HRD Logbook) and QSO's in session.  There is no "manually worked before tables", I only doing the manual corrections because they are missing when doing the JTALERT "Rebuild Alert Database".  Perhaps I am missing your point.

Steve AD4K


locked Re: Rebuild Alert Database

g4wjs
 

On 26/08/2021 13:42, Steve Roth - AD4K wrote:
My system consists of the following:  WIN 10 PC with current updates, WSJT-X latest version (V250.0-rc1), JTALERT V2.50.5 and HRD Logbook latest version.  I have been using this system for the last year.  I had been NOT having JTALERT directly log to my HRD Logbook, but WSJT-X was doing the logging.  It took me a long time to get the settings correct for JTALERT to automatically log to HRD Logbook and to have all  the JTALERT functions like "Show QSO History Popup" working.

<snip>

After I got confirmation that everything was functioning, I did a complete rebuild of the B4 database by using the JTALERT "Rebuild Alert Database" function.  When it was done, my "wanted data" did not match my LOTW worked data, i.e. my states worked were mostly "not worked", and my DXCC worked data was partially done, with some errors.  I can use my LOTW data to manually update the wanted data. i.e., wanted states, wanted DXCC by band, etc.

My question is -- how does the Rebuild Alert Database do its job?  When I do the rebuild, I can see it scanning all sorts of things.  Does it scan my HRD Logbook?  If so, it seems to be missing things.

The other thing I found is that my JTALERT B4 Annotations on some stations is absent even though I have worked them and put them in my HRD Logbook.

Can anyone comment on these issues?

Thanks, Steve   AD4K

Steve,

you are confusing the manually maintained worked before tables in JTAlert with the automatic system that gathers information from you connected logging program and QSOs in session. The two systems are separate and mutually exclusive. If you want to check who you have worked before when you are using the automatic system, then look in your logbook!


--
73
Bill
G4WJS.


locked Rebuild Alert Database

Steve Roth - AD4K
 

My system consists of the following:  WIN 10 PC with current updates, WSJT-X latest version (V250.0-rc1), JTALERT V2.50.5 and HRD Logbook latest version.  I have been using this system for the last year.  I had been NOT having JTALERT directly log to my HRD Logbook, but WSJT-X was doing the logging.  It took me a long time to get the settings correct for JTALERT to automatically log to HRD Logbook and to have all  the JTALERT functions like "Show QSO History Popup" working. Here is the dump  

After I got confirmation that everything was functioning, I did a complete rebuild of the B4 database by using the JTALERT "Rebuild Alert Database" function.  When it was done, my "wanted data" did not match my LOTW worked data, i.e. my states worked were mostly "not worked", and my DXCC worked data was partially done, with some errors.  I can use my LOTW data to manually update the wanted data. i.e., wanted states, wanted DXCC by band, etc.

My question is -- how does the Rebuild Alert Database do its job?  When I do the rebuild, I can see it scanning all sorts of things.  Does it scan my HRD Logbook?  If so, it seems to be missing things.

The other thing I found is that my JTALERT B4 Annotations on some stations is absent even though I have worked them and put them in my HRD Logbook.

Can anyone comment on these issues?

Thanks, Steve   AD4K


locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

Michael Black
 

Lemme know when you want to get together.




On Wednesday, August 25, 2021, 01:27:44 AM CDT, Dan Bathker <d.bathker@...> wrote:



OK Mike W9MDB
Big Thanks in advance

But I need another day or three or four to get organized.

In the past I was pleased enough with Logging as done by WSJT-X.
Operating my little station here with compromised dipole antenna I managed DXCC (20m) and WAS (20 and 40m) on FT8 during last 2 years despite low sunspot numbers.
I felt there was no need for anything fancier. I like "lean and mean".

Then my first mistake was getting greedy for DXCC also on 40m thinking I "needed" JTAlert.

So many recent sw changes here are now even more confusing/complicated by my recent adding
DXKeeper aboard on advice of Laurie to get that logging program.

But DXKeeper also refuses to work.
 

Mike
I can do screen-captures of anything you ask to see and navigate to anything you want to see on the HD here and quick email to you.
Big Thanks again in advance
I will call you in a couple days or so

Dan K6BLG
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

On 8/24/2021 8:34 PM, Michael Black via groups.io wrote:
Hi Dan,
Will you be around tomorrow we could hook up and see about getting you running?

I'm normally around after 0800 Central time.
I help a lot of people.

Call me 217-960-0233

Mike W9MDB





On Tuesday, August 24, 2021, 08:03:23 PM CDT, Dan Bathker <d.bathker@...> wrote:



I too am unable get any issue of JTAlert to work with any version of WSJT-X including latest ver. 2.50.1.

Net Framework is installed on Win10 12 GB machine here and after still another fresh reinstall of both WSJT-X and JTAlert the confirmation popup
continues to indicate it remains "aboard and well".

I have read, reread and reread again everything I can get my eyes on including the Incredible amount traffic generated by this group addressing endless problems.
 
I have also tried to understand directions given on this group as written by Laurie such as the need to "populate" a log.
But there is no such direction dealing with "populate" a log in any user instructions I can find for JTAlert, only mention of "populate" I have seen was on this group by Laurie.

I am close to throwing in the towel.
6 months effort struggling with fussy software still not operating is too much to ask of anyone, even an 83 year old ham licensed for 68 years.

And yes I well realize Laurie is considered by many as a hero.
Unfortunately with my continued negative results with JTAlert Laurie is not yet my hero.

My considered suggestion:
Give Up adding even more 'bells and whistles' to such Already Complicated software and produce a stripped-down "lite" version that hams can actually get running.

respectfully
K6BLG
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------    


On 8/24/2021 5:08 PM, HamApps Support (VK3AMA) wrote:
On 25/08/2021 9:17 am, jrpascucci via groups.io wrote:
Hi, 

I sympathize with the person in another thread who said, simply, 'nothing works' - I was also having troubles for a couple of days and had never seen it approaching working until I (a software engineer with 30+ years background) dug down a bit deeply and found the problem.

Symptoms: Title bar says ???m where it should read the band, no Help->About box spawns, literally no audio of any kind plays, many of the windows didn't function (a few did, which made it impossible to understand from someone who has never seen it working), but certainly no interactions with wsjt-x worked in any way.

Description: After following the instructions, I already had the latest released .net, tried wsjt-x version 2.2.2, 2.4.0 and 2.5.0 (which is what I'm running now), set the multicast according to the help instructions.
    NB: the .net check tool at the end of install had never run correctly, but kept pointing me to an indistinct location, where I had followed the instructions and was told I already have the .net, but indeed I had the wrong thing (the console version in x86, I believe).

What needed to happen was that it requires the .NET 5.0 Desktop runtime.
       This is located here.

Root cause: When I ran jtalertv2.manager.exe by hand, I got the following error (which was not reported in any other way)
A fatal error occurred. The required library hostfxr.dll could not be found. If this is a self-contained application, that library should exist in [C:\Program Files (x86)\HamApps\JTAlert\pluginsX\win-x64\].If this is a framework-dependent application, install the runtime in the global location [C:\Program Files\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\InstallLocation]."
Hostfxr.dll existed in: C:\Program Files (x86)\dotnet\host\fxr\5.0.9, which is the wrong thing, it needs to exist C:\Program Files\dotnet\host\fxr\5.0.9

Recommended User Experience fix: some method of the UI detecting that jtalertv2.manager.exe is not running when started and indicating that the problem lies there might help normal people diagnose what's going on.

Anyway, I look forward to using your software. 

Thanks, and
73,

JRP
KC1MNC

The several windows not opening and sound test failing is an indication that the JTAlertV2.Manager.exe process, which handles all those, is not running. The cause in 99.99% of cases is an incorrect NET 5 install, specifically not installing the correct "Desktop" Runtime.

The framework check constantly reporting the Desktop Runtime not being installed was behaving correctly, it was doing its job.

This pinned FAQ message https://hamapps.groups.io/g/Support/message/35794 has instructions for installing the correct runtime along with the latest MS down load links.

Sorry, not much more I can do if the non-desktop version of the runtime is incorrectly installed despite the numerous postings to this group and having the framework check report a missing runtime.

de Laurie VK3AMA


--
Dan Bathker
PO Box 23
La Canada CA 91012

d.bathker@...

Virus-free. www.avast.com

-- 
Dan Bathker
PO Box 23
La Canada CA 91012

d.bathker@...


locked Re: Prob Decode Windows

Johan Barre <johan.barre@...>
 

hi laurie  txs for last info test with.net but still the probleme 
i have reinstall computer with win10 and now 7 family and now working 
have just a bug (or bad parameter) when i past tx , decode part stopruning  uniil restart jtalert any idea ?

regards and txs again for your geat help 

F4HHL Johan 

Le mer. 25 août 2021 à 00:17, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> a écrit :
On 23/08/2021 1:02 am, Johan Barre wrote:
@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 

Check that you have a version of the .NET 4.7.2 (or 4.8) Framework installed. It should be as it is standard for current and updated versions of Windows, but it is possible it is not. The Decodes window requires the NET Framework 4.7.2 or 4.8

de Laurie VK3AMA

3161 - 3180 of 39870