Copasetic Flow

 I made eight QSOs on my first hour long straight key month shift operating as K3Y/6! Points of note: I'm still operating five watts from the kitchen window in San Francisco. The ' shiny F2 ' cutoff was not disproven. The critical frequency between San Francisco and Utah did go below 7,750 kHz and there was only one QSO that went east of Louisiana out to New York. That happened when the fof2 value was about 8200 kHz. Does the Data Fit with ND7K in Arizona? I noticed that while Utah had disappeared again, I was still being spotted in Arizona at 01:00 UTC. Looking at the fof2 values to the spotting station, ND7K revealed that this spot conformed to my evolving rule of thumb. The midpoint fof2 is at about 8,000 kHz at the time, so above 7,750 kHz. Note for future use: The rig's freuqncy/fof2 = 14.0574/7.750 = 1.8138 The factor is for use with this figure.

 I've spent a lot of time getting Project TouCans' straight key back up and running better than ever before this month, and it finally paid off! I made a QSO with N2KPJ this morning! That's San Francisco to New York on 5 Watts! Hopefully I'll have a video QSL later, but in the mean time, There's a look at the station as it appeared this morning, indoors and everything! (Well, I was indoors. The rig was still outside.) Videos I've also cleaned up my dit/dah timing in a week's worth of practice . Here's my latest:

 Back in November, I pushed a datasette plugin to the rm-rbn-history repository that used Jinja and the existing table of QSO coordinates that's also housed in the repository to create kml maps based on Datasette queries.  Here's a video of the latest use case: applying for the SKCC 1,000 Miles per Watt Award In the video I demonstrate the following: Creating a histogram of QSOs by date Querying QSOs by date range to isolate a single day Creating a KML map that loads into Google Earth installed on a Chromebook