Difference between revisions of "S19: Hot Wheels"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 101: Line 101:
 
|   
 
|   
 
* Research previous projects wiki page and gather useful information.
 
* Research previous projects wiki page and gather useful information.
−
* Discuss about roles and study data sheet of the required parts and list down minimum two parts for each required function.
+
* Identify and discuss individual modules within the project and finalize roles of each team member.
 
* Demo CAN Communication
 
* Demo CAN Communication
 
|
 
|
Line 115: Line 115:
 
| 03/12/19
 
| 03/12/19
 
|  
 
|  
 +
* Each team member review their corresponding module hardware requirements and finish ordering required components.
 +
* Study data sheets of sensors used in each module.
 +
* Pick PCB design platform and begin work on PCB design/schematic.
 +
 
* Finish ordering components for addtl modules (GPS/compass, LCD, Sensors,etc)
 
* Finish ordering components for addtl modules (GPS/compass, LCD, Sensors,etc)
 
* Init Android project/begin work & research on UI fragments, Bluetooth, Maps API
 
* Init Android project/begin work & research on UI fragments, Bluetooth, Maps API
Line 132: Line 136:
 
| 03/19/19
 
| 03/19/19
 
|  
 
|  
−
* Finalize PCB design/order by end of week
+
* Finalize PCB design/order by end of week.
−
* Set-up Bluetooth API on Android app/transmit to board
+
* Each team member start work on implementing individually working modules.
−
* Interface GPS module to SJOne Board over UART
+
* Demo a "Hello World" program implementation by each module.
 
|
 
|
 
*  
 
*  

Revision as of 22:32, 12 March 2019

Project Title

<Team Name>

Abstract

In the HOT WHEELS project, we plan to design and construct an autonomously navigating, electric R.C car which uses CAN bus for internal communication and an android app for selecting car destination. Development of the R.C car's subsystem modules will be divided amongst the eight team members.

Introduction

The project was divided into N modules:

  • Sensor ...
  • Motor..
  • ...
  • Android

Team Members & Responsibilities

<Team Picture>

Gitlab Project Link - [1]

<Provide ECU names and members responsible> <One member may participate in more than one ECU>

  • Master Control
    • Kailash Chakravarty
    • Harmeen Joshi
  • Sensor
    • Rishabh Sheth
  • Motor
    • Kriti Hedau
    • Tahir Rawn
  • Geographical
    • Harmeen Joshi
    • Nandini Shankar
  • Communication Bridge Controller & Android Application
    • Swanand Sapre
    • Aquib Mulani
  • Code Review & Commit Approvers
    • Rishabh Sheth
    • Nandini Shankar



Schedule

Week# Date Task Status Completion Date
1 02/12/19
  • Form Teams
  • Completed
  • 02/12/19
2 02/17/19
  • Setup a Slack workspace for the team.
  • Setup private channel on Slack workspace
  • Completed
  • Completed
  • 02/17/19
  • 02/17/19
3 02/26/19
  • Create a Gitlab project and add all team members as well as Preet
  • Order CAN transcievers
  • All team members get familiar with the Gitlab environment and make their initial commit.
  • Completed
  • Completed
  • Completed
  • 02/26/19
  • 02/26/19
  • 02/26/19
4 03/05/19
  • Research previous projects wiki page and gather useful information.
  • Identify and discuss individual modules within the project and finalize roles of each team member.
  • Demo CAN Communication
  • Completed
  • Completed
  • Completed
  • 03/07/19
  • 03/07/19
  • 03/07/19
5 03/12/19
  • Each team member review their corresponding module hardware requirements and finish ordering required components.
  • Study data sheets of sensors used in each module.
  • Pick PCB design platform and begin work on PCB design/schematic.
  • Finish ordering components for addtl modules (GPS/compass, LCD, Sensors,etc)
  • Init Android project/begin work & research on UI fragments, Bluetooth, Maps API
  • Start working with PWM API to interface with RC Car
  • Make high-level block diagram of system
  • Pick PCB design platform and begin work on PCB design/schematic
  • In-Progress
  • In-Progress
  • Not Started
  • Not Started
  • Not Started
6 03/19/19
  • Finalize PCB design/order by end of week.
  • Each team member start work on implementing individually working modules.
  • Demo a "Hello World" program implementation by each module.
7 03/26/19
8 04/02/19
9 04/09/19
  • Finish implementing individual working modules.
  • Not Started
10 04/16/19
  • Work on integrating individual modules into the final testing.
  • Identify test cases for the integrated prototype model.
  • Start integration testing.
  • Not Started
  • Not Started
  • Not Started
11 04/23/19
  • Finish integration testing.
  • Finalize Wiki page documentation.
  • Not Started
  • Not Started
12 04/30/19
13 05/07/19
14 05/14/19
15 05/22/19
  • Final Demo

Parts List & Cost

Item# Part Desciption Vendor Qty Cost
1 RC Car Traxxas 1 $250.00
2 CAN Transceivers MCP2551-I/P Microchip [2] 8 Free Samples

Printed Circuit Board

<Picture and information, including links to your PCB>

CAN Communication

<Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.>

Hardware Design

<Show your CAN bus hardware design>

DBC File

<Gitlab link to your DBC file> <You can optionally use an inline image>



Sensor ECU

<Picture and link to Gitlab>

Motor ECU

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable Servo Motors

<Problem Summary> <Problem Resolution>


Geographical Controller

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable GPS lock

<Problem Summary> <Problem Resolution>


Communication Bridge Controller & LCD

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Insane Bug

<Problem Summary> <Problem Resolution>


Master Module

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Improper Unit Testing

<Problem Summary> <Problem Resolution>


Conclusion

<Organized summary of the project>

<What did you learn?>

Project Video

Project Source Code

Advise for Future Students

<Bullet points and discussion>

Acknowledgement

References

Retrieved from "http://socialledge.com/sjsu/index.php?title=S19:_Hot_Wheels&oldid=51826"