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

Building CW speed the sensible way: Farnsworth, keyers, filters and when to trust a decoder

ci_cover.jpg

This is a general discussion thread for anyone working on CW operating skill, whether you're still learning characters or trying to get comfortable in a contest pileup. The same few questions come up repeatedly, so here are the main points and some open questions for the group.

Learning and Farnsworth timing. Farnsworth sends each character at a faster speed (say 18-20 WPM) but stretches the gaps between characters and words, so the overall rate is slower. The point is that you learn each letter as a rhythmic sound ("dah-di-dit") rather than counting dits and dahs. If you learn at a true 5 WPM, you tend to hit a wall later when you have to unlearn the counting habit. Many people use Farnsworth or the Koch method (starting with two characters at full speed and adding more as you reach about 90% accuracy). The open question is when to reduce the extra spacing. A common answer is to shrink the gaps gradually until the character speed and overall speed match.

Keys and paddles. A straight key is simple and gives you full control over timing, but fast sending gets tiring. Iambic paddles with an electronic keyer make the dits and dahs for you, and squeezing both paddles alternates them. Mode A and Mode B differ in what happens when you release the squeeze: Mode B adds one extra opposite element, which some operators like and others find annoying. A bug (a semi-automatic key such as those made by Vibroplex) makes automatic dits with a pendulum and leaves dashes manual, which gives it a distinctive "fist." Boutique paddle makers such as N3ZN get mentioned a lot for smooth feel and adjustability. The thing that matters most is that the paddle's travel, tension and contact spacing suit your hand. A good paddle set too heavy or too light can feel worse than a cheap one adjusted well.

Sending quality. Clean spacing matters more than raw speed. Evenly sent characters at 22 WPM are easier to copy than ragged ones at 30. Check your weighting and your inter-character spacing, and if your rig has a keyer memory, record yourself and listen back.

Receiving, filters and QSK. A narrow CW filter (often somewhere between 200 and 500 Hz, depending on conditions and the receiver) can cut adjacent signals dramatically, but very narrow settings can cause ringing that smears the characters. Matching your sidetone and receive pitch to a comfortable note (many people like 500-700 Hz) helps you tune to the right frequency. QSK, or full break-in, lets you hear between your own elements, so the other station can interrupt you. It's very useful in a contest or on a busy net, though it depends on how fast your transceiver switches between transmit and receive, and relay noise can be distracting. Semi break-in with a short hang time is a fine alternative.

Abbreviations and prosigns. The usual things: CQ, DE, K, KN, AR (end of message), SK (end of contact), BT (pause or separator), UR, RST, TU, 73. In contests, cut numbers are used, such as 5NN for 599. Prosigns are sent as a single character with no gap between the letters, so AR is sent as .-.-. rather than A-R. Q-signals, such as QRS (send more slowly), QRQ (send faster), QRL? (is the frequency in use?) and QSB (fading), are also part of everyday CW.

Skimmers and decoders. CW Skimmer can decode many signals across a band segment simultaneously, which is useful for spotting and for feeding the Reverse Beacon Network. Single-signal decoders work well on clean, steady, machine-sent code and poorly on weak, fading or hand-sent signals with irregular timing. The question for the thread: do you think leaning on a decoder slows down learning to copy by ear, or is it a harmless confidence check?

Contests. A CW contest is a good way to build speed, because the exchanges are short and repetitive. Often the best way in is to run low power on a few bands, or to answer CQs from stations calling at a speed you can manage, and gradually move up to calling CQ yourself.

What has been the most useful change for you in building speed or accuracy: the key or paddle, the filter setup, a training method, or something else?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the decoder question, I'd treat it as a cross-check, not a crutch. If you put it on screen while you copy, your brain will tend to read the text instead of listening. A better use is to copy first, then glance at the decoder to confirm a callsign or exchange you weren't sure of. A decoder also makes mistakes in exactly the situations where you most want help: weak signals, QSB, and a sloppy fist. If it gives you something that looks wrong, trust your ears and ask for a repeat.

On paddles, I'd also say adjust before you replace. Lower the contact gap until it's small but doesn't cause false doubles, then tune the tension so the paddle returns without you feeling you're fighting it. Many problems that are blamed on iambic mode are really a gap or tension issue. If you keep getting an extra dit or dah at the end of letters like C or Q, try the other keyer mode before concluding it's your technique.

  • Administrators

The point about spacing is the one I'd put first. When people say they can't copy at 25 WPM, it's often because the characters are being sent at 25 with ordinary spacing and they've only trained at lower character speeds, so each letter is going by before they've recognized it. Training at a higher character speed with extra spacing (Farnsworth), then shrinking the spacing, closes that gap.

For filters, one practical approach is to start fairly wide (maybe 400-500 Hz), find the signal, then narrow it only as far as the QRM requires. If the signals start to sound "bell-like" or the dits blur together, you've gone too narrow for the speed you're working. A wider filter is easier on your ears at higher speeds, and in a contest it can also help you notice a station calling just off frequency.

If anyone wants to try QSK, check how it sounds with headphones and with a speaker first. Some rigs click or thump on every element, and it can be tiring if the T/R switching isn't quiet. In that case a slightly longer semi break-in hang time may be more comfortable.

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.