Date   

locked Re: JT Alert still shows worked B$ stations

Tim Davis KJ4DHF
 

Laurie,
Ok I give that a try and see how it goes.
All I want it to do is like in previous versions. It was a great little program when you first started with JT Alert. It has come a long ways over the years.

I had it set so that all Worked B4 stations were blacked out per mode. If I worked the station on FT4,FT8,JT9,JT65 they were always blacked out
per the mode I was using at the time. ( I did not need a duplicate qso) If I had not worked them they would be displayed in the JT Alert window for that particular mode.


locked Re: JT Alert still shows worked B$ stations

Laurie, VK3AMA
 



On 11/03/2021 8:32 am, Laurie, VK3AMA wrote:

On 11/03/2021 8:07 am, Tim Davis KJ4DHF via groups.io wrote:
That did not fix the problem. It looks as if something not reading the logbook after I switch modes. Started great FT8 switched to FT4 still blanking out all the Worked B4 stations. Switched back to FT8 displaying all calls including the Worked B4.

Its rather confusing what your describing from your messages.

Do you want B4 callsigns displayed, yes or no?
  • if yes then don't use the hide B4 filter
  • if no, then use the hide B4 filter.

What are you expecting to see when you change modes from FT8 to FT4 with respect to B4 display. Are you expecting previously worked FT8 callsigns (but not in FT4) to show as a B4, yes or no?
  • If yes then you need to tick the Ignore Mode checkbox under the Worked B4 settings.
  • If no, that is you want to consider Ft4 as separate from FT8 with respect to B4 status, then leave the "Ignore Mode" checkbox unticked.

de Laurie VK3AMA



I neglected to mention, B4 checking is done against your log, one time only for the current JTAlert session with the results stored in a fast memory-based cache. Reading the B4 status from a log is orders-of-magnitude slower than from memory, thus the use of a cache. If you are changing the basis of the B4 checks, like "Ignore Mode" or "Ignore Band" or "Ignore Grid" than the cached status will be wrong, you will need to restart JTAlert. Note: there is NO need to restart JTAlert when you change Mode or Band, it is only needed if you change the criteria for B4 checking that a restart is needed.

de Laurie VK3AMA



locked Re: JT Alert still shows worked B$ stations

Laurie, VK3AMA
 


On 11/03/2021 8:07 am, Tim Davis KJ4DHF via groups.io wrote:
That did not fix the problem. It looks as if something not reading the logbook after I switch modes. Started great FT8 switched to FT4 still blanking out all the Worked B4 stations. Switched back to FT8 displaying all calls including the Worked B4.

Its rather confusing what your describing from your messages.

Do you want B4 callsigns displayed, yes or no?
  • if yes then don't use the hide B4 filter
  • if no, then use the hide B4 filter.

What are you expecting to see when you change modes from FT8 to FT4 with respect to B4 display. Are you expecting previously worked FT8 callsigns (but not in FT4) to show as a B4, yes or no?
  • If yes then you need to tick the Ignore Mode checkbox under the Worked B4 settings.
  • If no, that is you want to consider Ft4 as separate from FT8 with respect to B4 status, then leave the "Ignore Mode" checkbox unticked.

de Laurie VK3AMA




locked Re: JT Alert still shows worked B$ stations

Laurie, VK3AMA
 

On 11/03/2021 8:16 am, Herschel Hall wrote:
Have you ran the rebuild alert database feature ?
WA9KIA
That wont help. The Alert database rebuild does not affect B4 reporting. B4s reporting comes directly from log lockups.

de Laurie VK3AMA


locked Re: DX SPOT BEACON REMOVAL

HamApps Support (VK3AMA)
 

On 11/03/2021 8:09 am, Anthony W. DePrato wrote:
Can anyone tell me why the below is showing up on the dx cluster also i would like to know how to stop this..

YES I am running the latest versions of WSJT and JTALERT.and DXLAB

YES I have all psk beacons and any think i could find that said anything about reverse beacons and broadcasting turned off.

also i never was on 14.080 so why does this false spot show upEmacs!

Thanks for any help
73 Tony WA4JQS

What application is that image taken from?
Please repost the image showing the column headers?

de Laurie VK3AMA


locked Re: JT Alert still shows worked B$ stations

Herschel Hall
 

Have you ran the rebuild alert database feature ?
WA9KIA 

On Wed, Mar 10, 2021 at 3:07 PM Tim Davis KJ4DHF via groups.io <kj4dhf=yahoo.com@groups.io> wrote:
That did not fix the problem. It looks as if something not reading the logbook after I switch modes. Started great FT8 switched to FT4 still blanking out all the Worked B4 stations. Switched back to FT8 displaying all calls including the Worked B4.


locked DX SPOT BEACON REMOVAL

Anthony W. DePrato
 

Can anyone tell me why the below is showing up on the dx cluster also i would like to know how to stop this..

YES I am running the latest versions of WSJT and JTALERT.and DXLAB

YES I have all psk beacons and any think i could find that said anything about reverse beacons and broadcasting turned off.

also i never was on 14.080 so why does this false spot show upEmacs!

Thanks for any help
73 Tony WA4JQS


locked Re: JT Alert still shows worked B$ stations

Tim Davis KJ4DHF
 

That did not fix the problem. It looks as if something not reading the logbook after I switch modes. Started great FT8 switched to FT4 still blanking out all the Worked B4 stations. Switched back to FT8 displaying all calls including the Worked B4.


locked Re: JT Alert still shows worked B$ stations

Tim Davis KJ4DHF
 

Sorry I must have grabbed wrong pic. As i know i deleted all the white space.

I think I found my problem.

If I put check mark by Do not show worked before call signs be it in FT4 or FT8 it shows the Worked B4 stations, If I remove the check mark

it blacks out the Worked before station in my Alert window.

No check mark =


Which is what I was looking for.


locked Re: JT Alert still shows worked B$ stations

HamApps Support (VK3AMA)
 

On 11/03/2021 7:00 am, Tim Davis KJ4DHF via groups.io wrote:
Hello,

I been running Jt Alert for ages using the black out feature for Worked before stations. Updated to 2.16.14 then 2.16.17 and when I switched from FT8 to FT4 it shows all call signs even Worked B4.

What have I missed or done wrong.

Your posted image was too large resulting in it being scaled down (by the group settings) making it near impossible to decipher. You should have cropped out all the excess white space or alternatively (and preferred) posted separate images.

The problem as I understand it is that previously worked B4 Callsigns on FT8 are not being shown as B4 when you switched mode to FT4. Is that correct? If so, that is the correct behavior. The Worked B4, by default, considers Mode when checking the status. If you don't want mode specific B4 checking, tick the "Ignore Mode" checkbox.

de Laurie VK3AMA




locked JT Alert still shows worked B$ stations

Tim Davis KJ4DHF
 

Hello,

I been running Jt Alert for ages using the black out feature for Worked before stations. Updated to 2.16.14 then 2.16.17 and when I switched from FT8 to FT4 it shows all call signs even Worked B4.

What have I missed or done wrong.


locked Error updating Jtalert

FastWeb
 

Hallo,

I'm Ivan (I4JBJ)

 

I have been using version 2.16.6 of jtalert for a long time.

Upgrading to version 2.16. 17 I receive a UDP communication error without having changed any parameters.

The jtalert window is visible but obviously without showing any stations.

By reinstalling the xxxx version everything returns to normal and the stations reappear.

I repeated this operation several times and got the same behavior.

Attached is a file with the printing of some windows.

I have no idea what kind of mistake.

I Need help

 

thank you

Ivan

 

 

Ivan Beltrami

Via Bellinzona 20

41124 Modena

 

Cell. 3489030747

ibeltrami@...

 

 


locked Re: How JTAlert communicates with WSJT-Xand logger such as HRD

g4wjs
 

On 10/03/2021 16:50, KT7AZ wrote:

I have found bits and pieces of how JTAlert connects to WSJT-X and with logging programs such as HRD.  It would really help if there was a flow chart or diagram as to what happens under the hood.  Such as how data is transferred between the programs, etc.

Thanks

Gary
--
KT7AZ
Hi Gary,

I can speak about how JTAlert and WSJT-X exchange information.

WSJT-X instances are configured to send information packets (UDP datagrams) to a specified server application (an IP address or host name along with a service port number), that server listens on the host and service port and can be JTAlert. The data packets include each decode as it happens, changes in key status values like mode, and other dynamic status information like frequency etc.. The server may also reply to these messages with other messages that can "drive" WSJT-X in a few specific ways, like initiating a QSO with a station previously decode calling CQ. The protocol optionally allows for multiple servers to interoperate with WSJT-X instances sharing the same server service port number by using a technique called multicast group addressing.

I am not an expert on how JTAlert interoperates with HRD, but I believe the HRD logbook is a TCP/IP server that other applications, like JTAlert, can feed logged QSO information. I also believe HRD does not provide a logbook lookup facility via that channel, so JTAlert may also open the HRD logbook database directly for read-only access to query worked before status etc..

Rather confusingly HRD is also able to take network traffic sent from WSJT-X, although that feed was never intended for that purpose. That feed has only the basic ADIF information of logged QSOs accepted in WSJT-X. This channel is via UDP sent to a different host and service port pair specified in WSJT-X, currently named as the "Secondary UDP Server (deprecated)" in "Settings->Reporting", deprecated because the N1MM Logger+ application, for which it was originally intended, now use the preferred UDP feed I mention above.



--
73
Bill
G4WJS.


locked How JTAlert communicates with WSJT-Xand logger such as HRD

KT7AZ
 

I have found bits and pieces of how JTAlert connects to WSJT-X and with logging programs such as HRD.  It would really help if there was a flow chart or diagram as to what happens under the hood.  Such as how data is transferred between the programs, etc.

Thanks

Gary
--
KT7AZ


locked Re: Weird sound problem - Win10, WSJT-X

Larry Banks
 

Hi Pete,
 
Perhaps you need to ask the WSJT-X folk.  This is the JTAlert forum.

73 -- Larry -- W1DYJ

 

Sent: Tuesday, March 09, 2021 14:05
Subject: [HamApps] Weird sound problem - Win10, WSJT-X
 
Setup is Win 10 Pro, WSJT-X v2.3, Icom 7610.  Audio via USB1 on radio.  Was working ok but transmit audio stopped.  The really odd thing is that WSJT 'Tune' worked ok, actual transmit sent no audio.

System restore solved it - had to reinstall WSJTX update.  Quick audio settings reset and everything worked again.
Any ideas on what happened? And how to stop it happening again?

I hate Win 10.

73 de M0PTB
PeteS


locked Weird sound problem - Win10, WSJT-X

Pete Singleton
 

Setup is Win 10 Pro, WSJT-X v2.3, Icom 7610.  Audio via USB1 on radio.  Was working ok but transmit audio stopped.  The really odd thing is that WSJT 'Tune' worked ok, actual transmit sent no audio.

System restore solved it - had to reinstall WSJTX update.  Quick audio settings reset and everything worked again.
Any ideas on what happened? And how to stop it happening again?

I hate Win 10.

73 de M0PTB
PeteS


locked callsign data base problem

Steve
 

I can not install the latest callsidn database as it says Imcan not run it. All the virus programs stop me from running it.


locked Re: Highlighting wanted dxcc in decodes (not only cq)?

Wyndell - K5WJF
 

I run rebuild after about 50 contacts in FT8.  Works great and keeps me from doing a lot of duplicates.  And using a black border for CQs helps them stand out better.  YMMV

 

73 de Wyndell K5WJF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Daniel
Sent: Tuesday, March 9, 2021 07:44
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Highlighting wanted dxcc in decodes (not only cq)?

 

Nobody out there with a solution?
"Rebuild Alert Database" didn't help.
JTAlert doesn't read its ADIF file on start-up.
I can only have all or no DXCC in the "wanted" window.

Cheers
Daniel




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: Just want to say Thank You!

Marion D. Kitchens
 


Many, many thanks to Laurie for your great program.
 
de K4GOK, Marion  Ole man Marion, that is :-)
 
On Tue, 9 Mar 2021 07:33:55 -0500 "Fred Roberts" <fred5352@...> writes:

Hey Laurie.....if you are a he and not a she.....ooopppsss.....sorry.....but still....THANK YOU for a great program and support!
Fred
WB4QOC



Sent from my phone.....Fred

On Mon, Mar 8, 2021, 10:28 PM Chuck Adams <cfadams@...> wrote:

Fred

WB4QOC

 

For the record, Laurie is a unisex given name.

 

Among males, it can be a short form (hypocorism, or pet name) of Lawrence or Laurence (prevalent in England and Australia).

 

I do believe VK3AMA  -- LAURIE COWCHER  is a dude.

 

Regardless, I’d still kiss him for all he has done for ham radio!

 

NTTAWWT.

 

As the Aussies say “Good on ya mate!”

 

73,

 

Chuck (Charles)

KV4VT

 

https://en.wikipedia.org/wiki/Laurie_(given_name)

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Marion D. Kitchens
Sent: 8 March, 2021 8:47 PM
To: Support@HamApps.groups.io
Cc: Support@hamapps.groups.io
Subject: Re: [HamApps] Just want to say Thank You!

 

What Fred said :-)

 

K4GOK

 

On Mon, 8 Mar 2021 20:38:02 -0500 "Fred Roberts" <fred5352@...> writes:

Laurie,

       I just wanted to say thank you for the outstanding JTalert program that makes operating ft8/ft4 a pleasure rather than a job. Having to scroll back thru all of the decodes was next to impossible (I know, I tried). And the lists - the B4 list, keeping track of Countries, States, Provinces, etc. is nothing short of 5 star brilliance. Lest we forget, the incredible support that she provides to the program thru this group! 

Thank you Laurie!

Fred

WB4QOC

 

 

Sent from my phone.....Fred

 

On Mon, Mar 8, 2021, 7:07 PM Joe <wq6q@...> wrote:

As expected, no fault found with JTAlert!  I did not know that you had to restart JTAlert after changing the B4 date setting!  Mystery solved!!

Thank you, Laurie!

 

 


locked Re: Just want to say Thank You!

Marion D. Kitchens
 


Many, many thanks to Laurie for your great program.
 
de K4GOK, Marion  Ole man Marion, that is :-)
 
On Tue, 9 Mar 2021 07:33:55 -0500 "Fred Roberts" <fred5352@...> writes:

Hey Laurie.....if you are a he and not a she.....ooopppsss.....sorry.....but still....THANK YOU for a great program and support!
Fred
WB4QOC



Sent from my phone.....Fred

On Mon, Mar 8, 2021, 10:28 PM Chuck Adams <cfadams@...> wrote:

Fred

WB4QOC

 

For the record, Laurie is a unisex given name.

 

Among males, it can be a short form (hypocorism, or pet name) of Lawrence or Laurence (prevalent in England and Australia).

 

I do believe VK3AMA  -- LAURIE COWCHER  is a dude.

 

Regardless, I’d still kiss him for all he has done for ham radio!

 

NTTAWWT.

 

As the Aussies say “Good on ya mate!”

 

73,

 

Chuck (Charles)

KV4VT

 

https://en.wikipedia.org/wiki/Laurie_(given_name)

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Marion D. Kitchens
Sent: 8 March, 2021 8:47 PM
To: Support@HamApps.groups.io
Cc: Support@hamapps.groups.io
Subject: Re: [HamApps] Just want to say Thank You!

 

What Fred said :-)

 

K4GOK

 

On Mon, 8 Mar 2021 20:38:02 -0500 "Fred Roberts" <fred5352@...> writes:

Laurie,

       I just wanted to say thank you for the outstanding JTalert program that makes operating ft8/ft4 a pleasure rather than a job. Having to scroll back thru all of the decodes was next to impossible (I know, I tried). And the lists - the B4 list, keeping track of Countries, States, Provinces, etc. is nothing short of 5 star brilliance. Lest we forget, the incredible support that she provides to the program thru this group! 

Thank you Laurie!

Fred

WB4QOC

 

 

Sent from my phone.....Fred

 

On Mon, Mar 8, 2021, 7:07 PM Joe <wq6q@...> wrote:

As expected, no fault found with JTAlert!  I did not know that you had to restart JTAlert after changing the B4 date setting!  Mystery solved!!

Thank you, Laurie!

 

 

3041 - 3060 of 36387