S14: Need For Speed
Contents
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
Need For Speed
Abstract
An Android Application will be designed such that the tilt of the cell phone will be the motion for the car. Tilting will be first calibrated at zero position and from that position relative tilt of the phone will be captured. These signals from the accelerometer and gyro sensor in the cell phone will be transmitted to the car via Bluetooth. On the car we will be having a Bluetooth adapter connected to the LPC1758 SJ One Board. Moreover, if there is an obstacle in front of the car, then the car will come to a halt state for collision avoidance. This will be achieved with the help of IR sensor mounted in front of the vehicle.The software setup will be such that, we will install ES file explorer from Android Market on the phone. LPC1758 library will be written on Free RTOS. The car will be the device with which the phone has to be paired using Bluetooth. Once the phone and SJ One board is connected, we are ready to play NEED FOR SPEED!!!
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- Amey Patil
- Software Setup
- Android Application Programming
- Siddhata Patil
- Hardware Design
- Android Application Design
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# | Planned Date | Completed Date | Tasks | Status |
---|---|---|---|---|
1 | 3/6 | 3/13 | Planning Hardware and ordering required components | Completed |
2 | 3/20 | Designing and Assembling the Hardware | ||
3 | 3/27 | |||
4 | 4/3 | |||
5 | 4/10 | |||
6 | 4/17 | |||
7 | 4/24 | Testing our Project | ||
8 | 5/1 | Final Project Report | ||
9 | 5/8 |