Difference between revisions of "F17: Rolling Thunder"
Proj user2 (talk | contribs) (→Schedule) |
Proj user2 (talk | contribs) (→Schedule) |
||
Line 106: | Line 106: | ||
* <font color="blue"> Test ultrasonic sensors (maxbotix and parallax ping) and identify the suitable one for front and rear. </font color> | * <font color="blue"> Test ultrasonic sensors (maxbotix and parallax ping) and identify the suitable one for front and rear. </font color> | ||
* <font color="green"> Verify basic commands to Traxxas motor, send basic commands (e.g. forward) to RC car from SJOne board. </font color> | * <font color="green"> Verify basic commands to Traxxas motor, send basic commands (e.g. forward) to RC car from SJOne board. </font color> | ||
− | * <font color=" | + | * <font color="orange"> Analyse the communication required across the controllers. |
− | * Design Message IDs based on the priority of the messages and the data to be sent across. | + | * <font color="orange"> Design Message IDs based on the priority of the messages and the data to be sent across. |
− | * Implement the DBC file compatible with all the controllers. | + | * <font color="orange"> Implement the DBC file compatible with all the controllers. |
* Configure GPS device baud rate and interface it with SJOne board using UART. | * Configure GPS device baud rate and interface it with SJOne board using UART. | ||
* Parse data received from GPS device to transmittable format. | * Parse data received from GPS device to transmittable format. | ||
Line 120: | Line 120: | ||
* <font color="blue"> Implement sensor code and perform standalone testing.</font color> | * <font color="blue"> Implement sensor code and perform standalone testing.</font color> | ||
* <font color="green"> Finish motor controller API. Test motor driving in different situations, begin to listen to CAN for controls. </font color> | * <font color="green"> Finish motor controller API. Test motor driving in different situations, begin to listen to CAN for controls. </font color> | ||
− | * <font color=" | + | * <font color="orange"> Establish communication across all the CAN controllers over CAN bus based on the DBC file. |
− | * Verify the power-up interactions between Master and the other controllers | + | * <font color="orange"> Verify the power-up interactions between Master and the other controllers |
* Interface motor to the SJOne board and check for basic functionality. | * Interface motor to the SJOne board and check for basic functionality. | ||
* Interface Compass module with SJOne board using I2C serial bus. | * Interface Compass module with SJOne board using I2C serial bus. | ||
Line 140: | Line 140: | ||
| 11/07/2017 | | 11/07/2017 | ||
| | | | ||
− | * <font color="blue">Filter sensor value readings and send it over the CAN bus to the Master controller. </font color> | + | * <font color="blue"> Filter sensor value readings and send it over the CAN bus to the Master controller. </font color> |
* <font color="green"> Continue testing motor driver via commands from CAN bus. Begin work on LCD display. </font color> | * <font color="green"> Continue testing motor driver via commands from CAN bus. Begin work on LCD display. </font color> | ||
* Calibrate GPS and Compass Module.Develop code for GPS and Compass module communication over CAN . | * Calibrate GPS and Compass Module.Develop code for GPS and Compass module communication over CAN . | ||
Line 162: | Line 162: | ||
* <font color="green"> Finish LCD display. Make adjustments to motor as needed based on testing. </font color> | * <font color="green"> Finish LCD display. Make adjustments to motor as needed based on testing. </font color> | ||
* Verify the stringent requirement of Start-up Sync, Periodic heart-beat messages, Stop car through Bluetooth command. | * Verify the stringent requirement of Start-up Sync, Periodic heart-beat messages, Stop car through Bluetooth command. | ||
− | * Integrate all modules with the Master to test the data flow | + | * <font color="orange"> Integrate all modules with the Master to test the data flow |
* Design the way-point algorithm and start with the implementation. | * Design the way-point algorithm and start with the implementation. | ||
* Design the Navigation Algorithm and start with the implementation. | * Design the Navigation Algorithm and start with the implementation. | ||
Line 174: | Line 174: | ||
| | | | ||
* Implement motor feedback and IO display. | * Implement motor feedback and IO display. | ||
− | * <font color="indigo">Complete the implementation of Android application.</font color> | + | * <font color="indigo"> Complete the implementation of Android application.</font color> |
− | * Interface all the controllers each with additional implemented features | + | * <font color="orange"> Interface all the controllers each with additional implemented features |
− | * Verify the rest of the communication over the CAN bus across the five controllers | + | * <font color="orange"> Verify the rest of the communication over the CAN bus across the five controllers |
* Interface Geo controller and Android controller. | * Interface Geo controller and Android controller. | ||
| Not Started | | Not Started | ||
Line 194: | Line 194: | ||
* <font color="blue">Based on the algorithm for obstacle avoidance test the preciseness of data send from the sensor </font color> | * <font color="blue">Based on the algorithm for obstacle avoidance test the preciseness of data send from the sensor </font color> | ||
* Test the accuracy of check-points from the Bluetooth controller, location data from the Geocontroller sensor and Navigation Algorithm | * Test the accuracy of check-points from the Bluetooth controller, location data from the Geocontroller sensor and Navigation Algorithm | ||
− | * Verify the correct response of each module | + | * <font color="orange"> Verify the correct response of each module |
| Not Started | | Not Started | ||
| | | |
Revision as of 05:52, 10 October 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 |
Schedule
Week # | Start Date | End Date | Task | Status | Actual Date of Completion |
---|---|---|---|---|---|
1 | 09/19/2017 | 09/25/2017 |
|
Completed | 09/25/2017 |
2 | 09/26/2017 | 10/03/2017 |
|
Completed | 10/09/2017 |
3 | 10/09/2017 | 10/16/2017 |
|
In progress | |
4 | 10/16/2017 | 10/30/2017 |
|
Not Started | |
6 | 11/01/2017 |
CAN COMMUNICATION DEMO |
Not Started | ||
7 | 11/01/2017 | 11/07/2017 |
|
Not Started | |
8 | 11/08/2017 |
PROJECT PROTOTYPE DEMO |
Not Started | ||
9 | 11/06/2017 | 11/13/2017 |
|
Not Started | |
10 | 11/13/2017 | 11/29/2017 |
|
Not Started | |
11 | 11/29/2017 |
PROJECT PROTOTYPE DEMO 2 |
Not Started | ||
12 | 11/30/2017 | 12/05/2017 |
|
Not Started | |
13 | 12/07/2017 | 12/15/2017 |
|
Not Started | |
14 | 12/20/2017 |
FINAL PROJECT DEMO |
Not Started | ||
15 | 12/20/2017 |
PROJECT REPORT SUBMISSION |
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.