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 at 15 WPM: how do you split practice time between sending, copying, and gear tweaks?

ci_cover.jpg

This is a general discussion starter for anyone working on CW. The common plateau is that you can copy most characters at 15 to 18 WPM, but real QSOs and contest exchanges still feel rushed. Sending can feel just as uneven, especially with an iambic keyer.

Here are a few areas where operators often disagree, and I'd like to hear where people land on them.

1. Farnsworth timing vs. just slowing everything down. With Farnsworth, characters are sent at a faster speed (say 18 to 20 WPM) while the gaps between characters and words are stretched. The idea is to learn each character as a sound pattern rather than counting dits and dahs. The risk is getting comfortable with the long gaps and then struggling when a station sends with standard spacing. When do you tighten the spacing back up?

2. Keyer mode and paddle setup. Iambic A and iambic B differ in whether an extra element is sent after you release both paddles from a squeeze. If you find yourself adding an extra dit or dah, check the mode, the weight, and the paddle contact spacing and tension before blaming your hands. Paddles from makers like N3ZN are often discussed because of their adjustability, but any paddle that is adjusted properly and sits firmly on the desk will help. Many people also find a single-lever setup easier at first because it removes squeeze timing from the equation.

3. Straight keys and bugs. A straight key teaches rhythm and spacing very directly. A mechanical bug, such as a Vibroplex, makes the dits automatically while you send the dahs by hand. It has a distinctive swing, and it takes practice to keep dits and dahs consistent. Neither is necessary for good CW, but they do change how you think about spacing.

4. Filters and QSK. A narrow CW filter can pull a signal out of a crowded band. If it's too narrow, though, it can ring and make the code harder to copy, and you may miss a caller a few hundred hertz away. QSK, or full break-in, lets you hear the other station between your own elements. It's very useful in contests and fast exchanges, but it depends on your rig's TR switching and any amplifier you use.

5. Decoders and CW Skimmer. Skimmer-style software can show many signals at once, and decoders can help you check a callsign. They struggle with QSB, noise, and irregular timing, so they're best used as a second opinion rather than a replacement for your ears.

How do you divide your time between head-copy practice, on-air QSOs, contest practice, and gear adjustments? And which single change made the biggest difference to your comfort at higher speeds?

  • Replies 2
  • Views 18
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For copy practice, send-and-receive balance matters less than how you copy. If you write down every letter, you'll tend to fall behind as speed rises. Try copying in your head in short bursts: callsigns, then short words, then common phrases like CQ, DE, UR, RST, QTH, NAME, 73. Because abbreviations and prosigns repeat so often, recognizing them as units instead of letter strings frees up attention.

It also helps to separate prosigns from similar-sounding characters. AR ends a message, SK ends a contact, BT is a pause or separator, and KN means go ahead, only the named station. They're sent as a single run without letter spacing, which sounds different from the same two letters sent normally.

On Farnsworth: many people use it while learning new characters and then reduce the extra spacing as recognition becomes automatic. If a character is still being counted, slow the spacing, not the character speed.

  • Moderators

On the sending side, record yourself and play it back. Most problems show up immediately: crowded letter gaps, short dahs, or an extra element after a squeeze. Listen for spacing before worrying about raw speed. Clean code at 18 WPM is usually easier to copy than ragged code at 25.

For contests, a few habits help a lot. Send your callsign once and clearly, and repeat it only when asked. Learn the common cut numbers used in your contest, like T for zero and N for nine, if they're accepted. Don't match a faster station's speed if you can't copy cleanly; most good operators will slow down when you ask with QRS. If you want practice without pressure, tune around and copy exchanges before you call anyone.

On gear, use a narrow filter, but widen it when you're searching or you'll miss callers. Skimmer or an RBN-style spot list is a good way to confirm what you thought you heard, but keep your own copy as the primary source. If your decoder and your ears disagree, that's a useful hint to listen again, not necessarily proof that either one is right.

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.