The previous code would start filling in the clock face as the seconds progressed, but if someone plugged the clock in, it might look incomplete until the clock completed a sweep. I used the same calculations to determine which LEDs should be lit at any given time and send them each cycle.
I used the previous line-pointing code to draw a short hour hand, but it looked awful. The jagged line jumped to the correct place, but the unevenness was distracting. I tried to draw the hand manually, but I kept losing track of which LED I wanted to illuminate, so I opened a CAD file with the lights and added labels for one quadrant. I picked the lights I wanted for each hour and wound up with the center LED going blue whenever the relevant hour was in that quadrant and a little blue triangle to pick out the hour. If it was an hour divisible by 3, like 12, 3, 6, or nine, I drew a line with five LEDs in a row.
I looked into the EEPROM documentation and found the commands to read and write. Then I realized I needed to begin. When that did not work, I opened one example and realized that I needed to commit after a write. Once I had these commands in place, I could set the time zone through a serial port, and it would remember between power cycles. I want to be able to do the same with the wireless settings.
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
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.
2025-05-07
I used the previous line-pointing code to draw a short hour hand, but it looked awful. The jagged line jumped to the correct place, but the unevenness was distracting. I tried to draw the hand manually, but I kept losing track of which LED I wanted to illuminate, so I opened a CAD file with the lights and added labels for one quadrant. I picked the lights I wanted for each hour and wound up with the center LED going blue whenever the relevant hour was in that quadrant and a little blue triangle to pick out the hour. If it was an hour divisible by 3, like 12, 3, 6, or nine, I drew a line with five LEDs in a row.
I looked into the EEPROM documentation and found the commands to read and write. Then I realized I needed to begin. When that did not work, I opened one example and realized that I needed to commit after a write. Once I had these commands in place, I could set the time zone through a serial port, and it would remember between power cycles. I want to be able to do the same with the wireless settings.
 |
| One o'clock showing in blue (1:18 to be precise) |
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
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.
2025-05-07
Comments
Post a Comment