cdaller/morserino32-trainer

morserino32-trainer's Issues

Some suggestions

My opinions and ideas for what a add-on software to Morserino should have.

The reason for a piece of software or a app that uses Koch's method to both teach receiving and transmission of morse code, is because Koch's method used conditioned aka learned reflexes to receive.
In my opinion and what I know about psychology and the workings of the human brain, it should also work with learning how to operate a morse key.

How I think the software should work,and it's modes:

It should keep track of the users progress,time used and other statistics.
That information can be used to determine where the user is in the process of learning, where the user is having troubles and needs more time, and to pick up after a lesson.

I think that a lesson should last about 10 to 30 minutes,- because too long lessons are in my opinion counter productive.

Some of the information may be posted to https://lcwo.net/ if an API is available.

Training mode: First the program sends a series of K's in CW for 30 seconds while the character K is displayed. Then it repeats the procedure with the character M.

When that is complete it sends a four characters group using K and M in random places without displaying the signs. It then waits for a four characters input using the keyboard or the morse device, shows the characters you have gotten correct in green, the wrong ones in red.

That continues until the user has gotten 90 % correct of a number of groups, then a new letter is introduced ( for example X ), it is sent for 30 seconds while the character is displayed. Then the lesson continues using the new character until 90% of groups is correct, a new character or prosign is introduced and the lessons continues until all characters are learned.

It may also be possible to display the character K and send the character in morse 5 times and wait for 4~10 around seconds for the answer using the morse key or keyboard. It should also support multiple users on the same software instance.

It should also display statistics of a users progress and time used. The slowest permitted speed should be 13 WPM. Any speed below this is wasted time.

It should also be possible to adjust the mininum and maximum number of characters in the groups and if they are of random size. It should also support Farnsworth timing, characters are sent at the same speed as at higher speeds, while extra spacing is inserted between characters and words to slow the transmission down.

The advantage of this is that you get used to recognising characters at a higher speed,the characters does not "blend together" as easily and thus it will be easier to increase the speed later on.

Realistic mode: Available during Realistic mode: signal fading,qrm and white noise to imitate more "realistic conditions", as Hannes Matuschek Kochmorse has it. It is available at: https://github.com/hmatuschek/kochmorse

Kochmorse does have a CW detector, but it can't be used to input characters during learning how to receive Morse.

Morse alphabets that should be used : Primarly International, but the possibility to add regional extras like the Norwegian Æ Ø and Å. Those extras should be possible to add to the characters learned with a option in settings.

Compatibility with a Murmur client that can connect to a murmur server, that enables chatting in morse code with other users. The client is available at: https://www.mumble.info/

Similar low latency open source free software solutions could also be used.

A existing server already exists: http://internetcw.weebly.com/

Suggestion for a plugin for mumble: https://forums.mumble.info/topic/2542-fading-and-white-noise-plugin/
This may be done by the software itself if a plugin is to cumbersome.

Compatible with Hamsphere: http://hamsphere.com

I don't know if there is any API available for hamsphere, but the developers must know.

Platform Compatibility: Linux Ubuntu and variants,Windows and Mac OS.
A website could solve this issue.

winkeyer support.
Winkeyer can be emulated using a Aurdino: https://github.com/k3ng/k3ng_cw_keyer/wiki

Winkeyer has a open source driver, available here: https://github.com/ok2cqr/winkeyer_server

Collection of CW abbreviations

You can use this list: https://docs.google.com/spreadsheets/d/1ts38a33wrM31sx71aBhX_CTw-HkMzpenzmzQGZsL_44/edit?usp=sharing
(i added the "code" header for copy/pasting the content into your source code)

It was collected from the morserinos' source code (abbrev.h) in comparison with OE6RDD CW Schule Graz' documentation.

Echo Trainer: Abbreviations should show up quicker: before next abbrev. starts

In Echo Trainer (beta) mode, there is this feature which looks up and displays common CW abbreviations.

Currently, the meaning/description is shown only after some time after reception. It seems only when the next abbreviation is transmitted by the morserino the lookup of the description is done.

It might be a good idea to already load it after the "OK" is received.