banjoplayinnerd: (Default)
Lately I have been messing around with Esperanto, which like several other hobbies I picked up as a young man and had to drop when I got married and started raising a family. If you've heard of it, it's probably in the context of "it's a language that everyone in the world was supposed to learn to speak, but nobody speaks it any more" or some such incorrect piece of information. It is in fact alive and well, and like many constructed languages (from Solresol to Klingon) the Internet has given it a pretty sizeable boost. It's the 16th or 17th largest language on Wikipedia in terms of the number of articles written in the language, and it's one of 64 or so languages available on Google Translate.

Google Translate is an example of how "it's not so much that the bear dances well, as that it dances at all." Some of the translations I've run through it are pretty good. Many are lacking in one or more ways, primarily in the absence of certain words in Google Translate's vocabulary. For instance, it doesn't know the word "banjo." (For the record, the Esperanto word for banjo is . . . "banĝo." The two are pronounced the same; the letter "ĝ" in Esperanto has the same sound as the g in "ledge" or "orange.")

And this morning, it got one translation very, very wrong. There's a site called "Lernu!" (Esperanto for "Learn!") that sends out a word of the day every day, defined and with examples in Esperanto. Today's word was "veneno," which means "poison." The examples are sentences like "Plena glaso da vino, sed kun guto da veneno." (A full glass of wine, but with a drop of poison.) They show how the word can be used as a noun, a verb, as part of a proverb ("Running like a poisoned mouse" - something I've never heard before) and even as a part of a statement potentially inconsistent with continued viability ("Nobody can poison me - I'm immune!")

I decided to run the examples through Google Translate to see what would happen. Most of them translated closely enough that I could make the leap the rest of the way, and a few contained words that Google didn't understand, like "veneniĝo", literally "becoming poisoned".

And then we got to the last example, "Li povas morti, ĉar ni ne havas kontraŭvenenon." Google translated this as "He can not die, because we do not have an antidote." Kudos to Google for having "kontraŭveneno", literally "counter-venom", in its vocabulary. But the first part of the sentence is not just incorrect, it's wrong. "Li povas morti" means "He could die" or "It is possible that he can die." Google's translation "He can not die" is the polar opposite of what it should be.

I doubt anyone would ever use Google Translate to save someone's life, and if they did I doubt they'd need to do so by translating Esperanto into English. Even so, one has to wonder how Google got "povi" into its vocabulary with a value of "can not" instead of "could."

And for the record, it's not just English. "Li povas morti" comes out as "Él no puede morir" in Spanish and "Er kann nicht sterben" in German, both meaning "He can't die" and both just as wrong as in English.

Machine translation these days is moderately good. It's at least in a lot better shape than it was when I first heard about it in the early 1970s. But it still has a long way to go.

---------------------------------------------

I haven't been doing a lot of radio lately, but Saturday I fired up the software to see who was out and about. Conditions were good, and I saw signals from France, Germany and England. Other stations were calling hams in Eastern Europe and Africa, but I couldn't hear them.

When the French station ended up a QSO with a station near me and started calling CQ, I decided to answer him. To my delight and surprise he came back with a signal report just on the lower edge of the "good" range. I had hoped to catch the German station too but apparently he went off the air while I was making my exchange with the French station.

There's a natural phenomenon called the sunspot cycle. You may have heard of it. Over about an 11 year period the number sunspots waxes and wanes, and when it gets high, it's good news for high frequency radio communications. At the peak of the sunspot cycle in 1979 I was working stations all over the world on 10 meters. The peak of the sunspot cycle is going to arrive within the next year or so and I want to be ready. Maybe the opening to Europe over the weekend is an indication that it's on its way.
banjoplayinnerd: (Default)
This morning I had a few minutes to kill before I had to take off for work so I fired up the radio and did an exercise I call "one ping only." This is a reference to the Sean Connery/Alec Baldwin movie "Hunt for Red October." Baldwin's character sends a message to Connery, a sub commander, and wants him to acknowledge the message by pinging Baldwin's submarine once. "Vasily," Connery says to his XO, his voice unmistakable even with a hint of an Eastern European accent, "Verify our range to target. One ping only."

When I do a "one ping only" I send out a single CQ, not necessarily expecting a reply but wanting to see if my signal is getting out. If I see a lot of reception reports on the reverse beacon page, I know that frequency is open for business. If I see few or none, it's time to go somewhere else. Sometimes that's a different band, sometimes it's off to read a book or play with the grandkids.

I did a one ping only on 15 meters at about 6:50 this morning and got nothing. No reception reports at all. So I decided to see if anyone was listening on 17 meters. I got one reception report from a guy in Ohio. I was getting ready to switch things off when I got distracted, and when I looked up I saw that I was sending a second CQ. Oh well, no problem, I'll just turn everything off after that finishes. The CQ finished, I got ready to exit the program . . . and saw a transmission on my frequency. The display had been blank, so this was certainly someone answering my call.

WA7KPK KJ2U DN40

Hmmmm . . . DN40. Grid square DN is somewhere in the north midsection of the country. I set the software to send my answer and, as I usually do, searched Google for his call. His webpage on QRZ.com came up, showing that he was from Alpine, Utah and his name is Ken Jennings.

Wait a minute. Ken Jennings? Utah? Could it be . . .?

The answer is a bit farther down the page. "This question comes up from time to time. NO, I am not the Ken Jennings of Jeopardy fame . . . but I am his father. Unfortunately, DNA does not flow uphill." It's accompanied by a picture of his son with Alex Trebek, and a Jennings family portrait.

So that is my brush with those near greatness for today. I can add that to one of my best friends from Texas who was Willie Nelson's veternarian's assistant, and the time I did Windows 95 tech support for a woman who had been on a Mormon mission with Donny and Marie Osmond's parents. (One of these days I'll write about the time I got a tech support call from Donny Osmond.)

UPDATE: I got a very nice note attached to Ken's electronic confirmation telling me that his wife is from Edmonds and his daughter lives here in Shoreline. (His son's Wikipedia page says he was born in Edmonds.) I've mentioned before that JT65 is very formulaistic and you don't learn much about the other operator other than where they are, so it's always nice to get personal touches like this.
banjoplayinnerd: (Default)
* Within the hour of my contact with PY3ED, Edenir in Porto Alegre, Brazil, I got a confirmation, so now I have ten "countries" confirmed. Yay! (OK, so technically they're "entities," because let's face it, two of those "countries" are Alaska and Hawaii, but you say potato and I say solanum tuberosum.) At 6960 miles, give or take, it's not quite the most distant station I've worked this year. New Zealand and Australia beat it out. But I'm still happy to have worked him and the other Brazilian station from yesterday.

* The reverse beacon showed that my signal was getting out all over the place last night, including Japan and South Africa. I tried calling the South African station on the off chance that he was in his shack and watching the software when I called him instead of whatever South Africans do in the morning, but no such luck. Someday . . . someday.

* Or . . . maybe? After I tried calling him I went back to calling CQ before I went to bed, and after about the third try I saw a very faint signal on the waterfall. I could tell it was there but the software wasn't decoding it. At one point instead of CQ I sent QRZ? ("Who is calling me?") in the hope that he would keep trying and conditions would improve, but they never did before I had to switch over to monitoring and go to sleep. When that happens I occasionally tell myself it's some rare DX trying to get in touch with me, but it's much more likely to be a station in the gray area where their signal has gone up into the ionosphere but not come back down yet. Rare DX from Boise or Medford. :-)

* I am waiting to hear back from a recruiter on a job I interviewed for on Thursday. This would be a good job, but it would mean I'd have to commute to the Eastside again. The things we have to put up with to do mundane stuff like pay the rent.

* Igor the Younger banged into my banjo the other day. He knocked the bridge flat, broke the first string and knocked the tailpiece a bit out of line. I wasn't happy about this, but I'm glad he didn't put a hole through the head. I'd been thinking I can't remember the last time I changed strings, so it was time to do that anyway. Now I'll probably just take all the strings off, clean everything that looks like it can be cleaned, realign the tailpiece and put on new strings. If I do that it probably won't take much to get it into shape for my Interfilk gig at Conchord when that gets ready to roll around.

When I inspected the damage I found a crack in the bridge, so I'll also need to order a new bridge. I use a compensating bridge these days and the local music store doesn't carry them. Dusty Strings might, but I never make it to that part of town anymore. Honestly it's easier to order one over the net.
banjoplayinnerd: (Default)
There are days when I think I'm just shouting into the ether, calling CQ over and over and getting no replies even though I know people are hearing me. And then there are days when I make a few contacts but they're all in California. Nothing wrong with California, mind you, but working stations from a single area is like eating steak every night for dinner. As much as you might like steak, it's nice to have a pork chop or some chicken or macaroni and cheese once in a while.

And then there's tonight.

Tonight I worked not one, but two stations in Brazil, the first in the state of Rio Grande do Sul in the far southern part of the country, and the other near São Paulo. These are my first contacts in South America in a very long time. So I'm feeling pretty good and hoping that if I can pull in a signal from Porto Alegre, Uruguay and Argentina can't be far behind.

And now it's bedtime.
banjoplayinnerd: (Default)
The Igors are spending time with Mom and Dad this weekend so no playing fish or facilitating Officer Igor. Which is fun and all, but there's a bunch of stuff coming up the littles wouldn't be interested in.

* Folklife!

OK, the littles would love some parts of the Northwest Folklife Festival, and I hope their parents take them, but I for one don't envy anyone trying to chase Igor the Younger around a cheek-to-jowl Seattle Center. He's just too big and too fast and could be in the wading pool next to Key Arena before you can say "Bob's-yer-uncle."

Some of the things I like about Folklife:

. The price is right. It's free (funded by donations actually).

. Picking a spot and just watching "the free show" as my dad used to say. Just seeing the amazing variety of people going by.

. Listening to the buskers performing along the walkways and under the trees.

. Wandering around through the vendor displays. All kinds of food and lots of cool items I can't afford. I really miss the Musical Instrument Showcase; they used to have an entire room dedicated to selling instruments topped off by an auction, but the auction closed down several years ago and the Showcase wasn't far behind. I bought a didgeridoo and a Pyrex flute at the Showcase in years when I was a bit more flush; I still have both of them.

. Plopping down in a performance venue without knowing what's going to come up. You could get old novelty tunes from the 20s and 30s on fiddle and uke, followed by a bandura concert and then by a traditional Thai dancer. We've seen gamelans and zydeco, storytellers and Irish bands.

This year we have a destination in mind rather than completely surrendering ourselves to serendipity. Miss Thing, our 15-year-old choir student, has an assignment to go to a choral concert and write a report by the end of the school year. Folklife is showcasing the Seattle Women's Choir, the Seattle Men's Choir, and the Seattle Girls' Choir on Sunday. I think that should qualify.

* Radio!

The bands have been a bit more active lately. I'm still not hearing anyone outside North America, Japan, Australia and New Zealand on HF, but that doesn't mean I should quite looking. I still need to get the antenna up in the air.

* Contest!

Ham radio contests are interesting critters. The idea is to make contacts with as many participants as possible during the span of the contest. Some contests are limited in scope (hams in Michigan, for instance, or veterans), and the idea is to contact members of that scope for contest credit, or if you're a member of the scope, make as many contacts with anyone participating as you can. Some are open to everyone who wants to participate, and everyone contacts everyone else. There are byzantine rules about how to calculate your score, but the basic idea is, work as many stations as you can. Contacts tend to go pretty quickly.

This weekend will be the CQ Worldwide WPX Contest, CW (Morse code) version, sponsored by CQ Magazine. It's a free-for-all where your score is in part based on the number of different prefixes you work during the contest. In this context the "prefix" is the part of a radio ham's call that precedes the block of identifying letters. It generally has both alpha and numeric characters and ends in a number. So for my call, WA7KPK, the prefix is "WA7". It's not as common a prefix as it used to be, but it's by no means rare. Then there are calls like 4U1ITU, the ham radio station at the headquarters of the International Telecommunications Union, the UN body charged with international radio regulations. Their prefix, 4U1, is literally unique. There's only one station with that prefix.

CQ Magazine sponsors an award called the WPX, which you can earn by getting verified contacts with ham stations with 300 different prefixes. It is probably possible to work enough stations for the WPX during a contest weekend. Certainly if you're attacking the contest seriously, you can do it if you can get the contacts verified. It's been many years since I did any heavy-duty contesting, and I don't know how involved I'll get with this contest. I may just hang around, give some participants a new multiplier, and not take it too seriously. The contest starts at 5 tonight and runs for 48 hours; there's no way I'll spend that much time at it (especially since you're required to take some time off during the contest). Or I may see how close I can get to that magic 300. I have over 50 now in about two months of operation, so who knows?

* General hamming!

Just getting on, doing some casual and digital operation. One of the interesting things about contests is that a big free-for-all like WPX can crowd the bands, leaving hams who don't want to participate grumbling about "those *%!@(& contesters". Some years ago three new bands were added to the ham radio spectrum; part of the deal for allocating those bands to us hams was that contest activity would not be allowed on them. I may meet up with some refugees from some of the more crowded bands on these so-called WARC bands if I decide the contest has crowded everyone else out. That, and my normal nets on Saturday, Sunday and Monday.

* Work!

Yes, the curse of the working class. I'm a contractor and need the money and don't get paid time off on this contract, so hi ho, hi ho, it's off to work I go. I have a couple of jobs I can do while everyone else is off enjoying the weekend.

Here's hoping you enjoy your weekend and get to do something fun.
banjoplayinnerd: (Default)
Lately I think I've mentioned a few times that I have a politician station, one that talks a lot and everybody hears it but it doesn't listen so well. That opinion is being reinforced today.

I am on the 15 meter band, one of the upper bands where long-distance communication is pretty common. The various maps and tools I use indicate that the band is hoppin'. There are people posting reception reports on the reverse beacons for stations in Europe and South America. Some Japanese stations are reporting in.

I'm showing up on the reverse beacons as well. I call CQ and get good signal reports from all over the US, plus occasionally ones from Australia, New Zealand or Japan. These aren't stations that are trying to contact me -- just ones (possibly unattended) who have reported hearing my signal.

The thing is, I'm calling CQ because I can't hear much of anything. There are a few stations listed in my reverse beacon reports that I picked up while I was out buying dishwasher detergent for my wife, and the highest signal strength I reported was a -20 (with -1 being "you sound like you're right next door to me"). The reports go down to -24 and even one at -27, which is right down in the noise that's always present in the radio spectrum. In contrast the reports people are giving me are good and string, with reports from -4 to -6 pretty common and even a -1 once or twice.

I can only conclude that there's something about my situation that is causing me to be as deaf as a sixth-grader on garbage day. One clue might be the signal strength of the background noise. I seem to remember it was at a fairly low level when I had my station in Montana. On the "S" scale we use it was maybe S2 or S3. At the moment my noise level is around S9, which would be a good signal if it were coming from a transmitter instead of . . . everywhere. In Montana I was still in the middle of a moderate-sized city, but those were the days before ubiquitous computers, cell phones, digital this and digital that and every piece of equipment in your house from your cable box to your toaster having a computer chip in it. Did I mention that computer chips are active sources of radio interference? There's a famous article from QST magazine where a guy built a transmitter from a single hex NOR gate integrated circuit and a few spare parts. It was a really weak transmitter, but he hooked it up to an antenna and made a few contacts with it.

I can only hope that the reason I'm getting so much noise is because my antenna is so low to the ground and runs through the house, picking up RF interference from all the computers we have around here. Once I figure out how to get the antenna higher in the air, the noise will die down and I'll be able to hear the weaker stations. I hope. (My favorite antenna in Billings was 30 feet up in the air. I wish I still had it.)
banjoplayinnerd: (Default)
Oh wait, that title is kind of a spoiler, isn't it?

For several days since I got the computer back up and running I had been having trouble making contacts on JT65, my current favorite digital mode. I wasn't showing up on the reverse beacon page when I called CQ and I wasn't seeing anyone on the waterfall (the scrolling signal display).

I couldn't figure out what was going on. I was sure I had transmit power. The audio was working OK, at least to make contacts on the local repeaters. I could hear Morse code signals. Everything was connected properly. I was starting to wonder if someone had taken down my antenna and replaced it with a dummy load - basically a big resistor used for testing that acts like an antenna except it doesn't radiate.

Then last night I looked down at the waterfall and saw a signal. I don't know who he was because the software hadn't decoded the message. I took a closer look and saw that the transmission had apparently started several seconds after the beginning of that minute.

It was then that a bit of enlightenment burst through the fog banks of my mind. Everything I had read about JT65 said you need to have absolutely accurate time because JT65 uses the current time as part of the decoding mechanism. If your time is off by up to about a second you're probably OK, but any higher delta can be a problem. The emphasis was on setting up a time synchronization program like Dimension4 in Windows, because Linux has the ntp protocol to keep machines on time.

Could it be that simple? This was a freshly installed Linux machine, and I thought Linux always installed ntp (the Linux time sync program) by default. Maybe I was wrong about that. Sure enough, "sudo install ntp" installed a new program instead of telling me I already had one running, and "ntpdate time.nist.gov" told me it was updating the clock, setting it back seven seconds. That's probably about how much the signal had lagged behind the start of the minute.

So that explains why signals weren't decoding, and conversely, why no one else was able to decode me. As for not seeing any signals, I chalk that up to a combination of the time differential and fairly poor band conditions the last few days. That's my story and I'm stickin' with it.

Last night I made two contacts, one with Michael in Plymouth, MI (a new state for me on JT65) and one with Richard in Vancouver, WA, who I've worked before. And I was very happy to have both contacts.

Now if that South African station would just reappear . . .
banjoplayinnerd: (Default)
It's been a busy week for me. Since Friday:

* I built my wife a Windows 7 computer out of the box my daughter donated us (the one she got from her brother). It has the new hard drive in it. So far it seems to be working OK, except that sometimes it takes a while for a command to fire up. I'll have to see if I can figure out why that might be happening. All of her files are there and her browser's home page is set to her favorite MMORPG, so she declares herself happy. (And will probably be even happier when I put Age of Mythology on for her.)

* Once she was up and running I used her former Windows XP machine as the basis for rebuilding my server/ham radio machine. The installation actually went quite well so far. All of the programs I regularly used on the previous version of the machine are in place. I can ssh into the machine, use squid as a remote proxy, serve up the family's pictures and music in samba and just generally keep the house running. I don't have mail for penguinsinthenight.com set up yet, but that will come soon.

* The ham radio programs I've been using lately are on the machine now and are working pretty well, except that one of them insists on resetting the volume to 100% every time it launches. I don't know what's going on there, but I'm a member of the program's Yahoo group so I can ask if anyone's seen anything like it.

* Unfortunately conditions haven't been that good on the ham bands recently, at least for me. For instance this morning I sent out a CQ on 20 meters to see what would happen. The reverse beacon system said only one station somewhere in the Midwest reported hearing me, and my signal level was pretty poor. I don't think it's an equipment problem. Radio propagation comes and goes, and there could be externalities like the solar flare we had last week that could be disrupting communications.

* I never did make contact with the station on Socotra Island off Yemen, and I think they're probably tearing down their camp now and getting ready to head back to Russia and California. I actually never even heard them. I could tell they were there by the pileups, though.

* The fact that I haven't done much radio time isn't necessarily a bad thing. My wife's aunt died over the weekend and she and my daughter drove down to southern Idaho for the funeral. They took Igor the Younger with them. He enjoys long car rides and trips to see great-grandma, at least in principle until he's been in the car for 14 hours. So I've been spending a little time with Igor the Older and my oldest granddaughter.

* I did get out of the house for a couple of hours yesterday. One of the local boys organized a project for his Eagle Scout badge to map out communication capability around the area. A group of teams consisting of Scouts, radio hams and adult Scout leaders fanned out to various locations and we did a survey of how well the hams in each location could hear each of the other locations. This is going to be factored into an area communications plan so we know how well, for instance, we can communicate between my location in Shoreline and another location in Bothell. The distance is only about five miles but there's a lot of hilly terrain and a lot of trees. We were using a frequency right at the edge of where trees start interfering with the signal.

* Once in a while I actually remember to practice my banjo.

Anyway that's what I've been up to the past few days.
banjoplayinnerd: (Default)
Igor the Younger is fascinated with my ham radio setup. Every so often he has been asking if he can "push that thing that goes beep beep beep."

This is where I should explain that when modern-day hams send Morse code they aren't listening for the clack-a-clack-a-clack-a of the key like you hear in old movies. Sometimes, like with an electronic keyer, there isn't a clack-a-clack-a to listen to. Instead they use an operating aid called a sidetone, a tone that the radio emits when the key is pressed. The sidetone gives you an idea of what your "fist" sounds like as it goes out over the air.

So when Igor the Younger says "that thing that goes beep beep beep" he's talking about playing with my key.

Initially I resisted. I occasionally leave my radio on while I'm at work and he's at home with Grandma so I can help out with reverse beaconing, and even though it would be hard for him to actually put a signal on the air with the key if the rig is set for digital modes, he's a regular Curious George and I don't want him messing with the radio when I'm not there.

But then I, being an Evil Mad Scientist (which is why I have a pair of Igors) came up with an evil mad plan.

"Boofy," I told him. "You want to make the radio go beep beep beep?" Of course he did, so I just set the radio to generate the sidetone but not transmit – a feature I learned about a few days ago that lets you do code practice when you're off the air – and parked him in front of the key. He loved it. He spent a good half hour going beep beep beep, and then doing the same thing making short and long beeps with the electronic keyer. He even figured out that if you hold both paddles of the keyer at the same time you get an iambic "di-dah-di-dah-di-dah" pattern.

I also let him turn the main tuning knob and one of the knobs on the antenna tuner. We weren't transmitting and it's easy enough to set them back to where they belonged, so why not? Now he thinks he's a regular Marconi.

He's also fascinated that I put wires across the back yard. Once in a while he will tell me "Grandpa! There are birds on your wire!" Of course I go check to see if there are any birds roosting on my dipole. I don't care if they do, I just don't want them to knock it down or anything.

"Well, Boofy, if there are, I hope when I go beep beep beep it tickles their feet."
banjoplayinnerd: (Default)
There's this guy in New Zealand named Geoff. He's a radio ham, and his callsign is ZL3GA. I've never met him, don't know anything about him other than his callsign and what's on his website . . . and that this afternoon he was able to hear my signal at a low average quality, 7400 miles away.

The intersection of computers and ham radio has provided us with the ability to do some very interesting things. One of those is automated signal reporting, sometimes called "reverse beacon." When a ham is off the air (yeah, it happens once in a while) they can leave their equipment on with the software running and it will report any signals they hear back to a central server. You can then query that server to see if anyone has heard you, and how well.

It looks sort of like this:

UTC RX TX Signal Dial Offset DX Bearing
20:16 WB0LCW WA7KPK -15 21076 8 1535 102°
20:16 KC9RNK WA7KPK -20 21076 11 1759 90°
20:16 K6JEB WA7KPK -13 21076 -27 660 177°
20:16 W5JZ WA7KPK -6 21076 70 1694 117°
20:16 AK1P WA7KPK -19 21076 5 710 175°
20:16 KB3X WA7KPK -11 21076 16 2315 95°
20:16 KB9AMG WA7KPK -12 21076 16 1696 88°
20:16 ZL3GA WA7KPK -17 21076 -48 7402 223°
20:16 K0ASK WA7KPK -13 21076 -11 1517 104°

The column headings are a bit cryptic (and shortened from the original), but the relevant columns are "signal", "DX" (short for "distance") and "Bearing." "DX" and "Bearing" are the approximate distance in miles and azimuth, or great circle bearing, from my location in Shoreline. "Signal" is how well the other station is receiving me. Higher is better, with 0 being the best. My -6 to W5JC in Texas is pretty decent. Most of the other stateside signals are average to verging on poor. (-24 is generally considered about the lowest signal that the software can decode.) The big surprise was my signal into New Zealand, which at -17 is below average but still very readable.

This is a great tool for finding out whether my signal is getting out and how well. The fact that I sometimes have Japanese, Australian, New Zealand and Asiatic Russian stations reporting that they can hear me is a Good Thing. I wish I was being heard by more European stations, but right now I'll take what I can get.

Unfortunately sometimes I feel like I have a "politician" station in that my message gets out just fine but I don't hear them very well, or sometimes at all. I have plans to improve on my antenna over the next month or so and it will be interesting to do before-and-after comparisons to see whether the improvements actually improved anything. 

banjoplayinnerd: (Default)
Yesterday it occurred to me after posting my journal entry entitled "Yemen" that for an American to make a public post on a major discussion forum with a title like "Yemen" might show a lack of common sense.

To that I say, pfffft. Here's why.

Someday I'll post the story of how I got bitten by the radio bug. For now, suffice it to say it happened when I was 8, and by the time I was 11 I was sending reception reports to stations overseas and getting QSL cards - postcards confirming my reception report, almost always with a picture somehow related to the culture, history or scenery of the country in question. One notable exception was HCJB, a primarily ecclesiastical station in Ecuador, whose QSL card just showed their call sign and slogan "Heralding Christ Jesus' Blessings" along with details of the reception confirmation.

Many stations had "listeners' clubs" you could join if you sent in a certain number of reception reports in a year. Members of the club got special stickers, pennants, newsletters or other mementos. The stations loved them, as it was a way to judge who was listening, where, at what times of the day, and how well the signal was getting through.

Some just sent packets of such goodies as a matter of course. The most notable of these, at least of the ones I was able to copy easily, were Radio Prague, Radio Warsaw, Radio Sofia, Radio Bucharest and Radio Moscow.

Notice a pattern there, other than the word "Radio" followed by the name of a national capital? (Back then Prague was the capital of Czechoslovakia; nowadays it's still a capital, but of only about half as much territory.) If you're under about 30 you might be forgiven for thinking they were all just in the eastern part of Europe.

Back in the 1960s, though, these countries were all members of the Warsaw Pact, a mutual-defense organization set up to keep NATO in check. McCarthyism had mostly ended, the John Birch Society was a footnote to politics and Pete Seeger had recovered from the blacklist to perform on TV, but make no mistake, the Cold War was still going. We were only a few years out from the Cuban missile crisis. Propaganda ran hot on both sides, and we and the Soviet bloc countries used any means we could to get the word out. For our side, that included Radio Free Europe and Radio Liberty. For them, it meant the North American services of their international broadcast operations. Interspersed with music and verbal travelogues were editorials toeing the Soviet line on international policy. Radio Havana Cuba was perhaps the most strident of the ones I could hear; I was later able to find others that were even more so.

None of that mattered to me. For me this was a hobby. I was mostly interested in the music and cultural programs and would usually just suffer through the editorials (whether from an eastern European station or the Voice of America) to get to the good stuff. And to get enough information to send the reception report that would get me the QSL I wanted.

One other thing I should mention is not just when I grew up, but where. Richland, Washington was created as a bedroom community for people working on the Hanford portion of the Manhattan Project. Pretty much over one summer weekend in 1943 it went from a sleepy little farm town of about 200 people to a city of over 20,000. And it was all run by the government, and for several years it didn't exist. Mail was postmarked "Seattle." Phone calls either weren't allowed or were tightly controlled. Saying the wrong thing could get you shipped out of town. By the time I arrived on the scene a lot of that had cooled down but we were all very much aware that we lived 30 miles from a first-strike target if the Cold War ever suddenly turned hot.

I have no doubt that the national security apparatus was keeping an eye on the mail at the Richland post office. I don't have any direct evidence that they were reading my letters to Prague and Vienna. I don't have any evidence for any of my suspicions. But I have long believed, given the people we know the FBI was keeping files on in those days, that my overseas correspondence with Foreign Powers did not go unnoticed.

And it tickles my heart greatly to think that somewhere in the other Washington, there is a file folder with my name on it that details the subversive correspondence of an 11-year-old, writing to Radio Warsaw that he had received a news broadcast anticipating a visit by Leonid Brezhnev to Poland followed by a report of an agricultural festival in Lodz.

Oh, and if you ever have occasion to find out that there was no such file, please. I don't want to know about it. I want to go on thinking that I grew up to be nowhere near the threat they thought I'd become.

Yemen

May. 1st, 2012 06:44 pm
banjoplayinnerd: (Default)
The ham radio world is abuzz, pretty much literally, with the news. An 11-man crew has set up a station in Yemen, specifically Socotra Island, and will be operating there for the next couple of weeks.

It's hard to describe how big a deal this is. Yemen and North Korea are the only two countries that currently do not allow their citizens to become radio amateurs, so contact with those two countries is almost nonexistent. Yemen is at or near the top of almost every DXers "Most Wanted" list. Socotra Island is the #1 most wanted location in the Islands On The Air program.

This is BIG.

At the moment I can't hear the Yemen station, but I can sure hear the "pileup" - the gaggle of stations trying to work him. Mostly I stay out of pileups because the "big guns" with their kilowatt signals and huge moose-antler antennas are way louder than I am.

So this time I plan to be sneaky.

According to the crew's web site they plan to use three modes: Morse code (CW), phone (SSB) and radioteletype (RTTY). Morse code generates huge pileups that I'll never get through. Phone is worse. (I'm not at all sure how I worked the French special event station, but their pileup was nothing compared to this.) So I'm going to wait until they are operating RTTY at a time and frequency favorable to North America, and . . . then wait my turn. But there will probably be fewer stations trying to work Yemen on RTTY, so my chances will be better.

Or I may just go chase the easier stations.

Just one more thing: yes, radioteletype is pretty much exactly what it sounds like. When surplus teletype equipment started becoming available after WWII, enterprising hams built modems to convert the electrical signals the teletype uses to audio and put them on the air. When people started experimenting with hooking sound cards up to ham radios, it didn't take long to create RTTY decoders. I've always thought RTTY was an interesting idea, but not interesting enough to buy and convert a teletype machine. Now all it takes is a piece of software. Isn't living in the future wonderful?
banjoplayinnerd: (Default)
So as I often do I got up at 3:30 this morning to go to the bathroom, and stopped off at the radio to see if anyone was on. (This is one great thing about digital modes like JT65. You can turn the volume all the way down because the signal is delivered straight to the computer through an audio cable. I can operate without bothering anyone.)

Guess who was calling CQ?

The same Australian station that had swamped me earlier calling Gabon.

So we made contact and now I have something like three or four Australian contacts and one New Zealander, the last couple of which were with the loop.

Have I mentioned how much I am liking this loop? I may just take the previous antenna down.

The next step is going to be how to make the loop work better. I have two projects in mind:

1. Adding about 60-70' of wire to the loop to make it work properly on the lowest frequencies I intend to use.

2. Raising the whole shebang to 20-30 feet in the air. At least up to a point, the higher up the loop is, the better the signal gets out.

The first should mostly be straightforward. The second will require a bit of ingenuity. Any ideas? (I have a couple that will require PVC pipe and sandbags.)

Oh, and I'm tired at work again, and once again it's my own darn fault.
banjoplayinnerd: (Default)
About 10 minutes ago I jumped up and down in my chair. "I got a Kiwi! I got a Kiwi!"

My wife just looked at me. She's used to this kind of behavior anymore. "So much for you going to bed on time, huh?"

The loop antenna is a success. In the past six hours or so I was able to:

* Make a contact on the 80 meter band for the first time in 30 years
* Make contact with a new state (South Carolina)
* Work Hawaii again
* Make contact with a new country (New Zealand)

And the reason I feel pretty good about the loop is: The New Zealand station called me! I didn't have to force him to dig my signal out of the muck; actually, the signal report he gave me was pretty good.

Now I have a dilemma. On the one hand, it's bedtime and I have to go to work tomorrow.

On the other hand, the fish are bitin'.

Pretty soon the band will dry up in any case, which will make going to bed easier. It's just hard to step away when things are going so well.

= = =

OK, I just thought I saw a very faint signal. The software couldn't detect anything, but I decided that if it was someone I might be able to work, I should give them the chance, so I sent:

PLS TRY AGN

This time there was a much, much stronger signal, so much so that if there was one there before, it couldn't have been the same station.

I just got swamped by an Australian setting up a contact with a station in Gabon.

I think it's time to go to bed now.
banjoplayinnerd: (Default)
Last week I got 200 feet of hookup wire from a supplier on eBay. I wasn't sure at the time what I would do with it, other than put it to work pushing radio waves. So I did some thinking and some planning, and about two hours ago I took the wire outside and started making a loop out of it along the back yard fence. The back yard fence is only about 8' tall, and taller is always better, so I wasn't sure what results I would get, if any, but I figured I'd give it a try.

I got the loop hung, ran the lead-in wires into the shack, and hooked everything up. Now it was time to test. The first test is, can I hear anything? I tuned to the 20 meter band and heard one of the "regulars" there calling CW. So far so good.

Second test, can I tune up the loop? That worked fine too. Now it was time to test.

20 meters was pretty quiet, so I went up to 17 meters, an underused band that hams have only had access to for about 30 years, to see what would happen. On the frequency the radio was tuned to, I heard something interesting going on, so I stopped to listen.

Time for a brief historical diversion.

April 2012 marks the 95th anniversay of the Battle of Arras, a major offensive during World War I near the town of Arras in northern France. Radio clubs often have special station setups and callsigns for big events like World's Fairs and Olympics. There were several special event stations to commemorate the sinking of the Titanic during April; I heard one but wasn't able to work him.

Up until today I had only ever heard about three or four special event stations and had only worked one, and that one was for Mt. St. Helens. The station I was hearing was using the call sign TM95BA. "TM" means the station is from "continental France," presumably as opposed to overseas possessions like St. Pierre et Miquelon. "95" represents the 95th anniversary, and "BA" for "Battle of Arris". Presumably the initials are the same in French.

TM95BA was coming in reasonably clearly and was firing off signal reports in rapid success. If there's one activity that makes JT65 seem leisurely by comparison, it's a rare station making his way through a gaggle of stations trying to contact him (this is called "working a pileup"). He wasn't swamped as far as I can tell, but he was going at the rate of about 3 contacts every 2 minutes, mostly to North American stations with a few Europeans in the mix.

I moved off frequency, made sure the new loop would tune up, boosted my power a little and moved back onto his frequency. Proper etiquette is to wait until a station finishes a contact before calling them, so I dutifully waited for him to signal QRZ? (which is used as an invitation to call) or 73 ("Best regards" - traditional ham signoff) or something similar before I called.

I started calling about 4:45 in the afternoon and he kept coming back to other stations. I don't blame him; they were probably swamping me and my Morse code is pretty rusty. Finally, at 5:03, he sent out a WA7 call. It sounded like what someone might think I sent, but I couldn't be sure. Was he calling me back? I didn't answer, but waited to see what he would do.

WA7? WA7 PSE K. "WA7 station, please go ahead." I slowed way down, both to send better Morse and to make sure he got my call right. If he misheard my call, I would get no credit for the contact.

WA7KPK 599 TU. "Your signal is excellent, thank you." In pileups and contests we hams always lie about our signal strength. It's always the best it could be, even if you have to dig the signal out of the noise. It's faster that way. The DX station knows he's getting out, and the other station just wants the contact. He can get a signal report from ordinary, non-rare stations.

TU 5NN E E. "Thank you. Let's stipulate that you have a perfect signal. Dit dit." The "dit dit" is the end of "shave and a haircut" and often tacked on to a final transmission to mean "I'm done." This is a very minimal contact. He already had my callsign, and I wanted to finish the contact quickly so he could move on to other stations. That's also proper etiquette.

E E QRZ? "Dit dit. Next??"

I had worked Europe! First time in over 30 years. I have to stress that France is by no means considered a rare station, but I managed to get the attention of a station that a lot of hams were looking for. It's always a very happy feeling. And there might be a nice commemorative QSL card in it for me.

I think I can safely say the loop works. Now for the big test. Does it work on the lower bands where I want to be able to check into some of the local nets? That's the real purpose of the project; anything else is gravy.

Now that I've proved the radio works I think I'll go chase Igor the Younger around for a while. Time for more contacts later.
banjoplayinnerd: (Default)
This morning I was up at 4:30 to go to the bathroom, and once that was done I thought I'd see what was happening on the radio. I sit down, switch on the software, and there in the middle of the screen is a faint signal. Well, I think, let's see who this is.

It was a station in Queensland, Australia.

On some bands long distance communication is quite common. I hear a lot of Japanese stations most afternoon on the 15 meter band. With my current setup, though, I consider myself lucky if I can pull in Florida or Hawaii on the 40 meter band, much less Australia.

I called him a couple of times but he came back to someone else, at which point I decided chasing any ham station, Australia or not, was silly when I had to get up for work in an hour.

So I went back and laid down until the alarm went off at 6:00. Got up, stretched, switched on the computer screen and started up the JT65 software.

There he was, the same station, calling CQ again.

I tried calling him a couple of times but he came back to a station in Helena, Montana. I got my shower, dried off, put my clothes on, sat down to put on my shoes and socks . . .

Once more, there he was, talking to a ham in Nevada. So I decided to try tailgating. I waited until he finished his conversation with Nevada and sent the signoff signal, and called him.

No answer. I called again. Still nothing. He had disappeared.

Frequency bands change characteristics according to the time of day, and I figured it was just the right time for the sun to come over the horizon and start bombarding the D layer of the ionosphere with solar radiation, which makes it absorb lower-frequency signals. (That's a gross oversimplification, but it'll do.) It's too bad. I don't get out 7000 miles on any band all that often, much less 40 meters, which I think of as a regional band. It's not - I used to occasionally make it into Europe when I lived in Montana - but most of the contacts I make with it are North American.

And as I pulled on my shoes and got ready to switch off the monitor, I checked the software one last time. There, at the bottom of the display, was the call of an Arizona ham I've seen around the band and worked at least once, giving the Australia station a signal report.

As they say on Twitter, smh.
banjoplayinnerd: (Default)
I managed to get my Montana contact, without having to do it through the countest. I had a contact with a guy from Hamilton, Montana the other day. If I think hard enough I might be able to remember where that is. I'm sure I knew once when I lived in Billings. (UPDATE: Yeah, I thought so. It's in the valley south of Missoula where my wife spent several years of her childhood.)

Then this afternoon I had a brief contact with a station in Australia. So much for being confined to contacts in California. Actually I currently have contacts with about half of the states and six "countries," but that doesn't stop me from being insecure about my ability to get my signal out.One thing about hams, we always want better antennas.

I've mentioned JT65 before, where the contacts are pretty minimal. That means I don't know much about the people I contact unless I look it up on the net, but JT65 still has its advantages apart from brevity and the ability to make contacts in rapid succession. When I send out a transmission there's usually about 90 seconds before I have to react to any reply that comes my way, and the reaction usually consists of clicking a radio button or typing a brief (10 characters) message, so I have time to do things like practice my banjo or work on the low whistle (which is coming along better than it was, but it's still not as natural as the recorder). You can bet that when the Australian station called me I was paying my full attention to him, though.
banjoplayinnerd: (Default)
Well, the Montana QSO party was a bust. I never heard one station participating in the contest all weekend. Due to the nature of how radio waves travel, this isn't necessarily unexpected, I was just hoping for better. On the other hand I did contact several other new states and one District. (There are less than 500 hams in DC, which in theory makes it three times as rare as North Dakota, the state with the lowest ham population. Under the Worked All States rules, though, DC counts as a Maryland contact. Hey, I don't make these rules up.)

When I say "new states," of course I mean "new this time around." I earned my Worked All States award back around 1979. The certificate is one of the things I wish I could find in the garage. I also worked all 50 states during one weekend in 1979, but I'll tell that story another time.
banjoplayinnerd: (Default)
So as I said in the previous post I missed out on South Africa. I got a consolation prize, though. This afternoon in rapid succession I got a contact into Hawaii, plus another one into Japan.

Under the somewhat arcane rules governing ham radio awards, Hawaii counts as both a state (for the Worked All States award) and as a country (for the DX Century Club, where you try to get contacts with hams in 100 different "countries.") Same with Alaska. This means that since March I've worked something like ten states and three countries. You'd think Canada and Alaska would be easy contacts, but I haven't managed to get them yet.

A quick word about countries: somewhere there's a definition of what constitutes a country for award purposes, but it's been a very long time since I've read it. The list includes over 300 entities, including such "countries" as the Isle of Man, Scotland, Wales, the Galapagos Islands, Asiatic Russia (as opposed to European Russia), St. Pierre et Miquelon, the naval base at Guantanamo Bay and the headquarters of the International Telecommunications Union in Geneva - as opposed to the United Nations headquarters in New York.

I earned my Worked All States (WAS) award the last time I was on the air for an extended period of time and got something like 45 countries toward DXCC. I want to try to get WAS again, and to get DXCC this time. Both are doable, but can be tricky. With DXCC, once you get past the countries with large, active ham populations - maybe 50 of them - you have to start digging for the rest.

Stateside, the tough part is working the states that have low numbers of hams. Wyoming comes to mind, as do both North and South Dakota. I remember reading recently that there are about 1500 hams in North Dakota, of which maybe 10% are active on the shortwave bands. So, now that this post is over I'm off to participate in something called the Montana QSO Party, where hams from Montana are encouraged to get on the air so the rest of us can contact them. When I earned my WAS, I was living in Montana, and for more than one ham I was their last state for WAS.

And one final note: Guess which states have the highest numbers of radio hams? California has the most, followed by Texas, Florida, and . . . for reasons unknown to me . . . Washington. Yeah, not too many people need me as their fiftieth state for WAS.
banjoplayinnerd: (Default)
I'm sure there will be other parts later, but this is today's story. Hopefully I can describe things so the non-hams in the audience will understand what's going on.

Yesterday my son invited us over for dinner, and I stuck around for a few minutes to help him with a computer problem. (Like many people who work in tech, I am the go-to guy for computer support for most of my family.) I got back home, read stories to the Igors, and decided to play a little radio before I went to bed.

I turned on the radio and tuned up to operate on the 40 meter band. 40 meters is an interesting band. During the day it's good for fairly short range communication, up to maybe 1000 miles. When the sun goes down if conditions are right you can get stations from a long way away. Sometimes that works to the hams' disadvantage, since parts of the band that hams in the Americas can use to communicate with each other are given over to high-power international broadcasters in the rest of the world. It can be hard to carry on a conversation when Radio Moscow is right next door, three times as loud as any of the hams. The situation is changing and broadcasters are moving out of the 40 meter band, which is a mixed blessing; if you could hear, say, Radio Moscow and knew it was broadcasting from a location in Kazakhstan, you would know that the band was open to that part of the world and you might be able to contact Central Asian hams in parts of the band available to them.

So there I was, just watching the readouts on the computer to see where the band was open. Several hams from the Midwest and South were talking to Latin American stations and a few East Coast stations were working Spain and England. Nothing out of the ordinary.

Soon after I saw this come up on the display:

ZS2ACP KR4RO R-19

"Hm," I thought. "ZS2? That sounds like a South African call." I did an Internet check and sure enough, ZS2ACP was listed as being in Port Elizabeth, South Africa. Lucky KR4RO, I thought, but I figured if I can't hear the Venezuelans people are working, there's no way I can hear South Africa, especially if his signal into KR4RO's area has a strength of -19. (Closer to 0 is higher, and -24 is generally considered about the minimum signal strength for a contact. Sort of like stellar magnitude, except -1 is the highest you can get.)

I went off to try to contact an Alaska station I heard calling CQ. I didn't get him. It was my own fault, I forgot to set the transmit frequency correctly. After I figured this out, the South African call sign came up again. This time he was talking to a ham with the call N3XX - most likely in the mid-Atlantic states, though I didn't check. Out of curiosity I stuck around, and after N3XX was done transmitting I saw a faint signal indicator on his frequency.

Naaah . . . it couldn't be. Could it?

N3XX ZS2ACP RRR

There it was, the South African acknowledging contact with N3XX! That was a surprise, to say the least. I don't think I ever heard a signal from that far away back when I had a really good 40 meter antenna in Montana. The software said he was just over 10,000 miles away. Wow!!

I stayed on frequency, listened to the two of them complete their QSO (two-way contact), and decided, just to see what would happen, I sent a contact request:

ZS2ACP WA7KPK CN87

I listened. No luck. The signal was gone. Oh well, it was worth a shot.

I tuned around the band for a while, looking for a contact. The band was moderately busy, which meant I was getting lost in the crowd a bit. Lots of strong nearby stations, but all of them talking to other people. I decided to try a slightly different tactic. Louder, nearby, more readable stations show up as bright patterns on the signal display. I started looking for fainter ones.

I found one faint, barely perceptible pattern and decided to listen in to see if the computer could decode the signal. Since each message in JT65a takes a minute to send and decode, I had to wait about 40 seconds for the readout. It appeared on the screen, and my jaw dropped.

CQ ZS2ACP KF26

The last thing in the world I expected was to hear the South African station calling CQ ("Anybody out there want to cntact me?"). South Africa is by no means a rare country, but it's unusual to hear it from North America on 40 meters, and when it happens you often get a "pileup" - a crush of signals from people like me, all wanting a contact.

So of course I called him back.

ZS2ACP WA7KPK CN87

No reply, which is what I expected. Again, his signal disappeared.

So I went back to listening for weak stations and found him again on a different part of the band, working someone in the Midwest. After the contact he called CQ again, and I answered again, but he was gone.

That's about the time I called it a night and started getting ready for bed. I figured calling him was worth a try, and I would have been pleasantly surprised if he'd replied, but if you got all the stations you called every time, what would be the fun in that?

Profile

banjoplayinnerd: (Default)
banjoplayinnerd

May 2014

S M T W T F S
    123
45678 910
111213141516 17
18192021222324
25262728293031

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 7th, 2025 12:47 am
Powered by Dreamwidth Studios