The programming cable for the Arduino Mini Pro was loaned to Joe Robertson for the Arduino Laser Tag project so it was not available. The Arduino Mini Pro was was removed from the prototyping board and jumper test wires were run between the relevant pins of each board.
The pseudo random color code was rewritten as a function and changed from writing the pseudo random variables directly to the NeoPixels and first writes them to part of a 2D integer array then writes them to the NeoPixel. This way the current color is stored on the controller which will be important for other color changing routines such as RAINBOW.
The second, third, and fourth switch positions were tested but failed because they were not connected. These connections were soldered then tested well in the program.
The rest of the posts for this project have been arranged by date.
This blog, including pictures and text, is copyright to Brian McEvoy.
Arduino boards connected with jumper test wires
The pseudo random color code was rewritten as a function and changed from writing the pseudo random variables directly to the NeoPixels and first writes them to part of a 2D integer array then writes them to the NeoPixel. This way the current color is stored on the controller which will be important for other color changing routines such as RAINBOW.
The second, third, and fourth switch positions were tested but failed because they were not connected. These connections were soldered then tested well in the program.
To do:
- Build all light hoods
- Build electronics
- Program Arduino
- Break up tasks
- Sketch pseudo-code
Write code for first switch and 4 NeoPixels- Buy, drill, and cut polycarbonate sheet
- Install switches
- Install light hoods
- Install electronics
- 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.
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 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.
Comments
Post a Comment