This project was always meant to be an intermediary between sound and video games. While this step was late, it was still relevant. I added a mode that would recognize serial data as the intensity setting. In this way, an automated system, like another Arduino, could tell the EWC how intense to make the music.
Sending serial data is a practical way to automate the intensity setting, and the default method is the onboard potentiometer. Still, I may want to allow users access to the intensity without a computer or the board itself. I added a mode that uses the accessory port to read another potentiometer capable of setting the intensity.
In the same way that I wanted folks to change the intensity, I wanted to provide a way to noodle without access to the core board. Another input on the accessory port was utilized as a remote button. This pin sets up as a sinking input, but it will recognize a rising edge or falling edge based on the startup state.
I capitalized on the universal input recognition code of the noodle button when I built a remote demonstration module. In this enclosure, I used a mechanical switch, whereas the first experiment used a touch-sensitive board. The touch board is active-high, but the switch was active-low, and I did not need to change the code for this. A potentiometer joined the switch to control intensity.
In addition to getting everything working, and even deleting old bugs, I finished this project and consider it a success.
My next project will be automating a children's glockenspiel toy. This is not the first time I've tried to automate an instrument, and it's not the first time I've tried to automate a glockenspiel. At least I don't call it a xylophone anymore. This time, my plan was to suspend a wooden bead across a bow and swing it with a hobby servo. I drafted an example after brainstorming several designs. The model was meant to be made of acrylic and cut on a laser cutter.
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.
Sending serial command
Sending serial data is a practical way to automate the intensity setting, and the default method is the onboard potentiometer. Still, I may want to allow users access to the intensity without a computer or the board itself. I added a mode that uses the accessory port to read another potentiometer capable of setting the intensity.
Remote slider
In the same way that I wanted folks to change the intensity, I wanted to provide a way to noodle without access to the core board. Another input on the accessory port was utilized as a remote button. This pin sets up as a sinking input, but it will recognize a rising edge or falling edge based on the startup state.
(0:11) External trigger on a touch-sensitive pad
I capitalized on the universal input recognition code of the noodle button when I built a remote demonstration module. In this enclosure, I used a mechanical switch, whereas the first experiment used a touch-sensitive board. The touch board is active-high, but the switch was active-low, and I did not need to change the code for this. A potentiometer joined the switch to control intensity.
In addition to getting everything working, and even deleting old bugs, I finished this project and consider it a success.
Complete hardware with external control box
My next project will be automating a children's glockenspiel toy. This is not the first time I've tried to automate an instrument, and it's not the first time I've tried to automate a glockenspiel. At least I don't call it a xylophone anymore. This time, my plan was to suspend a wooden bead across a bow and swing it with a hobby servo. I drafted an example after brainstorming several designs. The model was meant to be made of acrylic and cut on a laser cutter.
Draft of mallet holder
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