2019-06-18 (Tu) PillarGame

Testing addressable LEDs required a program, and I made a list of all the things I wanted to test, and I had a solid idea of how to experiment with everything. Most of the time, it was a simple matter of turning on the bare LEDs OR the lensed LEDs with different colors.

The test programming could have used a single button, but it was easy enough to use two buttons. Nine different tests were outlined, and each test had at least two states. One button would change the test being performed, and the second button incremented the state of the test.
Breadboarded controller

The first test was to simultaneously turn on the first LED in each strip as a single color, and the second button would increment which light was on by going down the line. This way, the bare LEDs could be on for a bit then switched to the lensed LEDs to see which looked better. The next three tests were the same routine but used different colors and white. The light from the lights with lenses appeared cleaner, but the diffused light filled in the white paper more fully.
Bare green LEDs
Green lensed LEDs

Another test turned on all the lensed lights OR the bare ones and swapped each time the function button was pressed. This was similar to the first tests but easier to compare adjacent LEDs by quickly toggling them.

The final test was to assign every light a prandom color, red, green, or blue and reshuffle each time the function button was changed.

I assumed I would have to suspend the paper an inch (25mm) away from the lights when using lenses, but it was closer to 1/2" (12mm), so this testing was informative.
RGB prandom mode

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
Completed projects from year 6

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.