2019-02-27 (W) ModuKey

Modifier key functions, like Alt and Ctrl, were sketched out but they were not consistent with the programming. Part of the problem was that they behaved exactly the same except in layer two. If this layer had been identical, programming would have been more straightforward. Black text on white plastic made for easy to read labels that were made with an ordinar label maker.

Stickers on modifier keys

Layer three was checked out. This layer had some mouse functionality, such as movement and clicking. The up and down movement was reversed at first, and the buttons would not repeat so the mouse would simply move a short distance each time the button was pressed or held. A double-click button was also programmed, but it would click the center button which was also corrected. Layer three also has a function where pseudo-random numbers are generated in the same ranges as D20 dice. These number generators were tested and found to be working but testing the full range of a D1000 did not happen.

After being away from the keyboard for a bit, some problems cropped up that were not visible before, like how one of the layer-shift buttons would not return to layer one when released. Only one of the four behaved like this, and it was corrected.

Issues and resolution notes

Pseudo-random tones arranged on a musical scale were played during startup. The random seed is pulled from an unpopulated analog input, and subsequent notes are generated from there. If the analog input reads the same each time, the startup will sound the same. Better prandom number generation would make for more diverse startup sounds. A three-second video is below which has the sound from the startup.

(0:03) Startup sounds

ModuKey on GitHub

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/

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

All information on 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.