Date   

locked Linux Question

Robert Rampolla
 

I am aware I am not the only one interested in a Linux version. I also did some searches on the topic and I saw a discussion from a while ago. Will JTAlertX work in Linux Mint?

I have found the latest version of both WSJTx and JTDX are taxing my computer to the point I can not turn off enough background programs to make it flow well. I see others are complaining as well.  I am thinking of converting my Asus Vivo Book to a dual boot laptop.


locked Re: Worked B4 sometimes not working

Michael Boudreaux
 

Hi,
Same here intermittently. Show before on wsjt-x but not on JTalert. It's been happening a few versions to me. Great program just ack the issue.  73 vk3xz  Mike


locked JTAlert not passing all WSJT-x v2.2.0rc2 decodes

Ken Bills
 

I have been running v2.2.0rc2 the past two days and noticed tonight especially that JTAlert is not passing most of the DX contacts through for selection. I have to manually pick them from WSJT-x decode window.

Not sure which side has the issue.

73
Ken-W9KB


locked Re: JTAlert Not Showing All Calls

Jim N6VH
 


On 5/26/2020 5:35 PM, HamApps Support (VK3AMA) wrote:
On 26/05/2020 2:19 am, Jim N6VH wrote:
Laurie,

I know this has been reported before, for previous versions of JTAlert. However, I just noticed it with 2.16.6 Release version. Also using the latest beta version of WSJT-X , 2.2.0-rc2. Occasionally, JTAlert will not display all the decoded calls. In the example in the screen captures, both calls were "B4", but only one of them was displayed in JTAlert. Both calls did show in the Decodes Window for that time slot. In another incident, a needed call didn't show in the call grid, but I was still alerted for it. I am reasonably certain my filters aren't involved, since the calls in question do display at other times.

73,

Jim N6VH


This is likely due to the changes I made to accommodate the new early FT8 decoding of WSJT-X introduced with rc1/rc2.

I am surprised there were not similar reports with rc1.

I can see in the code how this could happen and have made some timing adjustments for the next release.

de Laurie VK3AMA

_._,_._,_


Laurie,

Thank you. There might not have been reports, simply because it happened without being noticed. Since it only happens once in a while, it's easy to miss it. The only reason I noticed it is that I got an audio alert, but the call wasn't in the callsign box.

73,

Jim N6VH


locked Re: More than 36 decodes

Dave (NK7Z)
 

Hi John,
I don't use either, only LoTW. I do however always upload to all three as a courtesy to those that do. It takes almost no time for me to upload to the other two...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/27/20 12:05 PM, John L. Broughton wrote:
One consideration.
I started using eQSL, I hadn't been aware of it, when I got an email from a guy who worked me and told me he needed Arizona for an award on eQSL and asked me to join. I did join and then he informed me I had to be an Authenticated User for our QSO to count for an award, so I became one. I'm glad I did.
<soapbox>
Personally, I wish everyone used eQSL, LoTW and QRZ as I really like collecting awards on all three (check out my QRZ page).
My pet peeve is hams that refuse to use LoTW, eQSL or QRZ. I exchanged email with a ham in Europe who brags about all his DXCC awards on his QRZ page, but who refuses to QSL online. One would think he could appreciate what it means to other hams to get a QSL for a needed country, state, etc.
--
John L. Broughton
wb9vgj@arrl.net
2sliverhondas@gmail.com
www.wb9vgj.us
On 5/27/2020 7:07 AM, Jim Nuytens via groups.io wrote:
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.

On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


locked Re: More than 36 decodes

John L. Broughton
 

One consideration.

I started using eQSL, I hadn't been aware of it, when I got an email from a guy who worked me and told me he needed Arizona for an award on eQSL and asked me to join. I did join and then he informed me I had to be an Authenticated User for our QSO to count for an award, so I became one. I'm glad I did.

<soapbox>
Personally, I wish everyone used eQSL, LoTW and QRZ as I really like collecting awards on all three (check out my QRZ page).

My pet peeve is hams that refuse to use LoTW, eQSL or QRZ. I exchanged email with a ham in Europe who brags about all his DXCC awards on his QRZ page, but who refuses to QSL online. One would think he could appreciate what it means to other hams to get a QSL for a needed country, state, etc.

On 5/27/2020 7:07 AM, Jim Nuytens via groups.io wrote:
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.

On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.


Virus-free. www.avg.com


locked Re: More than 36 decodes

Larry Banks
 

Hi Kevin,
 
To be totally honest, I don’t always have the LoTW filter on.   I only need AK for 80M WAS (hard from MA) so when I am on 80 I operate with no filters.  If I picked up AK on 80, any number of “real” snail mail QSL requests would be worth it!

73 -- Larry -- W1DYJ

 

From: Kevin k5vp
Sent: Wednesday, May 27, 2020 11:30
Subject: Re: [HamApps] More than 36 decodes
 
While I understand the thought, I get QSOs from years back from ops who join now & upload their archived logs.  
 
Yes, the LoTW flag would likely come up when these ops start to use LoTW.  But, I figure 'bag 'em' now & confirm via LoTW when they upload their logs.
 
It's not 100% proof, but I'm getting confirmations from 2012, when I got back into the hobby.
 
Kevin k5vp
 
On Wed, May 27, 2020 at 7:59 AM Larry Banks via groups.io <larryb.w1dyj=mailto:verizon.net@groups.io> wrote:
Likewise, I filter out anyone not on LoTW.

73 -- Larry -- W1DYJ

 
 
Sent: Wednesday, May 27, 2020 10:07
Subject: Re: [HamApps] More than 36 decodes
 
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.
 
On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.

 
 
--
73,
 
Kevin Potter
k5vp


locked Re: More than 36 decodes

Kevin k5vp
 

While I understand the thought, I get QSOs from years back from ops who join now & upload their archived logs.  

Yes, the LoTW flag would likely come up when these ops start to use LoTW.  But, I figure 'bag 'em' now & confirm via LoTW when they upload their logs.

It's not 100% proof, but I'm getting confirmations from 2012, when I got back into the hobby.

Kevin k5vp

On Wed, May 27, 2020 at 7:59 AM Larry Banks via groups.io <larryb.w1dyj=verizon.net@groups.io> wrote:
Likewise, I filter out anyone not on LoTW.

73 -- Larry -- W1DYJ

 
 
Sent: Wednesday, May 27, 2020 10:07
Subject: Re: [HamApps] More than 36 decodes
 
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.
 
On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.



--
73,

Kevin Potter 
k5vp


locked Re: More than 36 decodes

Larry Banks
 

Likewise, I filter out anyone not on LoTW.

73 -- Larry -- W1DYJ

 
 

Sent: Wednesday, May 27, 2020 10:07
Subject: Re: [HamApps] More than 36 decodes
 
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.
 
On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.


locked Re: More than 36 decodes

Bill Barrett
 

I would prefer there was a  filter for "USA only" rather than "NA".
That would be useful for 6M activity since Canada and the Caribbean are DX on 6M for me. 
Thanks;
Bill W2PKY

On Wed, May 27, 2020 at 10:07 AM Jim Nuytens via groups.io <jim.kj3n=verizon.net@groups.io> wrote:
I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.

On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.



--
Bill Barrett
352-437-4758


locked Re: More than 36 decodes

Jim Nuytens
 

I agree. For example, I filter out anyone who is not on eQSL. Makes life a lot easier.

On 5/27/2020 00:47, HamApps Support (VK3AMA) wrote:

IMHO, 36 displayed Callsigns is too many. It is a chaotic mess of multiple colored callsigns. A better option is to filter out most of the unwanted Callsigns. Use the Alert Filters to help reduce the number displayed.


locked Re: More than 36 decodes

Dave (NK7Z)
 

I routinely go days with no alerts! :) It is nice!

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/26/20 6:19 PM, HamApps Support (VK3AMA) wrote:
On 27/05/2020 11:12 am, HamApps Support (VK3AMA) via groups.io wrote:
The beauty with this approach is that a Callsign that is displayed in JTAlert is likely a good candidate for a QSO. But this approach wont appeal to those more interested in racking up a high QSO count, that is qso "quantity" rather than qso "quality".
I neglected to add, a JTAlert window with few or no callsigns displayed due to filtering makes for a more enjoyable (IMO) experience in the shack. It is less stressful time without trying to decide every 15 seconds which Callsign could be a possible QSO candidate. It is a far less chaotic experience.
de Laurie VK3AMA


locked Re: More than 36 decodes

Dave (NK7Z)
 

Hi Laurie,

That is my goal-- I only want to see contacts that are needed for awards, and your filter section is great for that...

I leave the audio turned up on for the alerts, so when I hear one, I can count on it being a station I need...

THANK YOU, I have gotten a number of new countries that way in the past few months!

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/26/20 6:12 PM, HamApps Support (VK3AMA) wrote:
On 27/05/2020 10:54 am, Dave Cole wrote:
I use filters, and routinely see no decodes in the windows provided by JTAlert.  My filter logic is to remove anything I already have. i.e. If I have WAS, then I turn off states, if I have DXCC, then I kill DXCC for what I don't need.

The filters are wonderful in JTAlert...

73, and thanks,
Dave (NK7Z)
The beauty with this approach is that a Callsign that is displayed in JTAlert is likely a good candidate for a QSO. But this approach wont appeal to those more interested in racking up a high QSO count, that is qso "quantity" rather than qso "quality".
de Laurie VK3AMA


locked Re: Flex 6400 - two receivers - two bands - two jtalerts - wrong alerts #FT8

dimichele@...
 

Hi Laurie,
thanks for the reply. I understand and I'll be waiting for next release. 
A question:  Can I delete any previous choice (I mean: DXCC, WAS States, Zones ....) and restart with a clean alert choice start up?  I'd try to erase any previous setup of the "zones alerts". I have been using this, only for testing if the two instances were working fine. Unfortunately, now,  the zone's alerts are still displayed even if I did unclick the alert option box at the top of the window.
Thanks !  73 Take care.
Frank i2dmi 


locked Re: Worked B4 sometimes not working

Paul AC9O
 

Hi Laurie,

Definitely in the log. When I display the pop-up, it shows as worked too. In ACLog, when I start a contact, it lists the prior contacts so I can see it right away. 

Doesn't happen all the time, but seems to be more frequent. Very intermittent. Perhaps it some kind of a timing issue with the multiple decode passes in the new version of WSJT-X?

Thanks for looking.

73
Paul, AC9O


locked Re: Worked B4 sometimes not working

Stephen Taylor - K6SJT
 

Hi Laurie, sorry about not signing, I thought my name and call would be displayed in the header by groups.io - my bad

As I listed in my original message, the QSO is logged to HRD via JTAlert and JTAlert does confirm with "SUCCESS: QSO Logged" to HRD 

The windows then clears and can show several additional cycles, yet the WSO station still does not show as worked before in JTAlert -

PS - I run FT4 predominantly

Stephen Taylor - K6SJT


locked Re: Appending state to callsigns

HamApps Support (VK3AMA)
 

On 23/05/2020 4:13 am, Ed Deichler wrote:
I just re-launched JTAlert-X (V2.15.2) and do not see the state appended to callsigns in the billboard.  How to I add the states?

73 de Ed

States are appended if known and that depends on the Callsigns database being installed. A lightweight version of the database is automatically included with each JTAlert release, but could have been removed depending on what uninstall operations are performed within Windows Control Panel. Just reinstall JTAlert should fix that.

Also, the display of the 2 character State code is controlled by the "Do not show State code..." setting under the "Alerts -> Wanted US State" section of the Settings window.

de Laurie VK3AMA


locked Re: Updating Wanted Grids

David De Coons
 

Looking at the colors in WSJT-X it matches wanted grid. We have tried to reset the color alerts to default and uncheck grids, then restart both WSJT-X and JTALERT. 

I will have him test the wanted state filter. That is usually yellow, not orange. But we will check that anyway just in case. 

As I stated his issue is we imported his log from DX4WIN to HRD Logbook but nothing in the DX4WIN log had grid info. I am trying to get him into the 21st century and start using QRZ XML lookup. 

73
Dave wo2x


Sent from my waxed string and tin cans. 

On May 26, 2020, at 9:15 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/05/2020 11:02 am, David De Coons wrote:

We turned off the color notification for wanted grids and the black on yellow ?or brown, depending on PC monitor) still show up as wanted grids. He would prefer on HF bands to not receive notifications of new grids. He was using DX4WIN and that program was not configured for XML lookups so all his entries except 6 meters do not have grid information. 

I hope this better explains he would prefer to turn off notifications of new grids. 

73
Dave wo2x

Are you sure the black on yellow is a Grid alert and not some other alert type being generated? How are you determining it is a grid alert?
What does the "Alert Types Summary Windows" show you regarding the Alert colors, is Black on Yellow a Grid Alert or is it the default Wanted State Alert?

de Laurie VK3AMA


locked Re: More than 36 decodes

HamApps Support (VK3AMA)
 

On 27/05/2020 11:12 am, HamApps Support (VK3AMA) via groups.io wrote:
The beauty with this approach is that a Callsign that is displayed in JTAlert is likely a good candidate for a QSO. But this approach wont appeal to those more interested in racking up a high QSO count, that is qso "quantity" rather than qso "quality".

I neglected to add, a JTAlert window with few or no callsigns displayed due to filtering makes for a more enjoyable (IMO) experience in the shack. It is less stressful time without trying to decide every 15 seconds which Callsign could be a possible QSO candidate. It is a far less chaotic experience.

de Laurie VK3AMA


locked Re: Updating Wanted Grids

HamApps Support (VK3AMA)
 

On 27/05/2020 11:02 am, David De Coons wrote:

We turned off the color notification for wanted grids and the black on yellow ?or brown, depending on PC monitor) still show up as wanted grids. He would prefer on HF bands to not receive notifications of new grids. He was using DX4WIN and that program was not configured for XML lookups so all his entries except 6 meters do not have grid information. 

I hope this better explains he would prefer to turn off notifications of new grids. 

73
Dave wo2x

Are you sure the black on yellow is a Grid alert and not some other alert type being generated? How are you determining it is a grid alert?
What does the "Alert Types Summary Windows" show you regarding the Alert colors, is Black on Yellow a Grid Alert or is it the default Wanted State Alert?

de Laurie VK3AMA

6641 - 6660 of 36473