ARRL DX CW contest

 

I spent a lot of time in the contest chair this weekend. While the Olympics were on and on Sunday, the much-anticipated U.S. vs. Canada hockey matchup sparked sports fever in our house, but it belongs to my wife, not me. For me, it was all about contesting, so I happily settled behind the radio.

I began early Saturday morning and continued until Sunday evening, wrapping up at 23:45. Conditions fluctuated significantly: on Sunday morning, I noticed a lot of what I call “wobbling” in station signals. Solar activity picked up on Sunday, and I found many stations calling me were just above the noise floor. I ran for about 90% of the contest and enjoyed every minute. I can always tell when I’m spotted suddenly as the floodgates open with callers!

 

By the end of each evening, fatigue started to set in, and I found myself mixing up S and H or 7 and 8. When that happens, I know it’s time to pull the plug and walk away before frustration takes over.

The station, PC, and antenna all operated flawlessly. I had contacts from South America, Hawaii, and even Africa. There were also quite a few QRP stations reporting just 5 watts I double-checked, thinking they meant 500, but nope, it was 5! One of my many pins now claims South Korea, though I know that’s not accurate. When I looked up the call, I realized my mistake, but by then, the station had already moved on.

All in all, it was a memorable weekend of contesting, full of challenges and highlights.

 

RFI issue solved!

 

For those of you who are consistent readers of my blog, you may remember that for some time now, I have had an issue with RFI. The problem it caused was that my contesting program N1MM+ would freeze while CW contesting on 15m and sometimes on 20m and 40m. As well, the Reverse Beacon Network website would get hung up while refreshing the world map and not stop trying to refresh the page. I would just see a spinning hourglass on the map. This only happened when I was on 15m, unlike the issues with N1MM+. I determined it was due to RFI, as when I dropped my power output to 60 watts, the issue was gone. Now, some might say just operate at 60 watts and FORGET ABOUT IT, as was said on The Sopranos, but as for me, I just can’t do that.

Having Blog issues

 

 While taking part of my morning brew I noticed an issue with my blog. I have a list of the blogs that I follow and blogger calls it a blog list gadget. The little squares beside each of the blogs I follow is supposed to be a solid color and it is not. That is not a big deal but at the bottom of the blog list is a link that says "Show all". Now when I click on it the remainder of the followed blogs do not appear, nothing happens. I tried it both on my Windows and Mac pc with the same results. The max blogs you can show it 10 that you follow. When the Show all link is clicked the rest of the followed blogs should appear. I went to the gadget and played around with different settings and nothing was successful. I then went to AE5X blog  who has the same setup for followers as mine. His too the squares were not a solid color and the link at the bottom of the blog list did not work either. Now I am not sure if it is just an issue here or if it is wide spread across all blogger blogs? If you have a blogger blog with this gadget give it a try, give the link on my blog a try at your end and if this is a wide spread issue does anyone have a fix. 

Python script shutting down the station

 

Next up is my Python script for shutting down my contest station. That probably makes it sound like I’m running some massive, high-end operation—but in reality, I just really like things to work smoothly. I find it incredibly handy to simply double-click a Python shutdown icon on my desktop and have everything taken care of automatically. Some might call that lazy, overly dependent on a PC, or a bit geeky. I prefer the last option, and I’m fairly certain my dear wife would agree.

The reason I use a Python script for shutting the station down is the same reason I use one for startup: everything shuts down in the proper order. The shutdown process is essentially the reverse of the startup sequence, with a few hiccups that required some creative workarounds.

One issue was that certain applications—Win4Icom in particular—take noticeably longer to shut down than they do to start up, so I had to extend some of the timing in the script to allow for a clean exit. Another problem was that Win4Icom was not shutting down my Icom 7610 as it’s supposed to. As a result, the radio was staying powered on until the Wi-Fi plug turned off, cutting power to the supply and abruptly killing the radio. That obviously doesn’t allow for a proper shutdown sequence.

In the video, you’ll see that the Icom 7610 now shuts down cleanly at the very end of the shutdown process. I accomplished this by adding Python code that sends the appropriate Icom HEX command to power down the radio correctly.