CWT contest insists on RST?

[sipsmi]

Just stumbled on this project; being a Linux only shop here this is a nice find so well done.

I successfully got this configured with flrig for CAT and cwdaemon for CW sending with an FTDX10 and the first contest I tried to check was "CWT".
This seems to insist on RST in the exchange / logging however CWT is just exchange of Name + CWOps_NR ?

Before I start editing a copy of the code have I missed something here?

Many thanks for an excellent project.

Si G0FOZ

[mbridak]

Hi. Thanks for trying it out.

If you change the contents of the F3 macro key from {SNT} {EXCH} to just {EXCH} your problem will resolved.
Make sure you do both the run and s&p F3's.

To edit them you'd go to FILE > Edit Macros after making changes and closing the editor, just toggle between run and s&p to reload the macros.

Hope that helps

Cheers. Mike K6GTE

[sipsmi]

Most excellent - many thanks Mike.
Great bit of software - thanks.

[sipsmi]

So tried the software in the 13:00Z CWT today.

Very nice! Worked flawlessly.

Configuration:
FTDX10 with FLRIG and CWDaemon driving the two Yaesu ports for CAT control and CW sending ( see here for my note on persistent device mapping on Linux ).
not1mm using FLRIG XMLRPC for rig control and cwdaemon UDP socket for keying

What I liked.

• up down arrows to select from cluster band display and auto-fill call
• change speed quickly with PG-up/down
• ESC sent to cwdaemon to stop current text queue
• Space to jump to next required field ( jumped over RST fields.
• UI is effective and good looking

What I don't like.

• my own ability to read cut numbers at 40+ wpm ( nothing to do with the software :-) )

[mbridak]

Thanks for the follow up!
I'm glad it worked well for you.
Cheers, Mike K6GTE