Winter Field Day is a once a year 24hr emergency preparidness event for radio amateurs (Hams). During the event, we try and make as many radio contacts with other Hams in a 24 hour period. Bonus points are awarded for operating outside or using alternate power sources, such as battery/solar/wind. You can find out more about Winter Field Day by visiting the WFDA. You can find out more about amateur radio by visiting the ARRL.
The logger is written in Python 3, and uses the curses lib. It will work with Linux and Mac, but since the Windows curses lib is lacking it will not work properly in Windows.
The log is stored in an sqlite3 database file 'wfd.db'. If you need to wipe everything and start clean, just delete this file. The screen size expected by the program is an 80 x 24 character terminal.
I decided to write this after the 2018 Winter Field Day when I couldn't find a simple Linux logger for the event. Just a simple logger with dup checking that could generate a cabrillo log for submission.
- K6GTE Winter Field Day logger (Curses)
The project is now on pypi. So now to install and run the package, you would:
#install it with
pip install wfdcurses
#update with
pip install --upgrade wfdcurses
#run it with
wfdcurses- [24.2.19] Fixed deprecation changes to work on Python 3.9+
- [24.1.27] Removed some deprecations.
- [23.1.14] CAT, fixing flrig.
- [23.1.14] Snazzy new app icon.
- [22.12.28] Dropped BeautifulSoup and lxml, replaced with xmltodict.
- [22.12.27] Digital modes are now DG not DI.
- [22.12.18] You can now install via
pip install wfdcurses - [22.12.16] The RAC sections have been updated for 2023
- [22.11.12] Updated for 2023 WFD rules.
- [22.6.29] Added CW macros
This is a simple logger meant for a single op, it's not usable for clubs. There's no networking between logging machines etc.
After launching the program you may want to access the new Edit Settings screen by using the command listed in the next section. Here you can setup your call/class/section, CAT, callsign lookup, Cloudlog intigration, CW keyer.
Navigate the screen by pressing either TAB or Shift-TAB. Settings with brackets [_] are boolean. [_] means disabled and [X] is enabled. They can either be toggled with the SPACE key, or pressing either one of these XxYy1 to enable, or one of these Nn0 to disable it.
After you make your changes, either press the Enter key to save your changes, or the Esc key to abort any changes and exit the screen.
Commands start with a period character in the callsign field and are immediately followed by any information needed by the command.
.H displays a short list of commands.
.Q Quit the program.
.S Access the settings screen
.P# Sets the power level, .P5 will set the power to 5 watts.
.MCW .MPH .MDI Sets the mode. CW Morse, PH Phone, DI Digital.
.B# sets the band, .B40 for 40 meters.
.D# Deletes log entry. .D26 will delete the log line starting with 026.
.E# Edits log entry. .E26 will edit the log line starting with 026.
.L Generate Cabrillo log file for submission.
[esc] abort input, clear all fields.
After the command is entered press the ENTER key to execute it.
Okay you've made a contact. Enter the call in the call field. As you type it in, it will do a super check partial (see below). Press TAB or SPACE to advance to the next field. Once the call is complete it will do a DUP check (see below). It will try and Autofill the next fields (see below). When entering the section, it will do a section partial check (see below). Press the ENTER key to submit the contact to the log. If it's a busted call or a dup, press the ESC key to clear all inputs and start again.
You can enable/disable the use of rigctld or flrig in the settings screen. The flrig default port is 12345, and the default rigctld port is 4532.
The radio will be polled for band/mode updates automatically. There is an indicator at the bottom of the logging window to indicate polling status. Dim if no connection or timeout, and highlighted if all okay.
You can enable callsign lookups by enabling them in the settings screen. If you choose either QRZ or HamQTH place you credentials for that service in the username and password fields provided.
You can enable automatic logging to Cloudlog in the settings screen. Here you can enter your API key and URL to the service, along with a station ID if needed.
Once you put in your own call and choose a lookup provider, the program looks up your gridsquare. I did this because I didn't want to change the settings screen... I'm not kidding. After this, and after it looks up the grid for the other person, it'll show you the bearing and distance to the contact.
Use the Up/Down arrow keys or PageUp/PageDown to scroll the contact into view. Your mouse scroll wheel may work as well. Double left click on the contact to edit, or use the '.E' command. Use the TAB or Up/Down arrow keys to move between fields. Backspace to erase and retype what you need. Once done press the Enter key to save, or the Escape key to exit.
If you type more than two characters in the callsign field the program will filter the input through a "Super Check Partial" routine and show you possible matches to known contesting call signs. Is this useful? Doubt it.
As you type the section abbreviation you are presented with a list of all possible sections that start with what you have typed.
Once you type a complete callsign and press TAB or SPACE to advance to the next field. The callsign is checked against previous callsigns in your log. It will list any prior contact made showing the band and mode of the contact. If the band and mode are the same as the one you are currently using, the listing will be highlighted, the screen will flash, a bell will sound to alert you that this is a DUP. At this point you and the other OP can argue back and forth about who's wrong. In the end you'll put your big boy pants on and make a decision if you'll enter the call or not.
If you have worked this person before on another band/mode the program will load the class and section used previously for this call so you will not have to enter this info again.
You can use either cwdaemon or PyWinkeyer as a keying interface. After you run the program and choose your keyer interface you will find a file called cwmacros.txt in the base directory that you launched the logger from. The file has 12 lines, corresponding to the 12 function keys on most keyboards. The format of the file is simple:
F1|CQ|CQ WFD {MYCALL} {MYCALL} WFD
Three fields separated by a | character. The first field is the function key to map. The second is the name of the macro being sent. Which in this case does not make a whole lot of sense, because you can't see the name... Just go with it. The last field is the macro to send.
There are 4 substitution macros provided: {MYCALL} {HISCALL} {MYCLASS} {MYSECT} They send pretty much excatly what you think it should send.
So if your're running, you might want a macro like:
F2|exchange|{HISCALL} {MYCLASS} {MYSECT}
Who knows... Go wild. The world is your very limited, Oddly specific oyster.
If you use cwdaemon for your keyer, you can use the plus and minus on the keyboard to increase/decrease the sending speed by 1 wpm each time you press it. Pressing Escape aborts the sending.
- Enter a contact at a specific time.
Let me know if you think of something else.