This is a scratch my own itch project. It's just a simple, lightweight logger for the K1USN slow speed CW contest. I consider it now in a usable stable state. Feel free to use it and give me your comments.

• K1USN SST Logger
  • What it is
  • Recent Changes
  • Installing
  • Running
  • Settings
    • QRZ / HamDB
    • CAT
    • Enabling CW Interface
  • CW Macros
  • When the event is over

• Can now send CW via rigctld CAT for those radios that support it.
• Interface is now resizable
• Repackaged for PyPi and it now pip installable

In a terminal type:

pip install k1usnsst

In a terminal type:

k1usnsst

If you wish to used QRZ to look up the full name and gridsquare for inclusion in your adif log, Click the gear icon in the lower right corner and enter your username and password for QRZ. Then place a check in the 'use QRZ' box. If you don't subscribe to the QRZ service, you can place a check in the 'use HamDB' box.

The program can monitor your radio for band changes with either rigctld, FLRIG or None. Fill in the hostname and port for your choice.

Common port numbers are 4532 for rigctld and 12345 for FLRIG.

If you don't have rigctld or FLRIG and your a Debian/Ubuntu based Linux user you can install it/them with:

sudo apt install libhamlib-utils

sudo apt install flrig

In the setting screen, switch to the CW tab. Set the host that is running either cwdaemon or PyWinkeyer. Most likely localhost. Set the port that the service is listening on. cwdaemon defaults to 6789, Pywinkeyer defaults to 8000. And lastly click the bullet next to the service you will be using.

You can now choose Key via CAT to use rigctld to key the radio, negating the need for a winkeyer.

The program will check in the current working directory for a file called cwmacros_sst.txt. If it is not there it will create one. It will parse the file and configure the new row of 12 buttons along the bottom half of the window. The macros can be activated by either pressing the corresponding function key, or by directly clicking on the button. You can check the file to glean it's structure, but it's pretty straight forward. Each line has 3 sections separated by the pipe | character. Here's an example line.

F3|Run TU|tu {HISNAME} 73 ee

The first field is the function key to program. The second is the name of the button. And lastly the third is the text you would like to send.

A limited set substitution macros are offered.

{MYCALL}

{HISCALL}

{MYNAME}

{HISNAME}

{MYSTATE}

{HISSTATE}

{MYEXCHANGE} in case you're too lazy to type {MYCALL} {MYSTATE}

Click the 'Generate Log' button in the lower right side of the screen. Two files will be generated.

SST_Statistics.txt, which holds a breakdown of bands / QSOs / Mults, and a points total for the event.

SST.adi, an ADIF file you can use to merge into your main log if you so choose.

Before the next SST event you should delete the SST.db file to start fresh.