SARC Events


SARC Events


FoxHunt
Video
SARC Courses
Course Information
Field Day
Video
Showing posts with label CW. Show all posts
Showing posts with label CW. Show all posts

2019-12-29

The SARC CW Course


Morse Code Is Not Dead!

CW – the Original (and arguably, the best) Digital Mode

Invented in 1837, CW which is more commonly known as “Morse Code”, was the very first mode of communication sent over a wire or airwaves.  It is called CW or “continuous wave” because it is an unmodulated radio wave of constant amplitude, though it might more accurately be called “discontinuous wave” since the wave is broken into short and long segments separated by spaces, to represent letters of the alphabet, numbers and punctuation marks.  It is legitimately a digital mode because it exists in only 2 states  –“on” or “off”.

The length of the dot (or “dit” as we prefer to say) and dash (or dah)  and the spacing between them is not arbitrary but has a fixed relationship.  If the relationship is not accurate, the quality of the CW will be recognized as “poor” and in extreme cases may be virtually unreadable.  While most CW heard nowadays is created by software and is therefore perfect, we occasionally hear on the radio less-than-perfect Morse Code, sent by operators still using a mechanical device such as hand key or bug.

Since CW has largely been abandoned by the commercial, military and transportation world, it is now virtually within the sole domain of amateur radio operators, whose passionate adherents will likely stand by it to the bitter end.  So, if you think CW is dying out, then listen on the 20 m band during one of the many CW contests throughout the year.  You will be amazed at the number of CW operators sending Morse Code at rates between a lazy 15 wpm and the a breakneck 50 wpm or more, from every corner of the world.  

If you wish to use radio to communicate by the most reliable and sensitive means, you will not use CW at all, but instead one of the modern “weak signal” digital modes such as FT8, JT65 and a whole slew of others,  which have transformed our ability to accurately copy signals which may be so weak that you cannot actually hear them.  This is a boon to communication as it allows information to be exchanged even when using low power transmitters and poor antennas – unavoidable for condo dwellers.  So these forms of digital certainly have their benefits.  

However, if you wish to enjoy amateur radio in the most traditional, challenging and enjoyable way, you will find CW is the method of choice.   Yes, you can deploy digital decoders to help you read CW on a computer monitor, and many do.  However, even the best digital decoders are inferior to your ears and brain working together.  So if you are serious about using CW, you really must learn to copy it by ear.  

As a beginner, you will likely start with a hand key to send the characters which require a separate wrist movement for each dit and each dah.   In the past, CW operators would typically graduate to a semi-automatic key called a “bug” which sends a series of dits when the paddle is pushed one way, but single dahs when pushed the other way.  That certainly takes some of the work out of sending.  Actually very few CW operators now use a bug although the holdouts can still be heard on the airwaves.  

CW sent by a hand key or bug is usually distinctive of the operator and can often be recognized in the same way that a person’s individual handwriting differs from that of others.   During WW 2 the identity of German and British radio operators could often be recognized by their “fist” i.e. individual way of sending code characters.   



Hand key

  
Semi-mechanical Vibroplex “bug”

Nowadays, 95% of CW operators use a paddle and electronic keyer to send CW.  This combination is a big step up from the hand key and bug because it allows sending virtually perfect CW, which means the dits and dahs are of the correct length and spacing.  The keyer can be a separate unit into which you plug your paddle or, more commonly, it is built into the transceiver.  You push the paddle one way and it makes a string of dits; push it the opposite way and it makes a string of dahs.   It is not difficult to master and the result is uniform and perfectly formed CW.


Kent paddle



Bencher paddle



Electronic keyer with built-in paddle



External Electronic keyer which requires a separate paddle

You may occasionally hear about “iambic keying” which allows the keyer to minimize the keystrokes or hand movements even further.  To visualize how it works, consider the letter “C” which can be sent iambically by merely squeezing the two paddles together. With a single-paddle or non-iambic keyer, the hand motion would require alternating four times for C (dah-dit-dah-dit).  Most CW operators have not mastered this technique and it is not recommended for beginners.

If you’re stuck in a rut and looking for a new and challenging experience, consider learning CW.  Persistence and practice will get you through in the end and you will be ready to join the select group of hams known as “CWers”.  I heartily recommend it.

~John VA7XB







2019-11-17

Morse (CW) Teaching Software


A Variety Of Apps To Help You Learn Morse Code


We are offering a Morse Code class starting January 20, 2020


In the meantime, there are now a wide variety of apps and programs to assist you in learning CW.


Morse Toad  is an app that teaches Morse code through a series of simple lessons and exercises. Based on the proven Koch method, letters are learned one at a time, at full speed, and when the player demonstrates their mastery of the new letter, another is added until the full alphabet is learned. The Apple iOS version is shown but Android is also available. This is the one I’ve had the most success with refreshing my rusty CW, though the interface looks a bit old school.

WinMorse My choice for Windows computers. Convert text into Morse code. It does this by reading text from one of three sources: the Windows clipboard, a file, or you may directly type the text. WinMorse outputs the Morse code as a standard windows wav file.

MorseCat A freeware windows Morse code trainer for beginners and experts by DK5CI.

Code Quick Master Code In 30 Days it says... Maybe.

Super Morse Super Morse is the original comprehensive Morse Code training program for the PC. Super Morse permits the user to learn the Morse characters in a very orderly way using several different methods, including one unique to Super Morse; build speed with special exercises.

CWT a Morse code learning program for MSDOS by DK5LI.

CW Player Simple freeware program generates Morse characters and Q codes. It needs a sound card and Win95.

Morse99 the industry standard Morse code tutorial for pilots in the UK. Fully windows compatible with sound card support.

Ham University Ham University includes Morse Code lessons, graded exercises, and a game.

Morse Code Morse Code Training, Practice and Exam Program by Stormy Weather SoftWare Ltd.

RufzXP RufzXP is a free training software for improving code speed and CW practice, particularly (ultra) high speed memory copying of true amateur radio calls.

Morse Academy Online documentation and overview about Morse Academy, shareware CW learning software.

Codemaster V Reputation as the Morse code training package for either the newcomer to Morse code, or the experienced user who wants to improve his or her receiving skills.

Morse Pilot Morse Pilot is a popular and very comprehensive freeware Morse code tutor, trainer with decoder and encoder functions. Morse Pilot is intended for personal training, for example for radio ham or aviation examinations.

MorseRunner (Contest simulation with N1MM logger) Teaches and simulates CW contacts in a contest environment including noise, band conditions and various operating speeds.

Koch Method CW Trainer Based on the Koch Method as described by David G. Finley, N1IRZ, this software allows you to start out at the full speed you want to achieve by learning two letters and adding an additional letter once you reach 90% proficiency.

You may also want to checkout this blog post by Wayne K5UNX about learning CW https://www.amateurradio.com/cw-part-3/ 

You can get free online lessons and exercises at https://lcwo.net/ 


And, here from Norway, good reasons to learn CW

Morse code is no longer a requirement to acquire an amateur license here in Norway. The same is true for many (or most?) other countries. Still Morse code, or CW – continuous wave as it is often referred to as, has great value. Here are my top five reasons why I am learning Morse code.

1 – Excellent propagation
Voices are long gone and all you hear is static. Tune down to the lower end of the band and you will probably still hear dah-di-dah-dit dah-dah-di-dah. When “the bands are dead” as they say, the one thing you can still hear is CW. The propagation abilities are extreme.

2 – Power efficiency
Since all the radiated energy is concentrated in one single tone, morse code is an efficient form of communication with regards to power. This means that morse code is good for QRP use, or even QRPP. Also you do not need equipment that can handle large amounts of power. Thin wires and small components are enough to be heard around the globe.

3 – Easy to build kits
Small currents and simple signals do not need as advanced circuits as single sideband or FM do. There are several circuit diagrams and kits available to build, and many choose to design their own transceivers.

4 – Ultra portable transceivers
Morse code is great for SOTA and outdoor use. Small form factor kit transceivers kan fit in a small tin or plastic box, and other commercial lightweight CW only transceivers are available. When you need to bring other equipment like your tent, sleeping bag, clothing and food it is nice to bring a transceiver that does not add significant bulk and weight to the backpack.

5 – Easy way to get on the air for non-talkers
Many of us are the non-talking kind of person. I do enjoy an occasional rag-chew now and then, especially on the local 80 m net, but for now I prefer the “exchange vital information and move on” kind of style. It seems there are more of this kind of QSOs with CW.

6 – Awesome-factor

Bonus reason: Morse code has this nerdy awesome-factor to it. Morse code is something everyone recognize, but not many understand it. It truly is impressive to watch someone perform high speed CW.

~ John VE7TI







2019-10-31

November Contests


Spend some quality time on the radio!


By the time you read this, October will be over and the California QSO party, the Oceania DX contests (both phone and CW versions), and the CQ Worldwide SSB DX contests will be part of contest history for 2019. I hope most of you gave at least a couple of these a try. We’re on the bottom of the sunspot cycle, so it could be “now or never” for DX contests for most of us.

Incidentally for those of you who haven’t already discovered them, the ARRL Propagation bulletins can be found archived here: http://www.arrl.org/w1aw-bulletins-archive-propagation

And while we’re on the topic, the best propagation forecasting software I’m aware of (and free, at that) can be found here:  http://www.voacap.com

Have a look at the site carefully so you don’t miss the point-to-point propagation predictions, the coverage area maps, and the Nordic-based HF propagation-monitoring cluster. Although the spots for the monitoring cluster are CW, they show where signals received at the monitoring cluster are originating from, in real-time, and the summary at the top of the page shows the number of spots per band, which gives a fair idea of which bands are open at the monitoring location.

November starts out fairly quietly as far as high-profile contests go, but
  • CW: First full weekend in November (November 2-4, 2019).
  • Phone: Third full weekend in November (November 16-18, 2019).
Contest Period: Begins 2100 UTC Saturday and runs through 0259 Monday. (all dates and times UTC).  This contest has a wonderfully challenging exchange that is great for testing (or proving) your skills. Full information can be found here: http://www.arrl.org/sweepstakes

Be sure you read the exchange requirements carefully!

Between the two versions of the Sweepstakes we have the RTTY version of the Worked All Europe DX Contest. This could be challenging without a good antenna and an amplifier. An interesting feature of this contest is the QTC Traffic bonus points. If you find RTTY boring, or consider yourself an RTTY expert, this is the contest for you. Figuring out how to get your contest logging program to send QTCs to other stations will get your brain cells revved up, and actually managing the process will keep you on your toes in the contest. 

If you aren’t up to sending the QTCs, note that they are optional, so you can still do the contest in a mindless, er, I mean simplified way.

And for microphone aficionados with better-equipped stations, there is a phone contest the  2nd full weekend of November  2019-11-09 0700 - 2019-11-10 1300 UTC  the JIDX Phone Contest. Even if you find yourself with an embarrassingly simple station, Japan is probably the easiest DX we can get from the west coast, and all it costs to try is some time at a radio, so you don’t have anything to lose by giving it a shot. You can find the rules here:  http://www.jidx.org/jidxrule-e.html

For CW operators, November wraps up (November 23-24) with a biggie, and well worth the wait: the CQ Worldwide DX contest. Multipliers by the dozen (CQ zones and countries, per band), and suitable for all stations, big or small. While contacts with our own county don’t count for points (just multipliers), from our location it’s easy to get contacts with the US, for two points each. Starts 00:00:00 UTC Saturday Ends 23:59:59 UTC Sunday The exchange is simple (RST plus CQ zone), so if you love to pound brass, this one is for you! You can find the rules here: https://www.cqww.com/rules.htm

As always, for regular mid-week contest practice, CW contesters have the CWops Weekly Mini-CWT test (http://www.cwops.org/cwt.html) and SSB enthusiasts have the Phone Fray (http://www.perluma.com/Phone_Fray_Contest_Rules.pdf). The SEPAR Tuesday night 2-m net is now starting at 19:15 (PT), which makes it easier to check into the SEPAR net and then jump over to the HF bands for the Phone Fray. The Phone Fray is an easy contest for anyone with HF SSB capabilities, so be sure to give it a shot. (We need some more local action, hint, hint).

As always, you can find a list of most of the latest contests from the (customizable) WA7BNM contest calendar (http://www.hornucopia.com/contestcal/index.html), and by checking the monthly ARRL “Contest Corral” lists (http://www.arrl.org/contest-calendar).

73 & GL in the contests!


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

Great Tips…

~ John K3TN





2019-08-15

A Simple Touch 'Code' Keyer


An Inexpensive Circuit With An IC And A Few Parts

Imagine tapping the table to generate Morse Code! This simple code practice oscillator is for those who want to practice Morse Code in a different way, without the Morse key. It can be also used as a touch operated door bell.

The popular timer IC555 is wired as astable multi-vibrator. The frequency (tone) can be changed by varying the 100 K variable resistor between pin 7 and 6 of timer IC555. The volume can be changed by varying the 10 K variable resistor and the sensitivity of touch plate can be controlled by adjusting the 1 K Ohms preset at pin 4 of IC555.


The touch plate is connected to the base of transistor BC147B. In this circuit the length of wire between the base of the transistor and the touch plate is not critical. Typical is a 9 cm wire and a 3 x 6 cm 3mm thick aluminum plate. The addition of a relay or additional circuitry could key your transceiver.




2019-05-26

So You Want To Learn CW III


A Communicator Reprise: Part 3


Last month we had the first of three parts of an article on Learning to Send CW. In this post we conclude the series.


Improving Your Fist

Once you have done enough practice with your paddles to be able to be comfortable with them, you will want to set the keyer speed to 15 wpm (if it isn’t there already). The faster rate of characters will force you to recognize characters at the 15 wpm rate. This is the first step to getting your code sending speed up. 

Certainly at the 15 wpm rate you are likely to make many more errors than you have been used to. Don’t slip back, however: continue sending each character at 15 wpm, but allow more time between characters so you are able to focus on making correct single characters only.

As you continue over future sessions you should find that you are able to allow somewhat less space between characters. Continue, for now, allowing extended space between words. 

Gradually, you will find that certain character strings (e.g. “ing”, “the”, etc.) occur repeatedly, and you are able to send the sequence almost as if it were a single unit. This is the time to become concerned about inter-character spacing. I find fldigi to be a very useful tool for decoding CW, and like to use it to help develop correct inter-character spacing. (http://www.w1hkj.com/Fldigi.html) The program is free and has versions available for Windows, Mac OS X and Linux. 

After installing the program, connect an inexpensive microphone to the microphone port on your computer. If your computer doesn’t have a microphone port, but does have a built-in microphone (common with modern laptops) you will have to try to put the speaker from your code practice oscillator near the built-in microphone.

Configure fldigi to take its input from your computer microphone port. Set fldigi in CW mode (under Op Mode on the tool bar) and start sending CW for about 10 seconds. Now look on the waterfall display (bottom of window) and position the marker with the red lines so it spans the line running down the display, which will be at the frequency of your code practice oscillator. Now send some more code and you should start to see some characters in the upper yellow display (the receive window). If any of this is unclear, refer to the program documentation.

If you have things set up correctly, the characters in the yellow display should bear some resemblance to what you intended to send. If in doubt, try sending a series of “V”s with extended spacing. You should see a series of “V”s on the screen. If you have additional noise (garbage characters) showing up, refer to the program documentation to turn on and set a squelch level that permits decoding of only your sending (not background noise).
When you are convinced this is working correctly, start sending from your reference (book, newspaper, etc.). Send with extra inter-character spacing in the beginning. If you are forming your characters correctly, the correct character sequence will appear on the fldigi display. Once you have this working, now move to your usual sending rate but with extra spacing between the words.

Examine the characters showing up on the screen to see if they still match what you intended to send. Likely you will have some which will be incorrect, not because you sent the wrong character, but because you ran two or more characters together. You can experiment with this by sending the word “the” with accentuated inter-character spacing, and then reducing the inter-character spacing. When the spacing is adequate (or too much), there should be a clear “t” “h” and “e”. If the spacing between the “t” and “h”, for example, becomes too small, fldigi will interpret the two as one character and display a “6”. When this occurs you can see your inter-character spacing is inadequate and work on improving it to the point where the “t” and “h” are immediately adjacent, with no intervening spaces, but not run together as a “6”.

Continue, in this way, working on inter-character spacing for each successive word. You want each word to appear as a word with no extra internal spacing, and do not want any two characters to run together.

Once you have your inter-character spacing reliably correct, you can begin to reduce the inter-word spacing, as much as you are comfortable. If you find your words are running together, as shown by fldigi’s display, concentrate on adding just enough additional inter-word spacing until the words reliably appear as separate words on fldigi’s display.
You are now well on your way to developing a clean, understandable fist.


On-Air CW QSOs

When you are able to send code at an average rate of 10 wpm, you are ready for your first on-air CW QSO. This will be much harder than sending from a book, however, which is why you want to reach 10 wpm from a book before starting on-air.

As mentioned earlier, there are four steps in sending CW, and the techniques given to this point address only the last step. It is now time to address the first three steps: 1) What to say (the idea to be conveyed); 2) How to say it (the choice of words and syntax); and 3) How to spell the words. The pressure of a live QSO will make all four steps harder, but in particular, the pressure on you to address the first three steps in “real time” will force you to improve your CW skills the most.

When you begin to practice CW on the air, enlist friends who are at your level, or somewhat beyond, to join you for regular on-air rag-chews. There is no substitute for working together with at least one other person. Ideally, that person will be a non-critical partner who is developing their skills just as you are developing your skills. (Hence the desire of the SARC executive to have an active CW Interest Group.)

As you listen to the CW bands, you will often hear casual “HI, HOW COPY?” type short contacts, which follow a scripted series of exchanges: call signs, signal reports (RST), operator names, QTHs, and transceiver and antennas used at both ends. Then come the local weather reports if both parties wish to continue. After that it’s some variant of “TNX FER FB QSO ES 73” (CW-speak for “thanks for the contact, best wishes”). 

In this kind of contact you can write down the appropriate responses on a cue card and work your way down the list, much like sending from a book. To a large extent, you can even pre-program the responses in a memory keyer (as is commonly done for PSK31 contacts). But not with a rag-chew.

Just as is the case when in casual conversation, in a rag-chew your brain is forced to work on each of the four steps simultaneously. Just as chatting with someone you’ve just met at a party is a test of your conversational skills, rag-chewing is a real test of your CW skills. You are forced to think on the fly, in real time, and hope to avoid sounding like a total fool.  This is a critical step in the process of developing your CW skills.

It doesn’t matter for our purposes whether or not you are a natural rag-chewer. I, for example, would never engage in a rag-chew on SSB, but on CW I’m looking for the practice in the four steps of sending, and particularly the first three. When you are able to rag-chew in CW, freely sending whatever comes in to your head (with, we hope, some judgment applied), and have it come out in crystal clear, perfectly timed CW, you have arrived! (In case you are wondering, I’m no-where near that point yet, but I greatly admire those I hear doing just that a few kHz down the band.)

In your rag-chews, don’t worry if you think you don’t have anything to say. To simplify Step 1, I started by jotting down some notes before the scheduled QSO on the topics I would discuss. If necessary, describe the weather in some detail (but in your own words), or describe what you did since getting up in the morning. Describe the room you are sending from. Describe the clothes you are wearing. Detail what you had for your last meal, and why you chose that. It really doesn’t matter what you send, since you are practising sending, and your partner (one at a time for now; working several in the same QSO is harder and should be left for later) is practising receiving. Don’t send for longer than 60 seconds at a time before you go over to your partner to take a turn. 


Here are some tips for your on-air CW practice

Learn the basic structure, abbreviations, and pro-signs of standard CW QSOs. One basic reference is http://naqcc.info/cw_qsos.html.

As with any on-air activity, before starting make sure the frequency isn’t already in use, first by listening, and then by calling “QRL?”. Wait, still listening, and then about five seconds later (when anyone on frequency has had a chance to respond) again send “QRL? DE Your Call”. If there is still no answer, the frequency is yours.

Try to keep your individual transmissions short so you can develop a conversational style between you and your partner. Ideally you’ll get to the point where one of you will be able to ask the other a question and get a quick-turnaround answer, just as you would on a telephone.

At this stage of your skill development, send “KN” rather than “K” after each transmission, which indicates to other CW ops who might be listening that you don’t want other participants. (This won’t guarantee you don’t get other people calling you, but it will help. And be sure you understand this rule yourself so you don’t butt in uninvited on someone else’s QSO.)

The regulations in Canada require you to send your call sign at the start and end of a QSO, and every half-hour in between. So for short fast interchanges you can use “<BK>”, without signing, to invite your QSO partner to come back, and your partner can do the same with you. Just remember that, if you go beyond 30 minutes, you’ll each need to sign with your call, followed by “KN”. And don’t forget to sign again at the end of the QSO.
Unfortunately, my fingers sometimes keep sending when my brain gets busy trying to think of what to say next (Step 1), and so has stopped feeding them correctly spelled words (Steps 2 & 3). This is about as useful as the random characters that show up on your RTTY receive screen when listening between transmissions, and it can be very confusing to the other party in the QSO. Instead, train your fingers to send “<BT>” (the pro-sign for “ummmm”) when your brain is overloaded.

Sometimes you want your QSO partner to stand by for a short period of time while you “get your act together”. When this happens, send “<AS>”, the pro-sign for “hang tough buddy”. (Just don’t get so wrapped up in something else that you forget to go back to them.)

Sometimes my brain is so busy trying to select words and syntax for the part of the thought I haven’t started sending yet (Steps 2 & 3) that I leave out a few key words (or characters in words) in the part I’m sending. That can be embarrassing if the missing words or characters result in my message conveying a meaning quite different from my intention. Just as, when copying CW, you “copy behind”, when sending you “send behind”. We talk that way also, but after years of practice they seem to happen simultaneously and effortlessly. This is still difficult for me when sending CW, but I believe the solution is to relax and slow down, sending what I have already formulated and then sending a few “<BT>”s until I know what I want to say next.

Sometimes I forget how to spell words longer than five characters (Step 3) because my brain is juggling Steps 1 & 2. Like many of us, I spell by putting a word on paper and then fixing it when I recognize it doesn’t “look right”. Unfortunately, that doesn’t work with CW (although the CW text display on my Elecraft radios helps me see what I’ve just sent, which isn’t always what I planned). One way to address this is to learn the standard CW abbreviations for longer words (like “tomorrow”). This also speeds up the flow of conversation. For example, by the time a QSO-partner has sent “tomo” I can fill in the rest without listening, unless they are about to use the one other word my dictionary shows that starts with those characters, “tomography”, a word which doesn’t turn up often in my QSOs. Better to send just the CW abbreviation “TMW”. Abbreviations are good, if used properly.

In my experience, and that of a friend who is at about the same level of experience as I am, a form of Farnsworth keying, where the characters and words are sent at a higher rate and longer spacing is used between words, is easier to copy for developing CW ops. This is particularly true when you reach the level where you are copying the received code in your head, without pencil and paper.


Becoming Comfortable

With practice and familiarity, you will gradually gain comfort with CW rag-chews, and that will greatly improve your CW sending skills. Originally I would only work people I know. Then I found myself getting calls from people I’d never heard of but who wanted to work me (for whatever reason) while I was trying to contact my first regular on-air partner, Jay VE7KC, for our scheduled daily QSO.

Initially I felt uncomfortable using CW with someone I didn’t know, so I would try to politely explain I’m trying to make a sked with a friend, so couldn’t chat with them at that time. I’d give them a quick signal report and perhaps name exchange, say 73, and go back to calling Jay.

As time went on, occasionally strangers would break into our conversations (despite our use of KN). Often I’d let Jay, or later Deme VE7CRT and Jay, carry on the conversation with the stranger. I’d just sit and listen. But as my comfort with on-air CW has improved, I’m now finding that I am as likely as any of us to reply to the ham trying to break in, and do the initial RST, QTH, name exchange.

As mentioned earlier, there is no substitute for working with a friend when you begin. I started this way with Jay, VE7KC. Looking back in my (paper) log, I find that my first attempted QSO with Jay (when he was VE7OFH) was 6 May 2013. Initially we had a lot of trouble trying to work NVIS between our two physically close locations. My log shows those (initially, many futile) attempts until we learned the tricks of reliable NVIS. I strongly recommend keeping a paper log of your first CW QSOs as a record you can easily browse later.

My log also shows that on 10 January 2014 we added another friend (Deme, VE7CRT) to our regular QSOs. Lately we’ve added another ‘semi-regular’, Walt, VE7BGJ, who is often heard checking into our weekly SARC 2m net. And on occasion, hams we don’t know but who hear the QSO and just want to stop in and say “hi” join us for a visit. It has become fairly common, now, to have a four-way QSO going. 

And as this has developed, the continuing experience has helped both Jay VE7KC and I become much more comfortable letting the words and ideas flow freely from our “fists”. For my part, I no longer have to make notes to get through Step 1. Mostly I can manage Step 2 in real time. And I’m working on Step 3, with the help of strategic abbreviations (and occasional re-wordings!).

Good luck in your journey toward comfortable CW QSOs.

2019-05-19

So You Want To Learn CW II



A Communicator Reprise: Part 2


On 2019-04-12 we published an article on learning to copy CW (Morse Code). At that time we committed to following up with another article on learning to send CW.


Like the first article, this one is based on recent personal experience. The methods and tips that have been working for me may not work for everyone, but they will give a committed learner a place to start, with the knowledge that these methods have worked for at least one other person.

The methods described in this article are ones I used to become comfortable in daily CW QSOs with old friends and a few new friends. These “rag chews” normally last from 30-45 minutes and are at a speed of around 18-20 words per minute (wpm).  
This article will not prepare you to participate in CW traffic nets. Nor will it prepare you to work CW contests without using a computer or CW memory keyer to do the sending. But these are things you can grow into, if you choose, after developing the basic sending skills that are addressed in this article.


What You Need to Know Before You Start


Just as you can’t sing “Auld Lang Syne” if you don’t know the tune, it is essential to know the sound of good CW in order to send clear, readable code. 

Practice at copying good code is thus critical preparation for learning to send. If you have not yet learned to recognize well-formed, well-spaced words in CW, put this article aside until you have had more practice listening.

The minimum useful character speed (not necessarily the same as the average text speed) is 10 words per minute (wpm). (This is my opinion—I have read an expert opinion that learners should start at 25 wpm.) Below this the brain hears too much dead space between the dits and dahs and can’t get a sense of the sound pattern. (Although 5 wpm has been used in the US as a minimum code speed, all authorities I have come across have condemned this speed as being so low as to inhibit progression to higher, practical speeds.)

The average code speed can be effectively reduced (for beginners) by adding extra space between successive words (and, for very beginners, between characters, although this slows recognition of standard words and character groups).
Since CW conveys information using only two lengths of sounds, and all the information is in the sequence of these two lengths of sounds and the spacings between the sounds, timing is everything. The only difference between “5” and “SEE” is the spacing between the dits of the “S” and two “E”s.

There are standards for spacing between dits and dahs in a character, between letters in a word, and between words in a phrase. You can find the details at URL: http://www.kent-engineers.com/codespeed.htm, but basically the spacing between the dits and dahs in a character is the length of a dit, the spacing between two characters is the length of a dah, and the spacing between two words is the length of the character “H”.


Getting Ready: Decisions, Decisions


Before you can begin you have several decisions to make.

First, you will have to make a choice of sending apparatus, commonly called a “key”. Actually you have several choices, including the classic straight key (“pump”), the bug, dual paddles and keyer, and the single paddle and keyer. 

I’ve seen a variety of odd-ball sending devices, including the up/down microphone buttons on my IC-7000, the buttons on a recycled two-button mouse, a piece of bent metal and a thumbtack, etc. I strongly recommend purchasing a good quality commercial produced paddle to start, however. You can find some advice at URL: http://www.arrl.org/files/file/Morse/Learning%20Morse%20Effectively-Prior-N7RR.pdf,  but be warned that the highly praised Begali paddles are very expensive. I don’t recommend you start there (unless you want to sell it to me very cheaply if you decide to give up on CW, in which case I hope you buy the Begali Adventure with the mounting bracket for the Elecraft KX3 J). I started with a basic black body Bencher BY-1, and still use that for my base station.

If you choose a straight key, you will be unnecessarily limiting your speed, and a future transition to a paddle will be difficult since the hand and finger action is very different. 
A bug, on the other hand, is an invitation to malformed characters (and I’ve heard some doozies on the air). With a bug, the dahs are sent at manual speed, and the dits are sent at automatic speed. There is not necessarily any correlation between the two speeds, or even between the lengths of successive dahs. 

I recommend using a paddle and keyer. The keyer helps ensure characters are correctly formed.  A keyer used with paddles solves the “bad timing” problem—often heard from bug-users—by generating sequences of correctly timed and spaced dits and dahs. With a keyer, holding the dah paddle too long will generate more dahs, not a long dah (which, in CW-speak, represents the “cut” number for zero), as happens with a bug.

A decision you’ll have to make with the paddles and keyer option is whether you want a single or dual-lever unit. 

With dual paddles you can use Iambic keying. Iambic keying generates alternating dit-dah patterns when the two paddles are pressed at the same time. It requires good thumb-finger coordination and fine muscle control. I am convinced it is more mentally demanding that non-Iambic, since the brain needs to consider the particular pattern of muscle movements required for each character, and getting set up for these movements between characters can be challenging (it is for me when I push my speed up). However, there is a small efficiency advantage in using Iambic keying. 

I use Iambic keying, although I have read that high-speed CW operators commonly prefer single paddle keying, which is necessarily non-Iambic. You can find much more on Iambic keying in an opinion piece, from a negative but useful perspective, at URL: https://cwops.org/wp-content/uploads/2018/06/iambicmyth.pdf.   The explanations are very good, and some of the negative points are good ones. (One particularly pointed argument is the following: “In practice, anybody who can send at 5 wpm with a paddle can “squeeze key” effectively. At 20wpm it takes a lot of practice and some people just can’t do it. Above 40wpm the more complicated squeezes are forgotten about even by operators who “squeeze” everything at slower speeds.”)

In the rest of this article, I will assume you are doing Iambic keying with dual paddles and a keyer. (If you choose not to use Iambic keying, however, I will forgive you: just skip over those bits.)

Once you’ve selected and acquired your new paddles (and I’m going to assume you have selected paddles from here on), you will need to adjust the spacings and tension. You should start with the manufacturer’s recommendations, but you can also find very good information at URL: http://www.morsex.com/misc/keyadj.htm.  However you set things up initially, you will likely be fine tuning those adjustments for some time until you become comfortable with them, so be sure to learn the correct procedure for your unit.
Next you will need something to generate the sounds you need for code practice. You can find suggestions in the article by N7RR referenced earlier, or a “build-it-yourself” design at URL:  http://www.arrl.org/learning-morse-code (bottom link).  I purchased a PicoKeyer Plus at first. You can also get (as I did later) the widely supported K1EL Winkeyer WKUSB-SMT, which, afterwards, can be very useful for getting your rig to send CW from your computer (very useful for CW contesting). Both are easy to build kits for those who like to solder. 

If you have a modern HF rig, this will likely be your least (additional) cost option. Modern HF rigs generally can act as a good code practice oscillator if the QSK (sometimes called VOX) setting is turned off, so the transmitter does not generate a carrier automatically when the key or paddle is pressed. (When setting this up, test it by connecting the transmitter to a dummy load, and turning the power down to the lowest setting available.) Keep in mind, however, that you may not have as much flexibility in Iambic keying options as with the specialty keyers.

A modern specialty keyer can be set in one of at least three common modes: Iambic A, Iambic B, and Ultimatic. With both Iambic A and Iambic B keying, pressing both paddles simultaneously causes the keyer to output a sequence of alternating dits and dahs. The technical differences are described in an authoritative article (by John Curtis, President of Curtis Electro Devices) that can be found at URL: http://users.ox.ac.uk/~malcolm/radio/8044.psIambic A is easier to learn, since, when the paddles are released, the keyer completes the current dit or dah element and then stops.  With Iambic B, if the paddles are released during generation of an element, the keyer will follow whichever element it is currently sending with the alternate (dit or dah) element, so the timing of the paddle action is more critical and must be much more precise (which can be tough for beginners). 

Ultimatic keying is less commonly supported (except by specialty keying chips, such as that from K1EL). With Ultimatic keying the last paddle pressed determines whether the dit or dah is repeated. If the dah paddle is pressed last, for example, the current dit will be completed and then the keyer will generate a recurring series of dahs.

My ICOM IC-7000 supports only Iambic B, so that was how I started and continue today. However, if you have a choice, and choose to use Iambic keying, Iambic A may be easier to learn.

A final decision you will have to make is which hand to use to send. Although I am right handed, I send with my left, which leaves my right hand free to make notes. This is useful when doing fairly fast contacts that are being logged on paper, such as for Summits on the Air (SOTA) activations. It is generally easier, however, to use the dominant hand to send with, since muscle coordination will be better developed and muscle control will be more precise. Whichever choice you make you will likely have to live with, although I know at least one CW op who can send well with either hand.

If you decide to send with your left hand, I suggest you learn, as I did, with the paddle configured for a right-hander, where the left paddle sends dits. The advantage is that you can be a guest op in a right-hander’s shack without having to reconfigure their rig’s paddle settings (a step which is likely to be forgotten and so will confuse one or both of you).


Sending Practice


We’re finally here: you now get to send CW!  You have done your preparations, and obtained, assembled and tested the necessary equipment.

In the beginning you should concentrate on sending one letter at a time, with lots of spacing between letters. Start sending a few standard things, such as your callsign, and those old typing standbys: “The quick brown fox jumps over the lazy dog”, and “Now is the time for all good men to come to the aid of the party”. “My Fair Lady” fans might even try “The rain in Spain falls mainly in the plain.” But these quickly become boring, so you’ll need other material.

I’ve found simple books (hint: this is not the time to pick up that book you were reading on Maxwell’s equations, Laplace transforms, or string theory) and newspaper articles can be useful.

There are four basic steps in sending: 
  1. What to say (the idea to be conveyed);
  2. How to say it (the choice of words and syntax);
  3. How to spell the words; and
  4. How to send the letters in the words. 
Note that the first two steps are common to speech, and so will be familiar. The third step is common to writing and typing, but can be a stumbling block for CW (more on this to come). The fourth step is the one you want to practice first, and using a book as source material will allow you to focus on this step. This step is where you will develop the brain-finger muscle coordination that you’ll need to “talk” in CW, just as, when very young, you learned to coordinate your brain with your tongue, lips, and larynx to speak.
One tip: when sending from books (or other written material), don’t bother with the commas, periods, dashes, and oddities like exclamation marks and quotation marks. You hardly ever need these in real life. 

In real QSOs you can manage very well by abandoning all but a few punctuation marks and pro-signs. Especially useful are the forward stroke used for portable operation (“/“), the question mark (“?”), the pause (<BT>), “73”, the “go ahead” K, the “go ahead only the one station I’m calling” KN, and the “that’s it from me for this QSO” <SK>. 
Finally, you will make mistakes. (If you think you aren’t making mistakes then you aren’t listening closely enough to what you are sending.) 

The formal way of correcting an error is to stop, send a string of eight dits, and then re-start the word in question. In practice the number of dits doesn’t need to be exactly eight, as long as it is clearly more than five (code for the numeral five) and isn’t absurdly large. This is the method I generally use.

Three other methods you might encounter are:
  1. A short series of spaced dits (e.g. dit, space, dit) followed by the corrected word.
  2. A question mark, followed by the corrected word. (Also used to repeat a word where there may have been confusion, such as with an abbreviation such as “SARC”.)
  3. For errors which are obvious (e.g. clear mis-spellings such as “tommorow”), just ignore the error and keep moving, which respects the fact that the operator at the other end can figure out what was intended.
So, with your paddles, keyer, code-practice oscillator set up, and your book in front of you (with adequate lighting), start at Page 1 and work your way through 2-3 pages per session. Keep it up—you are training your brain to make your fingers do the talking.

One final tip: Unless you live alone, you may want to use headphones. (Otherwise in a couple of weeks you may find that you are living alone.)

Keep practicing...



2019-04-12

So You Want To Learn CW (Morse Code)?



A Communicator Reprise: October 2014


Periodically I hear fellow hams say they would like to learn CW. Recently I heard yet another ham say he would like to learn CW since we get twice as many Field Day points for CW contacts than for phone contacts. He suggested the club should help members learn.

At the September club general meeting, a quick survey showed that six members present were capable of operating at 15 words/min (wpm) or better, one was capable of 5 wpm, and six members were interested but had not yet learned CW. Clearly there is some interest in CW, and particularly in learning CW. If all those interested were to reach at least 15 wpm we could double our cadre of CW operators. If those who can operate at 15-20 wpm raised their proficiency to 25 wpm, we could significantly increase our contact rate in CW contests (like Field Day).

Back when I first got my licence (mid-1960s), being able to send and receive CW at 10 words per minute (wpm) was a requirement to earn a ham radio operator certificate. Ham classes at that time had a session where the instructor sent code and the class "copied" it.

Today, however, the inefficient teaching-intensive way I first learned code is unnecessary.  I started learning again, almost from scratch, in late 2011 after being away from ham radio for nearly 35 years. The first thing I discovered is the wide range of excellent resources now available via the internet. I’m convinced that, by making good use of the (largely free) materials available on the internet, anyone who can read and write can learn CW to the 20 wpm level, if they are prepared to work at it. All that might be needed is a little advice on "how to get started”, which I felt I could provide based on my own recent experience.  And so this article was born.

Keep in mind that these are my personal recommendations, based on my own personal experience. Looking on the internet you’ll find all kinds of articles telling you how to learn CW. Some of them may be helpful to you. The tools and techniques I discuss here worked for me.

Why CW?

CW is magic.
Since changing my operation from SSB (and some digital) to almost exclusively CW, I’ve added stations to my log from all over the US, the Pacific, and the occasional contact in Europe.

Now, if I had done this using a tower and beam antenna, running the usual 100 watts, this wouldn’t be even worth mentioning. Even if I pointed out that I was working stations in high demand (like the W1AW portable stations, and TX6G, a DXpedition on the Austral Islands), where I generally had to “bust a pile-up”, there would be nothing worth writing about. If, that is, I had been using a beam and 100 watts.

But I hadn’t. I had been running a simple “end-fed half wave” wire antenna, less than 10m above ground at its highest point, and using my KX3 portable transceiver set for 5 watts output.

The type of setup I use (QRP transceiver with simple wire antenna) could be within reach of many, or even most of you, and the low power avoids almost all problems with interference to your neighbours’ badly constructed (but high-cost) TVs.
But did I really mean I could contact Florida on 5 watts? Yes—confirmed on ARRL’s Logbook of the World, along with Hawaii, Japan, Austral Islands, New Zealand, Aland Island (Finland), Guam—all on 5 watts.  To top it off, my KX3 radio, with antenna, packs into a medium sized lunch bag and runs on an internal battery pack that holds 8 rechargeable AA cells. Perfect for an afternoon’s operation in a park. Although only a mediocre operator, using just 5 watts into a length of wire hung from a tree, I’ve been able to routinely bust pile-ups of more powerful stations who were using more elaborate (and expensive) antennas.

But, of course, I was using CW. Did I mention CW is magic?

It was this magic quality of CW that convinced me to get back into CW after 35 years away from ham radio. The three primary benefits to me are:

  1. More contacts, and at greater distances, at any power level (extremely important in a contest).
  2. DX contacts at low power (very important for QRP enthusiasts, who limit themselves to 5 watts of power output).
  3. Less use of band space, so more room to find a slot in which to operate when the bands are crowded (something we're increasingly likely to see on the lower HF bands as we slide down the backside of the sunspot cycle over the next few years).

CW, because it is just on and off, puts out the radio's full power (100 W for example) when it's on. SSB, on the other hand, puts out an amount of power that increases as the voice loudness increases (to 100 W maximum in our example, and usually much less).
Further, on SSB we need to carry the "frequency range of information" in human speech, which is roughly 2500 Hz (receive filters 2100 to 2800 Hz wide are typical). CW, on the other hand, is "carrier on, carrier off”, and needs only a couple of hundred Hz bandwidth (receive filters 200 to 400 Hz wide are typical).

So, put crudely, with SSB we are sprinkling our “up to 100 W” over about 10 times the frequency range of our “full 100 W” CW.  The tight filtering with CW means the receiver passes through less atmospheric noise (QRN) and man-made interference (QRM). All of this makes for more "punch" in a CW signal at the receiver. And that’s why it’s possible to bust pile-ups using 5 W into a simple wire antenna.

You Can Do It–If You Truly Want To

I've always liked Nike's slogan: "Just Do It". It sums up for me the one problem I've so often seen, in myself and others, that keeps people from doing something they say they want to do: lack of commitment.

CW is often seen as intimidating. Certainly, anyone who wants to do it is going to have to work at it. No one else can learn it for them. Basic capability in CW will require (based on my own recent journey to date) 2-3 years of a minimum of ½ hour of practice each day (best split over two sessions).  How do I define "basic capability"? Being able to participate in most CW contests and being able to hold a reasonably satisfying on-air CW conversation with another ham at speeds of 15-20 wpm.

It's actually not difficult to continue this level of commitment if one is serious at the start and keeps at it. It has been said that habits can be formed quickly with serious initial effort. CW practice will have to become a habit. But the progress becomes very enjoyable once the 10 wpm threshold is reached.

So before reading further, ask yourself if you really want to learn CW. You will not succeed if you are not willing to work at it over an extended period. Better to be honest with yourself and stop saying (or thinking) you want to. You aren't going to dream yourself into becoming a CW operator any more than you dreamed yourself into reading and writing a language. But if you really want to learn CW to the level of basic capability, here are some of the tools and techniques I've found helpful in my own journey back into CW after some 35 years away from the radio.

Learning to Copy CW

Now that you are convinced that CW is worth the effort (you are, aren't you?), and you've examined your schedule to find a spare half hour a day (you have, haven't you?), how can you get started?

Just as with human speech, there are two actions to CW: sending and receiving. And, just as with human speech, listening is more important than sending.  So we start with listening, or "copying" as it's generally called. (I will cover learning to send in a future article.)

The first thing to keep firmly in mind is that CW is received by your brain as sound. Many experts have pointed out that learning the characters as patterns of dots and dashes on paper is inefficient and ineffective. It is far better, from the start, to learn the characters only as sounds if you are ever to become comfortable with CW. Start there until you have learned at least the simple, common characters: “e”, “i”, “s”, “t”, “m”, “o”, “a”, “n”, “r”, and “k”.

The next step is to drill using the “Koch” method, which presents a few characters at a time, adding characters until all letters, numbers, and common punctuation have been learned. Once you start with the Koch method, you can continue to learn new characters as you go.

To learn using the Koch technique I found a very helpful (and free) program called “Morse Machine” at G4ILO’s website: http://www.g4ilo.com/morse-machine.html (Look at the bottom of the page.)

Morse Machine teaches Morse using the Koch Method.  Characters are presented in a prescribed sequence and the user types the appropriate key on the computer keyboard to indicate they recognize the letter. Initially only a few characters are presented, but as you prove you have mastered these, the program adds further characters until you know the full list of letters, numbers, and critical punctuation. A bar chart graphical display shows your progress. The slowest the program will send is 20wpm, so it prepares you well for the future stages in your learning. Keep drilling until you can work through the entire sequence with few errors. Practice at least ½ hour a day, if possible in two sessions a few hours apart. I used this program a great deal in the beginning, and it was grueling. But it worked.

Once all the characters are known, I believe the next step should be to start copying actual language (as opposed to random letter groups). There are many sources of computer-generated code, with perfect timing of the sound of each character, and perfect spacing between the characters. It is essential at this point that you learn the sound of perfect CW. You will be training your brain to recognize perfect code, and building a memory of how good code sounds which will be invaluable when you begin learn sending.

I find the ARRL code practice files very helpful. These can be found here:
http://www.arrl.org/code-practice-files

Files are available for speeds from 5 wpm to 40 wpm, so can be valuable whatever your experience level. The text is taken from past issues of QST magazine. Each mp3 file containing the transmitted code is accompanied by a text file containing the associated text, which will be your “answer sheet”. Don’t bother with speeds below 10 wpm—you must learn to copy at speeds that are useful in the real world.

Once you have listened to a few of these files, you will begin to recognize the sounds of common sequences of letters as single elements (sort of like “super-characters”). The first of these for me was “the”, which is not only a word in its own right, but the root of many other words such as “then”, “there”, “their”, “these”, etc. This “letter group” recognition is very important to being able to increase your copying speed to 20 wpm and beyond, and is a benefit of starting to copy real text early. Make a point of listening for common letter groups in your practice sessions.

Don’t think you must be able to write the code down when listening to get useful practice. Eventually you’ll need to “copy in your head”, so even just listening for the common letter groups when you are travelling in the car is very helpful (but don’t become distracted!). You can burn the files to a CD, or load them on an iPod or even your cell phone if you have a “handsfree” Bluetooth connection between your phone and your car sound system (this is the method I use). The files just continue to play as you drive, and you can mentally “tune in” and “tune out” as traffic conditions permit, with no loss of benefit. (You can do this on a bus too, but wear a good sound-sealed set of ear buds or your neighbours might be tempted to heave you out a window!)

Another source of plain language code practice is the Quote Of The Day (QOTD) CW podcasts, which can be found with Apple’s iTunes music software. Look under “Store” then “Podcasts” then search for “QOTD”, which is the "Quotes of the Day" converted to CW. The advantage of the QOTD podcasts is that they are short and change daily. Podcasts are available in speeds from 5 wpm (not recommended) to 30 wpm (not recommended for beginners).  A good place to start is the 10 wpm podcasts.

Whether you are copying the ARRL code practice files, or the QOTD podcasts, don't worry if you can't copy each one perfectly. Just get what you can and keep at it; you'll find you do better as time goes on.

After you begin feeling comfortable copying the ARRL code practice files or QOTW podcasts, you will be ready for more serious drill. At this point you will want to start driving your speed up, and the easiest way to do this is to make use of “Farnsworth” spacing. With Farnsworth spacing, the individual characters are sent at a high speed (here I suggest 20 wpm), but the spacing between characters is increased to give a lower average speed. So if you are reasonably comfortable copying 10 wpm code practice files then you could set the average speed to 10 wpm and the Farnsworth speed to 20 wpm. The higher speed characters will train your brain to recognize the characters you already know when sent at a higher speed. The extra time between characters gives your brain some time to “catch up”, and recognize that the burst of sound you just heard was an “s” and not an “h”.

There are several fine programs available that send code with Farnsworth spacing, including G4FON’s free Koch Method CW Trainer, available at http://www.g4fon.net (look to the left and select the “Koch CW Trainer”). (Note I am listing programs which run under Microsoft Windows; there are also fine programs that run on Mac computers. If you, like me, prefer Macs, then send me an email at my call @rac.ca and I’ll send you a list of Mac-based programs that I think will be helpful. Most of these aren’t free, however.)
G4FON’s trainer has various operating modes. The “Text File” capability allows you to load in a short text file and have the program send it to you. By selecting an “Actual Character Speed” of 20 wpm, and an “Effective Code Speed” of 10 wpm, you can use the Farnsworth method to train. The program has a lower window which displays the text after it has been sent, so you can see how well you are doing.

The program also offers two other very useful modes. One is the “Words” mode, where the program sends you lists of common words and word endings, selected from a drop-down list.  The other is the “QSO” mode, where the program sends you simulated QSOs, just as you might hear on the air (except, unlike what you will hear on the air, the code from the program is machine-perfect).

The program has many other features, allowing you to add noise, fading (QSB), simulate weak or strong signals, create irregular (“human-like”) character timing, etc. Once you’ve mastered the basics you can have a lot of fun playing with all the “complicating” factors.
Another similar program is G4ILO’s MorseGen, at http://www.g4ilo.com/morsegen.htm MorseGen can be used to drill with characters using the Koch Method, groups of random letters or numbers, common words, plain text from a file, or pseudo-QSOs. By using the speed and spacing sliders, you can create Farnsworth-like spacing.

As you progress, you will need to learn to copy “in your head”, without pencil and paper. You can, of course, do this with the ARRL code practice files, or QOTD podcasts. The problem with these, however, is that the spacing is “regular”, rather than Farnsworth. A program that allows Farnsworth spacing that I’ve found useful for this sort of practice is ebook2cw, at http://fkurz.net/ham/ebook2cw.html
ebook2cw is a command line program but it has an optional graphical user interface available which simplifies use for many of us.  The program converts a user-selected plain text file to Morse code audio files in MP3 (or OGG, if you prefer) format. It works on several platforms, including Windows, Linux, FreeBSD and Mac OS X. The program isn’t easy to configure on your machine (e.g you’ll have to install several additional files in the same directory as the executable program), but the effort is worthwhile.
If you look to the online (and free) Project Gutenberg library at http://www.gutenberg.org, you can find text versions of out-of-copyright books that may look interesting to you. The generated mp3 files can become huge if you translate an entire book at low speed, so try just a few chapters to start. Be sure you edit out all the unusual punctuation (all the keys on the computer keyboard that I didn’t list earlier), or you’ll be very confused by some legitimate but highly unusual Morse characters. After you do your first few conversions you’ll get the knack and soon have a superb supply of interesting material sent to you in Morse, using machine-generated code with whatever extra spacing (a la Farnsworth) you wish to apply. This is my favourite CW training program!

Many of the programs I’ve mentioned will generate code at your choice of tone frequency. I suggest something in the 600-700 Hz range, but (now you are becoming comfortable with CW) you can adjust the tone to suit your personal preference. Some programs even allow you to change the wave shape from sine (the usual) to sawtooth or square wave. Again, you may find these wave shapes better suit your personal preference.

A couple of other programs which are very effective for CW contest training are the popular Morse Runner (at http://www.dxatlas.com/morserunner)and the (much more demanding, in my view) RUFZXP, available at http://www.rufzxp.net/. These are programs that experts use to drill and get their speeds up before critical contests.  If you are reading this article, it will probably be a while before you are ready for these. When you are ready, you can talk to a member of the club’s contest group to learn more about their use.

Once you become comfortable copying code at 15 wpm, and can get the gist of at least some of it in your head (without pencil and paper), you are ready to try some on-air QSOs at 10 wpm. But before that, you’ll need to learn to send, and that will be the subject of a future article. In the meantime, you have your work cut out for you learning to copy proficiently!

For a time line on the changes made through the introduction of Morse code, see: https://www.emissary.ai/telegraph-morse-code-text/

In CW-speak, “gl es 73”.

_____________________________________


December 30, 2021,

We received the following email from a student's mom. The young lady was preparing a project on CW for school:

"I'm just reaching out to let the Surrey Amateur Radio Communications know your 'So You Want To Learn CW (Morse Code)' post was a big help to my daughter Corrine and a 'Famous Inventors and Inventions' project she's working on for her technology class. Her teacher thought it would be fun for the class to learn about a new invention or technology each week that changed history. The students are then required write a short paper about what they learned, and how it impacted society. It's been fun for both of us! 

Right before Christmas break, Corrine's teacher assigned a lesson on the telegraph and Morse Code! Your page led us to some great websites to check out, so Corrine and I wanted to make sure we thanked you!!

She found this timeline of the telegraph that I loved. It was neat to see how Morse Code and continuous wave changed the history of communication. This is it... https://www.emissary.ai/telegraph-morse-code-text/

I'd love to show Corrine and her teacher! It's always nice getting some recognition for a job well done, and perhaps Corrine will even get some extra credit? Brownie points would be nice with the next round of report cards coming out soon!

The project is due on Monday when Corrine goes back to school after Christmas break, if you get a chance to include it by then! I know the holidays/new year are hectic though, so if not, whenever you get a chance to include it is great! I really appreciate it!" 

73 (I just learned this!)  
Mrs. Sarah Jackson


CQ CQ CQ

Five-band HF Linked Dipole [updated January 2025]

An improved build This antenna was first described in the November-December 2023 Communicator. After a year of using it, I’ve developed som...

The Most Viewed...