S15: Hand Gesture Recognition using IR Sensors
Contents
Abstract
The aim of the project is to develop hand gesture recognition system using grid of IR proximity sensors. Hand gestures like pan, thumbs-up, moving hand back and forth, up and down or left and right can be recognized. These gestures can be used to control different devices or can be used in various applications.The system will recognize different hand gestures based on the IR proximity sensor values.
Objectives & Introduction
The idea is to make a 3x3 grid of using IR proximity sensors, and connect them via analog multiplexers to the ADC pins on SJONE board. As we move our hand in front of the sensor grid, the corresponding values of the sensors will change in a specific pattern. We will map this specific change in values to a gesture. Similarly we will be able to map gestures such as swipe left, swipe right, swipe up and swipe down.
IR Sensors- For the project we are using sensors manufactured by Sharp to determine distance from the objects. The sensors have a range from 10 to 80 cm. The analog voltage output varies with the distance of the object, it is 3 Volts when an object is 10 cm away while it is 0.4v when object is 80 cm away. The ideal operating voltage for the sensor is 4.5 to 5.5 volts.
Analog Multiplexers- We are also using 3 Analog 4:1 multiplexers. This is because SJONE board only has 3 ADC pins where as our sensor grid consists of 9 sensors. The GPIO pins of SJONE board will act as select lines to the multiplexers. The select lines will be common to all multiplexers.
Team Members & Responsibilities
- Harita Parekh
- Implementing algorithm for gesture recognition
- Implementation of sensor data filters
- Shruti Rao
- Implementing algorithm for gesture recognition
- Interfacing of sensors, multiplexers and controller
- Sushant Potdar
- Implementation of final sensor grid
- Development of the application module
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 3/22/2015 | 3/28/2015 | Research on the sensors, order sensors and multiplexers | Completed | 3/28/2015 |
| 2 | 3/29/2015 | 4/4/2015 | Read the data sheet for sensors and understand its working. Test multiplexers | Completed | 4/4/2015 |
| 3 | 4/5/2015 | 4/11/2015 | Interfacing of sensors, multiplexers and controller | Completed | 4/15/2015 |
| 4 | 4/12/2015 | 4/18/2015 |
|
Ongoing | |
| 5 | 4/19/2015 | 4/25/2015 |
|
Scheduled | |
| 6 | 4/26/2015 | 5/2/2015 |
|
Scheduled | |
| 7 | 5/3/2015 | 5/9/2015 | Testing and bug fixes | Scheduled | |
| 8 | 5/10/2015 | 5/16/2015 | Testing and final touches | Scheduled | |
| 9 | 5/25/2015 | 5/25/2015 | Final demo | Scheduled | |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
