2019-01-28 (M) ModuKey

It was difficult to tell which layer the keyboard was operating in since the color LEDs were not changing color like I expected. In the previous build, there were only two layers, and that made the color changing work, despite some flaws. In this version, the flawed code would not do anything except turn green. The problem was due to some math where integers were being divided and recorded in a float. Unfortunately, the integer math always resulted in whole numbers, and since I was trying to get a number between zero and one, the result was truncated. Once I translated the integers to floats, the result was predictable and usable, and that resulted in a spectrum of colors when the layer was changed.

Cycling through layers and colors

Once the color changes worked with the layers, the spectrum was expanded so that a more expressive display of colors was seen. This was so that the difference between modes was more noticeable and more mixing was done instead of displaying solid colors. The animation above shows the old range, green, red, and purple. The image below shows how it goes beyond blue, to reach purple, which would never have been seen in the previous revision.

Extended color range

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.