How to calculate performance when typing with Morse code

Morse code is one of two systems that allow you to represent alphabet, numbers, and punctuation marks: either through electrical pulses of variable lengths or through visual signals (think flashlight or lights).

There are multiple technical definitions, but the essence is that Morse code is one of two systems that allow you to represent alphabet, numbers, and punctuation marks: either through electrical pulses of variable lengths or through visual signals (think flashlight or lights). A sequence of dots, dashes, and spaces represents the letters, numbers, and punctuation.

Morse code generator helps in generating the Morse code. It is a tool that acts like a telegraph key where an user puts a message to convert it into a Morse code.

The International Morse Code is currently used, which was built on the primary system developed by Samuel F. B. Morse & Alfred Lewis Vail, a code for electrical telegraphy.

Our current system uses constant-length dashes (instead of the original variable-length dashes) along with dots for all letters. It might be easier to give an example (using visual Morse code in summing up electrical (sound) Morse code).

For Example :- …. .- — / .. .-.. ..- … / — ... / . ..- — .- .-. .- –. ..- .-. ..- (Ham club of kumaraguru)

Morse code is a fascinating access option for people who use switches. Here’s how to calculate performance when typing with Morse, to see how skillfully it’s working for you and how it compares to other access methods.

Morse code can be a useful way to type using only one or two switches. For some people who need a switch-based permit due to physical impairments, Morse might work as well or better than methods such as switch scanning. Reports of typing speed with Morse in the publications are optimistic but spare. And in the end, what counts most is how skillfully it works for a given person. To address that, we need to calculate typing performance with Morse.

How do we do that, in a way that’s accurate, detailed, and time-efficient? We’re going to use KPR’s Compass software for access examination to measure our Morse typing speed and accurateness. This post depicts how to do this and shows you how it reached the first time I used Morse code.

KPR compass software Setup – Morse code

To provide our Morse code permit, we’re going to use the Morse keyboard within Google’s Gboard app. This is convenient because it provides a no-cost way to get begun with Morse and see whether it suits your requirements.

We want to use KPR’s Compass software since it is designed specifically for computer access assessments to measure our typing performance. One benefit is that Compass will keep all of our typing data, and create statements of performance across time or different access methods.

OK, Gboard and Compass equip two nice components as a foundation to our setup, but there’s one notable problem. Compass software only works on Windows or Mac OS and Morse Gboard only works on iOS or Android.

How will we transmit our Morse keystrokes to the Compass typing test? Here’s where an app like Remote Mouse comes in; this allows you to type on the iPad and have the keystroke display up on your Mac or Windows PC. The free version will perform well for what we need.

So we require to set up three components: Morse Gboard, Compass, and Remote Mouse. Here’s how:
Follow the steps to set up Morse on the iPad, from a previous post. If you don’t like to use external switches, just stop after arranging up the Morse keyboard within Gboard.

Open the Compass application on your Mac or PC. You can ask for a free trial on KPR’s Compass page.
Arranged up your iOS device to transmit keystrokes to your Mac or PC, as shown in this video. Once you’ve downloaded and unlocked the Remote Mouse apps for the iPad and the Mac/PC device, it should automatically link. If not, tap on Not Linked in the iPad app, and select your Mac/PC by name.

This performed well for me operating an iPad and a Macbook Pro. Make sure you test it by visiting if you can type a word, like “hello”, utilizing Morse on the iPad, and have the keystrokes display up in a Notes app on your Mac or PC.

Calculate Morse typing speed

Now you’re prepared to measure typing performance. For this post, I calculated my performance. As a brand new Morse user, I selected the Compass Word test, to begin with, to offer me just one word at a time to stress about. I’m planning to pursue my performance over time as I understand the letter codes and practice.

Once you have something set up so that you can type on your Mac or PC using Morse code, here are the stages to calculate Morse typing speed and store the data in Compass:

  1. Open Compass.
  2. Make a new customer in Compass: at the Welcome Screen, click Start Compass, then click Create New customer. Enter a name for the customer data file, then Save & Continue.
  3. Choose the Word test to count to the Test List.
  4. Run the Word test. Type each word utilizing Morse code on the iPad. At the end of a word, you can click Enter on the Mac/PC keyboard or utilize the Morse code for entering (the time for typing Enter does not matter in the performance metrics).
  5. Consider the report after finishing the test.#

The video beneath demonstrates my first Word test using Morse. I have the test set up to show 4 words; you can do this at the Compass Test List using Configure Test before conducting the test.

I typed 2.3 words per minute on my first test. I consumed a lot of time looking at my cheat sheet to know what codes to enter, so that’s the main reason for my slow speed. After doing one 30-minute session with the Morse Typing Trainer, I enhanced it to 4.2 wpm. I’m going to attempt to maintain working on it and follow my performance over time.

Other methods to calculate typing speed

This setup is problematized a bit by the use of 2 devices: an iPad for the Morse typing and a Mac/PC to run Compass. You could facilitate the setup by using an online typing test on the iPad, but those tests have some drawbacks, including a lot of visual distractions, a one-size-fits-all presentation, insufficient precision, limited reporting, and storage for review at a later date, and incapability to directly compare access methods.