When hammering out CW on the amaetur radio bands, or anywhere else for that matter, it's important to be consistent. Your dahs should sound like your dahs, your dits like your dits, and other hams should be able to tell where a word stopped and another one started.
So, it occurred to me that since I was using the straight key for TouCans, I could have the JavaScript that communicates the key down and up actions to TouCans monitor and record my dah and dit lengths along with intra-character, (time between dahs and dits), intra-word, (time between letters), and word spacings.
I asked ChatGPT if it could addd two histograms to measure these values to the web page I asked it to make for the web page yesterday, and voila!
Right! I also asked ChatGPT to add a 'Practice Mode' button so that when I was practicing I didn't have to worry about calls being made to the Pico-W on TouCans.
ChatGPT cranked out all the histogramming code quite easily. The only small snag was asking it to format to a 9:16 ratio so the video would fit on a phone. Also? I guess I could run the straight from a phone now.
The next step wil be to ask for code that finds the maximum of the dit peak, then draws a line where the dah peak should go and works out words/minute based on the dit time.
The idea is that as I get used to using a straight key, the histograms should all become more narrow as my consistency improves.
If you'd like to try the app out, you can copy it from keyer.js and keyer.html on GitHub.
Here's a video of practice mode in action.
The top graph histograms key down times, so you can see my dits and dahs organizing themselves into peaks. The bottom graph histograms key up times. You're seeing the start of three peaks, the first one is the inter-dit-dah time, (should be about the same as a dit), the middle one is the inter-character time, (should be about the same as a dah), the third peak is the inter-word time, which should be about the same as 7 dits, but I'm clocking in at about 20 wpm words with slower dits and dahs, (anti-Farnsworth?)
Comments
Post a Comment
Please leave your comments on this topic: