Difference between revisions of "F17: Rolling Thunder"
Proj user2 (talk | contribs) (→Schedule) |
Proj user2 (talk | contribs) (→Schedule) |
||
Line 206: | Line 206: | ||
* <font color="indigo"> Add Google Earth/Maps to the Android app for selecting the car's destination.</font color> | * <font color="indigo"> Add Google Earth/Maps to the Android app for selecting the car's destination.</font color> | ||
* <font color="indigo"> Send car location to app and check points received to Geo module.</font color> | * <font color="indigo"> Send car location to app and check points received to Geo module.</font color> | ||
− | * <font color="brown"> Test each module individually | + | * <font color="brown"> Test each module individually </font color> |
− | * <font color="brown"> Verify the stringent requirement of Start-up Sync, Periodic heart-beat messages. | + | * <font color="brown"> Verify the stringent requirement of Start-up Sync, Periodic heart-beat messages.</font color> |
* Start adding contents to the relevent sections of wiki. | * Start adding contents to the relevent sections of wiki. | ||
| In progress | | In progress | ||
Line 231: | Line 231: | ||
* <font color="indigo"> Consistently communicate current car location to App, get check points from App and relay them to Geo module.</font color> | * <font color="indigo"> Consistently communicate current car location to App, get check points from App and relay them to Geo module.</font color> | ||
* <font color="indigo"> Send additional vehicle status information from can bus to the app for display.</font color> | * <font color="indigo"> Send additional vehicle status information from can bus to the app for display.</font color> | ||
− | * <font color="brown"> Field test and check for obvious issues in obstacle avoidance, navigation, maintaining speed (up/down hill). | + | * <font color="brown"> Field test and check for obvious issues in obstacle avoidance, navigation, maintaining speed (up/down hill).</font color> |
− | * <font color="brown"> Provide feed backs to each team on identified short comings. | + | * <font color="brown"> Provide feed backs to each team on identified short comings.</font color> |
* Update wiki with details. | * Update wiki with details. | ||
| Not started | | Not started | ||
Line 251: | Line 251: | ||
* <font color="orange"> Improvise steering logic based on field tests under various conditions and locations. </font color> | * <font color="orange"> Improvise steering logic based on field tests under various conditions and locations. </font color> | ||
* <font color="red"> Analyse field test results to re-calberate GPS offset values if required.</font color> | * <font color="red"> Analyse field test results to re-calberate GPS offset values if required.</font color> | ||
− | * <font color="indigo"> Complete the CAN information display activity of App (To help in field testing without the PCAN cable) | + | * <font color="indigo"> Complete the CAN information display activity of App (To help in field testing without the PCAN cable). </font color> |
− | * <font color="brown"> Test the accuracy of check-points from the Bluetooth controller, location data from the Geo-controller sensor and Navigation Algorithm. | + | * <font color="brown"> Test the accuracy of check-points from the Bluetooth controller, location data from the Geo-controller sensor and Navigation Algorithm. </font color> |
− | * <font color="brown"> Check overall robustness of the complete system. | + | * <font color="brown"> Check overall robustness of the complete system. </font color> |
* Update wiki with details. | * Update wiki with details. | ||
| Not started | | Not started |
Revision as of 07:45, 6 November 2017
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.
Rolling Thunder
Abstract
This section should be a couple lines to describe what your project does.
Objectives & Introduction
Team Members & Responsibilities
- Central Controller
- Akil Khan
- Jerry John
- Geographical Controller
- Abhilash Tuse
- Vishal Rajendra Shrivastava
- Communication Bridge + Android Application
- Akinfemi Akin-Aluko
- Johnny Nigh
- Motor and I/O Controller
- Saurabh Ravindra Badenkal
- Joshua Skow
- Sensor Controller
- Sona Bhasin
- Thrishna Palissery
- QA Team
- Akil Khan
- Saurabh Ravindra Badenkal
Legend
Color | Component |
---|---|
Blue |
Sensor Controller |
Green |
Motor/IO Controller |
Red |
Geographical Controller |
Orange |
Central Controller |
Indigo |
Communication Bridge + Android Application |
Brown |
QA |
Schedule
Start Date | End Date | Task | Status | Date of Completion | |
---|---|---|---|---|---|
1 | 09/20/2017 | 09/26/2017 |
|
Completed | 09/26/2017 |
2 | 09/27/2017 | 10/03/2017 |
|
Completed | 10/03/2017 |
3 | 10/04/2017 | 10/10/2017 |
|
Completed | 10/10/2017 |
4 | 10/10/2017 | Wiki Schedule | Completed | 10/10/2017 | |
5 | 10/11/2017 | 10/17/2017 |
|
Completed | 10/17/2017 |
6 | 10/18/2017 | 10/24/2017 |
|
Completed | 10/24/2017 |
7 | 10/24/2017 | DBC File | Completed | 10/24/2017 | |
8 | 10/24/2017 | DEMO: CAN communication between controllers | Completed | 10/24/2017 | |
9 | 10/25/2017 | 11/28/2017 |
|
In progress | |
10 | 11/01/2017 | 11/07/2017 |
|
In Progress | |
11 | 11/07/2017 | DEMO: Motors driven by wheel feedback and sensors
Final Wiki Schedule |
In Progress | ||
12 | 11/08/2017 | 11/14/2017 |
|
In progress | |
13 | 11/14/2017 | DEMO: Basic obstacle avoidance | In progress | ||
14 | 11/15/2017 | 11/21/2017 |
|
Not started | |
15 | 11/21/2017 | DEMO: GPS driving | Not started | ||
16 | 11/22/2017 | 11/28/2017 |
|
Not started | |
17 | 11/29/2017 | 12/19/2017 |
|
Not started | |
18 | 12/20/2017 | DEMO: Final Project
SUBMISSION: Final Project Wiki |
Not started |
Parts List & Cost
Item # | Description | Distributor | Qty | Cost |
---|---|---|---|---|
1 | SJOne Board | Provided by Preet | 5 | $400 |
2 | RC Car - Traxxas 1/10 Slash 2WD | Amazon | 1 | $189.95 |
3 | Bluetooth Bee BLE 4.0 Module | ebay | 1 | $15 |
4 | GPS Module | Amazon | 1 | $28.99 |
5 | Compass (CMPS11) | Acroname | 1 | $45.95 |
6 | Traxxas 6520 RPM Sensor | Amazon | 1 | $10.82 |
7 | Traxxas 2991 LiPo Battery and Charger | Amazon | 1 | $199.95 |
8 | Breadboard Jumper Wires | Amazon | 1 | $6.99 |
9 | MIFFLIN Acrylic Plexiglass Clear Plastic Sheet | Amazon | 1 | $9.89 |
10 | Printed Circuit Board | Amazon | 1 | $16.83 |
11 | PCB Mounting Feet Set | Amazon | 1 | $11.99 |
12 | Traxxas 6538 Telemetry Trigger Magnet Holder | Amazon | 1 | $4.63 |
13 | MB1240 XL-MaxSonar EZ4 Ultrasonic Sensor | Amazon | 2 | $73.90 |
14 | Parallax Ping Ultrasonic Range Sensor | Amazon | 2 | $69.98 |
15 | CAN Transceiver | Microchip | 10 | $10.00 |
16 | 4D systems 32u LCD | 4D Systems | 1 | $79.00 |
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:
<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.