[WT-support] Issues from ES9C

[SM5AJV]

I did also see this during CQWW CW. I tried to reproduce it tonight,
but didn't succeed.

During CQWW I think it happened when there was a call written in the
Second Radio Window. The problem was that I didn't always detected when
it actually happened, since the audio was on the other radio when sending the
TU message with the WRONG correction. Sometimes the other guy came back and
made me aware of it. But I think that several QSO may be lost due to this,
since the other guy maybe deleted the QSO since it sounded as he didn't make
it into my log.

73
Ingo SM5AJV / SE5E



> I confirm this bug.
> I cannot reproduce it but has been there for 3 years now and it is very
> annoying.
>
> 73
> José CT1BOH
>
>
>
> On Tue, Nov 30, 2010 at 8:10 PM, Tõnno Vähk <Tonno.Vahk at gafm.ee> wrote:
>
>> That was our first MS in CQWW with WT. Some issues:
>>
>> 3. A serious issue with $CORRECT. It seems that when the callsign field is
>> empty at the time when e.g. a message of $CORRECT TU ES9C is run the
>> $CORRECT send some totally wrong old callsign. Sometimes a call worked tens
>> of QSOs ago. I can't test is now on my laptop (it does not produce CW sound
>> for some reason) to systemize the bug but there is definitely a bug. I would
>> say that $CORRECT needs to be ignored when callsign field is empty, right?
>> This caused a lot of headaches for our RUN ops constantly when they had
>> already entered a QSO but needed to send TU message. Bob, maybe you can test
>> this bug to see what is the stuff that $CORRECT is sending when the callsign
>> field is empty.
>> 73
>> Tonno
>> ES5TV
>>
>> _______________________________________________
>> Support mailing list
>> Support at win-test.com
>> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>
>
>
> --
> --
> José Nunes
> CONTEST CT1BOH - http://www.qsl.net/ct1boh
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>