Re: [wsjt-devel] Message Type 2 Output.

[Rick E. <rel...@tw...>]

Ok That makes sense then.. I passed this on to the user..

73 Rick N2AMG

On 2/27/2025 1:57 PM, Joseph Taylor via wsjt-devel wrote:
> Hi Rick,
>
> Why should you be surprised? The calls you list do not have the format 
> specified in the WSJT-X User Guide for a standard callsign.
> https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0.html#PROTOCOLS
>
> "A standard amateur callsign consists of a one- or two-character 
> prefix, at least one of which must be a letter, followed by a digit 
> and a suffix of one to three letters."
>
>       -- 73, Joe, K1JT
>
> ------------------------------------------------------------------------
> *From:* Rick Ellison via wsjt-devel <wsj...@li...>
> *Sent:* Thursday, February 27, 2025 12:25 PM
> *To:* wsj...@li... <wsj...@li...>
> *Cc:* Rick Ellison <rel...@tw...>
> *Subject:* [wsjt-devel] Message Type 2 Output.
>
>
>   A user of N1MM brought something to my attention and after confirming
>   it today I see the same thing as he does.
>
>   None of the following calls AN45AL, AN45CA, AN45CO, AN45GR, AN45HU,
>   AN45JA, AN45MA, AN45SE
>
>   are sent out via a message type 2. I have trapped all of the calls
>   coming out of that message but when one of those calls are encountered
>   in the WSJTX Band activity window that call is not sent out.
>
>
>   73 Rick N2AMG
>
> --
> This email has been checked for viruses by Avast antivirus software.
> www.avast.com <http://www.avast.com>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel