Difference between revisions of "F17: Rolling Thunder"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 97: Line 97:
 
CAN COMMUNICATION DEMO
 
CAN COMMUNICATION DEMO
 
| Not Started
 
| Not Started
−
| 10/30/2016
+
|  
 
|-
 
|-
 
! scope="row"| 7
 
! scope="row"| 7
Line 116: Line 116:
 
PROJECT PROTOTYPE DEMO
 
PROJECT PROTOTYPE DEMO
 
| Not Started
 
| Not Started
−
| 11/07/2017
+
|
 
|-
 
|-
 
! scope="row"| 9
 
! scope="row"| 9
Line 139: Line 139:
 
* 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
 
| Not Started
 
| Not Started
−
| 11/15/2017
+
|  
 
|-  
 
|-  
 
! scope="row"| 11
 
! scope="row"| 11
Line 156: Line 156:
 
* Verify the correct response of each module
 
* Verify the correct response of each module
 
| Not Started
 
| Not Started
−
| 12/06/2016
+
|  
 
|-
 
|-
 
! scope="row"| 13
 
! scope="row"| 13
Line 166: Line 166:
 
* Complete end-to-end testing for various scenarios and conditions
 
* Complete end-to-end testing for various scenarios and conditions
 
| Not Started
 
| Not Started
−
| 12/15/2016
+
|  
 
|-
 
|-
 
! scope="row"| 14
 
! scope="row"| 14
Line 173: Line 173:
 
FINAL PROJECT DEMO
 
FINAL PROJECT DEMO
 
| Not Started
 
| Not Started
−
| 12/20/2017
+
|  
 
|-
 
|-
 
! scope="row"| 15
 
! scope="row"| 15
Line 180: Line 180:
 
PROJECT REPORT SUBMISSION
 
PROJECT REPORT SUBMISSION
 
| Not Started
 
| Not Started
−
| 12/20/2017
+
|  
 
|}
 
|}
  

Revision as of 19:47, 9 October 2017

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
  • Order components and distribute project modules.
  • Research on project requirements.
  • Research on different sensors to be used.
 Completed 09/25/2017
2 09/26/2017 10/03/2017
  • Set up project Git and Wiki page.
  • 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
  • Understand the hardware interfacing of each of the modules and test compatibility
  • Analyse power requirements
 Completed 10/09/2017
3 10/09/2017 10/16/2017
  • Analyse the communication required across the controllers.
  • 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
4 10/16/2017 10/30/2017
  • 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
  • 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
6 11/01/2016

CAN COMMUNICATION DEMO

Not Started
7 11/01/2017 11/07/2017
  • 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
8 11/08/2016

PROJECT PROTOTYPE DEMO

Not Started
9 11/06/2017 11/13/2017
  • 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
  • Design the way-point algorithm and start with the implementation. </span>
  • Design the Navigation Algorithm and start with the implementation. </span>
 Not Started
10 11/13/2017 11/29/2017
  • Implement motor feedback and IO display. </span>
  • Complete the implementation of Android application. </span>
  • Interface all the controllers each with additional implemented features
  • Verify the rest of the communication over the CAN bus across the five controllers
 Not Started
11 11/29/2016

PROJECT PROTOTYPE DEMO 2

Not Started 11/29/2017
12 11/30/2017 12/05/2017
  • Test the accuracy of the data sent from the sensor and the settings to the Motor based on the Obstacle Avoidance 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
 Not Started
13 12/07/2017 12/15/2017
  • Check for tuning or calibration of components if required
  • Brainstorm on the test cases
  • Complete end-to-end testing for various scenarios and conditions
 Not Started
14 12/21/2016

FINAL PROJECT DEMO

Not Started
15 12/20/2016

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=F17:_Rolling_Thunder&oldid=39913"