Difference between revisions of "F17: Rolling Thunder"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 85: Line 85:
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
| 09/19/2017  
+
| 09/20/2017  
−
| 09/25/2017  
+
| 09/26/2017  
 
|  
 
|  
 
* Order components and distribute project modules.
 
* Order components and distribute project modules.
Line 92: Line 92:
 
* Research on different sensors to be used.
 
* Research on different sensors to be used.
 
| Completed
 
| Completed
−
| 09/25/2017
+
| 09/26/2017
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2
−
| 09/26/2017  
+
| 09/27/2017  
−
| 10/02/2017  
+
| 10/03/2017  
 
|  
 
|  
 
* Set up project Git and Wiki page.
 
* Set up project Git and Wiki page.
Line 103: Line 103:
 
* Test the compatibility of each module.
 
* Test the compatibility of each module.
 
| Completed
 
| Completed
−
| 10/02/2017
+
| 10/03/2017
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
−
| 10/03/2017  
+
| 10/04/2017  
−
| 10/09/2017  
+
| 10/10/2017  
 
|  
 
|  
 
* <font color="indigo">Establish a connection over Bluetooth between the Android app and the BRIDGE controller.</font color>
 
* <font color="indigo">Establish a connection over Bluetooth between the Android app and the BRIDGE controller.</font color>
 
| Completed
 
| Completed
−
| 10/09/2017
+
| 10/10/2017
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
Line 120: Line 120:
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
−
| 10/10/2017
+
| 10/11/2017
−
| 10/16/2017
+
| 10/17/2017
 
|
 
|
 
* <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>  
Line 133: Line 133:
  
 
| Completed
 
| Completed
−
| 10/16/2017
+
| 10/17/2017
 
|-
 
|-
 
! scope="row"| 6
 
! scope="row"| 6
−
| 10/17/2017
+
| 10/18/2017
−
| 10/23/2017
+
| 10/24/2017
 
|  
 
|  
 
* <font color="blue"> Implement sensor code and perform standalone testing.</font color>  
 
* <font color="blue"> Implement sensor code and perform standalone testing.</font color>  
Line 148: Line 148:
 
* <font color="indigo">Receive data in the Android app from the SJOne.</font color>
 
* <font color="indigo">Receive data in the Android app from the SJOne.</font color>
 
| Completed
 
| Completed
−
| 10/23/2017
+
| 10/24/2017
 
|-
 
|-
  
Line 155: Line 155:
 
| [https://gitlab.com/RollingThunder/rolling-thunder-rc-car/blob/master/_can_dbc/243.dbc DBC File]
 
| [https://gitlab.com/RollingThunder/rolling-thunder-rc-car/blob/master/_can_dbc/243.dbc DBC File]
 
| Completed
 
| Completed
−
| 10/23/2017
+
| 10/24/2017
 
|-
 
|-
 
! scope="row"| 8
 
! scope="row"| 8
Line 164: Line 164:
 
|-
 
|-
 
! scope="row"| 10
 
! scope="row"| 10
−
| 10/24/2017
+
| 10/25/2017
−
| 10/30/2017
+
| 10/31/2017
 
|  
 
|  
 
* <font color="indigo">Transfer data over Bluetooth from the Android app to the SJOne.</font color>
 
* <font color="indigo">Transfer data over Bluetooth from the Android app to the SJOne.</font color>
Line 172: Line 172:
 
|-
 
|-
 
! scope="row"| 9
 
! scope="row"| 9
−
| style="text-align:center;" colspan="2"| 10/30/2017
+
| style="text-align:center;" colspan="2"| 10/31/2017
 
| Final Wiki Schedule
 
| Final Wiki Schedule
 
| In progress
 
| In progress

Revision as of 23:56, 30 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
  • 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
  • Order components and distribute project modules.
  • Research on project requirements.
  • Research on different sensors to be used.
 Completed 09/26/2017
2 09/27/2017 10/03/2017
  • Set up project Git and Wiki page.
  • Understand the hardware specifications of each component.
  • Study the datasheet of each component and the hardware interfacing.
  • Test the compatibility of each module.
 Completed 10/03/2017
3 10/04/2017 10/10/2017
  • Establish a connection over Bluetooth between the Android app and the BRIDGE controller.
 Completed 10/10/2017
4 10/10/2017 Wiki Schedule Completed 10/10/2017
5 10/11/2017 10/17/2017
  • Test ultrasonic sensors (maxbotix and parallax ping) and identify the suitable one for front and rear.
  • Verify basic commands to Traxxas motor, send basic commands (e.g. forward) to RC car from SJOne board.
  • Configure GPS device baud rate and interface it with SJOne board using UART.
  • Parse data received from GPS device to transmittable format.
  • Analyse the communication required across the controllers.
  • Chalk out the Message IDs based on the priority of the messages and the data to be sent across nodes.
  • Understand DBC and implement the DBC file compatible with all the controllers.
  • Transfer data from the Android app to the SJOne.
 Completed 10/17/2017
6 10/18/2017 10/24/2017
  • Implement sensor code and perform standalone testing.
  • Finish motor controller API. Test motor driving in different situations, begin to listen to CAN for controls.
  • Interface motor to the SJOne board and check for basic functionality.
  • Interface Compass module with SJOne board using I2C serial bus.
  • Interface Geo controller module with CAN Bus.
  • Establish communication across all the CAN controllers over CAN bus based on the DBC file.
  • Verify the power-up interactions and configurations between Master and the other controllers
  • Receive data in the Android app from the SJOne.
 Completed 10/24/2017
7 10/23/2017 DBC File Completed 10/24/2017
8 10/24/2017 DEMO: CAN communication between controllers Completed 10/24/2017
10 10/25/2017 10/31/2017
  • Transfer data over Bluetooth from the Android app to the SJOne.
 In progress
9 10/31/2017 Final Wiki Schedule In progress
11 10/31/2017 DEMO: Motors driven by sensor feedback
12 10/31/2017 11/06/2017
  • Filter sensor value readings and decide on incorporating the algorithm either in master controller or sensor controller based on performance testing
  • Continue testing motor driver via commands from CAN bus. Begin work on LCD display.
  • Calibrate GPS and Compass Module.Develop code for GPS and Compass module communication over CAN .
  • Add Google Earth/Maps to the Android app for selecting the car's destination.
 Not started
13 11/07/2017 DEMO: Motors driven by wheel feedback Not started
14 11/07/2017 11/13/2017
  • Implement obstacle avoidance algorithm based on filtered sensor data
  • Finish LCD display. Make adjustments to motor as needed based on testing.
  • Integrate all modules with the Master to test the data flow.
  • Interface Geo controller and Android controller.
  • Test each module individually
  • Verify the stringent requirement of Start-up Sync, Periodic heart-beat messages, Stop car through Bluetooth command.
Not started
15 11/14/2017 DEMO: Basic obstacle avoidance Not started
16 11/14/2017 11/20/2017
  • Test obstacle avoidance algorithm and fine tune sensor readings
  • Interface all the controllers each with additional implemented features.
  • Verify the rest of the communication over the CAN bus across the five controllers.
  • Implement motor feedback and IO display.
 Not started
17 11/21/2017 DEMO: GPS driving Not started
18 11/28/2017 12/04/2017
  • Verify the correct response of each module.
  • Test the accuracy of check-points from the Bluetooth controller, location data from the Geo-controller sensor and Navigation Algorithm
 Not started
19 12/05/2017 12/11/2017
  • Check for tuning or calibration of components if required.
  • Complete end-to-end testing for various scenarios and conditions.
Not started
20 12/20/2017

DEMO: Final Project

Not started
21 12/20/2017

SUBMISSION: Project Report

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=40150"