Quick And Simple Morse Decoder

[Rostislav Persion] wrote a simple Morse Code decoder to run on his Arduino and display the text on an LCD shield. This is probably the simplest decoder possible, and thus its logic is pretty straightforward to follow. Simplicity comes at a price — changing the speed requires changing constants in the code. We would like to see this hooked up to a proper Morse code key, and see how fast [Rostislav] could drive it before it conks out.

In an earlier era of Morse code decoders, one tough part was dealing with the idiosyncrasies of each sender. Every operator’s style, or “fist”, has subtle variations in the timings of the dots, dashes, and the pauses between these elements, the letters, and the words. In fact, trained operators can recognize each other because of this, much like we can often recognize who is speaking on the phone just by hearing their voice. The other difficulty these decoders faced was detecting the signal in low signal-to-noise ratio environments — pulling the signal out of the noise.

A Morse decoder built today is more likely to be used to decode machine-generated signals, for example, debugging information or telemetry. This would more than likely be sent at fixed, known speeds over directly connected links with very high S/N ratios (a wire, perhaps). In these situations, a simple decoder like [Rostislav]’s is completely sufficient.

We wrote about a couple of Morse code algorithms back in 2014, the MorseDetector and the Magic Morse algorithm. While Morse code operators usually rank their skills by speed — the faster the better — this Morse code project for very low power transmitters turns that notion on its head by using speeds more suitably measured in minutes per word (77 MPW for that project). Have you used Morse code in any of your projects before? Let us know in the comments below.

14 thoughts on “Quick And Simple Morse Decoder

  1. Traditionally, you’d have an audio filter and detector, maybe some agc or limiting, external to the computer.

    Buut some added some preprocessing, hardware to differentiate between dots and dashes.

    In Ham Radio magazine in later 1971, there was a CW decoder done without a computer, I can’t remember if it used ICs. Used a strip printer for output. Such decoders existed commercially, but that’s the only project I saw before software.

  2. Old ticker tape machines had *mechanical* baudot decoders, which could’ve been adapted for morse also. (Imagine a motor spinning a drum synced with the baud rate, and the incoming bits trigger what part is facing the paper, followed by the whack of the hammer when the last bit is “decoded”.) (I restored one of these recently.)

    1. Those mechanical decoders (much like the project described in the article) require pretty close speed control, in order for the receiver to sync with the transmitter and produce mostly-accurate output. Once you have that limitation, why use Morse code at all? Why not just use Baudot or six-bit ASCII?

  3. “… changing the speed requires changing constants in the code […] one tough part was dealing with the idiosyncrasies of each sender. Every operator’s style, or “fist”, has subtle variations in the timings of the dots, dashes, and the pauses between these elements, the letters, and the words” …

    https://csdb.dk/release/?id=151742

    Check this one out… at various speeds and indiosyncrasies… ;-)

  4. Great job on Persion’s simple solution! I love how neat and simple it is! As a personal challenge, I spent a month or two trying my hand at an alternative to the decoder presented by WB7FHC and others and came up with an Arduino sketch that works great at cleaner 60 WPM code as well as slower hand sent code, and it automatically adjusts for speed. It requires only a good input from a tone discriminator or just a hand key. Up to this point I’ve worked mostly on the sketch and have work to do still on the electronics. Check this out: http://www.k4icy.com/cw_decoder.html

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.