Letting the nanokeyer decode my morse attempts / 2020-07-31

2020-07-31 Letting the nanokeyer decode my morse attempts 1 month ago
I'm still trying to learn morse and I currently make too many errors while sending with the paddle at a reasonable speed (12 words per minute).

Digging into the documentation for the winkeyer protocol showed me the option to get the morse it thinks I sent back to the computer.

This is even a supported option in winkeydaemon, the -e option.
       -e     Turns  on  winkeyer's  'echo'  feature and makes the daemon echo
              transmitted CW to all active clients (see '-p').

              Test this feature with the  'netcat'  utility:  'echo  |  nc  -u
              127.0.0.1  6789'.  This creates an active, echo-only client ses‐
              sion.
And indeed I can test my work:
$ ./winkeydaemon -s 13 -e
$ echo | nc -u localhost 6789
CQ CQ DE PE4KH
This could be used to write a morse trainer program. For now I use it to test whether I paddle what I want.

Update 2020-08-23: When I mix decoding from winkeydaemon and using the keyer in CQRlog the result is that CQRlog doesn't repaint its windows and needs to be killed and restarted to get it to work again.

Tags: ,

, reachable as koos+website@idefix.net. PGP encrypted e-mail preferred.

PGP key 5BA9 368B E6F3 34E4 local copy PGP key 5BA9 368B E6F3 34E4 via keyservers pgp key statistics for 0x5BA9368BE6F334E4 Koos van den Hout
RSS
Other webprojects: Camp Wireless, wireless Internet access at campsites, The Virtual Bookcase, book reviews
This page generated in 0.004286 seconds.