Just for fun

It’s been over two months since I last posted, and I realized that part of the reason for that is that I’ve been waiting for something “important enough” to write about. Along the same lines, I’ve skipped operating in a couple of contests recently where I’d done so in the past because I didn’t have enough time to put in more than a couple of hours in the chair. I decided to fix both of those things recently.

Last weekend was one of the “big” contests, the CW version of the ARRL DX contest. In this contest, DX stations work US & Canadian stations, and vice-versa. (As opposed to contests where anybody works anybody, or are primarily US/Canada only.) This is a 48 hour contest, and while I’ve never operated for that entire period, I do usually try to spend time operating both during the day and in the evening to take advantage of different types of propagation at the different times of day. Last weekend, I didn’t have time to do that, but I did have a few hours on Sunday afternoon. I decided to spend the afternoon working whatever stations I could. When I operate in a contest, I like to have some kind of goal for myself. For this contest, I knew that I wasn’t going to beat my own personal best, so I decided that I’d do nothing but work multipliers for my first 100 QSOs.

Generally, this is kind of silly thing to do, especially for person who works in “Search & Pounce” mode, where you’re trying to just make contacts. Multipliers have additional value, and there are all kinds of strategies on working multipliers versus just working stations, but most of those apply to bigger stations who know they’ll be competitive. In any case, I decided that it would be fun to do, and that’s exactly what I did. Once I hit 100 QSOs I started working any other station that I found, but I still managed to work 141 multipliers out of 169 contacts.

My final score was only a bit over 71,000 points, which in this contest, is very low, but I did have a good time doing it, and that’s the point. Hopefully, this will get me “back in the saddle” for both contesting and working on my blog.

For anyone interested, here’s my claimed score:

         Band    QSOs    Pts  Cty
           7      35     105   22
          14      66     198   58
          21      56     168   49
          28      12      36   12
       Total     169     507  141
Score : 71,487

Post-post Thanksgiving Leftover Leftovers

As I mentioned in my last posting, I’ve still got a few items leftover from Thanksgiving. Unlike the leftover turkey and trimmings, these didn’t have to be tossed out after a couple of weeks, so they are still relatively fresh.
Going back to the CQ WorldWide DX Contest, I did have a few more comments to make. First I really learned to make use of the attenuator on my radio. When conditions are good, stations that are slightly off frequency can make it hard to hear the stations that you’re trying to work. By using the attenuator, it brings down the level of those signals so that I can more clearly hear the station that I’m trying to work. The station I’m trying to work is weaker too, but usually they drop less than the off-frequency station and it makes it possible to better copy what they are sending. This isn’t something that I alone have just magically discovered, it’s just been a while since conditions were good enough that off-frequency stations were so strong that I needed to get them dropped down.
And now, time to jump on my soapbox to talk about two things. The first of these I haven’t seen mentioned much recently in blogs or the contesting lists, but I noticed a number of times where a stations was calling CQ at a relatively slow speed (for a contest), perhaps 18 to 20 words per minute. I was always taught that you should always answer a station no faster than the station is calling, with the idea that you should only call CQ at a speed at which you are comfortable receiving. Why then do stations respond to those “slow” (which is a relative term here) CQs at 30, 35, or even 40 words per minute? I heard this a number of times, and while in some cases the slower station seemed to have no trouble copying the other station, in most other cases the slower station had to repeatedly ask for “fills” (meaning they couldn’t copy the exchange being sent.) If the other stations were too impatient to wait, they should find another station to work. When I work a CW contest, I have the ability to easily adjust my sending speed (I send using the computer, and it’s very easy to adjust my speed up and down in real time) and I have a hard time believing that some of these speed demons can’t do the same.
The second soapbox item is one that has been talked about a lot recently, which is regarding stations that do not ID frequently. For those readers who aren’t familiar with this, here’s the background: The FCC (and their equivalent in other countries) require stations to identify at certain intervals. In the US, you’re required to ID every 10 minutes and under certain other circumstances. Some operators, especially the “big gun” stations who have big signals and many stations calling them, try to shave off a small amount of time on each contact by not IDing after every contact. While a second or so might not seem like much, these are stations that might work 200+ stations in an hour, so assuming there are enough stations to keep them busy (which for those stations may actually be the case), there can, in theory, be enough time saved by not regularly IDing to be able to make more contacts in that time period. As an example, let’s say you can work one station in 20 seconds, or three per minute, which gives you a rate of 180 per hour. If you can shave two seconds off each contact, you can now work 3.33 per minute which translates into 200 per hour. That can add up over the course of a contest, under the right circumstances.
Of course, you need to ID occasionally to fulfill the legal requirements as well as letting the stations listening know who you are. (Yes, some stations can and do just assume that the spot on the packet cluster is correct. Sometimes it is, sometimes it isn’t. I want to hear a callsign myself before I work a station.) While I personally will ID after every contact on those rare occasions when I’m “running” stations, I think it’s OK to do it every 3rd or 4th contact, which means that the listening station have to wait no more than a minute or so to figure out the ID of the station. The problem is that some of these big gun stations have a seemingly endless stream of callers (many of whom are calling because of the aforementioned packet cluster spot) and they don’t ID for many minutes at a time. I’ve read their arguments which I won’t rehash here (if you’re interested, you can check out the archives of the CQ-Contest mailing list) but to me, they are just being selfish. From their perspective, they have plenty of folks trying to work them, and it’s just too bad for those of us who are waiting before calling. Often, I’ll just give up after listening for a short period of time, but I risk missing a valuable multipler if it turns out that the running station was something that I needed.
I don’t know what the right solution to this problem is, since the big guns aren’t going to change their operating processes just because I think that it would be nice to do so. Some contests require the station ID as part of the contest exchange (though sometimes they omit it there as well; I wonder if they will get disqualified if the contest sponsors discovers that?) which solves the issue, but since even minor changes to the contest rules seems to be upsetting to much of the contest community, I can’t see an ID requirement being added to any of the existing contests.

Post-Thanksgiving Leftovers

As most folks know, we had the Thanksgiving holiday here in the US last week. It’s a tradition to not only eat turkey with “all the fixin’s” but also have have some leftovers for a few days after that. I’ve got the same for my blog mostly with respect to things that were still around after Thanksgiving. So, in no particular order:

I did my usual “playing around” in the big CQ World Wide DX contest this past weekend. This is one of the “main events” in the ham radio contesting world, and while I didn’t really have time for more than just a few hours of making contacts, I did note a few interesting/amusing/annoying things. In this contest, you get points for working stations in other countries (not your own) with what’s called a “multiplier” based on the country and something called a zone. (The term “DX” refers to a station from another country.) Without going into too much detail, it’s relevant to know that there are 3 zones within the US. Your score is calculated by multiplying your points (number of contacts with stations outside your country) by the zone and country multipliers. You are allowed to work stations in your own country for the multiplier value, you just get zero points for doing so. It’s important to note that while you can get the 3 zone multipliers that are available for the US by working stations in Canada, if you want the country multiplier credit for working the US you must work a station in the US. Since it’s a zero-point contact, what I try to do is to find a US station that’s not busy and work them, since I don’t want to take them away from working their DX. Most operators understand this and have no problem with it, but on at least one occasion I called a US station who was CQing (repeatedly) with no responses only to have him respond “SRI ONLY DX”. In other words, he was telling me that he would not make a contact with me.

As noted, I only work US stations when they aren’t busy which was the case here. A complete contact with both stations exchanging information during a CW contest (which this was) takes around 20 seconds or less. So instead of helping me out by just completing the contact, he probably saved maybe 10 seconds by sending that other information. So much for good sportsmanship. (For what it’s worth, I noted his call and will avoid making contact with that station in the future, even in contests where non-DX contacts “count”.)

Also during the contest, I was working stations on 20 meters just calling stations and tuning up the band to find the next station. It’s not unusual, while doing this, to have another station that is doing the same as you are, and depending on what band you are on and the propagation conditions, you’ll sometimes be able to hear the other station. Sometimes, you wind up moving with that other station (sometimes more than one) and working the next station up the band either just before or just after that station repeatedly. Normally this isn’t a big deal, but I got stuck behind the equivalent of tractor-trailer truck on small road doing 20mph below the speed limit:

There was a station that would usually call the DX station before me and work him first. No problem. However, unlike the normal orderly contact sequence (which for this contest is very simple: a signal report, normally 599, then your zone, which is 5 for me, meaning my half of the exchange is send in CW as “TU 5NN 5”, with “TU” meaning Thank You, acknowledging that I got the contact information from the other station) he’d send something like “TU 5NN 4 4 4 TU DE (his callsign) (his callsign) (his callsign) 73″. You might send your callsign if you think the DX station didn’t get it, but the accepted way of doing it is prior to the other information and only if you think the other station might not have gotten it correctly. What wound up happening is that the DX station (who is normally working stations very quickly; remember that I mentioned it normally takes 20 seconds or less to complete a full contact) would hear the “TU 5NN 4 4” then assume that the other guy was through sending and send his “TU QRZ?” (meaning he got your info and is moving on), only to realize the guy was still sending. In one case I heard the DX start to send his final sequence 3 times “TU …  TU … TU” before the other guy finished.

The problem with doing this is that you slow everyone down, and while it’s not against the rules to do this, it’s another example of poor sportsmanship. The station doing this had to know that he was slowing everyone down. (And before everyone jumps on me, this was definitely not a new contester, so it wasn’t a case of “not knowing better”.) I’m not sure why he was doing this, but finally I just gave up and jumped far enough up the band so that he was no longer “in front of me” anymore. (In fact, I went way up the band and started tuning down, meaning that while I might cross paths once more, it would be in opposite directions.

I’ve got a few more leftovers to go, but I think I’ll just put them back in the ‘fridge for next time.

Powerline noise problem, resolved

As I mentioned in my previous post, I’d been having a problem with powerline noise recently. The noise started to improve after about 2 weeks, with it disappearing for periods but then returning, until gradually it stopped entirely around a week ago.

As I mentioned, I had reported the issue after about a week to the local power company and while it took a while (just under two weeks), I got a message yesterday from a technician who had been dispatched to check out the problem. He said that he was at my house at the time (I was at work) and wasn’t hearing any unusual noise but asked me to call him to discuss the problem. When I first listened to his message it sounded like he had just listened with his ears (not with any kind of equipment) and my first thought was that I’d have to go through and re-explain the situation to him. I didn’t have a chance to call him back until today, but when I spoke to him I discovered that he did understand the issue and worked in the department that deals with, among other things, RFI and TVI problems.

He asked me whether I’d had issues like this in the past (I haven’t) and I talked about how the noise seemed to start right after the power was restored to some nearby houses after the freak snowstorm in October. He said that what may have happened is that in situations like this, when they initially restore power they’ll do so in a temporary manner just to get people hooked up then come back later and and do a more permanent job. His thought was that the temporary fix was noisy, but as they went back to “clean up”, they may have found and corrected the issues. So while I don’t know exactly what caused the problem, the good news is that the problem is gone.

The other good news is that he gave me his contact information and told me that if the problem returns that I should call him directly, at which point he’d come right out (instead of me having to wait a couple of weeks) to investigate.

Powerline noise issue

Despite the fact that I live pretty close to some power transmission lines as well as the regular above-ground residential service, I’ve been pretty lucky in that I’ve never had much of an issue with powerline noise. Unfortunately, that changed just about a week ago. It might be coincidence, but there there were about 4 or 5 houses around a block away from here that lost power due to the October snowstorm that didn’t get it back until last Friday, which is when I started getting S7-S9 powerline noise on all the HF bands, 2m, and, to a lesser extent, 70cm. Given that there were still others in the area without any power (we were very fortunate in that we never lost power at our house), I figured I’d wait until the local power company indicated that they’d finished restoring power to everyone before calling to report it. (Powerline QRN is bad, but it doesn’t come close to not having lights or heat.)  In the meantime, I put my main HF rig (Icom 756 Pro II) on a battery and turned off the main breaker to the house to eliminate any possibility that it was something in the house, but with that done, there was no change to the noise signature.

On Wednesday, the QRN was gone for a few hours in the middle of the day, and I figured that maybe they’d found and fixed the problem on their own, but it was back by the afternoon. Yesterday, the power company officially announced that all customers were back in service, so I figured that I’d give them a call today to see what they’d say.

The automated voice response system had no way to understand “RFI” so it thought I was reporting an outage, and because that’s not the case, I finally got through to a human … who seemed equally baffled. I explained that I was an amateur radio operator and that I was hearing electrical noise that I hadn’t heard until about a week ago. He put me on hold for about 10 minutes and when he came out he said they’d be dispatching a crew.

While the recommendations for a situation like this are to try to narrow it down to a small area or even a single pole, in additional to not really having the right kind of DFing equipment for this, I’m home tending to one of my kids who is recovering from minor surgery, so I didn’t want to spend the time walking or driving around. I am crossing my fingers that PSE&G (my power company) will take this seriously enough to send out a properly equipped crew and find the problem. I’ll be keeping my fingers crossed.

Here’s a short video that I took showing what the powerline noise looks like:

TI7/K2DBK officially approved, Part 2

Please read Part 1 for the beginning of the story and some background.

Based on the information that I’d previously described, I sent an email to the Logbook of The World (LoTW) desk at the ARRL in mid-June briefly explaining what I’d learned and asking what would be needed for them to issue a certificate so that I could upload my contacts. (Briefly, each contact is “signed” using a digital certificate to ensure that it’s valid. The ARRL issues a certificate to an operator when it is satisfied that the contacts were made legally.) I got a quick response back which referred me to the ARRL’s Reciprocal Operating page which gives the requirements needed to operate from different locations around the world.  The information provided for that page links to OH2MCN’s terrific site that has details for hundreds of countries. The information on his site is largely provided by hams who have operated from those locations, but sometimes it’s not always completely up to date. (As an example, you can see my contribution to the entry for the Cayman Islands, which in turn has been updated since I wrote to Veke.)  Unfortunately, the information for Costa Rica did not include the updated details regarding SUTEL (and still doesn’t as of the time that I’m writing this.) I responded back to both the LoTW desk and the DXCC desk (since the DXCC desk is ultimately responsible for determining if an operation is “legal”), but did not hear back from them prior to leaving for Costa Rica.

After I returned, I electronically requested a certificate for my operation. As with most operations from other that a home country, I was advised that I needed to contact the ARRL with the required supporting documentation. I sent another note to the DXCC desk in early August again explaining the situation but after a couple of weeks of no response, I sent a note to Joyce, KA2ANF, my Division Director who did whatever magic Division Directors do and got me a reply form the DXCC desk. Unfortunately, the reply was substantially the same as the initial responses that I’d gotten back (referring me to the Reciprocal Operation page) and didn’t address the changes in the licensing authority. It said that even though their information was outdated, that I’d need a license or some other documentation from the local licensing authority.

At this point, it occurred to me that many of the people who I’d emailed or spoken to had operated recently from Costa Rica, certainly within the last two years, and several had been issued LoTW certificates. Since there was precedent, I figured that the best way to find out how they had gotten their certificates was to ask, so I gathered up a list of email addresses, and sent out an email, that said in part:

…I noticed that you have recently uploaded contacts from a Costa Rica operation to LoTW, and I was wondering if you’d recently obtained a certificate without a paper license, or if you had a previously-issued license that was used to obtain your certificate. To be honest, I’m hoping that you might fall into the first category meaning that there is precedent for my certificate to be issued under the same conditions.

Over the next couple of days, I got back responses from pretty much everyone I wrote to (and some that I didn’t; my note got passed on to a few others who I hadn’t originally written) and the story from each of them was the same: No, SUTEL wasn’t issuing licenses but it was OK to operate from Costa Rica as long as you were in the country legally and had an appropriate US license. N0KE, AA8HH, N0SXX, and K4VAC (which is a club) all confirmed that they’d been issued LoTW certificates based on the “new” information about licensing. Better still, I received information from several hams that included emails between themselves, the ARRL, and in some cases, between Keko, TI5KD, the president of the Radio Club de Costa Rica where the licensing information was explained and accepted as valid by the ARRL.

I wrote another note to the DXCC desk and provided this information, and waited. After another couple of weeks, I sent a reminder note (I know those guys are busy, and my issue certainly wasn’t a big one) and got a response back. They’d started to investigate, and would be getting back to me. I felt that at least they were finally reading what I’d written and there was hope. Just a few hours later, and I got back another email telling me that my operation was accepted and a LoTW certificate would be issued shortly. (It was.)

I’d like to thank everyone that I mentioned here for their help in getting through all this. In particular, Keko, TI5KD  was very patient in explaining the situation and helping me to be confident that I would eventually get through the red tape.

On a final note, I realized that in the spirit of “giving back” to the ham community, the best thing that I could do would be to get the information on OH2MCN’s site updated, so I’ll be writing to him shortly with the details that I’ve provided here (though in a more concise form).

TI7/K2DBK Post-event wrapup, part 2

This is part 2 of the series, click here to read part 1 

It’s been another crazy week at work and at home and I’d hoped to have another entry or two posted by now, but I just haven’t had the time. I’ve finally found a few minutes, so I’d like to focus on things from a DX perspective and talk a bit about QSLing.

As I’ve previously noted, the weather kept the total number of contacts far lower than I’d hoped, with the total number of contacts ending up at 87 for the week (including one duplicate who I helped out with an antenna check). It looks like I worked 22 different countries though I believe that one of those will be a busted call: I logged a caller with a “DX” prefix which would correspond to the Philippines but at the time I was working into Europe and I suspect that it’s actually a “DL” call. In terms of “best DX”, I worked into European Russia (UA) and Ukraine (UT) a few times, with the majority of the countries being in central Europe such as Spain, Italy, France, Belgium, Germany, Hungary, and others in that area. I worked relatively few US states, though I don’t have good statistics on the because I didn’t get the state from all the operators that I worked. Most of the stateside contacts tended to be in the US Southwest although I did work up into Virginia and farther up the US East Coast for a few contacts.

As I mentioned in my last post, I did manage to get a full-blown pileup going a few times, and I can really understand how addicting this can be. I’d love to be able to operate from a “real” DXpedition, or even from a “primarily radio” vacation somewhere, but for now my vacation time is limited so I tend to squeeze in radio when I can. I hope that at some point over the next year or two I can get creative and find time away for a “radio” vacation.

Regarding QSLing, I got a question this week from a station asking me about whether the contacts would be uploaded to Logbook of The World. As regular readers of this blog know, I’m a big fan of LoTW, and would love to make the contacts available there. However, I’m having some issues getting a LoTW certificate issued and it’s not clear when (or if) that issue will be resolved. (This only applies to my operating from TI7.) In the meantime, if you need a card, please QSL via my home call the “old fashioned” way with a paper card. Because of the relatively few contacts made, I’m not going to have a bunch of card commercially printed but I will design and print a card specifically for this operation. My QSL information is always kept up to date at my entry on qrz.com.

If you want to check to see if you’re in my TI7 log, I’ve uploaded that to the Clublog website which you can search here. If you think you worked me and you can’t find your entry in the online log, please drop me a note and I’ll check for you as it’s entirely possible that I busted a call or two.


Subscribe FREE to AmateurRadio.com's
Amateur Radio Newsletter

 
We never share your e-mail address.


Do you like to write?
Interesting project to share?
Helpful tips and ideas for other hams?

Submit an article and we will review it for publication on AmateurRadio.com!

Have a ham radio product or service?
Consider advertising on our site.

Are you a reporter covering ham radio?
Find ham radio experts for your story.

How to Set Up a Ham Radio Blog
Get started in less than 15 minutes!


  • Matt W1MST, Managing Editor