2014-12-25 (Th) Color/Touch Sensory Panel

The list of improvements and divided tasks was started by adding two registers to each light. These were going to serve as a location of pattern-specific numbers and a bit to go HIGH when transitioning. (*edit - After writing the paper journal but before typing it occurred to me that it would make more sense to have a total of six registers; three for current color and three for desired color. The program could compare the registers to see if a color change is necessary. This would eliminate a lot of instances where the code can falter.)

A start-up sequence was added which ramps up each color in turn then shuts off the lights. This is done to test that each emitter is working properly.

To do:
  1. Build electronics
    1. Solder reed switch
    2. Solder remaining NeoPixels
    3. Solder three more switches
    4. Solder power terminals for transferring power
    5. Solder terminals for accepting power from source
  2. Program Arduino
    1. Make master list of all modes
    2. Add start-up sequence
    3. Add numberOfPanels and numberOfLights (panels x 4) variables
    4. Add three more variables for each color to hold the color it should transition to
    5. Add transitioning sequence which looks at current and intended color then transitions if necessary
    6. Create mode to rotate primary colors & white
    7. Create mode to change all lights when any switch is pressedW
    8. Write digital output code for one or two sounds
    9. Write digital input code for reed switch to change modes 
      1. Eliminate pots
      2. Immediately shows first pattern of scheme when switched
      3. Immediately plays sound if appropriate
      4. Use bounce2 library
  3. Cut and drill polycarbonate sheet
  4. Install switches
  5. Install light hoods
  6. Install electronics
  7. Install polycarbonate and light diffuser sheets

Journal Page

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

A list showing of all the final posts of COMPLETED projects.

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, are 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 claim property or assets based on their post.

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