Sending Technique

Part of Telegraph

Sending technique is the physical and mental discipline of producing well-formed, accurately-timed Morse code — the foundation of reliable telegraph communication.

Why This Matters

Good sending technique is often overlooked in favor of speed. But a fast sender who produces poorly-formed code is worse than a slow sender with clean technique. Mangled timing — dots too long, dashes too short, spacing inconsistent — transforms readable code into an unintelligible blur that the receiving operator must struggle to decode, introducing errors into every message. Professional telegraph operators were judged first on accuracy and only secondarily on speed.

Sending technique is also self-reinforcing in both directions. An operator who practices with good form will improve in speed while maintaining accuracy. An operator who practices sloppy technique will reinforce the sloppiness, find that their copy rate never improves to match their sending speed, and ultimately communicate less effectively than their speed would suggest.

For a rebuilding community, operators who send clearly and at a pace their receiving partner can follow comfortably are far more valuable than operators who send fast but require constant repeats. One message received correctly is worth ten messages partially received and guessed at.

Basic Timing Relationships

The fundamental rule: a dot is the timing unit. All other durations are multiples of this unit:

• Dot: 1 unit
• Dash: 3 units
• Space between elements of the same character: 1 unit
• Space between characters: 3 units
• Space between words: 7 units

These ratios must be consistent throughout a transmission. If the first dot is 80 ms, the last dot of the message should also be 80 ms. A dash should sound exactly three times as long as a dot. A character space should sound exactly as long as a dash. Inconsistency in these ratios is what makes code difficult to copy.

The most common timing errors beginners make:

• Making dashes too long (this is the dominant error and the hardest to correct)
• Making dots and dashes the same length (heavy-handed keying)
• Inconsistent element weights (some dots too short, some too long, randomly)
• Incorrect spacing between characters (too short turns two characters into one)
• Incorrect spacing between words (too short makes words run together)

At 20 WPM, a dot is 60 ms, a dash is 180 ms, a character space is 180 ms, and a word space is 420 ms. At these durations, the elements are individually perceivable with a moment of attention. At 30 WPM, a dot is 40 ms — at this speed, timing must be reflexive; conscious correction introduces the very errors you are trying to prevent.

Straight Key Technique

The straight key (simple spring-loaded lever) is the original and most fundamental keying device. Correct technique:

Hand position: the wrist is elevated slightly, resting lightly on the operating surface but not pressing down. The thumb and first two fingers rest lightly on the keying knob. The third and fourth fingers may lightly touch the side of the key for stability. The hand should feel relaxed — no tension.

Keying motion: the dot comes from a quick wrist downstroke and return — the wrist moves, not the fingers. The whole hand lifts slightly at the wrist joint and drops sharply. A single relaxed wrist motion produces a clean dot. A dash is the same motion held down for three dot-lengths. Practice making dots and dashes separately until both feel natural and look consistent on a monitoring oscilloscope or slow-playback recording.

The key’s return spring tension must be adjusted for the operator: too light and the key bounces, producing extra contacts; too heavy and the operator must press hard, tiring the hand within minutes. Set the spring to the minimum tension that gives reliable return without bouncing.

At speeds above 20 WPM on a straight key, the wrist motion must become fluid and continuous rather than a series of discrete movements. Think of it as a flowing rhythm rather than a series of taps. Experienced straight key operators achieve 30+ WPM with clean technique through years of practice.

The most common mistake: gripping the key too tightly. A tight grip transmits muscle tremor into the keying, produces uneven timing, and fatigues the hand rapidly. The key should feel barely held — a light touch that can be released instantly. If your hand is sore after 30 minutes of practice, you are gripping too hard.

Paddle Key and Electronic Keyer

The paddle key (iambic or single-lever) moves side to side rather than up and down. The electronic keyer accepts the paddle input and generates correctly-timed dots and dashes. The operator’s role is rhythmic: squeeze left for a stream of dashes, squeeze right for a stream of dots. Characters are formed by alternating left-right pressure.

Electronic keyers maintain perfect timing ratios regardless of how quickly the operator moves — the keyer’s clock governs element duration, not the operator’s finger timing. This allows clean code at speeds that would be impossible on a straight key. Professional and competitive CW operators regularly achieve 40+ WPM with paddle and keyer.

For a rebuilding civilization without electronics manufacturing, the paddle keyer’s clock must be mechanical or electronic. A simple electronic oscillator (555 timer or equivalent) controls timing; the paddle switches select whether dots or dashes are generated. If no electronics are available, the straight key remains the only option.

A semi-automatic key (bug) uses a mechanical mechanism to automatically generate dots at a fixed rate while the operator controls dashes manually. The bug was the standard professional key from the 1900s through the 1970s. It requires no electronics and achieves 30–50 WPM in skilled hands. The dot mechanism is a vibrating spring that produces a series of dots as long as the lever is held against it; dashes are made manually by pressing the lever the other way.

Building Speed and Accuracy

Practice correctly: slow down until you produce perfect code, then gradually increase speed. Practicing sloppy code at speed reinforces bad habits. Record yourself and listen back — errors you don’t hear while sending become obvious in playback.

Use a code practice oscillator: a simple circuit that converts key presses into a tone through headphones or a speaker. This allows practice without disturbing others and without connecting to a live line. The tone should be comfortable for extended listening — 600–800 Hz is traditional.

Drills: practice specific difficult characters (C, J, P, Q, X, Y, Z tend to be irregular in the timing patterns operators develop). Practice the most common characters at high repetition (E, T, A, I, N, S, O, R are together over half of all English text). Practice common words as units: “THE,” “AND,” “FOR,” “THAT” should feel like single smooth gestures rather than individual characters.

Copy your own sending: listen to your own transmitted code and copy it simultaneously as practice. Any code that you cannot copy back accurately is code the receiving end cannot copy either. This discipline — being your own most critical receiving critic — rapidly identifies and eliminates specific timing errors.

Speed without accuracy is not communication. An operator who sends 30 WPM with 5% errors delivers messages containing an error every 7–8 words on average — unacceptable for formal traffic. An operator who sends 18 WPM with 0.1% errors delivers messages that are essentially perfect. Accuracy is the goal; speed follows naturally as accuracy is mastered.