You can use FLDIGI to decode what you are keying, I think that is a good way to practice.
For decoding practice, I really like qrq. It's a terminal program similar to MorseRunner. By default it gives you callsigns to practice decoding, but you can load lists of anything, like common words etc.
Another excellent resource is - Kurt has developed many resources for learning. I am also a fan of the CWOps CW Academy. This is how I learned - they host classes via Zoom that will take you from 0 to 30 wpm.
73 and hope to catch you on the air sometime - KE8BWA
On Sun, Feb 23, 2025 at 1:38?PM Shawn Rutledge K7IHZ / LB2JK via <social=[email protected]> wrote:
I guess it’s about time I get back to that.? I tried more than 30 years ago, with some DOS morse tutor program, got maybe to the point of recognizing half the alphabet or so, and stopped putting time into it.? But I got a code practice oscillator, and I enjoyed practicing sending more than decoding back then.
So I wonder if there’s some software for the sbitx for that: a morse code tutor that exercises you both ways, sending and receiving?
I just got my first paddle, a Putikeeg from AE. So of course I had to have a shot at reading the gpio pins for that last night.? I got it debounced too.? So I could keep going and write yet another code practice program, but I suspect it’s quite redundant.? There are several packages on the pi already (apt-get search morse or so will find them) and I guess they are all the type that play tones for me to decode.? And there are CW decoders of course, which take audio input.? But measuring timing to detect what I’m trying to send with my key could be done directly, rather than generating audio and treating that as the input.
