Difference between revisions of "S14: FaceTime Robo"

Revision as of 23:41, 1 May 2014

Grading Criteria

How well is Software & Hardware Design described?
How well can this report be used to reproduce this project?
Code Quality
Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
  Schematic Quality
- Quality of technical challenges and solutions adopted.

Project Title

FaceTime Robo

Abstract

FaceTime Robo (FTB) is a robot which helps in video chat. With the help of FTB, the user can do video chat without holding cell phone in hand. Now user can do multitask, while chatting with their loved ones. FTB works on face detection algorithm.

Objectives & Introduction

FTB has three different modes. The first mode is Normal mode. In normal mode, FTB just tracks user in the room. If user suddenly disappears from FTB range of view, then it would not be able to follow up with user. Therefore, second mode is developed. The second mode is called autonomous search mode. When FTB is set in autonomous search mode, then it keeps searching for user in the room. On finding the user, FTB automatically resumes normal mode. FTB also has voice recognition feature built in. FTB wakes up/sleep on user vocal command. The Third mode is sound localization mode. In this mode, user just calls FTB name and FTB turns into that direction and starts searching for user. The FTB uses It’s artificial intelligence to determine the direction of sound and turns into that direction.

Team Members & Responsibilities

Team Member
- Himanshu Saini
  - Hardware Design
  - Driver Development
  - Software Design
  - Integration and Test
  - Project Documentation

Schedule

Week#	Date	Task	Actual
1	02/27/2014	Rough Estimation of parts required in project	Done
2	03/06/2014	Parts Ordered	Done
3	03/13/2014	PWM and ADC Driver	Done
4	03/20/2014	Individual Testing of each parts	Done
5	04/03/2014	Implementation of face recognition algorithm	Done
6	04/10/2014	Windows driver development	Done
7	04/17/2014	Integration of project with RTOS	Done
8	04/24/2014	Sound localization testing	Done
9	05/01/2014	Complete testing of system starts	Done

Parts List & Cost

The table below summarizes the parts used and the cost for the project.

Ref Number	Part Number	Description	Qyt	Cost
1	SJ one Board	SJSU development board, LPC1758	1	$75
2	Servos	For Pan/Tilt Mechanism	2	$40
3	Microphones	For Sound Localization	2	$25
4	Webcam	Microsoft Webcam	1	$25
5	Wires	Length: 0.5', 0.3', and 1.00' feet	25	$35
6	Acrylic sheets	1 X 1 feet	1	$30
7	USB to Serial Converter	Converter	1	$20
8	Other Miscellaneous Stuffs	Stands and Screws	15 Screws and 8 Stands	$30
9	Brackets	For Pan/Tilt	2	$10
10	Velcro	Size 1 X 1 feet	1	$20

Design & Implementation

Hardware Design

The hardware design of FTB is consists of three layers. The very top layer of FTB has two servo motors, which are placed in such a way so that pan/tilt mechanism can easily be obtained. Bottom servo rotates from left to right. Top servo rotates up and down. The top servo has a bracket attached which has a Velcro on it. The reason of putting Velcro on bracket is to easily place or remove cell phone from FTB. The top layer of FTB also has a camera attach to the bracket. The camera also has inbuilt microphone. There are two more separate microphones on the top layer for sound localization.

The second layer of FTB is consists of breadboards, switches, power supply.

The third layer of FTB is consists of SJ One Board.

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

Send me your zipped source code and I will upload this to SourceForge and link it for you.

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.