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

Getting from 5 to 20 WPM: what actually moves the needle, and what to do when you stall

ci_cover.jpg

Most CW learners hit the same milestones in the same order. Characters are solid at 5 WPM, then 10-13 WPM feels like a wall, then somewhere past 15 the brain starts hearing words instead of letters. This thread is for comparing methods at each stage. Below is a rough map, and the replies can pick it apart.

Character speed versus overall speed. Whether you use Koch or Farnsworth, the usual advice is to keep individual characters at 18-20 WPM and stretch the gaps between them. If characters are sent at 5 WPM, you end up counting dits and dahs, and that habit is hard to unlearn. At full character speed each letter becomes a single sound, like a short word. Then you shrink the spacing as copy gets comfortable.

The 10-13 WPM plateau. This is often where you are still translating: hear a character, name the letter, write it down, and miss the next one while doing so. Raising speed alone may not fix it. What tends to help is copying slightly faster than is comfortable and accepting gaps, plus sessions where you stop writing and just listen for whole words. Common words (the, and, you, rig, ant, name, QTH) are good first targets because they get recognized as units.

Head copy. Start small. Take a block of easy text and follow it by ear with no pencil, then try a QSO exchange. Callsigns are good drill material because they are short, random, and what you will actually need on the air. Tools like RufzXP exist for exactly this kind of callsign work, and Morse Runner simulates contest pileups at adjustable speed and noise.

Schedule. Fifteen to thirty focused minutes a day generally beats two hours on a weekend. A simple split is a few minutes of new or weak characters, ten minutes of word and callsign drills, then a few minutes of real or recorded on-air copy. When you plateau, rotate the mix instead of grinding the same drill.

On-air practice. Slow-speed CW nets and practice sessions exist, and many clubs and CW groups run them, but check current schedules and frequencies with the organizers. Short contest-style events can be good for callsign and exchange copy because the format is repetitive and predictable. You do not need to enter seriously. Listening to the exchange pattern is practice too.

Keys and keyers. If you send with paddles, a keyer speed a few WPM below your copy speed helps keep sending clean. Weight and dah-to-dit ratio are usually left near default, around 3:1. Paddle contact spacing and tension are personal. Too tight causes missed elements, too loose causes doubled ones.

Ear versus software. Decoders are useful for checking what you thought you heard, but they struggle with fading, noise, and the irregular timing of hand-sent code. If a decoder is always on, your ear may never be forced to do the work.

Questions for the thread: what broke you out of a plateau? Do you drill callsigns separately or only in context? And where do you draw the line on decoder use?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the plateau, one thing worth checking is whether the problem is copy or recall. If you can recognize characters fine in isolation but fall apart in running text, the issue is usually lag: you are still processing the previous character when the next arrives. Dropping the speed won't fix that. A better test is to copy at a speed where you miss about one in ten characters, and just let the missed ones go. Skipping a character without chasing it is what trains you to stay current with the stream.

For callsigns, it helps to work them in two passes. First, pure recognition: letters and numbers at full speed with plenty of spacing. Second, in context: callsign embedded in a short exchange like 'CQ CQ DE' or 'UR RST 599'. The context pass teaches you where callsigns start and end, which is half the battle on a busy band.

As for software, a middle path is to copy by ear first and only afterward compare against a decoder or a recording. That gives immediate feedback without letting the screen do your listening for you.

  • Moderators

On keyer settings, there is a common mismatch to watch for: people set the keyer speed to match their copy speed, then find sending feels frantic. Sending slightly slower than you can copy is usually cleaner, and nobody on the other end minds well-formed code at a modest speed. Iambic A versus B is worth testing both ways. The difference is what happens when you release the paddles mid-squeeze, and one mode will feel more natural to your hands. Whichever you pick, stay with it long enough for muscle memory to form.

For QSO practice, a good ladder is to listen first, then answer a CQ using a canned exchange (name, QTH, rig, weather), then gradually go off-script. The canned part gives you a safety net while you get used to the pace. Many people find that the first real contact goes better than expected because the exchange is so formulaic, and the second goes worse because the other operator wanders off-script and your head copy has to keep up.

Straight key versus paddle is mostly a preference. Sending with a straight key can help you internalize rhythm and spacing, while paddles make sustained higher speeds easier on the hand. Neither replaces copy practice, though. Sending speed and receiving speed develop somewhat independently, so schedule time for both.

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.