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 past the CW plateau: Farnsworth, keyer mode, filters, QSK and where decoders fit

ci_cover.jpg

Many operators get stuck somewhere between 10 and 20 WPM. The usual causes are counting dits and dahs instead of hearing whole characters, sloppy sending that makes the other station work harder, or gear settings that fight you. This thread is for sharing what works on both the sending and receiving side. Here are some starting points for discussion.

Receiving. Farnsworth timing sends each character at a fixed, faster speed (say 18 to 20 WPM) and stretches the gaps between characters and words to bring the overall rate down. The aim is to hear each character as a single sound, not build it up element by element. The risk is that if you only ever practice with huge gaps, a normal QSO at the same character speed can feel rushed. Many people shrink the extra spacing over time until it disappears. Copying on paper or keyboard is a separate choice, but writing a character down while the next one is already arriving is a good habit to build.

Sending. Standard timing makes a dah three dit lengths, the gap inside a character one dit, the gap between characters three, and the gap between words seven. Most bad-sounding CW breaks those proportions, especially with run-together letters or odd word spacing. A straight key is the simplest way to learn rhythm. A bug (Vibroplex and similar semi-automatics) makes the dits automatically while you form the dahs by hand, so the "swing" is personal and easy to recognize. With an electronic keyer, iambic mode lets you squeeze both paddles to alternate dits and dahs. Mode A and Mode B differ in what happens when you release during a squeeze: Mode B adds one extra opposite element, and that catches a lot of people out when they switch.

Paddles. Makers like N3ZN and others sell paddles with adjustable contact gap and tension. Which feel is right is mostly personal preference, but a light, narrow gap usually makes fast sending easier and a wide, heavy setup suits some people better. If you keep getting extra dits or dahs, the cause is as likely to be your paddle adjustment or keyer mode as your technique.

On the receiver. A CW filter somewhere in the 200 to 500 Hz range cuts neighbors and noise, but a very narrow filter can ring and will make you miss callers a little off frequency. Set your sidetone and receive pitch so the signal you want sits in the middle of the passband. QSK (full break-in) lets you hear between your own elements, so you can be interrupted mid-transmission, which is handy in a pileup. It does require T/R switching that keeps up, including in any amplifier.

Questions to get started: what helped you most in moving from "I can copy at 12" to comfortable QSOs at 20? How do you decide when to stop adjusting gear and just practice more? And how much do you trust a decoder when you can't hear a callsign clearly?

  • Replies 2
  • Views 24
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One practical tip on keyer mode: pick one and stick with it for a while. Switching between Mode A and Mode B while learning makes it hard to tell whether an extra element is a mistake in your fingers or a setting. If you do not squeeze at all, the difference is invisible. Squeezing mostly matters for letters like C, K, Q, R and the like, where dits and dahs alternate.

Also check your weighting and dit/dah ratio. If your keyer sends 1:3 dits to dahs with the proper spacing, other operators can read you without strain. Some keyers have a weight setting that makes dits slightly longer, which can sound heavy at higher speeds. If someone sends you an "AGN" request on a callsign that you thought was clean, a recording of your own sending is worth a listen. It is often spacing, not speed, that makes a call hard to read.

For prosigns, remember they are sent as a single unit with no letter gap. AR (.-.-.) ends a transmission, SK (...-.-) ends the contact, BT (-...-) separates thoughts or serves as a break, and KN means go ahead to a specific station only. Practicing them as sounds rather than letters helps a lot.

  • Moderators

On decoders: CW Skimmer and similar software are excellent at spotting. The Reverse Beacon Network, for example, relies on skimmer-style decoding to show who is on the air and where. But decoding quality depends heavily on signal-to-noise ratio, fading, and how consistent the timing is. Hand-sent CW with irregular spacing, a bug with varying dahs, or a signal in QSB can all produce wrong characters. For a callsign in a contest, a decoder is a useful hint but I would still confirm by ear or ask for a repeat before logging a doubtful call.

Contest CW has its own conventions. Cut numbers are common in exchanges, so 9 becomes N and 0 becomes T, and 599 is often sent as 5NN. When you ask for a repeat, ask for only the part you missed instead of sending a full question or repeating the whole call back. If someone is calling you faster than you want to run, you can slow down, but staying near the caller's speed usually keeps the rate up. For search-and-pounce operating, listen to a couple of exchanges before calling so you know the format and the speed on that frequency.

Back on QSK: it is great for contests and DX because you catch someone calling over you or hear a station asking for a repeat. If you use an amplifier, check that its relay and your T/R sequencing can really handle full break-in, or you will clip the first elements or hear relay noise.

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.