2018-08-30 (Th) Emergency Rotary Keyboard EmerKeyB

An Arduino Beetle clone was connected and the programming was modified from the code necessary for a Digispark. The new controller didn’t use the digikeyboard library and it allowed a simultaneous serial connection. USB connection on the Beetle clone was built into the board and was not entirely reliable when any pressure was placed on the board. A USB extension cable could help with that.

Connected microcontroller

Reading the encode inputs was significantly easier with the new microcontroller. Using a serial connection allowed for much faster readings and accuracy seemed to increase as well. There were a few errant readings but that could be partially due to the quality of encoder.

Encoder outputs

An array of letters was created for ‘typing’ with the keyboard as a test to ensure the project could send different keyboard commands to the computer. This worked well but the first command would always send a backspace which was not acceptable. Mistakenly, a line was added to type the first letter in the array but it typed the letter on every cycle of the code which was significantly faster than the keyboard repeat function. The computer protected itself by disabling the USB port, assuming it was an attack. The code should be fixed but reprogramming the board hasn’t been possible. It may be necessary to use a different controller of the same model and put in good code.

Problematic feedback

The rest of the posts for this project have been arranged by date.

First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.