I had some trouble with wiggly finger rods, especially when the fastening bolt was loose, so I added a peg to the platform and a slot to the finger rod.
Guided finger rods
I wired up the latest model but managed to break one of the microcontroller pads. A broken input shouldn't be a big problem in the testing phase, and I can always replace the Arduino. I tried a different arrangement with the semi-conductive Velostat plastic, but it didn't pan out.
V0.03 built up
I began tracking the highest and lowest value for each finger. I couldn't just write a few down and code the records because I intentionally have different resistor sizes, resulting in various performances. I wanted code that could accommodate that.
Recognizing low and high values
I moved away from looking at raw input values and wrote the code to consider the upper and lower limits it was recording and basing the current reading on those measurements. In the end, I could print the values as a percentage, which was intuitive.
Printing percentages
The code was advanced enough that I could differentiate between a light touch and a firm press. I added code that would print a single message when it saw a tap, then a new one if it progressed. Before, I was sending a stream of values.
Recognizing different pressures
One of my inputs refused to behave and showed numerous inputs when I only intended a single. I added code required levels to drop below a certain point before it could issue a new command. My erratic behavior became a little sluggish, which was an acceptable trade-off.
Resetting finger input
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
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.
I wired up the latest model but managed to break one of the microcontroller pads. A broken input shouldn't be a big problem in the testing phase, and I can always replace the Arduino. I tried a different arrangement with the semi-conductive Velostat plastic, but it didn't pan out.
I began tracking the highest and lowest value for each finger. I couldn't just write a few down and code the records because I intentionally have different resistor sizes, resulting in various performances. I wanted code that could accommodate that.
I moved away from looking at raw input values and wrote the code to consider the upper and lower limits it was recording and basing the current reading on those measurements. In the end, I could print the values as a percentage, which was intuitive.
The code was advanced enough that I could differentiate between a light touch and a firm press. I added code that would print a single message when it saw a tap, then a new one if it progressed. Before, I was sending a stream of values.
One of my inputs refused to behave and showed numerous inputs when I only intended a single. I added code required levels to drop below a certain point before it could issue a new command. My erratic behavior became a little sluggish, which was an acceptable trade-off.
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
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