Difference between revisions of "S19: Zeus"
Proj user17 (talk | contribs) (→Sensors Controller) |
Proj user17 (talk | contribs) (→Sensors Controller) |
||
Line 408: | Line 408: | ||
== Sensors Controller == | == Sensors Controller == | ||
− | In this project, the sensor we use is LV-MAXSonar- | + | In this project, the sensor we use is LV-MAXSonar-EZ4, which is ultrasonic sensor. There are three sensors put in the front of our RC car and detect the left, middle and right side independently. |
=== Hardware Design === | === Hardware Design === | ||
Discuss your hardware design here. Show detailed schematics, and the interface here. | Discuss your hardware design here. Show detailed schematics, and the interface here. |
Revision as of 03:39, 17 May 2019
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
Zeus : The Autonomous Car
Abstract
When over a century ago Karl Benz invented the first car, it came as a miracle to people. Now, Almost every household owns a car. The industry has come from a 20 Horse power producing 2.9 liter Ford Model T (1908) to a massive 1500 Horsepower 5 liter Koenigsegg Regera (2018). And as such, further developments into the driving industry are bound to come. One such major field is the realm of Driverless smart cars. This project focuses on developing a driverless smart car(model) that is capable of going from one place to the destination without any manual input, avoiding obstacles along the way.
Objectives & Introduction
Zeus revolves around several SJone boards that have LPC 1758 at the center......(continue here). Following are the objectives of this project.:
- Zeus should successfully navigate from a fixed starting point to a fixed destination based on GPS.
- Obstacles on the way should be avoided.
- Code should be 100% Unit-Tested
- Communication should be established between Zeus and a mobile phone through an APP.
Team Members & Responsibilities
- Neel Patel
- Team Lead
- Master Module
- Android App
- BLE Module
- Himanshu Gunjal
- Master Module
- BLE Module
- Oliver Zhu
- GIT repository Manager
- Sensor Module
- Aman Chandan
- Material/ Components manager
- GEO module
- Karan Daryani
- Car Layout Designer
- Motor Module
- PCB
- Namdev Prabhugaonkar
- GEO module
- PCB
- Artik Shetty
- Motor Module
- Wendy Chao
- Sensor Module
Schedule
Week# | Date | Task | Activities | Status | Completion Date |
---|---|---|---|---|---|
1 | 02/12/19 |
|
|
|
|
2 | 02/19/19 |
|
|
|
|
3 | 02/26/19 |
|
|
|
|
4 | 03/05/19 |
|
|
|
|
5 | 03/12/19 |
|
|
|
|
6 | 03/19/19 |
|
|
|
|
7 | 03/26/19 |
|
|
|
|
8 | 04/02/19 |
|
|
|
|
9 | 04/09/19 |
|
|
|
|
10 | 04/16/19 |
|
|
|
|
11 | 04/23/19 |
|
|
|
|
12 | 04/30/19 |
|
|
|
|
13 | 05/07/19 |
|
|
|
|
14 | 05/14/19 |
|
|
|
|
15 | 05/22/19 |
|
|
|
|
Parts List & Cost
Item# | Part Description | Vendor | Qty | Cost $ |
---|---|---|---|---|
1 | RC Car | Sheldon's Hobby Store | 1 | 180.00 |
2 | SJOne board | Preet | 5 | 400.00 |
3 | GPS Module | 1 | ||
4 | Lipo Battery (7200 mAh) | Amazon | 1 | 37.99 |
5 | DB9 Connector | Amazon | 1 | 6.50 |
6 | LIPO Battery Charger | Sheldon's Hobby Store | 1 | 39.99 |
7 | Ultrasonic sensor | Robotshop | 4 | 99.80 |
8 | PCB | |||
9 | CAN Transceiver | Amazon | 5 | 49.95 |
10 | LCD Display | Obtained From Preet | 1 | Free |
11 | Xbee | Obtained From Preet | 1 | Free |
12 | Adapter for Lipo Charger | Amazon | 1 | 15.84 |
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.
Sensors Controller
In this project, the sensor we use is LV-MAXSonar-EZ4, which is ultrasonic sensor. There are three sensors put in the front of our RC car and detect the left, middle and right side independently.
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:
<Bug/issue name>
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.