locked Re: Matching Callsign


Michael Black
 

What version of JTAlert and WSJT-X are you running?

The latest are 2.16.4 and 2.1.2

de Mike W9MDB




On Saturday, May 2, 2020, 08:29:11 AM CDT, Dave Cole <dave@...> wrote:


No problem, I also tried B8CRA as well...  All visible here, and no
match of any kind, in any way...  Here is an odd one, I also tried
WW0WWV, who was on, and saw him decode, but got no match...  It is as if
all call matching stopped.  I have not seen NK7I on so I can't test that
assumption.

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:14 AM, g4wjs wrote:
> Hi Dave,
>
> RR, OK just mentioned because I see B8CRA active on 15m FT8.
>
> On 02/05/2020 14:13, Dave Cole wrote:
>> Nope, B1CRA, they are special calls out of China for some event.
>>
>> 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:12 AM, g4wjs wrote:
>>> On 02/05/2020 14:10, Dave Cole wrote:
>>>> Hello,
>>>> I have an issue I can't solve...
>>>>
>>>> I have NK7% working in the matching callsign section, and it
>>>> triggers when it hears NK7*, as it should.
>>>>
>>>> I also have B1CRA, as a matching callsign, and it fails to trigger...
>>>>
>>>> Any ideas?
>>>>
>>>> I have tested to be sure I get alerts for other triggers, I do, CQ,
>>>> etc., all work...  Just not B1CRA.  Any clue?
>>>>
>>>> --
>>>> 73, and thanks,
>>>> Dave (NK7Z)
>>>
>>> Hi Dave,
>>>
>>> do you mean BB1CRA
>
>
>
> --
> 73
> Bill
> G4WJS.
>



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