It should not have been evident to viewers, but HaD recently migrated sites, and I was left unaware that my article about this Arduboy had been accepted and then published. The tip came while I was chatting with c00p3r of the Dangerous Minds Podcast. The creation was a playable Arduboy that was made on a flexible substrate with capacitive buttons. That meant no moving parts, thin as a sneeze, flexible, and almost unplayable. It was still high on the NEATO factor.
Progress on the Electronic Wind Chimes progressed as quickly as ever. All of the inputs were connected all the way to the controller so they could be monitored by the software. This made it easy to figure out where all the wires were going and assign pins according to where they were wired, even though that did not always agree with the plans.
Carrying the plastic case around delicately and gingerly setting it down became tedious, so an enclosure was made with a handy sheet of plastic, some wood screws and a bunch of LEGO blocks. Despite the asymmetry, this case took a while to build.
The software in the controller was added to show the number of the digital pin being pressed, the clear itself when the button was released. This was important because the code had to be able to act on rising and falling edges, but not be bothered when there were no changes.
Analog inputs were next, and they had problems. This time, the issues were not in the code, but the hardware. Potentiometers were replaced if they output unreliable signals. Three pots were thrown away to substitute working hardware and others changed which pins they used when the first set failed.
Once the analog and digital signals were talking nicely, the screens had to get in on the action. Rising and falling edges for switches and buttons was relatively easy, but getting the code to "rest" when nothing was happening with the potentiometers was not so simple. A jitter factor was added which ignored slight changes with the analog signals. It took a little trial-and-error to find the smallest number which would allow fine control but ignore tiny blips. 0.5% was the sweet spot (5/1024).
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
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.
Progress on the Electronic Wind Chimes progressed as quickly as ever. All of the inputs were connected all the way to the controller so they could be monitored by the software. This made it easy to figure out where all the wires were going and assign pins according to where they were wired, even though that did not always agree with the plans.
Map with IO pins shown
Carrying the plastic case around delicately and gingerly setting it down became tedious, so an enclosure was made with a handy sheet of plastic, some wood screws and a bunch of LEGO blocks. Despite the asymmetry, this case took a while to build.
LEGO case
The software in the controller was added to show the number of the digital pin being pressed, the clear itself when the button was released. This was important because the code had to be able to act on rising and falling edges, but not be bothered when there were no changes.
Identifying pins when activated
Analog inputs were next, and they had problems. This time, the issues were not in the code, but the hardware. Potentiometers were replaced if they output unreliable signals. Three pots were thrown away to substitute working hardware and others changed which pins they used when the first set failed.
Broken hardware
Once the analog and digital signals were talking nicely, the screens had to get in on the action. Rising and falling edges for switches and buttons was relatively easy, but getting the code to "rest" when nothing was happening with the potentiometers was not so simple. A jitter factor was added which ignored slight changes with the analog signals. It took a little trial-and-error to find the smallest number which would allow fine control but ignore tiny blips. 0.5% was the sweet spot (5/1024).
(0:48) Analog and digital sharing one screen
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
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