Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Getting from 5 wpm to 20 wpm: what actually moves the needle, and where does everyone stall?

ci_cover.jpg

This thread is for comparing methods for building CW speed from beginner level to a comfortable 20 wpm. It covers practice structure, plateaus, gear, and the ear-versus-software question. Below is a rough map of the stages, and I'd like to hear where yours differ.

5 to 10 wpm: the characters have to become sounds. The usual advice is to send characters at a fast rate, around 18 to 20 wpm, with extra space between characters and words (Farnsworth timing), or to use the Koch method, which starts with two characters at full speed and adds one at a time once you copy about 90 percent. Both aim at the same thing: recognizing a character by its rhythm, not by counting dits and dahs. If you catch yourself thinking "dit dah dit dit, that's L," the character speed is too slow.

10 to 15 wpm: the first big plateau. This is where many people get stuck. Pencil-and-paper copy of every letter starts to cost you, because your hand falls behind your ear. Letters keep arriving while you are still writing the last one, and you lose the next two. The fixes are to copy a little behind the sender, to practice common words as single units (THE, AND, FOR, YOU, RIG, ANT, WX), and to start copying in your head for short stretches. Head copy is easier when you stop translating each letter into text and just let words and phrases register.

15 to 20 wpm: words, callsigns and exchanges. Callsign recognition is its own skill because there is no context to help you. A random string like K9ZQX can't be guessed from the letters before it the way a word can. Dedicated callsign trainers, plus a pileup simulator for contest-style exchanges, are worth the time here. Practice the standard QSO skeleton too: CQ, callsign, RST, name, QTH, rig and weather, TNX, 73. Once the structure is familiar you only have to catch the variable parts.

Schedule. Short daily sessions generally beat one long weekly session. Something like 20 to 30 minutes a day could be split as: 10 minutes of new or weak characters, 10 minutes of words or callsigns slightly above your comfort speed, and 5 to 10 minutes of real or recorded QSO material. A common approach to plateaus is to alternate days: one day at a speed where you copy about 95 percent, the next at a speed where you only get 70 to 80 percent. The slower days build accuracy and the faster days stretch your ear.

Sending matters too. If you use paddles, iambic mode A or B, paddle spacing and tension, and weighting all affect how clean your code sounds. Many keyers default to a 3:1 dah-to-dit ratio and standard spacing. Poor spacing between letters and words makes your code hard to copy at any speed. A sidetone pitch you find comfortable (many people like 500 to 700 Hz) reduces fatigue over long sessions.

Ear versus software. Decoders can be useful for checking what you thought you heard, but they struggle with QSB, noise, and hand-sent code with uneven timing. If you lean on one, your brain may stop doing the work. Using it only to verify after you've copied is a reasonable compromise.

Questions for the thread: what was the plateau speed where you stalled, what broke it, and are CW nets or contests useful for building speed, or are they better saved until you're already comfortable?

  • Replies 2
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On nets and contests, it helps to separate the types, because they train different skills. A slow, friendly CW net with a patient net control is mostly about structure: check-in format, handling a callsign list, and passing a short message with minimal fuss. The speed is often forgiving, and you get real on-air copy without much pressure. Ragchew QSOs are different, because the other operator sets the speed and the content is open-ended, so they are better for building head copy once words are coming easily.

Contests are very good for callsign and exchange skill, because the format is repetitive. You hear the same pattern over and over: callsign, signal report or serial number, and sometimes a name or section. Contest exchanges often use cut numbers such as 5NN for 599, and learning those speeds things up. Some contests have a QRS or slower-speed segment, and many operators will slow down if you send your callsign slowly and ask. You don't need to be fast to work a few stations, and listening to a contest without transmitting is also a decent way to practice callsign copy.

Two practical suggestions. First, record a few minutes of on-air CW and copy it later, so you can replay a passage you missed instead of guessing. Second, don't try to log everything in real time at first. Write only the callsign, or only the part you actually need.

  • Moderators

I'd push back a little on treating the ear-versus-software question as either/or. A decoder and a trainer are different tools. A decoder tells you what someone sent. A trainer, such as a character drill or a callsign program, builds the recognition itself. The risk with a decoder isn't that it exists, it's that you read the screen instead of listening, so your brain never learns the sounds. If you do use one, turn the display off during the first pass and look at it only when you're stuck.

On the plateau, one thing that often gets overlooked is character-speed discipline. If you slow the characters down to make the code easier, you can reinforce counting. Keeping character speed up and stretching only the gaps, then closing the gaps gradually, tends to be more productive. Another trick is to listen to material a bit faster than you can copy and just try to catch the first letter of each word or the callsign. That trains your ear to react quickly without demanding full accuracy.

For the key itself, check the basics before blaming your brain. If your paddles are set too tight, or the contact gap is too wide, you'll get dropped or doubled elements, and that shows up as errors in your sending at higher speeds. Set the gap and tension so a light touch makes a clean dit or dah, then adjust the keyer speed so the rhythm feels easy, not forced. Some people find mode A feels more predictable and mode B better for squeeze keying, so it's worth trying both before settling.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.