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 to do about plateaus, head copy and when to put the pencil down

ci_cover.jpg

Many learners get to around 5 wpm without trouble and then stall somewhere between 10 and 15. I'd like to collect what works for each stage, so here is a rough framework to argue with.

5 to 10 wpm: The usual advice is to learn characters at full speed, 18 to 20 wpm character speed, and stretch the gaps between them (Farnsworth spacing). If you learn at 5 wpm with normal spacing, you learn to count dits and dahs, and that habit is hard to unlearn. A Koch-style approach adds one or two characters at a time once you copy the current set at about 90 percent. Short sessions of 15 to 30 minutes every day tend to beat a single long weekend session.

10 to 15 wpm: This is where the plateau tends to show up. The sound of a character is gone before you have identified it, and you start copying one character behind. The fix people usually suggest is to stop writing every letter, copy only the first letter of each word, or just listen for whole words. Word lists of common short words and then callsign drills help here, because you start hearing patterns, not letters.

15 to 20 wpm: Head copy starts to happen on its own once you quit chasing it. Time on the air, or recorded QSOs and nets, matters more here than flashcard-style drills. Real operators have uneven spacing, and you need to get used to that.

Things I'd like opinions on:

1. How much of your practice should be callsigns versus plain text versus real on-air copy? Callsigns have no context to lean on, so they are good for raw accuracy, but they can feel like a different skill from ragchew copy.

2. Software decoders: useful for checking your copy, or a crutch? A decoder tends to fall apart with QSB, QRM and sloppy fists, which is exactly when you most want help.

3. Paddle and keyer settings. For sending, do you hold your sending speed a little below your receiving speed? Which iambic mode, A or B, and how tight do you set paddle tension and contact gap?

4. Is a CW net or a weekly contest-style event a good step up from drills, or does it only pile on pressure before you are ready? Check the current schedules and speed requirements for any net or event before joining.

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the plateau: a stall around 10 to 13 wpm is common because it is where counting stops working and recognition has not fully taken over. Raising the speed of your drills a little, even to a level where you only get 70 to 80 percent, often forces the jump. Then drop back to a comfortable speed for a while. Alternating between "too fast" and "comfortable" sessions seems to work better than grinding at one speed.

On callsign drills versus real copy, I'd use both for different jobs. A trainer like Morse Runner, RufzXP or a callsign mode in a web trainer builds quick, accurate recognition of suffixes and number-letter patterns. Real on-air or recorded QSOs teach you the predictable structure of exchanges: CQ, DE, RST, name, QTH, 73. The more of that structure you know, the less you have to decode character by character. If you are only practicing one of these, add the other.

For decoders, I'd use one as a scoreboard rather than a copy source. Copy by ear first, then run the same audio through the software afterward and compare. If you are watching the screen while copying, your brain learns to read instead of hear.

  • Moderators

On keyer settings, a few practical defaults to start from. Use a sidetone you find comfortable, usually in the 500 to 700 Hz range, and keep it the same as your receive pitch so you are not retraining your ear. Standard weighting is dash equal to three dits. Spacing matters more than raw speed: a sender at 15 wpm with correct gaps is much easier to copy than one at 20 wpm with mushed letter spacing. For reference, at 20 wpm one dit is about 60 ms, so tiny timing errors are very audible.

For iambic A versus B, it mostly comes down to what feels natural. B adds an extra element when you release the paddles after squeezing, which some find helpful and others find annoying. Try both for a few days each rather than switching constantly. Set paddle tension light enough that you are not fighting the spring and the contact gap small but not so tight that it double-triggers.

On nets and contests: low-pressure formats are a good middle step. Slow-speed nets and weekly short contest-style events like the CWops CWT sessions have a fixed exchange, so you only need to copy a name and number or callsign. That makes them a controlled way to practice real-world copy. Check the current times, speeds and rules from the organizers, since they change. If you can copy a few exchanges before a slot, do that before trying to jump in and send.

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.