[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.
Yep. Morse makes great error beep codes, and a single letter is easy enough to be parsable even by muggles. (like “long short short short” = “B”attery)
IIRC, we got an SGI (late 1990s) that beeped out S-O-S when it needed attention.
Local guy who I have done some rework for makes this thing. https://preppcomm.com/
It uses Morse code to act like 2 way paging or texting…has a 3w transmitter built in and can plug into higher power stuff.
It is a pretty neat little device.
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.
Here is my CW / PSK31 / PSK63 decoder from 2010, drawing around 2mA current, doing audio filtering on a MSP430 with no HW multiplier.
https://www.youtube.com/watch?v=hLyVI3wtlz8
https://www.youtube.com/watch?v=HcxIgqx17Vw
https://www.youtube.com/watch?v=2Aydo8dUZjM
Runs on http://www.msp430launchpad.com/
Source code
https://sourceforge.net/projects/pocketdigi/files/decoder/msp430-decoder-1.2-src.zip/download
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.)
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?
before the program runs….. you could use some statistics to get an average dit dat duration…
“… 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… ;-)
CQD.. The display must read CQD..
Just kidding! 😁SOS is fine here, because that’s what most people know and most people would be able to send.
Neat project! And just in time for the SAQ transmission on Sunday, by the way!
https://alexander.n.se/
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
Nice. But we need neural network driven one! I saw a few papers but no actual project so far :(
And this will turn your voice into Morse Code. https://hackaday.com/2020/07/16/speech-to-morse-code-courtesy-of-google/