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
This page contains design and implementation of our Embedded Software project, Need For Speed. It's about maneuvering an RC vehicle using the Acceleration Sensor in a smart phone. An Android Application is developed to transmit the Acceleration Sensor Signals to the vehicle via Bluetooth. The car is mounted with a Bluetooth module to receive data from the phone. And the acceleration and turning of the vehicle will be based on this data.
The vehicle is also mounted with two Infrared Sensor modules for collision detection, one in the front and other in the rear.Detection of any obstacle in the vehicles path will bring the vehicle to a halt state immediately.
Introduction
In this project we are using JY-MCU Bluetooth module to be the wireless link between the smartphone and the battery powered RC vehicle. The Android application is developed to transmit a particular byte for every threshold value of the Acceleration Sensor i.e. when the phone is one byte for front tilt and another for back. This received byte is compared by the SJOne board with few predefined values and accordingly PWM signals are given to the motors.
The input of the IR sensors is connected to the hardware interrupts on the SJOne board, the interrupt subroutine will be called every time there is an obstacle in the path of the vehicle, this subroutine will in turn stop the vehicle.
Objectives
As this project is both software and hardware based, our objectives were as follows;
- Hardware Objectives
- To achieve a constant 6V DC supply for the motors and 5V DC for the board from the battery.
- To interface the motors to the SJOne board via L298 motor driver.
- To calibrate the IR sensors to sense obstacle in 6" proximity.
- Software Objectives
- To develop an Android application to send the data from Acceleration Sensor via Bluetooth.
- To develop a FreeRTOS code to receive these signals and process them.
- To develop a FreeRTOS code to send PWM sigal to the motor for variable speed.
- To develop a FreeRTOS code to accept interrupt from the IR sensors and take actions accordingly.
Team Members & Responsibilities
- Amey Patil
- Hardware Design
- Free RTOS (Part 1: To interface motors and LPC1758 using PWM)
- Android Application(Part1: To send data from Android Phone to LPC1758)
- Siddhata Patil
- Free RTOS (Part 2: To form pairing of LPC1758 and Bluetooth module)
- Free RTOS (Part 3: To send and receive data between Bluetooth module and LPC1758)
- Android Application(Part2: To send results of accelerometer sensor from Android Phone to LPC1758)
Schedule
| Week# | Planned Date | Completed Date | Tasks | Status |
|---|---|---|---|---|
| 1 | 3/6 | 3/13 | Planning Hardware and placing order for the required components | Completed |
| 2 | 3/20 | 3/20 | Designing and Assembling the Hardware(Motors+Motor Driver+LPC1758) | Completed |
| 3 | 3/20 | 3/20 | Reviewing Datasheet, Pin Selection and Setting up the Software | Completed |
| 4 | 3/27 | 3/27 | Designing and Assembling the Hardware(Bluetooth Module+LPC1758) | Completed |
| 5 | 3/27 | 3/27 | Free RTOS pairing between LPC1758 and Bluetooth Module | Completed |
| 6 | 3/28 | 3/28 | Testing the pairing of Bluetooth and LPC1758 | Completed |
| 7 | 4/3 | 4/3 | Free RTOS code for PWM | Completed |
| 8 | 4/11 | 4/18 | Free RTOS code for sending and receiving data from Bluetooth | Completed |
| 9 | 4/18 | 4/24 | Android App Designing and learning basics of Android SDK | Completed |
| 10 | 4/24 | 4/24 | Android App Designing | Completed |
| 11 | 5/1 | Android App java code to transfer data from phone to LPC1758 | ||
| 12 | 5/1 | Android App java code to send values of accelerometer sensor to LPC1758 | ||
| 13 | 5/1 | 5/ | Final Project Report | |
| 14 | 5/8 | 5/8 | Final Demo |
Parts List & Cost
| Category | Item | Quantity | Unit Cost | Total Cost |
|---|---|---|---|---|
| Electronics | SJOne Board | 1 | 80.00 | 80.00 |
| 9.6V 1600mAh Rechargeable Ni-Mh Battery | 1 | 14.42 | 14.42 | |
| 6V DC Gear Motor with Tyres | 4 | 3.25 | 13.00 | |
| JY-MCU Bluetooth Module | 1 | 7.68 | 7.68 | |
| IR Transceiver Module | 2 | 1.00 | 2.00 | |
| L298 Motor Driver | 1 | 7.50 | 7.50 | |
| LM 7806 Voltage Regulator | 1 | 0.45 | 0.45 | |
| LM 7805 Voltage Regulator | 1 | 0.32 | 0.32 | |
| 10uF Electrolytic Capacitor | 2 | 0.13 | 0.26 | |
| 1uF Ceramic Capacitor | 2 | 0.10 | 0.20 | |
| Chassis | Smart Car Chassis | 1 | 10.00 | 10.00 |
| Connections | Nuts, Bolts and Spacers | 3.00 | ||
| Phone | Android Smart Phone | 1 | ||
| TOTAL | $138.83 |
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
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.
