Difference between revisions of "F17: Rolling Thunder"
From Embedded Systems Learning Academy
Proj user2 (talk | contribs) (→Schedule) |
Proj user2 (talk | contribs) (→Schedule) |
||
| Line 61: | Line 61: | ||
| | | | ||
* Set up project Git and Wiki page. | * Set up project Git and Wiki page. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Study the hardware specifications of each module and review them for hardware errors | * Study the hardware specifications of each module and review them for hardware errors | ||
* Study the datasheet for the components and come up with pin diagrams | * Study the datasheet for the components and come up with pin diagrams | ||
* Understand the hardware interfacing of each of the modules and test compatibility | * Understand the hardware interfacing of each of the modules and test compatibility | ||
* Analyse power requirements | * Analyse power requirements | ||
| − | | | + | | Completed |
| − | | 10/ | + | | 10/09/2017 |
|- | |- | ||
| − | ! scope="row"| | + | ! scope="row"| 3 |
| 10/12/2016 | | 10/12/2016 | ||
| 10/18/2016 | | 10/18/2016 | ||
| | | | ||
* Analyse the communication required across the controllers. | * Analyse the communication required across the controllers. | ||
| − | * < | + | * <font color="orange">Design Message IDs based on the priority of the messages and the data to be sent across. </span> |
| − | * | + | * Implement the DBC file compatible with all the controllers. </span> |
| − | * | + | * Interface GPS module with SJOne board. Firmware development and NMEA sentence parsing.</span> |
| In progress | | In progress | ||
| 10/18/2016 | | 10/18/2016 | ||
|- | |- | ||
| − | ! scope="row"| | + | ! scope="row"| 4 |
| 10/19/2016 | | 10/19/2016 | ||
| 11/01/2016 | | 11/01/2016 | ||
| Line 92: | Line 85: | ||
* Establish communication across all the CAN controllers over CAN bus based on the DBC file. | * 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 | * Verify the power-up interactions between Master and the other controllers | ||
| − | * | + | * Check the sensor functionality stand-alone with a minimal driver. </span> |
| − | * | + | * Interface motor to the SJOne board and check for basic functionality. </span> |
| − | * | + | * Interface Compass module with SJOne board. Firmware development and stand-alone testing. </span> |
| − | * | + | * Work on Bluetooth firmware development to integrate with SJ one board. </span> |
| Not Started | | Not Started | ||
| 11/01/2016 | | 11/01/2016 | ||
| Line 110: | Line 103: | ||
| 11/07/2016 | | 11/07/2016 | ||
| | | | ||
| − | * | + | * Read sensor values and filter the readings. Prepare sensor values to be sent over the CAN bus to the Master controller. </span> |
| − | * | + | * Integrate LCD and motor. Implement code for all the transactions of motor and LCD over CAN. </span> |
| − | * | + | * Calibrate GPS and Compass Module.Develop complete code for GPS and Compass module communication over CAN </span> |
| − | * | + | * Develop basic Android application to work with the Bluetooth module. Test the communication between SJOne board and Android application over Bluetooth protocol. </span> |
| − | * | + | * Design the Obstacle avoidance and start with basic implementation. </span> |
| Not Started | | Not Started | ||
| 11/01/2016 | | 11/01/2016 | ||
| Line 130: | Line 123: | ||
| | | | ||
* Test each module individually for accurate functionality based on communication with the Master | * Test each module individually for accurate functionality based on communication with the Master | ||
| − | * | + | * Verify the stringent requirement of Start-up Sync, Periodic heart-beat messages, Stop car through Bluetooth command. </span> |
* Integrate all modules with the Master to test the data flow | * Integrate all modules with the Master to test the data flow | ||
| − | * | + | * Design the way-point algorithm and start with the implementation. </span> |
| − | * | + | * Design the Navigation Algorithm and start with the implementation. </span> |
| Not Started | | Not Started | ||
| 11/08/2016 | | 11/08/2016 | ||
| Line 141: | Line 134: | ||
| 11/29/2016 | | 11/29/2016 | ||
| | | | ||
| − | * | + | * Implement motor feedback and IO display. </span> |
| − | * | + | * Complete the implementation of Android application. </span> |
* Interface all the controllers each with additional implemented features | * Interface all the controllers each with additional implemented features | ||
* Verify the rest of the communication over the CAN bus across the five controllers | * Verify the rest of the communication over the CAN bus across the five controllers | ||
Revision as of 19:37, 9 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
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/12/2016 | 10/18/2016 |
|
In progress | 10/18/2016 |
| 4 | 10/19/2016 | 11/01/2016 |
|
Not Started | 11/01/2016 |
| 6 | 11/01/2016 |
CAN COMMUNICATION DEMO |
Not Started | 11/01/2016 | |
| 7 | 11/01/2016 | 11/07/2016 |
|
Not Started | 11/01/2016 |
| 8 | 11/08/2016 |
PROJECT PROTOTYPE DEMO |
Not Started | 11/07/2016 | |
| 9 | 11/08/2016 | 11/15/2016 |
|
Not Started | 11/08/2016 |
| 10 | 11/16/2016 | 11/29/2016 |
|
Not Started | 11/15/2016 |
| 11 | 11/29/2016 |
PROJECT PROTOTYPE DEMO 2 |
Not Started | 11/29/2016 | |
| 12 | 11/29/2016 | 12/06/2016 |
|
Not Started | 12/06/2016 |
| 13 | 12/07/2016 | 12/15/2016 |
|
Not Started | 12/15/2016 |
| 14 | 12/21/2016 |
FINAL PROJECT DEMO |
Not Started | 12/21/2016 | |
| 15 | 12/20/2016 |
PROJECT REPORT SUBMISSION |
Not Started | 12/20/2016 | |
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.
