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 a CW station to feel right: paddles, keyer settings, filters, QSK and where decoders fit

ci_cover.jpg

This thread is for the practical side of CW operating: the parts that make the difference between copying and sending comfortably and fighting your own station. Many people start with a code-speed goal and ignore the equipment and settings that quietly limit them. Here are the main areas where small changes tend to matter, and I'd like to hear how others approach them.

Keyer and paddle setup. If you use an iambic keyer, the first thing to understand is Mode A versus Mode B. In Mode B, squeezing both paddles and releasing during an element adds one extra opposite element. In Mode A, the keyer stops when you release. Neither is correct for everyone, and sending errors often come from a mismatch between your habits and the mode. Paddle tension and contact spacing matter just as much. If the spacing is too tight you get double dits. If it's too loose you get missed elements at higher speeds. Weight and any dit/dah compensation settings are worth leaving at defaults until you know what you're fixing.

Straight keys and bugs. A straight key gives you complete control over timing and is a good way to feel the rhythm of the code. A semi-automatic bug, such as the Vibroplex type, makes the dits mechanically with a pendulum and leaves the dahs to you. It has a distinctive swing that some operators love and others find hard to control. Makers such as N3ZN come up often when people compare keys and paddles. Rather than trusting a brand name alone, check current specs, adjustment range and whether the base is heavy enough that it doesn't slide around on the desk.

Timing and Farnsworth. Standard timing uses a dit as one unit, a dah as three, one unit between elements, three between characters and seven between words. The PARIS standard word is 50 units, so dit length in milliseconds is roughly 1200 divided by WPM. Farnsworth spacing keeps the characters at a higher speed, say 18 to 20 WPM, and stretches the gaps between characters and words to lower the overall speed. That helps you learn to hear each letter as a sound pattern rather than counting dits and dahs. Many learners pair it with the Koch method, which starts with full-speed characters and adds letters gradually.

Filters, pitch and QSK. A narrow filter can make a weak station easier to copy, but if it's too narrow the signal can ring and the code smears. Many operators use somewhere in the 200 to 500 Hz range depending on conditions and then adjust. Set your sidetone and receive pitch to something comfortable, since a pitch you dislike gets tiring over a long session. QSK, or full break-in, lets you hear the other station between your own elements. Some radios and amplifiers don't handle it well, and relay clatter or hot-switching can be a problem. Semi break-in with a short hang time is a common compromise.

Abbreviations and prosigns. Standard shorthand speeds things up: CQ, DE, K, KN, AGN, PSE, TU, 73, QRS, QRQ, QRM, QSB and so on. Prosigns like AR, SK, BT and KN are sent as a single unbroken character with no letter gap. Cut numbers like 5NN for 599 are common in contests but can annoy people in a casual rag chew.

Decoders and skimmers. CW Skimmer and the Reverse Beacon Network can show you who's active on a band and where your signal is being heard. Software decoders can help with identifying callsigns, but they struggle with fading, noise, poor spacing and unusual fists. They won't replace copying by ear, though they can be useful as a second opinion in a contest.

My questions: What's your biggest bottleneck right now, sending cleanly, copying at speed, or setting up the station? And if you're moving toward contesting, are you using a logger with function-key macros and a skimmer feed, or keeping it simple?

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For sending, I'd say record yourself before changing any gear. Most 'my keyer is bad' problems turn out to be spacing problems: letters running together, or gaps between words that are too short. Listen to a recording with the sidetone off if you can, or run it through a decoder as a rough check. If the decoder consistently splits a letter, your character spacing is probably off even if each element sounds fine.

On Mode A versus Mode B, the best test is to send a few letters that need alternating elements, like C, K, R and Q, and see which mode gives you the output you meant. If you keep getting an extra dit or dah on the end of a character, try the other mode, or adjust how early you release the paddle. A lot of people find it's just a timing habit rather than anything wrong with the keyer.

For receiving, I'd keep Farnsworth at a character speed you can't comfortably count out. If you drop the character speed to match your overall speed, you end up counting dits and dahs and that habit is hard to break later.

  • Administrators

On the contest side, the choice of filter and AGC often matters more than raw speed. In a crowded band, a narrow filter can help you pull a callsign out of the pile, but if you're searching and pouncing you may want a slightly wider setting so you can hear nearby stations and avoid calling on top of someone. Many operators change filter width depending on whether they're running a frequency or tuning around.

If you use CW Skimmer or an RBN-style spot feed, treat the spots as hints, not confirmations. Skimmer errors, busted calls and partial decodes happen, especially when someone is fading or when two stations overlap. It's still worth confirming the call by ear before you transmit. A good logger setup with function keys for your CQ, exchange, TU and a repeat of your callsign saves a lot of effort, but it helps to be able to send manually when the exchange gets unusual.

One more thing about QSK: if you intend to use it with an amplifier, check the amplifier's documentation for its supported switching speed. A radio that handles QSK fine may not be happy driving a relay-based amp at the same speed.

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.