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.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 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

Stuck between 10 and 15 wpm: what actually moves the needle on the way to 20?

ci_cover.jpg

This is a question about the long middle stretch of learning CW, roughly from 5 wpm to 20. Getting the alphabet down is the easy part. The hard part is that progress stops being steady somewhere around the low teens, and the usual advice ("just practice more") doesn't say what to practice.

Here is a rough framework to argue with. Corrections and other approaches are welcome.

1. Learn characters at a real character speed. Both the Koch method and Farnsworth spacing keep individual characters fast, around 18 to 20 wpm, and stretch the gaps between them. The idea is that you learn each letter as a sound pattern ("dah-di-dit-dit") and not as a count of dots and dashes. If you learned at a slow 5 wpm with tight spacing, you may have to unlearn counting before you can get past about 12.

2. Shrink the gaps gradually. At a given wpm, standard PARIS timing makes one dit 1200 divided by wpm milliseconds, so 60 ms at 20 wpm. A dah is 3 dits, the gap inside a character is 1 dit, the gap between characters is 3, and the gap between words is 7. Once you copy characters cleanly with generous spacing, tighten the spacing toward standard. Many people stall here because they raise the speed and the gaps together, which makes everything harder at once.

3. Plateaus are usually about processing, not hearing. Around 12 to 15 wpm you are often still decoding letter by letter, and the pencil becomes the bottleneck. Common ways through:

  • Copy a few characters behind. Don't chase the sound as it arrives, because dwelling on a missed letter makes you lose the next three.
  • Practice at a speed where you get about 90% right, then push a little. If you are at 100%, it is too slow. If you are below 80%, it is too fast, and you will start guessing.
  • Drill whole words and common patterns (the, and, ing, tion, RST, 73, QTH, name, rig, ant) so you hear chunks and not letters.

4. Callsign drills are their own skill. Callsigns are random strings with no context, so you can't predict them the way you predict English. A callsign trainer such as RufzXP is a common tool for this. Short sessions of callsigns that repeat at a speed slightly above your comfort level make a big difference for contesting and DX.

5. Head copy comes from dropping the pencil on easy material first. Start with numbers, single words, or your own call and name, then short phrases, then conversation. Standard QSO exchanges are very predictable, which is why they make good head-copy practice: after a few CQs and signal reports you know what's coming.

6. Send as well as receive. If you use paddles, an electronic keyer sets element timing for you. Iambic mode A and mode B differ in what happens when you release the paddles while both are pressed, so try both and keep the one that feels natural. A keyer speed that is a little slower than your receive speed is fine at first. Clean spacing matters more than raw speed, and sloppy sending is hard for anyone to copy, including you when you listen to yourself on a recording.

7. Practice schedule. Short and regular beats long and rare. Something like 20 to 30 minutes a day, split into focused blocks (new characters or words, callsigns, then 5 to 10 minutes of real on-air listening), is usually easier to keep up than a two-hour weekend session, and sleep seems to help consolidate the patterns. Take a day off if your copy gets worse as the session goes on.

Questions for the thread: Do you use software decoders at all? What has helped you through the 12 to 15 wpm range? And when did you feel ready to get on the air or join a net?

  • Replies 2
  • Views 17
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the decoding question: a software decoder can be useful for checking afterward, but it works against you as a crutch while you're learning. If the screen is filling in letters, your brain has little reason to build the sound-to-character link, and decoders tend to fall apart exactly when copy is hard (QSB, QRM, a fist with uneven spacing). They are also less reliable than a trained ear on weak or noisy signals.

A more useful way to use software is as a coach. Generate your own practice text, play it back at your target speed, then compare what you wrote to the source file. That gives you error feedback without depending on a decoder for live copy. Programs like Morse Elmer, LCWO.net and similar trainers let you set character speed, effective speed and tone, and it is worth checking what each offers before settling on one.

For a first on-air experience, a slow CW net or a friendly ragchew at a speed you can handle is usually a better step than a big contest. Nets run a predictable script (check-ins, traffic, sign-off), which makes them forgiving. Many operators will happily slow down if you tell them with a short "QRS PSE".

  • Moderators

One thing to add on paddles and settings, since sending problems can look like receiving problems. If your sending is uneven, you will have trouble recognizing the rhythm of properly timed code when you hear it. A few things to check:

  • Weight and ratio: leave the dah-to-dit ratio at around 3:1 unless you have a reason to change it. Odd weighting makes code harder to copy.
  • Paddle spacing and tension: too light and you get false double dits, too heavy and your hand tires and the timing gets ragged. Adjust until the contacts feel firm but not stiff.
  • Speed: set the keyer speed to a pace where you can send perfectly. Cranking it up will reward you with errors, not progress.
  • Straight key or bug: nothing wrong with starting there, but the habits are different from iambic paddles, so pick one for the main practice block.

For contests, a mini contest or a sprint-style event is a good first step. They are short, the exchanges are fixed, and you can learn the format on a Saturday afternoon without committing to a whole weekend. Run a pileup simulator like Morse Runner beforehand if you want to practice exchanges and copying callsigns under pressure. Set it to a speed a little under what you think you can handle, because real stations will often be faster than you expect.

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.