locked Re: Matching Callsign


Steve, N3SL
 

Can you forget the wildcard stuff and enter the "exact callsign" (and you can do multiple) in the "Wanted callsign" window (settings, Alerts)?  


On Sat, May 2, 2020 at 8:44 AM Dave Cole <dave@...> 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@...> 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.