Learning the Code!

The hardware (and software)-free method.

Steve Katz WB2WIK/6

Not everyone wants to, or needs to learn the international code we often refer to as “Morse,” but if you would like to do so - whether to upgrade your ham ticket, or just for the fun of knowing something new, which is also the foundation of a very useful and inexpensive mode - maybe you can try my method. It's worked for an awful lot of people, and involves no investment in software, nor a computer, nor a CD-ROM nor tape cassette. It's a fun method that, in my experience, is more effective and faster than any other way to learn code. It also happens to be the way I learned, myself, about forty years ago. I've used and enjoyed CW operation ever since.

First, find a partner

Learning anything is easier when it's interactive. Listening to tapes or CDs, or playing with a computer program isn't really interactive, because the program cannot listen to your questions and answer them.

If you've ever tried to learn a foreign language on your own, simply by reading books and listening to tapes (or whatever), you know how difficult that really is. It's frustrating, but mostly it's boring. One has to be very motivated to learn a new language on his own. If, on the other hand, you've ever taken foreign language classes with an instructor and other students, you know how relatively easy that is.

The best foreign language classes are those where the instructor never uses your native language at all. He or she starts right out using only the “new” language - the one you want to learn. They'll introduce themselves in that language, and then ask your name, and you answer by providing a partial sentence in the new language, followed by your name. Thus, usually, in the first five minutes, you're already speaking the new language - even if you don't know what you're saying! This is the way language has been effectively taught in classrooms for hundreds of years, and it's very effective - that's why teachers are still using this method. The best part, and the part that keeps it interesting for students, is that it's interactive. You are part of the action right from the start.

Take two language students: One who uses computer programs, books and tapes, and another who attends real, interactive classroom instruction - and see who knows more of the new language six months later.

It's the same way with the code. You could learn it on your own. But it's a lot more fun if you learn it with a friend. Here's my very old-fashioned, but very effective method: Find a friend who is also interested in learning the code. Get together if possible; otherwise, this could be done on the telephone, or on the air if you already have some ham privileges (as Techs do, on the VHF bands), or even using VoIP on the internet, provided you're set up for that. But it's certainly more fun in person, as the interaction is full-duplex. That is, you can hear and see results instantly, and the other party can “break in” instantly if they need or want to. Plus, you get the whole body language thing going.

It takes no equipment of any sort to learn code; however, it does take at least a key to learn to send code. In my youth, I used both methods: The “hardware free” method, for practicing any-old-time, and the key-and-oscillator method to practice sending.

The hardware-free approach

Use your mouth and vocal chords to say the word, “dit.” Now, use them again, to say the word, “dah.” Now, say, “di-dah.” Then try, “dah-dit.” You've just now “sent” an E, a T, an A and an N in code, using nothing more than your mouth. You can do this anytime, anywhere, as long as you're not eating or drinking at the same moment as you're sending.

Photocopy a little practice chart showing the letters of the alphabet and the numerals 0 through 9 with the code symbols printed next to them. Everyone has a chart like this, somewhere. If you don't, download one from http://www.1728.com/morstest.htm

and when you make a copy of it, make it small enough that you can carry it around. It will be your handy reference for just a few days, and then you can throw it away - you'll never need it again.

A “dot” symbol is pronounced “dit” when you say it. A “dash” symbol is pronounced “dah.” Putting them together makes a “di-dah,” or a “dah-dit.” Making a letter V, which is three dots followed by a dash, is pronounced, “di-di-di-dah.” Got it? It's awfully easy.

You, too, can send code without a key, oscillator, or any equipment beyond that which you were born with.

Read your little code chart, and practice “sending” every letter, and then every number, using your mouth and your voice. Get your partner to do this, too. Spend a while doing it. You can “send” the whole alphabet and all the numbers several times this way inside half an hour. And, without paying any attention whatever, you'll be learning the code. Don't believe it? Trust me, you'll be learning it, even if you're not paying any attention.

When you get tired, stop. Arrange to get together with your partner again tomorrow, or the next day, or the next convenient time. But don't make it a month later, or you'll have to start all over again! Try to make your code practices convenient, but at least a few times each week. As with practicing anything, maintaining a consistent schedule aids practice a great deal. If at all possible, pick a time each day, even 30 minutes, and set it aside to get together with your partner and practice the code. In my youth, the time we picked was after school every day, at about 3:30pm, when I - and my friend - arrived home.

Practice makes good enough

Practice may eventually make perfect, but who cares? You needn't be perfect, you need to learn the code and have as much fun as possible doing so, to keep your interest up.

The next time you get together, whip out the little code charts and try sending something to each other. A favorite of mine was to “send” (by mouth!) the names of ball teams, like “Baltimore Orioles” or “New York Yankees.” Reason: My partner, who was also a baseball fan, would get 100% “copy” even if he only copied a few letters. His brain could fill in the blanks. This makes everyone more interested, because they're nearly guaranteed success right out of the gate.

Don't worry about code speed. “Send” as fast as you like. Actually, you'll be limited in your “sending” speed by only two things: Your ability to look up each letter and convert it to mouth-sent code, and your physical ability to pronounce the dits and dahs. If you get really good at this, as my friend and I did, you can “send” code about 20 words per minute, pretty soon. And that's a good speed. But it really doesn't matter. Don't sweat the small stuff.

The cool thing about learning and using code is that it doesn't matter if you get “100% copy,” ever. Even to pass the amateur exams, you need to accurately understand the context of what was sent, and perhaps scribble down a number or something unusual that's thrown in, but in general, understanding context alone is sufficient not only to pass the test, but also to operate on the air - for real!

In a life-or-death CW traffic handling emergency, which are very rare nowadays, 100% accurate copy may be important: Like the phone number of the nearest relative of a dying person. But how often will you come across such situations? Probably never. Forget about 100% copy, it just simply doesn't matter.

Look at it this way: When you chat with someone in person, or even on the telephone, do you write down everything they say? Heck, do you write down anything they say? Well, then why do it if you're using code? It's silly. My memory is quite sufficient for me to remember someone else's name, location and almost anything else he might tell me during the course of a five or ten-minute transmission. If I need to copy a telephone number, I'll write it down - just as I would if someone gave me a number in person. Or, maybe a street address. But for routine communications, there is no purpose served by writing anything down - it just slows the process, and makes code copy more difficult, as instead of understanding what the other party is sending, you can be tempted to simply write it, and then go back later to see what he sent. That's nuts.

Start out by “sending” familiar phrases and such. Keep it interesting. Keep “transmissions” brief, and then let your partner “send.”

Before long, you'll both be rattling away using code, initiating transmissions and decoding them, without writing anything down, and without thinking about the process. It comes naturally, if you let it.

My partner and I would sometimes walk to school together, since we lived only blocks apart, and when we did, during the first semester of eighth grade, we would “talk” only in code, by dit-dahing to each other. We'd dit-dah automobile license plates, street signs, billboards, anything we happened to see while walking. It was fun, and made the walk go that much faster - and it was even more fun if other kids happened onto us during the walk and couldn't begin to figure out what we were doing. Like using the secret decoder ring, without the ring.

As you can tell, I'm not a great believer in using “gimmicks” to learn the code. Learning the letter “D” by using the memory link “DOG did it” (dah di-dit) is silly because first you have to think of DOG, then you have to remember that means “D.” It takes a lot more time than simply learning “D” is dah di-dit. There are only 26 letters, ten numerals and four or five punctuation signs to know - maybe 41 characters in total, to convey every scrap of information on the planet to another code operator. That's too much to learn?

I'm also not a great believer in learning by study. So, I prefer to call all of this, “practice,” and not “study.” Don't set aside 30 minutes to study the code, set aside 30 minutes to practice it.

“Operating” without hardware and such

Have practice QSOs using the di-dah method. Learn what adequate spacing is, between characters (letters, numerals) and also between words.

Reasonable spacing between characters is about the equivalent of one “dah,” i.e., if you want to send the word “thusly:”

Sent Spacing until next character sent

Dah (space of same length as the dah)

Didididit (space same length as a dah)

Dididah (same space as a dah)

Dididit (same space as a dah)

Didahdidit (same space as a dah)

Dahdidahdah (same space as a dah)

The time space occupied by one dah is about the same as three dits. Thus, it takes about the same time to send “S” (dididit) as it does to send “T” (dah).

Reasonable spacing between words is longer. If it weren't, you wouldn't be able to tell where one word ended and another began. I use word spacing of about 3x character spacing, although there's no firm and fast rule for this. It just seems natural to do so, and makes for clearly sent code that almost anybody can copy.

Punctuation

The FCC/VE code test includes only a few punctuation marks or signals. It's important to know a period (didahdidahdidah), a comma (dahdahdididahdah), a question mark (dididahdahdidit) and a “slant bar,” (/) which is frequently used to indicate a portable, mobile or temporary operation and is (dahdididahdit).

Code operators use a lot of prosigns and abbreviations, and often use punctuation to indicate a break in the stream of thinking, or to change subjects. In a verbal conversation, you might say, “Oh, by the way...” or “to change the subject...” but using code, all those words would waste a lot of time and add nothing to the conversation. It's common for code ops to use a double dash (dahdidididah) to indicate a “break” in almost anything. When you hear this, don't bother writing it down! (You know, I don't believe much in writing down anything when using the code or operating CW.) It just indicates a break in thoughts, and is a bit less “formal” then sending a period. While good sentence structure dictates the rather frequent use of commas, when operating CW we don't use very many of those, either. There's really no reason to, unless the statement just screams for their use. Most punctuation is just a waste of dits and dahs, although to distinguish a question from a statement, the use of a question mark (dididahdahdidit) is quite common.

Prosigns are “made up” shortcuts using combinations of letters, or sometimes even a single letter, having a meaning specific to using code. A quick and dirty (and easy!) prosign is the letter “K,” which means, “go ahead and transmit,” and is found at the end of most transmissions when one station turns it over to another. There are dozens of prosigns, and you needn't know them all - in fact, you really needn't know any of them, although you'll come off as a better operator if you do. They're listed in the ARRL Handbook, the ARRL Operating Manual, at the end of all ARRL Logbooks, and many other places.

So are amateur radio “Q codes,” which are three-letter abbreviations that can be either statements (when followed by nothing) or questions (when followed by a question mark), all beginning with the letter Q. If you're already a ham, you should know some of the popular ones like “QSL” and “QTH.” There are many less popular ones. Take a look at them and see which ones you like. You're under no obligation to use any of them, but understanding the meanings of the most popular ones helps a great deal and saves time looking them up. (You do understand that “QTH” means “my location is,” while “QTH?” means “what is your location?” don't you? Seems obvious to me, but many newbies get bamboozled by the Q code followed by a question mark.)

A good Q-code list may be downloaded from http://members.shaw.ca/bikeal/ham_qc.html

If you understand the full meaning of a Q code, you can save a lot of time sending superfluous stuff. Example: Since “QTH” means “my location is...” there is absolutely no reason to send “QTH here is Wichita.” The words “here is” are superfluous, irrelevant and just plain a waste of dits and dahs. The code “QTH” already includes all that stuff, no reason to repeat it. A better method of sending your station location would be, “QTH Wichita, KS.” That's quite sufficient.

We use a lot of abbreviations and shortcuts, too, and most good (experienced) CW operators make up their own as they go along. No need to send “my name is Steve,” when “op Steve” tells the same story and wastes a lot less time. Instead of “my rig here is a Kenwood TS-2000,” just send “rig KW TS2000.” That's quite enough, and everybody will understand.

As you're dit-dahing your partner, start using shortcuts and abbreviations as soon as you want to - the sooner, the better, as they convey more information in less time and everybody uses them.

Real life story

My nephew Rob became interested in ham radio at the age of eight, because he lived with me (and my wife, who's his aunt) for a few years and saw me operating my station at home. Although he listened in to the “phone” contacts, he was clearly even more interested in my working CW. It was mysterious, and he didn't understand it, but he knew I was somehow “talking” with people, and just had to figure all this out.

Now, Rob has Cerebral Palsy and wasn't so well coordinated. His mind worked fine, but his body didn't always follow. So, much as he liked sports, and followed NBA basketball, he wasn't going to be an athlete. But he was an excellent fan. I told him that working CW meant learning the international (Morse) code, which, by the way, was so simple that many six year-olds have mastered it. (I just made that part up. It made the possibility of learning code that much more enticing for an 8 year-old.)

I gave him the little code chart with the dots and dashes, and off we went. I used my electronic keyer with its built-in sidetone and speaker, cranked it down to about 10 wpm, and started sending to him. “Los Angeles Lakers.” “Seattle Supersonics.” “Portland Trailblazers.” Before long, I'd get about halfway through the city name, and Rob would blurt out the name of their NBA basketball team. “New Yor....” and Rob would shout, “KNICKS!” It was just that easy for an 8 year-old.

Of course, Rob had one huge advantage: Nobody ever told him that learning the code would be difficult. In fact, I had told him just the opposite: Six year-olds learned it, and half of them were GIRLS. With that incentive, he had to not only master it, but do it better than the girls could, whoever they were.

A few days after his ninth birthday, Rob passed his Novice exam and became KD6EWT. By his eleventh birthday, Rob passed his Extra (the old 20 wpm one) and became AJ6E. He is quite the CW operator. Unfortunately, Rob went off to college and let his ticket lapse, but under the current rules, he could get AJ6E back, and now that he's graduated and has a place of his own (with his ladyfriend), I'm encouraging him to get back in. I'm sure he will. Especially if I loan him a rig!

Anyway, this story is true and Rob is exactly like every other kid I've ever taught the code: Picked it up instantly and without hesitation or complaint, because nobody ever told him it was hard. It was just another thing to learn, and kids learn new things every day.

It's not only receiving

Sending code is important, too. You may be able to pass the exam by only demonstrating the ability to “copy” code, but you can't make any contacts that way. Well, that's not quite true, anymore. Now, using computers and software, you actually can make CW contacts without knowing anything about sending code! But it wasn't always that way, and I think to truly enjoy using the code, learning how to send it is an important element. It's part of the “Art and Skill of Radiotelegraphy.” To work CW without knowing how to handle a key is like collecting old cars without ever getting your hands dirty.

So, although it's entirely possible to become quite proficient at code without any hardware at all, I do recommend at least a hand key and code practice oscillator. That “pair,” together, are available brand-new from MFJ for an Andrew Jackson or so. I've also seen them at swap meets and garage sales for much less. And, every time I see a pair like this for $5 or $10, I buy it, and then give it away to any local aspiring ham who wants it.

Learn how to handle the key and send with it, clearly. Experiment with hand, finger and arm positions to see what's comfortable for you. Usually, what's most comfortable is to push the key away from your body until it's as far back on a desk or table as your hand would naturally fall if you lay your forearm on the table, with your elbow a few inches in from the nearest edge. For an average man, that means the key should be 16-18” back from the front edge of the desk or table. For a woman or child, maybe a bit closer. Sending code should not be tiring.

If you ever become serious about actually using the code to make contacts, you won't be using a hand key very long, anyway. A hand key can't send good code fast enough to be serious, and you'll want to graduate to a keyer soon enough.

Factoid: If you can really copy code, which means you can understand what's being sent, it won't matter what the tone, frequency or pitch of the code is: As long as it's within your hearing range, you'll get it. Don't even ask or worry about this, it just doesn't matter. Just like “writing it down” doesn't matter. If you can copy code in your head, which is far more useful than learning only how to write it down, you will be able to write it down, also - if you ever want to. You'll find that most of the time, you won't want to, because it just isn't necessary.

(My nephew Rob, who passed his 20 wpm Extra when he was eleven, didn't write a thing down on his code test paper, other than his name. After all the code had been sent, he then filled in the answers to the questions. He was done about a minute after the code sending was finished. The examiner actually proclaimed, “Gosh darn, that's the first time I ever saw anyone do that.” I was there, and replied, “This is probably the first time you've seen anyone take the test who actually learned how to copy code the proper way.”)

Let the good times roll

If you practice with a partner, use the “dit-dah” method, and convince yourself that code is the easiest darned thing anyone could possibly learn...you'll be there, very quickly.

Secret: I taught code classes for many years, in junior high schools, high schools, adult schools, and more than a few ham radio club sessions, and always used the “no hardware/no software” method described here. Although a few students dropped out for various reasons, everyone who didn't drop out finished the class able to solidly copy 20 words per minute, after about four weeks of classes. And I mean everyone. Make it fun, keep it fun, don't get too scientific about it. Code operators have used Morse or similar code for one hundred fifty years now, before wireless communications existed. We're still using it. It goes way back before all the “methods” that amateurs have latched onto. Originally, most guys learned code as a way to make a living, handling messages for Western Union via telegraphy clackers. It paid well, and men - and some women - stood in lines, waiting to enroll.

Finally

I really don't care if the code requirement is eliminated from amateur licensing. I think the hobby will survive either way. But I'll keep using CW, because it's fun, efficient, and relaxing. Yes, relaxing. And quiet. Very quiet. I can operate CW all night long, using headphones and my very quiet keyer paddle, and people sitting in the same room don't even know I'm on the air, making contacts. I can do that using digital modes, too, but that requires a computer. After staring at a computer screen all day long, the last thing I want to stare at when I get home from the office is another computer screen...

73!

WB2WIK/6