2019-02-06 (W) ModuKey

Many of the loose ends, like layer and style notifications, had been tied up, so it was time to get back to verifying the layers and ensuring that all the keys did what they were supposed to be doing. Layer one had been getting quick fixes along with the rest of the coding as it was convenient, but it had not been successfully tested from start to finish. This test turned out well and confirmed that the little fixes were done well. Layer one, the usual typing layer, was operational except for a keyswitch which needs to have the solder joints redone.

Layer two was checked. This layer used the right half as a NUMPAD, arrow keys, and some of the other navigation keys like HOME, END, PAGE UP, and PAGE DOWN. These will likely be used with the layer shifting keys while the left side of the keyboard had functions and macros associated with Audacity. A few things needed attention and were tracked on the paper shown below. Some of the keys on board 7 needed to be rearranged, and one key turned the lights red. The red lights were a small code remnant that was removed, and the problematic keys were rearranged. At first, only the button presses were corrected so there was a time when the ESCAPE key was held for a full minute and it only caused problems.

Layer two was fixed up in a single day, and this whole post was written with only the Lazy Brown Dog keyboard, including the 7 above which was typed with the NUMPAD on layer two and the seven in this paragraph which was from the main keyboard on layer 1.

Worksheet for fixing layer 2

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.