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 around 15 wpm? Sorting out paddles, Farnsworth timing, filters and decoders

ci_cover.jpg

This thread is for the practical side of CW that tends to get scattered across a dozen topics: how you send, how you copy, and what gear or software helps or gets in the way. Many operators hit a plateau where sending feels fine at one speed but copying falls apart, or where copying is solid on the practice app but on-air signals turn to mush.

Here are some starting points, and I'd like to hear where people disagree.

Timing basics. A dit is one unit, a dah is three, the gap inside a character is one, the gap between characters is three, and the gap between words is seven. PARIS is 50 units, so dit length in milliseconds is 1200 divided by wpm. At 20 wpm a dit is 60 ms. Poor spacing is the most common reason hand-sent or paddle-sent CW is hard to read. Fast dits and dahs matter less than correct gaps.

Farnsworth timing keeps the characters at full speed (say 18 to 20 wpm) but stretches the gaps between characters and words, so the overall speed is lower. The idea is that you learn each character as a sound pattern instead of counting dits and dahs. The catch is that you eventually need to close the gaps, or you'll be stuck waiting for a slow-spaced operator who doesn't exist on the band.

Gear questions I'd like to cover: straight key versus paddle, iambic mode A versus B, whether a bug is worth the trouble, what to look for in a paddle (N3ZN and Vibroplex both come up often), how much QSK you need, and how narrow to set the filter. Then there's the decoder question: is CW Skimmer or a decoder app a useful training tool, or does it become a crutch?

For contest-minded folks: how do you handle cut numbers, repeats and speed matching without getting sloppy? Share what you've found works. I'll keep the first couple of replies to some baseline advice.

  • Replies 2
  • Views 31
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the sending side, start with the key type and what it forces you to do. A straight key gives you full control over timing, which is good for learning rhythm and bad for fatigue at higher speeds. A single-lever or dual-lever paddle with an electronic keyer makes the elements for you, so your spacing tends to be more consistent, but the keyer will faithfully send whatever sloppy timing you feed it.

Iambic keying means that squeezing both paddles alternates dits and dahs. In Mode B, if you release the squeeze during an element, the keyer sends one more opposite element. In Mode A it stops when you release. Many people who learned on one mode find the other produces odd extra dits or missing ones, so check which mode your keyer is set to before blaming your hands. Some keyers also offer Ultimatic or bug-style modes. It's worth trying them, but pick one and stay with it long enough to build muscle memory.

Paddle adjustments matter more than people expect. Contact spacing that is too wide makes you slow and heavy-handed, and too narrow gives accidental doubles. Tension should be light enough that you aren't fighting the spring but firm enough that your hand can rest without triggering. If you buy a well-regarded paddle from N3ZN or Vibroplex, you still need to set it to your hand. Check current availability and specs from the makers, since I don't want to quote anything that has changed.

A bug is a semi-automatic key. The vibrating pendulum makes dits automatically, and you make dahs by hand. It has a distinctive swing that many operators enjoy, but it takes practice and careful weight and spring adjustment. It's a nice thing to learn, not a shortcut to speed.

For QSK, full break-in lets you hear between elements, so you can tell when someone is trying to break you. It depends on fast transmit-receive switching in the rig, and if you run an amplifier, it has to keep up as well. Semi break-in with a hang time is quieter on the relays and fine for most casual operating. Use whichever mode doesn't chop off your first dit or clip the end of your last character.

Finally, record yourself. Listening to your own sending back is the quickest way to catch weight problems, uneven character spacing and word gaps that are too short.

  • Administrators

On receiving, the habit that holds many people back is translating each sound into a letter and then into a word. Aim to hear characters as units, then short words and common call signs as units. That's the reason Koch-style training with full-speed characters and Farnsworth spacing works for many learners: you don't build a habit of counting. Start with a few characters, add more as your accuracy is reliably high, and keep the character speed high enough that you can't count elements. If you have to, set the extra spacing wide and then shrink it over time.

Copying in your head, a character or two behind the sender, helps once you get past the beginner stage. Writing every letter as it arrives keeps your attention at the pencil, not on the next sound. A short note of call signs, names and signal reports is enough for most QSOs.

For filters, tune the sidetone and receive pitch to something comfortable, commonly in the range of 500 to 700 Hz, and make sure you're centered on the signal. A narrow filter can cut QRM dramatically, but very narrow filters can cause ringing that smears the characters together, and they make it easy to miss a station calling slightly off frequency. Use wider settings when searching and tighten them when working a crowded spot.

CW Skimmer and similar decoders are strong at picking out many call signs across a band at once. The Reverse Beacon Network is built on that sort of tool, and it's useful for checking where your signal is being heard. As a training aid, though, decoders do poorly with fading, noise, odd spacing and hand-sent irregularities. Use them to confirm what you thought you heard, not as a replacement for your ears.

In contests, much of the work is predictable. Learn your common prosigns and abbreviations (AR, SK, BT, KN, AS, BK, TU, and so on) and the usual cut numbers, such as N for 9 and T for 0 in a 5NN report. Set up memory keyer messages, send your call clearly rather than fast, and repeat only what's needed. Matching the other station's speed, or going slightly slower when the band is rough, is a courtesy that often gets more contacts in the log than blasting along at your maximum.

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.