Date   

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 



locked Re: JTALERT B4 and Wanted call

Jim N6VH
 

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


locked Logger32 +JTAlert+IC-7300

Gerard Arsenault
 

I recently set up logger32 on a new IC-7300 transceiver and have rig control and decoding working well on JTDX and WSJT-X. However, when I launch logger32, JTAlert stops decoding. Please note that the IC-7300 port is CLOSED when this issue is happening. Has anyone had this issue and found a solution?


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Here are my setup pages.  This works for me.

JTALERT HRD LOG Jul 21.jpg
JTALERT LOGGING.jpg
JTALERT WORKED B4.jpg
WSJT-X Reporting.jpg


On Sat, Aug 21, 2021 at 12:08 PM f8nhf <f8nhf@...> wrote:
Good evening Steve
can you tell me the method you use
I have HRD de luxe as my log
73 Denis F8NHF


locked Re: JTALERT "B4"

f8nhf
 

Good evening Steve
can you tell me the method you use
I have HRD de luxe as my log
73 Denis F8NHF


locked Re: JTALERT B4 and Wanted call

Bob Frostholm
 

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
KO6LU


locked Re: JTALERT "B4"

Bob Frostholm
 

test

73

Bob

Ko6Lu




--
Bob
KO6LU


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Thanks much for solving my mystery.  Sorry I missed your previous post - I tend to not do much FT4 and I never had the occasion to experience the problem. The situation with V31MA constantly calling gave me the opportunity to illustrate the issue.

I will go back to the way I was doing it (just using HRD to log for me).

Regards, Steve  AD4K


On Sat, Aug 21, 2021 at 10:30 AM DAVID MM0AMW via groups.io <david.gillies116=btinternet.com@groups.io> wrote:
I already raised this issue in message #36167 in mid July. It only seems to happen on FT4 as everything works as expected on FT8.  It also happens if you switch bands and back again whilst on FT4.

73
David 
MM0AMW


locked Re: JTALERT "B4"

DAVID MM0AMW
 

I already raised this issue in message #36167 in mid July. It only seems to happen on FT4 as everything works as expected on FT8.  It also happens if you switch bands and back again whilst on FT4.

73
David 
MM0AMW


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Okay Thanks, I will give that a try.  Steve - AD4K

On Sat, Aug 21, 2021 at 9:20 AM g4wjs <bill.8@...> wrote:
On 21/08/2021 14:17, Steve Roth - AD4K wrote:
> I recently upgraded to JTALERT Version 2.50.5 which has the new
> "Miscellaneous Alerts" "B4" history selection.  I did not change my B4
> settings to anything but continuous (no timeout).  It might be
> coincidental but since then some of my "B4" annotations to previously
> contacted stations are being dropped.  For example, this morning I
> contacted V31MA on 20M FT4.  V31MA was already in my logbook from a
> 20M contact in the past, both FT4 and FT8. There was no "B4"
> annotation on his callsign block and his block was "CQ Green".  After
> the contact I got a "B4" annotation on his callsign block and it
> turned red.  I went to 20M FT8 and came back to 20M FT4.  V31MA was
> still there but his callsign block did not have "B4" in it and it was
> "CQ Green".  So, I called V31MA and got another "B4" annotation and it
> changed color to red.  I then went to 20M FT8 for a minute, then back
> to 20M FT4 and V31MA was still there but the "B4" annotation was gone
> and it was "CQ Green" again.
>
> 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.
>
>
> Thanks, Steve    AD4K

Steve,

JTAlert loads worked before data form your logging program at startup
and updates it as you log stations, if you don't have JTAlert doing the
logging into your logging program then it will not update its database
of stations worked since it was last started. In other words your
configuration to log directly from WSJT-X to the HRD logbook is invalid.



--
73
Bill
G4WJS.






locked Re: JTALERT "B4"

g4wjs
 

On 21/08/2021 14:17, Steve Roth - AD4K wrote:
I recently upgraded to JTALERT Version 2.50.5 which has the new "Miscellaneous Alerts" "B4" history selection.  I did not change my B4 settings to anything but continuous (no timeout).  It might be coincidental but since then some of my "B4" annotations to previously contacted stations are being dropped.  For example, this morning I contacted V31MA on 20M FT4.  V31MA was already in my logbook from a 20M contact in the past, both FT4 and FT8. There was no "B4" annotation on his callsign block and his block was "CQ Green".  After the contact I got a "B4" annotation on his callsign block and it turned red.  I went to 20M FT8 and came back to 20M FT4.  V31MA was still there but his callsign block did not have "B4" in it and it was "CQ Green".  So, I called V31MA and got another "B4" annotation and it changed color to red.  I then went to 20M FT8 for a minute, then back to 20M FT4 and V31MA was still there but the "B4" annotation was gone and it was "CQ Green" again.

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.


Thanks, Steve    AD4K
Steve,

JTAlert loads worked before data form your logging program at startup and updates it as you log stations, if you don't have JTAlert doing the logging into your logging program then it will not update its database of stations worked since it was last started. In other words your configuration to log directly from WSJT-X to the HRD logbook is invalid.



--
73
Bill
G4WJS.


locked JTALERT "B4"

Steve Roth - AD4K
 

I recently upgraded to JTALERT Version 2.50.5 which has the new "Miscellaneous Alerts" "B4" history selection.  I did not change my B4 settings to anything but continuous (no timeout).  It might be coincidental but since then some of my "B4" annotations to previously contacted stations are being dropped.  For example, this morning I contacted V31MA on 20M FT4.  V31MA was already in my logbook from a 20M contact in the past, both FT4 and FT8.  There was no "B4" annotation on his callsign block and his block was "CQ Green".  After the contact I got a "B4" annotation on his callsign block and it turned red.  I went to 20M FT8 and came back to 20M FT4.  V31MA was still there but his callsign block did not have "B4" in it and it was "CQ Green".  So, I called V31MA and got another "B4" annotation and it changed color to red.  I then went to 20M FT8 for a minute, then back to 20M FT4 and V31MA was still there but the "B4" annotation was gone and it was "CQ Green" again.

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.


Thanks, Steve    AD4K


locked Re: JT Alert and 5X3R

Paul N3PS
 

Jim,

Running WSJTX v 2.4.0 . . .  Not sure where routed, found it to be bizarre as just an issue with one call sign and still existed after app and pc reboots . . 

--
Paul / N3PS


locked Re: JT Alert and 5X3R

Jim Reisert AD1C
 

On Thu, Aug 19, 2021 at 6:25 PM n3ps wrote:

Today, I worked HV0A on F/H without any issues. However, later in the day when attempting to work 5X3R on F/H, I was unable to get transmit to enable by clicking on the call sign in JT Alert nor in the band activity window on WSJTX . . . had to manually key in the call sign in WSJTX to eventually complete a QSO. And yes, I had HOUND enabled.

I subsequently not only relaunched JT Alert / WSJTX, but also restarted my PC . . . still couldn't get things to work for 5X3R, yet no issues with any other call signs . . .

Anyone else have this issue with 5X3R?
Paul, this sounds like a WSJT-X issue. What version are you running?



--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Prob Decode Windows

Johan Barre
 

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 



locked Re: JTAlert 2.50.0 Not Working

Tom Melvin
 

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: JTAlert 2.50.0 Not Working

Harry Hall
 

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

> *To: *Support@HamApps.groups.io <mailto:Support@HamApps.groups.io>

> *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 JT Alert and 5X3R

Paul N3PS
 

Today, I worked HV0A on F/H without any issues.  However, later in the day when attempting to work 5X3R on F/H, I was unable to get transmit to enable by clicking on the call sign in JT Alert nor in the band activity window on WSJTX . . . had to manually key in the call sign in WSJTX to eventually complete a QSO.  And yes, I had HOUND enabled.

I subsequently not only relaunched JT Alert / WSJTX, but also restarted my PC . . . still couldn't get things to work for 5X3R, yet no issues with any other call signs . . .

Anyone else have this issue with 5X3R?
--
Paul / N3PS


locked Re: Visit...

Mike Rhodes
 

Looks like someone's email got hacked.

Mike / W8DN

------------------

On 8/19/2021 12:51 PM, David Tucker wrote:

What do u need?

On 8/19/2021 11:17 AM, Jim Denneny wrote:

Hello,

How are you doing? Can you do me favor.

Thanks

Jim & Nancy


locked Re: Spam from KJ4GK

Carl - WC4H
 
Edited

Thomas.

May I suggest that you just post yourself on a cluster (once, not 100 times).
In the note/info box, post your tx freq & mode.

You can also put a message in the QRZ page of the callsign you are operating and give the op frequencies.

Word will get around.

73.
Carl - WC4H

1161 - 1180 of 37816