ator may
>> not have used HOUND mode at all!
>>
>> 73, Reino OH3mA
>>
>>
>>
>> *From:* WB5JJJ [mailto:wb5...@gmail.com]
>> *Sent:* 16. marraskuuta 2020 0:45
>> *To:* WSJT software development
>> *Subject:* [wsjt-devel] TX Freq lockou
73, Reino OH3mA
*From:*WB5JJJ [mailto:wb5...@gmail.com <mailto:wb5...@gmail.com>]
*Sent:* 16. marraskuuta 2020 0:45
*To:* WSJT software development mailto:wsjt-devel@lists.sourceforge.net>>
*Subject:* [wsjt-devel] TX Freq lockout
With the 7Q7 being the first
gt; Hi George,
>
> There is a minor problem with your lockout proposal as that operator may
> not have used HOUND mode at all!
>
> 73, Reino OH3mA
>
>
>
> *From:* WB5JJJ [mailto:wb5...@gmail.com]
> *Sent:* 16. marraskuuta 2020 0:45
> *To:* WSJT software developm
Hi George,
There is a minor problem with your lockout proposal as that operator may not
have used HOUND mode at all!
73, Reino OH3mA
From: WB5JJJ [mailto:wb5...@gmail.com]
Sent: 16. marraskuuta 2020 0:45
To: WSJT software development
Subject: [wsjt-devel] TX Freq lockout
With the 7Q7
With the 7Q7 being the first major DXP since early in the year, there are a
lot of "new" hams to F/H that don't read the information available. They
are hoping to "cut in line" by TXing initially below 1000, and even on the
DXP calling frequency, with their R-xx report. This causes tons of QRM an
