locked Re: Matching Callsign - Solved


Dave (NK7Z)
 

Hi,
Yes sir I do, and thank you for the suggestion! I used to use that a lot, but of late, I have moved my control clicking to WSJT-X for some reason...

I use extensive color codding, and have matched the alert colors within JTAlert, and WSJT-X, so locating a call I need is easy within WSJT-X. Again, thanks for the suggestion.

I will try using WSJT-X covering the UI of JTAlert, and see how that feels for a while. I have not fully defined what, and why, I am using things the way I am as of yet.

I have been working on a desk rebuild, and it is almost done. See:

https://www.nk7z.net/rf-patch-panel/

for photos of the remake. It starts at the top, and works its way down in time as you scroll down. I figure about a week and it will be installed.

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

On 5/2/20 10:42 AM, Michael Black via groups.io wrote:
Dave, you did know you can click on on the call slots to initiate a QSO in JTAlert, right?
You mean you get an alert and then hunt for it in the WJST-X decode window?
de Mike W9MDB
On Saturday, May 2, 2020, 12:39:12 PM CDT, Dave Cole <dave@nk7z.net> wrote:
Thanks Herb,
Your post made me think, what am I using the JTAlert display for, and
the answer is nothing...  I use JTAlert mainly for the audio alerts, so
I will put the display behind a fuller screen of WSJT-X!  THANK YOU!
73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources
On 5/2/20 8:33 AM, WB8ASI Herb wrote:
> Dave,  Just some food for thought.  I'm a big fan of the Decodes
Window.  Much easier and faster for me to scan the data in a vertical column than across the individual Callsign windows.  So Decodes Window is where I operate from, and have the Main UI Callsign Windows shrunk down to just one line of 9.  (Still need to see the Menu bar).  I don't filter anything on the Main Callsign window page, so all callsigns still come thru and Alert as desired.  I do however do my filtering via the Decodes Window and adjust as desired for whatever I'm chasing today. Much more flexible.  You can filter out US stations if you just want DX. I always filter out B4 to keep it cleaner.  You could filter and unfilter LOTW or whatever.  Good luck. 73 Herb WB8ASI
>> On May 2, 2020 at 11:21 AM Dave Cole <dave@nk7z.net
<mailto:dave@nk7z.net>> wrote:
>>
>>
>> Turns out the LoTW filter was killing the alert...  Even though I had
>> call sign selected, and had it at the top of the alert list, I also had
>> do not show unless LoTW set.  That blocked the alert, so the trigger
>> failed...  Thanks!  Having folks test it, and show it was working helped
>> a lot!
>>
>> 73, and thanks,
>> Dave (NK7Z)
>> https://www.nk7z.net
>> ARRL Volunteer Examiner
>> ARRL Technical Specialist
>> ARRL Asst. Director, NW Division, Technical Resources
>>
>> On 5/2/20 7:35 AM, WB8ASI Herb wrote:
>>> tested fine.  put in W% and you'll get plenty of Alerts.
>>>
>>>> On May 2, 2020 at 10:10 AM Dave Cole <dave@nk7z.net
<mailto:dave@nk7z.net>> wrote:
>>>>
>>>>
>>>> Can you retest that please?  The instructions indicate that it is only
>>>> good for a single character.  It multi, then I will start using it
like
>>>> that as well.
>>>>
>>>> 73, and thanks,
>>>> Dave (NK7Z)
>>>> https://www.nk7z.net
>>>> ARRL Volunteer Examiner
>>>> ARRL Technical Specialist
>>>> ARRL Asst. Director, NW Division, Technical Resources
>>>>
>>>> On 5/2/20 6:55 AM, WB8ASI Herb wrote:
>>>>> I've been successful in the past using the wildcard % for
multiple trailing characters ie. VY1% for anyone in Yukon Territory. 73 Herb WB8ASI
>>>>>
>>>>>> On May 2, 2020 at 9:44 AM Dave Cole <dave@nk7z.net
<mailto:dave@nk7z.net>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> That won't work out of the box.  As per the help file, the matching
>>>>>> function only works for a single character, and only a single
matching
>>>>>> character is allowed.
>>>>>>
>>>>>> To see the instructions for matching, use "SEARCH", and look for
"wildcard".
>>>>>>
>>>>>> I am trying to match an exact callsign, I see in the decode
window, and
>>>>>> that is failing...  I am at a loss here...
>>>>>>
>>>>>> 73, and thanks,
>>>>>> Dave (NK7Z)
>>>>>> https://www.nk7z.net
>>>>>> ARRL Volunteer Examiner
>>>>>> ARRL Technical Specialist
>>>>>> ARRL Asst. Director, NW Division, Technical Resources
>>>>>>
>>>>>> On 5/2/20 6:38 AM, Michael Black via groups.io wrote:
>>>>>>> How about B% ?
>>>>>>>
>>>>>>> Does that work?
>>>>>>>
>>>>>>> de Mike W9MDB
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Saturday, May 2, 2020, 08:30:40 AM CDT, Dave Cole
<dave@nk7z.net <mailto:dave@nk7z.net>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>> Thanks for the suggestion, however, that won't work, the
matching only
>>>>>>> works for the last single letter.
>>>>>>>
>>>>>>> 73, and thanks,
>>>>>>> Dave (NK7Z)
>>>>>>> https://www.nk7z.net
>>>>>>> ARRL Volunteer Examiner
>>>>>>> ARRL Technical Specialist
>>>>>>> ARRL Asst. Director, NW Division, Technical Resources
>>>>>>>
>>>>>>> On 5/2/20 6:16 AM, g4wjs wrote:
>>>>>>>    > On 02/05/2020 14:15, Dave Cole wrote:
>>>>>>>    >> I also tried B1CR%, and got no match.  I can clearly see
B1CRA calling
>>>>>>>    >> CQ on 40 as well, while under test.
>>>>>>>    >>
>>>>>>>    >> 73, and thanks,
>>>>>>>    >> Dave (NK7Z)
>>>>>>>    >
>>>>>>>    > Hi Dave,
>>>>>>>    >
>>>>>>>    > not sure why it is not working, but how about B%CRA , that
should cover
>>>>>>>    > all 9 of them.
>>>>>>>    >
>>>>>>>    >
>>>>>>>    >
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>

Join Support@HamApps.groups.io to automatically receive all group messages.