What Is An Accessible Radio? – Part 3

Part 3

So with the clunky command structure and its output. I decide that some accessibility is better than not enjoying my favourite brand of radio, as I document the FT-991A road to accessibility. As most people use Windows, this guide will use Windows 11 to control the radio. Links and commands will be put on a single line so that they can be copied to the clipboard, Control + c, and paste, Control + v, where possible. To my knowledge the given commands are also true for Windows 10.

I have already provided the link to the hamlib GitHub stable release in part one but here it is again.

https://hamlib.github.io/

On this page use the screen reader search function, (Typically modifier key + “f”) for the words “Current Stable”. Just below that is a link to the current stable release page. At the time of writing it is hamlib 4.5.4. After activating the link of the latest stable release. Again use the search function of the screen reader for w64 if the PC has a x64 processor, or w32 if the processor is a 32 bit processor. Consider downloading the .exe option so that unzipping is not required. If the system allows the downloading of executable files.

As with many open source projects, it is possible to obtain new features that are under active development. Sourceforge hosts daily snapshot builds. I would recommend these builds if the radio is newly supported by hamlib and it is suspected that its support is actively developed. In my case, the FT-991A is marked stable and its support is probably mature. In this case choosing the stable version makes sense.

Here is the bleeding edge builds sourceforge link:

https://n0nb.users.sourceforge.net/

Again use the search function of the screen reader to find w64 or w32 as appropriate for the system being used. Consider downloading the .exe option so that unzipping is not required. If the system allows the downloading of executable files.

Having downloaded a copy of hamlib just press enter and run the downloaded installer. I have not found it necessary to change any of the options and just accepted the defaults of this simple accessible installer.

Now I need to gather some information for rigctl to communicate with the desired radio. Basically the command is rigctl with 3 switches, these are mrs. Which are defined by a preceding dash and I will explain the 3 pieces of information in turn that is required and their correct syntax below.

The installer did not add hamlib to the path so Windows does not know where rigctl.exe is located. So I need to navigate to its location and run the commands from the same folder as rigctl.exe manually. Knowing I will be able to automate the process later.

I Pressed Windows + r.
I typed cmd
I pressed enter
I typed cd c:\
I typed cd prog
I pressed the tab key (Knowing it will auto complete)
I typed ham
I pressed the tab key (Knowing it will auto complete)
I typed bin
I pressed enter.

Notes:
1) I knew if the install has been placed in the Program Files )x86) folder. After pressing tab so that program files appears, I would need to backspace once. Then I would press the spacebar, then the tab key again to auto complete.
2) cmd.exe the program I am using here has a problem with its own back slashes. Therefore, I had to write it out in stages.

Having installed hamlib and navigated to the installed program folder. . I need to find the model number of the radio, to be controlled. Which is for the model switch expressed as “-m”. So that hamlib knows what radio is connected to the computer. By typing “rigctl -l”, the program will return with a complete list of all the radios hamlib supports. As the list is long it is necessary to filter the results by using the pipe symbol sending the output to the find function of Windows. Just like this:

rigctl -l | find “991”

This will list all the listed radios with the string 991. Note that the string needs to be in quotes. Typically there are 2 lines of output giving the model number and its status. Note where the model number 1035 is presented from this example:

1035 Yaesu FT-991 20221104.14 Stable
RIG_MODEL_FT991

Now I have the model number the command looks like this so far. Note the dash before the switch and the spaces between the switch and argument.

rigctl -m 1035

The remaining 2 switches are down to the computer and radio’s configuration. The “-r” switch is the radios location on the computer i.e. what com port has been assigned to the radio. I Made sure the correct driver had been installed, as instructed by the manufacturer of the 991A.

To find the radios com port i.e. its location, I did this:

Ensuring the radio is powered on and connected to the computer with the right cable.
I tabbed until the screen reader spoke “Start Button”.
I pressed the Applications Key alternatively I could have pressed Shift + F10.
Then I pressed the letter m.
Then I pressed tab.
Then I pressed p.
Then I pressed the Right Arrow Key
Then I press Cursor Down through the list of ports in order to observe what com ports have been assigned to the radio and made a note of the port number.

Now the command is looking like this:

rigctl -m 1035 -r com1

If I had wrote the wrong com port number rigctl will just refuse to load. and return me to the desktop.

Now for the final piece of information the speed switch “-s”. This is the baud rate of the radios serial port configuration.

By typing the following command, I was able to establish the range of baud rates the 991 supported as stated in the caps_dump output.

rigctl -m 1035 -u | find “serial”

The find command returned: Serial speed: 4800..38400 bauds, 8N2 CTS/RTS

I found that the wrong baud rate causes Rigctl to take some time to present the “Rig Command” prompt and radio commands will not work.

I simply pressed q and quit rigctl. Then I pressed Up Arrow which displayed the previously entered command. Then I just back space over the baud rate and tried another value from the list below. Guided by the command above caps_dump for the 991 and observed that the baud range was 4800 – 38400. The caps_dump will be explained in the next part of this guide.

I notice immediately when I had the correct value as the “Rig Command” was immediately displayed. I pressed the letter ‘f’ and the radio returned the current frequency. I made a mental note of the successful baud rate of 4800.

Standard Baud Rates include:
1200
2400
4800
9600
14400
19200
38400
57600
115200

These were taken from:
http://www.ece.northwestern.edu/local-apps/matlabhelp/techdoc/matlab_external/baudrate.html

Now my command is complete and looks like this:

rigctl -m 1035 -r com1 -s 4800

In the next part I will generate a few useful files and write a batch file to automate the process so that pressing enter on a batch file starts rigctl and connecting to the 991A, right from the desktop.

Take Another Stab at CW G4FON Accessibility Review

Take another Stab AT CW

By Deborah Armstrong, KF6BKR

June 2013

Are you one of those who waited to get your general or extra after the code requirements were dropped? Or are you like me,an advanced who plateaued somewhere around 15WPM and just couldn’t seem to get beyond that speed?

Or perhaps you used to copy fairly fast, but now the skill is rusty.

Of course, many of us have no desire to learn CW and that’s just fine. There is a place in ham radio for a variety of avocations.

But suppose being a high-speed CW OP appeals to you. Noticing all the noise on the bands lately, I wanted to grab a pee-wee antenna and climb a mountain to get away from it. But phone QRP is not as exciting as using code, and CW is the only thing that’s really going to punch through all that noise. Those of us plagued with local antenna restrictions might view CW as a way to enjoy operating under the radar.

Besides, I wanted to understand beacons or even a repeater ID without struggling to copy the faster transmissions. And sometimes, hearing a strong CW QSO on my shortwave, I was just so curious about what those two hams were ragchewing about. And of course, I’d love to expertly operate those accessible rigs with CW frequency and menu readouts!

To master CW, we’ve been told that all we need to do is practice, and surfing the web, we discover that multiple learning ideas and tutorial software abounds. We can purchase or run free applications on most any computer, including our smartphones. We can buy the pocket Morse code trainer from MFJ, or use old-fashioned tapes. I even bought a set of old Morse code training records for a buck at a swap meet.

I attempted to practice with many offerings, and was still stuck on my plateau. As a blind ham, I felt kind of embarrassed, as many of my other visually impaired friends took to code like a duck to water. I also found much of the tutorial software inaccessible; I memorized the tapes and records and even though I walked around silently repeating dits and dahs to myself, as soon as the speed of others’ code shot up, I was five or more letters behind trying to copy.

Ray Goff, G4FON, and Dave Finley, N1IRZ had the same problem. Though accomplished tinkerers and communicators, they too had despaired of learning the code, despite attempts to practice using a variety of methods. When I discovered how they’d succeeded, I knew I’d found my solution.

Many methods are based on having you build a look-up table in your head; three dits is an S, 4 dits is an H. Farnsworth spacing gives you enough time to rapidly search that table to copy each character, before the next is sent.

Lugwig Koch, a German psychologist in the 1930s, felt that learning code this way was all wrong. He suggested we learn CW at the high speed in which we ultimately intend to copy so we never develop the limiting habit of searching that mental look-up table. His Koch method trains your reflexes by starting first with just two characters, and after you’re able to copy them with 90% accuracy, you then add a third character. Progressing at your own pace,you can copy characters, digits and prosigns, whole words, and eventually entire conversations in your head. And you learn this all at rapid-fire speed!

The Koch method is rewarding because you are always copying fast code. It motivates practice, because success is immediate. You work at a pace that is individualized for just you, learning what you can, when you find the time. The only real requirement is that the practice should be regular.

It doesn’t take talent or a good ear, or any special ability except the willingness to drill. Dave was so taken with the Koch method he wrote several articles on, and single-handedly revived the technique. Back in the 1930s, Koch’s research had been a curiosity as it was impractical to implement. To achieve his successes of teaching volunteers in 12 hours to copy all characters at high speeds, Koch needed human operators who could repeatedly drill his subjects. Dave realized today computers can do that, so he wrote “Morse Code: Breaking The Barrier” which was published by MFJ. In this book, Dave explains how to configure Morse tutor software for the Koch method. And of course, the MFJ-418, their pocket tutor can also be configured for Koch.

But I find the MFJ-418 mostly inaccessible, because its layered menus are difficult to memorize. When I asked on the blind-hams Internet list for thoughts about accessible software, the clear recommendation was to use the Koch trainer written by Ray, G4FON.

Ray’s Windows software works with JAWS, NVDA, Window-Eyes, System Access and SuperNova. I’ve tried it with them all. I also tried it under both Windows XP and 64-bit Windows 7 and Ray claims it works all the way back to Windows 95. And because it’s already set up for the Koch method, you don’t need to change the number of characters, or the order in which they are presented. Best of all it’s free.

The Koch trainer screen’s layout keeps most options in view. There are only two items on its menu bar, file and About. Under about, there’s a single help screen. Under file, you can choose to record the audio it sends in MP3; you can exit help or call up a single dialog box for Setup. It’s really not necessary to fool with the setup at all.

Under the menu bar, there are clearly labeled icons, toolbar buttons for Start, Stop, Setup and Finish. Setup takes you to the same configuration dialog you could access from the File menu. Start and stop begin and halt a training session. Finish exits the program. You can click directly on the graphics or on their corresponding labels below them. You can use a screen reader’s graphics labeler to label the graphics too, though that’s not necessary, since clicking on the onscreen label also activates the button.

Though there is no keyboard access to these buttons, a helper program, discussed below, will give you all the keyboard access you need. If you hover over one of the toolbar icons with the mouse, its corresponding label is also highlighted, making it very easy to use even for those who are not computer whizzes.

The remainder of the screen is a grid filled with controls, which can be clicked on or accept focus by repeatedly pressing TAB or SHIFT-Tab. These are spin boxes, radio buttons or check boxes. They are not in any logical tab order unfortunately, and I’ve emailed Ray suggesting that would be a simple change to improve their ease of access. The spacebar toggles a check box, arrows change the selected radio button or spin the value up or down in a spin control. These are labeled in a way that a screen reader can correctly identify, but will not be read automatically; you must use the screen reader’s keystroke to read the current control or object to determine its current state. If you are an advanced user of a screen reader you can also tell it to “re-class” the controls so it can better read them interactively.

Mostly these settings can be left alone, but a few require some explanation.

I was initially frustrated that no obvious setting appeared for creating pauses between characters. Working at the default 20 words per minute, I couldn’t keep up, even with just two characters. Searching forums, I found sighted people complained they couldn’t write that fast either. I realized it wasn’t a question of typing or writing fast, but reacting fast, which I had made yet no effort to train myself to do. You can set “actual” and “effective” code speed. By default, both were at 20 WPM, and I had to experiment with each of them until I got it to send fast enough to be challenging but slow enough I had time to react. Pauses occur when “effective” is faster than “actual”. Of course as I progress, I’ll keep increasing these values. Depending on your tolerance for frustration and your proficiency, you’ll definitely want to experiment with both these settings. Sometimes when changing one, the other changes as well, so it takes a bit of fiddling to get them to work for your current skill level. And because your progress will be rapid, you’ll find you have to keep fiddling with them every few sessions. Admittedly, this is a bit quicker to do with a mouse, but though cumbersome for a keyboard user, it’s accessible and easy to do.

The characters spin box selects the number of characters you’ll be drilled on. A beginner starts with 2, and after mastering them, moves on to 3, 4 and then 5. Eventually, you spin that setting up to 40, which is the highest it goes. The order in which new characters is presented can be changed in Setup, but I figured Koch knew more than I, so I didn’t touch that setting.

The “display delay” controls how long the program waits before presenting the “answer” onscreen after sending a character. Because I am not copying with focus staying in the Koch Trainer window, the delay doesn’t really matter, but if you want your screen reader to read, in real-time, the characters as they appear onscreen, you can give the delay a try. In general a screen reader will simply repeat the entire text as it’s rewritten to the screen, so I believe that keeping your focus in the Koch trainer window while it is sending is more confusing than helpful. People who see the screen should also experiment with whether they like watching the answers appear, or would rather minimize the program while it’s sending.

When I turn off speech and work with a Braille display, having the characters appear just a quarter second after I copy them is very useful. This is how I practice copying in my head, and for my needs I alternate copying in my head with typing in my copy so I’ll be equally proficient at both.

The remainder of the settings onscreen are best avoided by the beginner, but very useful for ops who need to practice under band conditions. You can turn on QRM and adjust a simulated noise level. You can reduce the signal strength, enable QSB, and even put a chirp on the signal, or have it simulate code sent by a straight key. You can also toggle variable weight, speed and pitch dither , and truly force it to send you Morse that’s not at all easy to decipher!

I’ve describe settings which are always available in this onscreen grid. They are automatically saved as soon as you change them, and when you run the program again, they’ll be configured just as you left them. There is no way I’ve found to return to the program defaults.

If you pull up the setup dialog under the file menu, you can adjust more advanced parameters. You can tell the simulated straight key OP to send with a bad fist. You can control some rigs. You can type in text for it to send.

The only setting I find in this dialog to be useful for the beginner is “session length” which defaults to five minutes. For me, five minutes is tiring and a 2-minute session is plenty. I set “session length” to 2 and have multiple 2-minute practice periods throughout the day. You could also increase the session length, record the output and keep troublesome practice sessions on your music player. (To record within the trainer program, you’ll need to install the Lame MP3 Encoder.)

This setup dialog has no cancel button, so you have to click OK to dismiss it. It also has the effect of saving your settings, so be careful about making changes.

Using the trainer is easy. Click its toolbar Start button, and it will begin randomly sending groups of the letters K and M. Some groups are five characters, some are only 1 or 2.

Most people copy using a pencil and paper. I first switched to a new window and simply typed the results in to Notepad. At the end of a session, which will stop automatically, you are supposed to manually compare your results with the characters that appear in the trainer’s window.

But looking further on Ray’s site, I discovered the helper program KOCH-RX, which must be unzipped and copied to the same directory where the Koch trainer resides. Koch-Rx gives you an edit box where you can type in your copy and a button to compare your results with the text that was sent. You can quickly learn if you are up to the 90% accuracy you need before adding another character. And, Koch-RX adds keyboard control, so you simply tab to a Start and Stop button. Once you click or press Space on Start, your focus is automatically redirected to the edit field where you type in your copy. KOCH-RX therefore is perfect for the screen reader user or anyone who doesn’t want to manually compare their results and calculate percentages!

In the Koch trainer, the results are in an ordinary read-only edit box, which is sandwiched in tab order between the many other check boxes, spin boxes and radio buttons on the grid. Note that screen readers will see it as an unlabeled edit field. Visually, it appears near the bottom of the screen, making it easy to magnify just that results box. It’s also possible to simply park your Braille display in that box, so you can easily view the text after it’s been sent.

And if you are a rank beginner, this is how to learn. Simply focus on the results and watch the characters appear without attempting to copy. You will soon be hearing the difference between the K and M characters and want to start trying to copy them.

Because I already knew the characters, my goal was to learn to copy faster. I first tried setting it to all 40 characters, but found it was like copying off the air. I wasn’t very good. I set it back to 2 characters, and kept increasing the speeds, until I could tell the difference between K and M at 35 words per minute. Then I spun the characters box to 3, and the software added the letter R. I quickly discovered my reflexes weren’t fast enough and I had to drop down to 15 WPM until I could accurately respond to the letter R sent among a forest of Ks and Ms.

I also tried copying in Braille, quickly realizing that though I now could copy some characters at 35WPM, and I can certainly write Braille quickly as well, that combining those two abilities was going to require additional practice. Were I not already a proficient typist, I well might have decided to either stick with writing Braille or simply copying in my head. For now, Braille goes on the back burner, because I’m rarely going to use it in the field.

Though it isn’t mentioned in the literature on Koch, I personally found that knowing when a random group ended and it was time to type a space in my copy was even more difficult than recognizing the individual characters. I tended to type in long strings of characters without spaces. When copying a real QSO it’s pretty easy to insert spaces later, and pick missing characters from context. But having to pay attention to the spacing to know when a random group ends really sharpens your listening!

As you develop speed using Koch, you realize that it’s a lot like jumping rope, dancing, throwing a ball, touch typing, or even handwriting. Though a small child may need to think about how to write the letter W, and might confuse it with M, an adult writes automatically, with no conscious thought. As a fast typist, I can quickly hit the letters Z and X without making mistakes, and without thinking about which finger to use or where to reach. My reflexes have been honed for rapid typing by years of practice.

My CW reflexes still have a way to go, but the plateau has melted and I’ve made more progress in just a few days than I’ve experienced over the years.

As you become yet more advanced, the program, and the G4FON site, also contain files containing over 300 sample test QSOS. Though the code requirement isn’t part of today’s licensing, the original tests are still quite useful for skill-building. You can also download code practice MP3 files at various speeds from the ARRL site.

The Koch trainer gives you that chance to build the reflexes you’ll need to copy real on-the-air QSOS. And once your reflexes take over, you can relax and free your brain to enjoy the conversation.

If you aren’t at a Windows computer the iPhone app, HamMorse, is known to work well with Voice Over, the screen access solution for Apple products. There are also several other Koch training apps for Mac, Android and iOS. You can continue to improve those reflexes while you are out and about.

If you doubt the power of reflexes, just watch a teenager message her friends on her cellphone. She may balk at practicing the piano, and fail to do kitchen chores with the speed and efficiency of her mom, but I bet she can outpace her parents when it comes to texting! If we all view CW practice in the same playful light, we will have our reflexes trained in no time!

(Deborah Armstrong, KF6BKR)

Thoughts on touch screen technology and amateur radio

I recently wrote the following on an email list for blind radio amateurs.  It was in response to concerns about the increasing use of touch screens to replace physical controls.  I thought it would be useful to post here, and might help explain why touch screens, even with full talking accessibility, might not be ideal for all radio applications.

 

If the accessibility has been implemented properly, touch screen technology can be easily used by a blind person, and in the case of the Smartphone, can lead to the use of apps that would never be found with a traditional device.  On this basis I certainly wouldn’t dismiss touch screens out of hand.

 

Saying all that, there is a problem with touch screen technology that I’ve not heard mentioned anywhere else.  Basically, you need to be listening ‘fully’ to know what you are doing.  On a device with voice feedback and traditional buttons, you can probably get most things done with only cursory attention to the voice, because you remember the sequence of physical operation.  Using a touch screen needs you to be listening to the feedback completely at every stage.

 

On a radio, this is not a useful function.  Ideally you will want to make adjustments without any chatter that might distract you from the signal.  I touch on this scenario in my review of the Kenwood TS-590, when pressing the button to hear the sub VFO.  The frequency is announced by the voice every time you press and release the button.  Fortunately, you can turn off the automatic chatter, and it can be seen that Kenwood have given this some careful thought.  Too much talk is as bad as not enough!

 

Turning a silent physical control to adjust say Noise Reduction is likely to be much more  comfortable for a blind operator, than  one being forced to use a chattering touch screen.  It is for this same reason I prefer not to use software, with a talking screen reader,  to control a radio in real time.  The only audio I ideally want to hear is the incoming signal, anything else can be  a distraction <big smile>!

 

Enjoying Amateur Radio despite pain and fatigue

By Quentin Cruse GW3BV

Amateur radio is a hobby and for some an obsession that can be enjoyed by almost anyone. Many people with disabilities enjoy amateur radio as it enables them to communicate with the outside world, gives them a sense of community and brings satisfaction through self education. However what if your health problems mean that you suffer with pain and fatigue? Would this mean that amateur radio is not for you? From personal experience I believe the answer is no.

First of all I must say that as a disabled person you already know that any task or enterprise you undertake, whether its trying to go shopping, having a shower or using your radio will take more energy, time and probably pain than most people will experience. However you endure such difficulties because you are alive and life is worth living. Therefore some of what I describe will take some effort to setup and get started. However the effort will be worth it!

Let’s say that you suffer with a lot of pain, perhaps including headaches. How can you enjoy and contribute towards amateur radio? One of the main issues I have with amateur radio is the noise. I know this may seem an obstacle with a hobby that appears to require you to use your ears, but its not as much of a problem as you may think. When using FM, perhaps on VHF/UHF, static and other QRM/QRN is going to be negligible and you may be able to engage in QSO’s with little difficulty. What though if you want to chase some DX or simply work further afield than your own locality?

To begin with I take the view that if I can only spend 10 or 15 minutes a day tuning across a couple of bands and having just one QSO with someone in a foreign country, I have had a good day. I have indulged my hobby, taken time for myself and learnt a little more about amateur radio and the world around me. However there are ways to do more and for me this mainly involves digital modes.

Digital modes can be found on all of the amateur bands and it is reasonably simple to get started. Most relatively modern rigs going back to the 1990’s will have the necessary ports on the back of the rig to enable connection to a computer. (It is possible to connect an older radio using the headphone socket and PTT line) An interface between the computer and radio will be required but these are available for as little as £30 or less. You will then need to install a suitable program on your computer to decode and transmit digital signals. There are many different ones available. I won’t describe how to set all this up as there are plenty of other guides available online.

The reason digital modes are so useful is that they do not require you to hear or listen to anything. They are primarily a visual mode. The software decodes the signal on your computer screen, normally using what is called a “waterfall” display. This gives a graphical view of the signals available. Clicking your mouse on a signal will cause the software to decode that particular signal. You will then see what the other amateur is sending as text. You can just “listen” or “watch”, reply to a CQ call or put out a call of your own.

I have found PSK31 to be probably the best and most popular digital mode available. It is straightforward to use and you can quickly make a few contacts. There is no need to deal with harsh static and the additional pain and fatigue this can bring. Most software will provide you with macro buttons. These are preprogrammed mini text files that are sent with a click of the mouse which give your details such as QTH, name, equipment etc. All of which should help to make the experience less tiring. In fact it is possible to have a QSO and only need to use the mouse. Most software will enable you to auto-fill the other stations callsign, name etc. into your macros. Additionally most of the software will incorporate a logbook to store your contacts. Some will also link to qrz.com giving you more information about the other amateur.

Another digital mode which I find very rewarding is the WSPR system. This is slightly different in that you do not make QSO’s in the traditional sense. Using WSPR your computer will transmit and receive very low power signals. The WSPR online database is updated by all users in real time. If your signal is heard in VK then the database will let you know. By the same method other amateurs will know if their signal has been heard by you. This system is very much automated, so once setup can be left to transmit and receive whilst you do something else. In my personal case I have often left WSPR running whilst I have a rest. I can then return to the shack after an hour or two and see who has heard my signal and who I have heard. I find it very rewarding and fascinating to track the changes in propagation across different bands over the months. To my mind WSPR is an excellent way to be involved in amateur radio and learning about propagation and aerials even though I am unable to be sat hunched over the radio for hours on end. Again there is a WSPR community which can enhance your enjoyment of this mode.

WSPR Screenshot

WSPR Screenshot

Of course these digital modes can be enjoyed by non licensed radio enthusiasts. They are also primarily low power modes, especially WSPR, so can provide a level playing field for those with foundation licenses.

So does pain and exhaustion have to be a barrier to enjoying the world of amateur radio? I don’t believe so. Most people with disabilities make adjustments to enable them to do different activities. For some it is using a wheelchair to play basketball, for others it will be playing bowls using adapted balls, for those of us in front of a radio it is no different. We simply have to do things in a way which we can manage and yet will still bring pleasure and satisfaction.

For additional information on WSPR visit G4ILO’s excellent website at www.g4ilo.com/wspr.html. Or of course the main WSPR website at www.wsprnet.org

For extra information PSK31 and setting up an interface try www.bpsk31.com and http://www.mymorninglight.org/ham/psk.htm