I downloaded the VibeClock REV1 program, but initially, there was no light activity until I cleared a short between the signal and power, resulting in the first sixty LEDs lighting up in a pie-slice shape. I wrote a multidimensional array with the first locations separated by ring number. After debugging, my testing function turned on the lights one ring at a time while cycling through colors.
I needed a function that would return the address of any LED when I supplied a ring and position. The function also needed to respond to the position "-1" with the last light on the ring. I started with a purpose-built function that focused on the 60-light ring, responded to seconds, and then moved to the goal. There was some messy math, but I got it working.
I used yesterday's function, which translated a ring and position into the address of any LED. With this ability, I could calculate a line based on the time and number of lights in a ring. Unfortunately, the line was unsettlingly jagged. The effect may be less abrupt when there is a border between two colors.
I converted the line-drawing function into one that changed the clockface from one color to another. I tweaked a few settings to make it look nice, and I was delighted that it looked more purposeful than the squiggly line I had yesterday.
I got the hour hand functioning, but it was a blue dot with a floating triangle unless the hour was divisible by three, in which case I could connect four LEDs in a row. I got the non-volatile memory working so I can set the time zone and retain that value after a power cycle.
Sarah, Amanda, and I welcomed Chris from Home Brewed Comics to discuss his upcoming comic, C.R.I.T. and Thunderbolts*. The show peaked when Amanda pulled the loose story threads we missed or ignored.
The rest of the summary posts 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
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
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 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.
![]() |
Rings changing colors |
I needed a function that would return the address of any LED when I supplied a ring and position. The function also needed to respond to the position "-1" with the last light on the ring. I started with a purpose-built function that focused on the 60-light ring, responded to seconds, and then moved to the goal. There was some messy math, but I got it working.
![]() |
Code for turning on LEDs in a continuous ring |
I used yesterday's function, which translated a ring and position into the address of any LED. With this ability, I could calculate a line based on the time and number of lights in a ring. Unfortunately, the line was unsettlingly jagged. The effect may be less abrupt when there is a border between two colors.
![]() |
A line traveling at one increment per second |
I converted the line-drawing function into one that changed the clockface from one color to another. I tweaked a few settings to make it look nice, and I was delighted that it looked more purposeful than the squiggly line I had yesterday.
![]() |
Filling the clock with red lights |
I got the hour hand functioning, but it was a blue dot with a floating triangle unless the hour was divisible by three, in which case I could connect four LEDs in a row. I got the non-volatile memory working so I can set the time zone and retain that value after a power cycle.
![]() |
One o'clock showing in blue (1:18 to be precise) |
Sarah, Amanda, and I welcomed Chris from Home Brewed Comics to discuss his upcoming comic, C.R.I.T. and Thunderbolts*. The show peaked when Amanda pulled the loose story threads we missed or ignored.
Critical Affection:Thunderbolts* (1:40)
The rest of the summary posts 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
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
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 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.
Comments
Post a Comment