Date
1 - 18 of 18
locked More than 36 decodes
|
Graham Alston
Hi Laurie,
I'm routinely seeing more than 36 decodes (v2.2.0-rc1 now displays the number in the bottom status window). The maximum rows/columns in JTAlert is 4x9=36. Perhaps it's possible to add another row (5x9=45)? 73 Graham VK3GA
|
|
|
|
neil_zampella
Not sure if Laurie can do that in this version series (2.xx), You could check the CQ only box on WSJT-X, and only see those stations calling CQ. You'll still get anyone responding to you.
Neil, KN3ILZ
|
|
|
|
Also, you could use the Decodes Window to see the entire list. 73 Herb WB8ASI
On May 25, 2020 at 9:38 AM neil_zampella <neilz@...> wrote:
|
|
|
|
B. Smith
The WSJT-X Decodes Window is my preference for IDing callers. There are a lot of good features in JTAlert but using the 36 boxes to find targets isn't one of them. The use of the JTAlert color codes seems to interact usefully with the WSJT-X Decodes Window, but I don't understand exactly how that is supposed to work.
|
|
|
|
HamApps Support (VK3AMA)
On 25/05/2020 4:07 pm, Graham Alston
wrote:
I'm routinely seeing more than 36 decodes (v2.2.0-rc1 now displays the number in the bottom status window). The maximum rows/columns in JTAlert is 4x9=36. 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. Increasing the main display past 36 will not be happening with the V2 series of JTAlert, sorry. With JTAlertV3 there is not limit. de Laurie VK3AMA
|
|
|
|
Dave Cole
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.
toggle quoted messageShow quoted text
The filters are wonderful in JTAlert... 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 5:47 PM, HamApps Support (VK3AMA) wrote:
On 25/05/2020 4:07 pm, Graham Alston wrote:I'm routinely seeing more than 36 decodes (v2.2.0-rc1 now displays the number in the bottom status window). The maximum rows/columns in JTAlert is 4x9=36.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.
|
|
|
|
HamApps Support (VK3AMA)
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 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
|
|
|
|
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
|
|
|
|
Dave Cole
Hi Laurie,
toggle quoted messageShow quoted text
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 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".
|
|
|
|
Dave Cole
I routinely go days with no alerts! :) It is nice!
toggle quoted messageShow quoted text
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.
|
|
|
|
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:
|
|
|
|
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
--
Bill Barrett 352-437-4758
|
|
|
|
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:
|
|
|
|
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:
--
73, Kevin Potter k5vp
|
|
|
|
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
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:
73,
Kevin Potter
k5vp
|
|
|
|
John L. Broughton
One consideration.
toggle quoted messageShow quoted text
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:
|
|
|
|
Dave Cole
Hi John,
toggle quoted messageShow quoted text
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.
|
|
|
|
John L. Broughton
Dave,
toggle quoted messageShow quoted text
Thank you for your consideration. I wish more fold did the same. However, without being a Authenticated User on eQSL, QSLs with you cannot be counted by the other station toward awards; it is just personal satisfaction for them working you if you are in one of their needed states. I, too, am an ARRL VE. We had a session a couple of weeks ago that observed social distancing protocols. I did not participate in it, but it went well according to reports. 73, John, WB9VGJ -- John L. Broughton wb9vgj@arrl.net 2sliverhondas@gmail.com www.wb9vgj.us
On 5/27/2020 1:10 PM, Dave Cole wrote:
Hi John,
|
|
|
