[WT-support] ALERT! CQWW RTTY RULES FOR MS??

[Tõnno Vähk]

I think a short follow up is in order here.

The dev version worked 100% throughout the whole contest in 5 station network. Band change counters were great, it would have been very difficult without them. CTRL-ARROW now worked 100% in the Bandmap!

Some notes:

1. WT and MMTTY seems to require very powerful computer? I had one of my older but very decent laptops running at one station and the CPU usage was constantly running close to 100% and RTTY code was often delayed. Sometimes it took more than 3 seconds of solid carrier after starting TX for the code to start slowly coming. Is there something that can make it easier for the computer or I just need more powerful machines?:)

2. Check multiplier window does not show if State/Province is needed on another band. It makes it very hard for the RUN operator to know if the stations needs to be QSYed. He should look it up from Worked S/P window but that is usually too hard to do. Could this be improved? I think Check multiplier window needs another column.

3. Partner window is updated only when something written or deleted on the other station's callsign field. BUT... when the callsign is grabbed with Insert from RTTY window then Partner window stays blank! This is a small detail maybe but I guess could be classified as bug? In RTTY thus the partner window becomes very inefficient.

4. Grabbing callsign with INSERT from RTTY window did not work for RUN station when it was in Advanced SO2R mode. I did not test it extensively, just switched to SO1R and it worked OK. But it had to do something with scenarios. My INSERT key was defined as: $LOGGEDCALL $SPACEBAR $GUESSEXCH $F2, F2 was defined as $RST $ZONE and in scenarios F2 was defined as $R2R2 $F2 $R1R2 I think. This might be an serious issue for SO2R operator. Somebody might want to try if he can replicate this problem. For me it seemed to trigger 2xSPACEBAR moving the cursor to S/P field and not grabbing anything from RTTY window.

5. The old thing of wishing to have $KEYB Macro to be inserted in a message to trigger ALT-K (keyboard mode) to be able to program for example TU NEXT $KEYB to do tail ending. Or to send PSE QSY $KEYB to QSY a multiplier. I am not 100% sure - you guys have not already implemented it, have you?? I long for this every CW and now also RTTY contest.

73
Tonno
ES5TV

-----Original Message-----
From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On Behalf Of Tõnno Vähk
Sent: Friday, September 24, 2010 10:41 PM
To: support at win-test.com
Subject: Re: [WT-support] ALERT! CQWW RTTY RULES FOR MS??

It works!:) Everything is correct, counting is correct for both stations and the development version does not explode in my 5 PCs. Not yet at least.

Thanks for fantastic reaction Larry.

And thanks Ed for clarifying the rules. All clear now!

73 and cu in contest

tonno

-----Original Message-----
From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On Behalf Of Laurent HAAS - F6FVY
Sent: Friday, September 24, 2010 8:05 PM
To: support at win-test.com
Subject: Re: [WT-support] ALERT! CQWW RTTY RULES FOR MS??

Hi Tõnno

Tõnno Vähk a écrit :

> Larry, thanks, you mean the current wt_dev.zip from nightly is the updated one?

Absolutely.

The zip file must be dated 24-Sep-2010 17:29 or later (revision 421).

73

Larry - F6FVY
_______________________________________________
Support mailing list
Support at win-test.com
http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
_______________________________________________
Support mailing list
Support at win-test.com
http://www.f5mzn.org/cgi-bin/mailman/listinfo/support